Troubleshooting: Crashes

Begin with the smallest reversible checks:

1. Close Minecraft and the Flarial Launcher completely, then restart both.
2. Confirm your Minecraft build is listed on Compatibility.
3. Disable the module or setting you changed immediately before the crash.
4. Test with default resource packs and without other injected DLLs or third-party overlays.
5. If the crash repeats, note whether it happens during launch, injection, world entry, combat, or a particular key press.

Reinstalling repeatedly is rarely useful until you have tested a fresh config and removed third-party conflicts.

If Minecraft crashes before you can turn off a module, temporarily reset the active config without deleting it:

1. Close Minecraft and Flarial.
2. Open %localappdata%\Flarial\Client.
3. Rename the Config folder to Config-backup.
4. Relaunch Flarial and reproduce the same action with the fresh config.
5. If the crash is gone, restore profiles one at a time instead of replacing the entire new folder.

This is the preferred recovery for crashes that begin after changing a font, keybind, visual option, or module setting. See Manage Configs for backup and import guidance.

If Minecraft freezes at launch or the logs mention DirectX/DX12, first disable Better Frames and VSync Disabler, restart the computer, and update the graphics driver from the GPU manufacturer.

Test again with default packs and without capture tools or overlays. Do not edit config internals or registry values as a first response. If the issue continues on a supported build with those modules disabled, include the full graphics error and GPU model in your report.

Flarial is not expected to run reliably beside another injected client or custom DLL. Reproduce the problem with only the official Flarial launcher and client loaded.

If that fixes the issue, add optional overlays or modifications back one at a time. Support may be unable to diagnose a crash that only occurs when another injector is active.

A module that fails on one Minecraft build may already be fixed or temporarily disabled in a newer Flarial release. Update first, then disable the affected module and test the same action again.

Common examples reported in older builds include Waila during world entry, Skin Stealer during use, combat visuals after a Minecraft update, and Better Frames during startup. Treat these as historical clues, not a current diagnosis. Check the changelog for the version you are using.

Include enough detail for someone else to reproduce the problem:

• Minecraft Bedrock version and Flarial version
• Windows version and GPU model when graphics are involved
• The last action before the crash
• Related enabled modules, packs, overlays, or custom DLLs
• Whether a fresh config changes the result
• The matching crash_*.txt report and relevant launcher/client logs

Review logs for personal information before posting them publicly. Send the report through Flarial support or the support area in the Flarial Discord.