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.
It's odd that people are such different experiences with the SP4. I use Edge every day, and have not had a Display Driver crash since the 12/2 updates. I think it might be useful MSFT if everyone reporting problems here states the configuration of their system.
The only serious bugs I have experienced since 12/2 are with the Dock (Brick) - and possibly a minor issue with battery life (about 7 hours max). My configuration:
SP4 bought 10/26 in U.S., 8/256 i5, Type Cover with Fingerprint Sensor
I have a surface pro 4, i7, 16gb, 256 gb hdd configuration. I have all the available updates installed, yet I am still experiencing display driver issues, which is not just limited to scrolling situations on web pages. I am using IE 11, not edge, and I have experienced it several times while streaming Amazon Prime videos, along with several "funky" short vertical lines showing up at the bottom of the video. Also, while the video is streaming and I open up the Action Center, the display in the entire area of the action center is fuzzy. I have also had the driver crash several other times, while not even using internet explorer.
I have expected some issues with new hardware releases, but I am upset that this issue has not been fixed yet. Especially after spending well over $2000 on this computer and accessories specifically for this device - If I would have known about this issue I would not have made the purchase. I will be advising people to purchase a different product, or wait until this issue is resolved.
