Jump to content

Constant Game Crashing.


4 replies to this topic

#1 lazytopaz

    Member

  • PipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 316 posts
  • LocationPoland

Posted 28 May 2017 - 09:20 AM

Hi there.
Like the subject tells since like last 4 days I'm unable to play more than one match.
At random : either start of the match (where you can see map and map mode screens), during, or right after, or at the beggining of the 2nd match I get a crash.
After that first crash I'm unable to turn the game on (crashes either just after you put in your credentials or when you see mechlab in the background but you still see "loading" in the middle of the screen).

Rule is : after reinstalling fully a game/or re-downloading corrupted PAK files, I am able to play up to MAX 1 game. Sometimes it crashes before the game launches but more or less I'm able to fully play one match. After that game will not work without full fix. That's why I'm keepin copies of "working" MWO to quicker test things around to find a fix. Funnily seems like only MWO only has problems running (after format c: and win10 reinstallation ofc).

Which in the end tells some of my *.PAK files have been corrupted and I have to re-download them through steam or just basically reinstall the whole game.
Because of that Steam also freaked out and told me : nope you have no mechwarrior installed mate even tho there are almost 18 gigs of files with mechwarrior online slapped across it in the steam directory.

Whole gig started when I've ran out of my limited (100 GB per month) internet pool.
Not connected at all. Something wrong with my pc. Tested it out on my gf's ****** laptop and it works fine on hers. So there's something wrong with my rig.

Sidenote : apparently 1 mbps (mega-bits) which is about 0.125 MBps (megabytes) is well enough to play this game. So to any s#it tier internet speed users (such as myself right now) - you're fine.

What I did so far.
Multiple reinstallations of Mechwarrior Online.
Tried it both on SSD (which holds my O/S), and on old but good HDD WD1000GB.

Formatted O/S SSD and did full clean reinstallation of Win10 (previously was win7 upgraded to win10)

Current setup :

BIOS: BIOS Date: 11/09/12 13:17:53 Ver: 36.03
Operating System: Windows 10 Pro N 64-bit (10.0, Build 15063)
Processor: Intel® Core™ i5-3450 CPU @ 3.10GHz (4 CPUs), ~3.1GHz
Memory: 12288MB RAM
Available OS Memory: 12256MB RAM
DirectX Version: DirectX 12
Card name: NVIDIA GeForce GTX 970
Display Memory: 10187 MB
Dedicated Memory: 4059 MB
Shared Memory: 6127 MB

//yup runnin two monitors, dem search times are boring from time to time, so I'll watch some stuff or just do something else on 2nd monitor.

Monitor Name: Generic PnP Monitor
Monitor Model: DELL U2715H
Current Mode: 2560 x 1440 (32 bit) (59Hz)
Output Type: HDMI

Monitor Model: HP LP2475w
Monitor Id: HWP26F7
Native Mode: 1920 x 1200(p) (59.950Hz)
Output Type: DVI



P.S. How can I upload/attach here my dxdiag/mwo dump file ? (just as plain text??)

TL;DR
CryEngine Error
A file appears to be corrupted. Please run the MWO Repair Tool to fix the issue. If issues persist, please contact Support services.

Reinstalling game doesnt help. One game, reinstall, one game, etc.

Edited by lazytopaz, 28 May 2017 - 10:44 AM.


#2 NARC BAIT

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 518 posts
  • Twitch: Link
  • LocationAustralia

Posted 29 May 2017 - 06:16 AM

nothing should make the files corrupt so quickly ... not even a virus should impact the .pak files as quickly ... if a bank of memory is throwing weird results, that could make anything of the complexity of CRC checking be corrupt second time around ... if you upload a log, just add some tags around it, that is, the start and the end, without the spaces, they go '[ spoiler][ code]' and '[ /code][ /spoiler]' to end up looking like this
Spoiler

Edited by NARC BAIT, 29 May 2017 - 06:17 AM.


#3 lazytopaz

    Member

  • PipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 316 posts
  • LocationPoland

Posted 30 May 2017 - 12:48 AM

When I'll get the chance I'll do that. Thanks for reply ;)

But after checking it seems my mobo after almost 6 years of (somewhat bumpy) service it's gasping it's dying breath. Been having bsod's left and right, always a different ones (even after fresh and clean re-installation of win10).

I've took out 2 out of 4 sticks of ram. Didn't help, but went "aw what the hell" and swapped them to (now) empty slots.... and suddenly I can play something from 5 to about 15 games. Although I'm keeping always a copy of MWO on external hdd. Because eventually it still does crash... and corrupts my pak files. Funnily enough it does sometimes screw with the copy of files on the same drive :o.

So that's that.
To my logic it seems that :
MWO picks up PAK files that contain everything is needed to run the game - maps, mechs, decals, cockpit items, animations, etc. Extracts them to RAM, uses whatever it needs and after a game ends packs it back and puts back on SSD/HDD. That's when my mobo screws with those files and corrupts them during "re-packing" and putting them back on my SSD.

I presume that pak files are done to save up some space and organise all of the MWO structure into neat packages instead of catalogs and so on. It probably speeds up loading time as well... but let's be frank SSD's are so cheap and quick these days.

It's not for security reasons because people are extracting anything and everything they want from this game already.

I wish there was a MWO dev/programmer who would be able to convert MWO with PAK to just MWO with extracted PAK's.
It would probably increase game size from 18GB ...dunno the ratio/quality of packaging but let's even say it doubles the size. It still would prevent that big of a data corruption. It would most certainly made it load slower.

Then again system is working for everyone else (and for me, from time to time).

#4 lazytopaz

    Member

  • PipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 316 posts
  • LocationPoland

Posted 30 May 2017 - 02:19 PM

Ok here's one.

Spoiler


No. 2
Spoiler

Edited by lazytopaz, 30 May 2017 - 02:41 PM.


#5 NARC BAIT

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 518 posts
  • Twitch: Link
  • LocationAustralia

Posted 30 May 2017 - 11:24 PM

oh no ... log number 2 reveals the line
FRead did not read expected number of byte from file, only 128 of 0 bytes read
and that's a bug, we used to see, years ago, that I'm not sure ever got tracked down properly ... but it went away for a lot of people ... or those people went away ... some of the people who said they 'fixed' it, ended up finding a problem with their RAM, others ended up swapping antivirus, and seeing the issue, less ... if your antivirus 'marks' the file, adding one bit of data to the end will throw out the CRC/MD5 checksum, whichever its using ...

I'd stay focused on the RAM, essentially, after a file is loaded, and becomes unused, its not specifically unloaded, under the assumption, that you might want to load it again ... and if its unlucky enough to be loaded into a bank that's not running perfectly, the whole thing can die as a result ... for some more in depth troubleshooting, I'd recommend something like https://www.howtogee...m-for-problems/ ... try the inbuilt windows tool first, assuming its present in the N version of windows ...





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users