Solved Random BSODs

[Faintuk]

BSODs occurring usually around twice daily. They often happen when gaming, but I've also had them when browsing the web.

 

[Faintuk]

I've run memtest+ twice (total of 12 passes) and received no errors.

 

[Arc]

Welcome aboard, Faintuk

► Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.


► upload your MSINFO32.nfo file. It will help us to get some more insight to your system.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[Faintuk]

I'll try Driver Verifier now.

 

[Arc]

Well, let us know if it crashes in verifier or not.
We will review the further dumps and the msinfo simultaneously

 

[Faintuk]

The system crashed almost immediately, with the BSOD indicating dadder.sys was at fault, the driver for my old 1800dpi Razer Deathadder mouse. I've replaced it with another mouse to see if anything changes. Attachment should contain the latest minidump.

 

[Arc]

well done!
Now you may disable driver verifier, and see if the system works perfectly or not.

If needed, that may be enabled again!

 

[Faintuk]

Thank you for your help. Will post again if problems return!

 

[Arc]

Thank you for your help. Will post again if problems return!

It's a nice experience to deal with a geek

 

[Faintuk]

Another BSOD (System Service Exception)! Re-enabled verifier.

 

[Faintuk]

Two more crashes with verifier enabled. Unfortunately they were both restarts and did not generate BSODs. Could an inadequate PSU be the cause? My current one is 380w.

 

[Arc]

Two more crashes with verifier enabled. Unfortunately they were both restarts and did not generate BSODs. Could an inadequate PSU be the cause? My current one is 380w.

Tough to say, but easy to say that you get a higher one, of at least 600w

 

[Faintuk]

Installed a new PSU. Reinstalled windows. Updated to service pack 1 and almost an immediate bsod. Attached the details. I've received different instructions for using verifier. Do I need Standard settings, Force pending I/O requests, and IRP Logging all ticked?

 

[Faintuk]

Installed this hotfix Computer randomly stops responding because of a deadlock situation in Windows Server 2008 R2 or in Windows 7. If nothing works I'm going to give the 32bit version of w7 a try.

 

[Arc]

Run Memtest86+, for at least eight passes.

Let us try to search the cause of the crashes in the memory.

 

[Faintuk]

I've already run memtest+ for 12 passes. No BSODs since applying this hotfix though, including when gaming. Cautious optimism that it fixed the issue...

 

[Faintuk]

Another BSOD. Occured when in-game. Nothing new, error code 3b.

 

[Arc]

Next step: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Do it.

 

[Faintuk]

Ran Furmark for 20 minutes with the settings suggested. Temperatures never exceeded 58 Celsius and I saw now visual errors. In light of this (and the replaced PSU & successful memory checks) I rolled back the bios version to the last stable build and am yet to experience a blue screen. Fingers crossed...

 

[Arc]

May we see your latest crash dumps?