Surface Pro 4 BSOD - Windows 10 x64
- Thread starter moosic
- Start date
Hi. . .
pdc.sys is a Microsoft Power Dependency Coordinator driver - Driver Reference Table - pdc.sys
It is listed as the probable cause of 4 of your 8 BSODs, but it is not the actual cause -- it is merely a default.
The other 4 dumps listed the Microsoft DAM (Desktop Activity Moderator) Kernel driver dam.sys - Driver Reference Table - dam.sys
Again, it is not the cause - just a default.
The bugchecks on all dumps - 0x14f - A system component failed to respond within the allocated time period, preventing the system from exiting connected standby. The dumps don't tell us what the system component is.
Run Driver Verifier - see if any 3rd party drivers are flagged - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html
Let it run for 24 hours minimum.
I don't know at this time if we're dealing with a software or hardware issue.
EDIT: Are all Windows Updates installed? I'm getting symbol errors on the Windows kernel in the dumps.
Regards. . .
jcgriff2
pdc.sys is a Microsoft Power Dependency Coordinator driver - Driver Reference Table - pdc.sys
It is listed as the probable cause of 4 of your 8 BSODs, but it is not the actual cause -- it is merely a default.
The other 4 dumps listed the Microsoft DAM (Desktop Activity Moderator) Kernel driver dam.sys - Driver Reference Table - dam.sys
Again, it is not the cause - just a default.
The bugchecks on all dumps - 0x14f - A system component failed to respond within the allocated time period, preventing the system from exiting connected standby. The dumps don't tell us what the system component is.
Run Driver Verifier - see if any 3rd party drivers are flagged - https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html
Let it run for 24 hours minimum.
I don't know at this time if we're dealing with a software or hardware issue.
EDIT: Are all Windows Updates installed? I'm getting symbol errors on the Windows kernel in the dumps.
Regards. . .
jcgriff2
Code:
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\011916-10312-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Tue Jan 19 20:11:22.518 2016 (UTC - 5:00)
System Uptime: 1 days 8:33:00.282
Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )
BUGCHECK_STR: 0x14F_INVALID
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_INVALID_pdc!PdcpMonitorOnWatchdogWorker
Bugcheck code 0000014F
Arguments 00000000`00000000 00000000`00000100 00000000`00000000 00000000`4f4d524d
BiosVersion = 103.873.768
BiosReleaseDate = 11/09/2015
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012416-9875-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Sun Jan 24 14:51:48.513 2016 (UTC - 5:00)
System Uptime: 1 days 2:47:32.294
Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )
BUGCHECK_STR: 0x14F_INVALID
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_INVALID_pdc!PdcpMonitorOnWatchdogWorker
Bugcheck code 0000014F
Arguments 00000000`00000000 00000000`00000100 00000000`00000000 00000000`50434c45
BiosVersion = 103.873.768
BiosReleaseDate = 11/09/2015
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020216-10015-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Tue Feb 2 21:29:56.573 2016 (UTC - 5:00)
System Uptime: 1 days 23:11:17.967
Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )
BUGCHECK_STR: 0x14F_INVALID
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_INVALID_pdc!PdcpMonitorOnWatchdogWorker
Bugcheck code 0000014F
Arguments 00000000`00000000 00000000`00000100 00000000`00000000 00000000`50434c45
BiosVersion = 103.873.768
BiosReleaseDate = 11/09/2015
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020316-9437-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Wed Feb 3 06:45:12.211 2016 (UTC - 5:00)
System Uptime: 0 days 8:57:37.992
Probably caused by : dam.sys
BUGCHECK_STR: 0x14F_DAM
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys
Bugcheck code 0000014F
Arguments 00000000`00000004 00000000`00000001 ffffc000`b13fa910 ffffd000`529efb60
BiosVersion = 103.873.768
BiosReleaseDate = 11/09/2015
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030116-10390-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Tue Mar 1 11:36:32.100 2016 (UTC - 5:00)
System Uptime: 0 days 3:19:53.448
Probably caused by : dam.sys
BUGCHECK_STR: 0x14F_DAM
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys
Bugcheck code 0000014F
Arguments 00000000`00000004 00000000`00000002 fffff801`71837a58 ffffd000`7c4cdb60
BiosVersion = 104.1085.768
BiosReleaseDate = 01/29/2016
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030116-12843-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Tue Mar 1 08:15:48.224 2016 (UTC - 5:00)
System Uptime: 3 days 17:26:50.250
Probably caused by : dam.sys
BUGCHECK_STR: 0x14F_DAM
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys
Bugcheck code 0000014F
Arguments 00000000`00000004 00000000`00000002 fffff800`82e67a58 ffffd000`4713eb60
BiosVersion = 104.1085.768
BiosReleaseDate = 01/29/2016
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030216-10296-01.dmp]
Built by: 10586.122.amd64fre.th2_release_inmarket.160222-1549
Debug session time: Wed Mar 2 17:43:20.993 2016 (UTC - 5:00)
System Uptime: 0 days 18:15:31.309
Probably caused by : dam.sys
BUGCHECK_STR: 0x14F_DAM
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_DAM_IMAGE_dam.sys
Bugcheck code 0000014F
Arguments 00000000`00000004 00000000`00000002 fffff801`8ce17a58 ffffd000`7c270b60
BiosVersion = 104.1085.768
BiosReleaseDate = 01/29/2016
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\011616-8984-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Sat Jan 16 18:41:08.455 2016 (UTC - 5:00)
System Uptime: 1 days 0:24:22.916
Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )
BUGCHECK_STR: 0x14F_INVALID
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: 0x14F_INVALID_pdc!PdcpMonitorOnWatchdogWorker
Bugcheck code 0000014F
Arguments 00000000`00000000 00000000`00000100 00000000`00000000 00000000`50434c45
BiosVersion = 103.873.768
BiosReleaseDate = 11/09/2015
SystemManufacturer = Microsoft Corporation
SystemProductName = Surface Pro 4
MaxSpeed: 2400
CurrentSpeed: 2496
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
Last edited:
OK... be sure to save your work often because if Driver Verifier detects a driver violation, it will force a BSOD immediately. This is what we're hoping for -- to find the offending driver, assuming one exists.
Regards. . .
jcgriff2
Regards. . .
jcgriff2
Hi Moosic,
Have you noticed if the BSoDs are occurring when your Surface is going into/coming out of standby? It could be by either intentionally pressing the standby button, or due to inactivity. Both PDC and DAM are related to connected standby. "PDC_WATCHDOG_TIMEOUT" occurs when the system fails to exit connected standby as the result of a timeout, see:
When you get these crashes, do you have your Surface plugged into an external monitor, or are you using it standalone?
Have you noticed if the BSoDs are occurring when your Surface is going into/coming out of standby? It could be by either intentionally pressing the standby button, or due to inactivity. Both PDC and DAM are related to connected standby. "PDC_WATCHDOG_TIMEOUT" occurs when the system fails to exit connected standby as the result of a timeout, see:
Code:
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: fffff8018ce17a58, Pointer to the resiliency client (pdc!_PDC_RESILIENCY_CLIENT).
Arg4: ffffd0007c270b60, Pointer to a pdc!PDC_14F_TRIAGE structure.When you get these crashes, do you have your Surface plugged into an external monitor, or are you using it standalone?
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.
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 enabledI enabled hyper-v three days ago based on recommendations on /r/surface. It was throwing blue screens long before this. It has been blue screening since launch day.
"launch day" as in the day that you got the new system?
If so, why not take it back and exchange for another?
I have access to other Surface Books and SP4 devices. I'm seeing similar behavior on those devices. I don't think it is a hardware issue.
Sadly the Surface Pro 4 isn't a perfectly stable device - I've had quite a few issues on mine.
The latest firmware updates have helped me immensely, but it's not perfect. I don't think it ever will be. There are bugs in Windows 10, the Intel drivers and the firmware. I love my SP4 - it's beautiful and fantastic for use in school for note taking, but it's a pretty buggy device.
Had a few of the same BSOD on my device in the early days - none recently though.
I'm also running ESET on my Surface, although I don't think that's the cause. If uninstalling ESET resolves the issue, then let me know.
The latest firmware updates have helped me immensely, but it's not perfect. I don't think it ever will be. There are bugs in Windows 10, the Intel drivers and the firmware. I love my SP4 - it's beautiful and fantastic for use in school for note taking, but it's a pretty buggy device.
Had a few of the same BSOD on my device in the early days - none recently though.
I'm also running ESET on my Surface, although I don't think that's the cause. If uninstalling ESET resolves the issue, then let me know.
Are you using the Windows 10 version of WinDbg?
I'll be uninstalling ESET on Monday. I have to move my machine into another OU so I can uninstall. I'm also running Eset 5. I'm going to get my hands on Eset 6 and give it a shot.
Yes.
I'm running Windows 10 Enterprise 1511, fully patched. If that matters.
Ok great - perhaps that will help.
Connected Standby is one of the buggiest things I've ever used though.
Can you go to Device Manager and let me know what version of the Intel display driver and Marvell WiFi driver you have installed?
Also, try disabling WiFi during sleep just to test: Settings -> System -> Power & Sleep -> Uncheck stay connected to WiFi while asleep
An ex staff member here made a detailed post about this bugcheck on his blog: Debugging and reverse engineering: PDC_WATCHDOG_TIMEOUT (14f) debugging
I'm also thinking it might be tied to connected standby. It might be tied to my vpn as well. I see tons of entries in my event log about my VPN connecting over and over before the BSOD. I might be leaving the VPN connected before I leave the machine alone. It seems like it goes to sleep and then the VPN keeps trying to reconnect.
I assume you're just using the built in Windows VPN - not OpenVPN or anything?
Correct. L2TP
Has Sysnative Forums helped you? Please consider donating to help us support the site!