Windows 8 gets a new blue screen of death

Windows 8 has a ton of new features that we have been covering extensively over the past 24 hours or so. But who knew that Microsoft would also make a change to one of the most dreaded screens of all? We are speaking, of course, about the "blue screen of death", the harsh screen that comes up when a Windows operating system decides that it doesn't know what to do and locks up. It's not something any Windows users want to see.

Under the new Windows 8 operating system, Microsoft has put in a new version of the blue screen of death. It's still something that you don't really want to see but this time, Microsoft has decided to give it a more sympathetic look. The fonts that display the error message are more modern looking and more importantly, you also see a big frown emoticon staring back at you. It makes you feel that instead of being angry with you, Windows 8 is sorry that it has to unexpectedly shut down and make you lose all of the work you have been doing up to that point.

Sure, it's a minor thing among all of the major new features and improvements in Windows 8, but we suspect that you will be seeing this new blue screen of death on occasion while using the pre-release operating system. But, as we get closer to the final builds and eventually RTM, the BSOD will hopefully never show its ugly (and sad) face.

Image via MobilityDigest.com

Report a problem with article
Previous Story

Windows 8: How to re-enable the classic start menu

Next Story

Steve Ballmer: 500,000 Downloads of Windows 8 already

41 Comments

Commenting is disabled on this article.

I'm willing to bet by the time the final is released...Microsoft will change the part of the bsod screen that says..

It'll restart in.....to...your computer will restart in.

I just don't see Microsoft leaving it to....It'll restart....on the final build.

wotsit said,
HOW ABOUT STOPPING THEM FROM ACTUALLY HAPPENING?!

Vast majority of bluescreens are caused by buggy 3rd party drivers. So... as soon as that gets solved, I think we'll get there.

Johrie said,
Hmm why isn't any error code stated on the bsod?

Because most people don't need it, and it can be accessed via a log file after the computer has rebooted.

xpclient said,
Hope there's an option to turn on the one with technical details. The details are there for a reason, not for fun.

Or you can just go take a look at the event log / dump files it creates?

Wow Microsoft actually getting rid of MS-DOS-erra elements? I think hell just froze over... Let's see if they manage the get rid of those archaic selection dots as well this time around...

.Neo said,
Wow Microsoft actually getting rid of MS-DOS-erra elements? I think hell just froze over... Let's see if they manage the get rid of those archaic selection dots as well this time around...
16-bit app support is disabled out of the box, so I'm gonna say yes.

Sraf said,

Yes, but it's a more calming blue!


Even soothing. You would almost wouldn't mind, Windows ever crashing again.

fehu said,
extremely informal
maybe too much?

Computers aren't formal anymore. Changing the BSOD to something like this helps make the entire experience (at least a little) more human. It's friendlier, rather than being a cold chunk of text you don't understand. I, personally, love it.

the actual bsod is very ancient and programmer styled, but this looks like some message that i get when my game can't connect to the multiplayer server

prismatics said,
It doesn't give any details! How are you supposed to figure out what's wrong by searching for "System Service Exception"?

That's the same message that you would actually use in older Windows OSes. I have had the BSoD myself, but due to running the 32bit version in VMware player (which doesn't support Windows 8 yet) and my error was "HAL_INITIALIZATION_FAILED"

prismatics said,
It doesn't give any details! How are you supposed to figure out what's wrong by searching for "System Service Exception"?

Just check the even viewer after the restart, usually gives a much more detailed answer than the bluescreens ever did and you have all the time you want to read it

Leonick said,

Just check the even viewer after the restart, usually gives a much more detailed answer than the bluescreens ever did and you have all the time you want to read it

And what if the pc won't start back up? googling the first numeric code helps pinpoint the problem easier than just the description.

ObiWanToby said,
I see this in a loop with Virtualbox. Can't seem to get it to work

I use Virtualbox and no problems. I used windows 7 settings, when I did windows other it did not work.

ObiWanToby said,
I see this in a loop with Virtualbox. Can't seem to get it to work

I struggled for a bit last night. Today I used the Win7 settings with 2gb ram and 256mb of video ram (2d and 3d acceleration has to be turned on to raise the memory so high) and didn't run into any problems. Best of luck

ObiWanToby said,
I see this in a loop with Virtualbox. Can't seem to get it to work

VirtualBox wouldn't run 32Bit for me, but 64bit ran fine

ObiWanToby said,
I see this in a loop with Virtualbox. Can't seem to get it to work

Find an extra drive and install it on that. One never gets the full experience with a virtual machine.

DrakeN2k said,
Looks much better

Tehcnically though its not a Blue screen as you can see in the picture its just an overlay over the windows 7 default wallpaper included in the build. It was covered on neowin before, a previous build had a similar SOD on a solid black background. I guess if that were to still happen it would also be appropriate for it to be called BSOD.