Crashes and Black Screen Fixes#

The Binding of Isaac: Rebirth crashes and black screens come with no error codes to look up — the clues are in log.txt in the save directory; most crashes stem from mods and corrupted configuration, and disabling mods, fixing the config, and verifying files — in that order — solves them.

First, what makes troubleshooting this game special: it has no numeric error code system. When it crashes, no error-code dialog pops up — instead the save directory generates a log.txt log and a .dmp dump file for investigation — so searching the web for “isaac error code” is basically a dead end; the right approach is to read the log and match your symptom. This page is based on the Steam version of Rebirth plus the Repentance DLC, and only collects failures whose causes and fixes the community has verified; every issue is tagged with its current status; no unsourced error codes or patch numbers will be invented here.

Quick Index: Find Your Section by Symptom#

Crashes Report No Error Codes — Where to Find Clues#

Short answer: both clues after a crash are in the save directory — log.txt records the game’s runtime log, and the .dmp is a crash dump file — this is the game’s only “error reporting”.

The default save directory location differs by platform:

After a crash, open log.txt in the same directory and focus on the last few lines — the log is appended over time, and the final block usually corresponds to the actions right before the crash. Build two habits while troubleshooting: change only one variable at a time before reproducing, and note the symptom after each change; you don’t need to understand the .dmp file itself — its existence only says “the game crashed”, and the real handling approach is covered in the sections below.

What to Do When Windows Crashes Immediately on Launch#

Short answer: most launch crashes are a corrupted config file or a third-party component conflict — deleting options.ini to reset the game to defaults solves most cases.

Follow these steps in order:

1. Close the game and enter the save directory listed in the table above;
2. Delete options.ini (personal settings reset, but saves are unaffected);
3. Relaunch the game to verify;
4. If it still crashes, open log.txt in the same directory and check the last lines to locate the cause.

If deleting the config doesn’t help, there are two more verified causes. First, the auto-updater of the community script extension Repentogon can corrupt game files — uninstall and reinstall Repentogon, or remove it completely and test. Second, one case was caused by a missing lua5.3.3r.dll runtime library file — putting it back into the game directory restored normal behavior. Both cases come from community troubleshooting threads in July 2024, where the posters confirmed the fixes above worked.

What to Do When the Game Crashes After Installing Mods#

Short answer: crashes after installing mods are almost certainly mod problems — especially outdated or broken item-modifying mods; set EnableMods to 0 in options.ini to disable them globally, then investigate one by one.

A typical scenario from community threads: a player crashed every time in the minecart section of Mines II, and the cause was finally traced to a mod. The tell-tale pattern is “crashes at the same spot every time” or “only started crashing after a certain mod was installed” — crashes this consistent call for a completely different approach than random ones.

Troubleshooting steps:

1. Open options.ini in the save directory;
2. Change EnableMods=1 to EnableMods=0 to disable mods globally;
3. Launch the game to verify it is back to normal;
4. Once mods are confirmed as the cause, re-enable them and test one by one — suspect item-modifying mods containing items.xml first — they edit the game’s item table directly and are the most likely to crash at the moment of entering a map when versions are incompatible.

Crashes when entering a map (rather than at launch) are almost always mod problems — this lesson comes from a community answer accepted in November 2023, and it is still the first thing to check. If you want mods but fear crashes, add one new mod at a time and enter a map immediately to test, so any problem is traced instantly.

What to Do About Launch Crashes on Steam Deck#

Short answer: Steam Deck launch crashes come down to two causes — mod conflicts under the native Linux path, and the runtime environment itself; handle it in the order of disabling mods, forcing Proton 8.0-4, and verifying file integrity.

Specific steps:

1. Switch to desktop mode and enter the Deck save directory given in this page’s quick index;
2. Open options.ini in a text editor, change EnableMods to 0, and return to gaming mode to verify;
3. If that fails, open the game’s properties page in Steam and force Proton 8.0-4 under the compatibility options;
4. If it still crashes, return to desktop mode and verify file integrity so Steam re-validates the game files.

This same procedure comes from a community answer accepted in November 2023; the three routes are ordered from cheapest to most expensive, and most Deck players stop within the first two steps with the problem solved.

What to Do When macOS 15.4 and Above Crashes on Launch#

Short answer: this is not your machine’s fault — verifying files, reinstalling, and changing launch parameters are all useless — the root cause is an outdated DRM loader inside the Steam client that is incompatible with newer macOS, and the most reliable fix right now is a community patch.

The technical details are worth spelling out: Apple-silicon (M-series) Macs run the game through Rosetta 2 translation, and at startup it loads Valve’s old loader steamloader.dylib; its dyld compatibility stub jumps to an unmapped memory address (0x7fff5fc01008) on macOS 15.4 and above, causing an immediate segfault crash. The problem broke out after the macOS 15.4 update in late March 2025, was pinned as a consolidated report on the official forums from May 2025, and affects 15.4, 15.4.1, 15.5, 15.7, and 15.7.2, while the various macOS Tahoe 26 versions behave inconsistently.

Verified fix:

1. Go to the GitHub repository isaac-afterbirth-macos-fix (an open-source project under the MIT license);
2. Download the ZIP and run the included install.command — the script configures the Steam launch entry automatically;
3. The patch can be uninstalled, and the author confirmed it works on macOS 15.7.3 with an M2 Max.

One-line summary: the official side has still offered no fix, and the community patch is currently the only verified working route. If your Mac is still on an older macOS and the game runs fine, think twice before upgrading.

Window Opens but Black Screen — No Picture#

Short answer: black screens share the same causes as launch crashes — corrupted config, mod conflicts, GPU drivers, or runtime library issues — so run through the launch-crash procedure; the only exception is translation layers.

Two cases:

1. Black screen on a normally installed Steam version: go back to the “What to Do When Windows Crashes Immediately on Launch” section and follow delete config, check Repentogon, disable mods, verify files — community support material explicitly attributes black screens to the same classes of problems as launch crashes;
2. Black screen when entering the Mirror levels of Repentance under translation layers like Crossover or Whisky: this is a rendering-level issue that only appears in unofficially supported environments; there is no official fix and no reliable community workaround yet.

An honest word for translation-layer players: the game’s official macOS support was limited to begin with, and a translation layer adds one more unofficial layer on top; rendering black screens in those setups are hard to fix with settings alone. If you can, prefer an officially supported native environment.

Save Wiped or Won’t Load#

Short answer: don’t rush to start a new save — the game keeps daily automatic backups, the save_backups folder in the save directory stores backups by date, and renaming a normal-sized backup back to the original filename and overwriting restores your save.

There are two verified causes of wiped saves: a crash or force-quit interrupting the save write, and Steam Cloud sync overwriting the local save with an older one. Early after Repentance’s 2021 launch there was a wave of wiped-save reports, and the studio said fixes and mod support would keep coming; the community also has long-standing “saves disappeared after installing Repentance” feedback, most of which was actually an illusion caused by the save file prefix switching from abp_ to rep_, or cloud sync conflicts — the saves were never really gone.

Recovery steps in priority order:

1. Open the save directory and go into the save_backups folder;
2. Find the backup from the day before the incident by date and pick one with a normal file size (skip 0-byte or obviously undersized files);
3. Rename it back to the persistentgamedataN.dat format and overwrite the same-named file in the save directory;
4. If backups fail too, retrieve the cloud save from Steam\userdata\<ID>\250900\remote\ and compare;
5. If the save is restored but unlocks are missing, open the stats menu and press Alt+F2 to trigger achievement sync and rebuild unlock progress.

One more warning: the studio has labeled Repentance+ online co-op as “Beta — may be unstable or even corrupt saves”; fortunately the game keeps save backups from before Repentance+; online mode rules and disconnect handling are on our Local Co-op page.

Tuning Low FPS and Scroll Stutter on Weak Machines#

Short answer: low FPS is mainly caused by the cost of render scaling and camera settings — changing two entries in options.ini brings clear relief; no rush to upgrade hardware.

Adjust in order:

1. Open options.ini in the save directory;
2. Set MaxRenderScale to 1 — directly lowers render scaling, at the cost of some visual clarity;
3. Set CameraStyle to 2 — reduces stutter in large-room scenes;
4. NVIDIA GPU users should set this game to “Prefer maximum performance” in the control panel.

Before you start, check whether the machine itself clears the bar against our System Requirements page: this 2014 game is extremely light (449 MB of storage) and even integrated graphics can run it — if even it drops frames, the problem is usually outdated drivers or background load, not insufficient hardware.

FPS Locked at 60 — Is It a Fault?#

Short answer: no, it is engine design — the game ties its game speed to the frame rate, hard-locked at 60 FPS; it cannot be unlocked normally and doesn’t need fixing.

The logic: game logic runs per frame — running at 120 FPS makes the whole game 2x speed, and locking to 30 FPS makes it half speed. The community’s high-FPS project also explicitly notes this is an engine design of “rendering hard-locked at 60 FPS, logic at 30 hertz”. Two practical takeaways:

• Don’t use third-party tools to force a different refresh rate or unlock the frame rate — game speed gets thrown off, which is a fault of your own making;
• The community does have frame-interpolation solutions, but they are unofficial; for smooth visuals you are better off accepting the native 60 FPS rhythm.

For speedrunners this design is actually a good thing: everyone’s game speed is identical, so timing is fair. Practice at the 60 FPS rhythm too; routes and planning are on our Speedrun Tips page.

Random Crashes Leaving Only .dmp Files#

Short answer: for crashes with no fixed crash point, the directions are permissions, antivirus, and third-party overlays; a .dmp file left behind by a crash is normal and does not mean the game files are broken.

Check in order:

1. Run Steam or the game itself as administrator;
2. Add the game directory to your antivirus whitelist — false positives killing runtime libraries are a common source of “random crashes”;
3. Turn off third-party overlays like Discord and test — overlays inject code into the game process, and compatibility with this game is not guaranteed.

This set of directions comes from a 2019 community troubleshooting thread and still applies to random crashes today. If all three steps are done and it still crashes, go back to the universal order at the top and start over — random crashes often need a combination of fixes.

Universal Troubleshooting Order: Cheapest to Most Expensive#

The consensus order formed by cross-referencing multiple community threads — follow it without skipping steps:

1. Disable mods: set EnableMods=0 and launch to verify;
2. Delete or edit options.ini: reset the config file;
3. Verify file integrity: run the file check on the game in Steam;
4. Check log.txt: read the last lines of the log before the crash;
5. Restore save backups: use save_backups to overwrite back to a good save;
6. Check permissions, antivirus, and overlays: run as administrator, whitelist, disable the Discord overlay.

The logic behind the order is rising cost: the first two steps take a minute, verifying files re-downloads a few MB to several hundred MB, and every software-level fix must be exhausted before touching saves. Most players’ problems stop within the first three steps; cases that reach step six without success usually need to ask for help in a community thread with log.txt attached, rather than blindly changing more settings.

Do These Problems Still Exist Today: One Timeline#

Two conclusions can be read from the timeline. First, the classic Windows issues (corrupted config, mod conflicts, permissions and overlays) have kept the same fixes for years — these are mature, stable procedures; just follow them. Second, the crash since macOS 15.4 is the only active problem with “no official fix, community patch only”; Apple-silicon users must confirm patch compatibility before upgrading. For version choices and platform differences, see our Price and Buying Advice page; for what the Repentance DLC changes, see the Repentance DLC page.

Related Guides#

• Beginner’s Guide — core mechanics, controls basics, and early survival
• System Requirements — platform requirements and graphics settings
• Price and Buying Advice — version differences, current prices, and when to buy
• Local Co-op — co-op rules and Repentance+ online mode caveats
• Repentance DLC — new content and mechanics changes in the DLC
• Unlocks Guide — all achievements and unlock conditions, paired with the achievement-sync trick