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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. 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

    0 comments No comments
Accepted answer
  1. 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

    0 comments No comments
Accepted answer
  1. Anonymous
    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.

    0 comments No comments

655 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-10-27T21:08:25+00:00

    Just got the surface pro 4 - keep getting the following error:

    "Display driver stopped responding and has recovered. Display driver Intel Graphics Accelerator Drivers for Windows 8(R) stopped responding and has successfully recovered."

    Seems this was an issue back with Surface Pro 2.

    0 comments No comments
  2. Anonymous
    2015-10-28T13:07:42+00:00

    How disappointing. Brand new, out the box and I already have issues with my Surface Pro 4. Screen flickering, speaker popping. My google research reveals that there are known issues. I get an error message that refers to the display driver and then the screen locks up and I am not able to do anything on this device. Too much money spent for these issues right out the box. First night with the device and not able to do anything much with it as I got this display driver message 3 times within 30 minutes. Back to my MAC and IPad for now. Since this is a known issue what does Microsoft expect me to do with this costly device in the meantime?

    0 comments No comments