LiveKernelEvent 141
WARDOGS GPU driver timeouts: LiveKernelEvent 141 (and 1b0, 1b8)
This one is on your machine
No patch or confirmed fix yet, and Bulkhead has not acknowledged it as a game bug. Switching anti-aliasing to TAA, capping your GPU clock or power, and trying another driver are what players report helps. Raising the Windows TDR timeout makes it happen less often, not never.
What you see
The game freezes or crashes mid-match, sometimes with a black screen or a GPU driver reset, and Windows Reliability Monitor logs a LiveKernelEvent 141 (or 1b0, 1b8). Other games run fine on the same PC. Players report it on AMD RX 9070 XT and RX 7900 XTX and on Nvidia RTX 30, 40 and 50-series cards.
Also reported as: LiveKernelEvent 141 · LiveKernelEvent 1b0 · LiveKernelEvent 1b8 · VIDEO_ENGINE_TIMEOUT_DETECTED · GPU driver timeout · driver timeout · TDR · display driver stopped responding · gpu crash
Fixes, in the order worth trying
Work top to bottom and stop when the game launches. Each step is labelled with how much evidence sits behind it, so you can skip the guesses if the first ones work.
01 Switch anti-aliasing to TAA
ReportedThe one setting change players report helping. On Steam, a player who crashed in the inventory says moving to TAA stopped it, at the cost of a softer picture. On Reddit, a player crashing every match with FSR artifacts was told to use TAA or native anti-aliasing instead. Try it before anything that touches drivers or the registry.
02 Cap your GPU clock or power limit
ReportedOn r/WarDogs a player with LiveKernelEvent 1b8 on an RTX 5060 was told to cap the GPU frequency at about 80%, and another replied "That solved the issue for me". Others suggest an undervolt or a lower power limit in MSI Afterburner or AMD Adrenalin. A card that is stable everywhere else can still time out under one game's load.
03 Close RGB, peripheral and overlay software
ReportedIn the same Reddit thread one player traced their crashes to the SteelSeries app. Others close Discord, Steam and Nvidia overlays and capture tools. This takes a minute and rules out a common cause.
04 Try a different GPU driver
ReportedPlayers have both rolled back and updated, with mixed results. One Nvidia player was told to go back to 610.62; the poster said 617.4 had not helped. Do a clean install with DDU if you change version. There is no driver anyone has shown to fix it.
05 Raising the TDR timeout makes it rarer, not gone
ReportedPlayers set TdrDelay and TdrDdiDelay to 8 under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers. On Reddit one player says "it WILL reduce the frequency" and another says "it didn't do it for me". On Steam it reduced crashes but did not stop them. Microsoft says these keys are for driver developers and that end users should not change them, so back up the registry first, and remove the values if they make no difference.
06 Send Team17 a DxDiag if you open a ticket
ConfirmedIn the Steam thread, Team17's support accounts asked for a DxDiag report, a chkdsk /f /r /x, and a clean-boot test. That is what support will ask you for, so attach it from the start.
Did this fix it for you?
Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.
No comments yet. Be the first to say whether this worked.
LiveKernelEvent 141 is not a WARDOGS error code. It is what Windows logs when one of the GPU's engines fails to respond in time and Windows resets the graphics driver instead of blue-screening. By default Windows waits 2 seconds before it does that. In WARDOGS, the reset usually looks like a freeze, a black flash or a crash to desktop.
Who is getting it?
Players on AMD and Nvidia cards alike (Reported). The Steam thread started on an RX 9070 XT and has 15 replies. One poster says stress tests pass and Helldivers 2 runs stable on the same PC. Another, on an RTX 4070 Super, ran chkdsk, DISM, sfc and MemTest86 without finding anything. On 18 October a player reported 5–10 crashes a day and asked if a hotfix was coming; that question is unanswered.
On r/WarDogs, the longest thread (19 comments, from 24 September) is on an RTX 3080 Ti laptop, with crashes every 30–90 minutes and LiveKernelEvent 1b0 reported alongside 141. Newer threads add an RTX 5060 with 1b8, an RTX 3060 and an RX 9070 XT crashing every match, and a player with two RX 7900 XTX PCs that both started crashing.
Is Bulkhead fixing it?
Not that it has said. Team17's support accounts replied in the Steam thread with the standard checks: a DxDiag, chkdsk and a clean boot. No patch note names GPU timeouts, and the Reddit threads that asked Bulkhead directly have no developer reply. If a hotfix mentions it, this page will say so. For live problems, see the status page.
Not this crash?
- The whole PC reboots with no blue screen. That is Kernel-Power 41, a different log entry.
- A blue screen with a stop code. Start from WARDOGS blue screens.
- "Out of video memory" on screen. That one has its own page.
- A freeze of several seconds and then the game carries on. That is the Season 2 freeze, a different problem.
If that did not do it
Every WARDOGS error, by symptom
Start from what you can see on screen rather than from the code.
Is WARDOGS down right now?
Live server state and player reports, updated continuously.
Can your PC run it?
Some crashes are a spec problem wearing an error code.
Server regions and browser
Which regions exist, and how to find a match in one.