Display driver stopped responding and has recovered, shows wrong drive

Since upgrading to Windows 10 from 8.1, I've seen the following message several times.

Display Driver stopped responding and has recovered
Display driver Intel HD Graphics Drivers for Windows 8(R) stopped responding and has successfully recovered.


When it happens, my laptop screen goes black for a few seconds, except for the taskbar and toast notification. I also have an external monitor that doesn't seem affected at all.

I can reproduce the error pretty consistently if I rapidly switch a Flash video back and forth between full-screen and embedded, but that's not the only time I've seen the problem.

As far as I can tell, everything continues running. Even the full-screen video continues running after the screen isn't black any more.

The weird thing is that the driver name it shows isn't the driver I'm using. I've already upgraded my display drivers to the latest available from Intel's site.

Some things I've observed:

• The information presented by Windows in Settings -> Display -> Advanced display settings shows the driver for Windows 10 that I downloaded from Intel.
• The "Intel HD Graphics Control Center" that was installed along with the driver shows the latest driver version that I downloaded from Intel.
• In Settings -> Apps & Features there's only one "Intel(R) Processor Graphics Driver" listed.
• Event viewer shows very little useful information:
  
  • General
    Display driver igfx stopped responding and has successfully recovered.
  • Details (XML View):
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Display" />
    <EventID Qualifiers="0">4101</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-07T18:18:24.000000000Z" />
    <EventRecordID>1528</EventRecordID>
    <Channel>System</Channel>
    <Computer>Envy</Computer>
    <Security />
    </System>
    - <EventData>
    <Data>igfx</Data>
    <Data />
    </EventData>
    </Event>
  
  

It's conceivable that Intel updated the driver, but forgot to change the string somewhere so the error is actually for the Windows 10 driver.

I don't know how to find out exactly what failed or why. It's getting that string from somewhere.

Any ideas?

Just registered to say that I have the exact same problem (lenovo Y50-70 with intel 4600 igpu) - latest drivers.
We may have more luck with intel communities. Gonna post there & link to your post.

I'm having the same issue. Sometimes I can play a game for hours or five minutes. I started with whatever video drivers Windows 10 gave me when I upgraded from Windows 8.1, drivers from Asrock (I'm using a H97M Pro4), Intel driver, new driver from Asrock, new Intel driver (currently using this now). No joy with any of these.

I've upgraded my BIOS, other drivers etc. I had no issues in Windows 8.1.

I am starting to get that same message quite regularly, not playing games. I have an ASUS GTX 660 Ti and the driver is 355.60. I can't remember having this problem before I got this last driver. I may go back one version and see if this problem continues.

We've helped many people with the "display has stopped responding and has recovered" error. I hope this helps!
Windows 10 - Display Driver Stopped Responding and Has Recovered - YouTube

SimpleHow2z said:

We've helped many people with the "display has stopped responding and has recovered" error. I hope this helps!
Windows 10 - Display Driver Stopped Responding and Has Recovered - YouTube

this didn't help me that much if at all. After reading every post on the web about this problem over the last month or so I did a fresh install of windows ten as I was working with an upgrade install. Still having the problem along with hangups and reboots with various kernal errors and other junk.

Ended up being a setting in my bios! A default setting is to not be using a PnP operating system which the bios then assigns the addresses. Once I switched that to ON my problems have gone away.

landtank said:

this didn't help me that much if at all. After reading every post on the web about this problem over the last month or so I did a fresh install of windows ten as I was working with an upgrade install. Still having the problem along with hangups and reboots with various kernal errors and other junk.

Ended up being a setting in my bios! A default setting is to not be using a PnP operating system which the bios then assigns the addresses. Once I switched that to ON my problems have gone away.

I managed to fix this but i had too do a factory reset few weeks ago now on Win8.1 since Windows 10 has rubbish drivers and too many issues.
BEFORE YOU DO THIS POST WHOCRASHED LOG TO ME DOWNLOAD :http://www.resplendence.com/download...ashedSetup.exe
After you posted whocrashed log ill tell you to do it. Once downloaded click analyse then file export save it and post it here(This is for BSOD and that)
1. Make a restore point ( NEEDED)
2. Download DDU from internet display driver uninstaller
2. Once dowloaded open and click open in safe mode
3. Chooses the display driver that is causing this ( Nvidia, Intel , Amd)
4. Click uninstall and reboot
5. Once rebooted install FROM MANUFACTURER
6. Go to Manufacturer Website fro your computer and download latest chipset drivers etc... (Driver and updates for your computer)
7. Your good to go

landtank said:

this didn't help me that much if at all. After reading every post on the web about this problem over the last month or so I did a fresh install of windows ten as I was working with an upgrade install. Still having the problem along with hangups and reboots with various kernal errors and other junk.

Ended up being a setting in my bios! A default setting is to not be using a PnP operating system which the bios then assigns the addresses. Once I switched that to ON my problems have gone away.

I'm having this exact problem, sporadically. I'm basically a computer novice. I found instructions on how to access the BIOS and did so successfully; however, I could not locate what setting you're describing when you state "a default setting is to not be using a PnP operating system which the bios then assigns the addresses." Can you clarify/help me find the specific setting in BIOS that you switched to "ON?" Thank you very much.

Hi, I'm new and am having the same problems. In my case, my laptop is only one week old and had Windows 10 pre-installed.

In my graphics card properties window, I am reading the following message:
"Device PCI\VEN_8086&DEV_0416&SUBSYS_F9391179&REV_06\3&11583659&1&10 requires further installation."

Could this be related to the problem and, perhaps more importantly, how do I complete the suggested further installation?

Sorry. I know I joined several weeks after this thread may have been considered closed, but I'd be really interested to hear if anyone has resolved this sort of problem.