Koljasha Posted November 13, 2015 Share Posted November 13, 2015 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 Quote Link to comment Share on other sites More sharing options...
Fiery Posted November 20, 2015 Share Posted November 20, 2015 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. Quote Link to comment Share on other sites More sharing options...
felipe_app Posted January 19, 2016 Share Posted January 19, 2016 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. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 19, 2016 Share Posted January 19, 2016 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. Quote Link to comment Share on other sites More sharing options...
felipe_app Posted January 19, 2016 Share Posted January 19, 2016 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. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 19, 2016 Share Posted January 19, 2016 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? Quote Link to comment Share on other sites More sharing options...
felipe_app Posted January 19, 2016 Share Posted January 19, 2016 Thank you. Are you using a 32-bit Windows or 64-bit? Windows 64 bits. Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 20, 2016 Share Posted January 20, 2016 Thank you. As it turns out, this is a bug of Intel's Windows 10 video drivers. We've run into the same issue than this gentleman: http://stackoverflow.com/questions/34676697/embedding-manifest-into-the-application-binary-breaks-opengl-2 Quote Link to comment Share on other sites More sharing options...
felipe_app Posted January 21, 2016 Share Posted January 21, 2016 That's interesting. Thank you for the feedback. Any idea why does it work with Aida64 5.30.3500 version? Quote Link to comment Share on other sites More sharing options...
Fiery Posted January 22, 2016 Share Posted January 22, 2016 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 Quote Link to comment Share on other sites More sharing options...
nelsonhf Posted March 25, 2016 Share Posted March 25, 2016 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 Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 25, 2016 Share Posted March 25, 2016 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 Quote Link to comment Share on other sites More sharing options...
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.