5 replies to this topic

[CallMeGunny]

I'm a little pressed on time, so I'm literally copying and pasting a message I sent to support which includes a small paragraph detailing how I fixed my (very) regular crashes (game freezes, does not recover), as well as why I believe the crashes were occurring and the fix worked. Sorry but I simply do not have the time to retype this in the proper format and so a copy and paste will have to do. Hope it helps anyone who was having the same issues I had:

Sending you my omichron logs of several week's usage.

As well a note about memory related crashes I've noticed with my system (as I have been able to 'fix' my CPU hang-based crashes entirely:

My specific computer has 8GB of RAM. HOWEVER, it has 2 different TYPES, 4GB of my RAM is "CORSAIR VENGEANCE" and 4GB of my RAM is "CORSAIR XMS3":

While similar enough to work, the game ALWAYS crashes when my total system memory usage exceeds 4GB. Windows Task Manager reflects 0-2% CPu usage and memory usage (in mwo proccess) increasing by a constant 200KB per second (roughly, counted by visual only.)

This may be due to the game attempting to write to memory on one set of DIMMs, and a problem arising with it attempting to write onto a different type of DIMM.

So far, I have not had issues with my computer exceeding 4GB memory usage in other applications, so I figured I'd mention this.

As for my solution: I lowered my "Texture Detail" to "medium" and now my total system memory usage never exceeds 3.10GB usage at any given time: And since changing this I have not crashed ONCE, zero exceptions.

Edited by CallMeGunny, 15 April 2013 - 05:10 AM.

[xenoglyph]

You should use some stress test tools to test your system to find out for sure. First step should be Prime95 -> Options -> Torture test -> Blend.

Bootable Memtest CD is also very good, you can run that overnight. If both those pass then your RAM is not the issue.

Prime95 does a mostly OK job of testing CPUs (Options -> Torture test -> In-place large FFTs), but my real CPU test is now using x264 for a full HD transcode of a movie. If there's even a hint of CPU instability x264 -will- crash, where other tools won't have a problem.

[CallMeGunny]

xenoglyph, on 15 April 2013 - 08:28 AM, said:

You should use some stress test tools to test your system to find out for sure.  First step should be Prime95 -> Options -> Torture test -> Blend.

My computer is heavily overclocked: these tests have been run probably several hundred times over it's life. Anytime there was an issue, it was fixed and test were run again until it was confirmed fine.

Edited by CallMeGunny, 15 April 2013 - 05:14 PM.

[xenoglyph]

Mine's heavily OCed as well (water cooled with 32gb of RAM... I know a thing or two), and I passed every test I could throw at it until I tried transcoding with x264. It took me a while to figure out that good advice on my own, I'd give a shot.

If MWO crashes because of your RAM, then other things will crash too. I recommend isolating and repairing the root of your hardware fault. Right now, I'd say you have 3 possible culprits: unstable CPU OC, unstable RAM (do you OC or mess with timings?) or unstable GPU OC.

'Fixing' this crash by artificially limiting MWO's RAM usage isn't a proper fix at all. If you really think it is your RAM, try giving it a bit more voltage, or loosening the timings a bit, or both.

[Tarl Cabot]

Without more details on the ram, just reviewing Corsair website, they run at different voltages.

XMS3 1600MHz, 9-9-9-24, 1.65V
Vengeance 1600MHz, 9-9-9-24, 1.5V (voltage set to be compatible with Sandy core 2nd generation.

That would help explain some of the issues.

You could try switching/trading memory slots, reversing which one is closest to the CPU to see if it would offer some stability.

What OS are you running also?

Edited by Tarl Cabot, 15 April 2013 - 07:11 PM.

[zinetwin]

Just out of curiosity, you are running an x64 os right? For the most part 32bit windows only supports 4GB of ram and if you add more it can do wierd things.
I just checked and the mwoclient executable does have the largeaddressaware flag set meaning it does support more than 2GB of memory usage which is good. I don't know if the game is truly x64, you would think it is since it's crytek 3.
On the hardware side, did you do any tweaking to the FSB or HT in your overclocking? If you do you may need to change the ram multipliers on the gpu for added stability, I forget exactly what the term for it is but it's basically a signaling issue between the pcie layer and the northbridge on intel chips or the HT system on AMD's. Sort of like a network collision.

The recommended testing approach would be to undo the overclock and run everything at stock to see how it performs before going crazy.

Or you could grab a benchmark like heaven or 3dmark and let them go to town.