Update 0.1.2 fixes the recent KB5124010-linked WD-L020 crash
On 30 September BULKHEAD's Update 0.1.2 notes said the recent WD-L020 crash caused by Windows 11 preview update KB5124010 was fixed. Install the current game update through Steam first. The notes publish no client build number and do not retroactively diagnose WD-L020 reports from before KB5124010 was released; Team17's older rollback steps remain historical fallback guidance.
Season 1 named six crash fixes, and almost nobody quotes them
Most changelogs say “various stability improvements”. The Season 1 changelog of 9 September did not: under **Performance and stability** it lists six crashes individually, which is the closest thing to a public map of what was actually going wrong. If your crash matches one of these, it has a named fix and the answer is to be on a current client.
The full Season 1 performance list →
- Fixed two crash paths in the frame generation pipeline
- Fixed a crash caused by network calls scheduled off the game thread
- Fixed a crash when closing a chatbox entry tooltip
- Fixed a crash involving buildables
- Fixed a crash when firing a weapon whose owner had left
- GPU crash reports now carry more detail, “so we can act on them faster”
What Patch 0.11 claims about crashes, in full
One line: **“More GPU crashes addressed.”** That is the entire crash content of the 12 September patch. It names no hardware, no driver, no error code and no individual crash path — so it is a published fix claim and not evidence that any particular crash is resolved. Worth being on; not worth reading as a promise about your card. The same patch is mostly about the server browser, which is a different page.
Launch Stability Hotfix #1 was not about crashes
It gets grouped with them because of the word stability, and it is worth separating. The 10 September hotfix forced every logged-in player to restart and download a client update, then readmitted players in controlled batches. BULKHEAD listed what it was intended to address: players unable to join servers, players unexpectedly kicked during play, and extended login queue times. Those are connection failures, not crashes, and they have their own page.
The reports that outlived the patches, and the one thing they agree on
This is the part with no official answer. Two players filed unusually well-instrumented reports four days apart, on **opposing GPU vendors**, and Windows logged the same thing for both: **LiveKernelEvent 141**, a graphics-subsystem timeout rather than an ordinary application crash. Neither report is a measurement by this site and neither proves a cause. What the pair does establish is narrower and still useful: whatever this is, it is not one vendor's driver, and it survived the driver updates and the toggles both players had already ruled out.
If the game runs but goes silent: the audio fixes →
| Reported | Hardware | Windows records | Dump names | When it hits |
|---|---|---|---|---|
| 19 Sep 2026 | RTX 5080 / Ryzen 7 9800X3D | LiveKernelEvent 141 | nvlddmkm.sys; three Aftermath dumps reading DXGI_ERROR_DEVICE_HUNG 0x887A0006, out-of-memory false | 7–30 min after launch |
| 15 Sep 2026 | RX 9070 XT / Ryzen 7 9800X3D | LiveKernelEvent 141 | dxgkrnl.sys, dxgmms2.sys and amdkmdag.sys in WATCHDOG dumps | 5–15 min into a match |
“It takes my whole PC down” is a distinct report, and it is common
A large share of the searches are not about the game closing — they are about the machine locking up. That is a different description, and it recurs on different hardware and at a different moment. One player reports the freeze arriving 2–3 seconds after the launcher loads, **“right around the time the anti cheats load up”**, with a hard restart the only way out; another reports it at startup on a Ryzen 9 5900XT with an RTX 3080; a third reports crashes and freezes in half their matches. Recorded as reported, with dates and links, and with no remedy attached.
What is published about the anti-cheat →
- 16 Sep — whole-PC freeze 2–3 seconds after the launcher loads, on hardware the player describes as high-end AMD
- 15 Sep — whole-PC failure at startup, Ryzen 9 5900XT and RTX 3080, 64 GB
- 19 Sep — crashes and freezes in roughly half of matches; the crash dump never completes
- 19 Sep — a separate failure: the Elytra anti-cheat service itself crashing with 0xc000001d in heartbeat.dll, at an offset the player says repeats identically
Why there is no numbered fix list on this page
Search any of these strings and you will find confident step lists. Some of them probably help somebody. The problem is checkability, and one thread shows it plainly: a report titled **“solved”** collects replies whose remedies are speculation, and one reply says outright that its steps came from pasting the complaint into a chatbot before answering. Publishing a list here would add one more unverifiable set of steps to that pile, in this site's typeface, where it would read as though somebody had checked it. What is publishable is what the studio fixed and what players have actually recorded — which is above.
If it is a code and not a crash, it is a different page
A dialog with a number in it is a separate problem from a process disappearing, and this site keeps one page per string so the number can be searched for directly. Eleven of them are documented, including the launcher codes, the anti-cheat login failures and the authentication errors.
What would have to be measured
Naming it is the honest alternative to guessing. Settling the LiveKernelEvent 141 reports needs a crash reproduced on a named build with the dump kept, across at least one card from each vendor, with the timeout window recorded rather than described — and then the same run on the following client build to see whether it moved. That is measurable, it is expensive, and this site has not done it. Until somebody does, the two reports above are two reports, and they are labelled as such.
-nogpucrashdebugging: the launch option players are passing around
It is a Steam launch option, not an error. Players add it under the game's Properties → General → Launch Options, and since the start of October it has spread on the Steam board as a frame-rate fix. The one non-player source is Intel: its support article 000103295, last reviewed 15 September 2026, says WARDOGS stuttered every 3–5 seconds on Arc B580 cards, that “the game's request for GPU crash debug information is the likely cause”, and that adding the option resolved it. Intel's listed resolution is a driver, 32.0.101.8993 or later. That article covers one GPU. For every other card there are only player accounts, and they disagree.
The “Outdated Graphics Driver” warning and the minimum versions players report →
- Not established: what the option does on cards other than the Arc B580. BULKHEAD and Team17 have published nothing about it.
- Not established: whether it changes what a crash report contains. Season 1 says GPU crash reports now carry more detail, and the option's name says it turns crash debugging off; no source connects the two.
- This site has not measured it on any hardware, so it is reported here, not recommended.
| Who | What they report | Date |
|---|---|---|
| Intel support (Arc B580 only) | Stutter every 3–5 s; the option “completely resolved” it; update to driver 32.0.101.8993 or later | Reviewed 15 Sep 2026 |
| Player, Steam | “I went from around 90 FPS to 170 FPS” | 1 Oct 2026 |
| Player, Steam | “Depending on your GPU, it can either drastically improve performance or make no difference at all” | 2 Oct 2026 |
| Player, Steam | “it got me another 30FPS” | 3 Oct 2026 |
| Player, Steam | “had this in my launch options for a week and didn't notice any difference in frames” | 4 Oct 2026 |
Adding or removing -nogpucrashdebugging, step by step
The option has its own page: the Steam path, a line builder that adds it to existing launch options without duplicating it or removes it without touching the rest, Intel’s article in full, and every dated player report since 1 October, including one from after Season 02.
Common questions
What is the new WARDOGS WD-L020 crash?
Update 0.1.2 says the recent crash caused by Windows 11 preview update KB5124010 is fixed. The patch does not diagnose older WD-L020 reports or publish a client build number.
Why does WARDOGS keep crashing?
There is no single published cause. BULKHEAD has named six specific crash fixes in the Season 1 changelog and says Patch 0.11 addressed more GPU crashes without naming them. The crashes still being reported publicly after those patches have no official explanation, and the two most detailed reports record a Windows graphics timeout, LiveKernelEvent 141, on both an NVIDIA and an AMD card.
Why does WARDOGS crash my whole PC?
This is reported often enough to be a distinct pattern rather than a variant, but no official source addresses it. Players describe a full system freeze needing a hard restart, some seconds after the launcher loads and around when the anti-cheat starts, and others describe it during matches. This site records those reports with their dates and does not publish a fix for them, because no checkable one exists.
What is LiveKernelEvent 141 in WARDOGS?
LiveKernelEvent 141 is a Windows Reliability Monitor entry for a graphics-subsystem timeout, not a WARDOGS error code. Two dated player reports — one on an RTX 5080, one on an RX 9070 XT — record it at the moment the game crashes, with dumps naming the DirectX and vendor driver components. BULKHEAD has not commented on it.
Did Patch 0.11 fix WARDOGS crashes?
Patch 0.11 states that more GPU crashes were addressed. It names none of them, so there is no way to check it against a particular crash. It is a fix claim, not evidence your crash is resolved.
Where does WARDOGS put its crash reports?
Players describe a WARDOGS Crash Report Handler appearing briefly and closing after a crash, and Season 1 says GPU crash reports now carry more detail so the studio can act on them faster. No official source located states where the files are written, so this page does not name a path.
Is WARDOGS crashing caused by the anti-cheat?
Unestablished. One 19 September report is a crash of the Elytra anti-cheat service itself, with a Windows exception code and faulting module, and one whole-PC freeze report places the freeze around the moment the anti-cheat loads. Both are single player accounts. No official source connects the anti-cheat to the crashes, and this site does not either.
Does -nogpucrashdebugging improve WARDOGS performance?
On an Intel Arc B580, Intel's own support article (reviewed 15 September 2026) says it resolved stuttering every 3–5 seconds, and lists driver 32.0.101.8993 or later as the fix. On other cards there are only player reports, and they split: some describe 30 to 80 more frames per second, others no difference. BULKHEAD has not commented on it, and this site has not measured it.
What is “no GPU crash debugging” in WARDOGS?
It is the same thing as -nogpucrashdebugging, written out as words: a Steam launch option players add under WARDOGS → Properties → General → Launch Options. It is entered as one word with a leading dash — exactly -nogpucrashdebugging, as every player report and Intel write it — not as separate words. It is not an error or a crash fix; Intel ties it to stutter on the Arc B580, and players disagree about what it does on other cards.
Sources & verification
The fixes are BULKHEAD's own wording, read from the Season 1 and Patch 0.11 announcements on 19 September 2026. The reports are public Steam threads, each dated and linked. This site has not reproduced a single crash on its own hardware and does not present a player's dump reading as a measurement.
| Source | Type | Read |
|---|---|---|
| BULKHEAD · WARDOGS Update 0.1.2, 30 September 2026Published at 06:57:06 UTC. Schedules an 08:00 UTC maintenance window estimated at one hour and publishes the complete 0.1.2 change list: a fix for the recent KB5124010-linked WD-L020 crash, named cash and XP exploit changes and enforcement, a four-way Deploy flow, browser/admin controls, stability, Havoc, buildable, throwable, crosshair and localisation fixes. The maintenance window is an announcement, not a live recovery signal. | Publisher stated | 2026-09-30 |
| WARDOGS Updates / Team17 Support · WD-L020 and Windows 11 KB5124010, 23 September 2026Published by the official WARDOGS Updates account at 12:26:05 UTC and mirrored in a pinned Steam thread by G_Medlin [developer]. This was the preliminary KB5124010 investigation and optional rollback guidance. Update 0.1.2 on 30 September supersedes its active-status wording by announcing the recent KB5124010-linked WD-L020 crash fixed; the older notice remains the source for the rollback warning and for why historical WD-L020 reports are not all retroactively diagnosed. | Publisher stated | 2026-09-23 |
| BULKHEAD · Pre-Load Live & Season 1 Changelog, 9 September 2026Published 22:46:09 UTC. Records server-browser, voice, stability, progression and economy changes from beta to Season 1. | Publisher stated | 2026-09-11 |
| BULKHEAD · Scheduled Maintenance & Patch 0.11, 12 September 2026Published 22:26:39 UTC. Schedules approximately one hour of maintenance from 08:00 UTC on 14 September and details server-browser, community-server, crash, capacity and economy-enforcement changes. Planned features are explicitly not part of this patch. | Publisher stated | 2026-09-14 |
| BULKHEAD · Launch Stability Hotfix #1, 10 September 2026Published 20:20:33 UTC (04:20:33 SGT on 11 September). Reports a released client update and controlled queue admission; it does not establish that every server is healthy. | Publisher stated | 2026-09-11 |
| Steam · WARDOGS developer announcements | Publisher stated | 2026-09-11 |
| Steam · “Repeated DX12 GPU crashes — RTX 5080 / 9800X3D / LiveKernelEvent 141”, WARDOGS Report a Problem, 19 September 2026Opened 02:14 UTC. The most instrumented public crash report located. The player names the build and engine the dumps record — WARDOGS build 501228, Unreal Engine 5.7.4 — and reports three NVIDIA Aftermath dumps that all read DXGI_ERROR_DEVICE_HUNG, error code 0x887A0006, out-of-memory flag false, with Windows Reliability Monitor logging LiveKernelEvent 141 and naming nvlddmkm.sys. Hardware: RTX 5080, Ryzen 7 9800X3D, 32 GB, Windows 11 25H2 build 26200.9457, Game Ready 616.92. Updating the driver did not change it. One player's machine; the dump contents are what they report reading, not something this site reproduced. | Unverified | 2026-09-19 |
| Steam · “RX 9070 XT / LiveKernelEvent 141 / game crash”, WARDOGS Report a Problem, 15 September 2026Opened 19:55 UTC, four days before the NVIDIA report and on the other vendor. Same Windows event — LiveKernelEvent 141 — with WATCHDOG dumps naming dxgkrnl.sys, dxgmms2.sys and amdkmdag.sys, after 5–15 minutes in a match, with the WARDOGS Crash Report Handler appearing and closing. The player lists what they had already ruled out: file verification, overlays, HAGS, FSR, Frame Generation, PIP scopes, Anti-Lag, AFMF, Enhanced Sync, frame caps at 180 and 120, stock clocks, and a −200 MHz offset. Two independent reports on opposing GPU vendors recording the same Windows event is the reason this pair is cited together. | Unverified | 2026-09-19 |
| Steam · “the game was freezing my whole pc every time i tried launching it - solved”, WARDOGS discussions, 16 September 2026Opened 00:26 UTC. The freeze is described as arriving 2–3 seconds after the launcher loads, “right around the time the anti cheats load up”, with a hard restart the only way out, on hardware the player describes as high-end AMD. The title says solved; the thread's replies are player speculation, and one reply states outright that its remedy came from pasting the complaint into a chatbot. That is why no step from this thread appears on the page — the report is the evidence, the fixes are not. | Unverified | 2026-09-19 |
| Steam · “Game Crashes my PC”, WARDOGS discussions, 15 September 2026Opened 04:48 UTC. “Anytime i try to start the game it crashes my pc”, on a Ryzen 9 5900XT with an RTX 3080 and 64 GB — a third hardware combination, and an NVIDIA one, reporting a whole-machine failure at launch rather than in a match. Cited for the shape of the report and its date, not for the remedies the player says they tried. | Unverified | 2026-09-19 |
| Steam · “Elytra service.exe crashes (0xc000001d in heartbeat.dll)”, WARDOGS discussions, 19 September 2026Opened 15:08 UTC. Windows Event Viewer IDs 1000 and 1005 with the anti-cheat service as the faulting application: C:\\Program Files\\Elytra\\service.exe, faulting module heartbeat.dll, exception 0xc000001d (STATUS_ILLEGAL_INSTRUCTION), at a constant fault offset the player says repeats identically. Named here because it is a crash of the anti-cheat service rather than of the game, which is a different failure from the DX12 pair — and because Elytra is the component the EULA addendum already puts in scope. | Unverified | 2026-09-19 |
| Intel Support · “Intel® Arc™ B580 GPU: Frame Drops and Stuttering in Wardogs”, article 000103295, last reviewed 15 September 2026Intel's own troubleshooting article, about its own GPU — a hardware vendor, not BULKHEAD or Team17. It says the stutter occurred every 3–5 seconds regardless of graphics settings, that the game's request for GPU crash debug information is the likely cause, that adding -nogpucrashdebugging to the Steam launch options completely resolved it, and gives the resolution as driver 32.0.101.8993 or later. Scoped to the Arc B580 on Windows 11; it says nothing about other cards. | Publisher stated | 2026-10-06 |
| Steam · “23GB RAM usage when 16GB is recommended?!”, WARDOGS discussions, opened 15 September 2026Cited for two replies: 2026-10-01 01:01 UTC, “FPS issue fixed with this command: -nogpucrashdebugging I went from around 90 FPS to 170 FPS”; and 2026-10-02 15:35 UTC, giving the Properties → General → Launch Options path and saying it “can either drastically improve performance or make no difference at all” depending on the GPU. Two players' accounts, not measurements. | Unverified | 2026-10-06 |
| Steam · “The game needs more fps”, WARDOGS discussions, 3 October 2026Opened 2026-10-03 13:30 UTC. Cited for one reply at 15:22 UTC: “try the '-nogpucrashdebugging' thing in the steam launch preferences for this game, it got me another 30FPS”. | Unverified | 2026-10-06 |
| Steam · “USE THIS FOR BETTER FRAMES IN YOUR LAUNCH OPTIONS”, WARDOGS discussions, 4 October 2026Opened 2026-10-04 15:25 UTC with the option alone. A reply two minutes later: “I had this in my launch options for a week and didn't notice any difference in frames”; the opener answered on 5 October that it got them “an extra like 50 frames”. Cited because it holds both outcomes in one thread. | Unverified | 2026-10-06 |
