Laptop monitor won't wake after sleep when updating intel gfx drivers.

I have a asus ux305ca. Has a gma 515. Latop comes with windows 10 x64. If i update the gma drivers, either manually or via windows update (insider builds which includes an updated driver). The machine will work fine, but after sleep and you open the lid, the monitor won't wake. You can however install the older driver asus has on their website which will restore functionality.
Is this a bios problem or what exactly is not compatible with the newer intel drivers?

Same computer, same problem. After windows automatically updated the computer today the screen won't start after the lid has been shut, but the computer itself starts.

I rolled back the system to a restore point, and it worked fine. But then I re-intalled the newer intel driver (154022.4424) and the same problem arises. I also tried installing a beta driver (154022.4444) but no luck either. I will now try installing an older driver i found on intels website (154010.4300).

If you reinstall the driver from the asus site, it will start working again.
But, if you restore the computer to factory default, it will keep the driver. So that does not fix the problem. In the beginning i didn't know what was wrong, so i phoned asus support which said it was a hardware issue and i need to get it replaced.

The one i have now is my 6'th replacement, before i my self figured out what the problem was.
I have also written asus national and global about the problem, no response. And i've written to the national asus team before where they responded quickly.

The big problem is that preview builds are including a newer driver, which means it'll not be long before they roll out to the average user. Eventually everyone with a ux305ca will have this problem.
I recently wrote back to them that i took their silence as a nope, and that i would most likely get this refunded.
Then go for a asus tp301ua instead, it's only 67€ more and most likely won't have this problem as the i5 is more widespread than the m3.

But i still don't quite understand where the complication is.

I think I got it figured out yesterday, as installing the older intel driver from 2015 resolved the issue. I've only had this machine for a week though. Hopefully intel will fix the issue soon.

Most likely they will not, i've had 6 since February.