BSOD crashes, appears to be related to bad driver

[drJanitor]

Hello,

My computer has been BSODing/Randomly shutting down the past couple of days. I've downloaded a couple of programs to try to help diagnose the problem but have so far come up empty handed. I've run memtest86+ as well as the windows memory diagnostics because of the errors I've seen, however neither one of these have reported errors. If anyone has time please take a look at this. Any help would be greatly appreciated!

If any additional information is required please let me know. Attached should be a copy of the sf_diagnostics.

Thanks

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1A[/COLOR], {41287, 30, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454b5 )

Usual causes:  Device driver, memory, kernel

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

 

[drJanitor]

BlueRobot:

Thanks for the tip. I will run the memtest on each stick and in each DIMM slot. I will let you know the results. Thanks so much!

 

[drJanitor]

Hello:

So I've tested all of my RAM for at least passes. This is the testing I did:

RAM Stick 1 in DIMM Slots 1-4 (29 passes in DIMM 1, 8 in the rest)
RAM Stick 2 in DIMM Slot 2 (12 passes)
RAM Stick 3 in DIMM Slot 3 (30 passes)
RAM Stick 4 in DIMM Slot 4 (15 passes)

So, I'm not sure if I should test RAM Sticks 2-4 in the other DIMM slots but that didn't make logical sense to me. There were no errors in any of the tests.

Is there a next logical step? Could it just have been that the RAM needed to be reseated?

Thanks in advance for any help

 

[x BlueRobot]

Use Driver Verifier to scan for any corrupted which may be causing problems, it works by running various stress tests on the drivers, in order to create a BSOD which should hopefully locate the driver; run for least 24 hours.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[drJanitor]

Hmm, before I was able to run the verifier my computer blue screened again, and now seems to have trouble even getting past loading (as it crashed while trying to load windows so now it has to restore the settings. Should I try to load up some additional dump files (if I can even get that far)

 

[x BlueRobot]

Yes, upload any additional .dmp files which have occured

Here's some additional help and information for Driver Verifier:

• http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[drJanitor]

BlueRobot

FIrst, thanks for helping me with all this stuff. Secondly, I don't know how to proceed any further. Here is what has been happening:

I come home from work, try to turn my computer on, it tells me (since its been BSODing during boot now) that it needs to repair windows. I allow it to do that. It repairs windows without a problem, and I get all the way to my computer. I tried to run the SF diagnostics tool, but during that process, it always blue screens. So, unfortunately, I can't get you the additional blue screens because my computer won't stay on long enough.

On an interesting side note, after the computer BSODs the first time (while running the SF tool) I try to restart it, and before windows is done loading, it BSODs again, and continues to get shorter and shorter for how long the computer will run. That is, until I remove a stick of memory, upon which the process basically restarts. I remove a stick of memory, it will start up, repair windows, let me log in, start running the SF tool and then BSOD again.

Are there any further suggestions?

 

[x BlueRobot]

Find this directory:

C:\Windows\Minidump

Then attach any .dmp files which have been saved there, using:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[drJanitor]

Thanks so much for your help. I was able to log on just long enough to get the dump files as well as part of a SF diagnostics tool report. Here is what I have. So, I realize that some of the dmp files are from several months ago, but if they help please take a look at them. If there is anything I can do to help with this process just let me know.

Just as an FYI, the final blue screen (after I got all these files had an error of "PFN_LIST CORRUPT")

 

[x BlueRobot]

[COLOR="red"]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff80002aad4f0, fffff880039625c8, fffff88003961e20}

Probably caused by : [COLOR="Red"]rdyboost.sys[/COLOR] ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control

rdyboost.sys is the Windows driver for the Ready Boost feature, and seems to be causing some issues, disable Ready Boost and then post back your results:

• http://www.sevenforums.com/tutorials/33289-readyboost-setup-use.html