Solved BSOD with System Thread, IRQL Less than, Memory Managment, etc.

[ZedDEAD]

Hello,
I just want to say thanks for checking out my post, as this has been an ongoing problem with my computer for about a year now.

First off, when the BSOD's started I tried a computer repair store hoping they would find the problem right away. While they had my computer it never blue screened once. So they weren't able to find the problem, however they never even tried to look at my dump files. So, I decided it was time to take matters into my own hands. After some searching I still couldn't find the problem, and pretty much gave up and just let the occasional BSOD occur. They use to happen around once every 4-5 days, but now its twice or even three times a day depending on which games I'm playing, sometimes when I'm just on the desktop too!
It's getting pretty frustrating, and I am hoping I will get lucky and can have someone help me solve this problem... But here is the .zip file. Thank you for taking the time to look
The BSOD's seem to be mostly inconsistent, but the ntoskrnl.exe has been the cause several times, so I'm not sure if there is something corrupted there or what. Anyways thanks again for checking this out, and any help would be super awesome!

 

[Golden]

fffff880`059c34e0  fffffa80`09020000
fffff880`059c34e8  fffffa80`081719f0
fffff880`059c34f0  00000000`00000001
fffff880`059c34f8  fffff880`1328675dUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B][COLOR="Red"]nvlddmkm.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x21e75d
fffff880`059c3500  fffffa80`00000001
fffff880`059c3508  fffff880`059c4558

Uninstall the display driver then reboot. Now reinstall the driver only, following these specific steps outlined here:
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

fffff880`09fa5e40  fffff880`09fa6280
fffff880`09fa5e48  00000000`00000000
fffff880`09fa5e50  fffff880`13d5ace9Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [B][COLOR="red"]Rt64win7.sys[/COLOR][/B]
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0xbce9
fffff880`09fa5e58  fffffa80`078c7918
fffff880`09fa5e60  fffffa80`09dad665
fffff880`09fa5e68  fffff880`09fa626
.
Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        F[B][COLOR="red"]ri Mar 16 23:31:36 2012[/COLOR][/B] (4F6339B0)
    CheckSum:         000B1298
    ImageSize:        000AA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Realtek network driver - its outdated.

You need to run a few tests:

RAM - run 8 passes, no less
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Storage - run the DOS verison of the SHORT test only
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[ZedDEAD]

Thanks for checking my issue out Golden!
So I went through and did a fresh install of the Nvdia Driver, and went to my motherboards website to update most of the drivers (Ethernet Realtek Driver, USB, CPU, and Audio) No BSOD's during the process which is nice Later tonight I will run the Memtest86 as well as the Storage Short test, and let you know the results. Thank you again for the help so far!!

 

[ZedDEAD]

Okay so I ran Memtest86+ and I am pretty sure I found the problem!
Test 1 had 38 errors with both sticks in, so I took one out and got 24 errors, tried again on the same stick with 138 errors! Then I moved that stick to another slot and got a ridiculous 811 errors
So I pulled that stick out and used the second one, with much much better results as it passed with flying colors I believe the problem must of been a bad stick of RAM. Ill be replacing it soon, so for now I'll just use 4GB.
Thank you for the advice and help this busy time of year! I am so happy that you have found a solution to this never ending problem lol. Ill keep testing but if I have no BSODs for sometime I think it will be safe to say it's fixed.

 

[Golden]