I have bought AsRock DeskMini 110 Barebone system. It includes the components below.
H110 chipset STX Mainboard
Intel i7-7700T CPU
Samsung DDR4 17000 8GB x 2ea = 16GB
Samsung 850 Evo SSD 500GB + 1TB = 1.5TB
Windows 10 Pro 64bit
I've installed the driver v.184.108.40.20671 for the HD 630 graphics. and every time my PC woke up from Sleep Mode, the monitors(I use dual monitors. The one by HDMI, and the other by DP) showed abnormal broken and black screen. It was OK if the PC woke up from Hibernation Mode. This problem happened only when it woke up from Sleep Mode.
I inquired of AsRock Distributer about this matter. They didn't sure about the cause of the problem, but they exchanged a mainboard to new one. But this issue was not solved at all.
So, I tried another way. I deleted the graphic driver and installed the older version v220.127.116.1142. Then the problem has dissapeared!!! It now wakes up from Sleep Mode normally!!!
It seems that latest driver vv.18.104.22.16871 has some bug about Sleep Mode. Could you please check this issue?
Try 22.214.171.12478 from https://downloadcenter.intel.com/download/26836 Download Intel® Graphics Driver for Windows* [15.45]
(Both same branch as 126.96.36.19942)
Thank you for your reply.
Today, I did simple experiments with several versions of drivers. The result is in the below.
188.8.131.5271(the latest version) : Problem occured.
184.108.40.20649(the driver automatically installed during Windows 10 RS2 update) : Problem occured.
220.127.116.1127(downloaded by the link you gave me) : It was OK. (I don't know why but this was not found on the Intel's download page)
18.104.22.16878 : It was OK.
So, I presume that this bug was occurred at some time after version 4727. I hope Intel get to know about this issue and fixes this in their next drivers
Actually i think you have an issue with the different branches.
21.x.x.x = 15.45 works for you
22.x.x.x = 15.46 fails on your rig
If you want to narrow the issue, both of the following drivers should fail:
22.214.171.12429 from https://downloadcenter.intel.com/download/26941/Intel-Graphics-Driver-for-Windows-15-46-?product=989... Download Intel® Graphics Driver for Windows* [15.46]
126.96.36.19918 from http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2017/07/afd2d2be-00a0-4bc4-8ada-21... http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2017/07/afd2d2be-00a0-4bc4-8ada-21...…
Install Microsoft's driver via "have disk method" as described at:
ignore prolog about MS surface, treat CAB like ZIP
Oops, I did the test with the driver version 4729 yesterday, but I omitted to write it.
Yes, 4729 had the problem too.
I didn't test with 4718 yet, and although I don't know the details about the Branch, I think it is true that you said about it.
v188.8.131.5242, v184.108.40.20678, v220.127.116.1127, all the drives I have tested which have 21.xx.xx.xxxx in their version number have no problem.
v18.104.22.16829, v22.214.171.12449, v126.96.36.19971, all the drivers I have tested which have 22.xx.xx.xxxx in their version number cause the trouble.
Now, I'm using 4727 driver but I would like to install latest driver with no issue.
INTEL!!! ARE YOU WATCHING THIS? YOU HAVE TO LISTEN CAREFULLY WHAT STEFAN3D SAID!!!
I understand you are having graphics issues when the computer wakes up from sleep mode.
Let me apologize for any inconvenience this issue may be causing to you.
We are currently investigating this issue. We have created an internal Bug ID 1406457227 for this behavior. As soon as we have more information we will post it in the following Community thread /thread/116427 https://communities.intel.com/thread/116427
Some customers have reported the issue goes away when they install latest BIOS. If after installing latest BIOS issue persists the workaround available at the moment would be using driver v188.8.131.5242.
I recommend either posting your inquiry in the other thread or use the "Follow" option that is on the upper right corner in order for you to get updates.
I think Intel learn to fix their own problem. Waiting for a bios update from all manufacturers for all their motherboards or laptops is absurd!
The bug appeared 4 months ago and no news about a fix other than the brilliant debuggers of Intel cannot reproduce problem.
I didn't know this problem has been that long.
And... Did Intel really say so? Then, don't they even have a intention to solve this matter?
It's so disappointing if it is true...
I would like to confirm that Intel is investigating this issue.
Please refer to this thread:
This is where we will be posting all news and updates concerning this situation.
I'll proceed to lock this thread in order to keep all reports under the same thread for increased visibility.