This is a first for me. After the last 2 betas I'm having CTDs randomly. There's no error message, except the windows "ArmA 2 isn't working" error. The crash seems to happen randomly but it also seems to happen after the debriefing upon mission completion and I just had it crash when opening the editor after selecting the island I want to use.(First time that happened)

I haven't CTDs in years but now they seem to be popping up a lot since the most recent betas. It happens when I'm using ACE2 and when I just try vanilla A2CO, so I don't think it has anything to do with mods. I'm pretty sure it's a video problem.

Here's my system:

i7 2.93Ghz
Win 7 64
4Gb Ram
ATI 5870 1Gb

And here's what I get in my .rpt:

Code:
Exception code: C0000005 ACCESS_VIOLATION at 00677FCC
graphics:  D3D9, Device: ATI Radeon HD 5700 Series, Driver:aticfx32.dll 8.17.10.1083
resolution:  1995x1255x32
Version 1.59.82128
Fault address:  00677FCC 01:00276FCC C:\Program Files\Bohemia Interactive\ArmA 2\Expansion\beta\arma2oa.exe
file:     @Mission_4
world:    Zargabad
Prev. code bytes: D2 34 8B 80 54 02 00 00 8B 54 1A 14 6B C0 48 41
Fault code bytes: C6 44 02 01 00 3B 4E 1C 7C CB 8D 4E 18 E8 DA 98

Registers:
EAX:FFFFFFB8 EBX:1D602A00
ECX:000000A5 EDX:55570000
ESI:29128730 EDI:00000000
CS:EIP:0023:00677FCC
SS:ESP:002B:0184EE4C  EBP:0184EE5C
DS:002B  ES:002B  FS:0053  GS:002B
Flags:00010206
=======================================================
note: Minidump has been generated into the file C:\Users\Dan\AppData\Local\ArmA 2 OA\arma2oa.mdmp
I'm pretty sure it has to do with the recent betas cause I've never had an ounce of trouble playing the game on pretty much full settings. I've even toned down the setting but it still crashes.

Am I right in thinking this is caused by the betas or is there something else I can try? I have all the recent drivers too.

---------- Post added at 08:40 AM ---------- Previous post was at 07:56 AM ----------

Nevermind. It seems it's being addressed in the newest beta.