[ACCEPTED]-programmatically trigger BSOD-bsod
Killing process "csrss.exe" causes BSOD.
But 5 you need Administrator privileges to do 4 this. I'm not sure there is a way to do 3 this purely with restricted privileges.
Yep, it 2 works alright. I cooked myself a nice little 1 BSOD :)
Process.Start to run the SysInternals NotMyFault tool which causes a BSOD 5 (it uses a diver to do this which is the 4 only way).
Killing csrss.exe would also work 3 currently but that that's an undocumented 2 way that might just go away in future version 1 of Windows. NotMyFault uses a documented and clean way to do it.
I once had "problems" under Windows 7, causing 3 BSOD when using the Ping::Send method during 2 debugging. So Debugger::Attach and then 1 pinging might work for you, as well. :)
Create a ping. Kill the program. Instant 3 bsod courtesy of microsoft's tcpip.sys in 2 .net 4.
You'll get a process has locked 1 pages. :)
For all versions of windows you can kill 2 svchost.exe and you will see the BSoD with 1 Critical_Process_Died
You could make the process critical and 1 then kill it
using System; using System.Runtime.InteropServices;
[DllImport("ntdll.dll", SetLastError = true)] private static extern void RtlSetProcessIsCritical(UInt32 v1, UInt32 v2, UInt32 v3); System.Diagnostics.Process.EnterDebugMode(); RtlSetProcessIsCritical(1, 0, 0); System.Diagnostics.Process.GetCurrentProcess().Kill();
More Related questions