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
    2015-11-19T13:17:40+00:00

    After installing the 18 November updates, I'm still getting the display driver failure/recovery message at random intervals when using Firefox browser.  As an aside, the Pro4 is still stuck in tablet mode when awakening from sleep/hibernate mode.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-19T11:44:52+00:00

    Well, after all the updates being applied I have not had one issue at all. My SP4 has been running perfect ! Even when using Edge. And I use the hell out of my SP4 being a IT manager for a software company. Now I have kept my power settings the same though while on battery power, hibernate instead of sleep. Battery life is good, no display crashes and it is very speedy.  Wish the best of luck to all of you that are having issues still. I am a happy camper now :D

    Me too - no issues since the last update; I've not had a system freeze, and it has woken from sleep properly several times with no reboot required. Early days, but very promising here.

    Was this answer helpful?

    0 comments No comments