As an RX 7800 XT user with a fully optimized, high-end system, I can confirm that the persistent AMD DX12 crashes in Black Ops 7 are not a user-side problem. My setup includes an Intel i7-14700KF CPU, 32GB of DDR4 RAM running at 3600MHz, and an NVMe Gen4 SSD, all meticulously configured for stability. I have disabled Resizable BAR and Above 4G Decoding, closed background applications like Chrome and Discord, turned off overlays, and set all AMD graphics options to safe modes—including Anti-Lag, Enhanced Sync, and RSR. In-game, I’ve reduced textures and shaders to low, limited VRAM usage, and run in Fullscreen Exclusive mode.
Despite these extensive optimizations, the game consistently crashes at the same moment: during the transition after the killcam or scoreboard, when returning to the lobby. The crash signature consistently points to cod.exe and KERNELBASE.dll, matching reports from thousands of AMD users across RX 6000 and RX 7000 series cards. Analysis of crash dumps shows that while page faults decreased from 31 million to 5 million after optimization, working set memory still balloons to 5–6GB, with pagefile usage spiking to 7–9GB just before the crash. This occurs precisely when the engine attempts to unload and reload DX12 buffers post-match.
This issue is clearly rooted in the game’s engine, as NVIDIA users do not experience these crashes. With no communication or patch from Treyarch since launch, players are refunding the game and unable to enjoy it with friends. It’s time for the developers to acknowledge and resolve this unacceptable problem.
It’s a relief to see someone with such a high-end, optimized setup having the exact same crash at the lobby transition; my experience with my 6800 XT is identical, down to the cod.exe and KERNELBASE.dll error. I’ve spent hours tweaking settings to no avail, so this confirms my suspicion that it’s a deep driver or game engine issue on AMD’s side. Has anyone found a temporary workaround that actually lets you stay in the lobby after a match?
I completely understand your frustration, especially seeing that identical KERNELBASE.dll error on a different card like the 6800 XT—it really points to a widespread AMD DX12 issue. While a true fix is pending from AMD or the developers, one temporary workaround that has allowed some players to stay in the lobby is to set the game’s process priority to “Normal” via Task Manager immediately after launch, as “High” priority seems to exacerbate the crash. Let me know if that helps at all on your system, and please share any other findings you come across.
I had the exact same crash pattern on my RX 6800 XT, right after the killcam before the lobby, so seeing you detail that specific moment with a high-end i7 setup confirms this is a deep driver or game bug. It’s frustrating to have done every recommended fix, like disabling Resizable BAR and all overlays, only to hit the same wall. Has anyone found a temporary workaround that actually lets you finish a match?
I hear you—it’s especially validating yet frustrating to see that same crash pattern, like right after the killcam, persist even on a different high-end AMD card. While a true fix awaits a driver or game patch, some players report that manually setting the game’s process priority to “Normal” in Task Manager and disabling any hardware monitoring software can sometimes get you through a match. Let me know if that tweak changes anything for your 6800 XT.
To address the issue, try disabling all settings in Windows Security under Exploit Protection. Additionally, turn off the Windows Game Bar.
I play on PC and haven’t experienced any crashes so far. Hopefully they resolve this issue for those of you who are affected.
My friends are experiencing the same issue.
The complaint post reads like it was written by ChatGPT.
As a non-native English speaker, I use ChatGPT to ensure my message is clear. How does that affect the actual game issue?
As a French user, I’m experiencing the same issue.
This issue also affects Nvidia systems. My friend with a 4070 Ti and I with a 5070 can’t progress far in endgame or zombies due to DirectX crashes. I suspect this is related to the anti-cheat, as we tested Black Ops 6 and had no problems in either Zombies or Multiplayer. Even switching to DX11 via launch options doesn’t resolve it.
Please release a patch quickly.
I had frequent driver issues with Cold War when using an AMD card. Unfortunately, this seems to be a recurring problem with Treyarch games.
I have an RX 6800 XT and Ryzen 7 5800X, and my game hasn’t crashed once since launch, even with frequent play.
The issue can vary based on your specific setup, including:
– AMD driver version
– Windows build
– In-game settings
– GPU load
– CPU model
– Background applications
– Anti-cheat software
Is this an AI response? We’re using the same anti-cheat since we’re playing the same game, and likely the same Windows version. My GPU load is at 100% because I max out the game settings, which would typically make performance worse. I’m on the latest drivers.
NVIDIA users are also experiencing kernel issues. I completely reformatted my hard drive and reset my system, but it still doesn’t work.
My debug indicates the problem originates from rand.sys, which is part of the anti-cheat system that’s more aggressive than the beta version.
Is there truly nothing we can do?
To address the DirectX error, I was able to significantly reduce crashes by doing the following:
– Disabling EXPO/DOCP in the BIOS
– Setting the VRAM target to 50% in the game settings
– Installing the latest NVIDIA hotfix driver
I understand your frustration. I’m experiencing the DirectX overclock detected crash as well, even though I’m not overclocking. I also continue to get consistent packet bursts despite trying everything possible on my end to fix it. This has been an ongoing issue for years.
I crash at the end of every match, which is unacceptable since we paid for the game. Is there a way to contact customer support about this?
I’m using Nvidia and also experiencing crashes every hour or two with DirectX error 0x887A0005, so this issue isn’t limited to AMD systems.