J
James338
I believe I have a driver problem that is causing black/blue screens but I'm not sure which driver is causing the problems. I've updated and reverted my display driver multiple times so I don't believe that is the issue. Below are reports from WhoCrashed. Is there a better way to find out which specific driver could be causing the issue.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 6/23/2020 9:57:31 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062320-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x9C (0x80000001, 0xFFFFAF0154BD9B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 6/23/2020 9:57:31 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!HalBugCheckSystem+0x1A89)
Bugcheck code: 0x9C (0x80000001, 0xFFFFAF0154BD9B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 6/12/2020 8:12:00 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-8156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFB400017EA180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 6/10/2020 11:00:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061020-5796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFE78B31DEA8B0, 0xFFFF8A8D81608670)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a 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.
Continue reading...
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 6/23/2020 9:57:31 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062320-5265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x9C (0x80000001, 0xFFFFAF0154BD9B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 6/23/2020 9:57:31 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!HalBugCheckSystem+0x1A89)
Bugcheck code: 0x9C (0x80000001, 0xFFFFAF0154BD9B10, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 6/12/2020 8:12:00 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061220-8156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFB400017EA180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 6/10/2020 11:00:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061020-5796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFE78B31DEA8B0, 0xFFFF8A8D81608670)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a 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.
Continue reading...