Solved DPC_WATCHDOG_VIOLATION resuming from sleep. Windows 8 64

Hi all,

I'm getting a DPC_WATCHDOG_VIOLATION resuming from sleep but I think I got one trying to shutdown once but maybe it was shutting down to sleep.

Thanks for any help.

Welcome
Tentatively it appears that your problem is due to a driver. The information given indicates a driver that is not the most likely cause. See if driver verfier can detect the true problem. Run for 36 hours
Verifying Drivers: Enable or disable the Driver verifier in Windows 8

Enabled. Will run for 36 hours.

So do I now continue to use the computer normally (i.e. sleeping/rewaking the computer) and wait for a crash? Then re-upload the new SF zip file?

Use the computer as always. If you have an idea of what action caused the BSODs make sure you do that too. Use it for 36 hours. We want BSODs, since the verifier puts stress on the drivers and the weak ones will cause BSODs. So for the next 36 hours BSODs are a good thing.

New crash today. First one in awhile. This time during boot. Verifier is still enabled. Different error, something about THREAD

The verifier has named a driver. Lets hope this is the answer. Go to the website and update driver. Do not follow any other instructions in this For Information Only article
wrfiltv.sys - What is wrfiltv.sys ?

That would be the Creative soundblaster world of warcraft wireless headset driver. Windows 8 installed the driver for it automatically and there is no new driver for it since 2010 for Win7 so I just uninstalled the driver and removed the usb transmitter. Nothing but problems with that headset anyway.

Thanks for all your help!

You are welcome.

If the BSODs continue turn on verifier again.

I clicked on the verifier.exe link you provided above and read the instructions for use. The two that commented had tried it and had their computers stuck in a loop as a result. How can verifier.exe be used without causing an additional problem? I am getting a Windows 8 BSOD every time when coming out of Sleep Mode and getting a DPC.Watchdog_Violation error. Nothing I have done or a third level MS Support person has done has found the supposed driver that is causing the problem. I will post the problem in a new thread in your BSOD Crashes and Debugging section.

Thanks.

Driver Verifier stresses drivers. If the driver that fails because of Driver Verifier is one that's loaded early in the boot process - it's gonna fail early in the boot process. That's the price of using Driver Verifier.

That being said, there are several different things that you can do to "get around" this.
First is attempting to get into Safe Mode and disable Driver Verifier from there.
Second is to use a System Restore point to set the system back to a point before you started using Driver Verifier.

The second method requires a bit of preparation:
- set a System Restore point BEFORE enabling Driver Verifier
- create a System Repair Disc so you can boot to System Restore
- test the System Repair Disc to be sure that it works and that you can access System Restore when using it

Further suggestions at my Driver Verifier webpage: Driver Verifier Settings