So it just happens that I’m always unlucky with the hardware in all 3 gaming desktop PCs that I’ve built over the last ~14 years that they would have this behaviour? (Bluescreen out of nowhere, without any intensive hardware usage or weird behaviour or anything that justifies triggering this)
I haven’t ran Linux on this machine yet, but I’m more likely to go for it with each passing day. I can let you know how it goes and how many crashes I get.
I don’t expect any, as I’ve been using Linux on my laptops for close to 10 years now and the only time I had a hardware problem was because I was using my old laptop as a server and its HDD died - but that’s because HDD laptops are not meant for these usage patterns, so totally expected tbh.
I find it super interesting that there is this pushback from you and the other user here saying “Windows doesn’t have any problems”, which now turns into “Ah but that’s hardware and Linux would have it too!” - How can you know?? How can you make such an apt diagnosis that it’s not a Windows-only issue with practically zero information??
Because if we are just blindly applying patterns then yes I can do the same - I’ve literally never had a running Linux system crash on me, from running it in VMs, Cloud VPSs, Laptops and even a Raspberry Pi. And in the same timeframe I’ve had more random blue screens on Windows than I can count. And I can tell you that I looked quite hard at a few of them to try and avoid triggering them. The only one I managed to figure out was that in a Laptop X USB-powered headset combo I could never start up the system with the headset connected, as if the cable was messed with and the dongle lost connection, it would immediately blue screen the laptop. But if it booted with the USB dongle disconnected and I connected it later, it was totally fine!! - Even with this crash being caused by hardware, how can you say that this is a reasonable behaviour from a “production-ready” OS? The latter behaviour tells us that it is totally possible to handle this hardware error without a full system crash, but it can happen all the same!
I honestly don’t understand what you or the other user get from being so adamant about Windows being good, or being “not that bad”, or just “Windows isn’t the problem here, you are” 🙃 I hope at least Microsoft pays you well for the advertising!
Yeah. Sure it did.
You want a pic for proof? Ok, no worries.
Taken:
Sat, Jan 17, 2026 • 12:09 PM GMT+01:00Can’t wait for you to say this was 'shopped now. Go ahead, humour me.
Not shopped, but that is a hardware issue and has nothing to do with Windows.
If you ran Linux on it, you would have the same issue. Just the screen wouldn’t be blue.
So it just happens that I’m always unlucky with the hardware in all 3 gaming desktop PCs that I’ve built over the last ~14 years that they would have this behaviour? (Bluescreen out of nowhere, without any intensive hardware usage or weird behaviour or anything that justifies triggering this)
I haven’t ran Linux on this machine yet, but I’m more likely to go for it with each passing day. I can let you know how it goes and how many crashes I get. I don’t expect any, as I’ve been using Linux on my laptops for close to 10 years now and the only time I had a hardware problem was because I was using my old laptop as a server and its HDD died - but that’s because HDD laptops are not meant for these usage patterns, so totally expected tbh.
I find it super interesting that there is this pushback from you and the other user here saying “Windows doesn’t have any problems”, which now turns into “Ah but that’s hardware and Linux would have it too!” - How can you know?? How can you make such an apt diagnosis that it’s not a Windows-only issue with practically zero information??
Because if we are just blindly applying patterns then yes I can do the same - I’ve literally never had a running Linux system crash on me, from running it in VMs, Cloud VPSs, Laptops and even a Raspberry Pi. And in the same timeframe I’ve had more random blue screens on Windows than I can count. And I can tell you that I looked quite hard at a few of them to try and avoid triggering them. The only one I managed to figure out was that in a Laptop X USB-powered headset combo I could never start up the system with the headset connected, as if the cable was messed with and the dongle lost connection, it would immediately blue screen the laptop. But if it booted with the USB dongle disconnected and I connected it later, it was totally fine!! - Even with this crash being caused by hardware, how can you say that this is a reasonable behaviour from a “production-ready” OS? The latter behaviour tells us that it is totally possible to handle this hardware error without a full system crash, but it can happen all the same!
I honestly don’t understand what you or the other user get from being so adamant about Windows being good, or being “not that bad”, or just “Windows isn’t the problem here, you are” 🙃 I hope at least Microsoft pays you well for the advertising!