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 No 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 No comments

2,411 additional answers

Sort by: Oldest
  1. Anonymous
    2015-11-08T10:25:42+00:00

    I have had the same problem with an SP4: if the screen turns off automatically, I can't turn it back on again. I have to hold down the power button for 15 seconds to do a hard shutdown, and restart.

    One approach that seems to work is never to let the screen turn off automatically, as mentioned above. Always sleep it using the menus. It restarts easily.

    Another approach is getting onto the Insider Fast track and installing build 10586. I've only just done that myself a few hours ago, and though it's early days it seems to be waking properly for the first time touch wood.

    I also wonder whether setting the sleep timer to be shorter than the screen off timer might help, if it's a screen off problem rather than a sleep problem. I can't test that right now because since 10586 I can't reproduce the problem. :) Touch wood.

    John

    UPDATE: Ugh. Spoke too soon. Had to do the 15 second poweroff again to start it again from sleep. Resorting to kludge #1 until a real solution is found...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-08T14:18:21+00:00

    Same here. It is unacceptable that a device so expensive and a version 4 still has these VERY ANNOYING issues. Never had these problems when I was on Mac. Fix this Microsoft!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-11-09T02:19:33+00:00

    Just like many people on this thread, my Surface Pro 4 (i5/8GB/256GB) has issues multiple times during the day on waking up from sleep.

    When I close the fingerprint Type Cover, the screen turns off as expected. But when I open the Type Cover and press the power button to wake it up, about 20% of the time it doesn't wake up or Windows Hello IR camera doesn't work or it will wake up but the TouchPad will stop working even if the keyboard works. Sometimes, this happens even if I open the Type Cover and press the power button within a couple of minutes from closing it.

    This has been very frustrating to me because I am forced to reboot the machine at the most inopportune moments (such as when getting ready to take notes or to give a Surface Pro 4 demo to someone)!

    So I finally figured out how to look at the Crash Dumps (.dmp files) using WinDbg and it shows that my Surface Pro 4 frequently gets the VIDEO_TDR_TIMEOUT_DETECTED (117) error!

    Hopefully someone from Microsoft Surface Team is reading this and can take this information to troubleshoot and fix this issue!!

    Error Details for Microsoft Surface Team:

    : kd> !analyze -v


    Bugcheck Analysis


    VIDEO_TDR_TIMEOUT_DETECTED (117)

    The display driver failed to respond in timely fashion.

    (This code can never be used for a real bugcheck.)

    Arguments:

    Arg1: ffffe001c07ae3f0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

    Arg2: fffff80144836770, The pointer into responsible device driver module (e.g owner tag).

    Arg3: 0000000000000000, The secondary driver specific bucketing key.

    Arg4: 0000000000000164, Optional internal context dependent data.

    Debugging Details:

    BUGCHECK_P1: ffffe001c07ae3f0

    BUGCHECK_P2: fffff80144836770

    BUGCHECK_P3: 0

    BUGCHECK_P4: 164

    FAULTING_IP:

    igdkmd64+16770

    fffff801`44836770 ?? ???

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

    TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

    CPU_COUNT: 4

    CPU_MHZ: 9c0

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4e

    CPU_STEPPING: 3

    BUGCHECK_STR: 0x117

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    STACK_TEXT:

    ffffd00029c8f8f0 fffff801452411d1 : ffffe001c07ae3f0 0000000080000000 ffffe001c07ae3f0 ffffe001c73c38f0 : watchdog!WdDbgReportRecreate+0x104

    ffffd00029c8f940 fffff8014524074f : ffffc00000000000 ffffc000fc3f6830 ffffe001c07ae3f0 ffffe001c07ae3f0 : dxgkrnl!TdrUpdateDbgReport+0xe1

    ffffd00029c8f990 fffff8014522c830 : ffffc000fc68cc52 ffffe001c19b4010 ffffe001c19b47b0 ffffe001c07ae3f0 : dxgkrnl!TdrCollectDbgInfoStage2+0x1df

    ffffd00029c8f9c0 fffff80145240e45 : 0000000000160138 0000000000000000 fffffffffffe7960 0000000000000000 : dxgkrnl!DXGADAPTER::Reset+0x168

    ffffd00029c8fa10 fffff80145240f9b : 0000000000000000 fffff800575db340 ffffe001bdeceda0 fffff8005727c5d0 : dxgkrnl!TdrResetFromTimeout+0x15

    ffffd00029c8fa40 fffff8005727bdd9 : ffffe001c65cb680 fffff80145240f40 ffffe001c0fa0660 000000000016da38 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b

    ffffd00029c8fa70 fffff800572e8558 : ffffe001bc37a780 0000000000000080 fffff800575db340 ffffe001c65cb680 : nt!ExpWorkerThread+0xe9

    ffffd00029c8fb00 fffff800573553c6 : fffff80057565180 ffffe001c65cb680 ffffe001c65fd800 0000000000000000 : nt!PspSystemThreadStartup+0x58

    ffffd00029c8fb60 0000000000000000 : ffffd00029c90000 ffffd00029c89000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

    STACK_COMMAND: kb

    FOLLOWUP_IP:

    igdkmd64+16770

    fffff801`44836770 ?? ???

    SYMBOL_NAME: igdkmd64+16770

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5629d0c5

    FAILURE_BUCKET_ID: LKD_0x117_IMAGE_igdkmd64.sys

    BUCKET_ID: LKD_0x117_IMAGE_igdkmd64.sys

    PRIMARY_PROBLEM_CLASS: LKD_0x117_IMAGE_igdkmd64.sys

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:lkd_0x117_image_igdkmd64.sys

    FAILURE_ID_HASH: {df5cc292-6e03-34f8-7849-e22c43f13df4}

    Followup: MachineOwner

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-11-09T17:19:54+00:00

    try a two button restart

    Step 1: Press and hold the power button on your Surface for 30 seconds.

    Step 2: After Surface turns off, press and hold volume-up button and the power button on your Surface at the same time for at least 15 seconds, and then release both.                                                                             

            The screen may flash the Surface logo, but continue holding the buttons down for at least 15 seconds.

    Step 3: After you release the buttons, wait 10 seconds.

    Step 4: Press and release the power button again to turn your Surface back on.

    That does work, but it is annoying to have to do this several times in one week. At least now I can get it back up again, so thanks.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments