Windows 10: BSOD Random Page_Fault_In_Non_Paged_Area with Debug Files

I randomly got a Blue Screen called Page_Fault_In_Non_Paged_Area while playing a game. I had this blue screen before and I thought it would disappear once I downloaded Windows 10. It has came up again and I am afraid that I may loose my computer. What should I do in this error? I uploaded debug files for someone to look up. I do want to state one thing, my intel CPU did reach above 170 F (~76 C) in core temp.

I really need help, files and things are backed up but I need this computer for college, and I cannot afford another one. *cry

:)

 

Windows 10, BSOD - ntoskrnl.exe problem

Just had the BSOD error "PAGE_FAULT_IN_NON_PAGED_AREA"

I was trying to play the game Firewatch at the time, launched into a save state. Almost immediately froze and then the BSOD appeared.

Any suggestions?

 

random Freezing leads to BSOD. I give up.

Stop code is random.

like CRITICAL_PROCESS_DIED, BAD_SYSTEM_CONFIG_INFO, DPC_WATCHDOG_VIOLATION..

I've got multiple BSOD and the stop code is that random.

right now after multiple debugging the issue, I hypothetically assume it's my nvme fault.

I've ordered a new nvme drive and gonna retest the system if this will works.

 

CPU-Z is being blamed here, although I believe the same driver is used by Speccy.
Code: BugCheck 50, {ffffe00100000018, 0, fffff80130f024a2, 2} *** WARNING: Unable to verify timestamp for cpuz138_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz138_x64.sys Could not read faulting driver name Probably caused by : cpuz138_x64.sys ( cpuz138_x64+24a2 )[/quote]
As you don't have CPU-Z installed as far as I can see I'd recommend uninstalling Speccy for the time being. Do you have the latest version installed?

 

I do have Speccy installed, and I researched the problem, it seems like people are blaming Speccy. I'll go uninstall it. I want to keep this thread open incase if I have any other problems.

 

Threads will always stay open on here. If you ever mark a thread Solved you can always mark it unsolved if problems arise in the future.

I'm not sure which version of Speccy you had installed but you could try this one. I've been running it without issue.

 

So far uninstalling Speccy has given me no BSOD, and I again had the current most recent version. I'll see if this one works.

 

Tried installing your version of Speccy, right as I opened it, I got a BSOD with the same error, attaching log files.

If you find a fix, please let me know. I mean if it is unfixable, I would like an alternative program. I also have done research and Speccy does give some BSOD for some other people.

 

Yep it's Speccy again. I'll drop a line to Piriform and leave Windows Feedback see if they can get to the bottom of it. I'm sure it will be sorted soon, but it looks like uninstalling it for now.
Code: Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff802000800b6, 0, fffff800afc724a2, 2} *** WARNING: Unable to verify timestamp for cpuz138_x64.sys *** ERROR: Module load completed but symbols could not be loaded for cpuz138_x64.sys Could not read faulting driver name Probably caused by : cpuz138_x64.sys ( cpuz138_x64+24a2 ) Followup: MachineOwner[/quote]

 

Thank you, if they do fix the bug, please send an update. Speccy is a great tool when it doesn't give BSOD.

 

Guessing there has not been an update yet?