If for some reason you want to simulate a freeze or crash in Windows 11 or 10, this is possible.
You can use the notmyfault app from Sysinternals for this. Notmyfault is designed to deliberately cause crashes, leaks and hanging processes in Windows for testing purposes. For example, deliberately causing a crash in Windows for testing purposes can be useful for software developers or system administrators who want to see how their systems react under extreme conditions.
However, it is important to emphasize that these types of tests should only be performed in a controlled environment, such as a virtual machine or test computer, to avoid damaging important data or systems. Always save your data before performing a simulated crash.
How do I intentionally cause a freeze or crash in Windows?
To begin download NotMyFault from Sysinternals to your computer. Then open the appropriate version for your computer architecture, the 32-bit or the 64-bit version.
There are three different jams available. The first is the “crash”, a normal freeze. The second is a “Hang” which allows you to simulate the computer becoming unresponsive. Finally, there is the “Leak”. This allows you to simulate a memory leak where the computer can slow down dramatically or even freeze.
Each jam also offers different options. For example, the following options are available for the “Crash” that you can simulate:
- High IRQL fault: This simulates a system crash by executing an operation at an inappropriately high Interrupt Request Level (IRQL). This causes an inconsistency in the system, resulting in a blue screen (BSOD).
- Buffer overflow: Simulates a system crash by intentionally writing data beyond the limits of an allocated buffer.
- Code overwrite: Simulates a system crash by deliberately overwriting code in memory. This simulates a critical security error, resulting in a blue screen (BSOD).
- Stack trash: Causes a system crash by deliberately corrupting the stack. This simulates a serious programming error, leading to a blue screen (BSOD).
- Stack overflow: Causes a system crash by deliberately overloading the stack. This simulates a common programming error, leading to a blue screen (BSOD).
- Hardcoded Breakpoint: Causes a system crash by triggering a predefined breakpoint in the code. This simulates a debug scenario, resulting in a blue screen (BSOD).
- Double free: Intentionally causes a system crash by re-freeing memory that has already been freed. This simulates a critical programming error, leading to a blue screen.
You select an option and click the “Crash” button to simulate a crash. You will then see that your computer freezes, usually resulting in a blue screen.
Read here how to identify or resolve crashes:
- How to analyze BSOD or blue screen in Windows 11 or 10.
- Look up a blue screen error message in the Windows log.
- Windows 11 keeps crashing? Try these 7 tips!
I hope to have informed you with this. Thank you for reading!