New
#11
Providing the memory.dmp file was useful - it allows you to display the deferred procedure call (DPC) queues for the processor.
The 0x133 stop code had first parameter = 1 which tells you that there are DPCs running from more than one driver and the one that shows up in the stack is not always the one responsible for the crash.Code:0: kd> !dpcs CPU Type KDPC Function 0: Normal : 0xffffa8031cc550e0 0xfffff8054574fd1c nvlddmkm 0: Normal : 0xfffff80538f83568 0xfffff8053aa999e0 nt!KiEntropyDpcRoutine 0: Normal : 0xfffff8053ae1eb60 0xfffff8053ab3ec50 nt!PpmCheckPeriodicStart 0: Normal : 0xfffff8053ae301e0 0xfffff8053aa95d40 nt!KiBalanceSetManagerDeferredRoutine 0: Normal : 0xffffa8031c99d788 0xfffff805424a66b0 ndis!ndisInterruptDpc
If you continue to get BSOD events I would start looking at your network drivers since the other DPC was related to ndis.sys which is triggered by the network.