WebProNews

Tag: BSoD

  • Google Chrome Will Get Error Codes To Help With Troubleshooting

    Google Chrome Will Get Error Codes To Help With Troubleshooting

    According to ZDNet, Google’s Chrome web browser will soon receive error codes similar to those shown on the Windows blue screen of death (BSOD) display.

    The feature was proposed by Eric Lawrence, a software engineer working on the Chromium-based version of Microsoft Edge. The goal is to provide users with a convenient way to diagnose issues by giving them an error code they can research and learn about.

    The feature is currently being tested in Chrome v81, but there has been no confirmation that it will make the final build of v81, or be included in the next release. Either way, all indications are this is a permanent addition to the browser.

    As ZDNet highlights, since it was an engineer working on Microsoft’s browser that suggested the feature, it will likely make its way to other Chromium-based browsers, such as Opera, Vivaldi and Brave.

  • Windows 8 Blue Screen of Death Has A Sad

    While everyone is pouring over the Windows 7 Tutorials, Guides” href=”http://ihackers.net/”>Windows 8 preview, one of the more amusing finds concerns the infamous Windows’ Blue Screen of Death, which is Microsoft’s way of telling you the session of Windows you’ve been working with has failed, either through user error or a computational mistake.

    In previous BSoD formats, the screen contained details of the crash, followed by a “restart your computer” command or something similar. In Windows 8, however, the details are no longer featured on the next-gen BSoDs. Instead, they’ve been replaced by a frown smiley and a message telling you your computer gagged and needs to be restarted.

    An example of these new BSoDs can be seen leading this post, which comes courtesy of Geek.com. Apparently, Windows was developing a more ominous Black Screen of Death, but instead, chose the more friendly-looking frown.

    Because the new BSoD frown face doesn’t offer any details as to why the computer crashed, Geek.com explains what concerned users will need to do in order to find out why:

    A reboot is going to happen at this point, but if you want to find out what caused the problem you need to write down or remember the search term it presents you with. The two search terms I have seen suggested so far are “System Service Exception” and “HAL Installation Failed.” I doubt either will return that much useful information as they are both quite generic terms.

    Just because we can, here’s a YouTube featuring the history of the various BSoDs Windows users have encountered.


    Is the frown face an improvement or does all the information need to be present, as was the case with previous BSoDs?