Display malfunctions after waking from sleep

[svds]

Since the Windows 10 update of OS-build 16299.19 , my Zbook displays the following screen after waking from sleep mode:

The only way to get into the notebook again, is by restarting it. 

However, when connecting an external screen, the external screen does work (meaning that it is probably a display driver issue). 

I am running all the latest driver versions of my Display Adapters and monitor. 

The BIOS is up to date. 

The issue never occurred before the Windows update, the newest update of Windows did not fix the issue.

Removing the update does temporarily fix the issue, however since Windows 10 automatically updates the OS, this is not a permanent fix (and of course shouldn't have to be). 

[GGnoRe]

I am running into the same issue, is there any help on this yet?

[Ixthnar]

Me too,

I have even tried disabling / reenabling  the laptop display dirver.  Only a restart gets the display back.

[svds]

I have found the solution to this problem, after a long search. 

It turns out that the Intel HD graphics driver version 22.x is the problem. 
Your device manager will say this is the latest version, however it is not. You have to manually update it to version 23.x. (i believe it was this link https://downloadcenter.intel.com/download/27412/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?pr...)

This will probably give you some error, saying that your chipset is not compatible. 

This in term you can fix, by going back to the default driver for Intel HD graphics (oldest one available on your pc) and upgrade to 23.x from there. 

Hopefully you get the job done, if not message me again and i'll try to help you out.

[esheafer]

---

@svds wrote:

I have found the solution to this problem, after a long search. 

It turns out that the Intel HD graphics driver version 22.x is the problem. 
Your device manager will say this is the latest version, however it is not. You have to manually update it to version 23.x. (i believe it was this link https://downloadcenter.intel.com/download/27412/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?pr...)

This will probably give you some error, saying that your chipset is not compatible. 

This in term you can fix, by going back to the default driver for Intel HD graphics (oldest one available on your pc) and upgrade to 23.x from there. 

Hopefully you get the job done, if not message me again and i'll try to help you out.

---

This was the solution for me!! Thanks for posting this, very helpful.

[AlainCX]

Hello,

thanks for the help, but I don't know exactly how to do this :

"This will probably give you some error, saying that your chipset is not compatible. 

This in term you can fix, by going back to the default driver for Intel HD graphics (oldest one available on your pc) and upgrade to 23.x from there. "

What are the steps to follow ?

Thanks !

[esheafer]

---

@AlainCX wrote:

Hello,

thanks for the help, but I don't know exactly how to do this :

"This will probably give you some error, saying that your chipset is not compatible. 

This in term you can fix, by going back to the default driver for Intel HD graphics (oldest one available on your pc) and upgrade to 23.x from there. "

What are the steps to follow ?

Thanks !

---

I didn't have that issue at, here were my steps:

1. Right-Click Start, click on Device Manager

2. Locate and Open Display Adapters

3. Right-Click on "Intel(R) HD Graphics 530" and Click Properties

4. Click on the Driver tab, confirm your driver version is 22.x (we want to go to 23.x)

5. Click the Update Dtiver button and let windows do its thing. It took my coupter about 5 minutes to finish. 

6. Optional: I rebooted after it was complete. Follow the steps above and confirm the new driver version of 23.x is there.

Enjoy!

[AlainCX]

It seems to work for me.

Thanks !

[MarkozOne]

Jesus, thank you, worked for me too ! Tried so many things. Thought it was a problem with the graphic card drivers at first. 

[RichieEye]

---

@MarkozOnewrote:

Jesus, thank you, worked for me too ! Tried so many things. Thought it was a problem with the graphic card drivers at first. 

---

Amen to that, Brothers and Sisters.