Repeated BSOD after firmware update - Surface pro 3, Windows 10

Anonymous

Hey everyone

There was a firmware update for the SP3 I just did and my device now seems completely bricked. When I boot it, I instantaneously get a BSOD with one of those two messages : kernel security check failure or driver unloaded without cancelling pending operations.

The BSOD tells me I have to use a win10 device to boot it from, but when I tell the BIOS to boot with my USB win10 key, it doesn't and keeps telling that the OS can't boot and to use a win10 disc (no CD reader on the SP3). Nothing I've tried works so far.

I've had my sp3 for just over a year and I really liked it before windows 10, and I really hope I can get it fixed.

Thanks for your help,

Émile

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

MODERATOR EDIT (10/5/2015): Steps listed here previously are now updated to the following. If you receive a blue screen error after installing the 9/29/2015 Surface Firmware Update please start at step 1 to address.

Step 1 – System Restore Point

1. Boot Surface using USB recovery media. If you do not have recovery media you can download from here: http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/downloadablerecoveryimage. Once you have recovery media proceed to next steps. Note: The USB drive must be formatted to FAT32 (not NTFS) in order to work correctly.

2. Press and hold the volume-down button while you press and release the power button. When the Surface logo appears release the volume-down button.

3. When prompted select the language and keyboard layout you want.

4. Select Troubleshoot, then Advanced Options, followed by selecting System Restore then select the target operating system.

5. In System Restore, click Next.

6. Click on a system restore point that was prior to applying the System Firmware update. Please use a restore point 9/28 or earlier.

7. Click Next.

8. Click Finish.

9. Click Yes when asked if you want to continue.

10. After moving to an earlier restore point you should boot into Windows.

If you were able to restore to an earlier restore point you should now be able to use your Surface again, no additional steps are needed. If you were not able restore to an earlier restore point or you did not have a restore point then continue to step 2 below.

Step 2 – Safe Mode

1. Boot Surface using USB recovery media by pressing and holding the volume-down button while you press and release the power button. When the Surface logo appears release the volume-down button.

2. When prompted select the language and keyboard layout you want.

3. Select Troubleshoot, then Advanced Options, followed by selecting Command Prompt.

4. Type the following command in the command prompt and then press enter:

bcdedit /set {bootmgr} displaybootmenu yes

5. Type the following command in the command prompt and then press enter.

exit

6. Press Turn off your PC.

7. Press the power button on Surface to turn it on.

8. Press F8 when the Windows Boot Manager screen comes up to go to Startup Settings.

9. Press “4” to enable Safe Mode.

10. Surface may do disk checking as well as perform a scan and repair. Surface will then restart. If Surface does not do this and instead boots into Safe Mode, go to step 13.

11. Press F8 when the Windows Boot Manager screen comes up to go to Startup Settings.

12. Press “4” to enable Safe Mode.

13. Surface will start in Safe Mode. Sign into Surface. Press the Windows Start Menu, press Power and select Restart.

14. Press Enter when the Windows Boot Manager screen comes up to boot into Windows 10.

15. Surface will start normally. Sign into Surface. Right-click the Windows Start Menu and click Command Prompt (Admin).

16. Click Yes to allow this app to make changes.

17. Type the following command in the command prompt and then press enter.

bcdedit /set {bootmgr} displaybootmenu no

18. Press the Windows Start Menu, press Power and select Restart.

If you are now able to boot into Windows you should now be able to use your Surface again, no additional steps are needed. If you were not able to boot into Windows then continue to step 3 below.

Step 3 – Reset Surface to factory settings

1. Follow the steps in the article below to boot Surface using USB recovery media and reset Surface back to factory settings: http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/usbrecovery

Please let us know how it goes.

Thanks,

Josh

0 comments

187 additional answers

Anonymous

2016-06-17T16:45:56+00:00

Hello,

My Surface Pro 3 (8/512) occasionally crashes when I wake up from sleep. Usually the screen remains blank for longer than the usual wake period, after which when I log in and find that all of my programs are closed (e.g. the computer restarted rather than/after waking). Today, however, the screen turned on with a BSOD message before restarting. The error message was "PDC_WATCHDOG_TIMEOUT". I'm a bit concerned because a couple weeks ago my home-built desktop also started BSODing with the same error message (randomly, not during wake from sleep) and I'm wondering if the issue on the two computers could be related, perhaps to some Windows Update. I read previous threads about a restart-on-wake issue that were related to the pen driver, but I don't see any hint of that in the debug report. I have the debug reports from the Surface if they're helpful:

6/17:

Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\061716-10093-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       .sympath srv*https://msdl.microsoft.com/download/symbols

OK                                             C:\symbols

Symbol search path is: .sympath srv*https://msdl.microsoft.com/download/symbols;C:\symbols

Executable search path is:

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.306.amd64fre.th2_release_sec.160422-1850

Machine Name:

Kernel base = 0xfffff8012ca16000 PsLoadedModuleList = 0xfffff8012ccf4cd0

Debug session time: Fri Jun 17 09:10:23.166 2016 (UTC - 7:00)

System Uptime: 4 days 22:22:32.375

Loading Kernel Symbols

...............................................................

................................................................

...............................................................

Loading User Symbols

Loading unloaded module list

..................................................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 14F, {0, 100, 0, 50434c45}

Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )

Followup:     MachineOwner

3: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PDC_WATCHDOG_TIMEOUT (14f)

A system component failed to respond within the allocated time period,

preventing the system from exiting connected standby.

Arguments:

Arg1: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 0000000050434c45, A value indicating the internal path taken to initiate the request.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: Microsoft Corporation

SYSTEM_PRODUCT_NAME: Surface Pro 3

SYSTEM_SKU: Surface_Pro_3

SYSTEM_VERSION: 1

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3.11.1150

BIOS_DATE: 12/09/2015

BASEBOARD_MANUFACTURER: Microsoft Corporation

BASEBOARD_PRODUCT: Surface Pro 3

BASEBOARD_VERSION: 1

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 100

BUGCHECK_P3: 0

BUGCHECK_P4: 50434c45

BUGCHECK_STR: 0x14F_MONITORON_0x0_ELCP

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MALACHITE

ANALYSIS_SESSION_TIME: 06-17-2016 09:30:58.0487

ANALYSIS_VERSION: 10.0.10586.567 x86fre

LAST_CONTROL_TRANSFER: from fffff800fc6e19d9 to fffff8012cb58780

STACK_TEXT:

ffffd000233a5b38 fffff800fc6e19d9 : 000000000000014f 0000000000000000 0000000000000100 0000000000000000 : nt!KeBugCheckEx

ffffd000233a5b40 fffff8012ca58c59 : fffff8012cda9200 ffffe001c1012800 fffff80100000000 ffffe001bbe85868 : pdc!PdcpMonitorOnWatchdogWorker+0x29

ffffd000233a5b80 fffff8012cb03b65 : fd732b065ec98a0c 0000000000000080 ffffe001b92a3040 ffffe001c1012800 : nt!ExpWorkerThread+0xe9

ffffd000233a5c10 fffff8012cb5d926 : ffffd0007d55a180 ffffe001c1012800 fffff8012cb03b24 e19a42d8869562a1 : nt!PspSystemThreadStartup+0x41

ffffd000233a5c60 0000000000000000 : ffffd000233a6000 ffffd000233a0000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 6554c1e422ba11db3654290d3c393f4442aaea94

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 030e8e9deb055c9fca4b56340ef04abec30cf624

THREAD_SHA1_HASH_MOD: 9153fcc24a9debd7fc9e7c503c3c6added606b19

FOLLOWUP_IP:

pdc!PdcpMonitorOnWatchdogWorker+29

fffff800`fc6e19d9 cc              int     3

FAULT_INSTR_CODE: 44cccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: pdc!PdcpMonitorOnWatchdogWorker+29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: pdc

IMAGE_NAME: pdc.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 571af2a5

IMAGE_VERSION: 10.0.10586.306

BUCKET_ID_FUNC_OFFSET: 29

FAILURE_BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

PRIMARY_PROBLEM_CLASS: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

TARGET_TIME: 2016-06-17T16:10:23.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-22 21:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 55c

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x14f_monitoron_0x0_elcp_pdc!pdcpmonitoronwatchdogworker

FAILURE_ID_HASH: {b02d0e71-ffbb-2e94-5732-48affd4e19e6}

Followup:     MachineOwner

6/12:

Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\061216-12640-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       .sympath srv*https://msdl.microsoft.com/download/symbols

OK                                             C:\symbols

Symbol search path is: .sympath srv*https://msdl.microsoft.com/download/symbols;C:\symbols

Executable search path is:

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.306.amd64fre.th2_release_sec.160422-1850

Machine Name:

Kernel base = 0xfffff801e741f000 PsLoadedModuleList = 0xfffff801e76fdcd0

Debug session time: Sun Jun 12 10:46:19.506 2016 (UTC - 7:00)

System Uptime: 6 days 0:20:51.252

Loading Kernel Symbols

...............................................................

................................................................

..............................................................

Loading User Symbols

Loading unloaded module list

............................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 14F, {0, 100, 0, 50434c45}

Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )

Followup:     MachineOwner

2: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PDC_WATCHDOG_TIMEOUT (14f)

A system component failed to respond within the allocated time period,

preventing the system from exiting connected standby.

Arguments:

Arg1: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 0000000050434c45, A value indicating the internal path taken to initiate the request.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: Microsoft Corporation

SYSTEM_PRODUCT_NAME: Surface Pro 3

SYSTEM_SKU: Surface_Pro_3

SYSTEM_VERSION: 1

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3.11.1150

BIOS_DATE: 12/09/2015

BASEBOARD_MANUFACTURER: Microsoft Corporation

BASEBOARD_PRODUCT: Surface Pro 3

BASEBOARD_VERSION: 1

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 100

BUGCHECK_P3: 0

BUGCHECK_P4: 50434c45

BUGCHECK_STR: 0x14F_MONITORON_0x0_ELCP

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MALACHITE

ANALYSIS_SESSION_TIME: 06-17-2016 09:42:48.0928

ANALYSIS_VERSION: 10.0.10586.567 x86fre

LAST_CONTROL_TRANSFER: from fffff801505519d9 to fffff801e7561780

STACK_TEXT:

ffffd0008c77fb38 fffff801505519d9 : 000000000000014f 0000000000000000 0000000000000100 0000000000000000 : nt!KeBugCheckEx

ffffd0008c77fb40 fffff801e7461c59 : fffff801e77b2200 ffffe0016b7d1040 fffff80100000000 fffff801e771d068 : pdc!PdcpMonitorOnWatchdogWorker+0x29

ffffd0008c77fb80 fffff801e750cb65 : 0000000000000000 0000000000000080 ffffe00169e74040 ffffe0016b7d1040 : nt!ExpWorkerThread+0xe9

ffffd0008c77fc10 fffff801e7566926 : ffffd0009995a180 ffffe0016b7d1040 fffff801e750cb24 0000000000000000 : nt!PspSystemThreadStartup+0x41

ffffd0008c77fc60 0000000000000000 : ffffd0008c780000 ffffd0008c77a000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 6554c1e422ba11db3654290d3c393f4442aaea94

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 030e8e9deb055c9fca4b56340ef04abec30cf624

THREAD_SHA1_HASH_MOD: 9153fcc24a9debd7fc9e7c503c3c6added606b19

FOLLOWUP_IP:

pdc!PdcpMonitorOnWatchdogWorker+29

fffff801`505519d9 cc              int     3

FAULT_INSTR_CODE: 44cccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: pdc!PdcpMonitorOnWatchdogWorker+29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: pdc

IMAGE_NAME: pdc.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 571af2a5

IMAGE_VERSION: 10.0.10586.306

BUCKET_ID_FUNC_OFFSET: 29

FAILURE_BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

PRIMARY_PROBLEM_CLASS: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

TARGET_TIME: 2016-06-12T17:46:19.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-22 21:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 5bf

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x14f_monitoron_0x0_elcp_pdc!pdcpmonitoronwatchdogworker

FAILURE_ID_HASH: {b02d0e71-ffbb-2e94-5732-48affd4e19e6}

Followup:     MachineOwner

6/6:

Microsoft (R) Windows Debugger Version 10.0.10586.567 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\060616-11562-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       .sympath srv*https://msdl.microsoft.com/download/symbols

OK                                             C:\symbols

Symbol search path is: .sympath srv*https://msdl.microsoft.com/download/symbols;C:\symbols

Executable search path is:

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 10586.306.amd64fre.th2_release_sec.160422-1850

Machine Name:

Kernel base = 0xfffff80144407000 PsLoadedModuleList = 0xfffff801446e5cd0

Debug session time: Mon Jun 6 10:23:29.235 2016 (UTC - 7:00)

System Uptime: 5 days 0:21:53.206

Loading Kernel Symbols

...............................................................

................................................................

..............................................................

Loading User Symbols

Loading unloaded module list

..................................................

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 14F, {0, 100, 0, 50434c45}

Probably caused by : pdc.sys ( pdc!PdcpMonitorOnWatchdogWorker+29 )

Followup:     MachineOwner

0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PDC_WATCHDOG_TIMEOUT (14f)

A system component failed to respond within the allocated time period,

preventing the system from exiting connected standby.

Arguments:

Arg1: 0000000000000000, Client ID of the hung component.

Arg2: 0000000000000100, Win32k did not complete a monitor-on request in a timely manner.

Arg3: 0000000000000000, The most recent POWER_MONITOR_REQUEST_REASON value for this request.

Arg4: 0000000050434c45, A value indicating the internal path taken to initiate the request.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.306.amd64fre.th2_release_sec.160422-1850

SYSTEM_MANUFACTURER: Microsoft Corporation

SYSTEM_PRODUCT_NAME: Surface Pro 3

SYSTEM_SKU: Surface_Pro_3

SYSTEM_VERSION: 1

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 3.11.1150

BIOS_DATE: 12/09/2015

BASEBOARD_MANUFACTURER: Microsoft Corporation

BASEBOARD_PRODUCT: Surface Pro 3

BASEBOARD_VERSION: 1

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 100

BUGCHECK_P3: 0

BUGCHECK_P4: 50434c45

BUGCHECK_STR: 0x14F_MONITORON_0x0_ELCP

CPU_COUNT: 4

CPU_MHZ: 8f7

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R) SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: MALACHITE

ANALYSIS_SESSION_TIME: 06-17-2016 09:44:29.0286

ANALYSIS_VERSION: 10.0.10586.567 x86fre

LAST_CONTROL_TRANSFER: from fffff800b28819d9 to fffff80144549780

STACK_TEXT:

ffffd0002518cb38 fffff800b28819d9 : 000000000000014f 0000000000000000 0000000000000100 0000000000000000 : nt!KeBugCheckEx

ffffd0002518cb40 fffff80144449c59 : fffff8014479a200 ffffe00115a75240 fffff80100000000 ffffe001110d0dd8 : pdc!PdcpMonitorOnWatchdogWorker+0x29

ffffd0002518cb80 fffff801444f4b65 : 0000000000000000 0000000000000080 ffffe001106b2680 ffffe00115a75240 : nt!ExpWorkerThread+0xe9

ffffd0002518cc10 fffff8014454e926 : ffffd0016255a180 ffffe00115a75240 fffff801444f4b24 0000000000000000 : nt!PspSystemThreadStartup+0x41

ffffd0002518cc60 0000000000000000 : ffffd0002518d000 ffffd00025187000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 6554c1e422ba11db3654290d3c393f4442aaea94

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 030e8e9deb055c9fca4b56340ef04abec30cf624

THREAD_SHA1_HASH_MOD: 9153fcc24a9debd7fc9e7c503c3c6added606b19

FOLLOWUP_IP:

pdc!PdcpMonitorOnWatchdogWorker+29

fffff800`b28819d9 cc              int     3

FAULT_INSTR_CODE: 44cccccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: pdc!PdcpMonitorOnWatchdogWorker+29

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: pdc

IMAGE_NAME: pdc.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 571af2a5

IMAGE_VERSION: 10.0.10586.306

BUCKET_ID_FUNC_OFFSET: 29

FAILURE_BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

BUCKET_ID: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

PRIMARY_PROBLEM_CLASS: 0x14F_MONITORON_0x0_ELCP_pdc!PdcpMonitorOnWatchdogWorker

TARGET_TIME: 2016-06-06T17:23:29.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-04-22 21:04:21

BUILDDATESTAMP_STR: 160422-1850

BUILDLAB_STR: th2_release_sec

BUILDOSVER_STR: 10.0.10586.306.amd64fre.th2_release_sec.160422-1850

ANALYSIS_SESSION_ELAPSED_TIME: 5bf

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x14f_monitoron_0x0_elcp_pdc!pdcpmonitoronwatchdogworker

FAILURE_ID_HASH: {b02d0e71-ffbb-2e94-5732-48affd4e19e6}

Followup:     MachineOwner
Was this answer helpful?

0 comments No comments
Anonymous

2016-05-05T03:05:22+00:00

Thank you very much, It's helpful for Surface devices.
Was this answer helpful?

0 comments No comments
Anonymous

2015-10-24T23:16:28+00:00

I would have to go back to mid-August, as the machine wasn't in use for a few weeks. In fact, I did that early in October, but it promptly downloaded the files and started trying to update again (it was thought the update was pulled, but apparently not at that time. Anyway, I undid the system restore and left it alone, and it's been working OK other than having the failed messages for the 3/29 KB.

I think I'll just leave it alone. I went in the software dist. folder and deleted all files with that KB number on them, and I see it hasn't attempted to install it since 10/15, with the machine being in use daily, so maybe it finally gave up. I'll just assume they'll fix it eventually, or not.
Was this answer helpful?

0 comments No comments