Yes, thanks for providing your dump file settings. Everything seems to be the default.
Code:
BugCheck 17C, {ffffd40e79144040, 2710, 0, 0}
Probably caused by : pdc.sys ( pdc!PdcpLockWatchdogWorkerRoutine+3d )
The crash seems to have occurred when exiting standby mode. The first parameter of the bugcheck is the thread which contains the callstack before the crash. There isn't much useful information here. This bugcheck is very difficult since it is poorly documented, with every little information provided by Microsoft, so there's going to be some educated guesses involved here unfortunately.
Code:
0: kd> knL
# Child-SP RetAddr Call Site
00 ffffbb8d`10ee66b0 fffff800`8822f96d nt!IopLiveDumpEndMirroringCallback+0x7e
01 ffffbb8d`10ee6700 fffff800`8822a7c7 nt!MmDuplicateMemory+0xcc1
02 ffffbb8d`10ee67e0 fffff800`884b949d nt!IopLiveDumpCaptureMemoryPages+0x7f
03 ffffbb8d`10ee68a0 fffff800`884ad57d nt!IoCaptureLiveDump+0x289
04 ffffbb8d`10ee6a40 fffff800`884adc88 nt!DbgkpWerCaptureLiveFullDump+0x12d
05 ffffbb8d`10ee6aa0 fffff800`884ad3db nt!DbgkpWerProcessPolicyResult+0x30
06 ffffbb8d`10ee6ad0 fffff80b`86a9533d nt!DbgkWerCaptureLiveKernelDump+0x19b
07 ffffbb8d`10ee6b20 fffff800`87e3f4d5 pdc!PdcpLockWatchdogWorkerRoutine+0x3d << System detects that Power IRPs are taking too long to process
08 ffffbb8d`10ee6b80 fffff800`87f1ab87 nt!ExpWorkerThread+0xf5
09 ffffbb8d`10ee6c10 fffff800`87f80be6 nt!PspSystemThreadStartup+0x47
0a ffffbb8d`10ee6c60 00000000`00000000 nt!KiStartSystemThread+0x16
Let's dump the current power state of the system using the !poaction debugger extension:
Code:
0: kd> !poaction
PopAction: fffff80088166820
State..........: 0 - Idle
Updates........: 0
Action.........: None
Lightest State.: Unspecified
Flags..........: 10000003 QueryApps|UIAllowed
Irp minor......: ??
System State...: Unspecified
Hiber Context..: 0000000000000000
Allocated power irps (PopIrpList - fffff80088166ee0)
IRP: ffffd40e760c88a0 (wait-wake/S4), PDO: ffffd40e73f1c060
IRP: ffffd40e7525c940 (wait-wake/S4), PDO: ffffd40e75223620
IRP: ffffd40e75245940 (wait-wake/S4), PDO: ffffd40e75251060
IRP: ffffd40e752dfc10 (wait-wake/S4), PDO: ffffd40e75e14060
IRP: ffffd40e76f3ec10 (wait-wake/S4), PDO: ffffd40e75157050
IRP: ffffd40e753a1ab0 (wait-wake/S4), PDO: ffffd40e76eeda90
IRP: ffffd40e753e9010 (wait-wake/S4), PDO: ffffd40e7539a060
IRP: ffffd40e753908b0 (wait-wake/S4), PDO: ffffd40e75398060
IRP: ffffd40e753e48b0 (wait-wake/S4), PDO: ffffd40e7538f060
IRP: ffffd40e752bb010 (wait-wake/S4), PDO: ffffd40e7538e060
IRP: ffffd40e76f2ac10 (wait-wake/S4), PDO: ffffd40e76e84060
IRP: ffffd40e7558b740 (wait-wake/S4), PDO: ffffd40e75153050
IRP: ffffd40e752e1c10 (wait-wake/S4), PDO: ffffd40e76ea63c0
IRP: ffffd40e7b509700 (wait-wake/S4), PDO: ffffd40e76e98060
Irp worker threads (PopIrpThreadList - fffff80088165a10)
THREAD: ffffd40e710c1040 (static)
THREAD: ffffd40e710d7040 (static)
Broadcast in progress: FALSE
No Device State present
The current power state is
0 - Idle which is a standby mode implemented in operating systems Windows 8 and above. It allows the system to instantly 'wake' from sleep. Notice how Windows 8 machines used to boot very quickly from sleep? This is the Modern Standby mode implemented by Microsoft. It's the same power state which your smartphone would use when you press the power button.
Another important aspect is the currently queued power IRPs. Notice how they're all for the same power state transistion?
Let's grab the first IRP from the list, and see what is happening in it's stack:
Code:
0: kd> !irp ffffd40e760c88a0
Irp is active with 4 stacks 2 is current (= 0xffffd40e760c89b8)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e1 ffffd40e73f2ce40 00000000 fffff80b8707f3e0-ffffd40e74a431a0 Success Error Cancel pending
\Driver\ACPI ndis!ndisWaitWakeIoCompletion
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e0 ffffd40e74a43050 00000000 fffff80087f21890-ffffd40e73f50f00 Success Error Cancel
*** ERROR: Module load completed but symbols could not be loaded for e1d65x64.sys
\Driver\e1dexpress nt!PopRequestCompletion
Args: 00000005 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffd40e73f50f00
Args: 00000000 00000000 00000000 00000000
Notice how the IRP is currently pending? This IRP tells us that the system has told the device to transition from its standy mode to power state, however, it appears to become stuck therefore leading to the crash which has occured.
The minor code IRP_MN_WAIT_WAKE simply sends a wake signal to the device, which in turn will produce another power IRP which will tell the driver to transistion to a fully powered state. The wake signal may originate on desktop screens may be a nofication or the movement of the mouse cursor.
The next driver is the IRP stack appears to be related to your Intel network driver:
Code:
0: kd> lmvm e1d65x64
start end module name
fffff80b`89950000 fffff80b`899da000 e1d65x64 (no symbols)
Loaded symbol image file: e1d65x64.sys
Image path: \SystemRoot\system32\DRIVERS\e1d65x64.sys
Image name: e1d65x64.sys
Timestamp: Wed Jul 12 14:29:18 2017 (5966242E)
CheckSum: 0008DB2A
ImageSize: 0008A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
This isn't to say that the driver is at fault, but it provides some indication of where the system is crashing and which device drivers may be responsible.
Just picked another power IRP from the list, and it appears that the Xbox driver which cwsink mentioned is present.
Code:
0: kd> !irp ffffd40e753a1ab0
Irp is active with 16 stacks 12 is current (= 0xffffd40e753a1e98)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 1 ffffd40e76eeda90 00000000 00000000-00000000 pending
\Driver\USBHUB3
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e0 ffffd40e76e5b430 00000000 fffff80b8707f3e0-ffffd40e752d41a0 Success Error Cancel
\Driver\ACPI ndis!ndisWaitWakeIoCompletion
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e0 ffffd40e752d4050 00000000 fffff80b88c72aa0-ffffbb8d0cab5208 Success Error Cancel
*** ERROR: Module load completed but symbols could not be loaded for mt7612US.sys
\Driver\mt7612US xboxgip!gipFilterGenericCompletionRoutine
Args: 00000005 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 e0 ffffd40e76f8d6e0 00000000 fffff80087f21890-ffffd40e753a9bd0 Success Error Cancel
\Driver\xboxgip nt!PopRequestCompletion
Args: 00000005 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffd40e753a9bd0
Args: 00000000 00000000 00000000 00000000
I would just updating the Xbox driver and ensuring that anything network related is updated too such as security programs.
Code:
0: kd> lmvm mt7612US
Browse full module list
start end module name
fffff80b`88c00000 fffff80b`88c61000 mt7612US (no symbols)
Loaded symbol image file: mt7612US.sys
Image path: \SystemRoot\System32\drivers\mt7612US.sys
Image name: mt7612US.sys
Browse all global symbols functions data
Timestamp: Wed Dec 09 06:44:11 2015 (5667CDBB)
CheckSum: 00062A42
ImageSize: 00061000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
The device stack for the IRP:
Code:
0: kd> !devstack ffffd40e76eeda90
!DevObj !DrvObj !DevExt ObjectName
ffffd40e76f8d6e0 \Driver\xboxgip ffffd40e76f8d830
ffffd40e752d4050 \Driver\mt7612US ffffd40e752d41a0 NDMP3
ffffd40e76e5b430 \Driver\ACPI ffffd40e7220ebe0
> ffffd40e76eeda90 \Driver\USBHUB3 ffffd40e76eea600 USBPDO-9
!DevNode ffffd40e75228100 :
DeviceInst is "USB\VID_045E&PID_02E6\470636"
ServiceName is "mt7612US"