Some time ago, the motherboard and CPU were replaced, and the graphics card was displayed as the CPU core. Because there were a lot of programs, there was no new installation system, but under the old system. The previous programs were completely retained and patched again, and everything looked perfect.
It was not until I played Angry Birds that I found that OpenGL was not working. I suspected that it was a driver problem. Updating the graphics card driver to the latest version still failed. Google has tried countless solutions, but they don’t work. Using the GPU CAPS Viewer, the OpenGL driver was not found.
Occasionally see an article that logout users, with another account login can use OpenGL, remember there is an account, immediately logout after using another account login system, found that OpenGL is really available.
What’s the problem?This must be because the user’s configuration is different, so we export the HKCU in the two users’ registries into reg files, compare the two files with TotalCommander, search OpenGL, and find that there are more in the new registry
[HKEY_CURRENT_USER\Software\Intel\Display\CUICOM], another active reg file does not have it, so try to remove it altogether.
Start the GPU CAPS Viewer again and see that the OpenGL driver is correct, version 3.1. The problem that had troubled us for several days was finally solved.
Conclusion: After the replacement of the graphics card, the old registry key is not deleted. There are two Intel graphics card configurations in HKCU. It is concluded that the system uses the first one to initialize OpenGL, which of course fails.
It was not until I played Angry Birds that I found that OpenGL was not working. I suspected that it was a driver problem. Updating the graphics card driver to the latest version still failed. Google has tried countless solutions, but they don’t work. Using the GPU CAPS Viewer, the OpenGL driver was not found.
Occasionally see an article that logout users, with another account login can use OpenGL, remember there is an account, immediately logout after using another account login system, found that OpenGL is really available.
What’s the problem?This must be because the user’s configuration is different, so we export the HKCU in the two users’ registries into reg files, compare the two files with TotalCommander, search OpenGL, and find that there are more in the new registry
[HKEY_CURRENT_USER\Software\Intel\Display\CUICOM], another active reg file does not have it, so try to remove it altogether.
Start the GPU CAPS Viewer again and see that the OpenGL driver is correct, version 3.1. The problem that had troubled us for several days was finally solved.
Conclusion: After the replacement of the graphics card, the old registry key is not deleted. There are two Intel graphics card configurations in HKCU. It is concluded that the system uses the first one to initialize OpenGL, which of course fails.
Read More:
- Solution to the failure of ROS noetic initialization (rosdep init)
- Solution to the failure of creating bitmap with multithreaded OpenGL
- [Solved] Timeout failure when upgrading horizon DAAS from 9.0.1/20.2.0 to 9.1.0/21.1.0
- Error ns when starting VirtualBox virtual machine after upgrading kernel_ ERROR_ FAILURE
- CMDTUX_CAT:1685: ERROR: Application initialization failure
- Solve QQ startup error: Initialization failure: 0x0000000C
- Solution to display CPU over voltage error when Windows system starts
- The solution of OpenGL not displaying normally in win7 system
- OpenGL result white screen solution
- Solution / error of. Net framework 4.0 installation failure HResult 0xc8000222 solution
- Error: transfer of control bypasses initialization of: variable XXX solution
- Solution to CUDA installation failure problem visual studio integration failed
- NPM and cnpm installation failure solution
- Simple solution for node sass installation failure
- The usage of Java JUnit unit test and the solution of initialization error
- The solution of using OpenGL’s Glu Library in qt5.2 under win7
- The solution of configuring OpenGL in vs2017
- Solution to node sass installation failure
- Solution to 800b0001 failure of Windows Update
- QT running prompt failed to create OpenGL context for format qsurfaceformat (version 2.0, options qflags() solution)