Q: "How does one go about forcing a Blue Screen of Death on a Windows system?" A customer of mine asked me this question and it required some digging. Apparently, the only way to test a cluster configuration that they were setting up and ensure that it was properly failing over was to initiate a bugcheck (or what people affectionately refer to as a "Blue Screen") on one of the cluster nodes.
The answer lies in an obscure tool from the MSPRESS book, "Windows Internals".
http://www.microsoft.com/technet/sysinternals/information/windowsinternals.mspx
Toward the bottom of this web page, there is a section called "Book Tools" with an entry for a tool called "Notmyfault".
Notmyfault: Use this executable and driver to crash your system in several different ways. Chapter 7 uses Notmyfault to demonstrate pool leak troubleshooting and Chapter 14 uses it for crash analysis examples. The download includes x86 (in the exerelease directory) and x64 versions (in the exerelamd directory) as well as full source.
What makes this tool interesting is that it’s available in both x86 and x64 forms: Something that you don’t think about that much because traditionally it’s been a 32-bit world but with the escalation of x64’s importance, having x64-based versions of tools like these are becoming increasingly important.
So leverage this tool for your cluster nodes and otherwise "Blue Screen" away!
kurtsh
Kurt Shintaku's Blog 