Hello,
I am having a similar issue with nvlddmkm driver. I've been getting this problem since end or start of summer 2023. This issue doesn't appear in several games I have, but it does in some, which I, for the most time play on. Commonly, it would trigger TDR, which turns my screen black for several seconds and recovers. Sometimes the application just crashes. I've also got 2 BSODs with "VIDEO_TDR_FAILURE" in almost a year. Unlike many people, I don't seem to find any artifacts appearing on my screen while playing games. In other tasks other than gaming I get no problems at all.
I get different errors on Event Viewer depending which game I am playing on, but this is the latest one I've got:
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video8
Error occurred on GPUID: 100
The message resource is present but the message was not found in the message table
I have to remind that I am using a Laptop with an iGPU and dGPU.
What I suspect might be the cause of this problem is due of bad power management, as my laptop is not directly connected to the wall.
A solution, which I have found, but annoying for demanding games, is to underclock the Laptop by putting it on "Performance" mode in Armoury Crate.
"Turbo" mode, which would be the highest mode available for me, was always stable for my laptop and kinda frustrates me that it doesn't anymore on the specific applications.
Anyways those are my specs:
Laptop: ASUS TUF Gaming Laptop FX706HC
OS: Windows 11
CPU: i5-11400h @2.60 GHz
RAM: 32 GB 3200 MHz (was 16gb before)
iGPU: Intel UHD Graphics
dGPU: RTX 3050 4GB Mobile
As its the 20th of April 2024, I have no idea what changes I have done to my computer before this issue first appeared.
Another thing before I end, this driver issue first appeared in 2021-2022, in the same year period I got my laptop, but it was rare for me at that time.