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-29T15:24:03+00:00

    Could you help a novice with the process or steps to follow to successfully install the beta video drivers? I have a SP4. Thanks, much, for any help provided.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-29T17:13:10+00:00

    Yeah, it's quite simple. First, you must download the drivers from the website. After you have the drivers these are the steps.

    Extract the ZIP file (don't download the EXE version) to a folder where you know where you are. 

    Right click the windows menu and click Device Manager

    Expand Display Adapters

    Right click Intel HD Graphics 520

    Update

    Click "browse my computer for driver software"

    Click "let me pick from a list of device drivers on my computer"

    Click Have disk

    Click browse

    Locate the folder, and use the files there and select the driver you'd like to use.

    It'll take a little to update the driver, and then the screen will turn off and on a time or two. My person devices needed a restart so the touch screen would work correctly again, or the pen. Both devices had different reactions to the driver changes, but a reboot always fixed the issue.

    Hopefully this helped.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-11-29T17:35:53+00:00

    Thanks, Kent. Very helpful. I am getting an error message that says the "device driver is not compatible with my device". I downloaded the following:

    File name: win64_154012.zip

    Version: Beta 15.40.12.4326 (Latest)

    Date: 11/20/2015

    Size: 179.82 MB

    Language: English

    Operating Systems: Windows 7, 64-bit*, Windows 8.1, 64-bit*, Windows® 10, 64-bit

    I have a SP4, i5, 128GB, 4GB RAM

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-11-29T17:54:38+00:00

    https://downloadcenter.intel.com/downloads/eula/25541/Intel-Beta-Graphics-Driver-for-Windows-7-8-1-10-15-40-?httpDown=https%3A%2F%2Fdownloadmirror.intel.com%2F25541%2Feng%2Fwin64\_154012.zip

    That's the link I would use. I'm sure it's the same, just making sure. 

    Can you give me a screenshot of what you're seeing? and possibly the last 2 steps from where you browse to the correct folder and INF. 

    Let's see if we can get this fixed!

    Was this answer helpful?

    0 comments No comments