See that’s the kicker, windows has so many “are you sure” pop ups about stuff that most people just click through them without reading the fine print. People get desensitized to it and just ignore them, or maybe even they just assume microsoft is trying to sell them on a feature they don’t care about.
And in this case it didn’t save the files to the trash can, I imagine because it was synching local files with what was in one drive. Not the user deleting local files.
I had a colleague at work that had to redo several days of work because of the one drive thing.
The long and short of it is that they noticed that their connection was being super slow, opened up task manager to see if anything was eating bandwidth, saw one drive, went it it, correctly diagnosed that it was uploading files to it and eating up bandwidth, and then deleted all the files in one drive to stop it.
One drive decided that this meant they wanted all the local copies of the files deleted as well. Like, on the one hand, not the correct way to stop that behavior, but also like, the kind of thing a lot of people would try, and it then deleting all the local files in turn is an unintuitive outcome.
Just down load more ram capacity. It the button right under the down load more ram button.
If the game was crashing to desktop, it was probably not a graphics card thing, but that you were running out of ram and the system was just automatically killing the program when that happened. That’s a system stability thing, it prioritizing the needs of the system and desktop over a program so as to prevent the whole system from crashing.
The easiest solution to that is to increase the “swap” size (IE a bit of storage that gets set aside to act as back up memory). That is a system level thing, but it’s not really a big deal to change.
If you were getting to the command line, Linux was running, although, if it was just the command line then it may have been an issue with the desktop or window manager not starting. And if it was an issue with the desktop or window manager, then I could see changing some boot loader settings fixing that. Like, making sure the boot loader automatically starts the desktop when the computer boots. not sure how you got from messing with graphics card to the system only booting in command line, but, shit happens. I’ve broken my system in weirder ways while pulling at the guts.
By switching from cinnamon to XFCE desktop you may have solved the issue with the game crashing simply because you had more memory available, as XFCE is a much lighterweight desktop.
If the games was slowly slowing to a crawl before freezing up completely but not outright crashing to desktop, that could have been an issue of running out of video ram for the the GPU, I’ve had that happen with helldiver’s 2. I don’t remember exactly what I did to fix that, something with the launch options that affected the graphics settings or capped the frame rate I think. Not sure how changing between desktops could have fixed that though.