BSOD while gaming, mulitple error codes.

[Salamandrex]

Just recently started getting BSOD's while gaming, two so far. However the fashion in which they happened are similar to the last time my computer BSOD in which the CPU was faulty.Having replaced it I went 2 months BSOD free until last night's batch. Was hoping to find a solution to the problem. Temps when running were at or near normal during gaming around 35 on CPU 49 on Mother board and Graphics card and 30 on Hard drive. Any help would be greatly appreciated.

 

[Arc]

Your crash is STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL . http://www.carrona.org/bsodindx.html#top
Usual causes: Device driver.

But no trace of a device driver is found in the stack. 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.

 

[Salamandrex]

Hello, thanks for the response. Ran driver verifier and got a BSOD attached is the dmp zip. I'll continue to run it for another crash to provide the most information possible. The latest BSOD occurred while i was playing a game for about 10 minutes and it was a PFN list corrupt which from my understanding points towards RAM? Thanks for the help so far

 

[Maguscreed]

Arc may disagree, but after looking at that... well it has some really strange info in the unloaded module list.
Basically I suggest running this overnight to check your memory at this point.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
(if it hits errors right away you can stop it, but generally they recommend allowing it to run for many passes to be sure.)

 

[Salamandrex]

Alright will do thanks for the help! Does the strange info usually indicate anything particular?

 

[Maguscreed]

well memory dumps are ...dumps of what was in memory. If that's not coming out straight there is a possibility there is a problem with the physical RAM itself. I'm still not ruling out his initial call of 'driver problem' ram is just really easy to check overnight while you sleep.

 

[Arc]

No question of disagree, Maguscreed You are much more knowledgeable and experienced than me
And, if a crash with Driver verifier enabled also indicate to memory corruption, your suggestion RAM - Test with Memtest86+ is my suggestion, too!

 

[Salamandrex]

Went through 9 passes and no errors were found.

 

[Golden]

9 passes in two hours???????? Are you sure it wasn't 9 tests only?

 

[Salamandrex]

I started it last night before bed when Magus suggested it. Running for 15 hours now.

 

[Golden]

Whew! Thats better! Or you have lightning RAM...............you mentioned previous CPU issues, so I wonder if its worth checking that quickly again?

http://www.sevenforums.com/tutorials/220743-cpu-stress-test-using-intelburntest.html

 

[Salamandrex]

Ran stable throughout only reaching a max temp of 52. Which is odd considering these symptoms are the same I had with the other malfunctioning CPU. Maybe it's a video card problem considering the crashes mostly happen during gaming or shortly after.

 

[Vir Gnarus]

There are indeed a number of crashes related to your video card, one way or another. Your ATI driver looks like it's from Apr 5, 2012, so you'll wanna update it. In addition, a BIOS update and chipset driver updates for your motherboard should be in order. Remove all software that came with your motherboard as well, since these things are known for causing the issues you're mentioning. Only leave (and update) drivers that came with, no utilities, 'enhancement' software or anything like that.

I'm also kinda puzzled by the two oddball unloaded modules Magus mentioned. They look strangely like they have some sort of pattern to them, but otherwise their names are unusual and garbled. I know malware looooves to use scrambled module names, so that can be a cause in addition to potential memory corruption.

I've also found what looks to be a c0000102 error in one of your latest crashes, which if correct, is talking about a corrupt file on disk. Run CHKDSK /R followed by SFC /SCANNOW (preferably SFC ran from Windows DVD, not from disk) just to confirm we aren't dealing with disk issues.

Overall, we're kinda shooting in the dark right now. My suspicions kinda weigh in favor of the graphics card problem, but anything can go with this kind of unreliable data (minidumps aren't the best resource of data).

 

[Salamandrex]

I updated all my drivers and chipsets and ran the chdsk as well as SFC. As far as the concern of Malware that was my first thought too so i ran a Malware Bytes scan and it came back clean. I also use MSE as recommend by the site. No crash as of yet. I'll continue normal use and see if the problem crops up again.

 

[Salamandrex]

No crashes since October 9th then today I received this one while watching a video. Normal gaming use was used in between crashes nothing new downloaded and Malwarebytes and MSE are fully updated.

 

[Vir Gnarus]

If I'm reading this correctly, it seems like there's a problem when DirectX attempted to do a DMA (direct memory access) to your GPU's memory cache. The graphics drivers themselves are from July, so I'm wondering if they need updating. Otherwise, this may smell of a problem with your graphics card. This coincides with the fact it happens during gaming. However the running process at the time that caused this crash was Google chrome. Were you running a game inbrowser?

 

[Salamandrex]

No I was watching a stream on chrome at the time. I'll try updating again thanks for the reply

 

[Salamandrex]

Also the fact it went so long without a crash would that indicate that its a driver problem instead of a hardware on the gpu?

 

[Vir Gnarus]

Urp, ok, I misread your previous post. You're saying gaming is ok, but that one streaming in chrome was what bugged it out?

 

[Salamandrex]

Yeah, it's been fine for the past couple weeks until this one. I'll keep gaming and see if that causes any crashes but as of now the chrome crash was the only one. I think you might be right about it being a graphics problem considering it was watching a video game stream.