BSOD - DPC_WATCHDOG_VIOLATION.

[phillpower2]

Device manager info acknowledged (y)

For now, see how the change of USB settings as they are goes.

[Exyztence]

Sadly, the PC crashed today, again when I was idle and the reason was ,system".

[phillpower2]

Two options, both will take you a while to do;

Uninstall and then reinstall all drivers and making sure that the chipset, storage and GPU drivers get installed first and in that order.

Run Driver Verifier;

To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2 (y)

[COLOR=rgb(226, 80, 65)]Please note that the options available differ slightly in Windows 10.

1.[/COLOR][COLOR=rgb(226, 80, 65)] Create a Windows System Restore Point -

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select “Create a Restore Point”
Windows 8/ 8.1 - Using Microsoft System Restore (Windows*8) | HP® Support

2. Run Driver Verifier -

• Windows 7 & Vista - START | type verifier
• Windows 8.1 & 8 - 10 Press WIN +X keys | select “Command Prompt (Admin)” | type verifier
  

Make these selections -
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list
3. Check these boxes -

▪️ Special Pool
▪️ Pool Tracking
▪️ Force IRQL checking
▪️ Deadlock Detection
▪️ Security Checks (new as of Windows 7)
▪️ Concurrency Stress Test (new as of Windows 8)
▪️ DDI compliance checking (new as of Windows 8)
▪️ Miscellaneous Checks

4. Select last option - Select driver names from a list
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where “Microsoft” IS NOT the Provider
7. Click on Finish
8. Re-boot[/HIDE]

• If the Driver Verifier (DV) finds a violation, [color=“#FF0000”]it will result in a [color=“#0000FF”]BSOD
• After re-start, you may not be able to log on to normal Windows

… • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up

… • Select “System Restore”

… • Choose the restore point that you created in step #1

• For Driver Verifier status

— select last option, 1st screen -or-

— type verifier /query (in a cmd/DOS screen)

• To turn Driver Verifier off - verifier /reset then re-boot
• The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
• All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.

[COLOR=rgb(84, 172, 210)]Please note that Driver Verifier may need to be left running for up to 72hrs, you should use the computer as you normally would and DV will not affect this unless a BSOD occurs.[/COLOR][/color]

[Exyztence]

Hi.
The computer was very laggy when entering the password to log in, and as I was on the desktop it immediately jammed and restart. Without bluescreen, just restart. After a few times I had to resume the restore point because I could not get into windows. Due to the fact that it was resetting and didn’t give any BSOD, I don’t have any minidumps. I think my problem is caused by some drivers.
What should I do now? Would PC turn on in safemode while the driver verifier is on, or it would also restart?
Greetings,
Oliwier.

[Exyztence]

^ I forgot to mention, sorry. It all started when I ran the driver verifier.

[Exyztence]

Now, happened two times ,system interrupts" and I had 100% CPU usage. I had to restart then my PC twice.

[phillpower2]

If it was driver/driver verifier related crash dmps would have been generated Oliwier.

You have a Samsung SSD which are generally very good so I would suggest looking at Windows first.

Disable Driver Verifier.

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.

Some other fixes suggested here

[Exyztence]

I have already done this test, haven’t I? It is the one where ESET logs were?
Btw I dont have high CPU usage, right now with browser turned on and teamspeak app, it is 2-7%. It just happened twice that in task manager was something like ,system interrupts" and I had 100% cpu usage by it.

[phillpower2]

We have done so many tests that I can`t remember, was it not Autoruns or possibly MTB that we found ESET, regardless, your choice to run the AIO or not.

[Exyztence]

I’ve run already AIO, even 3 times. It didn’t help me. Do you have any more ideas that can help me? Any solutions? I can even pay you or something, but I really want my PC to work and dont give me BSOD randomly.

[phillpower2]

People getting their computers sorted is all the reward that I need and if cash was so important to me I wouldn’t volunteer here but instead do more hours running my own business.

Not sure what you want to do now, I know what I would do but if you are unhappy about running the AIO tool you will not like my suggestion.

[Exyztence]

I have run AIO, no changes. Today this BSOD, a lot of stack_text.

[phillpower2]

USB audio has come back to haunt us

Can you upload the AIO repair log for us.

What next, it depends on what you want to do really but after looking at the latest dmp you will already be aware that no specific driver was identified but USB audio was involved in some way, the audio part could be a red herring btw and the problem could be with USB ports in general.

I see two options, running DV and starting from scratch, let me know if you have any ideas yourself, stick with me and I will stick with you on this (y)

[phillpower2]

Thread closed due to lack of feedback from the OP.