Jump to content
AIDA64 Discussion Forum
Koljasha

Bug in OpenGL in 5.50

Recommended Posts

Hello everybody!

Sorry for my English - I use translator.

On my computer version 5.50.3600 incorrectly displays the information on the OpenGL. Previous version 5.30.3500 displays all correct.

Reports made the difference in a couple of minutes. On your computer, I have not changed anything.

 

In attach reports two versions.

If you need more complete reports - write.

Report_extreme_5.30.3500.txt

Report_extreme_5.50.3600.txt

Share this post


Link to post
Share on other sites

We haven't changed anything about the OpenGL module, so it should work similarly across the two AIDA64 versions you've tried. Try to reinstall AIDA64 v5.50, restart Windows, and it may just help.

Share this post


Link to post
Share on other sites
I confirm the exact same issue.

 

Latest version (5.60.3700) shows wrong OpenGL information. I spent an entire day to figure out why I had only OpenGL 1.1 support, when I tried other tool and realized it might be an Aida issue.

 

Aida64 5.30.3500 and GPU Caps Viewer shows the information correctly.

Share this post


Link to post
Share on other sites

I confirm the exact same issue.

 

Latest version (5.60.3700) shows wrong OpenGL information. I spent an entire day to figure out why I had only OpenGL 1.1 support, when I tried other tool and realized it might be an Aida issue.

 

Aida64 5.30.3500 and GPU Caps Viewer shows the information correctly.

We've never noticed that as an issue on our test systems so far. Please let me know what video card do you have, which Windows version do you have installed, and the video driver version you've got installed.

Share this post


Link to post
Share on other sites

We've never noticed that as an issue on our test systems so far. Please let me know what video card do you have, which Windows version do you have installed, and the video driver version you've got installed.

 
Some information about my system:
Windows 10 Pro (10.0.10586)
Intel® HD Graphics (Arrandale)
Video driver 8.15.10.2993
 
It is the driver from Intel site, but the same happens with the windows update driver.

Share this post


Link to post
Share on other sites

Some information about my system:

Windows 10 Pro (10.0.10586)

Intel® HD Graphics (Arrandale)

Video driver 8.15.10.2993

 

It is the driver from Intel site, but the same happens with the windows update driver.

Thank you. Are you using a 32-bit Windows or 64-bit?

Share this post


Link to post
Share on other sites

Previous AIDA64 versions didn't have the compatibility / supportedOS tags in the application manifest. We've had to add them to properly support Windows 10. However, by adding them to the manifest, it seems Windows drivers behave differently. Apparently Intel's legacy video drivers cannot handle such situations. We've checked, and it's not just AIDA64. The latest version of OpenGL Extension Viewer simply crashes when you start it under 64-bit Windows 10 with a Clarkdale IGP :(

Share this post


Link to post
Share on other sites

Same problem with Sandy Bridge IGP.

 

OS: Windows 10 Home Single Language x64 (10.0.10586.164 (Win10 TH2))

GPU: Intel Sandy Bridge-MB - Integrated Graphics Controller (MB GT1)

Driver version: 9.17.10.4229

 

AIDA64 5.70.3800 reports OpenGL renderer as "GDI Generic".

 

Regards,

Nelson

Share this post


Link to post
Share on other sites

Same problem with Sandy Bridge IGP.

 

OS: Windows 10 Home Single Language x64 (10.0.10586.164 (Win10 TH2))

GPU: Intel Sandy Bridge-MB - Integrated Graphics Controller (MB GT1)

Driver version: 9.17.10.4229

 

AIDA64 5.70.3800 reports OpenGL renderer as "GDI Generic".

 

Regards,

Nelson

Yes, we're aware of that. It's caused by a bug in Intel's legacy Windows 10 video drivers. We haven't yet found a way to get around the issue on our end :(

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Similar Content

    • By Soul--Reaver
      System:
      Asus Sabertooth Z77
      Intel 3770K
      Nvidia Geforce 1070
      Logitech Keyboard G510S
       
      Aida64 version: 6.25.5400
       
      I'm using the LCD in my keyboard and Aida64 to monitor certain system values.
      I've noticed that the CPU util percentages are not correct on the LCD display.
      The most obvious is that when the system is completely idle (CPU util.png), The LCD will never show a lower number then 28% for CPU7 Utilization (LCD CPU util.png) on the LCD.
      The other numbers are also weird or incorrect but that is more of a feeling i have. The other CPU utils feel weird because i never see 1% or 2%. It's always 10%, 11%, 12%, 14%, 22%, 28% etc. but never below 10% except 0%
      As shown in "CPU util.png" Aida64 is capable of getting the correct percentages, it just does not show them on the LCD display in my keyboard
      Kind regards
      Swen Kruiper


    • By sea
      Hello Sir,
       
      Would you please help to confirm if any AIDA64 logging compatibility issue with AMD Renoir platform (UMA)?
      Is it possible to solve by AIDA64?
      Thank you.
       
      We found high F/R BSOD or hard hang with 0xEA or 0x116 when running Burnin with AIDA64 logging or idle for a period of time after Burnin 8hrs pass with AIDA64 logging on AMD Renoir platform. 
      After confirmed, only AIDA64 logging for a period of time can reproduce, no need to run other APPs.
      And ever found BSOD 0xEA just when AIDA64 was detecting sensor information.
      Steps and log files of hang with dump 0x116 are as the attached files for the reference.
      Full dump please refer to download link: https://wetransfer.com/downloads/b30b6b2d51919809840bb14f8681e86d20200814161731/ccd94a25b5779c27897a6bdf19d921b720200814161833/3e7b99
       
      Other checked:
      1. BURNIN+AIDA64 log_update frequency 1s: Fail
      2. BURNIN+AIDA64 log_update frequency 10s: Pass
      3. Furmark+AIDA64 benchmark: Pass
       
      AIDA64: 6.25.5400.0
      OS: Win10 20H1
      AMD platform: Renoir FP6 UMA
       
      AMD's feedback:
      Found PCI Configuration Space that BAR5 is empty when BSOD 0x116 occurred. But, GFX driver should not save and restore PCI configure.
      Not sure why AIDA64 tool could be save/restore PCI configure?
      AIDA64 log steps.7z AIDA64_3.5hrs_hang_0x116_minidump.7z
    • By Moarty
      The CPU Temperature on the AsRock B550M Steel Series is incorrectly reported.
      Ryzen Master reports 86C while AIDA64 reports 46C
      MSI AfterBurner (RTSS) reports it correctly.
      I know its a brand new chipset, I'm not worried about it, just wanted you to know

    • By Erm Ermi
      Hi all, I created a new pc with GEFORCE GTX 1650 SUPER VENTUS XS OC graphics card but when I start aida64 in the gpu section it tells me that it is a GEFORCE GTX 1650 SUPER AERO ITX OC. I just wanted to report this little bug hoping it will be fixed in the future. thanks and good job.
    • By TimFx
      AIDA64 is no longer functioning properly. causing system crash
      windows shell experience stop responding
       
×
×
  • Create New...