Call of Duty®

Call of Duty®

View Stats:
Vakarian Nov 2, 2022 @ 1:32pm
What causes this error?
Crashing mid game every 10 or so minutes with this error code 0x00001337 (0) N
Nothing pops up on google about it....
< >
Showing 1-15 of 26 comments
Do you have razer cortex?
Vakarian Nov 2, 2022 @ 1:40pm 
Originally posted by Count Istvan Teleky:
Do you have razer cortex?
Nope, i don't have any software from Razer
Vakarian Nov 2, 2022 @ 1:41pm 
Originally posted by Count Istvan Teleky:
Read, might help:
https://quoramarketing.com/how-to-fix-modern-warfare-2-error-code-0x00001338-0-n/
Edit: i actually opened and read the damn thing and saw the fixes it told me to do, i've already done a majority of these and nothing has helped
Last edited by Vakarian; Nov 2, 2022 @ 1:42pm
0x0000 1337 (0) N is in there.

An issue with the game’s files is indicated by the error number 0x00001338 (0). Fortunately, there is a solution to this problem so that you may resume playing the game you adore. We will demonstrate how to resolve error code 0x00001338 in Modern Warfare 2 in this article (0).

Launch the Game Again
In most cases, the Modern Warfare 2 error codes 0x00001338 (0) N and 0x00001337 (0) N are just a glitch, and a relaunch of the game should fix the issue. The error message asks for a scan and repair, but only do that if your game fails to launch the second time. When you launch the game, run it in safe mode and you should be able to play fine.

Switch back to default skins
Several reports have been concerned about this specific trigger that makes the game crash. They repeatedly encounter the same problem number while attempting to play the game, preventing them from finishing even a single match. Fortunately, they were able to resolve the problem by altering their skin. They were all playing using any second skin, which was why their game was crashing since it was faulty.

Make sure you don’t have any skin other than the basic skin before, and try relaunching the game.

Delete the player record folder
The previous step has to be backed with deleting the player data of the game. You may also try removing the “players” folder from CoD Modern Warfare 2 documents to see if it resolves the 0x00001338 problem. After that, your problem should be rectified. However, you might need to reset some of the game’s default settings.

Follow these steps if you don’t know how to delete the “players” folder: In File Explorer, navigate to the Documents folder on your computer.

Go to your computer’s Documents folder in File Explorer.
Access the Call of Duty Modern Warfare 2 Beta folder within the Documents folder, then use the right-click menu to choose “Delete” after selecting the player’s folder.
After that, start the game, change the settings as desired, and test it to see whether the problem persists.
Baba-Sanya Nov 5, 2022 @ 1:01pm 
Originally posted by Count Istvan Teleky:
0x0000 1337 (0) N is in there.

An issue with the game’s files is indicated by the error number 0x00001338 (0). Fortunately, there is a solution to this problem so that you may resume playing the game you adore. We will demonstrate how to resolve error code 0x00001338 in Modern Warfare 2 in this article (0).

Launch the Game Again
In most cases, the Modern Warfare 2 error codes 0x00001338 (0) N and 0x00001337 (0) N are just a glitch, and a relaunch of the game should fix the issue. The error message asks for a scan and repair, but only do that if your game fails to launch the second time. When you launch the game, run it in safe mode and you should be able to play fine.

Switch back to default skins
Several reports have been concerned about this specific trigger that makes the game crash. They repeatedly encounter the same problem number while attempting to play the game, preventing them from finishing even a single match. Fortunately, they were able to resolve the problem by altering their skin. They were all playing using any second skin, which was why their game was crashing since it was faulty.

Make sure you don’t have any skin other than the basic skin before, and try relaunching the game.

Delete the player record folder
The previous step has to be backed with deleting the player data of the game. You may also try removing the “players” folder from CoD Modern Warfare 2 documents to see if it resolves the 0x00001338 problem. After that, your problem should be rectified. However, you might need to reset some of the game’s default settings.

Follow these steps if you don’t know how to delete the “players” folder: In File Explorer, navigate to the Documents folder on your computer.

Go to your computer’s Documents folder in File Explorer.
Access the Call of Duty Modern Warfare 2 Beta folder within the Documents folder, then use the right-click menu to choose “Delete” after selecting the player’s folder.
After that, start the game, change the settings as desired, and test it to see whether the problem persists.
0x0000 1337 is not 0x0000 1338
grego Nov 6, 2022 @ 4:16pm 
Having the same problem, did you end up finding a fix if not do you have a low or high price build?
Vakarian Nov 7, 2022 @ 10:05am 
Originally posted by grego:
Having the same problem, did you end up finding a fix if not do you have a low or high price build?
i fixed it by installing nvidias new hotfix drivers, and deleting the players folder (Documents/ Call of duty). haven't crashed since.
Martin Cloon Nov 7, 2022 @ 10:40am 
Originally posted by Vakarian:
Originally posted by grego:
Having the same problem, did you end up finding a fix if not do you have a low or high price build?
i fixed it by installing nvidias new hotfix drivers, and deleting the players folder (Documents/ Call of duty). haven't crashed since.


Unfortunately not worked for me
Steegis Nov 14, 2022 @ 12:48am 
Yeah I have the latest drivers from NVIDIA and it still crashes on me I tried deleting my temp files so ill see how that goes tomorrow
Brainbleach Nov 14, 2022 @ 1:07am 
It’s the new nvidia drivers causing these crashes. You need to rollback drivers.
I found that it might be related to Nvidia DLS so try disabling any Nvidia-specific option?
Martin Cloon Nov 14, 2022 @ 10:58am 
Latest drivers arent the fix. Not had any crashes since removing riot shield
StaticKillz Nov 14, 2022 @ 5:43pm 
Originally posted by JordyCrumpet:
Latest drivers arent the fix. Not had any crashes since removing riot shield
I had never gotten the 1337 error prior to adding riot shield and then I crashed 4 games in a row. Removed riot shield and haven't crashed since. Thanks for the heads up!
Martin Cloon Nov 15, 2022 @ 11:35am 
Originally posted by StaticKillz:
Originally posted by JordyCrumpet:
Latest drivers arent the fix. Not had any crashes since removing riot shield
I had never gotten the 1337 error prior to adding riot shield and then I crashed 4 games in a row. Removed riot shield and haven't crashed since. Thanks for the heads up!

No problem :) Saw someone recommend it on reddit a couple weeks ago after being very frustrated myself
< >
Showing 1-15 of 26 comments
Per page: 1530 50

Date Posted: Nov 2, 2022 @ 1:32pm
Posts: 26