BSOD - Several Error Types pointing to ntoskrnl.exe

Arc · 18 Jan 2014

v4l33 said:

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? :/

Something like this? A balloon from the systrey?

If so, it is the GPU. But furmark will not be able to catch it.

I am also a victim of this, with my earlier GPU

v4l33 · 18 Jan 2014

Yes, exactly that. But like I said the problem goes away once I lower the default factory OC clocks, so guess it's related to the OC/PSU. The question remains, could it be the cause to the ntoskrnl.exe BSODs during idle/low load after I lower the GPU clocks? I mean can a combination of GPU core/memory frequencies lead to system instability, even tho it supports higher clocks?
E.g.
HD 7770 default AMD clocks - 1000/1125
HD 7770 default Sapphire OC clocks - 1100/1250 <- video driver timeout
HD 7770 OC lowered clocks - 1050/1200 <- no video driver timeout, possible ntoskrnl.exe BSOD cause?

Arc · 18 Jan 2014

Factory overclocks, as it is said by our overclocking team, are designed to bear that overclocking.

If the issue goes away with reducing the magnitude of the OC, thats a good news.

Though I doubt that the stability will be carried forward for long, but my best wishes will be with you.

I am not very experienced with overclocking, but our overclocking team is the authority. I am requesting them to suggest you here.

v4l33 · 18 Jan 2014

That's what I thought also, and having the PC holding up during Prime95, Furmark and OCCT full load stress tests I suppose it rules out a bad PSU also since the power drainage is maxed during those tests.
I don't know what else to do, guess I'll have to bear with these crashes until I change my PC or the faulty hardware fails for good. :/
Anyway, thanks a lot for the support, learned alot during this debugging. :)

v4l33 · 18 Jan 2014

Ok so got another BSOD, see attachment, and I think this one is a lucky one.
This is what WinDbg says:

Code:

STACK_COMMAND:  kb
SYMBOL_NAME:  ZEROED_PAGE_CORRUPTED
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware_ram
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED
BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED
Followup: MachineOwner

So it's safe to assume that the memory is faulty afterall, even if memtest86 passed succesfully?

Britton30 · 18 Jan 2014

The debug files really make no distinction between types of memory Although yours says hardware_ram, it could be memory in the GPU or CPU even, the different cache levels. It may possibly also be the hard drive cache, I'm not sure.

v4l33 · 18 Jan 2014

Dang it. So back to square one I guess. I'll run memtest86 again for the 3rd time overnight and see what results I'll get.

Britton30 · 18 Jan 2014

Swap your RAM modules to different slots to see if still no errors.

v4l33 · 18 Jan 2014

Did that already a week ago or so, wanted to test maybe the motherboard slots are faulty, sadly still getting crashes.

Britton30 · 18 Jan 2014

Ok, sorry I can't help you. Back to you Arc.:)