XP BSOD's

[AzKidd69]

I know quite a few of you out there are runnin XP and are having BSOD's as I can see from the threads floating around here...

I have 2 real quick changes to offer that can really help out in your troubleshooting quests..

First of type "msconfig" in the run box and select the boot.ini tab.,,

then put a check mark in the box that says /BOOTLOG
while in here go to the startup tab and clean up what loads @ startup
then hit apply, ok and exit without restart

this will create a file called ntbtlog in your windows folder for XP that can be opened with notepad to see what drivers/services fail to load..

next thing to do to get rid of all those magically disappearing BSOD's open control panel system (or any other of a million ways to get to the system applet {windows+break}, etc...)

then select the advanced tab... then click the button for settings under startup and recovery..

under 'System Failure" select Write an event to the system log, and unselect Automatically restart
now you will see program errors in your event log under Administrative Tools and you will now be able to write down that sometimes crytic but normally helpful error message info when you get a BSOD..

[Lycia]

Originally posted by AzKidd69
I know quite a few of you out there are runnin XP and are having BSOD's as I can see from the threads floating around here...

I have 2 real quick changes to offer that can really help out in your troubleshooting quests..

First of type "msconfig" in the run box and select the boot.ini tab.,,

then put a check mark in the box that says /BOOTLOG
while in here go to the startup tab and clean up what loads @ startup
then hit apply, ok and exit without restart

this will create a file called ntbtlog in your windows folder for XP that can be opened with notepad to see what drivers/services fail to load..

next thing to do to get rid of all those magically disappearing BSOD's open control panel system (or any other of a million ways to get to the system applet {windows+break}, etc...)

then select the advanced tab... then click the button for settings under startup and recovery..

under 'System Failure" select Write an event to the system log, and unselect Automatically restart
now you will see program errors in your event log under Administrative Tools and you will now be able to write down that sometimes crytic but normally helpful error message info when you get a BSOD..

Doesn't clicking on RUN, then typing "eventvwr" negate the need to do th efirst one?

[AzKidd69]

Not necessarily.. I have seen items pop up in a boot log that were prior to the Event Reporting Service Loading...

Since the service is not loaded it will not be reported...