BattlEye causing DayZ to ping 1000 ms+ in lobby = crash

[snarkmus 0]

Hi,

I've been scanning and scouring the internet for 5 days now for all possible fixes, been in contact with the BE support but still cannot get DayZ to run without getting absolutely insane lags. The problem beings in the lobby when running either through Steam or DayZ Commander. It started out with the BattlEye corrupted Data #5 but that eventually went away for some odd reason. I've also that the memory error from time to time, not sure why. And yes, I'm running DayZ and Arma on the absolute lowest settings of everything.

Here's just a few things I've tried:

- Replace files

- Manually installing BE, downloading new BE files and replacing them in every possible folder

- Window moding it

- Reinstallation of Arma2;Arma2OA and Steam all itself

- Changing 'Run as admin'

- Deleting Local App Data for Arma2OA and letting BE initialize and update itself

- Beta patching

- Disabled all Firewalls possible (don't even have a Anti-virus installed and disabled Windows firewall aswell)

- Updating firmware on router and even bypassing it

- Changing the order for expansions (couldn't do it at one point - wouldn't let me or just gave me a random error)

- Nothing found in the .RPT file that points me towards an error

I've noticed more people have the same problem and everything points to it being BE causing it. When running DayZ on a server that is BE disabled - everything works fine. When deleting the Local App Data file for BE, running it a older version, everything works fine - until it updates itself to v.1.195 and the lag begins.

Thanks for reading and if you have any new solutions that isn't listed above - help is greatly appreciated. I might have forgotten something I've tried in the list above.

Best regards,

snarkmus

[nik21 287]

What software is running in the background? Did check your memory for errors (memtest86)?

Edited May 9, 2013 by Nik21

[snarkmus 0]

I've basically turned off everything that isn't absolutely required to run. No, I haven't checked any memory for errors - I don't see how this could be a RAM related issue though. I've uninstalled quite a few programs these last days aswell in a trial-and-error fury but nothing seemed to work.

[nik21 287]

I've also that the memory error from time to time, not sure why.

Which memory error exactly? That COULD be related to your memory.

edit: What's your internet connection speed?

Edited May 9, 2013 by Nik21

[snarkmus 0]

I'm pretty sure it was the one posted in a thread just below this one - something like Error: The instruction at '0x00000000000' referenced memory at "0x0000000000". The memory could not be written.

Running a 100/100 MBIT. Just ran a speed test at speedtest.net; 89 down, 75 up atm.

[snarkmus 0]

I guess I should also mention I'm running Windows 8 Bootcamp from my MacBook Pro Retina and using a external screen. I did unplug as I know it's more heavy on the RAM when using a external monitor - no change.

Edit: checked my RAM usage when launching DayZ. I've got 8 GB RAM and it's only using up about 50% of it.

Edited May 9, 2013 by snarkmus

[nik21 287]

I'm pretty sure it was the one posted in a thread just below this one - something like Error: The instruction at '0x00000000000' referenced memory at "0x0000000000". The memory could not be written.

This error is caused by GameTracker Lite Client.

[snarkmus 0]

I'm not even using GameTracker Lite Client. I believe that's the client used when running DayZ through Steam and Arma 2 OA, right? I always use DayZ commander when launching and have been doing so far the past months. The only reasonable explanation is that BE bugs it out. Guess I'll have to wait for a fix for it.

Edit: Just played about 2-3 hours on a BE disabled server - no problem with RAM, crashes, lag or anything.

Edited May 9, 2013 by snarkmus