surface pro 4 display adapter crash

Anonymous
2015-10-29T15:57:46+00:00

Split from this thread.

Surface pro 4 display adapter error, "Display adapter igfx stopped responding and has recovered", event id 4101. Seems to be only when running Edge.

What date is on the current driver??

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 No comments
Answer accepted by question author
Anonymous
2016-02-17T23:02:27+00:00

Hi All,

We released an update on 2/17/2016 that addresses this issue.

We recommend that you install this update to keep your Surface performing its best. You can get updates now by checking Settings> Update & security> Windows Update.

To confirm the updates are installed, check Settings> Update & security> Windows Update> Advanced options> View your update history.

Thanks,

Josh

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2016-02-15T00:03:05+00:00

Hi

I suspect devices racing to awaken are interfering with each other. Leaving WiFi on during sleep (settings > system>power & sleep), which I set yesterday,  seems to have fixed the black screen on "awakening" problem I have been having on my surface pro 4. (Of course sleep, under the balanced power scheme, consumed up to 23% of battery capacity this way).

WiFi set off during sleep used to reconnect after sign-in and startup. Updates installed in January changed this so that it was on by that time.

Since I've still gotten the MTConfig errors sometimes and also distributed COM errors and warnings on Kernel-PnP: WUDFRd failing to load for device ... and ACPI: EC returned data when none was requested, that were also being reported in the 'System' event log, inelegance remains. However, my screen isn't black and I don't have to force shutdown and reboot to wake the Surface.

Hope this helps

K

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
2016-01-15T11:25:17+00:00

Try a two button reset

Step 1: Swipe in from the right and tap or click Settings, tap or click Power, and then tap or click Shut down to shut down Surface. If you can’t shut down Surface normally, 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.

if this does not work, you will need to exchange it.

Was this answer helpful?

0 comments No comments

655 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-01-20T21:13:48+00:00

    I too manually installed Intel display driver version 4352 and have yet to received another display driver crash notice or odd transitions in display brightness.  Microsoft might be delaying the official release of this driver until they can fully test it after they rushed out the previous build stating that it fixed all of the display issues and that turned out not to be the case for everyone.  The other possibility is that they've already determined that this build does not resolve all of the issues and are waiting for Intel to release the next build.  This and other driver updates might be included in Insider Preview Build 11099 (Info here).  As an IT Engineer, I might not mind installing Insider Preview Builds but wouldn't necessarily go recommending that others do the same because I have experienced some very annoying issues with certain builds on my other 2-in-1 convertible laptop and a tablet.  Here some SP4 issues that I'm experiencing.

    1. Yes it's a backlit display but I'm experiencing a higher than normal amount of light leakage from multiple spots around all sides that's more noticeable in low light situations.  Will see if display driver version 4352 affects that.
    2. Type cover:  Frequent key and trackpad response issues where the cursor location sometimes disappears and reappears in the wrong place as there's a delayed response to my typing or tapping on the trackpad.  Much less frequently, the fingerprint scanner fails to work after the system wakes from sleep.
    3. OS issues: Edge browser is a system resource hog and huge drain on the battery, especially when opening sites with multimedia content.  This causes the system fan to run at full speed.  Closing the culprit tab is sometimes difficult and the tab title will just flash at you.  Hitting the back arrow to exit the page before closing the tab tends to help.  Be sure to close Edge before entering sleep/hibernate mode.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-18T20:24:32+00:00

    Guys,

    I was able to alleviate 90% of my issues by forcing the newer Intel driver mentioned in this thread (20.19.15.4352). Just use 7zip and extract the files, and manually force it in device manager by saying (Let me pick from a list of device drivers on my computer). 

    My original issue (and snippet of email) to Microsoft is as follows:

    "The SP4 is border-line unusable in it’s current state with the one that I have from early inventory. If you are connected to the dock and lock the PC, 75% chance it doesn’t come back and you have to hard reset. Put it to sleep and the odds are even worse. In that 25% of the time that it actually does come back from lock, you lose your external monitor configuration and the display driver crashes. 

    In this state, I wouldn’t send these out to our end users. I can deal with this, but I know end-users would never be able to handle it. "

    Thanks for the Intel driver suggestion all; it really has mostly fixed my issues.

    Chris

    Was this answer helpful?

    0 comments No comments