How to Force a Blue Screen of Death (BSOD) on Windows 11

The Blue Screen of Death, commonly called a BSOD, appears when Windows encounters a serious system or driver problem that it cannot safely recover from. Normally, a BSOD happens unexpectedly because of faulty drivers, hardware problems, corrupted system files, or other system-level issues.

Windows also provides ways to intentionally trigger a crash for testing purposes. This can be useful when you are testing crash-dump settings, debugging drivers, checking system monitoring software, or learning how Windows handles a critical failure.

A forced BSOD immediately interrupts Windows and may restart the computer. Any unsaved work can be lost, so this should only be performed on a test system or when you have a specific reason to generate a crash.

Method 1: Enable the CrashOnCtrlScroll Registry Setting

One of the built-in ways to intentionally trigger a Windows crash is to enable the CrashOnCtrlScroll Registry setting.

The exact Registry location depends on the keyboard driver being used.

For most modern USB keyboards, open Registry Editor and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters

To open Registry Editor:

1. Press Windows + R.
2. Type:

regedit

3. Press Enter.
4. Select Yes if User Account Control appears.
5. Navigate to the location above.

Right-click an empty area in the right pane and select:

New > DWORD (32-bit) Value

Name the value:

CrashOnCtrlScroll

Double-click it and set Value data to:

1

Click OK.

If you are using a PS/2 keyboard, the corresponding location is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

Create the same CrashOnCtrlScroll DWORD there and set it to 1.

After making the change, restart Windows.

Method 2: Trigger the BSOD With Ctrl+Scroll Lock

After enabling the Registry setting and restarting the computer, you can intentionally trigger the crash.

Press and hold the right Ctrl key.

While holding it, press the Scroll Lock key twice.

The sequence is:

Right Ctrl + Scroll Lock + Scroll Lock

If the configuration is correct, Windows should immediately initiate a system crash.

The computer may display a blue screen and then restart automatically.

This is not a normal keyboard shortcut. It is a deliberate kernel-level crash mechanism designed primarily for testing and debugging.

Before trying it, save everything you are working on. The forced crash can cause unsaved changes to disappear.

If nothing happens, check that:

• You used the right Ctrl key.
• Scroll Lock is actually being sent by your keyboard.
• The Registry value was created under the correct keyboard driver.
• The value is set to 1.
• Windows was restarted after changing the Registry.

Method 3: Force a Crash Using Command Prompt

You can configure the crash setting without manually editing Registry Editor by using an elevated Command Prompt.

For a USB HID keyboard, open Command Prompt as administrator and run:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters" /v CrashOnCtrlScroll /t REG_DWORD /d 1 /f

For a PS/2 keyboard, use:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters" /v CrashOnCtrlScroll /t REG_DWORD /d 1 /f

After the command completes successfully, restart Windows.

You can then use:

Right Ctrl + Scroll Lock + Scroll Lock

to trigger the crash.

This method is particularly useful when configuring test machines because the Registry modification can be performed quickly from the command line.

You can verify the setting afterward using Registry Editor or the reg query command.

For example:

reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters" /v CrashOnCtrlScroll

The result should show the value as 0x1.

Method 4: Configure Windows to Create a Crash Dump

If your purpose is to test a BSOD rather than simply make Windows crash, configure memory-dump settings before performing the test.

Windows can save information about the system state when a serious system crash occurs.

To review the settings:

1. Press Windows + R.
2. Type:

sysdm.cpl

3. Press Enter.
4. Open the Advanced tab.
5. Under Startup and Recovery, click Settings.
6. Find Write debugging information.

Depending on your Windows configuration, you may see options for different types of memory dumps.

You can also check the dump-file location from this window.

If you are testing a driver or debugging a system problem, selecting an appropriate dump type can provide useful information after the crash.

The amount of information saved depends on the dump type you select.

Remember that creating a dump file requires available disk space. Large memory dumps can consume significant storage, particularly on systems with a large amount of RAM.

Method 5: Test the BSOD and Check the Result

Once the crash setting and dump configuration are ready, save your work and trigger the BSOD using the configured keyboard combination.

After Windows restarts, allow the system to complete its startup process.

You can then check whether Windows created a dump file.

The location depends on the dump type and configuration. A common location for a small memory dump is:

C:\Windows\Minidump

A complete or kernel memory dump may be stored elsewhere according to the settings configured in Windows.

You can also open Event Viewer to inspect system events surrounding the crash.

Press:

Windows + X > Event Viewer

Then look through the Windows system logs for information associated with the unexpected shutdown or crash.

For advanced debugging, Windows crash dumps can be opened with compatible debugging tools to investigate the underlying system state.

If you are simply testing whether Windows can generate a crash dump, the existence of the expected dump file may be enough to confirm the test.

Method 6: Use a Laptop or Keyboard Without Scroll Lock

Many modern laptops do not have a dedicated Scroll Lock key.

If your keyboard lacks Scroll Lock, check whether your manufacturer provides the key through an Fn combination.

The exact combination varies between keyboards.

Another option is to connect an external keyboard with a physical Scroll Lock key.

You should make sure that the operating system actually receives the Scroll Lock input. A key combination printed on a keyboard does not necessarily behave identically across all hardware.

If you cannot generate the crash using the keyboard method, check your keyboard configuration and confirm that the appropriate CrashOnCtrlScroll setting is enabled for the driver being used.

For testing purposes, an external keyboard can make the procedure easier.

Method 7: Disable the Forced BSOD Setting

After completing your test, disable the crash shortcut.

Leaving the setting enabled is unnecessary for normal Windows use because the keyboard combination is specifically intended to cause a system crash.

Open Registry Editor and return to the location where you created CrashOnCtrlScroll.

For a USB HID keyboard:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters

For a PS/2 keyboard:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

Double-click:

CrashOnCtrlScroll

Change the value from:

1

to:

0

Alternatively, you can remove the value entirely.

You can also disable it from an elevated Command Prompt:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\Parameters" /v CrashOnCtrlScroll /t REG_DWORD /d 0 /f

Restart Windows after changing the setting.

Once disabled, the Ctrl+Scroll Lock combination will no longer be configured to deliberately crash the system.

Method 8: Recover Safely After a Forced Crash

A forced BSOD normally causes Windows to restart, but you should still check the system afterward.

First, allow Windows to complete its startup process.

Then check:

• Whether Windows starts normally.
• Whether your important files are intact.
• Whether a memory dump was created.
• Whether Event Viewer recorded the crash.
• Whether Windows reports any startup or recovery problems.

If Windows repeatedly crashes after the test, remove or disable the CrashOnCtrlScroll setting and restart the computer.

If the system continues crashing for another reason, investigate the new crash separately rather than assuming every BSOD is caused by the keyboard setting.

You can also check Windows Update, recently installed drivers, and system logs if unexpected crashes continue.

A forced BSOD should be treated as a controlled test, not as a troubleshooting method for an ordinary Windows problem.

Conclusion

Windows 11 includes mechanisms that allow advanced users to intentionally generate a Blue Screen of Death for testing and debugging. The CrashOnCtrlScroll setting can be configured for the appropriate keyboard driver and then triggered using Right Ctrl + Scroll Lock + Scroll Lock.

This can be useful when testing crash-dump collection, debugging drivers, or verifying how a system responds to a kernel crash. Before triggering the crash, save all work and make sure you understand that Windows will be interrupted immediately.

If you want to analyze the crash afterward, configure Windows memory-dump settings before performing the test. After completing the test, disable CrashOnCtrlScroll and restart Windows so the system returns to normal operation.

FAQs

1. Can I intentionally cause a BSOD in Windows 11?

Yes. Windows provides a supported mechanism for deliberately triggering a crash through the CrashOnCtrlScroll setting. It is primarily intended for testing and debugging.

2. What keyboard combination causes the forced BSOD?

When the required setting is enabled, press and hold the right Ctrl key and press Scroll Lock twice.

3. Will a forced BSOD damage my computer?

A software-triggered crash is not intended to physically damage the hardware, but it abruptly interrupts Windows and can result in lost unsaved data. It can also be inappropriate to perform repeatedly on a system containing important work.

4. How do I stop the Ctrl+Scroll Lock BSOD feature?

Set the CrashOnCtrlScroll Registry value to 0, or remove the value, and then restart Windows. This disables the intentional crash shortcut.

Quick Summary

• Enable CrashOnCtrlScroll under the appropriate keyboard driver Registry key.
• Restart Windows before testing the shortcut.
• Press Right Ctrl + Scroll Lock + Scroll Lock to trigger the BSOD.
• Disable the setting after testing and restart Windows.