Plutonium

Your crash log only shows a generic 0xC0000005 access violation, not a specific map/script error. Since it happens in vanilla, in every mode, I’d stop focusing on BO2 files and test local conflicts instead. Try this in order: fully uninstall Norton/third-party AV for a test add exclusions for BO2 and %localappdata%\Plutonium disable/close all overlays and hook tools (Discord, Steam, GeForce, RTSS, ReShade, Overwolf, capture software) check Event Viewer after the crash for the faulting module name reinstall the Plutonium launcher clean If it still crashes after that, the next useful thing is the .dmp file or an Event Viewer faulting module, because the txt alone isn’t enough to pin it down.

Your crash log only shows a generic 0xC0000005 access violation, not a specific map/script error. Since it happens in vanilla, in every mode, I’d stop focusing on BO2 files and test local conflicts instead. Try this in order: fully uninstall Norton/third-party AV for a test add exclusions for BO2 and %localappdata%\Plutonium disable/close all overlays and hook tools (Discord, Steam, GeForce, RTSS, ReShade, Overwolf, capture software) check Event Viewer after the crash for the faulting module name reinstall the Plutonium launcher clean If it still crashes after that, the next useful thing is the .dmp file or an Event Viewer faulting module, because the txt alone isn’t enough to pin it down.