bsod

I was reading a while ago somewhere online that you could make a custom BSOD. I don't remember where but I know it had something to with calling HalDisplayString which would switch to the bluescreen and print a message. I tried calling HalDisplayString from a simple driver but nothing happens. I was wondering if anyone could point me in the right direction. Here is the code to the driver. #include "ntddk.h" #include "wdm.h" NTSYSAPI VOID NTAPI HalDisplayString( PCHAR String ); NTSYSAPI VOID NTAPI NtDisplayString( PCHAR String ); DRIVER_INITIALIZE DriverEntry; NTSTATUS DriverEntry( __in struct

I was getting bored with my XP box one day, so I decided to try some of the answers to this question to see if any of them would cause a BSOD. They didn't, and they seemed like they would be the most likely to do that, so I was wondering if it is possible to trigger a BSOD from user-mode in C/C++, and if so, how? It seriously difficult to make a BSOD from user mode unless the user mode program interacts with buggy drivers (may be a particular sequence of operations can reveal the bugs in particular driver) disturbs the driver stack. From user mode, the inputs are validated well before passing

I have an application that sometimes causes a BSOD on a Win XP machine. Trying to find out more, I loaded up the resulting *.dmp file (from C:\Windows\Minidump), but get this message when in much of the readout when doing so: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ******************************************

I am trying to make a program that records a whole bunch of things periodically. The specific reason is that if it bluescreens, a developer can go back and check a lot of the environment and see what was going on around that time. My problem, is their a way to cause a bluescreen? Maybe with a windowsAPI call (ZeroMemory maybe?). Anywhoo, if you can think of a way to cause a bluescreen on call I would be thankful. The computer I am testing this on is designed to take stuff like this haha. by the way the language I am using is C\C++. Thank you You can configure a machine to crash on a keystroke

Purely for academic reasons. is it possible to programmatically cause a BSOD to occur under windows xp/windows 7 in C#/.NET. I'm suggesting there's got to be some dirty hack, or some vulnerability to abuse to cause this. I'm looking for a snippet of code to run that guarantees a BSOD in a finite period of time. Killing process "csrss.exe" causes BSOD. But you need Administrator privileges to do this. I'm not sure there is a way to do this purely with restricted privileges. EDIT: Yep, it works alright. I cooked myself a nice little BSOD :) System.Diagnostics.Process.GetProcessesByName("csrss")

I was looking for a way to simulate pressing the right Ctrl key in C#, it must be the right one. I know this can be done for the left one but I couldn't find anything on the right one. It is so I can simulate the key press for the manually triggered bsod. Thanks Reniuz You can use keybd_event event to simulate right Ctrl key press. [DllImport("user32.dll", SetLastError = true)] static extern void keybd_event(byte bVk, byte bScan, int dwFlags, int dwExtraInfo); public const int KEYEVENTF_EXTENDEDKEY = 0x0001; //Key down flag public const int KEYEVENTF_KEYUP = 0x0002; //Key up flag public const