Desiderius Price

Your reasoning makes perfect sense.  Unless you loathe gambling, if you stop in a casino and you start gambling, it’s really easy to lose track of time, though the 51 hours you cite is rather extreme.  Then again, most if not all records are an extreme of one form or another, for good or ill.

While I ended up with something else (way better), yeah, always fun what you do come across.  Casinos are designed to help you lose track of the time, to keep playing.  First time to Vegas, I intended to gamble, but was actually put off by all the glitz, so I didn’t.  Opted for a show instead & the star trek experience.

All things considered I think you made the better choice. Last time I went in if it wasn’t for my phone alarm I set before hand I’d been there for more than a couple hours.

Overall, this machine has been very stable, rock solid, to the point that I’d only have to reboot due to power outages (ie not on battery backup) or kernel/driver updates.  That’s why it was odd to be in a position to have to reboot daily/hourly when I was used to 60/90 days.  Fingers crossed the driver downgrade works, lets me defer pricey upgrades.

If your computer started acting up without you doing some other change to it first, I wouldn’t have my hopes raised too high.  And if the problem stuck around on your main computer after a card swap, especially if the removed card worked on your other machine (you never said,) then I would be looking at something on the main system board.

If you did a software patch or driver update to the O/S recently, rolling that back will hopefully roll the problem away.  Otherwise, hope for something “cheap and stupid,” like a memory module or different accessory card starting to go bad and impinging on system resources needed by the video card for the video to work correctly.

Good luck, whatever it turns out to be.

Luckily, it did start acting up after an update (which IIRC included video drivers).  As the notes mentioned g-sync, and my issues had sync issues in them when piped through my KVM, my shrewd guess is that it was a bad driver (or something not properly configured).  So, downgrading the drivers back to the old ones will likely fix it (at least for now).