- User Since
- Feb 20 2015, 4:06 AM (431 w, 4 d)
May 11 2016
Hmm. Plausible. Not sure why it's affecting only a small group of people, though.
-edit- Deleting the BattleEye client and reacquiring it through verifying cache didn't do anything for me.
This has also been happening to me. Here is the extent of what I tried to get it to launch properly (with no success):
-Updated AMD video drivers
-Added the nosplash and skipintro start params to Steam
-Checked integrity of RAM - it was good.
-Uninstalled video drivers and re-installed
-Ran Dayz from program filesx86/steam/steamapps/common directly
-Ran DayZ as admin
-Opted into unstable and back (Got a different but similar error message when I did this, didn't write it down though)
-Verified integrity of game cache through Steam
-Ran all DayZ files and executable as admin simultaneously
-closed all additional programs
-Deleted the game off Steam as well as all remaining files in the directory.
-Deleted all older versions of AMD video drivers
-Slightly upped GPU and CPU speeds through BIOS
-Deleted and re-installed chipset drivers
Using windows 7 w/ 2gb AMD card, i7 3.6ghz cpu, 16gb RAM