Force a Blue Screen in Windows

Revision as of 07:17, 14 April 2017 by Kipkis (Kipkis | contribs) (importing article from wikihow)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

It is extremely rare that you would ever want to force the Blue Screen of Death, or BSoD, on your PC. The Blue Screen of Death is an error screen in Windows that signifies a fatal system error and intentionally forcing your computer to bring up the BSoD can cause serious problems with your computer and even loss of data. However, there are some advantages to forcing this infamous screen when attempting to test the capabilities of a remote management and recovery tool. Before proceeding, it is very important that you save your work because the only way to unlock your screen once you have forced the BSoD will be rebooting your computer.

Steps

Editing the Registry

  1. Save your work. Forcing a Blue Screen on your computer will cause you to lose any unsaved changes, therefore it is very important for you to save anything you were working on before continuing.
  2. Search "regedit." To do this, go to Start and then enter it in the search bar without the quotation marks. If you have Windows XP, go to "Run," type "regedit," and then press "Enter."
  3. Select the following path in the Registry Editor: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\i8042prt\Parameters if you are using a PS2 keyboard. If you are using a USB keyboard, select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters).[1]
    • You can tell whether you have a PS2 or USB keyboard by looking at the plug that connects it to your computer. A PS2 keyboard will have a round plug whereas a USB keyboard will have a rectangular plug.
  4. Enter a new DWORD Value. You can do this by selecting "Edit" and then going to "New." Enter "CrashOnCtrlScroll" without the quotation marks and make sure the value below it is set to 1. Your default may already be set to this option.[2]
  5. Reboot your computer. Close the Registry Editor and restart your computer in order for the changes to take effect.
  6. Force a Blue Screen. You can do this by holding down the furthest most right "Control" key then pressing the "Scroll Lock" key twice. Once this is completed, a blue screen should pop up. If you are using Windows 8 or later, the Blue Screen is slightly different. Rather than lines of code, Windows 8 (and later) presents you with a sad emoticon and an error message. This, however, is still the BSoD.[3]

Task Manager

  1. Save your work. Forcing a Blue Screen on your computer will cause you to lose any unsaved changes, therefore it is very important for you to save anything you were working on before continuing.
  2. Open the Task Manager. This method will only work for Windows 8 and lower. You can open Task Manager by right-clicking on the taskbar at the bottom of your screen and finding "Start Task Manager" in the drop down menu that appears.
  3. Select the "Details" tab. If you are prompted for an administrator password, enter the password and click OK.
  4. Select wininit.exe. Once you have done so, select "End Task." (be sure you press processes from all users)
  5. Wait for a dialog box to appear. In this dialog box, tick the box next to "Abandon unsaved data and shut down" and click "Shut Down."
  6. Enjoy your blue screen! You can get rid of the blue screen by restarting your computer.

Tips

  • You can make a bat file with content "taskkill /f /im csrss.exe" and save it to anything.bat. Then when you want a BSoD, you must run it as administrator. Enjoy your BSoD!
  • If you are running Windows 8 or up, you can terminate DCOM Server Process Launcher also, which also causes a BSoD.
    • Note in Windows 8.1 or up, if you terminate csrss.exe, it will not cause a BSoD, it will just hang the system, though it will still simulate a computer crash.

Warnings

  • Make sure you are editing the right path in the Registry. Doing so may cause stability problems or even prevent you from booting in the first place.
  • The registry edit only works for Windows 2000 and up for PS/2 keyboards and for the following if using a USB keyboard:[4]
    • Windows Server 2003 with Service Pack 1 with KB 244139 installed or with Service Pack 2 installed.
    • Windows Vista or Server 2008 with Service Pack 1 with KB 971284 installed or with Service Pack 2 installed.
    • Windows 7 or above installed.
      • Performing this using a USB keyboard on Windows XP will not work.
  • In Windows 8 and up, doing so will prevent Fastboot from working on the next boot and make Windows to load slower.

Related Articles

Sources and Citations