This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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??
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.
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
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
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.
Solved?
This may seem brain dead, but it seems that all we had to do is make sure the correct drivers are actually installed.
Like everyone else, I went to the Microsoft Surface Book site https://www.microsoft.com/en-us/download/details.aspx?id=49497 and downloaded the November driver update. I downloaded the msi file as instructed and then rebooted. But kept experiencing problems.
Then as suggested in this thread, I downloaded the zip file. I went to device manager, and updated the drivers for the firmware (yes, in some cases the firmware is actually not automatically updated), the display adapter, the batteries, the network adapter and Bluetooth. In each case I did not do an online search for the driver but instead "search my computer" and pointed to the drivers section of the downloaded zip. I then selected the proposed driver. As a final step, I repeated the procedure but this time selected "Let me pick from a list of device drivers on my computer" and selected the latest version of the drivers available. Surprisingly, in some cases, not the latest driver was being used. For the display driver, I chose Intel HD 520 version 20.19.15.4316 (11/3/2015) that seemed the latest and was somehow available in my PC although version 20.19.15.4308 is the one in the zip file.
I was then prompted to reboot. On my second Surface Book, this prompted a firmware update upon reboot. In both of my Surface Books, the reboot was with no incident.
After that, all the problems have disappeared (so far). I have tested several scenarios that were crashing the video, and so far everything works.
If the solution was that simple, shame on Microsoft for not letting us know earlier.
For your Surface Book or Surface Pro 4?
Solved?
This may seem brain dead, but it seems that all we had to do is make sure the correct drivers are actually installed.
Like everyone else, I went to the Microsoft Surface Book site https://www.microsoft.com/en-us/download/details.aspx?id=49497 and downloaded the November driver update. I downloaded the msi file as instructed and then rebooted. But kept experiencing problems.
Then as suggested in this thread, I downloaded the zip file. I went to device manager, and updated the drivers for the firmware (yes, in some cases the firmware is actually not automatically updated), the display adapter, the batteries, the network adapter and Bluetooth. In each case I did not do an online search for the driver but instead "search my computer" and pointed to the drivers section of the downloaded zip. I then selected the proposed driver. As a final step, I repeated the procedure but this time selected "Let me pick from a list of device drivers on my computer" and selected the latest version of the drivers available. Surprisingly, in some cases, not the latest driver was being used. For the display driver, I chose Intel HD 520 version 20.19.15.4316 (11/3/2015) that seemed the latest and was somehow available in my PC although version 20.19.15.4308 is the one in the zip file.
I was then prompted to reboot. On my second Surface Book, this prompted a firmware update upon reboot. In both of my Surface Books, the reboot was with no incident.
After that, all the problems have disappeared (so far). I have tested several scenarios that were crashing the video, and so far everything works.
If the solution was that simple, shame on Microsoft for not letting us know earlier.
