imagefile13.pak issues

[*Harl3y*Qu!nn*]

this game keeps crashing, giving image file 13.pak error what is this, and why? have tried every suggestion online, now I want it fixed cant play the game!

[*Harl3y*Qu!nn*]

I know you pain, and I am getting very annoyed. I paid a lot of money for this game and the season pass and I bought it for the multiplayer, but it fustrates the hell out of me.

[ATVIAssist_Sean]

The disc read error is more related to files than anything to do with a disc, weirdly enough, but yeah please do let me know if you send over that information and I'll forward it up to our other teams to investigate. Thanks.

[*Harl3y*Qu!nn*]

ok so i cant figure out how to send these files. It keeps crashing and I feel I should not have to deal with this.. I am so annoyed, had a contract need 3 more kills to finish it 90 kills and bam dang game crashes and I fail it because I had 10 minutes left but the crash took my time up and so I lost my contract and the coins i spent on it.. thank you so much COD and steam. tired of the crashing, I have reached my limit with this...will not make the mistake of buying season passes on a game until I know it is not a bugging out crash fest.

[*Harl3y*Qu!nn*]

this is not just me having this issue and COD and steam needs to fix this.. we spend a lot of money on this game to have it crash all the time...I feel if your gonna charge 60 a game and then charge for a season pass then it should work right!!!

[ATVIAssist_Sean]

Originally posted by *Harl3y*Qu!nn*:

this is not just me having this issue and COD and steam needs to fix this.. we spend a lot of money on this game to have it crash all the time...I feel if your gonna charge 60 a game and then charge for a season pass then it should work right!!!

I understand where you are coming, especially as someone who plays on PC at least half of the time, but I'm afraid I've only seen this error a few times before and it was fixed either through Verify Integrity of Reinstall.

We of course don't want you to have to go any tough or time consuming troubleshooting, which is one of the reasons we always start with the shortest and quickest troubleshooting options, but in your case you've tried all of those basics. The only options after that would be to get your information and sent it up to one of other teams that have more experience with PC troubleshooting.

Let me know and I'd be happy to help with that, but if it is something that started with a patch you could wait until the next update (which is relatively soon) and see how it performs after that.

[grirvan]

My crashing has never ended. Some days are worse than others. Play a ton of other games, no problem, including Call of Duty games.

[grirvan]

image 1 and image 177 errors inless than an hour. Very discouraging.

[ATVIAssist_Sean]

Originally posted by grirvan:

image 1 and image 177 errors inless than an hour. Very discouraging.

Hey there, sorry to hear you are running into some issues too. Have you been able to discern if the crashing is related to anything on your end or just the game? For instance, have you tried changing graphical settings, updating drivers, updating Windows, Verify Integrity of the Game Files, or even reinstalling? Did any of that have any effect on the crashing or did it keep persisting at the same frequency?

[Carlsberg]

Odd times i have errors like that i download a new copy of the file to a different area of the disk to eliminate the possibility its a read issue. Steps i take are;

1. rename the file, (so it will not be recognised).
2. verify the game files, the file will be replaced with a new copy elsewhere on the disk.
3. delete the one you renamed.

That usually works i find. (don't forget to note the name you give it so you can find it again).

[grirvan]

I have tried multiple drivers, graphics settings high and low, windows 10 is up to date, verified integrity many many times and it never has shown corrupt or missing files. I have reinstalled multiple times, including on a totally different drive and it does the same thing. I have even deleted all image.pak files, then verified integrity and it re-downloaded those files. Then I copied those "good files" to another location and it when it happened again, I went to the copies location and replaced the culprit image.pak file with a known good one and it still occurs. I am exhausted of ideas. Please note: it is not just image13.pak as the thread title, it has been many different image.pak numbers.

[Carlsberg]

Originally posted by grirvan:

I have tried multiple drivers, graphics settings high and low, windows 10 is up to date, verified integrity many many times and it never has shown corrupt or missing files. I have reinstalled multiple times, including on a totally different drive and it does the same thing. I have even deleted all image.pak files, then verified integrity and it re-downloaded those files. Then I copied those "good files" to another location and it when it happened again, I went to the copies location and replaced the culprit image.pak file with a known good one and it still occurs. I am exhausted of ideas. Please note: it is not just image13.pak as the thread title, it has been many different image.pak numbers.

Copying the "known good file" is not the same, neither is deleting and replacing, it still comes from the same disk space and if its a read issue it will not appear as a fault until the file is read, it needs to be replaced anew in another location.

[*Harl3y*Qu!nn*]

Well Black ops 4 sounds to be out of the question for my husband and I, since this one is not working and we cant play together and seem to have wasted a lot of money and time on it....2 times the game cost and 2 times the season pass and then a xbox one edition also...but I think I am fed up and wont be buying that one...

[grirvan]

Originally posted by Carlsberg:

Odd times i have errors like that i download a new copy of the file to a different area of the disk to eliminate the possibility its a read issue. Steps i take are;

1. rename the file, (so it will not be recognised).
2. verify the game files, the file will be replaced with a new copy elsewhere on the disk.
3. delete the one you renamed.

That usually works i find. (don't forget to note the name you give it so you can find it again).

Please confirm I understand your instructions correctly:
1) after error occurs, identify the exact image.pak file that was error-ed (which will be located in COD WWII directory) and rename something else
2) verify files integrity and it should automatically re-download that file
3) go back to "renamed" (error-ed) file and delete it

[grirvan]

Had an image1.pak error last night. Renamed the file to a dummy .pak name. Verified files and it found the one missing and it replaced. Deleted the original file I renamed. Played 10 more minutes and had another image1.pak error. :( :( :(

[GaNdolph]

Check your RAM. In my case it was a faulty memory module