Random BSOD - DPC_WATCHDOG_VIOLATION

axe0 said:

A standalone program you mean? (no installation required for running)
I suggest that you use a different program for the same or update the .exe, this driver we are talking about is 8 years old, I have a driver test in mind (driver verifier) which most likely will flag this driver.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

This is the program: Download Real Temp 3.70 | techPowerUp
There is no installer/uninstaller, it is just a folder of files and you run the exe. That ring zero driver is part of that set. So really, all I need to do is not run it...
Do you have another similar program you recommend for monitoring CPU/GPU temps?

I will try the verifier shortly.

OK I got another crash and minidump with the driver verifier running on all non-MS drivers. See attachment.Attachment 68749

Carsomyr said:

Do you have fats 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...

axe0 said:

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

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) 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.

Warpedcow said:

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...)

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...