For those crashing with game_steam_ship.exe Post your specs

[DANTIGO]

**PSA: There is a user who has posted numerous times to this thread that tries to get you to either download shady software or manipulate your registry on Windows. I would advice to ignore any input from this user that is potentially harmful to your system. These articles were made 2 years ago for the 2019 Modern Warfare and for older builds. The titles were repurposed to garner click bait.**

Keep it to this executable crash only and an error code similar to 0x00001338 (0) N
There's a lot of different ones in our case, but if you can't launch the game at all and experience something like this please share your specs in the discussion.

Again this is for those who can't even get into the game and if their game crashes on start up or 15 minutes into the game. If your whole PC crashes you probably have a different issue going on, and if that's the case please do not share your specs. Lets keep this targeted to one issue at a time.

For those who are "shadowbanned" please make a different thread.
We need data only related to this issue.

I just want to see what kind of systems also have the same issue as me, and perhaps we can all see how wide spread this issue is. I have logged over 180 hours into this game, and as the Warzone 2 update came out I haven't been able to get past the title screen since. On top of that it has gotten much worse recently where I just receive a black screen on launch followed by a crash error shortly after.

Most of us have all tried the common work around, so don't use this thread to post what has worked for you, or what you think is wrong. We all know by now that this game is just entirely unstable, and we shouldn't have to resort to those kind of steps.

We need some sort of public statement or acknowledgement from the devs instead of a little badge hidden away in their trello boards stating that they are "investigating."

Post your GPU as well as the driver version
Your CPU
Ram and Speed
Motherboard
and what OS you're currently on.


GPU: NVIDIA GEFORCE RTX 3080 (Latest Driver 527.56)
CPU: 13th Gen Intel(R) Core(TM) i9-13900k
RAM: DDR5 32GB 5600MHz
OS: Windows 10 (latest update)
Mobo: PRIME Z790-A WIFI

Please follow this format. If you're unsure what hardware you have. You could always click the help drop down on the top left of steam, and select "System information"

Edit: Your Driver version either for GPU or OS, and what type of ram you have (DDR) matters. Please don't forget those


**UPDATE: I found the issue. If you're having error 1338 or 7 it's due to your cpu cores failing during shader optimization. So assuming you have a decent cpu, your seating pressure may be causing an issue, which would just require you to re-seat your CPU and see if that does anything, or you have a shot CPU with broken cores that specifically get used during shader optimization.

In my case core 4 and 6 were experiencing failures, and both of those cores get used during shader optimization for every DX12 game, thus crashing on start up for anygame in that frame work.

If you want to see if your CPU is failing, i recommend doing a stress test OCCT. Do this with stock settings on your MB and don't overclock. Especially if you're running into these errors stock, you will be able to RMA your CPU with your warranty, as long as you don't show know signs of overclocking or volt manipulation.**

If I could I'd delete this post because that mantis kid is still giving people false leads and harmful work arounds, but I can't, so I'm just leaving this update here.

I've RMA'd my CPU and I'm able to play now

[DANTIGO]

So apparently since December 15th, crashing is no longer flagged as an issue and is marked as resolved. This is interesting because this is the day that my issue got worse. Here's the link to the post on Trello. https://trello.com/c/jQ0cPghO

[DANTIGO]

Although there's not much insight, Raven Software still has theirs as an Advisory under investigation. https://trello.com/c/7iZtA17C

[DANTIGO]

Bump

[1MantisPhoenix]

Play with studio driver 526.56, not game ready
GTX1070, i5 10400f, 32GB RAM,
Crashes fixed with the right settings. Game ready made it crash again. Studio drivers fixed it again.
ie. Not crashing,
Win10 21H2, 19044.2364

[1MantisPhoenix]

Tell me what your nvidia control panel low latency is, and what your in-game nvidia reflex settings are,

[Mapify]

I5 9600K 3060 32 gig of ram n 2 tb m.2

[DANTIGO]

Ursprünglich geschrieben von 1MantisPhoenix:

Play with studio driver, not game ready
GTX1070, i5 10400f, 32GB RAM,
Crashes fixed with the right settings. Game ready made it crash again. Studio drivers fixed it again.

I'm gonna try this right now!

Ursprünglich geschrieben von 1MantisPhoenix:

Tell me what your nvidia control panel low latency is, and what your in-game nvidia reflex settings are,

I can't get into the game at all but I've been attempting to run the game with everything as low as possible i just can't open it

Edit: Still crashing at start up. Same error 0x00001338 (0) N

[DANTIGO]

Ursprünglich geschrieben von Zeus:

I5 9600K 3060 32 gig of ram n 2 tb m.2

Are you able to get any gameplay in at all, or do you also crash at start up?

[1MantisPhoenix]

Ursprünglich geschrieben von DanteIndigo:

Ursprünglich geschrieben von 1MantisPhoenix:

Play with studio driver, not game ready
GTX1070, i5 10400f, 32GB RAM,
Crashes fixed with the right settings. Game ready made it crash again. Studio drivers fixed it again.

I'm gonna try this right now!

Ursprünglich geschrieben von 1MantisPhoenix:

Tell me what your nvidia control panel low latency is, and what your in-game nvidia reflex settings are,

I can't get into the game at all but I've been attempting to run the game with everything as low as possible i just can't open it

Edit: Still crashing at start up. Same error 0x00001338 (0) N

Crashing at startup, was a cryptography thing, :) trying to find the fix for you,
"6 . Edit the Registry
You can also make a Registry edit to solve Dev Error 6036. Here's what you need to do:

Open the Registry Editor (see how to open the Registry Editor for in-depth steps) and navigate to the following location.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography
Right-click on MachineGuid and choose Modify.
Type d1eb246e-6243-4460-a88e-5d4e52b1ef6b in Value data and click OK.
"
Checkout the link that fix 6 is from: https://www.makeuseof.com/windows-modern-warfare-dev-error-6036/


But also, there's multiple errors they link to one error :
"There are several factors that can lead to the 0x00001338 Error in Modern Warfare 2, such as missing/corrupted game files, in-game character skin issues, corrupted Battle.net Cache, outdated GPU drivers, etc. This error can be pretty easy to fix, as it has many confirmed fixes.".

Let us know how studio drivers go,


Otherwise, last resort will be trying steam launch option -dx11 to help make this run,

[DANTIGO]

Just tried undervolting my GPU too with no success

[DANTIGO]

I've tried dx11 but I'm pretty sure that's impossible for this game. I don't think the Engine allows for that

[1MantisPhoenix]

"
Double-click MachineGUID ('TAKE NOTE OF YOUR KEY UNDER "VALUE DATA" IF THIS AFFECTS YOUR COMPUTER NEGATIVELY YOU CAN ALWAYS ENTER YOUR OLD KEY AGAIN') I would recommend storing the key in a notepad file for the time being just to be extra safe if you are worried your pc will break (It won't) but I wouldn't recommend losing the key for safety reasons. Don't be scared though, everything will be okay I promise."

Also note the original default key, in case it gives you issues, you can revert it back,
but, as Elboss let me know, the key was actually matching, and by him entering the value again, it suddenly worked,

[DANTIGO]

Ursprünglich geschrieben von 1MantisPhoenix:

Ursprünglich geschrieben von DanteIndigo:

I'm gonna try this right now!





I can't get into the game at all but I've been attempting to run the game with everything as low as possible i just can't open it

Edit: Still crashing at start up. Same error 0x00001338 (0) N

Crashing at startup, was a cryptography thing, :) trying to find the fix for you,
"6 . Edit the Registry
You can also make a Registry edit to solve Dev Error 6036. Here's what you need to do:

Open the Registry Editor (see how to open the Registry Editor for in-depth steps) and navigate to the following location.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography
Right-click on MachineGuid and choose Modify.
Type d1eb246e-6243-4460-a88e-5d4e52b1ef6b in Value data and click OK.
"
Checkout the link that fix 6 is from: https://www.makeuseof.com/windows-modern-warfare-dev-error-6036/


But also, there's multiple errors they link to one error :
"There are several factors that can lead to the 0x00001338 Error in Modern Warfare 2, such as missing/corrupted game files, in-game character skin issues, corrupted Battle.net Cache, outdated GPU drivers, etc. This error can be pretty easy to fix, as it has many confirmed fixes.".

Let us know how studio drivers go,


Otherwise, last resort will be trying steam launch option -dx11 to help make this run,

I don't trust this Registry Edit step. Not something we should have to tamper with

[1MantisPhoenix]

Here's another big fix thread, https://ugetfix.com/ask/how-to-fix-0x00001338-error-in-call-of-duty-modern-warfare-2/#:~:text=Battle.net%3A,integrity%20of%20the%20game%20files

[DANTIGO]

Ursprünglich geschrieben von 1MantisPhoenix:

Ursprünglich geschrieben von DanteIndigo:

I've tried dx11 but I'm pretty sure that's impossible for this game. I don't think the Engine allows for that

it works, i've played in dx11 and 12, steam launch option must be used,

my current launch options are -dx12 -high
You do not need to undervolt your GPU, you can underclock the GPU Core clock , either turn off all overclock on the GPU Core, or prevent it from boosting over 2100Mhz,

This is one of the reasons why I stated not to comment tips on how to fix this error. This is utter bs because this game will not launch with DX11. It's impossible. It's just not a thing. What ever command you type the game will always be DX12. This rule applies to the previous CoD as well