Windows

3 Ways to Trigger a Blue Screen of Death (BSoD) on Windows 11

A guide on how to force BSOD on your Windows 11 computer

58views

Highlights:

  • Back up all important files before initiating a BSoD on Windows 11.
  •  IT professionals or developers who comprehend the risks of forcing a BSOD may legitimately need to induce a BSOD for testing purposes.
  • Casual users should desist from attempting this due to the associated risks.

How to Trigger a BSoD on Windows 11

Method 1: Use the Task Manager

The Task Manager is an essential tool that keeps tabs on all the processes on your system. This tool can also help to force a BSOD error on Windows 11 by pressing specific commands. Follow the steps below to do this.

  1. Right-click on your taskbar and click Task Manager.
    Open Task Manager
  2. Navigate to the Details tab, select  wininit.exe from the list of options, then click the End task button.
    End task on Task Manager
  3. When a dialogue box appears, choose the Abandon unsaved data and shut down option, and click Shut Down.
  4. After doing this, the BSOD will appear.
  5. To remove the BSOD, simply reboot your PC.

Method 2: Make use of the Registry Editor 

You can easily force a BSOD on your PC by using the Registry Editor. Follow the outlined steps below to do this. Always remember that this process is risky and could cause permanent damage to your device if you make a mistake. Ensure you back up your registry before proceeding.

  1. Open the Registry Editor by holding the Windows + R keys simultaneously, type regedit in the text field, and then hit Enter.
    Regedit to open Registry Editor
  2. For USB keyboard users, navigate to the path below.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters
  3. Right-click on your Parameters key, and go to New > DWORD (32-bit) Value.
    Create D-word value
  4. Rename the new DWORD key as CrashOnCtrlScroll.
  5. Double-click the newly created key, change its value from 0 to 1, and click OK.
    Create D-word value
  6. For Legacy PS2 keyboard users, go to the path below.
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
    Path to making a BSoD on Windows 11
  7. Right-click on the right-hand side, navigate to New > DWORD (32-bit) Value and name it CrashOnCtrlScroll.
    Create D-word value
  8. Then, double-click the newly created key, change its value from 0 to 1, and click OK to implement the change.
    Set value data
  9. For Hyper-V keyboard users, navigate to the path below.
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\hyperkbd\Parameter
  10. Once on this path, follow the same steps as PS2 keyboard users to create a DWORD and change its value.
  11. Then, reboot your system.
  12. To initiate a BSOD, hold the right Ctrl key on your keyboard and press the Scroll Lock twice.
  13. To undo the BSOD, reboot your computer.

Method 3: Use the PowerShell

The PowerShell is a powerful command line utility that you can use to run critical system commands, including forcing a BSOD.

  1. Press the Windows key, type PowerShell in the text field, and click the Run as Administrator option.
    Open PowerShell
  2. In the PowerShell interface, input wininit and hit Enter.
  3. After running this command, the BSOD will appear along with some error messages.

Potential Dangers of Inducing a BSOD on Windows 11

A Blue Screen of Death (BSOD) is a critical system error that halts your computer and displays an error message. Inducing a BSOD for troubleshooting purposes can be extremely dangerous, especially if you intend to use the Registry Editor. This is why:

  • Work in open programs that you have not saved can be permanently lost.
  • Recurring BSODs can damage your system files and result in even more periodic crashes.
  • Forceful system crashes can harm hardware components in severe cases.
  • Messing with the Registry Editor to induce a BSOD can result in permanent system instability and demand a full reinstallation to fix.

Sometimes, stress testing software or system simulators might provide safer alternatives to induce controlled system crashes for testing intents.

Disclaimer: Any damage caused by an attempt to complete this process, leading to tampering with your system, is at your own risk. If you’re uncertain about how to go about this process, I recommend consulting a qualified technician.

Leave a Response

David Ogbor
David is a tech guru with extensive knowledge in technical articles. He is passionate about writing and presents technical articles in an easy-to-understand format for easy comprehension. He aims to present easy solutions for day-to-day problems encountered while using PC. In his spare time, he likes traveling, playing sports, and singing.