WARDOGS Steam EA Guides
Fix Play Info

Last checked 14 Sep 2026 · Steam Early Access. Guides may change after patches.

WARDOGS Black Screen on Launch: Stuck at Startup Fixes (Steam EA)

TL;DR: This page is for black screen / blackscreen / stuck at startup on Steam Early Access — the process starts (or Steam says Running) but you never reach a usable menu. It is distinct from mid-match crash and from auth/queue codes like 1147405308. Fork first: music-but-black (display / window / overlay) vs hard crash (dump / instant desktop). Store anti-cheat is Elytra (not EAC as current). Safe tests: overlays off one-at-a-time → windowed launch option ( flags on Launch Options) → file verify → GPU driver sanity → Elytra identify/repair if launch dies at AC init. Shader-compile stalls that later recover → patience + stutter notes; process exit → Crash ladder. No invented FIXED stamps.

Last checked 2026-09-16 (Early Access).

TODO: Steam Running + black client window / no menu — stamp build/GPU/driver
TODO: Steam Running + black client window / no menu — stamp build/GPU/driver

What this page is (and is not)

Covered Send elsewhere
Black screen before / at menu —
Stuck at startup / infinite “loading” with black frame —
Music or audio continues but picture stays black Windowed / display fork below
Hard crash to desktop during / after splash Crashing
Mid-match exit while already playing Crash — mid-match section
Auth dialog / 1147405308 / Access Denied, no black frame 1147405308 · Servers
Hitching after you can play Stuttering / Low FPS · Settings
WD-LO14 / WD-L014 Unable to launch WD-L014

Public third-party black-screen roundups (2UpSkill Aug 2026 playtest-era; LagoFast; PixelNitro; Sportskeeda) mix EAC wording with overlay / windowed / shader tips. For current Steam store tag, rebuild the AC branch around Elytra — do not lead with “delete EasyAntiCheat folder.”

Symptom fork: music-but-black vs hard crash

Observation Lean First moves
Audio / menu music continues; picture black Display mode / resolution / overlay hook Alt-Tab; force windowed test; disable overlays
Black briefly → instant desktop; crash reporter Hard crash Crashing ladder
“Compiling shaders” / long stall, then continues First-run shader compile (community lead) Wait once; don’t Alt-F4 mid-compile if progress continues (LagoFast lead)
Shader stall then every launch crashes Corrupted cache / GPU path (public leads) Verify files; shader-cache cleanup leads on Stutter page; Crash if dump
Steam Running → stops; no window Won’t launch class Crash + WD-L014 if coded
Elytra / AC splash loops then black AC init Elytra identify/repair (community folder/UI)
TODO: Compiling Shaders message vs pure black frame — two screenshots
TODO: Compiling Shaders message vs pure black frame — two screenshots

Decision tree

Black / stuck at startup?
│
├─ Exact dialog is auth / 1147405308 / Access Denied (readable text)?
│ └─./wardogs-error-1147405308/./wardogs-servers-down/
│
├─ WD-LO14 / WD-L014 / Unable to launch?
│ └─./wardogs-wd-l014/ (+ Elytra repair)
│
├─ Hard crash dump / EXCEPTION / Crash Reporter?
│ └─./wardogs-crashing/ (full ladder)
│
├─ Music or audio continues; picture black?
│ ├─ Alt-Tab / Win+Tab — is a window off-screen?
│ ├─ Disable Discord / Steam / GPU / Afterburner overlays (one at a time)
│ ├─ Steam launch options: try -windowed │ │ Document on./wardogs-launch-options/ — one flag at a time
│ ├─ Optional: -dx11 as isolated test [ ON EA — may no-op]
│ └─ Still black → file verify → GPU driver → Elytra identify
│
├─ Long shader / loading stall, process still alive?
│ ├─ Wait (community: first compile can look frozen 10–20 min — LagoFast)
│ ├─ If it eventually plays but hitchs./wardogs-stuttering-fps/
│ └─ If it always dies here → Crash + shader-cache public leads
│
└─ Unknown / mixed └─ Capture 30s of behavior → Crash hub symptom matrix

Fix ladder (black-screen first)

Run top → bottom. Re-test after each row.

# Step Detail Evidence
1 Confirm failure class Music-but-black vs dump vs auth text Screenshot / short clip
2 Full Windows + Steam restart Clears stuck GPU driver / Steam IPC Note if ReBar/HAGS untouched yet
3 Disable overlays one at a time Discord, Steam overlay, GeForce/AMD, Xbox Game Bar, MSI Afterburner/RivaTuner, RGB injectors Which toggle restored picture?
5 Isolate second flag only if needed e.g. -dx11 alone, then combine only if documented Never dump 10 flags
6 Verify integrity of game files Steam → Installed Files → Verify Record repaired count
7 GPU driver sanity Clean install current Game Ready / Adrenalin; avoid “oldest driver folklore” Stamp driver version
10 Read ElytraLauncher.log Community path: %LOCALAPPDATA%\Wardogs\ElytraLauncher.log Paste last lines into support block
11 Shader-cache cleanup leads Only if compile crash / repeat hitch after driver change Public leads (Worldeka / PixelNitro / 2UpSkill) — no miracle claim
12 Still failing Support paste + Discord/Steam ticket Evidence > reinstall loops

Overlay sub-ladder (highest-yield local branch)

Overlay How to disable for test Note
Discord Settings → Overlay → off → relaunch Common black-screen / AV conflict lead
Steam WARDOGS → Properties → General → disable Steam Overlay same
GeForce Experience / AMD Vendor overlay / ShadowPlay / Instant Replay off same
Xbox Game Bar Win+G settings → off same
MSI Afterburner / RTSS Exit fully (tray) same
RGB / board utilities Quit injectors Document name

Re-enable after isolation so you know which hook was guilty.

Windowed / display notes

Public guides (2UpSkill, LagoFast FAQ) cite -windowed / borderless-style tests when music continues on a black frame. Treat flags as community lab tools, not studio-verified miracles:

TODO: Steam Launch Options field with single -windowed entry
TODO: Steam Launch Options field with single -windowed entry

Elytra-first (do not lead with EAC)

Fact / lead Status
Steam store feature tag: Uses Kernel Level Anti-Cheat Elytra Editorial WebFetch 2026-09-13 — treat as current store fact
Community repair: Elytra folder helper → Repair ccstartup / AxeeTech / LagoFast public leads — confirm UI
Log file community path %LOCALAPPDATA%\Wardogs\ElytraLauncher.log
Old “delete EasyAntiCheat” articles Deprecated as default for EA store tag

If a residual EasyAntiCheat folder still exists on disk, document as anomaly — do not assume deleting it is safe or required.

Full AC + exception ladder → Crashing / Won’t Launch (Elytra).

Shader compile vs true black screen

Pattern Public lead Action
First launch long “Compiling Shaders,” then OK LagoFast: can look frozen 10–20 min then continue Wait once; subsequent launches faster
Crash every time during compile PixelNitro / Worldeka / 2UpSkill shader-cache leads Verify → driver → cache cleanup → HAGS test
Black frame, no shader text, music on Display / overlay fork Windowed + overlays
Process exits with access violation Crash spoke Don’t only clear cache forever

After you can enter matches but hitch when entering new areas, continue on Stuttering or Low FPS — that is not the same as stuck-at-startup black screen.

Boundary cases

Edge Action
Overlay off fixes picture; overlay on → black Keep conflicting overlay disabled for WARDOGS; document which
Verify finds 0 files Continue overlays + Elytra — zero mismatches ≠ healthy display/AC path
Reinstall did nothing; log shows install-stage failure Stop reinstall loops; read ElytraLauncher.log
Hotfix #1 just landed; “black screen” is actually Access Denied text Auth spoke / Servers — wrong page
Guide says “repair EAC” Ignore as current default — store is Elytra
Music-but-black on multi-monitor Check window on wrong display; Win+Shift+Left/Right
Shader compile succeeds once, later launches black Overlay / display mode drift — re-run ladder from overlays

Multi-monitor / HDR quick checks

Check Note
Game on primary display? Drag windowed test to known-good monitor
Unusual resolution / ultrawide first boot Windowed native → set mode in-menu
GPU driver crash (TDR) Ctrl+Shift+Win+B then relaunch (Sportskeeda-class lead)

Crash or outage? (quick redirect)

Signal Stay here Leave
Black window / stuck startup / music-but-black Yes —
Mid-match crash after playing — Crashing
Everyone auth-failing, readable 1147405308 — 1147405308
JOIN TIMEDOUT — 1628505091
Playable but stutter / low FPS — Stuttering · Settings

Do / Don’t

Do Don’t
Fork music-but-black vs hard crash first Treat every black frame as “reinstall Windows”
One launch option at a time; link Launch Options lab Paste ten undocumented UE flags as verified
Elytra identify/repair after store/tag + on-disk check Lead with EAC folder deletes from playtest posts
Disable overlays one-at-a-time and re-enable to isolate Disable Windows security permanently “for launch”
Wait once on first shader compile if process alive Alt-F4 mid-compile then blame “broken shaders” without evidence
Stamp GPU driver + build on every retest Invent FIXED / FPS% claims

Support paste block

Game: WARDOGS (Steam) AppID 1867240
Build / stamp: Symptom: music-but-black / pure black / shader stall / crash-to-desktop
Audio present?: Y/N
Crash Reporter / exception text:
GPU + driver version:
Overlays tested off: Discord / Steam / GeForce / AMD / Game Bar / Afterburner / other
Launch options tried (one at a time):
File verify result:
Anti-cheat identified: Elytra (store) + on-disk ElytraLauncher.log last lines:
HAGS on/off tested?: Steps tried (ladder #s):

FAQ

Q: WARDOGS black screen on launch — where do I start?
A: Decide music-but-black vs hard crash. Then overlays → -windowed test → verify files → GPU driver → Elytra repair. Auth text → auth spoke, not this ladder.

Q: Is black screen the same as mid-game crash?
A: No. Mid-match exits after you already played belong on Crashing. This page is startup / display init / shader-at-boot.

Q: Should I repair Easy Anti-Cheat?
A: Not as the current default. Store tags Elytra. Use Elytra identify/repair community path; treat leftover EAC folders.

Q: Which Steam launch options fix black screen?
A: Community leads often start with -windowed; -dx11 appears as an isolated lab flag. All flags need and may no-op — full lab on Launch Options. Never dump a pile of undocumented miracles.

Q: How long should I wait on “Compiling Shaders”?
A: LagoFast-class public lead: first compile can look stuck for a long stretch yet continue. If the process is alive and disk/GPU active, wait once. If it always crashes at the same point, switch to Crash + cache cleanup leads.

Q: Overlays keep breaking the picture — which one?
A: Disable one at a time and re-enable after success. Discord and vendor overlays are the highest-cited locals; your PC may differ.

Q: I fixed the black screen but now hitch in matches — next page?
A: Stuttering or Low FPS for symptom triage; Best Settings for FPS-vs-clarity slider goals. No invented FPS%.

Q: Steam says Running then stops with WD-LO14.
A: That is Unable to launch / AC init class → WD-L014 and Crash Elytra section.

Q: Could this be servers down?
A: Only if you actually receive auth/queue dialogs. Pure black local window with no online-services text stays on this page; status habit still useful once via Is Down.

Q: Does HDR or multi-monitor cause WARDOGS black screen?
A: Undocumented as official. Treat as A/B: windowed on primary display, then toggle HDR/Auto-HDR once. Document results; don’t invent a universal rule.

Q: I hear compiling shaders but see black — wait or kill?
A: If the process is alive and disk/GPU busy, wait once (LagoFast-class patience lead). If it repeatedly dies at the same percent with a crash reporter, switch to Crash + shader-cache leads — don’t infinite-wait a hard crash.

Sources