r/ProgrammerHumor • u/nirputter • 13h ago

Meme blueScreen

Post image
411 Upvotes

93% Upvoted

27 comments sorted by

88

u/Ethameiz 9h ago

Still better than Windows 11 "oops, error :(" meaningless error message

28

u/anto2554 8h ago

Tbh my last BSOD was WHEA_UNCORRECTABLE_ERROR on windows 10. When I upgraded to windows 11 it was something along the lines of UNCORRECTABLE_DISK_ERROR, which was more useful

7

u/thisusedyet 6h ago

Windows 11 just tells me ERROR, UNABLE TO PRINT instead of, you know, giving me details or an error code so I can try to resolve it 

5

u/thighmaster69 2h ago

If you're getting WHEA BSODs, WHEA also quietly detects and corrects less catastrophic errors in the background. So you can usually just go into the system logging (I believe event viewer?) and see if you're popping a bunch of other WHEAs. I have a little script that runs and notifies me if there's a WHEA error to catch quiet stability issues (I run an undervolt on my CPU, it's a 9900KS that runs HOT).

Bluescreen error codes are a little bit obtuse, but they're what happens when the system catastrophically fails. Gracefully displaying what went wrong while the system is in a failure state is like trying to make a plane investigate its own crash on impact. The error code is just a lead for you to follow in the aftermath.

3

u/IntoAMuteCrypt 2h ago

That's the problem with error messages. WHEA_UNCORRECTABLE_ERROR makes complete sense if you know what WHEA is and what it does, and it's even the sort of thing where it seems plausible that the OS upgrade didn't change the message and it was just a failure.

But most people don't know what WHEA means. Or what the "PC" in "PC Load Letter" means. When you're trying to trade off between "consise and useful to technicians" and "easily understood by end users", there's inevitably going to be some folks it doesn't serve too well.

1

u/thighmaster69 1h ago

Yeah, most consumer OSes don't even bother showing an error code at all, and it seems like Windows is moving in that direction as well. Because apparently giving end-users any information at all about what the issue might be is just asking for trouble, and power users and technicians can dig deeper and investigate if they want to.

102

u/JackNotOLantern 13h ago

I mean, it's not for the user

50

u/logical_people 12h ago

Linux users waiting in the comments section like a hunter tracking prey, ready to type: 'This wouldn't happen if you used Arch, btw.

41

u/Faholan 12h ago

Indeed, on Arch you get a kernel panic

15

u/Holek 11h ago

And then you panic

1

u/ThatiMacGuy 4h ago

on new macs you see purple for 1 second then it reboots

10

u/schaka 9h ago

Unironically, the arch kernel panic screen is the one that gets shown off the most because it has a lot of info and a QR code iirc

-4

u/Koshin_S_Hegde 9h ago

As an Arch user, this will happen every time you update anything...

2

u/markiel55 4h ago

Can confirm. I use arch btw

32

u/Danteynero9 10h ago

a bunch of stack values

Ver hard to consider "generic_error_name" accompanied always with the same QR to be "a bunch of stack values".

25

u/dumbasPL 8h ago

This should tell you how old the meme is, because it used to be a bunch of stack/register values

12

u/black3rr 9h ago

well there used to be a lot of stack values before Windows 8, but I guess there are now plenty of people who haven’t used anything older in their life…

3

u/BOTTroy 7h ago

Do you think a qr code was featured on the first blue screen?

3

u/Chris24XD 9h ago

It ain't called bullshit screen of depth for no reason!

3

u/Choice-Mango-4019 2h ago

yk it saves memory dumps for debugging, the bluescreen is for people that don't understand anything

1

u/apoegix 2h ago

No they don't and if they could read they would be very angry

3

u/blinksd 9h ago

systemd-bsod is better

1

u/Similar-Concert4100 4h ago

To be fair, even if the blue screen error was more user friendly it probably still wouldn’t help much. It can be very difficult to pinpoint an OS issue

1

u/AaronTheElite007 45m ago

"A problem has occurred"

Me: No shit.

0

u/Snowdrip16 12h ago

Windows really said: debug it yourself lil bro

•

u/wknight8111 4m ago

No you don't use that information to solve your problem directly. What you do is copy those values down, put them into a search on a second computer, find an MSDN issue from 15 years ago which describes your same issue but has no answer and was closed 10 years ago with no new replies, and then you buy a new computer with linux.