New
#1
BSOD - ntoskrnl.exe & ntkrnlmp.exe
Hi, I've recently been getting multiple BSOD errors cause by the following modules ntoskrnl.exe and ntkrnlmp.exe
Here is a WhoChrased report:
On Thu 2017-08-03 1:33:12 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 2017-08-03 1:33:12 PM 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: 0x139 (0x3, 0xFFFFB00124994DB0, 0xFFFFB00124994D08, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
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 2017-08-03 1:22:34 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-9203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF3F7F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF802DD579F7F, 0xFFFFD4806A368698, 0xFFFFD4806A367ED0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 2017-08-03 1:16:46 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x50 (0xFFFFCC019AA9D068, 0x0, 0xFFFFF802EED3CBF3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Thu 2017-08-03 1:06:29 PM your computer crashed
crash dump file: C:\Windows\Minidump\080317-12078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801A3B08D00, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.