Slashdot Mirror

← Back to Stories (view on slashdot.org)

Creating BSODs?

Posted by Cliff on from the now-that's-an-odd-request dept.

mvanhorn asks: "This is not a joke, or a troll, but my company is testing a failover solution for NT and we were wondering about simple reliable ways to intentionally cause a BSOD. Please don't say "just fire up an application..." it will be neither useful, or funny. But really humorous answers that solve the problem are welcome."

1 of 40 comments (clear)

  1. SysInternals has your answer by Chelloveck · · Score: 4

    SysInternals has a solution for this. One of its products is called BlueSave, which is a utility that will save the text of the BSOD to a file. BlueSave is conveniently packaged along with a companion utility that will cause your PC to crash to the BSOD.

    We've provided the source and executable to a program, BSOD, that you can use to intentionally crash your computer in order to test BlueSave. Note that this program uses a device driver component to perform privileged operations and is therefore not exploiting a bug in Windows NT.
    --
    Chelloveck
    I give up on debugging. From now on, SIGSEGV is a feature.