- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When Windows boots, my HP 2311gt monitor is not detected on start-up. Running an Asrock Arc A380 using the 31.0.101.5333 driver using the HDMI port. Unplugging and plugging the monitor back in after Windows has booted corrects the problem, but that is quite annoying.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello JasonStern,
Thank you for posting in our communities.
Please try connecting only the HP 2311 GT and booting into BIOS/UEFI. Do you see any video displays? and please take note that in this environment there are no GPU drivers loaded, and thus it can help me isolate the issue.
And by the way, have you tried other video outputs? What about other cables or other monitors?
And did this monitor ever work with this GPU? since I would like to understand if any recent changes in the system may have triggered the problem.
We look forward to your response!
Thank you, and have a great day ahead!
Best regards,
Carmona A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The timings are out of spec when booting the display. Thus, the EDID provided to try to reproduce.
Running the Standard VGA Graphics Adapter driver works, albeit without the full functionality of the Arc A380.
There is nothing wrong with the display, cables, etc. If I downgrade to an AMD RX560, I do not experience this problem.
The real oddity is that hot swapping the display works. So, there is nothing hardware-side that prevents the Arc A380 from driving the display. But at power up, it is not correctly reading and then driving the EDID timing values. But a disconnect/reconnect resolves this.
If you have a tool to read the timing values, I can provide captures of it out of range and in range. And when I say tool, I mean more than something that reports "60Hz" - I mean the pixel clocks, h-sync, and v-sync timings when it is working versus when it is not working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello JasonStern,
Thank you so much for the response; they were all highly noted.
I will raise our case with our engineers, so please generate an SSU report to help us further analyze important details on your system, such as the OS build number, graphics driver version, errors logged in the system, etc. To generate the SSU report, please refer to the article How to get the Intel® System Support Utility Logs on Windows*. Please send us the generated SSU.txt file.
Thank you, and have a great day ahead!
Best regards,
Carmona A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Of course.
Attached is the SSU report. But please provide the engineers with the EDID I previously provided, as this appears to be the EDID not being read correctly on start-up, which leads to some default values for the pixel clock timings that the display doesn't support. And again, hot swapping resolves the issue, which indicates that there is a different code path being executed on a hot swap which works versus the monitor detection on cold start.
Thank you,
Jason
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello JasonStern,
Thank you so much for providing us with your SSU and sharing your thoughts on how we can isolate the issue. Rest assured that I will provide the EDID that you have shared with our engineers, and by the way, all the additional information that you have mentioned was highly noted.
We will now do further research on this matter and post the response on this thread once it is available.
Have a fantastic day, and thank you very much for your patience and understanding!
Best regards,
Carmona A.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any resolution here? I have almost the same defect after updating to the same verison of driver or even to newer - 31.0.101.5379
Win+Ctrl+Shift+B helps to restart graphic driver and can use it till restart. So just rolled-back for now to 31.0.101.5252 - it works without that issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@ACarmona_Intel - The display works fine in basic BIOS mode or using Microsoft's default standard VGA adapter driver. But doing that obviously disables any DirectX, OpenGL, and video encode/decode performance, which was the main point of buying a discrete GPU. The HP display is a bit older and only has HDMI or DVI (which the Arc cards do not support), and I don't feel like dropping $20 on a converter that might not resolve what is clearly a driver issue. I don't have the equipment to diagnose exactly what is going wrong, but with the latest driver, the timings being used on a cold boot are incorrect. Maybe it is failing to read the EDID? Maybe there is a bug in setting the horizontal or vertical refresh rates? Either way, it's a driver issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@strangerX1- Thanks for reminding me about the "force Windows to reset the driver" hotkey. I've only used it when things get really bad. Specifically on my former AMD RX560, which currently has its own rare issue with video decompression in certain cases when using remote desktop.
I'll try it again next time I reboot. Hope it works, as at least I wouldn't have to physically unplug and plug back in the HDMI cable. But starting Windows, then force resetting the video driver once the O/S completes its boot up process doesn't seem like a long-term solution.
The HP 2311gt does passive stereoscopic 3D, which never really took off. Thus, it isn't something financially replaceable short of VR headsets, which then breaks a multi-monitor configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Totally with you - I want a proper fix - I wasted quite a lot of my time on trying to puzzle out the issue with not much luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello JasonStern,
Thank you so much for patiently waiting on our response.
Upon reviewing your situation, it appears that the HP 2311GT display may have a compatibility concern. As this seems to be an isolated case, it might not be prioritized by our driver development team in the immediate future. To bypass this, you might consider using a DisplayPort connection, which could help avoid the LPCON chip—a third-party component used by the A380 vendor for DP-to-HDMI conversion. Additionally, reaching out to AsRock could provide further insights, as this could be the cause of the issue.
Thank you, and have a great day ahead!
Best regards,
Carmona A.
Intel Customer Support Technician

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