Hi all.
This issue started quite a while back up to a year or more. It would be random failures to boot with the "ntoskrnl.exe" being listed as corrupt or missing. In the past doing a reboot would get me into the OS, I had no issues once the PC was in windows.
Now, recently while playing DCS in the FA-18 hornet the game began to stutter, the audio crackled, the PC became unresponsive and finally displayed a BSOD with "DPC_WATCHDOG_VIOLATION".
Now my PC will do this randomly. It has happened just browsing this forum for example. Sometimes I get away with some severe stuttering and audio artifacts for any time between 5 and 30 seconds then it comes good, other times it will hang indefinitely, and others it will BSOD.
It will happen watching videos on and offline as well, I have tried watching the videos off of both my RAID drives and my OS SSD.
The crash seems to occur quickly when playing a game called OSU. The audio will loop, and the frames will loop as well.
Interestingly the UI in the game does not freeze, for instance; the combo counter will fall to zero, and not get stuck where it was like the cursor and playing field does. It will then either BSOD, or allow me to escape the game.
I tried runnining OSU off of a RAM disk (I thought maybe a hard drive or SSd issue), same problem.
I've done a lot of troubleshooting on my own and have got nowhere.
This is what I have tried thus far.
- Disabling SLI
- Updated BIOS
- Updated intel rste drivers (hardware raid)
- Clean Re-install of windows 10
- Removed all OC's from my hardware
- Ran Prime 95 for several hours no crash
- Ran 3D Mark TimeSpy for several hours no crash
- Updated Samsung SSD Firmware
- Updated Drivers for SSD
- Clean install of graphics divers
- Took machine to local IT repair shop, stress tested all components - pass (they never experienced a crash or hang - which led me to believe my power delivery at home was the cause)
- (decided to check some things myself), bought a multimeter and tested PSU
- Swapped out my old power extention leads and power-boards
- Updated my Sound Blaster driver
Perhaps its peripheral? Though I believe nothing I have connected to the PC could draw enough power to be an issue. I have connected
- one WD Elements 107C 4TB external (Has its own power) USB 3.0
- Razer Blackwidow keyboard 2x USB 2.0
- Razer Ouroboros mouse USB 2.0
- Logitech Z200 stereo speakers (Plugged into GameBlaster sound card) (rarely used)
- Logitech G35 Headset USB 2.0
- ASUS VG278HE monitor (Dual link DVI into top GPU)
Also worth noting temperatures are not an issue, I have watercooled CPU and GPU's, their temps never reach more than 60c.
I am at my wits end, I have no expertise in this sort of thing and frankly am close to binning this damned thing.
My PC
OS: Windows 10 Home 64-bit
Mobo: ASROCK X79 Extreme 9.
GPU: 2x EVGA GeForce GTX 780 in SLi -(tested SLi off still crash)
CPU: Intel i7 3930K @3.2Ghz
RAM: 4x4GB DDR4 2400Mhz Corsair Dominator Platinum (speccy says DDR3 1200Mz?)
Storage: 1x Samsung 850 Evo 500GB, 3x Toshiba DT01ACA100 1TB 7200 RPM in RAID 0, 1x External WD Elements 107C 4TB
Audio: ASRock Game Blaster
--------------------------------------- Dump txt below ---------------------------------
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff807`4eab3000 PsLoadedModuleList = 0xfffff807`4eecda50
Debug session time: Wed Jan 2 11:32:00.140 2019 (UTC - 5:00)
System Uptime: 0 days 0:06:37.859
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8074eff4380
Arg4: 0000000000000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8074ed0cc4b to fffff8074ec64b40
STACK_TEXT:
fffff807`5126d358 fffff807`4ed0cc4b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`4eff4380 : nt!KeBugCheckEx
fffff807`5126d360 fffff807`4ebdd4cf : 0000315a`8ff08eb1 fffff807`4dae2180 00000000`00000282 00000000`00006377 : nt!KeAccumulateTicks+0x12c10b
fffff807`5126d3c0 fffff807`4ea1e47c : 00000000`00000000 fffff807`4ea846e0 fffff807`5126d830 fffff807`4ea84790 : nt!KeClockInterruptNotify+0xcf
fffff807`5126d6e0 fffff807`4eb08115 : fffff807`4ea846e0 fffff807`4ea846e0 fffff807`5126d860 fffff807`4ea84790 : hal!HalpTimerClockIpiRoutine+0x1c
fffff807`5126d710 fffff807`4ec6653a : fffff807`5126d830 fffff807`4ea846e0 fffff807`5126db50 fffff807`4ebe104f : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`5126d760 fffff807`4ec66a87 : fffff807`5126d8f0 fffff807`4ec66a87 fffff807`4dae2180 fffff807`545777dc : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`5126d7b0 fffff807`5484d345 : fffff807`00000020 fffff807`5126d960 fffff807`5126db50 fffff807`54577e64 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`5126d940 fffff807`00000020 : fffff807`5126d960 fffff807`5126db50 fffff807`54577e64 fffff807`5126db50 : nvlddmkm+0x4dd345
fffff807`5126d948 fffff807`5126d960 : fffff807`5126db50 fffff807`54577e64 fffff807`5126db50 ffffad89`c1680000 : 0xfffff807`00000020
fffff807`5126d950 fffff807`5126db50 : fffff807`54577e64 fffff807`5126db50 ffffad89`c1680000 ffffad89`c169e050 : 0xfffff807`5126d960
fffff807`5126d958 fffff807`54577e64 : fffff807`5126db50 ffffad89`c1680000 ffffad89`c169e050 fffff807`5454b08a : 0xfffff807`5126db50
fffff807`5126d960 fffff807`5126db50 : ffffad89`c1680000 ffffad89`c169e050 fffff807`5454b08a ffffad89`c16a6000 : nvlddmkm+0x207e64
fffff807`5126d968 ffffad89`c1680000 : ffffad89`c169e050 fffff807`5454b08a ffffad89`c16a6000 00000000`00000000 : 0xfffff807`5126db50
fffff807`5126d970 ffffad89`c169e050 : fffff807`5454b08a ffffad89`c16a6000 00000000`00000000 00000000`00000001 : 0xffffad89`c1680000
fffff807`5126d978 fffff807`5454b08a : ffffad89`c16a6000 00000000`00000000 00000000`00000001 00000000`00000140 : 0xffffad89`c169e050
fffff807`5126d980 ffffad89`c16a6000 : 00000000`00000000 00000000`00000001 00000000`00000140 ffffad89`c1680000 : nvlddmkm+0x1db08a
fffff807`5126d988 00000000`00000000 : 00000000`00000001 00000000`00000140 ffffad89`c1680000 ffffad89`c1680000 : 0xffffad89`c16a6000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+4dd345
fffff807`5484d345 4533c0 xor r8d,r8d
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: nvlddmkm+4dd345
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c0f578b
FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+4dd345
BUCKET_ID: X64_0x133_nvlddmkm+4dd345
Followup: MachineOwner
---------
This issue started quite a while back up to a year or more. It would be random failures to boot with the "ntoskrnl.exe" being listed as corrupt or missing. In the past doing a reboot would get me into the OS, I had no issues once the PC was in windows.
Now, recently while playing DCS in the FA-18 hornet the game began to stutter, the audio crackled, the PC became unresponsive and finally displayed a BSOD with "DPC_WATCHDOG_VIOLATION".
Now my PC will do this randomly. It has happened just browsing this forum for example. Sometimes I get away with some severe stuttering and audio artifacts for any time between 5 and 30 seconds then it comes good, other times it will hang indefinitely, and others it will BSOD.
It will happen watching videos on and offline as well, I have tried watching the videos off of both my RAID drives and my OS SSD.
The crash seems to occur quickly when playing a game called OSU. The audio will loop, and the frames will loop as well.
Interestingly the UI in the game does not freeze, for instance; the combo counter will fall to zero, and not get stuck where it was like the cursor and playing field does. It will then either BSOD, or allow me to escape the game.
I tried runnining OSU off of a RAM disk (I thought maybe a hard drive or SSd issue), same problem.
I've done a lot of troubleshooting on my own and have got nowhere.
This is what I have tried thus far.
- Disabling SLI
- Updated BIOS
- Updated intel rste drivers (hardware raid)
- Clean Re-install of windows 10
- Removed all OC's from my hardware
- Ran Prime 95 for several hours no crash
- Ran 3D Mark TimeSpy for several hours no crash
- Updated Samsung SSD Firmware
- Updated Drivers for SSD
- Clean install of graphics divers
- Took machine to local IT repair shop, stress tested all components - pass (they never experienced a crash or hang - which led me to believe my power delivery at home was the cause)
- (decided to check some things myself), bought a multimeter and tested PSU
- Swapped out my old power extention leads and power-boards
- Updated my Sound Blaster driver
Perhaps its peripheral? Though I believe nothing I have connected to the PC could draw enough power to be an issue. I have connected
- one WD Elements 107C 4TB external (Has its own power) USB 3.0
- Razer Blackwidow keyboard 2x USB 2.0
- Razer Ouroboros mouse USB 2.0
- Logitech Z200 stereo speakers (Plugged into GameBlaster sound card) (rarely used)
- Logitech G35 Headset USB 2.0
- ASUS VG278HE monitor (Dual link DVI into top GPU)
Also worth noting temperatures are not an issue, I have watercooled CPU and GPU's, their temps never reach more than 60c.
I am at my wits end, I have no expertise in this sort of thing and frankly am close to binning this damned thing.
My PC
OS: Windows 10 Home 64-bit
Mobo: ASROCK X79 Extreme 9.
GPU: 2x EVGA GeForce GTX 780 in SLi -(tested SLi off still crash)
CPU: Intel i7 3930K @3.2Ghz
RAM: 4x4GB DDR4 2400Mhz Corsair Dominator Platinum (speccy says DDR3 1200Mz?)
Storage: 1x Samsung 850 Evo 500GB, 3x Toshiba DT01ACA100 1TB 7200 RPM in RAID 0, 1x External WD Elements 107C 4TB
Audio: ASRock Game Blaster
--------------------------------------- Dump txt below ---------------------------------
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff807`4eab3000 PsLoadedModuleList = 0xfffff807`4eecda50
Debug session time: Wed Jan 2 11:32:00.140 2019 (UTC - 5:00)
System Uptime: 0 days 0:06:37.859
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8074eff4380
Arg4: 0000000000000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8074ed0cc4b to fffff8074ec64b40
STACK_TEXT:
fffff807`5126d358 fffff807`4ed0cc4b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`4eff4380 : nt!KeBugCheckEx
fffff807`5126d360 fffff807`4ebdd4cf : 0000315a`8ff08eb1 fffff807`4dae2180 00000000`00000282 00000000`00006377 : nt!KeAccumulateTicks+0x12c10b
fffff807`5126d3c0 fffff807`4ea1e47c : 00000000`00000000 fffff807`4ea846e0 fffff807`5126d830 fffff807`4ea84790 : nt!KeClockInterruptNotify+0xcf
fffff807`5126d6e0 fffff807`4eb08115 : fffff807`4ea846e0 fffff807`4ea846e0 fffff807`5126d860 fffff807`4ea84790 : hal!HalpTimerClockIpiRoutine+0x1c
fffff807`5126d710 fffff807`4ec6653a : fffff807`5126d830 fffff807`4ea846e0 fffff807`5126db50 fffff807`4ebe104f : nt!KiCallInterruptServiceRoutine+0xa5
fffff807`5126d760 fffff807`4ec66a87 : fffff807`5126d8f0 fffff807`4ec66a87 fffff807`4dae2180 fffff807`545777dc : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`5126d7b0 fffff807`5484d345 : fffff807`00000020 fffff807`5126d960 fffff807`5126db50 fffff807`54577e64 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`5126d940 fffff807`00000020 : fffff807`5126d960 fffff807`5126db50 fffff807`54577e64 fffff807`5126db50 : nvlddmkm+0x4dd345
fffff807`5126d948 fffff807`5126d960 : fffff807`5126db50 fffff807`54577e64 fffff807`5126db50 ffffad89`c1680000 : 0xfffff807`00000020
fffff807`5126d950 fffff807`5126db50 : fffff807`54577e64 fffff807`5126db50 ffffad89`c1680000 ffffad89`c169e050 : 0xfffff807`5126d960
fffff807`5126d958 fffff807`54577e64 : fffff807`5126db50 ffffad89`c1680000 ffffad89`c169e050 fffff807`5454b08a : 0xfffff807`5126db50
fffff807`5126d960 fffff807`5126db50 : ffffad89`c1680000 ffffad89`c169e050 fffff807`5454b08a ffffad89`c16a6000 : nvlddmkm+0x207e64
fffff807`5126d968 ffffad89`c1680000 : ffffad89`c169e050 fffff807`5454b08a ffffad89`c16a6000 00000000`00000000 : 0xfffff807`5126db50
fffff807`5126d970 ffffad89`c169e050 : fffff807`5454b08a ffffad89`c16a6000 00000000`00000000 00000000`00000001 : 0xffffad89`c1680000
fffff807`5126d978 fffff807`5454b08a : ffffad89`c16a6000 00000000`00000000 00000000`00000001 00000000`00000140 : 0xffffad89`c169e050
fffff807`5126d980 ffffad89`c16a6000 : 00000000`00000000 00000000`00000001 00000000`00000140 ffffad89`c1680000 : nvlddmkm+0x1db08a
fffff807`5126d988 00000000`00000000 : 00000000`00000001 00000000`00000140 ffffad89`c1680000 ffffad89`c1680000 : 0xffffad89`c16a6000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+4dd345
fffff807`5484d345 4533c0 xor r8d,r8d
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: nvlddmkm+4dd345
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5c0f578b
FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+4dd345
BUCKET_ID: X64_0x133_nvlddmkm+4dd345
Followup: MachineOwner
---------