Random BSODs: Usually error 0X0000001E, distorted screen + audio

[redlock]

Update Windows 7 completely.

If you get a BSOD after Windows has been updated, re-run the .bat file and upload the zip file again please.

I was starting to believe!

I updated one full, uh, tier, let's say, and my system was solid for a week. A whole week. Then I had a crash and thought, "fair enough, I didn't update all the way, so let's keep going." (I generally hate updating once the system is solid because of bugs. Right now, my taskbar with Aero on is set to black, but it fluctuates between black and default blue for reasons I can't determine...something with Desktop Window Manager, I guess. That's for another thread.)

Did that and I've had 3-4 crashes since. My system freezes on the blue screen and doesn't write a minidump, but the last message was INTERRUPT_EXCEPTION_NOT_HANDLED 0x000003D.

I've attached the latest zip from the batch, if you're still up for lending a pasta tentacle.

 

[Golden]

There is no .dmp file present...please re-run the .bat file and check contents prior to uploading.

 

[redlock]

There is no .dmp file present...please re-run the .bat file and check contents prior to uploading.

I checked the minidump folder and it seems the last few crashes didn't generate a dmp; I just have files from last month. I had to hard-reset on the blue screen, which interferes with the dump writing process, maybe?

 

[Golden]

Yes, it might still be writing the file.

Try this instead.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[redlock]

Yes, it might still be writing the file.

Try this instead.

Please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

Ran Verifier, got a crash which rebooted the machine on its own (Memory Management 1A), couldn't boot Windows so I restarted in Safe Mode, deactivated Verifier and rebooted. Upon reboot I visited the minidump folder...and no dmp was written.

Should I just try again? edit: going through with another Verifier run. Will update.

 

[Golden]

Follow these steps:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Then, when the system next BSOD's, follow this:

1. Download this .BAT file to your desktop

Download


2. Right-click the .BAT file and 'Run as Administrator'
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

 

[redlock]

Again, I went a while this time with no crashes, then a few days with a few crashes without writing a dump. The latest 2 crashes left dumps, though, so here's the zip from the batch file as well as the latest 2 dumps, just in case.

 

[redlock]

Few more crashes recently. Here's the latest SF Debug zip.

 

[redlock]

Well, crashes are occurring more and more often and getting Windows to boot properly takes some power cycling and patience. BlueScreenView also lists an exception error when I try to access minidump information.

I think I'll try a reinstall and, if it happens again, take my machine to a tech. Thanks for your help, Golden.