6 replies to this topic

[Surn]

I was launching into a clan assault... but had been in the mechlab on a IS mech. On game launch, FRead error.

Be sure to have one of your mechs selected before dropping in CW.

[Repasy Cooper]

I have been getting this error as well. I tried the solution you mentioned above, but it only seems to work some of the time for me.

I've had to run the repair tool multiple times, and I've noticed that each time the repair tool checks game\ghostbear.pak it discovers a CRC error:

"The file being extracted appears to be corrupted. Expected 0xC74E5A1A, Actual 0xE63964D4"

This file may be the culprit. Has anybody else had this file corrupt?

[Surn]

I have resorted to putting the newly downloaded .pak files in a separate folder so that I dont have to re-download them everytime I get a fread error. This is pretty insane.

Sometimes after the files are downloaded they simply disappear, mostly Objects.pak. So that was the first file I saved. Now, everytime I get an error... I copy my "good files" to the game or game/levels folder before running the repair tool. This saves me about 1/2 of the time to repair the game when it becomes corrupt.

[Tarl Cabot]

If you are having to run the repair tool often then I would actually be looking at system issues, primarily memory and/or harddrive. On my two systems I have only ran the repair two twice, with the first time just testing how it works and I do not recall why the second time.

Think of it this way, the paks are being opened then closed. Think of it as a book and when the book is closed a page gets folded, either due to some type of interference from another object, wind, etc. That folded page is causing an issue. That is the best way I can put it.

Memory settings set too aggressively and/or mixed memory. Run Prime95 for an hour. If able to run with fewer sticks then remove other sticks or a set of sticks and test by running MWO (for file corruption) and prime95. Switch sticks around.

Hard drive. If not disk errors then possible swapfile. Set Swapfile to none and defrag before reactivating swapfile.

My bets are with the memory, either the sticks themselves, the ram slots, bios settings or power fluctuations.

[zaid]

It ain't faulty hardware. The corrupt files and having the patcher DL the same files over and over because it erases the file it downloaded is a bug that is ~2 years old. They know it exists. They either can't fix it, or don't know how to fix it. Either way, some of us are stuck patching the game weekly. If it was hardware error, all games would get corrupted and windows would be corrupted as well. This subject has been coming up on a regular basis since beta.

[Tarl Cabot]

There is some difference between the data currently on the harddrive generating a CRC error and a download/redownload, except a download will have additional interference from the server, connection path to the player's computer. After reaching the computer then it would interact with the system's memory, motherboard, harddrive, etc. Get the picture?

If the issue were the actual download files everyone would be having issues. For the OP, the files were already on his computer when he has game issues, at which time the files are now corrupted, need to be downloaded and installed. You have seen his workaround of saving the files message #3, to replace the ones corrupted when he has an actual issue in a drop. Him moving the files from one location to another does not open them, he is able to play the game until there are errors again.

The files are unpacked during play then closed back up. The files are becoming corrupted after use. That is not a download issue itself.

Issue is being caused either by the system itself somewhere. PGI could unpack the files but would that actually fix the problem?

So far, just doing searches for players on other games who have CRC errors, either initial download, or repatching after getting several game errors, a few have reported back that replacing one piece of hardware or another has corrected the CRC issues, and for some it was affecting more than one game, not just the game itself but downloading/installing/repatching a game.

Found 4 who reported replacing ram and no more issues. 2 put the old ram in and the issues appeared almost immediately. Two replaced just the motherboard/different brand to clear up the CRC issues. One player did a clean install for the new board, but then went back, did a clean install with the old board and the CRC issues cropped up again on the first download.

Now does the above mean it is the hardware itself, or is it the setup/settings/etc? Without a more thorough investigation/tinkering it will not be known exactly the cause.

Passing the buck off onto PGI does nothing for the players having the issue now, especially if the issue is the person's system.

[Eldamar]

The last 4 times I got a Fread error its been while playing, and the system is running normal temps and all system markers are normal for my computer. I go to drop into a match usually non CW and it crashes on the screen showing which map it is going to be.

Then I have to run the repair tool at least 2 or 3 times for it to actually work for the first time or two it erases files but does not replace them