Getting more and more frustrated...bought some new components (CPU, MB, RAM, Graphics Card) for my computer back in August and let my vendor install them together with Win 10.
Three days later, after completing program installation and testing my joystick, my HDD crashed (don't know if it was a head crash or an electronics problem). Two words - Murphy's Law, as my latest backup was saved on that particular disc.
Still waiting for a result if my vendor can recover some of the data, he hasn't found the right model for parts swapping yet. No comment on that, I'm fully aware that this is a no-go in IT business
I only did that because of time-saving - my internal HDD was faster than my external ones.
Almost two months later, namely today, I paused a game for a coffee break. That lasted only about half an hour, but when I returned, my screen was black.
First, I didn't saw that as an issue, it goes into power save mode quite fast. So I turned it on, and saw - nothing. Did a reset, worked fine in the first seconds, then some of the pixels on the desktop flashed green and the whole computer hung.
Tried different repair modes (none of them worked), a system recovery via a recovery point (didn't really work either as it hung again after the Windows loading screen) and after that, the "Save Mode".
With that, I got a low-res desktop (of course), but couldn't really figure out what was wrong with my system. I got some weird error from Sticky Notes that they couldn't be opened in that Admin account I was using, but that's it. After restarting, I ran into the same problem again.
It worked fine until the Windows loading screen, then the Graphics Card fan returned into Idle Mode and the screen gave me a "No signal" message. I'm pretty sure Windows didn't load completely either. In some cases, after the loading screen but before the "No signal" message, I see some weird white line patterns on the screen...
I really suspect the Graphics Card to be the issue when trying to do high-res calculations as the low-res desktop in Save Mode worked. It's probably not Windows, because of the same reason...