SYS 49152

>>4094021
You know you can POKE something that will literally make the machine smoke and die?

>>4094241
Spoilers pls.
I'm peeking but not poking.

>>4094021
Only useful if you loaded a assembly program into that area of Dec 49152 or Hex $C000

>>4094021
I'm not aware of a "deadly" poke so to speak.
But crashing the system was extremely easy (like with all home computers)

POKE 1,0
And the system hangs, because you turned off the BASIC rom area and the BASIC interpreter that is interpreting the peeks and pokes, so you pretty much swept away the carpet under your own feet.
http://sta.c64.org/cbm64mem.html

>>4094851
I never dared to do it but I know it exists for a fact.

>>4095061
Maybe, but not for the C64 itself:
https://translate.google.com/translate?sl=auto&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=https%3A%2F%2Fwww.c64-wiki.de%2Fwiki%2FKiller_Poke&edit-text=&act=url

Stuff to control the periphery (especially disk and tape drives) may indeed either break it or wear it down quicker, like banging the drive head against the stop by software (like some program did to produce disk drive music using the motor).
But I don't think that there is a Poke that bricks a C64 (since the system software ran straight from the ROM without a method to break it). Usually stuff like that can just be resolved by turning the C64 off an on (or if you have one) using the reset button.

https://en.wikipedia.org/wiki/Killer_poke
But stuff like the Killer Poke for the Commodore PET to kill it's build-in monitor are still relevant today in modern hardware.

If I remember correctly the story behind this Commodore find is that it was still being used to balance tires digitally in an auto repair shop sometime in 2014, don't know much after that

>>4095117
Yeah, I know about the killer POKE urban legend, but this one's real, it won't be instant, but it will smoke after a few minutes. It will kill one of the chips in the chipset.