Share via

How to manually send stop codes via CMD (command line)?

Mattia Candotti 11 Reputation points
2022-03-22T10:40:10.953+00:00

I Understand that you can trigger BSOD by creating a registry entry that causes a crash by pressing Right Control and scroll lock. And I know that you can also crash the system by typing "wininit" into powershell, or killing the svchost.exe program via task manager. However I really want to use the "INITIATED_MANUAL_CRASH" stop code rather than killing an important system process and risking corruption of certain files. My computer has no right control key, nor does it have a scroll lock key. For reference, I am on a Surface Laptop 3. So I would like to know if I can send stop codes to kernel via the command line to trigger the "INITIATED_MANUAL_CRASH" BSOD. Thanks!

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,195 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. MotoX80 32,911 Reputation points
    2022-03-22T13:11:34.39+00:00

    NotMyFault can generate several different errors. It requires admin access to function.

    https://learn.microsoft.com/en-us/sysinternals/downloads/notmyfault

    1 person found this answer helpful.
  2. Daniel Kåven 696 Reputation points
    2022-03-22T11:59:00.6+00:00

    I did some research and found a script to handle the job, although I haven't tested it myself it got 238 stars and 66 forks.
    It is standalone and don't require admin-rights.
    https://github.com/peewpw/Invoke-BSOD

    It includes a PowerShell-script and an executable in case you haven't got access to PowerShell.

    Remember that you're using it at your own risk, please read through the script-file as well.

    Hope this helps you.