Just checking things out, not really my forte but interesting. Seems not much information regarding this in the .h file, the best documentation was from another member of this forum from year or so ago. Microsoft doesn't have a whole lot of support articles relating to Surface Pro lines either.
Checked Bios shows the latest from 2/17 update, msinfo32 didn't show any problem devices so I would think they all applied okay.
Looking deeper it seems logs indicate the issue first started around 1/16. How long have you had this system and was this the first time?
I would check installed programs "appwiz.cpl" and see if anything sticks out on that day.
Also ESET, Its fun to point figure at Antivirus and filter drivers. Maybe uninstall the AV agent for testing and see if the issue will reproduce with this uninstalled. I do mean uninstalled, when you disable the AV the filter driver will still be there. You can check this with "fltmc".
Another thing I notice was seems to be running Hyper-V?
Hyper-V Virtual Machine Management vmms Running Auto Own Process c:\windows\system32\vmms.exe Normal LocalSystem 0
We always recommend Hyper-V Host disable C-sates/C1e. Would seem these surface pro all seem to have tons of "sleep" states I can't image that a good thing.
Hyper-V and BIOS power plans (c-states) - PFE Virtualization Blog - Site Home - TechNet Blogs
One other thing you may look into is collecting a SDP report (support diagnostic package), choose memory dump collector. Sometimes there is good callouts there that would take much longer to find.
Code:
0: kd> !analyze -show bugcheck
PDC_WATCHDOG_TIMEOUT (14f)
A system component failed to respond within the allocated time period,
preventing the system from exiting connected standby.
Arguments:
Arg1: 0000000000000004, Client ID of the hung component.
Arg2: 0000000000000002, A resiliency client failed to respond.
Arg3: fffff800de9c7a58, Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT).
Arg4: ffffd0014edf9b60, Pointer to a pdc!PDC_14F_TRIAGE structure.
0: kd> dt pdc!_PDC_RESILIENCY_CLIENT
+0x000 Context : _PDC_COMMON_CONTEXT
+0x020 ResiliencyType : PDC_RESILIENCY_TYPE
+0x028 ClientReferences : Uint8B
+0x030 PoResiliencyClient : UChar
+0x034 CurrentTransactionId : Uint4B
+0x038 OneTimeTransaction : UChar
+0x03c CurrentState : PDC_CLIENT_STATE
+0x040 NextState : PDC_CLIENT_STATE
+0x044 ClientId : Uint4B
0: kd> dt pdc!_PDC_RESILIENCY_CLIENT fffff800de9c7a58
+0x000 Context : _PDC_COMMON_CONTEXT
+0x020 ResiliencyType : 3 ( PdcDamResiliency )
+0x028 ClientReferences : 0
+0x030 PoResiliencyClient : 0 ''
+0x034 CurrentTransactionId : 0xb4b
+0x038 OneTimeTransaction : 0 ''
+0x03c CurrentState : 0 ( ResiliencyClientPassive )
+0x040 NextState : 1 ( ResiliencyClientActive )
+0x044 ClientId : 4
0: kd> dt pdc!_PDC_14F_TRIAGE
+0x000 ClientProcess : Ptr64 _EPROCESS
+0x008 CallbackThread : Ptr64 _ETHREAD
0: kd> dt pdc!_PDC_14F_TRIAGE ffffd0014edf9b60
+0x000 ClientProcess : (null)
+0x008 CallbackThread : 0xffffe000`fad86340 _ETHREAD
###################################################
With a lot of these at least ones documented to be resolved were network related.
Didn't look like Verifier had any of those flags on.
0: kd> !verifier
Verify Flags Level 0x0002892b
STANDARD FLAGS:
[X] (0x00000000) Automatic Checks
[X] (0x00000001) Special pool
[X] (0x00000002) Force IRQL checking
[X] (0x00000008) Pool tracking
[ ] (0x00000010) I/O verification
[X] (0x00000020) Deadlock detection
[ ] (0x00000080) DMA checking
[X] (0x00000100) Security checks
[X] (0x00000800) Miscellaneous checks
[X] (0x00020000) DDI compliance checking
ADDITIONAL FLAGS:
[ ] (0x00000004) Randomized low resources simulation
[ ] (0x00000200) Force pending I/O requests
[ ] (0x00000400) IRP logging
[ ] (0x00002000) Invariant MDL checking for stack
[ ] (0x00004000) Invariant MDL checking for driver
[X] (0x00008000) Power framework delay fuzzing
[ ] (0x00010000) Port/miniport interface checking
[ ] (0x00040000) Systematic low resources simulation
[ ] (0x00080000) DDI compliance checking (additional)
[ ] (0x00200000) NDIS/WIFI verification
[ ] (0x00800000) Kernel synchronization delay fuzzing
[ ] (0x01000000) VM switch verification
[ ] (0x02000000) Code integrity checks
[X] Indicates flag is enabled