Boot Log

[Bare Foot Kid]

Hello everyone!

When one of y'all has time, will you please check this for me? I'm clueless.
I just want to make sure everything is in order.

View attachment 4232


Thank You Ted

 

[Dzomlija]

Hello everyone!

When one of y'all has time, will you please check this for me? I'm clueless.
I just want to make sure everything is in order.

View attachment 4232


Thank You Ted

Ted,

Generally speaking, the boot log is only usefull in determining which drivers are loaded by the system during boot. Unfortunately, not many of us know how to read it properly because it only lists the file names of the drivers, and those are mostly cryptic and provide no clues as to which driver it belongs to.

I'm looking at the last section of the log you attached (labelled " Service Pack 1 5 29 2008 19:07:43.375"). This gives an indication that the log was created on 29 May 2008 at 19:00? I'm guessing you rebooted you pc then...

The First two entries, "ntkrnlpa.exe" and "hal.dll" are the Window Kernel (the heart of the OS), and the Hardware Abstraction Layer.

A little further down, is se entries for "msisadrv.sys" and "msiscsi.sys". I'm guessing that by their filenames alone, you're using an MSI motherboard?

What you can do to figure out which files are for what is to Google for a particular filename. Another place to try identify what each file is would be FileNet (Windows XP file forum). Other than that, it takes a bit of practice to "decode" the filenames to determine what they are for. Here are some tips to help identify what a file belongs to:

"USB" - The file likely belongs to your USB drivers
"CDROM" - Self explanatory
"NTFS" - Handles the NTFS file system on storage devices.
"TCP" - chances are this file has something to do with the TCP/IP protocol on your network

One other thing to remmber is the higher in the log a file is loaded, the more important that file is. This is why "ntkrnlpa.exe" and "hal.dll" is right at the top. Nothing else will work if either of those two file are missing or corrupted.

The above is not entirely helpful, and woefully incomplete (I'm still sometimes stumped myself by the log), but I hope that clears it up a little...

 

[Bare Foot Kid]

Hello Dzomlija,

How have you been doing and how is Prometheus working out?

Thank you for your explanation.
As you say the "Bootlog" is cryptic to say the least!
It may be something I will continue to learn to decipher, we shall see.
I am so new to all this that other things need 'learning' first... haha!

Thanks again Peter!


Later Ted

 

[Dzomlija]

Hello Dzomlija,

How have you been doing and how is Prometheus working out?

Thank you for your explanation.
As you say the "Bootlog" is cryptic to say the least!
It may be something I will continue to learn to decipher, we shall see.
I am so new to all this that other things need 'learning' first... haha!

Thanks again Peter!


Later Ted

Ted,

Prometheus is, to put it mildly, like the Energizer Bunny - she just keeps going and going. I've run the gamut of processes to try and bring her to her knees, but I've yet to find anything wher the hardware cannot cope (other than Crysis - that beast bring down just about every computer I've seen!)

Peter