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.
I'm running the new driver for 2 days now and it has been night and day. So I assume your problems will be solved also.
The only things we need to wait for know are the sleep fix/update from microsoft (comming somewhere in the beginning of 2016 they said) and the microsoft version of the display driver you just installed. This will not really change anything I think but then you'll be running a microsoft tested drivers instead of just the Intel generic driver for your chipset (which is fine...)
Your unit is not faulty, let me stress that, the problems you've been having before is just because the last display driver update microsoft released contained a beta driver (you can see here: https://downloadcenter.intel.com/product/88358/Intel-Iris-Graphics-540-for-6th-Generation-Intel-Core-Processor ) and had a lot of known issues that where rather bad...
It solved some previous issues users had but not all of them, Intel then released a bit more mature version of that driver which you just installed.
I think it's much better and actually makes my Surface reliable (always wakes from sleep and no freezes/lockups anymore), Miracast actually works know and so on... There are still some known issues (mostly incompatible with some games) with it but I suspect Intel will release more driver updates in the coming weeks.
But we always have to wait before microsoft releases those updates in one of their sanctioned updates via the windows update platform and there is always a bit of time in between, one or 2 weeks probably...
If my system is reliable I do not mind waiting but the beta driver was so bad I went ahead and installed the generic driver. I'm glad I did.
So in conclusion, it's mostly Intell's fault of not supporting their new silicon with proper drivers from the get go. Maybe also a bit of Microsoft's fault for not applying enough pressure on Intel to come up with solid drivers? They had to use these chips as the market "needed/suspected" them... It's just really sad that so many people have problems and bad experiences with expensive devices just because drivers are not ready.
I also noticed that the 4326 'beta' intel release was the current windows update...................DOH
If MS were smart(hint) they would fast track the latest 4352 intel driver to windows update. Like now perhaps.
It appears that the currently 'windows updating' as we speak 4326 driver is less stable then the previous non-beta 4300... and causing them more issues.
Who would push a 'beta' driver update right before their holiday vacation?????????
Should be demoted....
MS pushed it OTA, not intel.....
