As part of a multi-operating system challenge (testing computer integrity), I need to find the fastest way to reproduce a genuine Blue Screen of Death (BSOD) on a Windows machine. Any version that is XP or later will work.

As Shinrai puts it:

So basically you're trying to BSOD a machine as fast as humanly possible, but only once, and you can't touch the machine before the clock starts?

Yep, that's exactly what I'm trying to do.

I'm wondering if there are simple commands or actions that will cause Windows to go haywire and spit out a blue screen. Any pointers would be very helpful.


  • Can't write a script/program
  • Can't mess with hardware
  • Must be able to do it WITHIN windows
  • Can't be fake

I need to be able to boot cleanly into Windows, then I must reproduce a BSOD on the fly. So hardware and required-boot solutions are good but they don't conform to these rules.

I arrived at the competiton ready to implement Shinrai's method of BSOD. Turns out there were no specific rules about turning your computer on and off, only that you can't mess with the hardware. I checked my keyboard -- it was a USB one, so I knew which key to edit. We were told to start and I quickly found and edited the key and rebooted. Luckily these were bare bones computers and not a lot of services had to be started - resulting in a fairly quick reboot. Looking around, I saw people screwing around with the registry but no one else was restarting their computer. I did the keyboard combination and BOOM windows spewed a beautiful BSOD (something the OS is actually good for).

I ended up winning and I only had one thing to say: "I'm happy to be going home to my linux box".

Thanks to Shinrai for the winning solution!

  • 5
    I'll add this as a comment since I'm sure that there are better ways, but on any machine with powershell on it the fastest way that I have found is: Remove-Item HKLM:* -recurse -force
    – EBGreen
    Jul 11, 2011 at 17:34
  • 1
    @EBGreen - Actually, that's pretty damned effective for this particular situation.
    – Shinrai
    Jul 11, 2011 at 17:35
  • @EBGreen - that's right along the lines of what I'm looking for. Does XP comes with powershell by default?
    – n0pe
    Jul 11, 2011 at 17:38
  • 1
    "Can't WRITE a script/program" Does that mean you can download a program from Sysinternals that does it? If yes: dl.dropbox.com/u/16862782/NotMyFault.zip will crash it instantly. AH HAHAHA!
    – sinni800
    Jul 11, 2011 at 23:15
  • 1
    @MaxMackie - What ended up being the winning solution?
    – Shinrai
    Jul 22, 2011 at 19:01

4 Answers 4


There is in fact a developer tool built into most versions of Windows to generate a BSOD on command. Here's how you cause it in Windows 7 on either a USB or PS/2 keyboard (I believe it is the same for XP/Vista on USB even though this article doesn't say so, I may be mistaken though):

You must ensure the following three settings before the keyboard can cause a system crash:

If you wish a crash dump file to be written, you must enable such dump files, choose the path and file name, and select the size of the dump file. For more information, see Enabling a Kernel-Mode Dump File.

With PS/2 keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.

With USB keyboards, you must enable the keyboard-initiated crash in the registry. In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.

You must restart the system for these settings to take effect.

After this is completed, the keyboard crash can be initiated by using the following hotkey sequence: Hold down the rightmost CTRL key, and press the SCROLL LOCK key twice.

The system then calls KeBugCheck and issues bug check 0xE2 (MANUALLY_INITIATED_CRASH). Unless crash dumps have been disabled, a crash dump file is written at this point.

If a kernel debugger is attached to the crashed machine, the machine will break into the kernel debugger after the crash dump file has been written.

  • 3
    Good answer for all keyboards, but does still require a lengthy reboot.
    – n0pe
    Jul 11, 2011 at 17:26
  • @MaxMackie - You only have to reboot the first time you change the setting, I didn't expect that would be a problem. It sounds like you'll be doing a lot of testing from the way you worded the question. :)
    – Shinrai
    Jul 11, 2011 at 17:26
  • yeah that's my fault for not specifying. I will edit my question and be a little more specific.
    – n0pe
    Jul 11, 2011 at 17:27
  • @MaxMackie - I see your edit but I don't see why a 'lengthy reboot' is a problem, but maybe I'm reading you wrong. You change the settings, reboot once, and then you can generate blue screens to your hearts content until the end of time (or the machine fails, whichever comes first). Of course, you'll have to reboot after each blue screen but that's true with ANY blue screen...
    – Shinrai
    Jul 11, 2011 at 17:30
  • 1
    Maybe I'm too vague in my question. This is for a sort of challenge. We need to reproduce a one-time BSOD. It doesn't matter if it only takes 1 reboot, it's only the first occurrence of the BSOD that actually counts.
    – n0pe
    Jul 11, 2011 at 17:32

This is an old documented technique. Should work at least up to Vista:

Find in regedit:


Create a DWORD key named CrashOnCtrlScroll and set it's value to 1.


To generate a BSOD, hold the right CTRL and press ScrollLock twice.

  • This only works for PS/2 keyboards. See my answer for USB as well.
    – Shinrai
    Jul 11, 2011 at 17:24
  • Seems like this works, but you need to reboot for it to take effect. Pretty long.
    – n0pe
    Jul 11, 2011 at 17:25
  • 2
    Nice one shinrai. You got +1
    – A Dwarf
    Jul 11, 2011 at 17:35

You can enable manually initiated crashes by performing these registry changes.

If your BIOS can switch your system's hard drive adapter between native SATA and legacy ATA mode (and possibly IRRT), switching to a different mode Windows was installed in will usually produce a BOOT_VOLUME_INACCESSIBLE error. I'm pretty sure disabling ACPI (if possible on your BIOS) when Windows was installed with ACPI enabled will also result in a bluescreen on boot.

Killing winlogon.exe using Sysinternal's Process Explorer produces a blue screen, but it's not the traditional "A problem has been detected and Windows has been shutdown to protect your computer..." screen.

This may also interest you - BlueScreen Screen Saver from Sysinternals.

  • lol at the screensaver, I love that thing. Probably not quite what he wants, though. xD
    – Shinrai
    Jul 11, 2011 at 17:31
  • After Max's comment on my answer, probably killing winlogon is the best solution to his problem. (I can't think of another app offhand that'll do the same thing but I'm sure there are others.)
    – Shinrai
    Jul 11, 2011 at 17:34
  • The screensaver is hilarious but yeah I'm not looking for that :)
    – n0pe
    Jul 11, 2011 at 17:36
  • Rightclick on wininit.exe -> "Kill Process Tree" will create a BSOD with "CRITICAL_PROCESS_DIED"
    – matthid
    Sep 24, 2016 at 11:48

You could do:

TASKKILL /IM svchost.exe /F

in the command prompt on Windows 10.

It will end a critical process and crash windows.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.