A Memory Leak Issue Reported with Call of Duty: Modern Warfare?
A Memory Leak Issue Reported with Call of Duty: Modern Warfare?
I'm experiencing a frustrating problem with the new Modern Warfare game. Every time I launch it, it freezes about 30 seconds into the main menu and then crashes with a CTD (Crash To Desktop) – without any error message. This happens approximately 9 out of 10 times, though occasionally it will load the game and stay running for a short time before crashing unexpectedly. I've tried numerous troubleshooting steps, including performing a clean boot by disabling non-Microsoft apps, increasing the page pool size in the game installation folder, removing overclocking from my CPU, GPU and RAM, setting the game priority to "Normal" in Task Manager, performing a clean install of Windows, reinstalling the game and Battlenet, running game file repair in Battlenet, testing my RAM with MemTest86 (with no errors detected), checking the hard drive for errors with a disc check (no errors found on my SSD), running an antivirus scan (no viruses detected), disconnecting and closing my VPN, clearing NV_Cache, and deleting user files related to the game. My PC specifications are: Asrock B450 Steel Legend motherboard, Ryzen 7 3700X CPU, MSI RTX2070 Gaming Z GPU, Corsair Pro 3600MHz 16GB RAM (2x8GB), EVGA 650W PSU. My temperatures during gameplay never exceed 60-65 degrees Celsius. I've also attached the crash dump file, which indicates an Access Violation (code c0000005) likely due to memory corruption, specifically within the `swprintf_s` function. The dump file shows a thread issue and indicates a potential problem with NV Optimus if using an Nvidia-based GPU.
Could you please outline the hardware specifications of your computer? In particular, could you detail your processor type, memory capacity, and RAM configuration? Running diagnostic tests such as Memtest86+ could help identify potential issues with failing components.
Hello! Apologies, I now realize that I should have included my glasses and a log of the steps I've taken. I’ve revised the discussion at the beginning, and the solution is Corsair 3600MHz 16GB RAM. I attempted to disable the XMP profile, reducing it to its standard 2133MHz speed, but this had no effect.
While I can't guarantee this will resolve your problem, it proved beneficial for me on my X570 motherboard. I repeatedly experienced crashes following the conclusion of multiplayer matches, a problem that hadn't occurred before. After updating my motherboard’s chipset drivers, this issue disappeared entirely.
https://www.amd.com/en/support/chipsets/...t-am4/b450
Hello! I verified my graphics card driver, reinstalling it completely to ensure it was up-to-date, but the problem persists. 🙁 I’m becoming increasingly frustrated with this issue. The game functioned correctly prior to the update to version 1.20, and since that change, it has consistently produced errors.
I am experiencing the identical problem, which is incredibly irritating. I performed three tests with memtest86... my computer appears to be operating without issues.
Not at all. I’ve been informed that it's linked to comparable problems, yet I remain skeptical.
I believe a problem with the graphics driver might be at fault. I’m currently running Driver Verifier, and it's generating a Blue Screen of Death loop – quite amusing, actually. Perhaps I am identifying the root cause.
I wouldn’t expect a quick resolution, as I resolved my problem by disabling Argus Monitor—I do use it. Subsequently, the developers released an official announcement acknowledging the issue but emphasizing that it stemmed from within the game itself. This aligns with my experience, as the problem initially appeared only after recent updates to the game. Since removing Argus, I haven’t experienced any further difficulties.
I attempted a diagnostic step to narrow down the cause, performing this prior to discovering Argus’s involvement. I established a new user account on my computer—it doesn't require administrator privileges, simply a standard one—and logged into that account to load the game. The game should then function without problems. If it does, begin installing software and applications from your other user account one at a time; these typically install without issue but may not run. This methodical approach can help rule out interference from external programs.
It appears that the latest patch and updates to the game’s anti-cheat system have created a conflict with Argus, so it's possible that other monitoring software or applications are also affected. Consider if you have any additional tools running? This might be a worthwhile experiment.
For now, disregard the "Memory_Corruption" error; it turns out that Windows frequently generates this message for a wide range of reasons, which offers little assistance. Examining my crashdump revealed that Argus was not mentioned, despite the game crashes occurring.
Furthermore, System File Checker causing blue screen errors on startup—I experienced this as well—so avoid pursuing that avenue of investigation.
Eventually, I discovered a problematic driver through Driver Verifier—scpvbus.sys, an outdated component for a previous PS2 USB controller that I hadn't touched in a long time. It’s challenging to determine if the issue is connected, as Monster Hunter World occasionally functions without problems, however the game now operates flawlessly. I also utilize Hard Disk Sentinel, which performs several similar functions to Argus, providing additional avenues for investigation should the crashes reappear.