Hi kujten & Welcome to the forums ^_^,
Sorry for the delay in response. I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
So, the system crashed because Windows detected that a DPC (Deferred Procedure Call) or the ISR (Interrupt Service Routine) crossed it's limit of the maximum time it could respond. Let's check the stack -
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Seems like the dump did not save any information from the dump files
5: kd> k
Child-SP RetAddr Call Site
ffffd000`209b1e38 00000000`00000000 nt!KeBugCheckEx
Kindly turn on Driver Verifier according to this **GUIDE** and let it crash the system for few times. Once the system has crashed a few times, kindly re-run the Diagnostic Utility and upload the freshly generated ZIP diagnostic so that it could be analysed.
Let me know how it goes ^_^