Skip to content
← All errors

Fetched optional streams (2/2/2/2)

WARDOGS "fetched optional streams (2/2/2/2)"

Published Data as of Season 1 · 10 Sept 2026

This one is not your machine

That line is the crash reporter reporting its own progress while it writes the dump file, not a diagnosis. It appears after any crash, so the useful question is when the crash happened: while the game was starting, during a match, or with the whole machine going down.

Check whether WARDOGS is down right now →

What you see

The game closes and a Crash Report Handler window appears: "The application has encountered an unexpected error. Oops! We ran into a problem and crashed. Dumping started... Fetched optional streams (2/2/2/2) data (140/140/140)". The numbers in the brackets vary between machines and crashes.

Also reported as: Fetched optional streams · Fetched optional streams (2/2/2/2) · 2/2/2/2 · fetched optional streams (e0/e0/e0) · fetched optional streams (190/190/190) · data (140/140/140) · crash report handler · oops we ran into a problem and crashed · dumping started

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 Read the numbers as progress, not as a code

    Confirmed

    The counts in the brackets are the streams and blocks the crash reporter has written into the dump. They change from machine to machine and from crash to crash — 2/2/2/2, e0/e0/e0 and 190/190/190 all appear in reports of completely different faults — so searching for them will not narrow anything down. What narrows it down is when the crash happened.

  2. 02 Match the crash to its moment

    Confirmed

    If the game closed while it was starting, before you reached the menu, the crash on launch page is the one with the fixes in it. If it closed during a match, the crash in match page covers what is known, including the picture-in-picture scopes setting. If Windows itself blue-screened or the machine restarted, the stop code page covers the virtualisation conflict behind those.

  3. 03 Take the current build and verify the files

    Confirmed

    Team17 support calls this a known issue under investigation and asks for two things: be on the latest patch, and verify the game files — Steam, right-click WARDOGS, Properties, Installed Files, Verify integrity of game files. It is the standard first step and it costs a few minutes.

  4. 04 Remove Dr.Web if you have it

    Reported

    One player reported the crashes stopped when Dr.Web anti-malware was fully uninstalled, and Team17 support names the same software in its own crash instructions. One report plus an official mention is not a rule, but it is a cheap thing to rule out.

  5. 05 Treat the rest of what circulates as one-offs

    Unconfirmed

    Every other fix posted for this line has exactly one player behind it: the -slno launch option, removing the FSR3 line from GameUserSettings.ini and reinstalling the Visual C++ runtimes, turning NVIDIA Reflex off, going back to Windows 10. Several players report each of those doing nothing. Try them if you like, but do not expect them to hold.

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.

  1. 140/140/140AND c:users\appdata\local\temp\packer_29227828_13532.dmp

    1. 140/140/140

      This line is not the error. When WARDOGS crashes, the Crash Report Handler opens and prints what it is doing while it packages the dump — dumping started, then fetched optional streams with a handful of counters. People paste that line because it is the only text on screen, and it has become a search term in its own right. It describes the reporter, not the crash.

      That is why the brackets vary. Reports carry (2/2/2/2), (e0/e0/e0) and (190/190/190) for faults with nothing in common, and one adds an upload-failure code, which only means the report did not reach Team17.

      Find the crash underneath it

      When it happened The page with the answers
      Starting up, before the menu Crash on launch
      During a match Crash in match
      Windows blue-screened or the PC restarted SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
      The game never starts and names a file Errors and crashes

      One thing to rule out first, because it is close enough to confuse: the in-game message "an unexpected error has occurred" with a long numeric code is a different fault with its own page at unexpected error. The Crash Report Handler window is the one that appears after the game has already closed.

      What is actually known

      Team17 support calls the Crash Report Handler reports a known issue and is investigating. Its own steps are the current patch and a file verification. Beyond that, no fix posted for this line has more than a single player behind it, and the reports carried on after Patch 0.11 on 14 September, which addressed GPU crashes.

      If you want to help it get fixed rather than work around it, the useful post says when the crash happens, what you were doing, your GPU and driver version, and whether it started with a patch.

      Source

      Team17 support, Crash Report Handler thread, Steam, 14 September 2026 ↗

      If that did not do it