This well-known "nvlddmkm.sys" issue is really taking a toll on your mental state!
This well-known "nvlddmkm.sys" issue is really taking a toll on your mental state!
Thanks for the update. I plan to run a full kernel dump if any problems persist.
About Symcrypt – I haven’t come across it before, but from my brief search it seems to be something commonly integrated into Windows.
https://techcommunity.microsoft.com...main cryptographic,Stack HCI, and Azure Linux
I believe certain applications on your computer have installed these libraries and kernel files possibly to connect with Azure. These aren't typical installations after a Windows setup. I don't notice any unusual features on your machine.
I plan to perform a fresh Windows installation today because a new NVMe drive is available. I’ll use the Windows Media Creation Tool to create a bootable USB, and unless updates are included, I’ll pause any updates once installed. For the rest, I’ll restrict installations until I’m confident about stability for easier troubleshooting. It’s interesting how I can list all the software I’ve installed.
It's a good idea to try it thoroughly using only Windows, with all updates applied and all drivers enabled. Many users often perform a full reinstall, including third-party components, which can sometimes resolve the issue.
has been attempting to restrict certain elements, yet some items will inevitably be required. To date, I've updated every component in this setup to refine it, switching from Nvidia to AMD for the GPU and starting from scratch today. I'm proceeding with standard troubleshooting procedures. Hopefully, this is the final attempt!
Instead of all at once, start with Win and check its stability. After that, add one program at a time, ensuring Win remains stable. If problems reappear, you'll identify the specific change that caused the issue.
So little update.
I think its done. I think its all good. Been running with new hardware and everything so far is all good. still going to take it slow setting it all up software wise to keep tsting but yeah think its done.
Now the sad part is i know someone else is going to have this error and they are goign to be like me and googling and reading everything I can on it trying to fix it myself.
This thread will be found and it may not even help them as I didnt 'fix it' i changed to AMD GPU lol ---
Man this 'little upgrade/case swap' really snowballed and I've ended up with a 100% new PC. Only thing from old PC in it is one of my old NVMEs but I still have a brand new NVME as well.
Oh well, thanks for everyones help. Much appreciated.
This is actually a valid fix as well.
Usually it happens with RAM, where it works butter smooth in 2nd PC but throws errors in 1st PC. And that - without any apparent reason since RAM should work fine in all compatible systems.