BSOD - DPC_WATCHDOG_VIOLATION.

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Status
Not open for further replies.
Apologies for the delay, couldnt find my cnned txt for disabling Hibernation.

Those two errors look more like graphics and Windows issues to me.

Press Windows+ R > Run box > type services.msc > OK.

In the Services window > go to the Windows Driver Foundation – User-mode Driver Framework service, double click on it to open the Properties
From the Windows startup type menu choose Automatic.
Check that the service is running in the dialog box below, click on Apply and then OK to save the settings

Restart the computer then do the following;

To disable Hibernation:

  1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)"
  2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input
  3. Now just exit out of command prompt
Restart and see how things go.
 
I don't have Windows Driver Foundation in services.msc
And I disabled Hibernation and restarted PC.
 

Attachments

  • Screenshot_2.png
    Screenshot_2.png
    66.9 KB Views: 8
That`s not good, if the following does not fix it I recommend you download the latest Windows 10 ISO and clean install Windows.

Download then run the Windows All in One Repair tool from here, disregard the malware guidance but follow the other steps to the letter and in particular ensuring that you first create a new restore point and perform a proper Windows clean boot before running the repair, details for the clean boot here.
 
I ran this app, it took some time but didnt help me. Still no Windows Driver Foundation in services.msc. Should it be there? I read that in few versions of windows, its not installed or something like that. If it should be there, what more can I do? I am after clean install, I didnt do anything more except installing drivers and games. No trustless apps.
My windows:
Version 10.0.18363 Build 18363
 
Exyztence said:
My windows:
Version 10.0.18363 Build 18363
Click to expand...
My apologies you are correct, it has been replaced with something else in later versions which makes the error even more puzzling, can you for now just see how things go after running the AIO repair tool, Ive got a big job on here so may not be around for a couple of hrs but will check back later.

There should have been an AIO repair log generated, can you look for it and if found go through it to see what has been repaired.
 
I don't really know how to check logs, but I found the folder.
I will attach it and if u could have a look at it in free time, because I don't know to what pay attention.
I think it made a lot of changes.
Thanks in advance. :)
 

Attachments

Hi, it crashed again when I was using sony vegas pro and editing my video. In WINDBG there is a lot of STACK_TEXT and there are few ,,USBXHCI". Maybe it will give us some results? Minidump is below.
Greetings:)
 

Attachments

Were you using a USB video camera at the time of either of the last two crashes.

Have you reinstalled ESET

05 - Repair WMI
Start (5/22/2020 7:07:12 PM)

Starting Security Center So We Can Export The Security Info.

Exporting Antivirus Info...
Windows Defender Exported.
ESET Security Exported.

Exporting AntiSpyware Info...
No AntiSpyware Products Reported.

Exporting 3rd Party Firewall Info...
No Firewall Products Reported.

Running Repair Under Current User Account
Done (5/22/2020 7:09:10 PM)

06 - Repair Windows Firewall
Start (5/22/2020 7:09:10 PM)

Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\services.7z
Done, 0.19 seconds.

Running Repair Under Current User Account
Running Repair Under System Account
Done (5/22/2020 7:09:23 PM)
 
Hi.
1. Yes, I have a plugged-in to my PC, USB camera - Logitech C920. It was used in-app called ,,facerig.exe" for about 30 minutes. Then I turned the app off and about 2 hours later the crash happened. (It was at the time when the second crash occurred.)
2. No, I haven't reinstalled ESET or any other Anti-Virus. I'm not downloading or installing any apps since we try to find out what is wrong.
Greetings,
Oliwier.
 
The first crash was nt related which is so generic a crash that they are real hard to pin down.

Second crash involved Windows video capture drivers that crashed and the dmp suggests that as you mention drivers for a USB device were involved, the USB camera drivers being the most likely.

Can you run the AIO tool again and upload the new log for us, this to see if ESET is still showing up, if it is it may explain the crashes.
 
ESET is still there I`m afraid and among other things it looks to be affecting Defender and the Firewall :confused:

05 - Repair WMI
Start (5/24/2020 11:18:52 AM)

Starting Security Center So We Can Export The Security Info.

Exporting Antivirus Info...
Windows Defender Exported.
ESET Security Exported.

Exporting AntiSpyware Info...
No AntiSpyware Products Reported.

Exporting 3rd Party Firewall Info...
No Firewall Products Reported.

Running Repair Under Current User Account
Done (5/24/2020 11:20:34 AM)

06 - Repair Windows Firewall
Start (5/24/2020 11:20:34 AM)

Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\services.7z
Done, 0.16 seconds.

Running Repair Under Current User Account
Running Repair Under System Account
Done (5/24/2020 11:20:46 AM)
 
Hi.
I checked some registry directories where should be any files of ESET and I didn't find anything. I also scanned for folders etc. No results for ,,ESET". Maybe it is some bug or something? I also ran the uninstaller the second time and uninstalled ,,leftovers". Then ran AIO, it says ESET is still there, but I don't know. What should I do now?
 
Pain in the proverbial to do I know but what I would do;

Download the latest ISO from here

Save the chipset, storage and GPU drivers to a thumbdrive.

Make a list of your most often used software and in the order in which you use them the most.

Clean install Windows.

Install the drivers for the MB starting with the chipset drivers first, then storage drivers, GPU drivers etc.

Get Windows and Windows Defender both fully up to date.

Create a new system restore point.

Install your first most used program and test for a while, if no problems, create a new system restore point, install the next most used program and test, repeat until you have everything installed and fully tested.

It is important not to cut any corners so as to be able to pin any specific program down should you start having problems after installing it.

Until you have resolved this issue I would not be installing any third party AV or new third party software.
 
Hi,
thank you for your message. So there is nothing else for me to do than clean install for the 5th time?
In general I also have a question. What it depends on, that on new hardware I have a lot of problems, and on the old nothing happened. Even as I had all the antivirus, virtual audio cable etc. installed. Does it depend on MB/CPU or something else?
Maybe I will run windows driver verifier?
 
EDIT:
Also, today occurred BSOD, I checked it and the reason was ,,USBXHCI". As I read on the internet, it can me MB related.
 

Attachments

The below only regarding the latest crash dmp;

Did you have anything connected to the USB ports at the time of the crash.

Have you checked the Device Manager for any yellow ! or red X and by the USB hubs in particular.

What caused the crash xHCI drivers, lot of info if you want to read it here

The Watchdog violation makes me think that those traces of ESET are behind your troubles and sorry to say I have no idea how to track them down, we tried Autoruns but there are still traces hiding somewhere.
 
Yes, I have connected to usb:
- mouse
- keyboard
- headset (also usb)
- mousepad (rgb)
- microphone (also usb, no xlr)

EDIT: it also happened that I spilled a drink on the keyboard, it did not work a few days and then began. maybe it causes something? (it happened twice, some time ago, the second one about 3 months ago)
 
The drink issue is unlikely to be related.

phillpower2 said:
Have you checked the Device Manager for any yellow ! or red X and by the USB hubs in particular.
Click to expand...
Can you answer this for us.

Suggestion, make sure that USB selective suspend is disabled, how to here
 
Status
Not open for further replies.
Top Bottom