Windows 10: Random BSOD - DPC_WATCHDOG_VIOLATION

This driver needs updating/reinstallation
Driver Reference Table - rt640x64.sys

Code: ffffd000`c0f124e8 fffff800`7eaaa305Unable to load image rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x6a305 0: kd> lmvm rt640x64 Browse full module list start end module name fffff800`7ea40000 fffff800`7eb25000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: rt640x64.sys Image name: rt640x64.sys Browse all global symbols functions data Timestamp: Thu Oct 01 12:34:33 2015 (560D0C39) CheckSum: 000F03D5 ImageSize: 000E5000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Do you have fast boot enabled? If you are unsure, do you have the sleep/hibernate options in your shutdown menu?

 

Yes, I have sleep and hibernate options though I do not use them...

 

[/quote] Thanks, by following your links I've got a new driver dated 2/19/2016 from Realtek, will see how that works.
The "old" driver is replaces was dated 10/1/2015.

If the "new" driver still crashes is there a generic NIC driver from Microsoft I can use instead? (This is the onboard NIC on the ASRock motherboard...)

 

Disable fast boot. I had the same problem with DPC_WATCHDOG_VIOLATION since the insider preview, which pointed to a driver that upgrading/downgrading/whatever didn't help. Ever since I disabled fast boot I have not seen it again (not to mention those options are geared towards laptops anyways) *Biggrin Go in control panel and click on power options, click on "change what the power buttons do", then click "change settings that are currently unavailable". Uncheck the "turnon fast startup" box, save your changes, and close. *Biggrin

 

Update - the download on the site is dated 2/19/2016 but the driver itself in that download is dated 1/7/2016.
Will try a stress test on the NIC to see if I can trigger another BSOD...

 

Well. Go figure within a day I got it again -_- It's not very often but just enough to be irritating, but mine point to nvidia drivers every time. And I have brought it to their attention many times. Off to start my own thread...

 

I got a lockup but no BSOD/dump over the weekend. Will try another stress test and see what happens. I've also swapped the ethernet to the other port on the motherboard on a whim.
Anyone have a good network stress tester to suggest?

 

OK, got another BSOD again but with the newest driver. Minidump attached.

 

This time the AMD drivers and Realtek network drivers have been flagged, but a BIOS update may improve stability
ASRock > P67 Extreme6
I would also make sure the AMD drivers are up to date.
Driver Reference Table - rt640x64.sys
Code: ffffd000`5d7bd438 fffff801`308ea2b5Unable to load image rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x6a2b5 2: kd> lmvm rt640x64 Browse full module list start end module name fffff801`30880000 fffff801`30966000 rt640x64 T (no symbols) Loaded symbol image file: rt640x64.sys Image path: rt640x64.sys Image name: rt640x64.sys Browse all global symbols functions data Timestamp: Thu Jan 07 08:48:31 2016 (568E184F) CheckSum: 000EF815 ImageSize: 000E6000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 ffffd000`5d7bcc08 fffff801`3109a0f3Unable to load image atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0x5a0f3 2: kd> lmvm atikmdag Browse full module list start end module name fffff801`31040000 fffff801`32787000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: atikmdag.sys Image name: atikmdag.sys Browse all global symbols functions data Timestamp: Fri Dec 04 18:14:28 2015 (5661C9F4) CheckSum: 016E6BC5 ImageSize: 01747000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

[/quote] I just ran the BIOS update successfully. Updating AMD drivers next.
Realtek of course is already at the latest revision.
Will run another stress test once AMD updated.

EDIT: AMD drivers are already at the latest version!

 

Stress test passed okay. Going to try it at least once more before crossing my fingers and tagging this solved.
Would be happy of course if the BIOS update fixed it, however I'm skeptical as the readme for the update only discussed new features, not any bug fixes... plus, the old BIOS worked just fine for this exact set of hardware for years running Windows 7 and 8 and even a few months running 10 before the BSODs started...

 

BIOS update seemed to do the trick. Marking as Solved with fingers crossed.

 

Sorry folks, not solved. Got another hard lock (no dump) just now while I was using it (during lots of network traffic - video was asleep).

Trying newer AMD and Realtek drivers now...

 

And just got another BSOD - different this time but it least it wrote a dump (attached)

Attachment 73487