BSOD, typically after gaming sessions.

[Dlovinger]

Hi all,

Over the last few weeks I've been seeing BSODs, and I figured it's time to do something about it. Today it's happened twice, with the first error being an "APC_INDEX_MISMATCH," which got stuck on initializing a .dmp file. This was after playing some Civ5, as in quit, left the r oom, came back to a BSOD (while playing I forgot to turn on vsync, temps ~70C- higher than I like but well within a safe range). A few hours later, after playing some more Civ (nothing too intense, temps never above 55C this time, etc), I got the BSOD that's attached here. For some reason it never made a full dump file, just a minidump. There should be plenty of harddrive / pagefile space, so that isn't an issue.

Attached is most of the hardware/pc info that you'll need.

Some other notes. A few months ago I upgraded to a 780Ti, before which I didn't really see these blue screens. I can't say that's the culprit, but hopefully you can all help. I clean reinstalled graphics drivers last week, so that shouldn't be an issue either. I'm suspecting memory as well, so I'll probably run windows mem diagnostic tonight.

Anyway.. I'll check the thread in the morning, so let me know if there's any additional info I can provide. Thanks for any help you can provide.

 

[Dlovinger]

So I ran a quick windows memory diagnostic, which didn't turn up with anything. I'm not sure if I should run a longer memtest86 or not..

 

[Dlovinger]

Bump... I'd love to see some opinions on this..

 

[Dlovinger]

Adding to this. I had another BSOD last night, again 5-10 minutes after playing a game. This was a little different though. The error message was "IRQL_NOT_LESS_THAN_OR_EQUAL." About a second after this blue screen appeared the pc shut off. It then tried to restart a second or two later. Then it shut down, and again attempted to restart. This looping continued until I flipped the power in the back. For the record, I do have "automatic restart" disabled in system options. After flipping the power back on and starting, it continued to loop again. Unfortunately no .dmps were created. This morning it is working fine.

From the above, I'm guessing that something is overheating. It seems like the computer was not allowed to start due to high temps. Correct me if I'm wrong though. But what I don't understand is why this happened a few minutes after gaming, not during. I did not get a chance to check my cpu temps, so I'm not sure if that's the problem. I'm also not sure if this is related to the previous BSOD.

Should I order new thermal paste asap? Any other ideas? Thanks.

EDIT: I should mention that, while I did not see temps just before the shutdown, I do regularly monitor temperatures and I've never seen anything abnormal. I have a Hyper 212EVO on the CPU, which is idling at 36C now and goes up to 50C, maybe 60C, under load. The GPU I've never seen go above 70C under load.

 

[Dlovinger]

I ran Memtest86 last night for 8 passes with zero errors and normal cpu temps. I don't believe it's a memory problem. I'm kind of thinking it's not the cpu overheating either. That leaves the GPU, which was the newest piece of hardware. I don't really believe that it's overheating, but then I can't explain the 'looping restart' issue I was having...

I feel like I'm talking to an empty room with uneducated speculation. Can someone please help?

 

[Dlovinger]

Just happened again. Playing diablo 3, minimized the game for a couple minutes, and got a blue screen. "Dumping physical memory to disk" got stuck at 95 for at least 30 minutes before I restarted, and hence no .dmp files. The message was "Driver_IRQL_NOT_LESS_THAN_OR_EQUAL." I wouldn't even mind getting another blue screen if I could just get some diagnostic info out of it...

I'm more worried though. After turning on, windows loaded to desktop and then immediately crashed again. The blue screen came up for about 2 seconds before the computer turned off and began power cycling again, as I had described above. I coulnd't catch the error message, though it was different than any previous.

It's on and *hopefully* stable now, but it seems to be getting more frequent.

 

[Maphesta]

Hi, did you ever find a solution to this problem?

I am having the same issues as you describe. Exactly the same. Nothing seems to overheat. Was it your memory, despite 0 memtest errors? I'm thinking it's my memory somehow..

 

[Laith]

Hi, did you ever find a solution to this problem?

I am having the same issues as you describe. Exactly the same. Nothing seems to overheat. Was it your memory, despite 0 memtest errors? I'm thinking it's my memory somehow..

Please do not bump 6 year old threads. If you have an issue, make your own thread instead.