Hi,
Haven't posted in awhile, my rig has been running smoothly up until several days ago. Things started acting up on the evening of March 20th, couldn't do a system restore since it said there were no points. The system crashed while playing the Witcher 3, black screen with looping sound. Then again a couple more times. I've tried using DDU to uninstall the display driver then re-install, a few different releases now, the latest driver as well as old ones.
I've been getting all sorts of crashes. Whenever I run a game it will crash. Just browsing the desktop the monitor will randomly go black for 5 seconds then come back with the green 'DVI' box in the bottom right corner. With the way Nvidia's drivers are it's hard to if I have hardware problem or what is really going on...
When the screen turns black I can't even get the monitor menu to pop up when pressing the button on the monitor, which it normally does even when the PC is off.
I'm getting these errors, not sure if anyone knows what the likely cause is. I've tried re-installing windows 10. Can't seem to find much from searching. Thanks for any help. I'm thinking it may be time to RMA the GPU.
Right now I'm on another PC and the monitor is working fine.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: GAMING-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17125642240 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/23/2017 11:21:51 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032317-13218-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x34AE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCC816DC44960, 0xFFFF9406D04684A0)
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 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 Thu 3/23/2017 11:21:51 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xCE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCC816DC44960, 0xFFFF9406D04684A0)
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 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 Wed 3/22/2017 9:54:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032217-13171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Tue 3/21/2017 10:09:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032117-13125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFBE0199F2A420, 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.
Haven't posted in awhile, my rig has been running smoothly up until several days ago. Things started acting up on the evening of March 20th, couldn't do a system restore since it said there were no points. The system crashed while playing the Witcher 3, black screen with looping sound. Then again a couple more times. I've tried using DDU to uninstall the display driver then re-install, a few different releases now, the latest driver as well as old ones.
I've been getting all sorts of crashes. Whenever I run a game it will crash. Just browsing the desktop the monitor will randomly go black for 5 seconds then come back with the green 'DVI' box in the bottom right corner. With the way Nvidia's drivers are it's hard to if I have hardware problem or what is really going on...
When the screen turns black I can't even get the monitor menu to pop up when pressing the button on the monitor, which it normally does even when the PC is off.
I'm getting these errors, not sure if anyone knows what the likely cause is. I've tried re-installing windows 10. Can't seem to find much from searching. Thanks for any help. I'm thinking it may be time to RMA the GPU.
Right now I'm on another PC and the monitor is working fine.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: GAMING-PC
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17125642240 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 3/23/2017 11:21:51 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032317-13218-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x34AE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCC816DC44960, 0xFFFF9406D04684A0)
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 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 Thu 3/23/2017 11:21:51 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xCE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFCC816DC44960, 0xFFFF9406D04684A0)
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 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 Wed 3/22/2017 9:54:08 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032217-13171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Tue 3/21/2017 10:09:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032117-13125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFBE0199F2A420, 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.
Facebook
Twitter
Instagram