Causing BSOD’s

I’m bored! So I’m posting this… If you want to play a “joke” on your friend and you are tired of those things that open and close the CD drive, and you want something more hardcore? I got the thing for you (lol) Actually all you need to do is call KeBugCheck and thats all.

#include “ntddk.h”
NTSTATUS DriverEntry( IN PDRIVER_OBJECT theDriverObject, IN PUNICODE_STRING theRegistryPath )
{
KeBugCheck(0);
}

If you tried it, and didn’t get a BSOD, only a crash, you have to change some settings in you computer. Goto Control Panel -> System -> Click the Advanced tab -> Click the last Settings -> Uncheck Automatically restart.

Free Image Hosting at www.ImageShack.us

If you want, you can also take a look at KeBugCheckEx

3 Responses to “Causing BSOD’s”

  1. Noz3001 Says:

    I prefer using the Hard Reboot method. (It seems GameGuard does too ;o )

    _asm {
    MOV AL, 0xFE
    OUT 0×64, AL
    }

    All your ports are belong to me.

  2. nog_lorp Says:

    Just cause you have auto-reboot on doesn’t mean you aren’t getting the BSOD, it just means it flashes for a second and then reboots :D . It is still a BSOD.

    How about a driver that disabled auto-reboot before BSOD’ing? :D Or perhaps (if feasible) generate a custom BSOD message – “A problem has been detected…
    … appears to be cause by this file: USER … ERROR_BETWEEN_SCREEN_AND_KEYBOARD”

    ~nog_lorp

  3. unlmtd Says:

    Yes, it is possible to make a custom BSOD. I’ll have to look into it though.

Leave a Reply