Harmonica

edit: for those with my problem below: https://dev-heaven.net/issues/37100 This works! Can play on 1.6 servers. I suggest renaming that file to .old, though... -------- I have the same problem, except it is the BeClient.dll that is causing the crash. Am using the latest beta 95208 for DayZ, core OA is 1.6 Steam version, running combined ops, game crashes with this error after joining a game of Warfare and picking sides, loading in. I'm not using any mods right now just trying to get into any Warfare game. Have tried replacing the BE files but it still crashes. Have tried creating a BattlEye folder in the main OA directory, still crashes. As far as I was aware, the beta patch does not overwrite the core game files, is this true or not? (It's not an RC).

Thanks, that's really useful actually because I have a few friends still on older drivers and I'll have them use that registry edit.

Thanks for the reply. I was using the drivers because my performance was good with them. Actually, in the days just before I posted nvidia released some new drivers which have probably fixed the problem (no crashes with them since installing) but I hadn't got around to updating. There was nothing wrong with my particular system, unfortunately this problem affects anyone with a recent GeForce card and any drivers from last year through February this year. Specifically, it's an issue with Windows 7 and how it monitors the GPU, when the card powers down for power saving, sometimes W7 thinks the card drivers have crashed, and reboots them (known as a 'TDR' problem). I guess the process is similar when using Six Updater (card powers up and down a lot when switching views/idling). Might be important for you to know for future reference! Also, a fix would be to allow software rendering.

Does the latest pre 2.9.5019 do anything different with the display/display drivers? I'm using nvidia drivers from october, which have a problem with (pretty much only) Firefox when it runs in hardware acceleration mode, because the GPU is constantly powered up and down and Windows thinks the driver has crashed, and reboots it. It seems that the latest version of Six Updater somehow does a similar thing with hardware acceleration, and within moments of auto-updating it crashed my drivers (a problem I hadn't seen since it was only related to Firefox). Is there a way I can roll back to the latest stable? Any information about this, and if anyone has experienced similar, would be great. I've only just started using Six Updater again in the past few weeks but hadn't had any crashes with it.