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.
Since upgrading to Windows 10, I can tell you that Microsoft has reintroduced this problem in Surface Pro 2. It happens with any browser, FF, Chrome or IE, not just Edge. Extremely frustrating that MS hasn't even acknowledged the issue for SP2 devices, they only seem concerned with SP4, presumably because so many people are returning them in the first 30 days. On that particular score, I returned my SP4 i7 after 48hrs because of the appalling fan noise. It would come on even when idle and after having applied all updates. Ordered another one, but if it suffers from the same thing, it will go back, too. Cannot believe how shoddy Microsoft has become recently.
It's really odd that people are having such different experiences with the same hardware and all software up to date. I received my SP4 on October 26, the first day of availability, so it must be from one of the first batches. I've had no display driver issues since the November updates. I do have glitches occasionally with Edge freezing or losing internet connection. I can often get things going again by using touchscreen functions.
