Windows 10: BSOD With Stop Code DPC_WATCHDOG_VIOLATION

Hello,


I have a customer of mine who recently got a Surface Laptop 3 and has been getting BSOD crashes with the stop code of DPC_WATCHDOG_VIOLATION. I have performed Windows updates, Surface driver/firmware updates, ran SFC scan, ran a chkdsk, but the issue still happens. I have gathered the minidump files on their computer and placed them here:


https://drive.google.com/file/d/1ZdOdDEwZjrZB400ZmiLLJ4QeWLHoQC58/view?usp=sharing


The most recent crash was 08/04/2020 around 5PM


Would anyone be willing to analyze these dump files and tell me where the issue lies? I am not quite good enough to figure that out.


Thanks!

:)

 

Several BSOD screens with different stop codes - Windows 10

I bought a new pc, few days ago. since I got it, my windows 10 crashed about 8 to 10 times already.
Each time I get a different stop code, the ones I got already was:

1. KMODE_EXCEPTION_NOT_HANDLED
   
2. SYSTEM_SERVICE_EXCEPTION
   
3. IRQL_NOT_LESS_OR_EQUAL
   
4. MEMORY_MANAGMENT
   
5. DPC_WATCHDOG_VIOLATION
   

All I could find is this question, but I don't know if his answer is the same as mine, please tell me if it is, I'll add pictures of anything needed.

Thank you for your help, in advance, it is really important.

EDIT: I updated all drivers (motherboard, nvidia gpu), and I got a new stop code after it crashed again: POOL_CORRUPTION_IN_FILE_AREA

 

BSOD dpc_watchdog_violation

Continued BSOD with stop code dpc_watchdog_violation, how do I stop this?

I used to bluescreenview to look at the crashdump file and it's flagged "ntoskrnl.exe" as the issue. I've seen multiple posts about updating drivers, but no drivers that I've touched have fixed the issue. I tried using driver verifier to help identify the
problem driver and it put my system into a bootloop that resulted in have to reinstall windows onto my machine.

 

Windows 10 DPC_WATCHDOG_VIOLATION on restart

Hello Tom,

There may be several reasons why you are getting this DPC_WATCHDOG_VIOLATION. To assist you better with this concern, kindly answer the following questions:

• When did this issue started happening?
• Does this error come with an error code/number?
• What troubleshooting steps have you done aside from the ones mentioned above?

In the meantime, you can check on this
thread and refer to the post of ZigZag3143 (MS -MVP). It discusses steps on what you can do with these kinds of stop errors.

We're looking forward for our reply.