Windows 8 Has Finally Updated The Blue Screen Of Death

Windows 8 Has Finally Updated The Blue Screen Of Death

It took Microsoft long enough, but they’ve finally (FINALLY!) changed the blue screen of death to be something a little more friendly and a little less scary.

Honestly, how many times have you used the dump information on the BSOD to actually diagnose a problem, compared to how many times you just rebooted the computer and didn’t think anything of it? A more cutesy error message is a better idea.

We’re also really glad they updated the similarly old-school task manager, so who knows what other changes we’re going to find in version #8.

Chip Hazard’s Facebook


    • I’m not sure how to feel about this. I like my error screens to have at least some vague information on them. Given most computers default to rebooting on bsod anyway, making it more user-friendly could just be wasted effort.

      Of course, this could just be nostalgia talking. My first computer was a win95 machine, so blue is the colour of my childhood.

  • Nice to see that Microsoft is not without humour. If it’s able to write a message to the screen, then it should be able to write message to a simple log file if you did want to access it for trouble shooting.

    • And what if the problem is a faulty HDD driver?

      This is useless if you want info. Its like the “Your mac now needs to restart” screen.

      I assume there is some way of getting the old screen back.

    • In my mind, if they have the ability to write to the screen, they have the ability to recover automatically. Of course, that would increase the size of the OS another couple gigs I’d guess, lol. (I swear, MS must secretly own stock in memory and disk manufacturers.) Showing my age, I remember when multi-user multi-tasking operating systems were under a meg and a gig was an unbelievable amount of disk. High rel systems had watch dog timers so they would automatically recover and/or reboot if they crashed to the point they couldn’t recover. Seems to me MS could put a little more effort into this area, but maybe that’s a lost art to programmers of today.

  • How about putting in some effort to eradicating the causes of the BSOD rather than changing how it looks?

    I get at least one a week. Most occur when coming out of hibernation.

  • I’m all for simplifying it, but i do use the data in the crash dump to some degree but mostly the just module name that caused it.

    Like on my ASROCK ION3D, it would say nuvo_cir_blahblah.vxd or something like that, i immediately knew the infrared driver was causing the issue. So they should provide a basic detail on the screen, perhaps if the keyboard can still function pressing F1 or something to get more info.

    • You know that, I know that but Average Joe Six-Pack and Granny Youtube wouldn’t have a clue what the problem was and all of that “information” to her would cause even more panic and confusion.

      A simple, “something went wrong, we’re restarting” message is a lot better.

      • Thats why i said to simplify it but not remove the actual useful information (95% of the info in the BSOD is useless to me, and the %5 that is useful woudl not be scary to average people), now granted on reboot it could popup a dialog saying this module faulted and look for a fix button like i got sometimes in vista when the Radeon 3500 drivers crashed the system (never did get that working flawlessly on vista), but i didnt get that on the ASROCK running Win7.

        For those times that you cant boot up windows at all, perhaps in their new fancy bootloader it could report bootup issues and provide an easy way to view the log data.

        Anyway BSODs are kinda supposed to be scary because it means there is something really wrong that needs to be addressed, it can jolt them into action, where as an “Oops sorry something went screwy your work is gone” makes it look like a windows issue rather than a 3rd party software issue (the cause of almost all BSODs i’ve ever seen).

  • Bad move. The BSOD gave plenty of useful information. It’s all well and good saying write the information to the event log, but what happens if you can’t log in at all? If it goes to the Windows splash screen the reboots (which is usually the HD, but sometimes RAM – the BSOD told you that)

  • you know, the detailed BSOD was better, even to the ignorant ones it told you “Hey man, this thing is busted” this new one will have users still trying to click around the place, not realizing the thing is borkd

Show more comments

Log in to comment on this story!