Donkey Kong Country 2 / GAME HISTORY

Can DKC2’s Castle Crush Glitch Really Destroy a Cartridge?

The screen can break up and saves can disappear. That does not mean the game has rewritten its ROM chip.

By Patchlo Editorial Desk · Published October 21, 2026 · Sources checked October 21, 2026

Scope: SNES Donkey Kong Country 2: Diddy’s Kong Quest. Behaviour can depend on game revision and the state reached by the glitch; no claim is made for the GBA remake.

Does resetting the SNES fix a corrupted save?

The alarming part is what happens after you switch the console off. A normal crash disappears when the game starts again. A value written into battery-backed save memory can remain there. That is why a software fault can look like a permanently broken copy even though the program stored on the ROM chip is unchanged.

In a 2012 demonstration, CoTeCiOtm reported the glitch on a real SNES. The creator separately compared working and damaged save files from an emulator and found one changed byte in that particular test. Changing it back restored that save. It is a useful report, not proof that every run changes the same byte. [1]

Does the glitch damage ROM, SRAM or the cartridge?

The corrupted display and possible save loss are real reasons to avoid trying it on a copy with progress you care about. They do not establish melted components or an erased ROM. Nor does switching the power off necessarily repair corrupted saved data. The bug’s reputation mixed a genuine persistent data problem with a much stronger hardware claim.

Does the same warning apply to the GBA remake?

Do not treat every release as the same program. Super Mario Wiki lists the Castle Crush problem for the SNES game and some rereleases, while distinguishing the GBA and Wii Virtual Console versions. This article concerns the original SNES bug; it does not show that a similarly named level in another release has the same fault. [3]