Multiple BSOD's

Most common are MEMORY_MANAGEMENT and DRIVER_IRQL_NOT_LESS_OR_EQUAL


System specs:
Windows 7 64-bit
Intel i7 Extreme Edition
12 GB G.Skill DDR3
Dual nVidia GeForce GTX 480's SLI
MSI X58 PRO-E



Since the last MEMORY_MANAGEMENT BSOD I've removed half of the RAM sticks and cycle through so that all of them have been used. I also ran Memory Diagnostics on it. No errors were found, and I haven't gotten any MEMORY_MANAGEMENT errors since taking it down to 6GB. I'm completely stumped though. This is such a nice build and these blues are making me depressed!

cnvt09 said:

Most common are MEMORY_MANAGEMENT and DRIVER_IRQL_NOT_LESS_OR_EQUAL


System specs:
Intel i7 Extreme Edition
12 GB G.Skill DDR3
Dual nVidia GeForce GTX 480's SLI
MSI X58 PRO-E

If they are memory management you should download a 3rd party app called memtestx86, burn it to cd, and run it for at least 6 passes to test your memory.

Ken

I'll do that tomorrow after I get a blank CD to use. What about the DRIVER BSOD? I've supplied plenty of dump files for your reading pleasure.

cnvt09 said:

I'll do that tomorrow after I get a blank CD to use. What about the DRIVER BSOD? I've supplied plenty of dump files for your reading pleasure.

26 DMP's should take a while am running them now.


Just to save time and since they are very similar I ran the most recent 5.

There are several causes that still point towards memory. Not only do 3 of them point directly to memory but in 2 of them the first parameter also points to a memory exception.

It is either ram or video ram. If you havent, download memtestx868, burn it to cd, and run it for at least 6 passes.

I would also download cpu-z, and gpu-z (both free) to keep track of the temps.


Ken

Code:

BugCheck A, {778500520050, 2, 0, fffff80003496183}
Probably caused by : CI.dll ( CI!SHATransform+ea4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, 10342993f, fffff8800351cd48, fffff8800351c5b0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoInitializeAdapterUniqueString+4c5 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1A, {41790, fffffa8008e7e9b0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80003510c30, 0, 0}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc000001d, fffff8800fe1bc40, fffff88003fef1e8, fffff88003feea50}
Probably caused by : memory_corruption

@Jonathan,

I have two video cards I'm using in SLI. Are you suggesting one of them is bad? I could test with each individually, but they are identical, so I'm not sure if you're hoping I have a different model of a video card laying around (in that case, I do not).



Also, the blue screens happen much more often if the computer has been left turned off for an extended period of time, and they always happen before I can get to my desktop. If I can start running apps in windows then I know that I will not see any blues unless I restart.


ALSO, about 50% of the time, Windows fails to load successfully. I don't know why. Sometimes it fires right up, sometimes I can't get past the glowing Windows 7 logo at startup. I assume a re-install of the OS will fix that though.

I got some more blue screens today, only one DMP file to show you all.

Also, I'm not sure why, but I noticed that some of these DMP files are showing up as having occurred before I even built the computer... I'm starting to think I might need to reformat, because something is clearly confused.


I unplugged one of my video cards and for the first time after 8 attempts, the computer booted up with no errors. I'm going to try it again later using only the other card.

Here's the new one.

I ran memtest for 10 passes. I was having issues running it from disc so I used a USB, I assume it doesn't matter.

0 total errors


I don't know if this is a clue, but often times, the bsod's happen when windows is starting, as in, "Starting Windows" is on the screen when it happens, NEVER once my programs start running. Sometimes I know the BSOD is coming because my desktop gadgets stop working... usually BSOD within 10 seconds of that failure.