jasper_wang Posted Monday at 06:54 AM Posted Monday at 06:54 AM 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 Tuesday at 05:54 PM Posted Tuesday at 05:54 PM 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 Thursday at 02:02 AM Author Posted Thursday at 02:02 AM 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 Thursday at 07:48 AM Posted Thursday at 07:48 AM 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
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.