194 replies to this topic

[Crazie General]

64 bit win 7 no ssd

[Soulgorger]

ltwally, on 02 November 2012 - 08:21 PM, said:

I would like to ask -- and I hope this thread is not an improper place to do so -- why the installer even needs to patch on first install? It would be better for everyone if it instead just downloaded up-to-date versions of all files. (Save the player time and bandwidth, and PGI bandwidth.)

6 of 1, 1/2 dozen of the other. Either way, the amount of info you have to download is going to be very similar.

[Soulgorger]

For those who are having the issue, and who do not have any corrupted .pak files, I have found a solution, but you won't like it.

My issue arrived with the Oct 25th patch. It was a 50/50 change on whether the game would crash with the "FRead" error when the match countdown timer hit "1." I ran the 7-zip checker and had no corrupted files. I then uninstalled the game from my HDD, reinstalled on the SSD, and then was totally unable to play, as the game would blackscreen in the mechlab, in the match, or simply close out without any errors noted.

Suspecting that my SSD was bad, I removed the SSD from the system, and reformatted onto my 2TB Hitachi HDD. After updating Windows with all updates, adding Avast and Spybot back in, and installing Office with all updates, I have yet to be able to replicate the problem or have any issues with game play or mechbay.

I later read online that when SSDs fail, they dont fail like an HDD, where an HDD will "fade away" as more sectors corrupt. An SSD either works or it doesn't, there's no middle ground or fading out.

So, for the adventurous, if you're still having issues and cannot find any .PAK file errors, I would encourage you to do a fresh system build and report back. Then slowly start adding in a program or two at a time and see if/when the FRead error crops back up. Sorry to be the bearer of bad news, but this may be our only recourse and chance to find the issue so it can be resolved.

[Lautschreier]

if this is the solution to that problem then erase my account and go your way!!!

in my PAK-files are NO errors!!!
the game starts and the graphic-quality is bad
the trees are grey,the other mechs are half-transparent and its full of glitches

crysis 2 runs at full quality in FULL-HD on my system

Edited by Niko Snow, 03 November 2012 - 07:08 PM.
Code of Conduct

[Conzar]

I got two corrupted files (objects and gamedata) from a 7zip check. I deleted them, hoping that the patcher would realise they aren't there and re-download, but it doesn't do that (is that really such a big change to do?). Stuck with doing a complete reinstall, which I don't have time to do, so just chipping in here with my machine details.

Intel i7-920, 9GB ram, Win7 (64 bit), Nvidia GeForce 560GTX, and a Corsair Accelerator caching SSD. All Windows Updates completed and Avira (free version) doing anti-virus duties.

[Captain Greene]

Conzar, on 03 November 2012 - 07:54 AM, said:

I got two corrupted files (objects and gamedata) from a 7zip check. I deleted them, hoping that the patcher would realise they aren't there and re-download, but it doesn't do that (is that really such a big change to do?). Stuck with doing a complete reinstall, which I don't have time to do, so just chipping in here with my machine details.

Intel i7-920, 9GB ram, Win7 (64 bit), Nvidia GeForce 560GTX, and a Corsair Accelerator caching SSD. All Windows Updates completed and Avira (free version) doing anti-virus duties.

If you ck this post here:

http://mwomercs.com/...ost__p__1312553

Krist tells you where you can D/L individual Paks.

[Soulgorger]

Conzar, on 03 November 2012 - 07:54 AM, said:

I got two corrupted files (objects and gamedata) from a 7zip check. I deleted them, hoping that the patcher would realise they aren't there and re-download, but it doesn't do that (is that really such a big change to do?). Stuck with doing a complete reinstall, which I don't have time to do, so just chipping in here with my machine details.

Intel i7-920, 9GB ram, Win7 (64 bit), Nvidia GeForce 560GTX, and a Corsair Accelerator caching SSD. All Windows Updates completed and Avira (free version) doing anti-virus duties.

If you read back in the thread, there's a link to the .pak files that you can download separately. There's no need to do a full install. I think it's on page 2.

Additionally, they are working on a repair tool that will check file validity and download only the corrupted files.

*edit*
Green beat me to it.
*endedit*

Edited by Soulgorger, 03 November 2012 - 08:24 AM.

[ltwally]

Soulgorger, on 03 November 2012 - 06:28 AM, said:

6 of 1, 1/2 dozen of the other. Either way, the amount of info you have to download is going to be very similar.

Not necessarily true. Patches do not only add new content. They remove outdated content. How much content (animations, textures, etc) are removed from a patch, and replaced with a newer version? And then again. And again.

This is wasteful of bandwidth.

And it forces an install process that is both considerably longer and considerably more prone to error than simply downloading up-to-date copies the first time.

It just doesn't make much sense.

Perhaps it's on the to-do list.

[ltwally]

Soulgorger, on 03 November 2012 - 06:34 AM, said:

I later read online that when SSDs fail, they dont fail like an HDD, where an HDD will "fade away" as more sectors corrupt. An SSD either works or it doesn't, there's no middle ground or fading out.

Your information is incorrect.

Both traditional Hard Disks and SSDs fail in a wide variety of ways. Sometimes there are S.M.A.R.T errors, sometimes not. Sometimes you have degrading performance/reliability, sometimes not. Sometimes it just up and dies one day.


Certain makes/models/firmwares will have a tendency towards one or the other, but this is by no means a guarantee. There is always a degree of randomness in component failure.

If your data is important, make backups. If it is more important, run RAID (1 / 5 / 6). (Be forewarned - last I knew no RAID controllers supported the SSD TRIM command.)

[Lord Jay]

Here is some more info:

Windows 7 Pro 64 bit.

What happened and what I did:

I had this error and 7-zip found errors in a .pak file.
I uninstalled and reinstalled.
The game played fine.
I set all the .pak files to read only and made a backup copy of all the files.
The game played fine.
Today out of the blue, my system blue screens when trying to drop into a match.
Reboot and try MW:O again and I get the FRead error.
I check my /pak files and sure enough they are corrupted. (Even though they were set to read only.)
So I copy over my backups and launch the game but I get the same error.
I verify my backups with 7-zip and now they are corrupted!

All things being equal I'd say hard drive or disk controller issues, but no other app or game is having these types of issues and all disk integrity checks pass 100%.

[Soulgorger]

Trist;

I thought about this some more in my sleep last night. Amazing how you can wake up with an idea.

The problem is that we're chasing ghosts, and only making guesses as to what it could be. The reason we're doing this lies within the error message itself. The error message is vague, and needs more detail.

Is there a means that PGI can turn on a more detailed "FRead" error message? We need to know what file it's trying to read, and the path that it's trying to read it from. When we have that error message, tracking this bug down will be much easier.

Additionally, I also made the assumption we're all getting this FRead message at the same point in game play. Mine occurred when the match started. The last number I saw was the "1" on the countdown timer, then the game would close and the error box would pop up. Can everyone with this issue concur that's when they saw the error? If not, when are you getting the error?

Maybe Trist can shed some light as to what files are read when the match actually starts. This would be another means as to discover which files are involved that could cause the error.

Just some thought.... Hope it helps.

[ObliviousKnowledge]

Soulgorger, on 04 November 2012 - 07:01 AM, said:

Trist;

I thought about this some more in my sleep last night. Amazing how you can wake up with an idea.

The problem is that we're chasing ghosts, and only making guesses as to what it could be. The reason we're doing this lies within the error message itself. The error message is vague, and needs more detail.

Is there a means that PGI can turn on a more detailed "FRead" error message? We need to know what file it's trying to read, and the path that it's trying to read it from. When we have that error message, tracking this bug down will be much easier.

Additionally, I also made the assumption we're all getting this FRead message at the same point in game play. Mine occurred when the match started. The last number I saw was the "1" on the countdown timer, then the game would close and the error box would pop up. Can everyone with this issue concur that's when they saw the error? If not, when are you getting the error?

Maybe Trist can shed some light as to what files are read when the match actually starts. This would be another means as to discover which files are involved that could cause the error.

Just some thought.... Hope it helps.

If you want to track which files are being read, Then you can use a tool called procmon. It is a windows utility that can record all activity done by a process on the computer. After fixing my fread issue, I have procmon setup to monitor MWOClient.exe whenever I play so I can hopefully provide some kind of info if this happens again.

[ltwally]

It happened again.

This time, the error was in ShaderCache.pak.

The last time I exited the game, the game froze up when I clicked the X (exit button), forcing me to use the Task Manager to kill the game process. (The exact process was MWOClient.exe, I believe)

I downloaded a copy of the file from the URL given above, and it seems to be working again.

System:
Win7 x64
AV: Microsoft Security Essentials
Disk: traditional hard disk (no ssd)

[Alistair Marsden]

As there has been speculation on if the issue was related to a virus scanner, I'm posting this here.

Platform: Windows7/long-mode
Virusscanner: None running, but several installed and deactivated (I'm working in anti-malware research, so using a virus on-demand scanner would kind of defeat the purpose.)
How often does this issue occur: About once every 30 Games. Since the last patch, I've had this issue four times.
How I did "fix" this issue every single time:

• Purge Shader-Cache
  
• Purge appdata/local/temp
  
• Restart windows.
  
• Start the game and have fun.

I've repeatedly tried reinstalling or downloading the Package-Files off the patch-server. However, the PAK files do not seem to cause the issue for me. My guess is that the patcher tried to put something into the its temp-folder (or read it for hashing), and fails at that.

Edited by Alistair Marsden, 04 November 2012 - 10:11 AM.

[Green Duke]

the cryengine-error happens to me at begin of closed beta since beta 2.nd reset an patch i only have senseless game closings while fight without any error the windows shuts down. Another problem jumpjets is a bit smoother but i saw not that many people also me stucked bedore somethings wrong there also i´m not sure maybe there is a memory problem after playing several hours i was havin bad lags just 2 times maybe its something else

[Captain Greene]

Interesting posts.
I continue to be able to play, maybe 30 games so far trouble free with the 4 errors I posted earlier still in place.

[Yaurah]

TY all, I hope I get in...Having multiple issues myself, lots of user, and system editing has only gotten me deeper in the rabbit hole...hopefully some reinstalling, and refreshing settings to origin will prove triumphant...See u in the matrix...

† PEACE †

CSJ

[Kmieciu]

Lord Jay, on 03 November 2012 - 04:37 PM, said:

So I copy over my backups and launch the game but I get the same error.
I verify my backups with 7-zip and now they are corrupted!

So maybe it`s the antivirus that corrupts the pak files?
I`ve got WIN7 x64 & Microsoft Security Essentials

Maybe we should exclude the MWO folder from being scanned by antivirus?

[x Marder x]

I had several corupt pak fiels and tryed to downloud them individual but the http://patcher.mwome...xtures.pak__new
is not louding. Cant find the page error 404

Win7 64bit

I did download the other files and did check them with 7zip and some of the files are corrupt others not. after coping the not corrupted files in the mwo folder some of the file got corrupt others not, that’s so rnd. I loading again the files and checking them until i get some files that are working.


The objects data is causing lots of rnd problems.
first try the atlas what ever was broken now its the centurion body dif.dds.
Is the size of the files causing the problem? the small files are working.


So i did have some luck and I did download a object file that was not broken. I did CTRL+C / V in the MWO directory and BAM after testing it it was corrupt. Delete the file and trey ed a second time ctrl+c/v and now the file is OK. game is working now. something is dmg the files in the copy process in the directory’s where it has to work. it is just a guess. I hope it can help. I did three time loud the game via installer and it was always some corrupted files. now with this manual testing of every file at once and ensuring that all files are OK it works and i can play.

ok now its strange i had one match and now i get the error Fread 32 out of 0 not the 128.

Ok now i have the 128 error again.

The game was loading a map 32 error and after i restarted the game i got the 128 error.
The mechanic_body.chr is broken.

I was checking with 7zip my other pak files. I have errors in causticvalley lvl.pak and desert lvl.pak.
Where i can downloud this files?

Edited by x Marder x, 05 November 2012 - 08:40 AM.

[Krist Smith]

Any __new files are leftovers from patcher failures, so you can safely delete those. As for the level paks, here's the URLs:

Desert - http://patcher.mwome...esert/level.pak
Caustic - http://patcher.mwome...alley/level.pak