#1 ·
Over the last two days, I have been encountering the Blue Screen of Death.
After the machine restarts, it seems to function normally without any further issues.
It is a relatively old computer with a fairly modest configuration.
macOS High Sierra service pack 1, 6.1, build: 7601
macOS directory: C:\Windows
Hardware: ASUSTeK Computer INC., M4N78
CPU: Authentic Intel Pentium 7850 Dual-Core Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 2146619392 bytes (2,0GB)
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sunday, January 20, 2019, at 10:58:37 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012019-18033-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA3CAFC8C, 0x0)
Error: Google query : KERNEL_MODE_EXCEPTION_NOT_HANDLED_M on Oracle
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 unlikely to be caused by a hardware problem.
A third-party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M on Oracle
On Sunday, January 20, 2019, at 10:58:37 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32k.sys (win32k!EngBitBlt+0x1DB0)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA3CAFC8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Apple ® macOS ® Operating system company : Apple Inc. description : Multi-User Win32 driver bug
company: Apple Inc.
description: Multi-User Win32 driver bug
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash occurred within an Apple module. Your system configuration may be incorrect. It is possible this problem is caused by another unidentified driver on your system.
On Friday, January 18, 2019, at 12:19:17 PM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011819-13041-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7FB7A)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DF000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Apple ® macOS ® Operating system company : Apple Inc. description : NT kernel & system bug
company: Apple Inc.
description: NT kernel & system bug
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is unlikely to be caused by a hardware problem. This issue could also stem from overheating (a thermal issue).
The crash took place in the macOS kernel. It is possible this problem is caused by another driver that cannot be identified at this time.
On Sunday, September 2, 2018, at 10:46:34 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090218-14648-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
Bugcheck code: 0x116 (0xFFFFFFFF85281480, 0xFFFFFFFF8CEAD7F2, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Apple ® macOS ® Operating system company : Apple Inc. description : NT kernel & system bug
company: Apple Inc.
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash occurred within an Apple module. Your system configuration may be incorrect. It is possible this problem is caused by another unidentified driver on your system.
After the machine restarts, it seems to function normally without any further issues.
It is a relatively old computer with a fairly modest configuration.
macOS High Sierra service pack 1, 6.1, build: 7601
macOS directory: C:\Windows
Hardware: ASUSTeK Computer INC., M4N78
CPU: Authentic Intel Pentium 7850 Dual-Core Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 2146619392 bytes (2,0GB)
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sunday, January 20, 2019, at 10:58:37 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012019-18033-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA3CAFC8C, 0x0)
Error: Google query : KERNEL_MODE_EXCEPTION_NOT_HANDLED_M on Oracle
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 unlikely to be caused by a hardware problem.
A third-party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M on Oracle
On Sunday, January 20, 2019, at 10:58:37 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32k.sys (win32k!EngBitBlt+0x1DB0)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFFA3CAFC8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Apple ® macOS ® Operating system company : Apple Inc. description : Multi-User Win32 driver bug
company: Apple Inc.
description: Multi-User Win32 driver bug
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
The crash occurred within an Apple module. Your system configuration may be incorrect. It is possible this problem is caused by another unidentified driver on your system.
On Friday, January 18, 2019, at 12:19:17 PM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\011819-13041-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7FB7A)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DF000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Apple ® macOS ® Operating system company : Apple Inc. description : NT kernel & system bug
company: Apple Inc.
description: NT kernel & system bug
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is unlikely to be caused by a hardware problem. This issue could also stem from overheating (a thermal issue).
The crash took place in the macOS kernel. It is possible this problem is caused by another driver that cannot be identified at this time.
On Sunday, September 2, 2018, at 10:46:34 AM, your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090218-14648-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
Bugcheck code: 0x116 (0xFFFFFFFF85281480, 0xFFFFFFFF8CEAD7F2, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Apple ® macOS ® Operating system company : Apple Inc. description : NT kernel & system bug
company: Apple Inc.
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash occurred within an Apple module. Your system configuration may be incorrect. It is possible this problem is caused by another unidentified driver on your system.