Recent Nvidia and Windows 11 patches are leading to the resurgence of nvlddmkm problems.
Recent Nvidia and Windows 11 patches are leading to the resurgence of nvlddmkm problems.
Interesting, this seems to be a question about an unusual situation. Why is it not common for everyone to experience this?
My PC stopped booting into BIOS completely. They received the machine and saw no issues, but discovered a minor CPU fault. Despite reports of similar symptoms, they upgraded to a newer 14th generation model and updated the BIOS. Now hardware problems seem resolved. Still, it crashes during Resolve, especially with video and audio files. Windows logs show Nvlddmkm errors each time. It might be the Nvidia drivers that caused trouble, even after a clean DDU install. There could be a microcode update on the 4090 card preventing fixes. Hopefully, Nvidia will release stable drivers soon—otherwise it seems my graphics card’s audio/video components are damaged. In my view, these issues usually stem from a simple Windows setting conflict or bloated driver changes. Microsoft may have added unnecessary bloat without realizing its impact.
The latest NV drivers seem problematic, especially on older cards like the 40 and 50 series. It’s unclear what update is needed—whether it’s a Windows update, full version, or feature patch. I just installed the newest Windows 11 update with security patches, and everything worked fine; benchmark scores even improved to 4070. I didn’t change the driver, which feels like a missed opportunity from last June. It looks like Intel is behind this issue, given the persistent NV errors. A 12th-gen chip would have been safer, and using a 14th-gen Intel with a 16-pin 4090 might be better. While it’s not ideal, Microsoft drivers are currently unreliable for this hardware. You could try rolling back the driver or Windows, but I’d suggest avoiding Intel 13th/14th gen devices going forward.
The 24H2 update along with the new drivers caused significant problems. It seems a major change occurred that forced a rollback of Nvidia drivers back to older versions, still facing issues. I restored Windows 11 to version 23H2, but the problems from the reverted drivers remain, especially when using Resolve or playing video and audio. I can handle games well, but struggle with sound and visuals. Right now it's just guesswork; no one knows exactly why these errors continue despite driver updates. It feels like the software has been deeply flawed, caught in a tangled mess of registry errors that keep problems alive. I strongly dislike Windows and Microsoft—it’s so unreliable it should be considered illegal.
I’ve used Intel since the 90s because they’re more dependable for important tasks. These recent issues have pushed me toward AMD in future builds. However, I don’t like AMD much; they focus too much on raw speed and neglect real-world stability, which is often ignored. Most tech enthusiasts chase performance, but stability matters most for those managing computer systems. I’d rather avoid AMD if it makes system operation risky—like navigating a dangerous minefield that could delay projects or harm sanity.
But the situation has changed. The turns are paused, and AMD appears more stable today. I’d prefer Nvidia to also move into CPUs, possibly with a seamless GPU-CPU integration using their Blackwell chip. That could revolutionize computing. A fresh 14th-gen model with updated microcode and BIOS should work well.
The concern is whether graphics cards can update their own microcode via drivers, affecting the card’s core functionality rather than the CPU. I’m unsure if GPUs have this capability, but that’s why I’ve already reverted back to Windows 11 and Nvidia drivers—it hasn’t solved the issue.
Choosing a GPU matters. Nvidia is the best all-rounder for gaming and professional audio/video work. AMD lacks comparable strengths in filmmaking and 3D applications.
The post mentions safety concerns about connectors. It suggests reducing wattage limits or considering alternatives. The author shares their experience with an Intel X64 CPU from 2017, noting performance issues and eventual switch to a different processor. They discuss AMD's strong performance and personal use of CapCut for video editing, warning that software compatibility can affect results. Finally, they advise testing other processors or software to identify the real problem.
It relies heavily on connector quality. I own the Asus model and haven’t seen any visible damage after installations. It doesn’t fit the professional standard I need. My main job involves high-end productions, so these tools are essential. Even Adobe’s versions aren’t working, but they lack the plugins and setup I’ve developed around Resolve. The only viable choice is a system that works with it. I have a Macbook as a backup, which helps, but moving between desktops for editing or color grading is still cumbersome.
The issue seems tied to drivers or Windows behavior rather than the hardware itself. Service technicians who replaced my processor reported no problems, yet some users still face difficulties. This suggests problems are widespread but go unnoticed because most people only use their PCs for gaming. I’ve swapped to a newer chipset, yet the challenges remain confusing and frustrating.
My concern isn’t with my processor—it’s about how Windows and Nvidia interact. While some creators share their experiences online, it’s insufficient to resolve the obstacles I encounter daily.
Consider testing different options and adjustments as a common approach. For CapCut, this isn’t usually critical unless you’re working professionally—it helps identify potential problems. With DaVinci, the issue seems more hardware-related rather than software. I suspect the problem is tied to Nvidia drivers, especially older versions, making ShadowPlay unsupported. The Nvidia app often fails, and even OBS needs powerful hardware to function well. Using Steam Recording is a workaround but still has performance limits. Overall, it looks like the driver compatibility is the main factor here.
It’s been a while since I bought my Legion 5 16IRX9 about six months ago. It came with 32 GB of RAM, an i7-14650HX processor, and a 4070 8GB drive. At first everything worked perfectly. Then the updates began one after another. Nvidia drivers? Fine. New Windows updates? Yes! Why not...? Well, after two weeks of heavy gaming use, the games started closing randomly—sometimes after 30 seconds, sometimes after 15 minutes or more, but always ending abruptly. There were no pop-ups or errors. It was the nvlddmkm event ID 153. Nothing helped. I tried everything: reinstalled Windows, ran MemTest86, updated BIOS, changed drivers, even contacted a local Lenovo service because it was a new laptop. Finally, after about one and a half months, everything worked again! It felt great to play once more. Until today. That day I accidentally opened Windows Update—no, not just any update, but a driver update called Intel Corporation - Display - 32.0.101.6733. Again, nvlddmkm event ID 153 popped up. I tried everything once more, but nothing fixed it. I suspect Lenovo thinks I’m the same person who had trouble figuring out the issue before. For this problem, they just said there’s a virus and asked me to reinstall. Tomorrow I’ll look them up again for a replacement. Right now, all I have is frustration with Microsoft and Nvidia.
I understand your point, and it seems like few people seem to be paying attention. These issues definitely affect many, yet they appear so quiet. Isn't it strange that Linus media isn't addressing this? Perhaps they should investigate why it's happening, since neither Nvidia nor Windows seems responsible. All these "reinstall" fixes won't help if the problem keeps appearing everywhere. We must identify the real core of the issue. What exactly is conflicting with Nvidia? What triggers these problems? It might just be a simple mistake or oversight that needs a quick fix. People are wasting our time trying to repair their PCs when the real cause isn't obvious. Most so-called solutions are just generic advice from support lines, like "have you tried turning it off and on again." We need a proper investigation to uncover the true reason before finding a solution.