The phrase "The PS3 application has likely crashed, you can close it" is the "Blue Screen of Death" for the emulation community. It is the moment where cutting-edge software hits the brick wall of complex hardware architecture.
Enable SPU Loop Detection: In the CPU tab, check this box to prevent certain infinite loop crashes.
Apply these general "safe" settings to see if stability improves: CPU Tab: Ensure SPU Decoder is set to Recompiler (LLVM). The phrase "The PS3 application has likely crashed,
Run as Administrator: Right-click the RPCS3 executable and select "Run as administrator" to rule out permission issues. Advanced Stability Settings
Orange (Ingame): The game runs but cannot be completed, or has massive performance/crashing issues. Apply these general "safe" settings to see if
: This is a frequent fix for crashes occurring during loading or shortly after starting gameplay. In Config > System and enable "Clear Cache automatically"
Happy emulating, and may your frametimes be steady and your shaders pre-compiled. : This is a frequent fix for crashes
Next he restarted RPCS3 and the game in diagnostic mode. The crash replayed at the same spot, reliably stubborn. That was good news; reproducibility meant a fix was possible. He toggled a few settings: async shader compilation off, frame limit synced to 60, and a different memory fetch strategy. One by one he eliminated variables. Each attempt taught him something: with shaders precompiled, the freeze moved later; with a lowered thread count, the audio desync vanished but the graphics hiccuped.
When the pop-up appears, you lose unsaved progress. However, RPCS3 autosaves emulator state?