Surface Pro 4 - Screen won't wake from sleep

Anonymous
2015-10-27T05:32:42+00:00

I received my Surface Pro 4 today and it worked fine. I put it on "sleep" for awhile, came back and turned it on. Once again it worked fine. I made an error and instead of putting it on "sleep" I  hit the power button to turn it off when I finished. Now it won't come on at all. The screen stays dark. If I push the power button I can see lights under the keyboard keys, then if I hit the power switch again they go off. But nothing happens to the screen no matter what I do. Has anyone else suffered from this?

Surface | Surface Pro | Display and screen

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
2016-08-19T19:27:34+00:00

It works fine for me after the Anniversary Update to Windows 10 Pro (Version 1607). It no longer goes into a coma.

I just traveled all week. Put my Surface Pro 4 (SP4) to sleep 10 to 20 times each day, and currently my task manager shows the up time to be 7:21:35:21 - 7 days! It is actually working the way I expected it to when I bought it!

It was such a relief to not be scared to put it to sleep during meeting breaks to save battery when working with my Pen and OneNote. For the past 7 months I've had to have it on power when in meetings so that it wouldn't go into a coma. That was always so embarrassing.

You can update to the latest version of Windows 10 by opening Settings > Update & security > Windows Update, and selecting Check for updates.

Was this answer helpful?

10 people found this answer helpful.
0 comments

2,411 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-06-08T12:13:37+00:00

    1724 is the model number.  The lot number is on the original box in small print on a sticker and says date/lot 15xx or 16xx where xx is month batch I think like mine is model 1724 with date lot 1548 which means 2015 April Batch 8.  Someone correct this if I am misinterpreting the month batch.  I used to think it was on the back as well.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-06-08T09:02:42+00:00

    And now I'm suddenly starting to see this as well. I had a couple of bug checks related to the IR camera before the big driver update, but now I get a black screen after waking from sleep, followed by bug check every other time I log (using Windows Hello) on it seems. I don't know if this is significant, but so far the crash/black screen has only happened when another user had locked the screen and was still logged on.

    I see a lot of talk about lot numbers? Is that the 4-digit code printed behind the kickstand? In that case mine is #1724. For those interested, these are the bugcheck details:

    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: 401

    BUILD_VERSION_STRING:  10586.306.amd64fre.th2_release_sec.160422-1850

    SYSTEM_MANUFACTURER:  Microsoft Corporation

    SYSTEM_PRODUCT_NAME:  Surface Pro 4

    SYSTEM_SKU:  Surface_Pro_4

    SYSTEM_VERSION:  D:0B:08F:3C:03P:38

    BIOS_VENDOR:  Microsoft Corporation

    BIOS_VERSION:  104.1121.768

    BIOS_DATE:  03/01/2016

    BASEBOARD_MANUFACTURER:  Microsoft Corporation

    BASEBOARD_PRODUCT:  Surface Pro 4

    DUMP_TYPE:  1

    BUGCHECK_P1: 0

    BUGCHECK_P2: 100

    BUGCHECK_P3: 0

    BUGCHECK_P4: 50434c45

    BUGCHECK_STR:  0x14F_MONITORON_0x0_ELCP

    CPU_COUNT: 4

    CPU_MHZ: 5e8

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,4e,3,0 (F,M,S,R)  SIG: 82'00000000 (cache) 82'00000000 (init)

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  DARTH

    ANALYSIS_SESSION_TIME:  06-08-2016 10:51:03.0353

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff8002c9f19d9 to fffff802b6d5c780

    STACK_TEXT: 

    ffffd000224b1a38 fffff8002c9f19d9 : 000000000000014f 0000000000000000 0000000000000100 0000000000000000 : nt!KeBugCheckEx

    ffffd000224b1a40 fffff802b6c5cc59 : fffff802b6fad200 fffff802b6ef6040 fffff80000000000 fffff802b6fad340 : pdc!PdcpMonitorOnWatchdogWorker+0x29

    ffffd000224b1a80 fffff802b6d07b65 : ffffd0010000007b 0000000000000080 ffffe00162491680 ffffe00170ff9800 : nt!ExpWorkerThread+0xe9

    ffffd000224b1b10 fffff802b6d61926 : ffffd00166040180 ffffe00170ff9800 fffff802b6d07b24 0000000000010224 : nt!PspSystemThreadStartup+0x41

    ffffd000224b1b60 0000000000000000 : ffffd000224b2000 ffffd000224ab000 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`2c9f19d9 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

    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-07T12:46:28.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-23 06: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: 1661

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x14f_monitoron_0x0_elcp_pdc!pdcpmonitoronwatchdogworker

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

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-07T22:22:53+00:00

    Surface 4 is still having these issues. BUMMPP!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-07T17:31:41+00:00

    I didn't want the hassle of having to reinstall everything so was hoping that the latest firmware would have fixed the issue, however, I talked to support and they are sending me a refurb which they have told me, and I quote "our device is being carefully checked by our technician before sending in. so I assure you that you will receive a good working device" . I'm skeptical about the refurb but will have to wait and see if it is a good working device.  I expect another lot 15xx with the same issue.

    Was this answer helpful?

    0 comments