Very commmon abbreviation for Blue Screen of Death. Both spoken and written.

--Jargon File, autonoded by rescdsk.

In most recent versions of Windows (notably Windows 2000), the BSOD is caused by faulty drivers, rather than faults in shipped kernel space. Anything that chokes and dies inside of Windows NT Kernel Mode will cause the BSOD. Unfortunately in Windows 9x, the kernel mode was a lot less protected, and things could quite easily muck with kernel space.

That is why a WinNuke would blue-screen you. Your network stack runs (for performance and kernel construction reasons), inside of kernel space. If you overflowed that, it would throw a BSOD and report the faulty module.

Similar to this is a Unix Kernel Panic, where the kernel cannot recover from such errors. Keep as much out of your kernel as humanly possible, for those reasons alone.

Also, the coolest program in the xscreensaver package, period.

"The finest in personal computer emulation, this hack simulates popular screen savers from a number of less robust operating systems. Written by Jamie Zawinski."

This has, not only the Windows NT BSOD, but the Windows 9x BSOD, the Mac ROM's "Sad Mac" icon, some sort of Mac OS debugger, an Amiga error screen, and more.

Log in or register to write something here or to contact authors.