- May 18, 2020
- 34
- 3
- 535
Hello, over the past couple of days I've been getting intermittent BSODs after my computer has been running for an hour or 2. I was suspicious of a driver that Windows 10 updates had installed last week so I updated the driver via geforce experience. Afterwords I installed any windows 10 updates that at the time were failing. To fix the updates I had to run the windows 10 trouble shooter after which I restarted and the updates pushed through without an issue. Based off of the recent BSOD I think its caused from my GPU failing but I'm not sure. I bought it back in 2016. I'm also concerned because I was having issues with my PC when I first built it last year but I haven't had any problems since then. In that case it turned out to be a bad CPU and I'll link the thread above the WhoCrashed logged. I might be able to get a GPU from a friend but it is a 1060 from his old build. Any and all advice is appreciated!
edit: forgot to say current GPU driver is 466.47
edit 2: The last time my computer failed I didn't see a bsod but it did restartand then I got the VIDEO_SCHEDULER_INTERNAL_ERROR I did check windows 10 updates for today and the only thing was Windows Defender Definition update.
PC Specs
CPU: Ryzen 5 3600x
Mobo: MSI x570-a pro (RMA twice)
Ram: pny xlr8 16gb ddr4 3200 (replaced once)
GPU: GTX 1060 6gb (working from old build and tried other graphics cards)
Hard Drive: Intel 660P M.2 (Currently in the process of RMA)
Temp HardDrive: Western Digital WD5000aakx
PSU: Thermal Take Smart 750w bronze (from old build)
Previous issue: https://forums.tomshardware.com/threads/computer-bsod-after-about-a-week-of-use.3608058/
WhoCrashed Log:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 5/27/2021 7:01:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xE0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF8204FB94F960, 0xFFFFCA0BC146E590)
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.
On Thu 5/27/2021 7:01:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052721-10609-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF8204FB94F960, 0xFFFFCA0BC146E590)
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.
On Wed 5/26/2021 7:55:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052621-10156-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003B6F10, 0x800000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Wed 5/26/2021 6:57:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052621-10328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x7F (0x8, 0xFFFF8A80D7454E70, 0xFFFFEE89C755E4FC, 0xFFFFF806417F0C28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Fri 5/21/2021 4:26:58 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052121-12765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024BB1451D, 0xFFFFF400C4A90028, 0xFFFFF400C4A8F860)
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 Sun 2/28/2021 10:00:50 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022821-11671-01.dmp
This was probably caused by the following module: mmcss.sys (0xFFFFF8017B1F1061)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017B1F1061, 0xFFFF9407887EFA58, 0xFFFF9407887EF290)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mmcss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MMCSS 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 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.
edit: forgot to say current GPU driver is 466.47
edit 2: The last time my computer failed I didn't see a bsod but it did restartand then I got the VIDEO_SCHEDULER_INTERNAL_ERROR I did check windows 10 updates for today and the only thing was Windows Defender Definition update.
PC Specs
CPU: Ryzen 5 3600x
Mobo: MSI x570-a pro (RMA twice)
Ram: pny xlr8 16gb ddr4 3200 (replaced once)
GPU: GTX 1060 6gb (working from old build and tried other graphics cards)
Hard Drive: Intel 660P M.2 (Currently in the process of RMA)
Temp HardDrive: Western Digital WD5000aakx
PSU: Thermal Take Smart 750w bronze (from old build)
Previous issue: https://forums.tomshardware.com/threads/computer-bsod-after-about-a-week-of-use.3608058/
WhoCrashed Log:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 5/27/2021 7:01:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xE0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF8204FB94F960, 0xFFFFCA0BC146E590)
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.
On Thu 5/27/2021 7:01:42 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052721-10609-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x3AD0)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF8204FB94F960, 0xFFFFCA0BC146E590)
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.
On Wed 5/26/2021 7:55:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052621-10156-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF680003B6F10, 0x800000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Wed 5/26/2021 6:57:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052621-10328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x7F (0x8, 0xFFFF8A80D7454E70, 0xFFFFEE89C755E4FC, 0xFFFFF806417F0C28)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Fri 5/21/2021 4:26:58 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052121-12765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6CF0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8024BB1451D, 0xFFFFF400C4A90028, 0xFFFFF400C4A8F860)
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 Sun 2/28/2021 10:00:50 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022821-11671-01.dmp
This was probably caused by the following module: mmcss.sys (0xFFFFF8017B1F1061)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8017B1F1061, 0xFFFF9407887EFA58, 0xFFFF9407887EF290)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\mmcss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MMCSS 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 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.
Facebook
Twitter
Instagram