Realistically, what is the most PHYSICAL damage a virus could do to your computer?
>>62226851
It could thrash your hard drive. Probably not much damage at all.
>>62226864
>Spinning disks in 2017
>>62226851
if you can flash the bios you can make the sysem not boot. theoretically some laptops have a power management prosessor. you could over volt some parts if you reverse engender the board. its not worth it though.
>>62226876
>Implying SSDs don't have limited rewrites.
There was an exploit which let to explode macbooks battery.
https://arstechnica.com/gadgets/2011/07/how-charlie-miller-discovered-the-apple-battery-hackhow-a-security-researcher-discovered-the-apple-battery-hack/
If you can modify firmware, you can damage components badly.
>>62226882
>its not worth it though.
That's why OPs pic is old timey. They don't bother anymore but in olden times there were things that messed with your harddrive and they were much more frail than now.
>>62226851
op here is a gift https://en.wikipedia.org/wiki/Killer_poke
its a list of sanity checking failures on hardware.
>>62226851
Run everything at 100%, hope for PSU overdraw.
>>62226876
Show me a 3TB SSD which isn't overpriced. :^)
>>62226905
oh and here is a medical one as a bonus
https://en.wikipedia.org/wiki/Therac-25
It actually cooked people.
>>62226851
Overheat but turn off fan until it destroys itself.
Or set the refresh rate on your LCD to an incompatible rate over HDMI until the driver board erupts into flames.
>>62226851
Turn it into a bomb, & blow your family to smithereens.
>>62226851
exploding a van
up the multiplier and disable hardware reset in case of thermal overload
Brick your firmware
>>62226882
>reverse engender
>>62226876
>having limited rewrites in 2017
>>62228531
>he thinks spinning rust doesn't have limited writes
>>62227483
The start of the disgrace
Turn you into a pedophoile and make you go to jail, is physical damage
>>62226905
>Systemd mounts variables used by Unified Extensible Firmware Interface on Linux system's sysfs as writable by the root user of a system. As a result, it is possible for the root user of a system to completely brick a system with a non-conforming UEFI implementation (specifically some MSi laptops) by using the rm command to delete the /sys/firmware/efi/efivars/ directory, or recursively delete the root directory.