Nvidia discrete graphic driver frequently been disabled from Device Manager and micro stutters during normal usage

Question

Nvidia discrete graphic driver frequently been disabled from Device Manager and micro stutters during normal usage

EX0T1C BUTT3R 0

Computer Specification

Display : Samsung Odyssey G8 OLED 34"
Motherboard: ASUS ROG STRIX X670E-I GAMING WIFI
Processor : AMD R9 7950X3D ( * Cache CCD 0 - PBO Core [ 0 to 7 ] Negative Offset 15)
RAM : G.SKILL 32GB Trident Z RGB CL36
Discrete Graphic Card : Nvidia RTX 4090 ( * undervolt - 0.975v )
Storage : Western Digital Black SN850X 2TB

Driver/BIOS Version

BIOS Version : 3881
Nvidia Graphic Driver : 610.88
Chipset Version : 8.03.25.247

Recently I've decided to do clean reinstall Windows 11 due to previously encounter way too often of computer crashing to blue screen and bugs throughout the years of updating etc. But even starting out from fresh, I'm experiencing severe issue that system have symptoms such as micro stutters when during normal load usage (eg. browsing Chrome or open file) or even when the system was idle.

Occasionally during bootup/restart sometimes it will just boot up into integrated graphic and the motherboard status white LED was kept on which indicates no display signal received from discrete graphic.

Furthermore, the discrete graphic driver kept on been disabled and doesn't resume on displaying image on screen. In result, I've to connect a HDMI cable onto motherboard in order to use the integrated graphic to get display signal and verify the discrete graphic driver has been grey out on Device Manager without any error indication.

The symptoms above mentioned were regularly happen time to time. I've done some researched that one of the Windows Update (KB5089573) have known issue which disrupt the handshake process of display signal from graphic card to a monitor, so I'm not sure that is one of the culprit issue.

If possible I would like to have someone from Microsoft technical team who could help inspect maybe the minidump file what's the root cause, as currently I've run into a wall on where should I look at to resolve the issues.

0 comments

1 answer

Your answer

Answer 1

David-M 127.5K Independent Advisor

Hi. I'm David, and I'm happy to help you.

Just to confirm: What method did you use to clean install Windows? Did you perform a clean installation using installation media (USB flash drive), completely erasing the system drive before reinstalling? Or did you reset the PC, removing everything?

Also, please share the minidump files.

These files are in C:\Windows\Minidump.

(If you don't have a Minidump folder, check if it is in the plural Minidumps.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

Looking forward to your reply.

EX0T1C BUTT3R 0 Reputation points

2026-08-15T04:21:29.84+00:00

Hello David,

Yes I've perform the clean installation with installation media and fully reformat (include partitions) my entire system storage drive and start over with the Windows installation process.

Just a quick add-on information on top my post, my RAM has been enabled with EXPO profile that initially runs on 6000MT/s , but now I've dialed it down to 5600MT/s as I suspect the RAM has in a point of certain degradation.

Here's the minidump file you're requesting for and much appreciated you for the help on looking into the issue, thanks again~

Minidump File

https://1drv.ms/u/c/d3c4a0a683103fd3/IQAan8Q62c-xS4mCy5Mu5grXAWKj-eNbZamhfWzOP8w-zeU
David-M 127.5K Reputation points Independent Advisor

2026-08-15T13:56:22.72+00:00

Thanks for the details:

The minidump file confirms a VIDEO_TDR_FAILURE (116) crash caused by the Nvidia driver "nvlddmkm.sys". This error occurs when the graphics card stops responding to Windows and fails to reset within the timeout period.

Since you have already performed a full clean installation of Windows 11, corrupted driver remnants are very unlikely to be the cause. In scenarios like yours, error 116 is frequently triggered by power state voltage drops.

The most likely culprit is actually the GPU undervolt (0.975V), and possibly the -15 CPU Curve Optimizer. Undervolts can pass heavy stress tests with ease, but they frequently crash during light tasks like browsing Chrome when the card switches power states, and the voltage dips too low. When that happens, the GPU loses connection with the PCIe bus, triggering the 116 error and disabling the card in Device Manager.

I'd suggest reverting your RTX 4090 back to stock settings (using whichever app you used to undervolt it, and setting the CPU Curve Optimizer back to default in the BIOS for now.

Feel free to ask any questions you may have.
EX0T1C BUTT3R 0 Reputation points

2026-08-17T02:33:02.7933333+00:00

Noted, I'll tryout revert all the undervolt configuration to default and by just running the system like I normally would in light and heavy load scenarios.

Anyway thanks again to you for the suggestions. If any further finding came up while after the adjustment revert back to default, I'll try list out the details what's been encountered.
David-M 127.5K Reputation points Independent Advisor

2026-08-17T12:03:48.04+00:00

Glad to help.

If you have any questions, don't hesitate to ask.
EX0T1C BUTT3R 0 Reputation points

2026-08-20T12:44:17.1566667+00:00

Hello David,

Here's an updated based on previous mentioned which done revert all the voltage adjustment to default.

I was still experiencing the symptoms of sudden frozen screen while just browsing Chrome, then the system discrete graphic disabled itself and switched to integrated graphic which I've to connect the HDMI cable on motherboard to get display signal and sometimes doesn't have response.

Or the system just crashed and generate both minidump as below provided in same day. Anyway, I'd plan trying to install an older known stable version of Nvidia graphic driver instead of the latest one and see whether it would behave in the same way as current.

Although my issue wasn't fixed completely but I'm do appreciate getting from your help.

Minidump File

First minidump
https://1drv.ms/u/c/d3c4a0a683103fd3/IQDmA-6tdRarQqUrccFChlpjAYrocaO80KJhm1TEKE_pAnw?e=ZQsMVz

Second minidump
https://1drv.ms/u/c/d3c4a0a683103fd3/IQA3Z8ySX-i3RJ56DRphR5lvAS4etGBtshwE6DVNRmdilPI?e=AQ26Cl