Crash and Black Screen Fixes#

The PC version of Elden Ring launches only through Steam, and the launch process is verified by the EasyAntiCheat anti-cheat system (EAC for short below), so its crashes and black screens have distinct platform traits: crashes cluster at the launch stage, mainly showing as a white or black screen followed by a bounce back to the desktop. The developers never published a specific error-code list, and community tutorials mostly describe symptoms, so this page organizes troubleshooting by “symptom” rather than “error code.” Everything below is based on community tutorials and official patch notes verified before 2026-10-15 — match your own symptom to the right section.

Quick Lookup: Find Your Section by Symptom#

Check the table below for your symptom first, then jump to the matching section — no need to read top to bottom.

White-to-Black Screen at Launch, Then Crash to Desktop: Anti-Cheat and Overlay Conflicts#

These crashes are mostly tied to the anti-cheat service conflicting with background overlays. Close the in-game overlays of Steam, Discord, and the like first, then repair the anti-cheat service — that alone resolves most launch crashes.

This was the most typical problem around the game’s launch (around March 2022) and is still the community’s first troubleshooting item today. EAC verifies the game process at startup, while overlay tools inject rendering code into the game window — when the two conflict, you see a white screen turn black and then a straight bounce back to the desktop. Troubleshoot in two steps.

Step one, disable the overlays that conflict with EAC one by one. Six confirmed conflict sources:

• Steam Overlay: Steam Settings → In-Game, uncheck to disable;
• Discord Overlay: Discord Settings → Game Overlay, toggle off;
• MSI Afterburner and its companion monitoring tool RivaTuner;
• NVIDIA GeForce Overlay;
• Xbox Game Bar;
• Floating windows of other recording and monitoring tools.

Step two, repair EAC itself. If you still crash with all overlays closed, follow this sequence:

1. Open the EasyAntiCheat folder in the game’s install directory;
2. Right-click EasyAntiCheat_EOS_Setup.exe inside and run as administrator;
3. In the popup window, select “Repair Service” and run it;
4. Restart the game afterward to verify.

If Repair Service doesn’t work, delete the entire EasyAntiCheat folder, go back to your Steam library, run “Verify integrity of game files” for the game, and the client will re-download the anti-cheat files. This combination has been community-verified for years — players were still using it in 2026 to fix launch crashes on high-end machines.

Endless Hang After White/Black Screen at Launch: Antivirus Interception#

When the screen goes white or black but the game hangs forever instead of bouncing to the desktop, an antivirus is usually blocking the anti-cheat process in the background. The community mass-confirmed in March 2024 that Malwarebytes was the main culprit; quitting it or disabling its protection modules lets the game start normally.

Unlike the “crash to desktop” in the previous section, a hang means the game window stays black — no error and no exit. Starting March 9, 2024, a wave of identical reports flooded the Steam community, eventually pinning down that Malwarebytes’ real-time protection interferes with EAC’s launch flow. Two ways to handle it:

1. The most direct: fully quit Malwarebytes, then launch the game;
2. Keep the software but disable its protection modules: in its settings, turn off the following four modules before launching — Malware & PUP Protection, Ransomware Protection, Exploit Protection, and Web Protection.

This finding was still being included in community troubleshooting tutorials in January 2025, showing the conflict is long-lived. If you use other security software with the same symptoms, the approach is identical: test “fully quit, then launch” first — if the game starts, it’s a protection-module conflict, and adding the game directory to the whitelist finishes the job.

The Universal Black-Screen Troubleshooting Order#

For a black screen with no error at all, troubleshoot from cheapest to costliest: verify game files first, then adjust permissions and launch method, then check GPU selection, and finally update drivers. The six steps below cover the most effective community remedies — run them in order:

1. In your Steam library, right-click the game → Properties → Installed Files → Verify integrity of game files;
2. Set “Run as administrator” for both eldenring.exe and start_protected_game.exe (the anti-cheat-protected launcher) in the game directory;
3. On the same properties page, try running in compatibility mode;
4. Add -windowed to Steam launch options to start in windowed mode, ruling out a fullscreen initialization failure;
5. Open Windows “Settings → System → Display → Graphics” and assign eldenring.exe the “High performance” GPU;
6. Update your graphics driver to the latest version.

Step 2 is easy to skip for start_protected_game.exe: the game’s normal launch goes through this protected entry — elevating only eldenring.exe without it can still fail at the anti-cheat verification stage. Only update drivers after the first five steps fail, and reboot once after installing the driver before testing.

White-Screen Crashes from Windows 11 Using the Integrated GPU#

On dual-GPU machines, Windows 11 may launch the game on the integrated graphics card, causing white-screen crashes outright. Assigning the game to the high-performance discrete GPU in the system graphics settings fixes it; dual-GPU owners can also disable the integrated GPU in Device Manager.

The mechanism: processors in laptops and some desktops come with integrated graphics, and the system defaults to “let Windows decide” GPU assignment — occasionally assigning Elden Ring to an underpowered integrated GPU, which white-screen crashes when the game initializes the graphics pipeline. Steps:

1. Open Windows “Settings → System → Display → Graphics”;
2. Click “Browse,” select eldenring.exe in the game directory, and add it;
3. Click the entry → Options → choose “High performance,” save, and restart the game.

If that fails, dual-GPU machines can disable the integrated GPU directly under “Display adapters” in Device Manager and launch the game, restoring it afterward if desired. Community tutorials listed this as the first-choice fix for Windows 11 white-screen crashes in both 2024 and 2026; discrete-GPU-only users can skip this section.

Mid-Game Crashes with No Warning#

When the game suddenly crashes mid-session with not even an error popup, the cause is usually drivers, missing runtimes, or background conflicts. Work through the five ideas below and the vast majority of mid-game crashes trace back to one of them:

1. Update the graphics driver to the latest version, reboot, then re-enter the game;
2. Complete the DirectX and VC++ runtimes — machines missing components crash more readily after long sessions;
3. Use Steam to verify game file integrity, repairing files deleted or corrupted by security software;
4. Close background programs — recording tools, performance monitors, network boosters, and antivirus — then test;
5. Check the install path: if it contains non-English or special characters, move to a pure-English path and reinstall (see next section).

These five ideas are ordered by likelihood: drivers and runtimes account for most cases, background conflicts come next. If crashes only happen in specific scenarios — say, long co-op sessions with multiple players — cross-check the co-op-related section as well.

Launch Failures from Non-English Paths and Usernames#

When the install path or Windows username contains non-English or special characters, the anti-cheat program may fail to read its files, leaving the game unable to start at all. Installing to a pure-English path like D:\SteamLibrary\EldenRing avoids this.

At startup EAC reads and writes its own files in the install and user directories; non-English or special-character paths can make this step fail outright, showing as “clicked play and nothing happened.” Two key points:

1. Install path: create a new pure-English-drive Steam library folder under Steam Settings → Storage, and use the “Move” function in the game’s properties to migrate it;
2. Windows username: likewise avoid non-English and special characters. If your current account name is not English, create a new pure-English account, log in, and test — community tutorials confirm this step rules out the username factor.

Checking the path right after installing, before the first launch, saves far more effort than troubleshooting after the fact.

Shader Compilation Errors When Playing Online#

Getting a shader compilation error in multiplayer and being unable to go online usually means a corrupted shader cache. Run three actions in order — clear the shader cache, update the graphics driver, then verify game files through Steam — and co-op generally comes back.

The shader cache is a set of temporary files generated by the graphics driver to speed up loading; version updates or abnormal exits can invalidate it. To clear it: use the Windows Disk Cleanup tool with “DirectX Shader Cache” checked, or clear the shader cache from your graphics driver control panel. If errors persist after clearing, update the driver and verify file integrity via Steam. For co-op mechanics and matchmaking rules, see this site’s multiplayer mechanics page.

Keyboard/Mouse Issues: Two Problems Officially Fixed in Patch 1.17#

If your issue is the camera not turning while talking to an NPC, or keyboard/mouse settings failing to reset to defaults, both were fixed by patch 1.17 released on August 27, 2026. Just update the game to the latest version — no folk remedies needed.

These are the two PC-specific issues called out in the official patch notes:

For these two symptoms, first confirm in Steam that the game is updated: the current PC patch is 1.17, and the most recent Steam public-branch update was 2026-09-08. If the problem persists after updating, go back to the launch-fault sections above. The full patch history is on this site’s patch history page.

Are These Problems Still Around: A Four-Year Timeline#

Crash issues have persisted from the 2022 launch to today, but the scope has narrowed to specific environment combinations; the two keyboard/mouse issues were clearly fixed by patch 1.17. This timeline helps you judge whether your case is “legacy” or “new”:

Two conclusions fall out of the timeline: first, launch crashes were never eradicated wholesale by any patch — top-tier hardware was still failing in early 2026, so when it happens, don’t assume “my machine shouldn’t have this problem”; just work through the steps above honestly. Second, official fixes for PC-specific bugs are ongoing — simply keeping the game and drivers up to date avoids part of the already-fixed problems.

Two Symptoms Often Mistaken for Faults#

Two situations are often taken as “the game is broken” when they aren’t faults — rule them out before repairs:

1. Frame rate locked at 60 FPS: The PC version’s native frame cap is 60 with no official unlock; a “less than silky” image is by design, not a performance fault;
2. Hardware below the minimum bar: The official minimum specs are Windows 10 64-bit, an i5-8400-class CPU, 12 GB RAM, and a GTX 1060 3GB card — note the officially listed 3GB VRAM variant, whose core specs are below the 6GB version, making this minimum line slightly harder than it looks on paper. If your hardware sits at or below the bar, crashes more likely stem from insufficient specs — lower settings or upgrade hardware before software troubleshooting.

Related Guides#

• Game Overview — an introduction to the world structure and overall gameplay framework
• Multiplayer Mechanics — a complete explanation of co-op matchmaking and summoning rules
• Patch Update History — every patch’s changes and the 1.17 fixes
• Controls Guide — a keyboard/mouse and gamepad keybinding reference