0x00001337 ntdll.dll BO7 GameInput Fix (Warzone Unconfirmed)

Quick answer (TLDR): If Warzone or Black Ops 7 dies with 0x00001337 and ntdll.dll, check your Microsoft GameInput version first. Version 4.0.302 can hang the game's main thread until the game kills itself, and rolling back to 3.5.283 fixed it at once in the one detailed report so far. Here's the fix:

• Open Settings > Apps > Installed apps and search for GameInput.
• If it reads 4.0.302, or another 4.0.x build and your crash matches, uninstall it.
• Download Microsoft.GameInput 3.5.283 from NuGet and run the GameInputRedist.msi inside it.
• Restart the PC and launch the game.

So far this has only been reported on the Xbox app / Game Pass build of BO7. It is not yet confirmed on Warzone, MW4, Battle.net or Steam, and Microsoft has not responded to the report. If your version isn't 4.0.x, jump to the fallback section.

Most of what turns up for this code is years-old forum advice to update your drivers. That advice is not useless, because 0x00001337 is an old code with more than one trigger. But it misses what is new: Gaming Services quietly moved a Microsoft input component to a new version, and a GitHub report filed on October 24, 2026 ties a Call of Duty crash to it.

Why do you get 0x00001337 and ntdll.dll in BO7 or Warzone?

The October report gives the first traceable cause we've seen for this crash on current Call of Duty builds. After Gaming Services upgraded GameInput from 3.5.270 to 4.0.302, the reporter's BO7 crashed on every launch, about 150 to 170 seconds in, while loading the frontend menu. The game's watchdog logged the main thread as blocked for 90 seconds, with GameInputRedist.dll as the top frame.

In plain terms, the reporter's best read is that the game was waiting on Microsoft's input component, the wait never ended, and the watchdog shut the game down. They only had a 5-frame capture, not a full stack, so that isn't proven. It may also explain why ntdll.dll gets named: per the report, the stuck thread was parked in KERNELBASE and ntdll, called from GameInputRedist.dll. The issue never says the crash box listed ntdll.dll, so that link is our read. Either way, replacing that file won't help.

"Uninstalling 4.0.302 and installing 3.5.283 from the Microsoft.GameInput NuGet package fixed it immediately with no other changes." — GitHub user 0xNulltraced (Cryptokong123), GameInput issue #53

A Reddit commenter pointed at the same component a week later. Under an r/CODWarzone crash thread from October 30, u/Front_Day_998 wrote: "If BO7, Warzone or MW4 crashes when launching through COD HQ with 0x00001337 (0x00000000) N and ntdll.dll, check your Microsoft GameInput version." That commenter tested on BO7 through the Xbox app and Game Pass, called the fix confirmed for BO7 on their PC, and described it as only potentially relevant to Warzone and MW4.

Does the GameInput fix apply to you?

Match your crash against this table before you change anything.

Your symptom	Possible cause	What to do
0x00001337, GameInput shows 4.0.x, crash about 2.5 to 3 minutes in on the menus	Possible GameInput hang	Roll back (next section)
Same crash on Xbox app or Game Pass	Possible GameInput hang, closest match to the report	Roll back
Same crash on Battle.net or Steam, GameInput shows 4.0.x	Unconfirmed, but cheap to test	Try the rollback, then the fallback list
Instant crash on launch, GameInput shows 3.5.x or older	Probably something else	Skip to the fallback list
0x00001338 instead, or KERNELBASE.dll with no 0x00001337	Probably a different crash	See the MW4 launch-day errors guide or the 0xE06D7363 guide

The report was also filed from one machine: a Windows 11 26H2 (build 26300) laptop with hybrid graphics. Its author says plainly they don't yet know whether the bug is specific to BO7, to that Windows build, or to that hardware.

How do you check your GameInput version?

Use either method. You need the number before you remove anything.

• Press Windows + I and go to Apps > Installed apps.
• Search GameInput and look for Microsoft GameInput. The version shows under the entry.

Or open Terminal and run:

winget list --id Microsoft.GameInput

Anything starting 4.0.3 is the branch to suspect. NuGet currently lists 4.0.300 (October 15), 4.0.302 (October 19) and 4.0.306 (October 28), and only 4.0.302 is named in the report.

How do you roll back GameInput to 3.5.283?

Close the game and the launcher first. You don't need to reinstall Call of Duty, and you don't need to touch ntdll.dll.

• In Installed apps, open the ... menu on Microsoft GameInput and choose Uninstall.
• Go to the Microsoft.GameInput 3.5.283 page on NuGet and click Download package. Check the page lists Microsoft as owner.
• You now have a .nupkg file. Turn on file name extensions in File Explorer, rename it to .zip and extract it.
• Open the redist folder and run GameInputRedist.msi. We downloaded the 3.5.283 package and confirmed the installer sits at that path.
• Restart Windows, confirm 3.5.283 shows in Installed apps, then launch the game.

Don't use a plain winget install here. winget install Microsoft.GameInput pulls the newest build winget carries, which on November 1 was 4.0.302, the exact version in the report. Winget's manifest also lists 3.5.283, pointing at the same NuGet package, so winget install --id Microsoft.GameInput --version 3.5.283 should work too, but we haven't run it. The manual route above is the one the report used.

Why did 4.0.302 come back after the rollback?

GameInput is not fully under your control. In the report, Gaming Services reinstalled 4.0.302 after a reset, and a Microsoft Q&A moderator says games or Gaming Services will reinstall or reconfigure the component even if you remove it.

That gives you three practical rules:

• Don't reset Gaming Services after rolling back. In the report, a reset changed nothing and restored the bad version.
• If the crash returns, re-check the version first. A new 4.0.x entry means something upgraded it. Repeat the rollback.
• Expect other games to pull it forward. GameInput is shared across your PC, and any game that ships its own installer can update it.

Does GameInput 4.0.306 fix the crash?

Nobody knows yet. Microsoft published 4.0.306 on October 28, four days after the report, but the NuGet version history lists only general 4.0 changes. Issue #53 was still open with no reply and no assignee when we checked on November 1, 2026.

If you land on 4.0.306 and the game runs, leave it alone. If it still crashes on the menus, it may be the same bug, so try the rollback. Either way, you can comment your result on the GitHub issue, because more machines would help narrow it down.

Still broken? What to try if GameInput isn't the cause

0x00001337 predates GameInput 4.0 by years. Players were posting the same code with ntdll.dll on MW2019 in 2021 and on Warzone in 2022. So if your version is fine, work through these in order:

• Repair the game files in your launcher. It's quick, though it did nothing for the GameInput case.
• Run a clean boot. Activision's Black Ops 6 PC troubleshooting article recommends starting with the bare minimum of programs, updating peripheral software and disabling overclocking or tuning tools.
• Do a clean GPU driver install. A driver update or swap is a common community suggestion for this code, though the October 30 poster had already reinstalled drivers without luck. A commenter in that thread suggested wiping the driver with DDU in safe mode, deleting the shader cache and updating the BIOS. Treat that as one player's routine, not a confirmed fix.
• Check the Warzone PC troubleshooting page for the current recommended driver versions.
• File an Activision PC crash report. Activision uses these to investigate PC crashes, and it gets your exact code on record.

If you also see stutter or frame drops rather than a hard crash, our Warzone lag and stutter guide is the better starting point.

How do you get your progress back once the crash is gone?

Lost a week of grind to crashes? Catch back up without the sweat:

• CoD Warzone Bot Lobbies: easy lobbies to farm XP and challenges.
• BO7 Account Leveling: raise your account level fast with a pro team.
• CoD Camo Unlocks (BO7): mastery camos unlocked for you.
• All Call of Duty services

FAQ

What does 0x00001337 mean in Call of Duty? It's a fatal crash code that Call of Duty players have reported for years, often alongside ntdll.dll, though some reports name the game's own executable instead. In the October 2026 GameInput report it appeared after the game's watchdog found the main thread blocked for 90 seconds. It doesn't point to one single cause on every PC.

Is ntdll.dll corrupted? Probably not. ntdll.dll is a core Windows file, and in the GameInput report it was only where the stuck thread appeared to be parked. Don't download a replacement ntdll.dll from a third-party site.

Is it safe to uninstall Microsoft GameInput? It's a normal uninstall through Installed apps, and it's the removal path a Microsoft Q&A moderator gives. Install 3.5.283 straight away so games that use the component aren't left without it.

Does the fix work on Battle.net or Steam? It's unconfirmed. Both first-hand reports come from BO7 on the Xbox app and Game Pass. The rollback is quick and reversible, so it's reasonable to test if your version reads 4.0.x.

How do I undo the rollback? Uninstall Microsoft GameInput, then run winget install Microsoft.GameInput from an administrator Terminal. That installs the newest build winget carries, which was 4.0.302 on November 1, or you can grab a newer package from NuGet the same way as the rollback.