TL;DR
Call of Duty (Steam version) crashed on every launch with “The
application has unexpectedly stopped working”. The cause was NVIDIA
Streamline (sl.interposer.dll), the component that wires
DLSS, Frame Generation and Reflex into the game. During DirectX 12
device creation it locked its own internal mutex twice on the same
thread and threw an exception.
The fix that worked: rename sl.interposer.dll to
sl.interposer.dll.bak in the game folder. Do it in both the
main folder and the sp26 campaign folder. The trade-off is
losing DLSS, Frame Generation and Reflex until the bug is patched.
The symptom
The game never reached the main menu. A few seconds after launch, the
Call of Duty HQ crash handler appeared with the same details every
time:
The application has unexpectedly stopped working.
Error Code: 0xE06D7363 (0x00000000) N
Signature: 03646FDD-B66D8A89-3D735B2E-66FFA5F5
Module: KERNELBASE.dll
Executable: cod.exe (later also sp26-cod.exe for the campaign)
Two details in that dialog matter. 0xE06D7363 is the
code Windows uses for a C++ exception, so this is not a classic memory
crash. KERNELBASE.dll is only where the exception was
raised, not where the bug lives.
Windows Event Viewer showed nothing for the game, because Call of
Duty catches its own crashes and writes its own reports.
The system
An older platform paired with a brand-new GPU:
| Part | Model |
|---|---|
| CPU | AMD Ryzen 5 1600 (6 cores / 12 threads) |
| Motherboard | ASRock AB350 Gaming-ITX/ac, BIOS P5.60 (2019) |
| GPU | NVIDIA GeForce RTX 5060 8 GB |
| RAM | 16 GB |
| Storage | SSD |
| OS | Windows 10 Pro 22H2, later upgraded to Windows 11 Pro 24H2 |
| Game | Call of Duty via Call of Duty HQ, Steam version |
What did not work
Every one of these left the crash signature exactly the same. That
consistency was the biggest clue that the problem sat inside the game’s
own files.
| Attempt | Result |
|---|---|
| Upgrade from Windows 10 to Windows 11 | Same crash |
| Enable Hardware-Accelerated GPU Scheduling (HAGS) | Same crash |
| Verify game files in Steam | Same crash |
| NVIDIA drivers 616.56, 621.14 and 621.24 | Same crash on all three |
| Full clean driver reinstall with DDU in Safe Mode | Same crash |
| Steam overlay off (it was already off) | Same crash |
| Update Visual C++ runtimes | Already current, no change |
I also checked for injectors such as ReShade, OptiScaler and MSI
Afterburner. None were present in the game process.
Reading the crash reports
Call of Duty saves a zip for every crash in
%LOCALAPPDATA%\Activision\Call of Duty\crash_reports. Each
one holds info.json, stacktrace_crash.csv, a
minidump and dxdiag output. More than ten reports, across both Windows
versions, carried the same signature.
The stack trace showed the exception thrown from
msvcp140.dll (std::_Throw_Cpp_error), called
directly by sl.interposer.dll. info.json
flagged it as a boot crash: graphics had not finished initialising, and
no settings file existed yet.
Two more steps pinned it down:
- The ThrowInfo address in
info.jsonpoints into
msvcp140.dll. Reading the RTTI there identified the
exception type asstd::system_error. - The exception object in the minidump held error code 16,
device or resource busy. MSVC’s standard library throws
that when a thread locks a non-recursivestd::mutexit
already owns.
A scan of the crashing thread’s stack then showed the full chain:
Streamline re-enters itself during D3D12 device creation. No
third-party software was on the stack: no overlay, antivirus hook or
injector. Why it happens only on some systems is still unknown. The 2019
BIOS on this board is one suspect I never tested.
🔥 The fix
Renaming sl.interposer.dll makes the game skip NVIDIA
Streamline and start normally. Credit for the idea goes to a
Steam Community thread about a similar Streamline startup crash in
Forza Horizon 6.
There are two copies to rename, because the campaign has its own
folder with its own copy. Close Steam and the game first, then run this
in PowerShell (adjust the path to your Steam library):
cd "E:\SteamLibrary\steamapps\common\Call of Duty HQ"
# Multiplayer / main launcher
Rename-Item sl.interposer.dll sl.interposer.dll.bak
# Campaign (sp26-cod.exe)
Rename-Item sp26\sl.interposer.dll sl.interposer.dll.bak
That is the whole fix. The other sl.*.dll files can stay
as they are. If you only rename the root copy, multiplayer works but the
campaign still crashes with the same signature under
sp26-cod.exe.
To undo it, rename the .bak files back to
.dll, or run Verify integrity of game files in Steam.
Caveats
This is a workaround, not a real fix. Keep these in mind:
- No DLSS, Frame Generation or Reflex. Use FSR or
XeSS in the graphics settings if you need the extra FPS. - Do not click “Allow Verify Game Files” if the crash
dialog appears again. It restores bothsl.interposer.dll
files and brings the crash back. - Game updates can restore the files. After a patch,
check both folders and rename again if needed. - Anti-cheat risk is low but not zero. Ricochet
checks game files. I found no reports of bans for renaming NVIDIA DLLs,
but you modify game files at your own risk. - Report it. Only Activision or NVIDIA can fix the
underlying bug. Send the crash signature
03646FDD-B66D8A89-3D735B2E-66FFA5F5and the crash report
zip to Activision
Support. - Test DLSS again occasionally. After a game or
driver update, rename the.bakfiles back. If the game
launches, the bug has been fixed.
Lessons learned
- Read the game’s own crash reports before trying generic
fixes. The answer was sitting in
%LOCALAPPDATA%\Activision\Call of Duty\crash_reportsthe
whole time. - An identical signature across changes is a signal.
When an OS upgrade and four drivers change nothing, the problem is not
the OS or the driver. - The faulting module is rarely the culprit.
KERNELBASE.dllonly raised the exception. The real story
was five frames deeper. - Check every executable a game ships. Modern Call of
Duty launchers bundle several titles, each with its own copy of the same
DLLs.
