original quote:
Anticlimactic and somewhat embarrassing update: as some people suggested, I left it unplugged for about half an hour last night and then tried plugging it back in… and it didn’t work. So I left it unplugged for a couple of hours and then tried it again before bed… and it didn’t work. Same error light despite multiple power-cycling attempts. So I left it unplugged overnight and plugged it back in today to try some of the BIOS stuff that other people suggested… and it booted up immediately without issue.
I feel stupid about even posting this now, especially since it blew up a bit, but I was tired and irritable after a long day of work, and an ominous GPU error code wasn’t exactly the seamless plug-and-play experience I had hoped for. But I guess if anyone encounters the same error, don’t panic like I did, just let it sit for a few hours and it will somehow sort itself out. Anyway, I’m sorry for the false alarm, thanks to everyone who suggested solutions, and now I’m going to spend this weekend playing Crusader Kings until my eyes hurt.
A random bit flip in memory. Sometimes errors can be retained.
That’s a hardware issue
Yeh, but is extremely outside of any manufacturers control for consumer level gear.
For mission-critical satellites or space crafts, then it’s either a 3-way-quorum or extremely ruggedised processors specifically designed for the radiation of space (with a massive performance penalty).
It’s not something you buy off the shelf. It is a specific requirement that is built in at all levels of hardware, firmware and software.
So, if the steam machine is designed for high radiation environments then it’s steams fault.
Seeing as it isn’t, a cosmic bit flip that is actually able to impact hardware negatively is so extremely unlikely that it isn’t Steam’s issue. At all.
I didn’t say it would be Steam’s fault. Just that a bit flip is a hardware issue, not a software one.