Black Ops 2 freezes, alt-tabs me, and then won't let me back in.
-
I've now even tried to add it as an exception to my Windows Defender and still it does the same thing. However, something weird did happen that fixed my game (until a restart of my PC atleast). While trying to fix my game, it crashed a lot more heavily(?) than usual. My other programs froze and there were a few visual glitches. Everything cleared up pretty quickly and so I launched the game only to see that I could now play. Unfortunately, I'm not sure how to replicate this or what it changed that let me play, but after restarting my PC to see if my game was fixed permanently, the regular freezing occurred.
-
kid_amnesiac did you try switching to windowed borderless in the game options?
Could be that you have a software with an overlay that crashes the game, or you're using ReShade so uninstall that or one of your PC plugged in device is crashing the game (VR headset, controller, other monitors etc.) so try unplugging non necessary devices
If none of this work then upload the latest crashdump you have in Google Drive, MEGA or similar and post it here, an admin will review the file whenever they have time.
@lResxt I've also just now realized that you didn't mean the txt file... oops. I will upload them and post the link here! I have opened them in WinDBG a few times to no avail, but one of them doesn't open so I will link the 2 latest ones I have (caused only by inputting commands into the terminal after having frozen and alt-tabbed already).
Here is the folder with two DMP files: https://drive.google.com/drive/folders/1_1Pt9X2uQqhz70SEuQnI6-LWrkOIKxlu?usp=sharing
For me the one created on September 4th doesn't open and only the one from September 3rd opens but your mileage may vary.
-
Another thing I've now noticed is that the game seems to work fine on online servers now, but if I launch into a solo match of zombies then the game alt-tabs me and won't let me back in.
-
did you fix this? having the same problem
-
Having some issue
-
I have the same problem
-
same problem
-
Literally one day it started working. I don't really know why or how I made it work. I'm sorry I couldn't be of more help but maybe this will be picked up again by an admin or member of staff. I tried my best to document everything I tried.
EDIT: If you're on Windows, maybe try adding all Plutonium/BO2 folders (namely %localappdata%/Plutonium) as exclusions in Windows Defender.
-
same problem
-
Guys, I finally managed to solve the crashes and black screen issues! It was a long process, but here is the breakdown of what I did and the root cause I eventually found.
Step 1: Debugging & Software Updates
I started by analyzing the crash dump (using WinDbg) and found an "Invalid Address" error related to the EAX register and d3d11.dll. Based on this:I updated to the latest DirectX (remember to uncheck the "Bing Bar" bloatware during install). I performed a clean install of the latest stable graphics drivers. I repaired the game files to check for corruption. Result: The problem persisted.Step 2: Windows Stability Tweaks (Registry)
Research suggested Windows 10/11 often loses connection with the GPU (TDR). I applied the following registry fixes:Disable MPO (Multi-Plane Overlay): Known to cause black screens/flickering on AMD. Increase TDR Delay: Changed the timeout tolerance to 10 seconds to prevent Windows from resetting the driver too quickly. Result: The system felt more stable, but the crashes eventually returned.Step 3: The Hardware Fix (The Root Cause)
Finally, I checked my BIOS/UEFI settings.My Setup: ASUS TUF B550m Gaming, Ryzen 5 5700G (Integrated Graphics), and 4x8GB Asgard RAM (Model VMA45UG-MEC1U22T3). The Issue: My motherboard's D.O.C.P/XMP profile was automatically setting the RAM to 3600MHz. However, looking at the specs for my specific RAM sticks, they are rated for 3200MHz. The Solution: I manually lowered the frequency in the BIOS from 3600MHz to 3200MHz.Conclusion:
Since I am using an APU (5700G), my system RAM acts as my Video Memory (VRAM). Because the RAM was unstable at the overclocked 3600MHz speed, it was causing address faults, leading the "GPU" to crash and triggering the d3d11.dll errors. Lowering it to the manufacturer's rated speed fixed everything.EDIT: REGEDIT
Windows Registry Editor Version 5.00 ; FIX 1: Desativar MPO (Causa telas pretas e piscadas na AMD) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm] "OverlayTestMode"=dword:00000005 ; FIX 2: Aumentar o tempo de tolerância do driver (TDR) para 10 segundos ; Isso impede que o Windows "mate" o vídeo se ele travar por um instante [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers] "TdrDelay"=dword:0000000a "TdrDdiDelay"=dword:0000000av
