jasper_wang Posted July 7 Posted July 7 After updating to Intel graphic version 101.6841 or later, AIDA64 crashes when accessing the Display > Monitor page, and it fails to capture the monitor information. I reported this issue to Intel, and they confirmed that the new driver blocks configurations with more than two EDID blocks. However, AIDA64 has not yet adapted to this change, which causes the issue. I have verified on both ARL and PTL platforms that the same problem occurs when using the same VGA driver version. Quote
Fiery Posted July 8 Posted July 8 On 7/7/2025 at 8:54 AM, jasper_wang said: After updating to Intel graphic version 101.6841 or later, AIDA64 crashes when accessing the Display > Monitor page, and it fails to capture the monitor information. I reported this issue to Intel, and they confirmed that the new driver blocks configurations with more than two EDID blocks. However, AIDA64 has not yet adapted to this change, which causes the issue. I have verified on both ARL and PTL platforms that the same problem occurs when using the same VGA driver version. I'm afraid we couldn't reproduce the issue on our own ARL-S test system (Asus ROG Maximus Z890 Hero motherboard with iGPU enabled) using Intel video driver version 101.6913. Please let us know what exact CPU did you use and what monitor(s) do you have connected. Edit: Meanwhile we've checked it with the same driver version of 101.6913 on our Lunar Lake test system (Asus NUC 14 Pro AI), and everything works just fine there either, no crashes at all. Maybe the issue affects only mobile processors (like ARL-H, ARL-U, PTL) and/or laptop-integrated display devices? Quote
jasper_wang Posted July 10 Author Posted July 10 On 7/9/2025 at 1:54 AM, Fiery said: I'm afraid we couldn't reproduce the issue on our own ARL-S test system (Asus ROG Maximus Z890 Hero motherboard with iGPU enabled) using Intel video driver version 101.6913. Please let us know what exact CPU did you use and what monitor(s) do you have connected. Edit: Meanwhile we've checked it with the same driver version of 101.6913 on our Lunar Lake test system (Asus NUC 14 Pro AI), and everything works just fine there either, no crashes at all. Maybe the issue affects only mobile processors (like ARL-H, ARL-U, PTL) and/or laptop-integrated display devices? This issue doesn't require an external monitor to reproduce. I'm using ARL-H and PTL-H CPUs. Could you try testing on these CPU platforms as well? Quote
Fiery Posted July 10 Posted July 10 5 hours ago, jasper_wang said: This issue doesn't require an external monitor to reproduce. I'm using ARL-H and PTL-H CPUs. Could you try testing on these CPU platforms as well? Sadly we don't have neither of those platforms. Can you please ask Intel whether the issue affects only ARL-H and PTL-H platforms, or is there any other platform we can use to replicate the issue? Quote
jasper_wang Posted July 18 Author Posted July 18 On 7/10/2025 at 3:48 PM, Fiery said: Sadly we don't have neither of those platforms. Can you please ask Intel whether the issue affects only ARL-H and PTL-H platforms, or is there any other platform we can use to replicate the issue? After confirming with Intel, this issue is mainly about “to report > 2 EDID block to OS or not”, and it should not be related to the CPU version. So, not seeing the issue means the EDID reported to OS is less than 2 EDID blocks, you can check the pass case to confirm that. Could you please help confirm this on your side? Quote
Fiery Posted July 27 Posted July 27 On 7/18/2025 at 7:59 AM, jasper_wang said: After confirming with Intel, this issue is mainly about “to report > 2 EDID block to OS or not”, and it should not be related to the CPU version. So, not seeing the issue means the EDID reported to OS is less than 2 EDID blocks, you can check the pass case to confirm that. Could you please help confirm this on your side? In order to replicate the issue, we'd need a test system with 2 EDID blocks. Do you know how to achieve that? Quote
mumak Posted July 27 Posted July 27 Lots of samples for testing: https://github.com/linuxhw/EDID Quote
jasper_wang Posted July 28 Author Posted July 28 14 hours ago, Fiery said: In order to replicate the issue, we'd need a test system with 2 EDID blocks. Do you know how to achieve that? You may need to have 2+ panels project and get 2+ EDID setting from them. I used ASUS G14/G16 can reproduce. Quote
Fiery Posted August 9 Posted August 9 On 7/28/2025 at 3:38 AM, jasper_wang said: You may need to have 2+ panels project and get 2+ EDID setting from them. I used ASUS G14/G16 can reproduce. We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works. Quote
jasper_wang Posted August 11 Author Posted August 11 On 8/9/2025 at 8:09 PM, Fiery said: We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works. Hi, we hadn't met crash problem now. but detection of panel size is wrong. It's square and different from dump by HWInfo. Is it a known issue? Quote
Fiery Posted August 11 Posted August 11 5 hours ago, jasper_wang said: Hi, we hadn't met crash problem now. but detection of panel size is wrong. It's square and different from dump by HWInfo. Is it a known issue? Please send me the EDID block of the system in email. If you have no tools to dump the EDID or don't know my email address, then please drop me a private message. Quote
jasper_wang Posted August 11 Author Posted August 11 51 minutes ago, Fiery said: Please send me the EDID block of the system in email. If you have no tools to dump the EDID or don't know my email address, then please drop me a private message. Hi Fiery, I had sent message to you, please check it, thanks Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.