A customer was developing an automated test that required the system to suffer a blue screen crash. They configured their test systems to crash when the ScrollLock key is pressed twice while holding the Ctrl key, and they wrote a simple program that ran as administrator and injected the appropriate keystrokes. But no crash occurred. What did they do wrong?
↫ Raymond Chen
Does anyone here not love a Raymond Chen mystery?
“Please do not use sneaky tricks like terminating critical processes like winlogon.exe. These failures get reported through the Watson service as a winlogon.exe crash, which creates confusing among the winlogon.exe team as they try to identify the source of a nonexistent bug. ” — why, hello there (;
There’s no mystery here.
It’s pretty obvious from the documentation that the crash is to be triggered at the various input drivers level.
So it’s also obvious simulating inputs is not gonna work.
I’m sorry but no… this just isn’t interesting. My developing a custom login agent to meet end user login requirement specifications wasn’t interesting either honestly. It’s boring tedious and annoying.