Hi Baqer King3
Welcome to Microsoft Community.
Based on your description, I understand that you have an R3 3200G processor and 1650S graphics card, activated the processor graphics card from the BIOS and activated the drivers but encountered a warning event, I understand very well how you feel!
The root cause of this issue may be due to having both integrated graphics (Radeon Vega 8 from your R3 3200G) and discrete graphics (GTX 1650 Super) enabled at the same time, resulting in a conflict when switching GPUs with the NVIDIA OpenGL driver. In particular, some programs may be trying to use a different GPU and the NVIDIA driver fails to set the context correctly (DrvSetContext failed).
I will give you some suggestions and troubleshooting options to hopefully solve your problem or find out what is causing it! However, this is the first time I've replied to this question, so please understand and provide more information in your reply (pictures would be great!). Thank you very much!
Option 1: Forces the specified program to use GTX 1650 Super.
Your error log mentions cncmd.exe, which may cause the OpenGL driver to crash if the program should run with an NVIDIA GPU and it is forced to use integrated graphics. You can set this up manually:
- Right-click on the desktop and open the NVIDIA Control Panel.
- Go to Manage 3D Settings.
- Find cncmd.exe in Program Settings (if you can't find it, you can add it manually).
- Select High Performance NVIDIA Processor for Preferred Graphics Processor.
- Click Apply and restart your computer.
Please note: The exact steps may vary depending on the version of the NVIDIA Control Panel.
Option 2: Disable integrated graphics (if you don't need it).
If your monitor is connected to a GTX 1650 Super and you don't intend to use the integrated graphics of the R3 3200G, try disabling it in the BIOS:
- Enter the BIOS (press Del or F2 while booting).
- Locate Advanced > Integrated Graphics Configuration.
- Set Primary Display to PCIe (or Discrete Graphics).
- Turn off iGPU Multi-Monitor (if this option is available).
- Save and reboot.
It is best to follow the video or article tutorials provided by the motherboard manufacturer to avoid making mistakes that could lead to other problems.
Disclaimer: If you are going to modify BIOS Settings, please back up all your personal files first to ensure you do not lose data.
Option 3: We tried updating, manually installing the graphics card driver.
Since graphics cards are categorized as discrete or integrated, I don't know what graphics card you are currently using, so I will describe them separately.
- integrated graphics card.
- Update the driver
“WIN + x” and select ‘Device Manager’ -> Find the corresponding integrated graphics card device -> Right-click on the device and select ‘Update Driver’ -> ”Automatically search for Update Driver”.
- Install Generic Driver
Also in “Device Manager” -> Right-click the device and select “Remove Device” (make sure “Remove Driver” (if any) is checked -> Restart the computer and the system will automatically search and install the generic driver.
- Manual Installation of Drivers
The driver involves the following cases:
(1) If it is a laptop computer, you can download the driver for the corresponding model of laptop through the brand's official website.
(2) If it is a desktop computer, you can download the driver for the corresponding model through the official website of the motherboard brand.
(3) You can also download the driver for the corresponding model through the official website of the hardware manufacturer.
Please note: Please try the latest version of the driver first, if the problem still exists, we can try some known older and more compatible versions.
- discrete graphics card.
For discrete graphics cards, I personally recommend the manual installation method.
First of all, we can completely uninstall the current graphics card driver with the help of DDU tool (Display Driver Uninstaller), and then download the latest version of the driver from the official website of the graphics card manufacturer and install it.
The main reason for using the DDU tool is to prevent file and registry leftovers, which may cause driver conflicts or problems that may still exist.
Again, if the latest version of the driver still has problems, we can try to install some known older and more compatible versions.
Option 4: If cncmd.exe is a component of a specific software, you can try:
- run the software in compatibility mode (right-click -> Properties -> Compatibility -> select Windows 10/8/7, etc.).
- Check the software for updates or try running it in administrator mode.
Option 5: From the event you provided, it appears to be a Warning level event, not an Error or Critical error. It can usually be ignored if your computer and related software are not crashing, having an abnormal image, or the program is not working.
This warning is from the NVIDIA OpenGL Driver, and the DrvSetContext failed functionality indeterminant in the logs indicates that NVIDIA's OpenGL Driver failed to switch rendering contexts, but this does not necessarily cause the program to crash.
You have recently enabled the R3 3200G integrated graphics card in the BIOS and installed its driver, while your GTX 1650 Super is also a discrete card. This means that your system now has two different GPUs, but some programs may have a conflict when trying to call the GPUs, causing OpenGL processing to fail.
- If your programs, games, and system are running normally, you can ignore this warning as it is a driver-level issue that does not necessarily affect actual usage.
However, if you are experiencing any of the following problems, you will need to investigate further:
(1) Crashes or performance degradation when running certain 3D software.
(2) Flickering, stuttering, dropped frames, etc. in games.
(3) Some applications fail to start or crash
(4) Other OpenGL related errors (e.g. OpenGL context lost).
If you don't encounter any of these problems, then don't worry, this log is just background information and won't affect your daily use.
- If you want to avoid this warning, you can do what I did before, such as forcing the program to use NVIDIA discrete graphics, disabling integrated graphics, etc.
But in general this is just a warning, not an error, and can be ignored if the system is working properly. The cause may be a GPU switching problem with dual graphics cards, which causes OpenGL context assignment to fail, but it doesn't necessarily affect the program's operation.
I sincerely hope that the above information and programs will help you! Please feel free to contact me (Photos related to the question would be great!).
I look forward to hearing back from you.
Best Regards
Arthur Sheng | Microsoft Community Support Specialist