Thank you for contacting Intel Communities.
Can you please provide the following information to better assist you?
Default level information for reporting Graphics issues and the reports listed on the thread.
I hope to hear from you soon.
I'll give you the descriptive info that is wanted.
The diagnostics files have serial numbers and network information in them. I'm not uploading those publicly online. If you want them provide me an e-mail address to send it to, or other means of privately uploading.
I'd suggest this is a firmware / low-level hardware issue given it happens on both Windows and Linux.
Answers (N/A if not applicable)
Provide a detailed description of the issue
When the PC has instructed the monitor to go to sleep it’ll initially turn off. But then intermittently the backlight will turn on, it will display NO SIGNAL, then immediately the backlight turns back off again.
This is through a HDMI connection.
Seems to happen regardless of operating system. Observed under Windows 10 and Ubuntu Linux 17.04.
Other people have complained about this issue previously with HD4600 graphics:
Please place an X to the right of the option showing how often you see this issue using specific steps. (Ex: 'Every few times a game is started it flickers.' <- This would be "Often")
Always (100%): X
Very Sporadic (<20%):
Brand and Model of the system.
Custom-built. Uses Gigabyte H87N-WIFI motherboard, Intel Core i5-4570S CPU.
Hybrid or switchable graphics system?
ie Does it have AMD or NV graphics too?
No – only Intel HD4600.
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
EFP – AOC Q2781PQ
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Any HDMI cable.
Hardware Stepping (see note1 below).
Graphics is Rev 6.
Operating System version (see note2 below).
Windows 10 x64 Version 1703 (OS Build 15063.250)
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
SW or Apps version used to replicate the issue.
Windows is all that is needed.
Single display, clone, or extended (see note2 below).
Display resolution & refresh rate setting of each display (see note2 below).
2560x1440 @ 60 Hz
AC or DC mode, i.e. is power cable plugged in or not?
AC mode – this is a desktop computer.
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
- In Windows ‘Settings’, select ‘Power & sleep’, set ‘When plugged in, turn off after’ to a specific amount of time.
- Wait until monitor turns off.
- Watch monitor. Eventually backlight will turn on, it will display NO SIGNAL, then backlight immediately turns back off. This could happen quite quickly, or you may have to wait 20 minutes to see it.
When the PC goes to sleep, the graphics controller will cut any video signal off, this is why you keep on getting the "No signal" message. The issue is more related to the monitor configuration other than issues with the graphics driver, this is why it happens with both Windows® 10 & Ubuntu.
You may want to check with the monitor manufacturer to see what is the expected behavior of your monitor, in addition, you can check if you have the latest .inf for your monitor (contact AOC for further information).
I hope this information helps.
Yes - I contacted the local AOC service/support office. They just replied asking for a serial number. Never heard anything at all after that.
Monitor .inf is the latest I could find.
I don't get the impression the monitor is supposed to do this. The behavior isn't consistent.
Thank you for the update.
Please let me know if you get any news from AOC, as you mentioned, this behavior didn't happen with your previous monitor, so this could be an issue with the new one other than issues with the graphics controller.