Hey there @M_a_t1! Welcome to the community! This error often comes from the driver level, here’s a post where the user resolved it (with lots of other proposed fixed/workarounds before that.)
It’s good, it’s settled. After 8 hours in all, I found what it was.
I tested and modified each NVidia settings and it was “Antialiasing - FXAA” it was on “On” and I put it on “Off”, it was bugging me in the “Window” tab and crashing .
But it’s good it works now, no bug.
It wasn’t the drivers, or admin rights. My drivers are always up to date.
Yep! It was the settings the drivers were interpreting in that case. One of the links in that thread I sent over goes over resetting Nvidia’s control panel’s default settings as well. Though the error can occur from so many different sources, I should definitely write a guide to step through of all of the confirmed ways it can occur and their fixes. Graeme’s post just goes through the least extreme (changing settings) to the most extreme (reinstalling drivers without some components).
