0
1
I am getting the dreaded DPC_WATCHDOG_VIOLATION on a newly setup Windows 8.1 rig. It uses a Gigabyte H87-HD3 Motherboard, i5 4570, 16GB RAM and has a Kingston 240GB SSD (no other h/w on the M/b). Logitech Wireless Keyboard K520 + mouse using unified USB receiver. The SSD is setup as SATA, AHCI is ON. UEFI is set to 'UEFI and Legacy'. I did not use the Intel drivers while setting up the SSD, I let Windows partition/format the Drive.
The System is stable otherwise but on almost all 'Restart' it freezes just after the Startup Screen comes up. Most of the times it crashes before password entry, occasionally it gets to password entry but freezes and crashes with DPC_WATCHDOG_VIOLATION soon after. If I power off and start, no issues.
Often I have seen that the network connection showing a yellow exclamation before crashing. I have tried updating the network drivers but no avail. (I am using on-board LAN no WIFI adapter in the system).
I have uploaded the Minidump files here. Any help with the crash analysis is greatly appreciated.
HI, Thanks for your inputs. That seems to be latest Driver version from Realtek around. I reverted to MS drivers but that didn't solve anything. Infact it made it worse (required 5+ attempts to bootup, unfortunately WinDbg is refusing to even load the MiniDump files generated). If the Audio device is busted, I guess I can RMA the M/b. One question though, if I disable the Audio device from BIOS and things start working, that should pretty much be all the proof required that Audio device is busted right? – sumitkm – 2014-03-24T10:13:16.657
Looks like disabling Audio from BIOS didn't help. Neither did disabling onboard LAN. I have got a bunch of new MiniDump files http://1drv.ms/1jm1S2r , that seem to all point at different drivers as per BlueScreenViewer.exe. Any new insights will help (feeling sheepish that I can't find the correct Symbol files to do this myself ;-)... )
– sumitkm – 2014-03-24T11:21:34.017OKay, I finally figured out how to use WinDbg to get the Bug Check Analysis and for all the MiniDmp files I can load I get the above analysis. But as the analysis shows above, WinDbg is pointing to HDAudBus. Curious to know how did you relate it to RTKVHD.sys (I am a WinDbg noob so please be kind :-)... ) – sumitkm – 2014-03-24T11:53:56.267
Finally some light at the end of the tunnel. Looks like turning Hyper V off solves the WATCHDOG_VIOLATION issue. It is very very similar to this issue http://www.eightforums.com/bsod-crashes-debugging/32377-dpc_watchdog_violation-windows-8-1-upon-logging.html (which I guess is answered by magicandre there also ;)... ). This gives a little relief that the H/W maynot be faulty, but it's absolutely no-no for me because a major point of the new machine was to use Hyper-V (WP8 development basically)
– sumitkm – 2014-03-24T13:08:15.300this is not me. Contact the Microsoft support about the issue. – magicandre1981 – 2014-03-24T18:24:18.217