BSOD - Several Error Types pointing to ntoskrnl.exe

v4l33 · 10 Jan 2014

I finally managed to get memtest86 to run overnight again, tho just for 6 passes (11.5h), don't have the time to leave it for longer atm because I rely on the PC for my work.

@Britton30 I uninstalled Spybot right after the scan, I don't like having software installed on my PC that I just use once a year, it's a habbit. :)
As for the drivers I will try to do that if I get another BSOD, would make sense since the crashes occured lately after numerous driver updates, one of them might be causing problems.

Currently waiting to see if uninstalling IDM and updating the NIC drivers will make a difference.

Arc · 10 Jan 2014

Memtest passed good (though 8 passes would be better).

Let us know how it goes.

v4l33 · 13 Jan 2014

Got another crash today, this is the most serious so far, no crash dump created.

Went for a shower for about 20min, left MS Publisher and Firefox open, and this is what I got when i got back. I have no idea what's going on.

ICIT2LOL · 13 Jan 2014

Again my 2 cents worth may be worth trying one of these and I would start with the Kaspersky one

5 Bootable AntiVirus Rescue CD for Windows: Free Download

v4l33 · 13 Jan 2014

Gonna format all the partitions and reinstall the OS today, tired of losing work because of these crashes, hopefully it's something software related and the problems will solve this way.

v4l33 · 18 Jan 2014

Reinstalled Windows clean, 3 days later another BSOD. I'm inclining to believe is a hardware problem, but no idea what exactly, could it be the motherboard?

Arc · 18 Jan 2014

It appears that some issue with the display driver is there.

Code:

fffff880`02f8cf38  fffff880`02d4ffc1Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x2efc1

Despite of using the latest one, 13.12 WHQL, as was seen in post #19.

If you know that the RAM, CPU, GPU and PSU are not failing, then the issue will be tagged with the motherboard.

v4l33 · 18 Jan 2014

Well the last crash was during a game. And something I didn't mention regarding the GPU because I thought it was irrelevant. I got a Sapphire HD 7770 OC edition, the clock and memory are overclocked from factory, and before getting all these ntoskrnl.exe crashes I kept getting crashes related to the video driver but only in a few games, never while idle or low load. Decided to lower the frequencies a little and those errors dissapeared. Could it be that lowering the frequencies closer to stock AMD ones is causing these ntoskrnl.exe related crashes? Tho the GPU passes Furmark stress tests without a problem.

Arc · 18 Jan 2014

ntoskrnl.exe is not anything responsible for the crash, but it is the karnel on which the crash is occurring. When the dump recording mechanism fails to assign a cause, it blames the karnel itself, wrongly.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

v4l33 · 18 Jan 2014

Speccy link here.
Tested again with Furmark with Xtreme Burn-in and PostFX options enabled, at default OC factory clocks, no artifacts and no crashes, temperature evens out at 83 degrees Celsius.
This I don't get it, the GPU seems fine with OC clocks during burn-in tests but crashes in some games. Before the BSODs in games I get screen flickering because Windows reports GPU timeout and trying to recover, and after 3-4 attempts it goes to BSOD. Once I lower the GPU clocks these problems disappear so guess it's either the GPU, PSU or the PCIE bus. But a stress test should give a hint if there's a problem, shouldn't it? :/