ntoskrnl.exe crashing with PAGE_FAULT_IN_NONPAGED_AREA

gcline33

Reputable
Nov 6, 2015
3
0
4,510
When playing dota 2 I occasionally get a bsod with this error. I replaced the ram about a month ago with new ram when upon early digging I suspected it might be bad ram, it doesn't appear to be the case.

Build info:
cpu: AMD FX 8100
motherboard: gigabyte 2AC8
ram: 16 gb DDR3
gpu: AMD Radeon HD 7770




Dump Files from blue screen viewer:


==================================================
Dump File : 100716-73726-01.dmp
Crash Time : 10/7/2016 12:09:18 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`3ab8c000
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`15324de2
Parameter 4 : 00000000`00000000
Caused By Driver : usbohci.sys
Caused By Address : usbohci.sys+36516000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70180
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\100716-73726-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 292,470
Dump File Time : 10/7/2016 12:11:19 AM
==================================================

==================================================
Dump File : 091216-51339-01.dmp
Crash Time : 9/12/2016 11:27:25 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`2e370000
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`1533f292
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6f400
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.23539 (win7sp1_ldr.160902-0600)
Processor : x64
Crash Address : ntoskrnl.exe+6f400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091216-51339-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 288,214
Dump File Time : 9/12/2016 11:29:04 PM
==================================================

==================================================
Dump File : 090416-58313-01.dmp
Crash Time : 9/4/2016 3:09:11 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`2cdcc000
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`15377292
Parameter 4 : 00000000`00000000
Caused By Driver : USBD.SYS
Caused By Address : USBD.SYS+277e0000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+6f400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090416-58313-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 288,158
Dump File Time : 9/4/2016 3:11:24 AM
==================================================

==================================================
Dump File : 082816-56519-01.dmp
Crash Time : 8/28/2016 12:26:59 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff8a0`27b5c000
Parameter 2 : 00000000`00000001
Parameter 3 : fffff880`1533f292
Parameter 4 : 00000000`00000000
Caused By Driver : netbt.sys
Caused By Address : netbt.sys+23c30000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+6f400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082816-56519-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 288,158
Dump File Time : 8/28/2016 12:29:07 PM
==================================================
 
Solution
I suspect that's the problem. Try updating the driver from it's OEM website if you haven't. Or try uninstalling the driver if you are already using the latest OEM driver and try using the default driver from windows instead.
I suspect that's the problem. Try updating the driver from it's OEM website if you haven't. Or try uninstalling the driver if you are already using the latest OEM driver and try using the default driver from windows instead.
 
Solution