A closing game and a restarting PC need different reports

Start with what you saw. “Crashing” may mean the game vanished while Windows stayed open, the picture froze, or the whole computer restarted. Preserve that distinction before trying a fix from someone else's post.

FailureRecord firstNext direction
The game closes before its menuLast visible screen, any launcher message and whether the update completedCheck the client installation.
A match loads, then the application closesMap/server, time since joining and the last actionTry to identify a repeatable trigger after checking files.
The screen freezes but Windows still respondsWhether sound continues and whether an error eventually appearsRecord the duration and affected action.
Windows shows a blue screen or restartsStop code or message, time and whether other applications do thisPreserve the system failure details for support.
An access message appears and the game remains openFull text and numeric codeUse the access diagnosis.

The September discussion includes differing outcomes from suggested workarounds. One reply even describes an apparent improvement followed by crashes returning. That is why an isolated successful launch is weak evidence for a permanent fix. EVIDENCE / 01Original r/WarDogs discussion: September beta crashesOpen source (opens in a new tab)

Check files on the client that is failing

First compare your machine with the published PC requirements, and confirm that the Playtest client has finished updating. Meeting the requirements does not rule out a bug, but it makes your report easier to compare with other systems.

Steam documents an installation check for games that crash. Restart the computer, open the affected game's library properties, select Installed Files, then choose Verify integrity of game files. Let that process finish before retrying. EVIDENCE / 02Steam Support: Verify Integrity of Game FilesOpen source (opens in a new tab)

Repeat the action that failed, with the same settings. Record whether Steam downloaded anything and whether the failure changed. If the game now launches, continue far enough to check the original trigger rather than stopping at the first menu.

Test one reversible change when the application still closes

If you added custom launch options or changed settings just before the problem began, save a copy of those values and return that change to its previous state. A clear before-and-after relationship is more useful than applying several tweaks together.

If a recording or overlay tool is active, you can close that one optional tool for a comparison. Keep the rest of the setup the same. If nothing changes, restore it before testing another candidate. Do not treat this as a reason to disable the game's own required services.

For a full PC restart, stop repeating the launch once you have the failure details. Do not copy BIOS or Windows security changes from a thread solely because another player also used the word “crash.” The exact system error matters.

Send the reproducible details, including what did not help

Record your CPU, GPU, memory, Windows version and graphics driver version alongside the client build. Add the point of failure, the complete message and the results of the file check or single-change tests.

If the failure appears only after a particular map loads or a particular action, describe that sequence in order. Say whether the same PC ran an earlier WARDOGS test, and when the behavior changed. Earlier success is useful context, without proving that a patch caused the problem.

Use the Team17 support page for its general support portal when the game has no listed product entry. EVIDENCE / 03Team17 Player SupportOpen source (opens in a new tab) Send any requested diagnostics through the official private route, and review them for account names or personal file paths before posting excerpts publicly.