New
#1
Page_fault_in_nonpaged_area
Currently suffering from some random timed BSOD after installing new motherboard/cpu/ram and upgrading to Windows 10 from 7. Originally upgraded, but had the same PAGE_FAULT_IN_NONPAGED_AREA BSOD, so I completely formatted my hard drive and installed a fresh copy of Windows 10 to see if it would help. Worked fine for a day or so, then got the same bsod earlier today. Doesn't seem to happen when I'm doing anything in specific, in fact, earlier today I was laying down trying to sleep and noticed it had BSOD.
Thanks for your help.
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., H170-PRO
CPU: GenuineIntel Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17102602240 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 6/13/2016 1:27:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061316-12718-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFD000C54B5A58, 0x0, 0xFFFFF80172BFD9E7, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 6/13/2016 1:27:46 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFD000C54B5A58, 0x0, 0xFFFFF80172BFD9E7, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.