When it will not launch, or dies mid-match
WARDOGS has published a long list of crash fixes and, in all of it, not one error code. So this page keeps the two apart: what the studio says it fixed, and what the codes on your screen mean according to the people who wrote them up.
| Code | What happens | Whose end |
|---|---|---|
| WD-L014 | The launcher stops before the game starts. Reported alongside a message asking you to contact support with the code. | Unknown. GameSpot says the studio told it the team is looking into it. |
| 1147405308 | Failed to authenticate with online services, which is the login path rather than the game itself. | BisectHosting reads it as server side during the launch outage, and says there is no fix at your end for that case. It adds that the same code can come from maintenance or from your own connection later on. |
WD-L014 written up by GameSpot, the authentication code by BisectHosting. Neither code appears in any announcement, on the store page or on wardogs.com.
What the studio has fixed, in its own words
- The launch hotfix targeted players unable to join servers, players kicked from servers mid-play, and extended login queue times. Listed in Steam announcement — Launch Stability Hotfix #1
- The launch changelog fixed two crash paths in the frame generation pipeline, a crash from network calls scheduled off the game thread, one when closing a chatbox entry tooltip, one involving buildables, and one when firing a weapon whose owner had left. It also says “Improved startup reliability, with clearer messages when something fails early and a route to recovery.” From Steam announcement — Pre-Load Live & Season 1 Changelog
- The same changelog adds “GPU crash reports now carry more detail, so we can act on them faster.” The patch three days after launch then lists “More GPU crashes addressed” and nothing more specific. That last one from Steam announcement — Scheduled Maintenance & Patch 0.11
None of that is an error-code reference, and none of it promises your crash is among the ones addressed. What it does mean is that being on the current build is the first thing to rule out. Everything below this line is community work.
What the guides tell you to try
For the launcher code, GameSpot gives six steps: run it as administrator, temporarily turn off memory integrity in Windows core isolation, verify the game files through Steam, repair the anti-cheat component, remove any leftover beta build, and restart Windows. It ends by saying the restart on its own was what worked, after every other step had already asked for one. For crashes in general, DriveEasy’s round-up adds GPU driver updates and turning off hardware-accelerated GPU scheduling.
Two notes on that list. Only one of the six changes nothing on your machine if it turns out not to be the cause — verifying files through Steam — so it is a reasonable place to start, though no source says corrupted files are the common cause here. And the anti-cheat step is the reason those guides print a product name the studio has kept out of everything it has published: what is and is not on the record.
The failure that is not yours
During the launch outage the authentication code was the login service, not your machine, and the studio’s own account of that night describes exactly that shape of failure: tickets issued by Valve expiring in a queue, with logins succeeding at a tenth of the intended rate. BisectHosting says the same code can turn up later for ordinary reasons, your own connection among them, so the timing is what tells you which one you have. Explained in BULKHEAD video — WARDOGS | Launch Day Recap When that is what you are looking at, the queue and the server browser are the pages that matter: servers and the login queue.
There is a separate, documented case where the game refuses to start on purpose: the rules page says a client that detects tampering or cheat software running will refuse to launch or refuse to connect. From wardogs.com — Security and Enforcement
If it will not run at all
Two clocks are running while you troubleshoot. Steam counts the time the game is open toward the two hours that decide a refund, and the refund window itself is fourteen days. If the hardware is the question rather than the software, the requirements page has the published floor, and the settings page has what the launch build changed about stability.