Distinguish shader, connection and crash symptoms, then check game files, drivers and networking by platform.
First separate the issue into shader preloading stuck, packet burst or latency during a match, or a crash or freeze. Record the full error code, platform, when it happens and whether it began after an update, then check official service status. Change one thing at a time and retry so you can identify what helped.
Quick navigation
- PC shader preloading
- Packet burst and networking
- PC crashes and file verification
- PlayStation and Xbox
- If the issue persists
Identify the symptom first
| Symptom | Check first | What it does not prove |
|---|---|---|
| Shader preloading appears after launch but the percentage is incomplete | Stay in the main menu and note progress and whether it has truly stopped for a long time. | Preloading again after an update does not necessarily mean files are damaged. |
| Packet burst, teleporting or latency appears during a match | Check service status, latency or packet-loss indicators and local network load. | One indicator cannot establish whether the computer or server is at fault. |
| The game returns to the desktop or console screen, or freezes completely | Record the error code, close and restart the game, and check for updates. | Reinstalling is not guaranteed to help; verify or repair files first. |
PC shader preloading
- After updating, launch the game and stay in the main menu until preloading finishes. Official guidance notes that leaving the menu may interrupt preloading.
- If the same progress remains completely unchanged for a long time, record the position and waiting time, close the game normally and restart the computer. Launch again and observe from the main menu.
- Check NVIDIA, AMD or Intel's official website for a driver supported by your graphics card. Restart after updating and allow shaders to finish. Check hardware support first and avoid drivers from unknown sources.
- If it still fails, verify files using the platform steps below and ensure both the system drive and game drive have sufficient space. Official guidance gives no universal preload duration for all devices; do not repeatedly force-close the game or delete unknown system folders.
Packet burst and networking
- Open official online service status and also check your PlayStation, Xbox or PC launcher's service status. If service is disrupted, record the time and test again after recovery.
- Stop large downloads, streams or backups on the same network. If possible, connect directly to the router with an Ethernet cable; Wi-Fi players can test again from the same location for comparison.
- Safely restart the router, wait for the network to return and try a match. Console players can run their network connection test; PC players should record displayed latency, packet loss and the time the issue occurs.
- Compare other modes, devices or another trusted network. If all household devices have problems, contact your internet provider. If it occurs only in a specific mode or after an update, record the results for official support.
Stuttering can also result from performance or shaders rather than networking. Note whether the packet warning coincides with low frame rate, busy storage or a particular map. A normal one-time speed test cannot prove there was no packet loss during the whole match.
PC crashes and file verification
Update the operating system, game and supported graphics driver, close unnecessary background recording or overlays, then test again. Before verification, close the game and let downloads finish:
| Platform | Path | Note |
|---|---|---|
| Steam | Right-click the game in Library → Properties → Installed Files → Verify integrity of game files | Labels may change with client updates; wait for the check and any required download. |
| Battle.net | Gear or options on the game page → Scan and Repair | Restart afterward and see whether it still crashes in the same place. |
| Xbox PC / Microsoft Store | Xbox app game management → Files → Verify and Repair | Read prompts carefully; official guidance warns relevant operations may affect unbacked-up mods or saves, so confirm synchronization and backups first. |
If you see an 0x error, record the full code; do not assume all 0x errors have the same cause. The official known-issues page has recommended repairing the game app for some Xbox PC 0x errors. Follow official instructions for Secure Boot, TPM, account verification and security settings; do not disable two-factor authentication or anti-cheat to try to fix the issue.
PlayStation and Xbox
- If the game freezes or returns to the home screen, close and restart it. If the issue recurs, restart the console.
- Check console system and game updates, confirm downloads are complete and storage is sufficient, and run the console network test for connection issues.
- Record the complete code shown, such as a possible PlayStation CE-series error, and check the appropriate platform on the official crash support page instead of applying PC shader steps.
- If reinstalling is needed, first confirm the account, synchronization and relevant save backups and read platform prompts. This is an option after earlier steps fail, not a guaranteed fix for server issues.
If the issue persists
See official known issues and the Warzone support center. When contacting support, include platform and launcher, error code, game and system versions, when it happens, reproducibility and steps already tried. PC users can add their graphics card and driver version. Do not submit passwords or verification codes.
Sources
Revision history
— Recently updated