Power Dropout, WTH is this?
I wanted to post this here and close the topic, in case my solution one day helps others.
The issue was in fact nvlddmkm Error Event 14.
This error, it turns out, is not anything specific but a catch-all for anything that causes the driver to time out. This can be due to hardware failure, driver failure, firmware/software conflicts, data corruption. This appears to be why there are so many different issues out there with similar symptoms and the same message but different "fixes", all of which are actually workarounds because until you know the actual issue you can't fix it.
I don't know why I defaulted to this being a hardware issue, there was a time that I would have looked at software first. Once I was directed at software though, I tracked the specific error in my event log to the day it started. That day I had installed some software from my employer for some volunteer work I had signed up to do. That first event was actually catastrophic, but corrected itself. I didn't see any more issues directly for weeks, and after that what I did see was slow, creeping issues that did not seem immediately related (but were), getting worse over time until last week.
This software, BTW, was Citrix Workspace. A software known at one time to cause issues and conflicts with dual monitor workstations that used GPUs. That was over 10 years ago, but I'm sure we're all familiar with "It's fixed" being only partly, often barely true.
Once I realized the connection of when everything started tho, I decided on one last ditch effort. I had already uninstalled the software that was the culprit, but that hadn't fixed the issue. Something must have been left over in the system - unsurprising.
By the time I figured this out I was close to RMA-ing my card. I had done every "fix" for this out there. None worked and some made it worse.
Last ditch: Format the C drive and Reinstall windows.
I also got a new surge protector with a tiny UPS in it, 2 new Certified DP cables (was using 1 HDMI and 1 DP of suspect quality before), and completely re-did my peripheral cable management.
My system has been stable and working perfectly with no errors or warns in the evet log at all for 48 hours.
Temps are even a little bit cooler.
In my case, it was a corruption caused by software.
Always check out this possibility. Trace the events back to their first date they started and try and remember what you did that day.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now