- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
System Used: Asus K501UX
CPU SKU: i7-6500U
GPU SKU: HD Graphics 520
Processor Line: U-Series
System BIOS Version: K501UX.209
CMOS settings: 512MB (RAM assigned to built-in integrated Graphics)
Graphics Driver Version: 20.19.15.4380
GOP/VBIOS Version: Intel Video BIOS (No version stated)
Operating System: Windows 10 64bit
OS Version: 1511
API: N/A
Occurs on non-Intel GPUs?: N/A
Steps to Reproduce:
1- Set Screen power-off timer to 1 min. to 10 min.
2- After the Screen turns-off try to activate it again with touch-pad or keyboard input
Expected Results:
1- On The latest driver (v.4380): The screen does not turn on, but gives a black output with the backlight of the LCD apparently on. When coming out of suspend, only the mouse/cursor appears on the screen and no other elements of the operating system are visible including a cntrl-alt-delete prompt. In my point of view this confirms it is a driver issue. Turning off the Screen and on again through dedicated function keys MAY turn it back on (at random).
2- On older drivers ex. (v.4424): The screen turns on sometimes and fails completely to turn-on at others, but it will always turn-on properly when coming out of suspend. Also turning off the Screen and on again through dedicated function keys MAY turn it back on (at random).
3- When intel's driver is DISABLED (from the Device Manager), the screen will ALWAYS turn-on immediately and consistently whenever a keyboard or other input is given to the computer.
Additional Information:
I Was suspecting a hardware problem, but that was completely ruled out after I disabled intel's driver and found that the problem was resolved, although that is not a possible solution despite the presence of another Graphics adapter on the system because the screen is directly driven by the built-in card.
Thanks.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Omar,
We are aware of this issue and working on a fix. I don't have an ETA on when we will fix however.
-Michael

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page