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.
As I mentioned previously I am now on my 3rd Surface Pro 4. This one seems to be working better. I still have a few (not many) display adapter issues but as has been mentioned that is an Intel problem. The fact that they are taking so long to fix it, seems to indicate that this is quite an issue with no quick and easy solutions.
By using hibernate instead of sleep the computer is also working better. Something about the sleep mode seems to sometimes keep the computer from every waking up. Microsoft Edge is a big problem. Most issue occur when using it. So I no longer have it as the default and I use Chrome exclusively. Within Chrome I have not had any crashes. Also when Edge is open my track pad sometimes freezes up. Closing Edge seems to fix that.
The people at the Microsoft store speculated that the Build numbers may be part of the problem. My first two had a Build number of 1541 and this one is 1546. I have no idea if that means anything...but maybe.
So we will see. Keeping my fingers crossed.
Yes, I see the docking problem as well. I have video taped the issue in case MS needs evidence (although I can't imaging that they would). You have, no doubt, figured out that rebooting after docking will clear the flashing. This handicaps the functionality of docking/undocking but it's better than nothing.
I'd be curious whether this is related to the graphics driver or this is a separate, dock-related problem.
-bs
