[Release] sysCrasher

[RyDog]

sysCrasher is a little tool that I made out of boredom that forcefully closes a critical system process to cause your computer to crash and display a BSOD.
This tool should be safe, but I take no responsibility if your computer corrupts, dies, mutates or catches on fire.
This was built and tested on a Windows 10 machine... Not sure if it works below Windows 8 if not, I can add a new process to close that should BSOD on lower Operating Systems.
Video Showcasing this (sorry for bad quality)

 

[Deleted member 386348]

Why, though?

 

[Deleted User]

Why, though?

For fun, maybe?

 

[Deleted member 386348]

For fun, maybe?

I guess

 

[Luckkill4u]

so we give this to noobs who ask for wares?

 

[FaTaL_ErRoR]

so we give this to noobs who ask for wares?

Yeah exactly, give them a program called sys crasher. "They will mever suspect that"
That'll teach them.
@ OP where would this even be useful? (I am actually curious not being sarcastic with you)
I ask because one only needs to put a bad driver in to make thos happen without the need of an added program.
I dont feel like downloading thise but what exactly is your program doing to cause the blue screen?
I ask because if it causes the blue screen in a different way I would love to have your souce code. As it may be useable elswhere.

 

[Deleted member 386348]

Yeah exactly, give them a program called sys crasher. "They will mever suspect that"
That'll teach them.
@ OP where would this even be useful? (I am actually curious not being sarcastic with you)
I ask because one only needs to put a bad driver in to make thos happen without the need of an added program.
I dont feel like downloading thise but what exactly is your program doing to cause the blue screen?
I ask because if it causes the blue screen in a different way I would love to have your souce code. As it may be useable elswhere.

It closes a critically needed system process that results in a blue screen.

 

[RyDog]

Yeah exactly, give them a program called sys crasher. "They will mever suspect that"
That'll teach them.
@ OP where would this even be useful? (I am actually curious not being sarcastic with you)
I ask because one only needs to put a bad driver in to make thos happen without the need of an added program.
I dont feel like downloading thise but what exactly is your program doing to cause the blue screen?
I ask because if it causes the blue screen in a different way I would love to have your souce code. As it may be useable elswhere.

I'm closing the scvhost.exe process, and I used a batch to exe converter using this line of code:

taskkill /im svchost.exe /f

I created this because when I googled 'how to force a bsod in Windows 10' the only thing that came up was a 'CrashOnCtrlScroll' tutorial, where my laptop doesn't have that key and it was a hassle to get it done regularly... This is intended to be used as a prank though You hide this program in a hidden folder and make a shortcut to prank your friends
Or if you have a worst enemy, just make it so Windows automatically boots this script so it BSOD on boot

 

[RyDog]

Just tested this on a 8.1 virtual machine and all it does is softlock it, so I will add a new process to close to ensure a BSOD

 

[gudenau]

Uhm, figure out XP and we have a deal. Working on a stupid prank thing myself that targets that because reasons.

 

[RyDog]

Try this one. I'll test it on Windows 8

 

[Mega-Mew]

I have this error when I try to search an unknow value in the physical memory with cheat engine

 

[Joom]

Killing svchost shouldn't cause a BSoD on any system. That kinda doesn't make sense.

 

[RyDog]

Killing svchost shouldn't cause a BSoD on any system. That kinda doesn't make sense.

scvhost.exe hosts multiple services. Killing one of those processes is killing a critical service that is hosted by Windows.

 

[DarkGabbz]

For fun, maybe?

To put it in autostart on a school pc.

 

[Joom]

scvhost.exe hosts multiple services. Killing one of those processes is killing a critical service that is hosted by Windows.

Yeah, but that still shouldn't cause a BSoD, especially since svchost deals with handling network hosts. Watch it with a network monitor or verbose firewall and you'll see a lot of familiar outbound connections being made. For example, it handles Skype's binding of ports 80 and 443 and the associated traffic. Killing a process that has kernel hooks in place, however, would cause a BSoD (which is essentially a kernel panic).

 

[Link.]

FYI, Windows has the ability to BSOD from a kernel debugger or keyboard shortcut. This is actually supported and documented by Microsoft.

https://msdn.microsoft.com/en-us/library/windows/hardware/ff560324(v=vs.85).aspx
https://msdn.microsoft.com/en-us/library/windows/hardware/ff545499(v=vs.85).aspx

No support for XP, though. Sorry, gudenaurock.

 

[JustAKirby]

Yeah exactly, give them a program called sys crasher. "They will mever suspect that"
That'll teach them.

I mean, we could just rename it.....

 

[DarkFlare69]

Maybe put a less suspecting icon next time so we can troll noobs

 

[Joom]

Maybe put a less suspecting icon next time so we can troll noobs

Or change the icon yourself with something like Resource Hacker.