gkainz
Final Approach
Grrrrr, I HATE windows! Had a Win 10 heavy desktop/small server that I inherited and passed along to church for our security camera surveillance systems, since it had 2 2-port video cards installed and enough memory and cpu to handle managing the video. I wiped Oracle and all my stuff, brought it to church and before they integrated it into the domain, they did windows patches (no! no! no!) yeah, I get it - somebody has to patch sometime...
So, 2 of the video outputs quit, and the system defaulted to mirror display mode after patching. No amount of fussing could change anything on the displays. Rolling back to before patch fails with no valid restore point found. Great. Digging through the log files reveals memory errors so it appears that the updates failed there but succeeded enough that windows thought it was a success? Hmmm, ok, memory errors. But POST didn't show any memory errors. I handed it off to another guy who hates windows less than me to fuss with. He said he believed that the o/s was corrupted, so rebuilt it. He found indications of memory errors, so they ordered new RAM for it. Installed new RAM and had different errors. Reinstalled the O/S from scratch and patched up to point of failure, where it failed again. Finally (and I don't know or care where or how) found that a C++ driver was in conflict with the ATI video driver. Found an old ATI driver from a couple of years ago, reinstalled and the free PC is now functional again, after a week of frustration.
When I got the dirty look of foisting a piece of junk on them, all I could say was "it was working when I brought it in here!" and reminded them "there's no such thing as a free puppy."
So, 2 of the video outputs quit, and the system defaulted to mirror display mode after patching. No amount of fussing could change anything on the displays. Rolling back to before patch fails with no valid restore point found. Great. Digging through the log files reveals memory errors so it appears that the updates failed there but succeeded enough that windows thought it was a success? Hmmm, ok, memory errors. But POST didn't show any memory errors. I handed it off to another guy who hates windows less than me to fuss with. He said he believed that the o/s was corrupted, so rebuilt it. He found indications of memory errors, so they ordered new RAM for it. Installed new RAM and had different errors. Reinstalled the O/S from scratch and patched up to point of failure, where it failed again. Finally (and I don't know or care where or how) found that a C++ driver was in conflict with the ATI video driver. Found an old ATI driver from a couple of years ago, reinstalled and the free PC is now functional again, after a week of frustration.
When I got the dirty look of foisting a piece of junk on them, all I could say was "it was working when I brought it in here!" and reminded them "there's no such thing as a free puppy."