To disable the automatic restart you can go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
Then click on the Advanced tab, then on the Startup and Recovery Settings button. In the next window, uncheck the box that says "Automatically restart", then click on OK to exit the dialog. The next time it happens, your system will stay on the BSOD until you restart it.
A BugCheck is nearly identical to a BSOD error message. You can generally use the error messages interchangeably. In this case, it's the last 2 figures that matter (d1). Here's a couple of links:http://aumha.org/win5/kbestop.php#0xd1http://www.osronline.com/ddkx/ddtools/bccodes_2zdz.htm
Generally this error is caused by a faulty device driver (as you already know). Further troubleshooting will involve determining where the error occurred (in which file). To do this, please follow this procedure:
- The first place to get the information is from the Blue Screen itself. Write down all of the long numbers, the description that's in all Caps with underscores ( _ ) between the words, and any file names that may be mentioned (be sure to note if there wasn't a filename in your post). A more in depth look at this is included in the second reference ( How To Use The Event Viewer ).
In the event that the BSOD flashes by too fast to read, use the first reference to disable the Automatically Restart function ( How To Disable Automatic Restarts ).
- The next place to find the information is in the Event Viewer. Use the mini-guide in the second reference to see how to do this ( How To Use The Event Viewer ).
- The last place to find the information is on your hard drive. Search your hard drive for files ending in .dmp and .mdmp. You're looking for the most recent file (or the one closest to the last BSOD that you experienced). Once you find it, use the third reference ( How To Debug Memory Dumps ) to perform an analysis of the memory dump. Be sure to use the !analyze -v command in the bottom of the Debugger's window before closing out your session. Then copy and paste the results into your next post. Someone will have a look at it to see if we can figure out what's gone wrong.
- Sometimes, when Error Reporting is enabled, the dump files will be stored temporarily on your system and are erased once the report is sent. To save this info, you'll have to copy the dump file before sending the report. To do this, just click on the "Details" link in the error report and you'll see some file locations listed. Choose the one that ends in .dmp or .mdmp, locate it in Windows Explorer, and copy it to your Desktop (you'll have to enable viewing of hidden files to do this). Here's an example of the Details:
ERROR REPORT CONTENTS Following files will be included in this error report
C:\DOCUME~ 1\Owner\ LOCALS~1\Temp\WER7fde.dir00\Mini112706-02.dmp
Edited by usasma, 12 December 2006 - 09:46 AM.
- John (my website: http://www.carrona.org/ )
**If you need a more detailed explanation, please ask for it. I have the Knack. ** If I haven't replied in 48 hours, please send me a message.
My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)
FYI - I am completely blind in the right eye and ~30% blind in the left eye.
If the eye problems get worse suddenly, I may not be able to respond.
If that's the case and help is needed, please PM a staff member for assistance.