Call of Duty®

Call of Duty®

View Stats:
cannot launch the multiplayer
after last season update, I am able to launch call of duty HQ, but when I open the multiplayer or anything relating to warzone or dmz, the game crashes with a cod error. The campaign launches just fine. I think part of the issue is because when you launch the game it restarts and launches into modern warfare II thus causing the issue. I don't think its ever going to be fixed. Modern warfare II has been sitting in my library and has been unplayed for over a year now. the game worked for mutliple months until the first seasonal update. then it broke the game. I have too many hours in the game to refund it and I am stuck with a game I can't play and wasted $62
< >
Showing 1-1 of 1 comments
The Weasel Apr 29, 2024 @ 7:30pm 
check out https://support.activision.com/warzone-2/articles/crashes-or-game-freezes-in-warzone-2

https://support.activision.com/warzone-2/articles/warzone-2-pc-troubleshooting

Choose warzone 2 then gameplay then crashes then click create a support ticket. https://support.activision.com/options?

Is your bios up to date by checking your motherboard website?

If not you would need a USB format the USB to fat 32 then download it then put it on the USB and plug it in to your PC and update.

Make sure all your drivers are up to date
Make sure windows is up to date

Also make sure you actually meet the requirements by using

https://www.pcgamebenchmark.com/call-of-duty-warzone-2-system-requirements

Could be over heating go to bios and change your fan speed for cpu or graphics card or both.

Check to see if you have any mini dumps by clicking c drive then windows then mini dumps

When using the event viewer, do custom, as this can narrow down the issue, and click saved and enter a name for it.

To create a custom view for the event viewer, click Action, then click the time the error happened. Then click error.

Then click on the event log windows.

Then click okay, then click saved.

This helps you narrow down the issue, then get WinDpg from the Microsoft Store, open WinDpg, and make sure to run as an admin. Click file, then go to file explorer.

use windpg on the mini dump file. Click analyze, and then when it is done, Failure bucket ID is what you're looking for.
Last edited by The Weasel; Apr 29, 2024 @ 7:35pm
< >
Showing 1-1 of 1 comments
Per page: 1530 50

Date Posted: Apr 29, 2024 @ 7:26pm
Posts: 1