> For the complete documentation index, see [llms.txt](https://corrupt.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corrupt.wiki/systems/playstation-1/corrupting-the-psx.md).
# Corrupting the PSX
## Corrupting the PSX
### Introduction
Corrupting the PSX is quite complex when compared to NES and SNES, and can be more difficult than floating point based systems such as the GC/Wii, but it’s still quite feasible for beginners.
| Recommended setup: Vector Engine
Limiter: \_\[MIPS]\_AllBranches, Value: \_\[MIPS]\_AllBranches
Limiter: \_\[MIPS]\_AllBranches, Value: \_MIPS\_NOP
Limiter: \_\[AnySystem]\_AnyFixedPoint, Value: \_MIPS\_NOP
Recommended Intensity: 50-200
|
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
### Recommended Settings
For most games it is rarely ever worth messing with anything other than the MainRAM. The GPURAM will specifically target textures and sprites. The SPURAM will only mess with the audio, but doesn’t do much other than popping sound and maybe stuttering. BiosROM won’t do anything other than crash the system when corrupting a game. DCache won’t usually do anything worthwhile and the System Bus is simply all of these together.
\
For Vector Engine settings, any of the MIPS lists into MIPS\_NOP (same as Zero) will work most optimally. AllBranches also works into AllBranches as well as it does with NOP. You can also take the \_\[AnySystem]\_AnyFixedPoint (or Any32) lists and pair them with a NOP, but these will usually need very low intensity. In general we’re talking anywhere from 10 intensity to 200.
### Expected Results
Most of the effects you will notice when corrupting the PSX with the MIPS lists will affect the game’s logic, differently than the NES/SNES, where it is more common to get clown vomit and audio corruptions. Since games will often store audio, video and models using raw data, you can mostly affect the way they are rendered on screen, but hardly ever change their properties with lists alone.
|  | An example of texture corruption effects.
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
|  | An example of model/rendering corruption effects.
|
|  | An example of code corruption effects. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://corrupt.wiki/systems/playstation-1/corrupting-the-psx.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.