Creating a boot log file

  • Thread starter Thread starter X_HOBBES
  • Start date Start date
X

X_HOBBES

I've just discovered that Win2000 doesn't write the boot log file to disk
until the SMSS.EXE process starts (when it's preparing network connections),
which means that the system needs to boot properly before it writes the log
file. Which genius thought of this bright idea??? The whole point of the
stupid boot log file is to diagnose boot problems. If the log file isn't
written to disk until the near end of boot up, then there's nothing to
diagnose if the system crashes before it boots up all the way. BRILLIANT
mastermind that thought this one through! That's kind of like having a
flight recorder only record flight data once the plane lands safely on the
ground -- pointless!!!

Does anyone know of a way to diagnose bootup problems where the system
freezes before the stupid SMSS.EXE service starts?

X_HOBBES
 
Post the exact text of any error messages you receive.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
<snip>
| Does anyone know of a way to diagnose bootup problems where the system
| freezes before the stupid SMSS.EXE service starts?
<snip>
 
No error messages -- just complete freeze requiring a hard power off of the
system. But since it freezes before the SMSS.EXE service starts, there's no
boot log file -- the boot log is cached to memory until SMSS.EXE starts,
then it gets written to disk.
 
More than likely some hardware failure.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| No error messages -- just complete freeze requiring a hard power off of
the
| system. But since it freezes before the SMSS.EXE service starts, there's
no
| boot log file -- the boot log is cached to memory until SMSS.EXE starts,
| then it gets written to disk.
 
Not quite -- this is one of several other Win2000 HDD's I use on this same
ThinkPad T22. They all work fine except for this one image. Unfortunately,
I need to get this image working. I would love to figure out which device
driver is causing the hangup, as I suspect a bad driver somewhere. But the
problem I'm faced with is that I can't find out at which point it's crashing
because Windows doesn't write the boot log file to disk until it's almost
completely booted up -- again, I think this is a very stupid implementation
of a log file feature. It should write each event to disk as it happens, so
if it stops, you know where it stopped.

So, my question still stands... how can I determine which device driver is
causing the hang up if I can't get a boot log file from windows? I suppose
I could disable every single driver and then turn one on at a time, but that
seems like it would be a bit time consuming.

Anybody have a suggestion?

X_HOBBES
 
Try a safe mode boot.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Not quite -- this is one of several other Win2000 HDD's I use on this same
| ThinkPad T22. They all work fine except for this one image.
Unfortunately,
| I need to get this image working. I would love to figure out which device
| driver is causing the hangup, as I suspect a bad driver somewhere. But
the
| problem I'm faced with is that I can't find out at which point it's
crashing
| because Windows doesn't write the boot log file to disk until it's almost
| completely booted up -- again, I think this is a very stupid
implementation
| of a log file feature. It should write each event to disk as it happens,
so
| if it stops, you know where it stopped.
|
| So, my question still stands... how can I determine which device driver is
| causing the hang up if I can't get a boot log file from windows? I
suppose
| I could disable every single driver and then turn one on at a time, but
that
| seems like it would be a bit time consuming.
|
| Anybody have a suggestion?
|
| X_HOBBES
 
I would try to boot in Safe Mode and see what it says.

--
George Hester
_________________________________
X_HOBBES said:
No error messages -- just complete freeze requiring a hard power off of the
system. But since it freezes before the SMSS.EXE service starts, there's no
boot log file -- the boot log is cached to memory until SMSS.EXE starts,
then it gets written to disk.



Dave Patrick said:
Post the exact text of any error messages you receive.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
<snip>
| Does anyone know of a way to diagnose bootup problems where the system
| freezes before the stupid SMSS.EXE service starts?
<snip>
Click to expand...
Click to expand...
 
Back
Top