Create bsod from user mode?

Is there any user-mode equivalent of KeBugCheck, or some other way of
causing a user-mode BSOD with a code that won't be easily confused with
anything else (like 0xE2)?

I have a hard-to-reproduce boot problem with a ps/2 keyboard filter
driver. If everything is OK then I have a user-mode app restart the
machine. If/when I can repro the problem I want something in user mode
that'll cause me to drop into Windbg.

(I know causing int3 will do it if I boot with /debug in boot.ini, but
because the machine runs unattended and reboots every 5 minutes I
wanted to try and use /crashdebug instead, so that when it goes wrong I
only get the info relevant to the boot that fails)

Maxim
Thu Aug 04 14:46:31 CDT 2005

Just press Ctrl-Break in WinDbg.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"clackmannan" <clackmannan@hotmail.com> wrote in message
news:1123176579.526249.241020@g14g2000cwa.googlegroups.com...
>
> Is there any user-mode equivalent of KeBugCheck, or some other way of
> causing a user-mode BSOD with a code that won't be easily confused with
> anything else (like 0xE2)?
>
> I have a hard-to-reproduce boot problem with a ps/2 keyboard filter
> driver. If everything is OK then I have a user-mode app restart the
> machine. If/when I can repro the problem I want something in user mode
> that'll cause me to drop into Windbg.
>
> (I know causing int3 will do it if I boot with /debug in boot.ini, but
> because the machine runs unattended and reboots every 5 minutes I
> wanted to try and use /crashdebug instead, so that when it goes wrong I
> only get the info relevant to the boot that fails)
>

clackmannan
Thu Aug 04 18:39:10 CDT 2005

Which would be fine, except the machine is running unattended and I'm
not there to watch it 24 hours a day. That's why I want to do it from
within an application ....

Pavel
Thu Aug 04 19:18:15 CDT 2005

Write a tiny driver that calls KeBugCheck and load it
from your application- or add private ioctl to your existing driver.

There still may be some ways to cause crash
from pure usermode, but next service packs can break them ;)

--PA

"clackmannan" <clackmannan@hotmail.com> wrote in message news:1123198750.844858.186190@g14g2000cwa.googlegroups.com...
> Which would be fine, except the machine is running unattended and I'm
> not there to watch it 24 hours a day. That's why I want to do it from
> within an application ....
>

clackmannan
Fri Aug 05 10:01:24 CDT 2005

Well, it's not pretty but I managed to do it by doing a
TerminateProcess() on WinLogon :-)

AFei
Fri Aug 05 12:52:14 CDT 2005


Capture the BSOD screen, show this picture as the top-most window and hide
mouse, filter keyboard inputs, make CPU 100% busy blah blah to make it looks
like real BSOD.... (just kidding.) :-D

"clackmannan" <clackmannan@hotmail.com> wrote in message
news:1123176579.526249.241020@g14g2000cwa.googlegroups.com...
>
> Is there any user-mode equivalent of KeBugCheck, or some other way of
> causing a user-mode BSOD with a code that won't be easily confused with
> anything else (like 0xE2)?
>
> I have a hard-to-reproduce boot problem with a ps/2 keyboard filter
> driver. If everything is OK then I have a user-mode app restart the
> machine. If/when I can repro the problem I want something in user mode
> that'll cause me to drop into Windbg.
>
> (I know causing int3 will do it if I boot with /debug in boot.ini, but
> because the machine runs unattended and reboots every 5 minutes I
> wanted to try and use /crashdebug instead, so that when it goes wrong I
> only get the info relevant to the boot that fails)
>