I had a dell studio 16. After a month it started giving this "DPC Watchdog Violation" BSOD at random, up to 5 or 6 times a day. There was another issue so Dell replaced it.
Again this system is giving me this error after a few weeks, currently 3 times a day-ish.
I've tried numerous fixes but having no luck. Any ideas how to nail this down as I can't afford to have it randomly crashing ?
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
Open Windows File Explore
Navigate to C:\Windows\Minidump
Copy the mini-dump files out onto your Desktop
Do not use Winzip, use the built in facility in Windows
Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
Then post a link here to the zip file, so we can take a look for you . . .
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/2ztd496k/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
Your issue is modern sleep (S0) most likey. There are horror stories of dell not working with S0 well. The old sleep S3 shut off and had little power use, but off. S0 puts the pc in a "Low power" State that when input is detected it springs back like your phone. Think of it as a kinda idle state, very low power use but still connected and listening for input. Ive got 2 pcs at work now, Same issue. Its a MS issue with the S0 state and dell. See the link below.