AmberHelios

try starting steam as admin by right clicking on steam and run as administrator and run both games up to the menus if any error messages come up take a screen shot or write the whole thing down we can help you better

http://www.arma2.com/beta-patch.php

http://opendayz.net/index.php?threads/dayz-debug-monitor.8256/

well fraggles hang around the tech support section long enough and you pick things up :)... ive seen you giving people correct advice on technical issues before..... well i think it was you. :D

delete the folder and redownload

seems to be an issue on some private hives running 1.7.6 if it happens over and over on the same server the only thing you can do it try another

it dont matter the program you use it still reads the variable from the dts and then applies a formula to work out said temperature for amd i believe its value / 8 and intel its tjunction - value i was saying its unreliable to read dont matter what program is you use to read it put it this way in one of my pcs i have dual radeon 6870's each one says its running at 60 in the amd software 58 in cpuid hw mon 59 in speedfan and 54 on my nzxt fan controler with the temp probe between the heatsink and the chip plus that to the fact that older hardware cannot run as hot as newer stuff and that each component cant run at the same temp threshold even if they are the same components ei just to say that one old x6 can run at 80 happily doesn't mean another x6 can

frags is right... temp programs are only as good as the probes on the mobo on cheap ones they can be 10 degrees out either way plus that with systems being old dont help . colour change when playing games usually indicate gpu issues. could be helpful if you posted you specs as well as what case you stuffed your new gpu and psu into

check the arma 2 files not oa if your on steam validate the files if not reinstall and then update to the latest versions

revalidate the files sometimes steam likes to play about and delete the exe for games its done it a fair few times before. start steam as admin validate both arma2 and arma2 oa and then start both games up to the menus and then you can start dayz

how is this troubleshooting get a mod to move you... you may have better luck

remove the merged files mate, when you uninstall the game delete the whole folder then reinstall

clean your pc of crap and retry to gain control over it. and then follow these steps close steam start steam in admin (right click and run as administrator) right click on arma2 and properties then local files click on verify integrity of game cache <-- do it twice and do the same for arma2 oa run arma2 to the menu run arma2 oa to the menu click in expansions make sure the following are enabled arma2 arma2 oa arma2 baf lite arma2 pmc lite if not enable them and restart then exit the game

glad your sorted mate

you hav 4 4870 must get a little hot :)

the sa58 is no longer banned its a normal spawn now. update to the latest filters on your server.

have you updated arma2 to version 1.11 and arma2 oa to version 1.62 before installing the patch from dayzcommander

there is a new update for commander now try that one

what skin have you got on

you need to update arma2 to version 1.11 and arma2 oa to version 1.62 and then install the beta patches this error also comes on with the beta patch when using steam as well as lingor island i get it when launching dayz from steam and i dont even have any lingor installed running beta patch 101480 but if i go back a couple of patches it dont come up. it doesnt stop you playing the game tho

it should be just under arma2 make sure you launch the game with steam started as admin so it puts the information about path location and cd keys into your registry

yeah you will but you need to drop the ammo too thats one of the other ones your getting kicked for

try checking your firewall

do you have the soldier skin and an sa61 they are still banned in the old scripts file the admin needs to update to the new versions those two items are at them lines on the old publicvariableval.txt

delete the files from your appdata folder in users see if that helps