New
#21
These latest dumps show that the same DPC bugcheck is occurring (0x133 with first parameter =1). Using the kernel memory dump we can look at the DPCs on the processor as follows:
The audio driver shows up again but also a network driver, these ones are MS and are usually not the problem.Code:0: kd> !dpcs 0 CPU Type KDPC Function 0: Normal : 0xffffed0245a4f000 0xfffff80335139220 nt!PopExecuteProcessorCallback 0: Normal : 0xffffed0245ca7000 0xfffff80335139220 nt!PopExecuteProcessorCallback 0: Normal : 0xffff9b8b1b9ddc38 0xfffff80df9b82ea0 HDAudBus!HdaController::CodecDpc 0: Normal : 0xffff9b8b1a3cdc40 0xfffff80df4c179a0 ndis!ndisPeriodicReceivesTimer 0: Normal : 0xfffff803342bdf90 0xfffff803350f5210 nt!PpmPerfAction 0: Normal : 0xffff9b8b1a5e30c8 0xfffff80df4e32450 tcpip!TcpPeriodicTimeoutHandler 0: Threaded: 0xfffff803342be0d8 0xfffff8033519a160 nt!KiDpcWatchdog
The 3rd party network driver is rt640x64.sys - it is already the newest on your MB website so all I can suggest is trying an older one.
I have tried extracting a trace of the DPC durations using the Kernel logger data in the dump but unfortunately it reports that time inversion has occurred and the Windows Performance Analyser will not load it. This is not something I've experienced before but @cwsink may have some ideas on how to proceed.