i'm wondering if i'm crazy, mwll stability.

[BlueT]

Overclocking might work with most stuff, but Crysis and MWLL is not most stuff...

Make sure nothing is running in the background is a sane idea as well as NOT overclocking as has been mentioned.

I have an old AMD 64 X2 HP machine, Win 7 64 Home Pr. 3 gigs of mem,
4850 with fan running at 90%-Yes sounds like an airplane....

But it is totally stable all the time in MWLL....

[BlueT]

Q6600 O.C.'d to 3.6/1600fsb

I bet that overclocking is your problem.
Test it and find out.
I see alot of folks having issues related to this and cannot figure out why they overclock on MWLL or Crysis.
Overclocking might be ok till you run a high end game and there just isn't one like Crysis so far that taxes systems like it does.

[sleepysheep]

Q6600 O.C.'d to 3.6/1600fsb

I bet that overclocking is your problem.
Test it and find out.
I see alot of folks having issues related to this and cannot figure out why they overclock on MWLL or Crysis.
Overclocking might be ok till you run a high end game and there just isn't one like Crysis so far that taxes systems like it does.

There is no problem running Crysis if you have done proper stability tests for long periods of time. Ofc if you get lazy like me and cba to do them long enough then Crysis will slap your CPU to death. And then you learn to do it properly

If your getting BSOD when playing Crysis, then you have some serious problem with your PC that is not related to Crysis at all.

In his case he could of not have a stable OC and thus it's crashing. But the fact is, if the game is just crashing and you get an error box then that is just Crysis being Crysis. If your having to restart your PC becuase of Crysis, it could just be Crysis or hardware/Driver problem.

But lets face it Crysis is a pile of poo when it comes to stabilty, and there isn't alot the devs can do about some of the issues, being they are completly Crysis related. Just wait for it to be transfered to Warhead for almost crash free MWLL

[(TLL)Frosted]

I have a e8500 3.16 ghz overclocked at 3.8ghz and I almost never crash, im also running dx10 because dx9 crash more for me

[HAARP]

CPUs are unique. What works for you might not for others.

[DeadOnAim]

It isn't my overclock guys...lol. I have had this chip running this O.C. all well under STOCK temperatures under the STOCK max voltage for 3 years now. I am not going back to 2.4 for one game and I am certainly not doing it just to play this. Every other new game runs fine, BF2 BC, Bioshock, and many many more. Its not my rig. The only program that hard locks is Crysis with the Mod loaded. I played the whole Crysis SP and MP with no problems like this. It is the Mod.

Again, I am not getting BSOD's. I know how to overclock and I personally lapped the processor and heatsink (Thermaltake Ultra120 Extreme) 3 years ago. It runs under 65 C under full load all four cores maxed when it has been running test programs.

So yeah. Its the Mod.

[xInVicTuSx]

Which is odd because, I'm playing the same mod and getting hardly any crashes at all.
Maybe its the 32 bit? I'm playing on 64-bit DX10, that might be more stable.

[sleepysheep]

Which is odd because, I'm playing the same mod and getting hardly any crashes at all.
Maybe its the 32 bit? I'm playing on 64-bit DX10, that might be more stable.

I am COMPLETLY unable to run dx9. It crashes from 1min-30min from running it. It's 100% unplayable for me. Soon as I load up x64 MWLL, almost zero problems.

I only tried x32 twice, and both times I crashed within an hour. Not that it matters, why wouldn't you play in x64 in a x64 OS? Makes no sence to do otherwise XD


Now you could argue maybe I'm the unluckest person alive, and I can't argue, but for me Dx10, x64, runs soooo much better with almost no crashes. (And if it does crash it normally takes like 4h+).

The game locking up completly is bad though never happened to me ever XD Something other than Crysis might be effecting it. But assuming every single driver and DX is updated, other than running it as x64 in DX10 mode, there isn't much you can do at all.

[Mekabuser=12thVR=]

i had three straight hard crashes last night...
annoooooooooooooooyyyyyyyyiiiiiiiiiiinnnnnng

[The Saint]

My MWLL stability has also decreased dramatically since 0.2.0, both in terms of crashes and connection hangs.

Nothing has changed on my end, so it's pretty puzzling. I'm hoping 0.2.1 will fix it by chance, since I've got no clue what the problem is.

[Yuber]

For me its just SA_Marshes that ctd's every single time. The strange thing is it didnt happen in 0.1 but only after 2/3 weeks of playing 0.2. Nothing changed about my system at all. And havent crashed on other maps even once. Just completely at a loss but i'll patiently await the next version hoping this issue will be resolved.

win 7 64, running in 64bit mwll
6g ram
rad 5870
asus rampage gene 2 mb with soundcard onboard

[~SJ~ Xarg Talasko]

Are you trying to use the novacat 'Mechs often on Marshes? Novacats seem to be causing client crashes, and I'm pretty sure Marshes is less stable this build.

[(TLL)CapperDeluxe]

it must be a case by case thing, I haven't crashed out really at all, couple of times max usually during map switches

[whitedrake 1FSAC]

ya, I can't track it down..   I do think i've crashed on marshes more than others though..  but maybe more often as a ba,  Heck I don't know....