New Tool Offers Life After Windows BSOD
An interesting new tool for PCs will drop you into a Linux shell when Windows crashes.of BugCheck2Linux NSG650 tools that have been attracting attention recently NTDEV Twitter leverages the Windows bug check callback function to run executables even after a BSOD (Blue Screen of Death) crash. So in this case “death” is not the end, it’s just the beginning of Linux.
It’s not a well-known fact that programs can run after a Windows BSOD, but BugCheck2Linux extends the current possibilities of running executables via a “bug check callback function”, booting an entirely different OS. increase. For information on the intended use of the bug check callback routine, see Microsoft Learn (opens in new tab) documentation site.
BugCheck2Linux runs as a driver, which “runs a little RISC V emulator that runs Linux”. NSG650 says screen output uses bootvid.dll and input relies on polling his PS/2 keyboard driver. The developer credits his ReactOS project for bootvid documentation, mini-rv32ima for RISC V emulator and Linux images, and his OSdev Wiki for PS/2 documentation.
There are some fairly severe restrictions on Linux installations that can be run after a Windows BSOD. For example, the display output is limited to 640 x 480 pixels and 16 colors, the system only works on his BIOS-based (not UEFI) systems, is slow, keyboard support does not allow user backspace, etc. There is a limit of In other words, this BSOD tool does not start a modern Ubuntu installation.
Being able to keep using a computer after a BSOD is impressive in itself, but what really captures the imagination here is the future possibilities beyond the small, limited Linux OS. NTDEV crashes a Windows PC to his BSOD, increasing the chances of instantly booting into Doom to vent post-crash stress. Perhaps trying a classic arcade title like Asteroids or Galaxian after the BSOD would be a more modest step.
Try BugCheck2Linux
If you’d like to give this tool a try, there’s a step-by-step guide on the GitHub page where you can find it. Essentially, the tool’s driver process needs to be downloaded and started so that the tool can run even in the event of a BSOD.
NTDEV’s video above shows a Tiny11 developer crashing a Windows 11 installation by running winini (as administrator) in PowerShell. Then you can see the Linux install is running after the BSOD.
It’s a fun project, but be careful with your PC and make regular backups just in case.