BSOD PDC.SYS / DAM in Connected Standby

Bobby42 · Sep 2, 2015

· OS: Windows 10
· x64
· What was original installed OS on system? Windows 8.1
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? full retail (MSDN)
· Age of system (hardware)? 6 Month
· Age of OS installation - have you re-installed the OS? 1 week / fresh installation

· CPU? Intel i5
· Video Card? Intel

· System Manufacturer? Microsoft
· Exact model number (if laptop, check label on bottom)? Surface Pro 3

· Laptop or Desktop? Laptop

Hi,

I have frequent BSODs on my SP3 with Win10 when it's in connected standby mode.

I already analyzed the Crash Dump and found the following failure:
BUCKET_ID: 0x14F_DAM_pdc!PdcpNotificationWatchdog

I know what pdc.sys and the NotificationWatchdog is and I know what DAM (Desktop Activity Moderator) is for.

My suspicion is that one of the installed applications causes the crash of the DAM process.

Do you see any hint in the dump which software it could be?

I had the problems after the upgrade and did a fresh installation. After I installed my application the bsod came back. If there is no hint in the dump the only way is to install the applications one by one and wait after each installation a couple of days to see, if the bsod is back.

Thx
Robert

View attachment SysnativeFileCollectionApp.zip

usasma · Sep 2, 2015

As you probably know, DAM suspends processes when the system is in connected standby.
The raw stack test also shows traces of hal.dll when the system crashes.
I'd first suspect an incompatibility w/W10

There's mention on the web that StoreApps shouldn't cause this - but shouldn't is a far cry from don't/won't
I'd first suggest re-registering your Store Apps: How to re-register Windows Store apps in Windows 10 / 8

The only error that might be to blame, that I see in the WER section of MSINFO32 is cyberJack Base Components (ctrsct32.dll). But it's not noted at the time of the BSOD's, so I have to wonder if it's an issue or not. Try uninstalling it to see if it helps (I presume that the BSOD is easily generated by putting the system into connected standby?)

As there's just not all that much on STOP 0x14F errors available, I'd fall back on the old standby - and run Driver Verifier according to these directions: Driver Verifier Settings

Analysis:
The following is for informational purposes only.

Code:

**************************Tue Sep  1 01:49:12.972 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\090115-10703-01.dmp]
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Built by: 10240.16463.amd64fre.th1.150819-1946
System Uptime:0 days 12:31:13.906
*** ERROR: Module load completed but symbols could not be loaded for pdc.sys
Probably caused by :pdc.sys ( pdc+12144 )
BugCheck 14F, {4, 1, ffffc001079315c0, ffffd00021701b50}
BugCheck Info: PDC_WATCHDOG_TIMEOUT (14f)
Arguments: 
Arg1: 0000000000000004, Client ID of the hung component.
Arg2: 0000000000000001, A notification client failed to respond.
Arg3: ffffc001079315c0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: ffffd00021701b50, Pointer to a pdc!PDC_14F_TRIAGE structure.
BUGCHECK_STR:  0x14F_DAM
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x14F_DAM_pdc+12144
CPUID:        "Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz"
MaxSpeed:     1900
CurrentSpeed: 2494
 
Processor may be overclocked!
Expected Frequency:   1900
Actual Frequency:     2494
Overclock Ratio:      1.31263
 
  BIOS Version                  3.11.0950
  BIOS Release Date             06/05/2015
  Manufacturer                  Microsoft Corporation
  Product Name                  Surface Pro 3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug 30 12:01:20.955 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\083015-7859-01.dmp]
Windows 8 Kernel Version 10240 MP (4 procs) Free x64
Built by: 10240.16463.amd64fre.th1.150819-1946
System Uptime:1 days 2:06:45.888
*** ERROR: Module load completed but symbols could not be loaded for pdc.sys
Probably caused by :pdc.sys ( pdc+12144 )
BugCheck 14F, {4, 1, ffffc000b02ffbf0, ffffd00020d99b50}
BugCheck Info: PDC_WATCHDOG_TIMEOUT (14f)
Arguments: 
Arg1: 0000000000000004, Client ID of the hung component.
Arg2: 0000000000000001, A notification client failed to respond.
Arg3: ffffc000b02ffbf0, Pointer to the notification client (pdc!_PDC_NOTIFICATION_CLIENT).
Arg4: ffffd00020d99b50, Pointer to a pdc!PDC_14F_TRIAGE structure.
BUGCHECK_STR:  0x14F_DAM
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x14F_DAM_pdc+12144
CPUID:        "Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz"
MaxSpeed:     1900
CurrentSpeed: 2494
 
Processor may be overclocked!
Expected Frequency:   1900
Actual Frequency:     2494
Overclock Ratio:      1.31263
 
  BIOS Version                  3.11.0950
  BIOS Release Date             06/05/2015
  Manufacturer                  Microsoft Corporation
  Product Name                  Surface Pro 3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

**************************Tue Sep  1 01:49:12.972 2015 (UTC - 4:00)**************************
TeeDriverx64.sys                  Wed Nov 27 12:56:32 2013 (52963250)
SurfaceDisplayCalibration.sys     Fri May  2 15:16:48 2014 (5363EF20)
SurfaceAccessoryDevice.sys        Fri May 23 00:54:43 2014 (537ED493)
TrueColor.sys                     Tue Jun 17 01:57:42 2014 (539FD8D6)
SurfacePciController.sys          Sat Sep 27 06:32:23 2014 (54269237)
SurfaceCapacitiveHomeButton.sys   Tue Nov 25 14:47:32 2014 (5474DCD4)
SurfaceIntegrationDriver.sys      Tue Dec  2 00:03:51 2014 (547D4837)
iaLPSSi_I2C.sys                   Mon Feb  2 04:00:08 2015 (54CF3C98)
iaLPSSi_GPIO.sys                  Mon Feb  2 04:00:09 2015 (54CF3C99)
SurfacePenDriver.sys              Mon Mar 30 16:11:03 2015 (5519ADD7)
wificlass.sys                     Sat Apr  4 01:49:01 2015 (551F7B4D)
mrvlpcie8897.sys                  Thu Jun  4 21:51:29 2015 (557100A1)
RTKVHD64.sys                      Mon Jun 29 22:53:38 2015 (559204B2)
intelppm.sys                      Thu Jul  9 23:12:59 2015 (559F383B)
IntcDAud.sys                      Fri Jul 10 07:58:41 2015 (559FB371)
igdkmd64.sys                      Fri Jul 17 20:27:57 2015 (55A99D8D)

http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
SurfaceDisplayCalibration.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SurfaceAccessoryDevice.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
TrueColor.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SurfacePciController.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SurfaceCapacitiveHomeButton.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
SurfaceIntegrationDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=iaLPSSi_I2C.sys
http://www.carrona.org/drivers/driver.php?id=iaLPSSi_GPIO.sys
SurfacePenDriver.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
wificlass.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=mrvlpcie8897.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys

Bobby42 · Sep 2, 2015

Thanks for your reply!

usasma said:
The raw stack test also shows traces of hal.dll when the system crashes.
I'd first suspect an incompatibility w/W10

But this might be in the original MSFT hal.dll!?

usasma said:
There's mention on the web that StoreApps shouldn't cause this - but shouldn't is a far cry from don't/won't

I do not use an StoreApps and did not install any other StoreApp. So might be a try worth and without risk for me to uninstall them via PowerShell.

usasma said:
The only error that might be to blame, that I see in the WER section of MSINFO32 is cyberJack Base Components (ctrsct32.dll). But it's not noted at the time of the BSOD's, so I have to wonder if it's an issue or not.

Ironically this is the only non-microsoft driver with offical Win 10 support. There is a printer driver and a usb network device driver which do not have offical win 10 support so I used the Win 8/8.1 version. I uninstalled the network driver in the meantime and the bsod happed again.

usasma said:
I presume that the BSOD is easily generated by putting the system into connected standby?

No. The BSOD happens while the device is in connected standby. It might be minutes after putting - or hours.

usasma said:
As there's just not all that much on STOP 0x14F errors available, I'd fall back on the old standby - and run Driver Verifier according to these directions: Driver Verifier Settings

Thx, i will try.

usasma · Sep 2, 2015

No, the presence of hal.dll is simply the system checking with hal.dll.
Most often you'll see this with compatibility errors, but it can be due to other things

You installed W10 - there are Store apps on your system
You upgraded from W8.1 - there were Store apps on the system then also.

The Cyberjack thing had an error in the WER section of MSINFO32. I did not see errors from other, non-Windows programs.
As such, it's the most suspect IMO - even if it's supposed to be W10 compatible.
Regardless, it won't hurt to uninstall it to see if the problem recurs.
As the error doesn't occur on demand, you'll have to test overnight then.

As for the Driver Verifier - if we get lucky it'll point out a 3rd party driver and we'll see what happens.
Should Driver Verifier not crash the system - then we're looking at a hardware/Windows driver/compatibility issue.

Bobby42 · Sep 2, 2015

Great, thanks again!

Hopefully it's not Cyberjack. It's the Smartcard Reader for HBCI/Online Banking. That would be "business critical" for me.

I'll post when I have something new. As the BSDO does not happen immediatly it could take a few days.

Search

Search

BSOD PDC.SYS / DAM in Connected Standby

Bobby42

New member

usasma

Retired Admin

Bobby42

New member

usasma

Retired Admin

Bobby42

New member