Access violation error when toggling OSD (Extreme v6.30.5500)

[Nanomusheens]

I have attached a screenshot of how it looks normally (second attachment), and what happens when I turn the OSD off then back on again (first attachment). I have to completely exit the program to fix it. Already tried uninstalling and reinstalling it. I have been unsuccessful at finding a solution through searching, unless I missed something.

When it works, it has the blue background, but when the OSD crashes, it just has a solid black background with whatever i have set as the top item in the OSD window. The memory addresses are different every time, of course, but it always references AIDA64.exe.

I sometimes have to toggle it due to if I make any adjustments to the layout, like removing one of the lines, the information stays there even though the line was deleted and whatever got moved up also (I removed the CPU fan speed line in the third attachment, but it still shows the numbers in orange under the CPU Core voltage readout). I have to toggle the OSD on and off to fix it, but then that introduces the access violation bug.

Windows 10 Pro 20H2 (Windows Insider, if it matters). System specs in second attachment.

[Fiery]

On 11/29/2020 at 7:25 AM, Nanomusheens said:

I have attached a screenshot of how it looks normally (second attachment), and what happens when I turn the OSD off then back on again (first attachment). I have to completely exit the program to fix it. Already tried uninstalling and reinstalling it. I have been unsuccessful at finding a solution through searching, unless I missed something.

When it works, it has the blue background, but when the OSD crashes, it just has a solid black background with whatever i have set as the top item in the OSD window. The memory addresses are different every time, of course, but it always references AIDA64.exe.

I sometimes have to toggle it due to if I make any adjustments to the layout, like removing one of the lines, the information stays there even though the line was deleted and whatever got moved up also (I removed the CPU fan speed line in the third attachment, but it still shows the numbers in orange under the CPU Core voltage readout). I have to toggle the OSD on and off to fix it, but then that introduces the access violation bug.

Windows 10 Pro 20H2 (Windows Insider, if it matters). System specs in second attachment.

If it's possible, please send us your AIDA64.INI file in order to let us try to replicate the issue by having the same OSD configuration as yours.  If you cannot attach it to a post here or you would rather send the file in email to us, please let me know in private message.