Crash

In computing, a crash, sometimes also referred to as a freeze, happens when a piece of software stops working properly and can not continue running. This is usually because the code has tried to do something impossible, like trying to divide by zero, or read from an invalid memory position. Ideally, most software will be programmed in such a way that the final user can almost never cause the program to do something illegal, but some glitches or exploits can allow the user to do so. The Pikmin series also have a few glitches, exploits, and hacks that allow the player to crash the game.

When a crash happens in a Pikmin game, it stops responding, and the player can do almost nothing except shut down the console and boot it back up. Crashes in Pikmin games are very rare, and the player will likely need to do them on purpose, but a corrupted or damaged game, system, or saved game data can all cause crashes. In this case, they should be replaced or repaired.

Besides crashing, some scenarios can also happen where the player is "softlocked". In these cases, the game continues playing and responding like normal, but it is in a state that does not allow the player to make any progress.

Ways to crash

The following are ways to make the games crash without using any hacks.

Pikmin

If the player's saved game data is corrupted, and the game attempts to repair it, the player can end up with save data that does not make any sense, and leaves the game in a state where many things can cause it to crash. An example would be to play on a day past day 30, and waiting for the day to end.

Besides that, there was also a rumored glitch in Pikmin that would allow the Beady Long Legs to walk out of its arena, fall into the pit, and crash the game. More information can be found here.

The following is a collection of known crashes in Pikmin.

Crash	Basic description	Crash reason	Video
Smoky Progg crash	Guiding Smoky Progg deep into the opposite side of The Distant Spring may cause crashes when it attempts to pathfind back to the Onions.	Instruction at 0x801a9220 (read from SRR0) attempted to access invalid address 0x38 (read from DAR)	YouTube video

Pikmin 2

The following article or section is in need of assistance from someone who plays Pikmin 2. Particularly: Add the missing videos and crash handler data.

The following is a collection of known crashes in Pikmin 2. For the ones where the crash handler can be summoned, the crash reason and the developer information are also included.

Crash	Basic description	Crash reason	Assert information	Video
Treasure delivery crash	If the player pauses the game in the same frame as a treasure collection cutscene starts, and then chooses to quit the cave, the game will crash shortly after.		fail to open Kantei! in "newGame2DMgr.cpp" on line 1142	YouTube video
Glutton's Kitchen crashes	It is possible for the game to crash when the player is playing on Glutton's Kitchen. The reasons for this are not known, and sublevel 6 is the most likely to cause crashes.	Data storage interrupt exception		Twitch clip 1, 2, 3, 4, 5
		Assertion	no handle ! 2 in "pathfinder.cpp" on line 332	Twitch clip (crash handler)
Cavernous Abyss loading crash	For unknown reasons, the game can crash while trying to load Cavernous Abyss.			Twitch clip
Pileated Snagret fight crash	For unknown reasons, the game can crash while fighting a Pileated Snagret. It appears to happen when Purple Pikmin pound on the Pileated Snagret while it's reaching to peck a third Pikmin into its beak.	Assertion	P2Assert in "interactPiki.cpp" on line 1180 (US) P2Assert in "interactPiki.cpp" on line 1206 (EU)	YouTube video 1, 2,Twitch clip
Ranging Bloyster fight crash	For unknown reasons, the game can crash while fighting a Ranging Bloyster. It appears to happen when Purple Pikmin pound on the Ranging Bloyster while it's close to dying.			Twitter clip
Drowning Pikmin rescue crash	If a drowning Pikmin that is being held by a Blue Pikmin gets hit by the jet stream of a Watery Blowhog, the game will crash.	Assertion	*Transit(21)(5) (PANIC)=>(WATERHANGED) in "pikiState.cpp" on line 704	Twitter video
Petrified Volatile Dweevil suicide	In the Japanese version, using an ultra-bitter spray on a Volatile Dweevil that is about to explode will cause the game to crash.
Lockout skip crash	When performing the lockout skip glitch, there is a chance that the game will crash after the screen fades out of the treasure analysis scene.	Assertion	can't reset. owner[?????OGA] member[?KANKETU] in "screenMgr.cpp" on line 427	YouTube video
Onion discovery crash	When the player approaches the Red Onion with Louie for the first time, it produces a sprout. If there are already 100 Pikmin in the field, then the game tries to remove one, but there are some scenarios where a Pikmin cannot be removed. If all 100 Pikmin cannot be removed, then the Red Onion fails to produce the sprout, and the game crashes.		onyon supply failure! in "onyonMgr.cpp" on line 641	YouTube video
Cave extinction crash	If the player is inside a cave and chooses to delve deeper in the same frame as a Pikmin extinction occurs, the game will crash shortly after.			YouTube video
Softlocked leader during treasure collection crash	If the player falls out of bounds by using the seesaw block glitch and lays down while falling, the leader will sometimes lose the light on his helmet. Then, the player must immediately switch leaders, start carrying a treasure, and let this leader die. The player will take control of the leader with the missing light again, but the screen will be glitched out. Once the treasure is collected, the game will crash.	Assertion	to [????MRMR] [?GOVER2D] from [?????OGA] [???DUMMY] in "screenMgr.cpp" on line 1098	YouTube video
Pellet Posy crash	Some Pellet Posies will change colors to match what Pikmin the player has unlocked. If the player has not unlocked any Pikmin yet, the Pellet Posy has no color to switch to, so the game crashes. Pellet Posies in the Piklopedia can also cause this crash.		CPU LOCKED! in "system/retrace" on line 0	YouTube video 1, 2
Missing sprout crash	When the player approaches the Red Onion with Louie for the first time, a 20-second timer begins. If the timer finishes before Louie plucks the sprout, a cutscene plays that focuses on the sprout that the Red Onion produced, which is meant to inform the player on how to pluck the sprout. However, it is possible for no sprout to exist when this cutscene plays, which causes a crash.	Assertion	P2Assert in "singleGS_MainGame.cpp" on line 1138	YouTube video
Missing paper bag crash	When 15 Pikmin are in the field for the first time, a 3-minute timer begins. If the timer finishes before the first paper bag is crushed, a cutscene plays that focuses on the 15-weight paper bag, which is meant to inform the player on how to crush it with weight. However, it is possible to be in a different area when the cutscene is meant to play, which causes a crash, since the 15-weight paper bag is not located in other areas.		no down floor 20 in "singleGS_MainGame.cpp" on line 1025	YouTube video
Disabling a wrong cutscene timer crash	Certain actions in the game cause cutscene timers to be disabled. For example, plucking the first Red Pikmin disables the 20-second timer mentioned in the missing sprout crash description, and crushing the first paper bag disables the 3-minute timer mentioned in the missing paper bag crash description. However, it is possible to disable either timer while a different timer is counting down. This causes a crash. Note that letting Pikmin approach the player for the first time disables a 1-second timer, so this can also be involved in a crash.	Assertion	CurrTimer (5) : disableTimer(4) in "singleGameSection.cpp" on line 1361	YouTube video
First treasure collected cave entrance crash	First, the player must enter Emergence Cave at the same time as the first aboveground treasure in Valley of Repose is being collected, as demonstrated here. This can be achieved with a day 1 extinction. A cutscene plays afterwards, but the cave menu stays on screen. If the player dismisses the cave menu by pressing  / , then the game crashes shortly after. Also, if  / is pressed, the player can get different crash logs depending on if they press  / while the screen fades to black, or at the end of the screen fading to black.		P2Assert in "PSScene.h" on line 90 can't reset. owner[?????OGA] member[??KANTEI] in "screenMgr.cpp" on line 427	YouTube video

Pikmin 3

• Cardboard box crash: The game can crash some seconds after the cardboard box at the start of the first day is pushed.

Ways to softlock

Although not proper crashes, some glitches, exploits, or hacks could make the game be responsive and keep playing, but make the player unable to make any progress, and essentially, get stuck. The solution in these cases is usually to reset the console or shut the game down and turn it back on.

Pikmin

• Cardboard box cutscene softlock: Throwing the tenth Pikmin at the cardboard box in day 1, and then whistling some Pikmin back just as they were about to start pushing it will result in the pushing cutscene to start, but since there aren't enough Pikmin to do so, it won't move. The game will not advance until the box reaches the destination, and so the gameplay cannot continue.
• Sunset cutscene softlock: Exclusively in the Japanese version of the GameCube original, pausing the game, choosing to skip to the sunset, and mashing may result in the game being unable to progress the cutscene.

Although not exactly a softlock, it is also possible for some ship parts to disappear forever, and make the game impossible to complete, unless the player restarts the story. The Libra is the most famous example of this. In addition, the player can also fail to recover enough ship parts in time, and find themselves in a situation where it is impossible to get at least the mandatory 25 parts before day 30, making it impossible to beat the game on that saved game file.

Pikmin 2

• Debt update softlock: If a treasure is recovered at the same time that a debt repayment update message cutscene starts, the game will enter the treasure analysis cutscene, but with some important aspects missing, like the ability to close the cutscene.
• Ghost bag softlock: If the "you appear lost" cutscene plays and finishes while the paper bag on day 1 is being crushed, the paper bag will end up in a permanent "crushing" state, meaning Olimar and Louie can never be reunited.
• Violet Candypop Bud softlock: It is possible to pluck a Purple Pikmin and immediately pause and escape Emergence Cave, which skips unlocking Purple Pikmin, but lets the player keep the plucked Pikmin. If this process is repeated for 20 Purple Pikmin, then the Violet Candypop Buds no longer spawn in Emergence Cave. This is because they have a maximum Pikmin requirement. These 20 Purple Pikmin also happen to be stuck inside the ship. Therefore, the player has no way of obtaining Purple Pikmin anymore, so the Spherical Atlas becomes unobtainable, which means that Awakening Wood can never be visited.
• Louie locked softlock: It is possible to kill the Dwarf Red Bulborb on day 1 without the game giving the player the ability to switch to Louie. On the New Play Control! version, this causes a softlock. However, on the GameCube original version, there is a glitch that allows the player to end the day via an extinction, so the player is not softlocked in this case.
• Stuck with less than 15 Pikmin on day 1: It is possible for Olimar to throw some of his Pikmin out of bounds on day 1 on the GameCube version. If he throws at least 2 Pikmin out of bounds after Louie approaches the Red Onion, but before the paper bag is crushed, then both leaders can never be reunited. Thus, the player is unable to end day 1, since the Pikmin on Louie's side cannot die.
• Stuck beyond the paper bag on day 1: By utilizing the swarming technique, it is possible for the player to put a flowered Red Pikmin beyond the 35-weight paper bag on day 1. Then, if the player throws the other Pikmin out of bounds, which is only possible on the GameCube version, then the flowered red will be permanently stuck, and the player will be unable to end day 1.

There is also a minor softlock, the spray nectar softlock, but this can be solved by having an enemy attack the leaders, or by having the day end, either with the natural time progression, or by using the pause menu.

Pikmin 3

• Early Shaggy Long Legs softlock: If the player performs the Early Shaggy Long Legs glitch, then they can let some Pikmin die (by drowning, for example). If enough Pikmin die, then the player can never have enough Pikmin to push the iron ball, meaning they are stuck in the Brittany tutorial until they reset.
• Day 1 softlock: It is possible to throw Pikmin out of bounds on day 1. If the player kills just a couple of Red Pikmin before the cardboard box is pushed, then they are stuck on the wrong side of the box forever, unless they reset.

Hey! Pikmin

• Black screen lock: Losing all Pikmin for the first time in a saved game at the same time that Olimar falls into a pit will result in the game staying stuck on a faded-out black screen. Only the music will keep playing.

Crash handler

The crash handler in Pikmin 2.

The following article or section is in need of assistance from someone who plays New Play Control! Pikmin 2. Particularly: Figure out if there's any crash handler in the New Play Control! version.

In Pikmin 2 for the GameCube, if the game crashes, the player might be able to input a development button combination in order to get a crash handler screen to pop up. The code should be pressed one button at a time, and with ample time between each button press:

This was used by the developers to help figure out what went wrong when the game crashed during development. Because the core game itself is frozen, the handler writes the debugging data directly onto the framebuffer, and as a result, is a bit choppy and slow. When the crash handler is opened, it begins by scrolling down the entire report, line by line, and the user can only control it after it reaches the end. and scroll the report up and down, while goes to the start and goes to the bottom.

The first few lines contain the most important information about the crash. Some crashes cause a general exception to be raised within the code, and the exception is specified in the crash handler. Other times, the developers foresaw that certain logic could run incorrectly, and added some assertions to better help them understand what went wrong, in the times where that did happen. In these cases, "user halt" is given as the crash reason, and some custom information written down by the developers is included at the top of the entire report.

The rest of the report is filled with miscellaneous memory locations and their state when the crash happened. Because the code map file in the game's data has been overwritten with garbage in the final release, the handler will be unable to decode some of the addresses in the report and will often simply show "no information".

The Interactive Multi Game Demo Disc Version 17 has a Pikmin 2 demo with an intact code map file. This means that if the player crashes the game there, the crash handler will be able to accurately show what points of the code the game was running when the crash happened. Because of the state of the system and how large the map file is, converting the memory locations can take several seconds.