I had a blue screen of death. Please tell me how to find out what it

smalltime0

Distinguished
Apr 29, 2008
309
0
18,780
Do you have more than one stick of RAM?
Try only having 1 stick at a time if you do...

Also please post your system specs. Sorta hard to tell you what to do without them.
 

shadowduck

Distinguished
Jan 24, 2006
2,641
0
20,790
Welcome to the pointless Vista Event Viewer!

Without specs you won't get replies.
Describe your system and what you did just prior to the BSOD. Turn off Auto Restart too.
 

shadowduck

Distinguished
Jan 24, 2006
2,641
0
20,790
Right Click my computer--> Properties

Click "Advanced system settings" in Vista or Click on the "Advanced" tab in XP..

Click Settings under "Startup and Recovery"

Uncheck "Automatically Restart" under System Failure
 

carver_g

Distinguished
Feb 10, 2007
341
0
18,810
If it's Vista, tap F8 after post (before OS boot) and one of the options will be something like turn off automatic restart after system failure. I don't know if this also works for XP.
 

carver_g

Distinguished
Feb 10, 2007
341
0
18,810


That's assuming the OS boots all the way. The OP is a little vague about this....
 

utahraptor

Distinguished
Sep 25, 2003
63
0
18,630
I was just wondering if windows logged the blue screen message and if so where it was located. I don't see why you would need my system specs to tell me that :( Sorry if I was not clear.
 

carver_g

Distinguished
Feb 10, 2007
341
0
18,810


We don't need your specs for that. :)

It 'logs' the blue screen in the sense that it does a memory dump. Rather than wade through and decode all that, just disable auto restart as explained above, and then have a look at the blue screen itself. It will give you a filename or a general message. It will also give you several memory strings. I've found that if you google the first two, you will often get a hit that will point you in the right direction.

Good luck.
 
Thanks Shadowduck.

@OP:
I followed those steps last year and it gave me a chance to see the blue screens. The useful part in them was the reference to nv4_disp.dll. I used that with Google and figured out my nVidia drivers were the problem. Your problem might be totally different, of course, but a file name would help a lot.
 

TRENDING THREADS