Game freeze – bulbapedia, the community-driven pokémon encyclopedia electricity usage


Game freezes can occur due to the lack of information input into the game, such as when walking out of the boundaries of an area. They also occur when performing glitches such as the Mew glitch incorrectly. Older cartridges and systems are also more prone to freezing than newer ones. The most common cause of a game freeze is the game being given too many tasks at once. For instance, there is a higher probability of the game freezing when the player tries tweaking. Incorrect cheat codes used on cheating devices such as Action Replay or GameShark can result in game freezes. On rare occasions, incorrect cheats may possibly render the save file unplayable and permanently damaged.

The game may also freeze if it is dropped, hit by any major force, has a dirty game cartridge/card, has been physically removed from the slot, or even if it is played on a faulty system (such as a Game Boy Color with low battery level). Game freezes are not limited to handheld systems, and it is possible for some home consoles to freeze up during gameplay. Leaving out of bounds by using the walk through walls glitch/cheat also freezes the game. A Game Boy Advance Pokémon game may freeze if the GBA itself is shocked by static electricity.

Game freezes are often accompanied by an odd buzzing sound; however, sometimes the normal music for wherever the player was before the game froze can be heard. Frequently, a loop or constant replay of whatever sound was being played prior to the freeze will be played. Sometimes, a freeze will play no sound, even if there was a sound being played before the freeze. In very rare cases, the music (and not the remaining sounds) can be the only thing to freeze, leaving the game still playable. Sometimes game freezes are accompanied by garbled sprites, various vertical lines and other scrambled graphics pixels and/or tiles.

The game may occasionally freeze while playing some copies of Ruby and Sapphire when a player’s Pokémon uses Thunderbolt or Thunder, or when fleeing from a wild Pokémon; however, cases of the glitch actually occurring are exceedingly rare. The problems caused by the glitch occurring can be rectified by turning off the battle effects. The moves only cause a temporary repeat of the sound, and it will go away if the Pokémon taking the damage is defeated.

Certain glitches do not cause the game to outright crash, but rather make it so that no buttons have any effect despite the game continuing to function in other ways. Examples of this include the music still being played, sprites still being animated, and NPCs continuing to move. All inputs fail to work and the player must reset the game.

• In Generation I, a level 1 Pokémon or a level 171 using Psywave will cause the game to softlock. The level 1 soft lock occurs as the game attempts to generate a random number between 0 and 1.5 × the user’s level (rounded down). No such number exists (floor 1×1.5 is still 1), preventing the game from continuing. Similarly, 1.5 × 171 = 256 (0x0100), but because the game only retains the least significant byte, it treats the product as 0. [1]

• Another division by 0 is while battling another Pokémon, if the attacker’s Attack or Special stat is higher than 255 and the defender’s Defense or Special stat, respectively, is lower than 4. Or if the defender’s current Defense or Special stat is 512 or 513 and the defender has used Reflect or Light Screen. Also if its current Defense or Special stat is 514 or higher when Reflect or Light Screen, respectively, is up, it will be treated as if it was much lower due to a roll-over glitch.

• The Pewter Gym skip glitch allows the player to bypass the person blocking the path out of Pewter City prior to defeating Brock and then talk to him from the right side, an action the developers did not anticipate. As the path the person walks is dependent on the side the player talks to him from, the game attempts to look up a path based on the player’s coordinates. Specifically, the game looks in the memory and tries find the coordinates (y=16, x=36 or hex:10 24) at an address ending in 2, 6, A or E. It then executes a path based on a two byte pointer following the coordinates, but the game may seemingly never find the coordinates at an applicable address and soft lock.

This is caused when a "rst 38" instruction is run in Generation I. Most of the RAM is corrupted during this freeze being replaced with "00 39" and the save file will disappear without a "the save data was destroyed!" message if the player was in SRAM bank 1.