MEmu crashing or freezing
A MEmu crash usually comes from a bad graphics mode. Switch the renderer, set the CPU cores, then reboot the instance.
Which crash you have
MEmu freezes in two different ways, and they need different fixes.
| What happens | Likely cause |
|---|---|
| Freezes at the loading bar, never reaches Android | Renderer does not match the GPU driver |
| Boots, then freezes after a few minutes of use | Instance is short on CPU cores or RAM |
| Crashes when a specific app opens | App needs ARM translation or a 64-bit instance |
| Whole window closes with no message | GPU driver crash or a corrupted instance image |
Freezing at the loading bar is by far the most common, and it is a renderer problem rather than a hardware problem.
Change the renderer
- Close MEmu and every running instance.
- Open MEmu Multi-Manager, click the wrench icon on the instance.
- Under Graphics, switch Rendermode from DirectX to OpenGL, or the reverse. Keep ASTC off unless a specific game asks for it.
- Under Performance, set CPU cores to 4 on a desktop (2 is enough on a laptop) and RAM to at least 3072 MB.
- Save, start the instance, and watch whether it gets past the loading bar.
If it boots with OpenGL but not DirectX, your GPU driver is the real problem — update it before switching back.
Stop it freezing during play
Instances that survive the boot and then lock up are running out of headroom. Give the instance its own CPU cores rather than sharing them with a second instance, and close browser tabs during long sessions. On 8 GB machines, two simultaneous instances is the practical limit.
If the instance image itself is broken
A corrupted image cannot be repaired from settings. Create a new instance in Multi-Manager, install only the app that matters, and keep the old one until you have copied any data out. That is faster than chasing a crash that happens in the same place every boot.