Microsoft Surface Pro (2017) BSOD PDC_WATCHDOG_TIMEOUT pdc.sys with Trend Micro Anti Virus

Anonymous
2017-12-16T02:29:14+00:00

Hi,

I've been getting bluescreens for a few days now after a while of doing nothing.

The tablet is currently unused next to me but is on and the display is off, eventually comes just the said BSOD and the part restarts.

Have current Surace Pack on Win10 and current updates.

What could be the PDC_WATCHDOG_TIMEOUT?

The triggering file is pdc.sys.

Surface | Surface Pro | Power and battery

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-01-29T05:01:53+00:00

My Company is experiencing the exact same issue with our Surface Pro Fleet of Devices (1796 & 1807); Trend has been fairly helpful but still yet to confirm a proper fix & it's currently not on the Developers Radar for future fixes.. The "workarounds" suggested & that I've deployed to a few Surfaces are proving successful. 

Trend Micro's Response: 

As per checking deeper on the DMP files that was collected, as per our Developers; the issue is because Behaviour Monitoring is unable to handle events from sleep mode. So indirectly, it leads to PDC.sys, or DAM.sys to BSOD.

--CUT--

PROCESS ffffbe830f8e8640 SessionId: 0 Cid: 196c Peb: d48258b000 ParentCid: 0368 DeepFreeze DirBase: 126388000 ObjectTable: ffffce8bc4bc6480 HandleCount: 2212. Image: TMBMSRV.exe

--CUT--

Suggested Action Plan to apply for testing, provided by Trend Micro: 

  1. Rename AEGIS drivers and create a folder with same name

c:\windows\system32\drivers\tmcomm.sys

c:\windows\system32\drivers\tmactmon.sys

c:\windows\system32\drivers\tmevtmgr.sys

(ps: Take tmcomm.sys for example, rename it as tmcomm.sys.bak, then create a folder named tmcomm.sys)

  1. Create the following registry key entry: 

[HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\aegis]

PowerMonitorTime=dword:0x10

Still awaiting for further development & feedback from Trend but have yet to experience a BSOD with the above mentioned Action steps followed.

Note our case is still opened with Trend Micro, I'll post updates as they occur.

Was this answer helpful?

50+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-01-03T12:18:56+00:00

I uninstalled Trend Micro Anti Virus and the problem went away.  We are now using Symantec Antivirus.

Was this answer helpful?

10+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-03-14T10:21:25+00:00

I can confirm applying just the registry key from the above posts fixes the BSOD/Crash on the 3 Surface books I have updated to 1709 with the latest driver pack 18_015_00 16299 (64 bit)  . 

  1. Create the following registry key entry: 

[HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\aegis]

PowerMonitorTime=dword:0x10

I have logged the call with Trend to find out what exactly the key does before I roll it out and if there is a fix/patch due to be released.

Was this answer helpful?

3 people found this answer helpful.
0 comments

52 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-07T01:06:41+00:00

    Small update from Trend After Some Escalation. 

    Script is no longer required & is recommended to remove the folders that were preventing the creation of the .sys files as indicated below:  

    rmdir C:\windows\system32\drivers\tmcomm.sys

    rmdir C:\windows\system32\drivers\tmactmon.sys

    rmdir C:\windows\system32\drivers\tmevtmgr.sys 

    For Mass deployment fix from the Trend OfficeScan XG  [This will deploy the Registry settings like the script moving forward to all Trend OfficeScan Agents]

    On Trend OfficeScan Server:

    1. Backup the OfcScan.ini located in C:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV 
    2. Turn off the OfficeScan Master Service
    3. Edit the Ofcscan.ini and amend the parameter below or add if it is not indicated.

    [Global Setting]

    PowerMonitorTime = 16

    1. Save the edited Ofcscan.ini
    2. Turn on the OfficeScan Master Service
    3. Login to OfficeScan Server Console
    4. Go to Agents > Global Settings > Click SAVE

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-05T03:25:34+00:00

    Uninstalling Trend did resolve the issue, though unfortunately this is not practical as Trend is utilized in our corporate environment. I have opened a support case with Trend, and as soon as I re-installed Trend (as recommended by them) the BSOD popped up again..

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments