Arma2 freezes on my new Phenom....plz help

[flv*venom* 83]

Hello people, I need help (and sorry for the long story).

A month ago I bought a new Mainboard, a new CPU and some Ram to be finally able to play Arma more or less lagfree.

The Mainboard is a "Gigabyte 790FXTA-UD5"

The CPU is a "AMD Phenom II X4 965"

and the RAM is two sticks of "Corsair xms3"<-a total of 4GB

(all other components which I still use have proven to be reliable and stable in the past)

now to my problem: from minute one of this system I had constant hangups freezes...you name it. So I sent the cpu and board back to have them checked(same with the Ram, which I bought someplace else) ...a few days ago I got them back with a note saying that everything is working perfectly, same goes for the RAM. But the moment I installed the system the problems surfaced again. Now I found out that the RAM does seem to be the problem, because after removing one stick everything is working, except for Arma2. I can play smaller missions like the "Trial by fire" or "counterattack" just fine with very nice fps. but everything else crashes the game after max. 5 minutes and if there's a "warfare" going on like "bear rising" or "war welcome" it often takes even less time to crash. has anybody an idea what's going on, because I'm beginning to give up hope of beeing able to play Arma on this rig.:(

[nikiforos 450]

What kind of GPU do you have?

I have similar system and GTX 275 and I dont experience any crashes except sometimes in Multiplayer when i get the message the game has stopped to run.

[wheres my rabbit ? 10]

what speed is your ram ?

[flv*venom* 83]

Hi there!

@Nikiforos: Well, I have a Geforce 9600GT with 512MB (PCIe), which was perfectly able to run Arma2 before.

@wheres my rabbit?: My RAM runs at 1333mhz

I forgott to mention that I'm using the onboard soundchip. (however, on my old rig I did this aswell with no problems)

furthermore, I am using WinXP SP3.

HMMMMMMMMM. I just had a look at the "arma2.rpt" and it keeps mentioning:

"Error: cannot load sound 'ca\dubbing\global\radio\male05\en\engagingtargete.wss', header cannot be loaded."

and

"Warning: no type entry inside class CampCaptureProgress/controlsBackground/InfoLabel "

among tons of other things, but right now I'm only using vanilla stuff.

is it possible that the 105 update went fubar?

Edited June 11, 2010 by FLv*VeNoM*
found something?

[TechnoTerrorist303 10]

@Nikiforos: Well, I have a Geforce 9600GT with 512MB (PCIe), which was perfectly able to run Arma2 before.

Although this isn't going to cause the problem you describe, I would suggest getting a better gfx card soon.

Make sure you have the right chipset drivers installed for your mainboard, if this isn't the problem then it is quite possible something screwed up during the patch installation. Reinstall Arma2 and try again.

Just so we're clear, you did reformat your hard drive and reinstall Windows after putting this new hardware in your machine right?

[flv*venom* 83]

Just so we're clear, you did reformat your hard drive and reinstall Windows after putting this new hardware in your machine right?

Yep, I did. learned that lesson the first time I tried to run the new system. In fact it I bought a completly new hard drive last tuesday :). @new gfx card: yeah that's on my to do list for next month, because my budget is allready stretched thin this month.

I just reverted back to my old system after experiencing a 'freezing' while typing a reply here in the forums. And when 'de assambling' the phenom to my shock I noticed that it was literally glued to the fan which was supposed to keep it cool. I don't get it, since it was a pretty freakin' huge and powerfull fan. it would explain the problems in Arma, but why would it stop working while 'only' beeing in windows then?

never the less, thanks for all support and helpfull suggestions from you. I'll give the rig a new try next month.

[TechnoTerrorist303 10]

Hang on, what? The chip should be "glued" to the heatsink using thermal grease, unless you're talking about the fan blades themselves which would certainly be odd. As for "just" being in windows, something could have happened in the background and caused the cpu usage to climb and then you would experience problems. Be very careful if you have "disassembeled" the assembly of chip and cooler, you may need to replace the thermal compound completely before running it again.