PAGE_FAULT_IN_NON_PAGED_AREA, random BSODs

anthonylert · 04 Mar 2014

Okay, I've run the MemTest three times, for a total of 25 passes and no errors. MemTest isn't going to find anything at this point. Right now I'm using the same drivers I used on my previous rig, cleanly installed twice. They never had an issue on the previous rig, but I suppose a change in hardware (motherboard, processor, and memory all being new) might affect it. There's enough differences in each bluescreen that chasing software won't go anywhere in my opinion.

I've started testing for further BSODs at a hardware level, starting with memory. I'll be removing one stick at a time to see if removing any given stick will result in a change in performance. I will do this until only one stick is left; if at that point BSODs keep happening, I can be confident the RAM isn't the issue. I have a known good video card I can install as well, to check for the same thing. Can you recommend anything to test the CPU?

Arc · 04 Mar 2014

anthonylert said:

Okay, I've run the MemTest three times, for a total of 25 passes and no errors. MemTest isn't going to find anything at this point. Right now I'm using the same drivers I used on my previous rig, cleanly installed twice. They never had an issue on the previous rig, but I suppose a change in hardware (motherboard, processor, and memory all being new) might affect it. There's enough differences in each bluescreen that chasing software won't go anywhere in my opinion.

I've started testing for further BSODs at a hardware level, starting with memory. I'll be removing one stick at a time to see if removing any given stick will result in a change in performance. I will do this until only one stick is left; if at that point BSODs keep happening, I can be confident the RAM isn't the issue. I have a known good video card I can install as well, to check for the same thing. Can you recommend anything to test the CPU?

Sound plan!

To stress test the CPU, you may follow it:
Hardware - Stress Test With Prime95

anthonylert · 04 Mar 2014

Stress tested the CPU for two hours as directed by tutorial. No errors on any of the eight logical CPUs. Removed fourth stick of RAM first and awaiting results. Previous record for no BSOD was six days, so if it goes a week without one I think I'll have sussed the issue.

anthonylert · 06 Mar 2014

End of first day after removing first stick. No BSODs so far, which is a significant departure in and of itself (over the last week, been getting them about every twelve to sixteen hours or so). Will continue monitoring.

anthonylert · 09 Mar 2014

Still no BSODs after the end of the fourth day. If it passes the week without incident, it will either be that particular RAM stick or the motherboard RAM slot. I'll have to narrow it down by putting one of the working sticks in that slot and see if BSODs return, but that will likely be the end of it. Will update again.

Arc · 09 Mar 2014

anthonylert said:

Will update again.

Its OK. :)

anthonylert · 11 Mar 2014

Welp, end of fifth day, another BSOD. Our old friend 0x3B, ntoskrnl.exe+75169. Attached dump. I'm fairly confident that the memory or the board is the culprit by this point, leaning toward the board given how reseating staves off BSODs for days at a time compared to once a day stop errors.

Arc · 11 Mar 2014

It appears that you havent taken the suggestions of post #20.

And still the display driver is not applied as suggested, unfortunately nothing more is left from our part.

Rest is on you.
__________________________________

Code:

fffff880`09aafa78  fffff880`0f5517b5Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xc87b5
-----------------------------------------
fffff880`0f489000 fffff880`100d2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Dec 19 22:32:52 2013 (52B326BC)
    CheckSum:         00C19112
    ImageSize:        00C49000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

anthonylert · 11 Mar 2014

Strange, I DID roll back to--oh, wait... right, I'd had to do a system restore at one point because Windows had stopped booting. Whoops. Reverting driver now.

anthonylert · 20 Mar 2014

Nine days of stability. I think I'm at the point where I've figured out the issue, the one-off video driver notwithstanding. Thank you very much for your input, it greatly assisted my troubleshooting process.