- May 31, 2013
- 65
- 0
- 18,630
This isn't a problem specific to Windows 10, it's been happening since Windows 8. Randomly I'll get a BSOD when waking my computer from sleep, with different errors each time. The crash dumps always point to a driver problem but never specifies which except once (NVIDIA driver). I don't think that NVIDIA driver is the overall problem since this issue has been going on for 3 years. My PC specs are:
Here are the dumps:
On Mon 2/8/2016 3:13:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020816-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0xC2 (0x10, 0xFFFFC001D9626AD0, 0x318022A, 0xFFFFC001D9626AF0)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
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 2/1/2016 8:30:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020116-8421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8001BCAF4AC, 0xFFFFD000216D9790, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 1/28/2016 1:36:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012816-15109-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xDFDCE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8019E4DFDCE, 0xFFFFD00023C1CE78, 0xFFFFD00023C1C690)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
■
On Sun 1/10/2016 12:15:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011016-8390-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8017C0E7F20)
Bugcheck code: 0x50 (0xFFFFE000C52E001C, 0x0, 0xFFFFF8017C0E7F20, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.75
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.75
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
Windows 10
Gigabyte GA-Z87X-UD4H
16 GB Corsair Vengeance RAM
EVGA GTX 980
Here are the dumps:
On Mon 2/8/2016 3:13:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020816-8062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0xC2 (0x10, 0xFFFFC001D9626AD0, 0x318022A, 0xFFFFC001D9626AF0)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
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 2/1/2016 8:30:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\020116-8421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8001BCAF4AC, 0xFFFFD000216D9790, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 1/28/2016 1:36:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012816-15109-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xDFDCE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8019E4DFDCE, 0xFFFFD00023C1CE78, 0xFFFFD00023C1C690)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
■
On Sun 1/10/2016 12:15:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011016-8390-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8017C0E7F20)
Bugcheck code: 0x50 (0xFFFFE000C52E001C, 0x0, 0xFFFFF8017C0E7F20, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 361.75
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 361.75
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 361.75 , NVIDIA Corporation).
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
Facebook
Twitter
Instagram