Share this article
Latest news
With KB5043178 to Release Preview Channel, Microsoft advises Windows 11 users to plug in when the battery is low
Copilot in Outlook will generate personalized themes for you to customize the app
Microsoft will raise the price of its 365 Suite to include AI capabilities
Death Stranding Director’s Cut is now Xbox X|S at a huge discount
Outlook will let users create custom account icons so they can tell their accounts apart easier
Microsoft expert advises against using keyboard shortcuts to force crashes
NotMyFault is the way to go for developers
2 min. read
Published onFebruary 22, 2024
published onFebruary 22, 2024
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
When developing software, sometimes you need to force a system crash or BSOD error, but that’s easier said than done, especially on newer PCs.
However, Microsoft experts have decided to share their secrets and show the developers how to do this properly, and if you want to learn more, keep on reading.
To force Windows to crash, use third-party software, Raymond Chen says
Crashing the system is a part of debugging, and in the past, developers on Windows were able to force a crash simply by using a keyboard shortcut.
Of course, this required a bit of registry tweaking beforehand, but for the longest time, this was a go-to method for many. However, this method no longer works since it’s not possible to automate this keystroke.
According toThe Register, the trigger for the crash is located in the input stack of the keyboard driver, which requires physical keys to be pressed.
This isn’t possible with modern debugging methods that fully automate this process. However, Mircosoft’s Raymond Chen has a workaround in the form of theNotMyFault tool from Sysinternals.
In case you’re not familiar, this tool can cause the system to crash, hang, or even produce memory leaks, and this can come in handy to developers.
Chen also advises against crashing critical processes such as winlogon.exe since they are getting reported to Microsoft thus causing Microsoft teams to analyze non-existing bugs.
Speaking of bugs are crashes, the latestKB5034763andKB5034765updates all have their share of crashes, and we hope that Microsoft will address them soon.
More about the topics:BSoD errors,crash
Milan Stanojevic
Windows Toubleshooting Expert
Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he spends most of his time learning about computers and technology.
Before joining WindowsReport, he worked as a front-end web developer. Now, he’s one of the Troubleshooting experts in our worldwide team, specializing in Windows errors & software issues.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Milan Stanojevic
Windows Toubleshooting Expert
Before joining WindowsReport, he worked as a front-end web developer. Now, he’s specialized in Windows errors & software issues.