menos

I run ArmA II since a few days on: early 2008 MacBook Pro 15" 2.5GHz Core 2 Duo NVIDIA GeForce 8600M GT 512MB 6GB DDR2 SDRAM 667MHz Windows XP Pro SP2 via Bootcamp installation Bootcamp 3.1 drivers (includes graphics driver) 1280x800 1200m normal textures default graphics card settings AA off shadows disabled post processing disabled object and landscape detail lowest settings latest ArmA II OA update I run it rather fluently @ about 25 fps in single player missions. I did not try player yet - lack of speedy servers here in China. I am not satisfied with the performance. ArmA ran very nice on this machine, as do other games.

I meet the optimum system specs, printed on the DVD, I bought and even exceed them in some points. I cannot get ArmA to play fluidly. I tried settings as the lowest possible and could play ArmA only on this setting. Unfortunately, there are no visible textures in this setting and graphics smear into a unrecognisable coloured screen. Even the mouse pointer in the menu is erratic. I can play other contemporary games on this computer with native resolution and high settings without any issues, Fallout 3, Crysis, FarCryII, STALKER, ..., to name a few. ArmA (original game) does run ok too. I feel a bit lost here - are there any users of a Macbook Pro, who are able, to run this game as advertised?

I made a fresh install of ArmA 1.08 and 1.14 patch on this machine: Macbook Pro Penryn 2.53 GHz nvidia 8600M 512MB 6 GB 667 RAM WinXP Pro 32bit The game runs extremely bad (always under 20 frames). setting all settings to the lowest options helps for a smoother experience, but this is not acceptable though. I run on the same Macbook Pro new games like Fallout 3 or Farcry 2 at native resolution (1440x900) in high res textures and very playable fps (above 40 frames). Whats wrong with my settings? I remember, ArmA being a hardware hog. What do other Mac user experience in setting up the machine for ArmA? Settings in game? Settings in the driver panel?

How does it fare on the MBP? I am just downloading it on a slow connection and plan, to use it on my 2.53 Penryn. I remember, that it ran very stuttering on my old Pentium D 2 years ago.

Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 18.08.2007 Time: 22:02:22 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module , version 0.0.0.0, fault address 0x00000000. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 61 72 6d ure arm 0018: 61 2e 65 78 65 20 31 2e a.exe 1. 0020: 38 2e 30 2e 35 31 36 33 8.0.5163 0028: 20 69 6e 20 20 30 2e 30 in 0.0 0030: 2e 30 2e 30 20 61 74 20 .0.0 at 0038: 6f 66 66 73 65 74 20 30 offset 0 0040: 30 30 30 30 30 30 30 0d 0000000. 0048: 0a . application suddenly freezed and it was impossible to change the freezed picture on the applications screen. The 2nd screen showed reaction, as i could normally move the mouse, click the desktop, . . . A few seconds later, with some tries in getting the PC to a reboot or any other reaction than the frozen main screen the pc went down with an BSOD.

I design automotive parts and tools for a living and there are hot times when customers are really eager i do work for 10 to 14 hours/ to get the job done without the most lovely device I had on one of my old workstations I used: A spacemouse - in concept quite similar to the device you show us. Once you get used to it you do not longer touch the keyboard - the mouse controls the functions (in ArmA would be the aiming) and the spacemouse controls the movement of the CAD part one moves on the screens (in ArmA you could map the movement to it). The spacemouse has one further very impressive feature, which could improve ArmA in such an revolutionary way, as TrackIR: The space mouse is an analog device with a very high precision without any jerkyness. Imagine a fluid movement of the character from slowly walking to a faster move, to running and even sprinting with this analog device without any dumb digital additional buttons for slow, fast, and sprint. Even the vertical movement could be done, as the spacemouse is really an device with full freedom, similar to trackIR. The real difference between the mediocre keyboard and an analog movement device is as similar as the evolution from an didital controlpad to an modern 900° FFB wheel for racing sims.

update: Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 18.08.2007 Time: 17:10:37 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x004043bc. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 34 30 34 33  t 004043 0050: 62 63 0d 0a        bc..   @ rowdied: Thanks for the input. Is your ArmA running now ? those ideas of yours replicates the bad feeling I had in my stomach when I found this forum shortly after the purchase of the software and the first troubles. The feeling implicated that there is no solution in particular for specific errors at all but stick poking and guesstimating all over the place - and eventually finding a smoothly running application by luck. Not the way I am used to solve problems unfortunately. I overclock the CPU from 2.66GHz per core to 3.12GHz, wich approved to be stable without any problems here (running this computer 24/7. No problems can be detected while running benchmarks and tools like Memtest or Prime. The Graphicscard as the RAM is all on stock, so do the busspeeds. All temperatures and V readouts show no critical values (CPU while hard at work for several hours 52°C). I would like to have factbased information about what effects overclocking a CPU has in particular. The more scientific and detailed the better. I get a better understanding of things, when they are not presented in an picturized and downscaled way. Any links to such topics? @ Kubicide: Well monitoring the used physical and virtual memory size and pagefileusage were things I didi in the very beginning of the problems, resulting in not finding any hints of a problem. I will follow this path after the testing I do at the moment. I started to test different video drivers from the 9x.xx to the newest 162.50 Quadro drivers. I have found out that the following method is the most stable I could achieve: 1) 162.18 FW WHQL (clean driver install as known) 2) Reboot as wanted after installation finish 3) Cancellation of the monitor wizard after reboot (still in low res mode) 4) resetting the resolution of both monitors and activation of the extended desktop via right click on desktop\ properties\settings menu 5) not touching the Nvidia menus under no circumstances 6) running ArmA I will further test how long ArmA will be stable under this given circumstances. Further work is the data logging regarding memory. It would be a great help, to have detailed information about the event logs I provided in the post. Clear information on causes would make Troubleshooting a lot easier. Are there any devs or insiders available to translate those faults? end of post. Forgive me for my slightly offensive/ sarcastic voice in the first place. I have calmed down and am back at normal efficiency to "work" on the issues I have with the combination of ArmA and this particular computer. to be continued, menos

Some of the things, I did in 6 weeks: experimented with pagefile sizes and did disable it too - no change in stability nor performance here. As WinXP is patched and fixed to the newest possible updates (I use Autoupdater, as it gives the most flexibility during install), I have tested the latest 3 versions of DX9c with ArmA. Now i have the August version and will leave it on the machine. Btw, Framework is updated along with all other MS updates aswell. Mobo and other hardwaredrivers are up to dae aswell. This PC has been build about 3 month ago and proofed absolutely rockstable without any clue of a problem with several demanding applications and torture programs. (Thats the reason, why this ArmA problem really buggers me) I suppose OGL is not used with the ArmA engine. I am quite aware of the troubleshooting thread and the guides and hints, the developers give on this forum. i have tested a lot of them and as there is such a great variety of things, that can potentially mess up ArmA, I see no way of getting rid of the CTDs without a Dev looking over some specific failure  footprints (Thats why I ll  keep this thread going as long, as the problem remains and a solution is found for users with such problems.) Any more ideas? Just a hint (I will definitely not go into detail, as this maxmem topic spreads the whole board - with a lot of speculation and trial and error methods too): I doo have 2 GB DDRII and ArmA makes use of aprox. 900MB, without using maxmem (look at the peakmemory usage in the taskmanager, while ArmA runs). Using maxmem to indicate the application that Allocation of an higher ammount of RAM is possible (maxmem > 1000), ArmA will use more of it. With maxmem=1280, the application uses about 1100 peak memory. As i stated before - there is no indication of any change in stability or performance of ArmA when using maxmem or several pagefile layouts. Dont shoot at the maxmem switch as an universal key for a better running ArmA - actually its a way to prevent an software to allocate bigger amounts of data to system memory than there is contiguous system memory available leading to an unable to allocote address xxxxxx stop of the software resulting in crashing. Somehow it seems to work as an helper of allocating more memory with it than without the switch on machines that are capable. There are several fine articles about WinXP memory management on the net (dealing with pagefile, RAM, software memory allocation, 32bit and 64 bit OSes, ...) Google Contiguous memory, memory management under WinXP, 4GB RAM limitation, 3GB boot.ini switch, ... http://www.dfanning.com/fileio_tips/lgfiles.html http://www.ittvis.com/services/techtip.asp?ttid=3346 Good night, menos

Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 16.08.2007 Time: 22:01:01 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module d3d9.dll, version 5.3.2600.2180, fault address 0x00041b3e. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 61 72 6d ure arm 0018: 61 2e 65 78 65 20 31 2e a.exe 1. 0020: 38 2e 30 2e 35 31 36 33 8.0.5163 0028: 20 69 6e 20 64 33 64 39 in d3d9 0030: 2e 64 6c 6c 20 35 2e 33 .dll 5.3 0038: 2e 32 36 30 30 2e 32 31 .2600.21 0040: 38 30 20 61 74 20 6f 66 80 at of 0048: 66 73 65 74 20 30 30 30 fset 000 0050: 34 31 62 33 65 0d 0a 41b3e..

Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 16.08.2007 Time: 00:26:08 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module d3d9.dll, version 5.3.2600.2180, fault address 0x00041b3e. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 61 72 6d ure arm 0018: 61 2e 65 78 65 20 31 2e a.exe 1. 0020: 38 2e 30 2e 35 31 36 33 8.0.5163 0028: 20 69 6e 20 64 33 64 39 in d3d9 0030: 2e 64 6c 6c 20 35 2e 33 .dll 5.3 0038: 2e 32 36 30 30 2e 32 31 .2600.21 0040: 38 30 20 61 74 20 6f 66 80 at of 0048: 66 73 65 74 20 30 30 30 fset 000 0050: 34 31 62 33 65 0d 0a 41b3e.. Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 15.08.2007 Time: 20:54:24 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module d3d9.dll, version 5.3.2600.2180, fault address 0x00041b3e. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 64 33 64 39   in d3d9 0030: 2e 64 6c 6c 20 35 2e 33  .dll 5.3 0038: 2e 32 36 30 30 2e 32 31  .2600.21 0040: 38 30 20 61 74 20 6f 66  80 at of 0048: 66 73 65 74 20 30 30 30  fset 000 0050: 34 31 62 33 65 0d 0a    41b3e.. Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 14.08.2007 Time: 21:15:59 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module d3d9.dll, version 5.3.2600.2180, fault address 0x00041b3e. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 64 33 64 39   in d3d9 0030: 2e 64 6c 6c 20 35 2e 33  .dll 5.3 0038: 2e 32 36 30 30 2e 32 31  .2600.21 0040: 38 30 20 61 74 20 6f 66  80 at of 0048: 66 73 65 74 20 30 30 30  fset 000 0050: 34 31 62 33 65 0d 0a    41b3e.. Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 14.08.2007 Time: 04:37:38 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0027a6a0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 32 37 61 36  t 0027a6 0050: 61 30 0d 0a        a0..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 14.08.2007 Time: 03:54:25 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x004043bc. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 34 30 34 33  t 004043 0050: 62 63 0d 0a        bc..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 14.08.2007 Time: 03:26:42 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module , version 0.0.0.0, fault address 0x00000000. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 20 30 2e 30   in  0.0 0030: 2e 30 2e 30 20 61 74 20  .0.0 at 0038: 6f 66 66 73 65 74 20 30  offset 0 0040: 30 30 30 30 30 30 30 0d  0000000. 0048: 0a             .    Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 12.08.2007 Time: 14:37:39 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0041b3d2. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 34 31 62 33  t 0041b3 0050: 64 32 0d 0a        d2..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 06.08.2007 Time: 20:26:27 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x00452acc. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 34 35 32 61  t 00452a 0050: 63 63 0d 0a        cc..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 06.08.2007 Time: 02:53:36 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x001e8560. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 31 65 38 35  t 001e85 0050: 36 30 0d 0a        60..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 06.08.2007 Time: 02:38:06 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0003b3c1. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 30 33 62 33  t 0003b3 0050: 63 31 0d 0a        c1..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 06.08.2007 Time: 01:56:42 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0003b3c1. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 30 33 62 33  t 0003b3 0050: 63 31 0d 0a        c1..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 06.08.2007 Time: 01:13:54 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0003b3c1. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 30 33 62 33  t 0003b3 0050: 63 31 0d 0a        c1..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 05.08.2007 Time: 16:47:01 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x003fd67b. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 33 66 64 36  t 003fd6 0050: 37 62 0d 0a        7b..   Event Type: Error Event Source: Application Error Event Category: None Event ID: 1000 Date: 05.08.2007 Time: 16:18:52 User: N/A Computer: WORKSTATION Description: Faulting application arma.exe, version 1.8.0.5163, faulting module arma.exe, version 1.8.0.5163, fault address 0x0003b115. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 41 70 70 6c 69 63 61 74  Applicat 0008: 69 6f 6e 20 46 61 69 6c  ion Fail 0010: 75 72 65 20 20 61 72 6d  ure  arm 0018: 61 2e 65 78 65 20 31 2e  a.exe 1. 0020: 38 2e 30 2e 35 31 36 33  8.0.5163 0028: 20 69 6e 20 61 72 6d 61   in arma 0030: 2e 65 78 65 20 31 2e 38  .exe 1.8 0038: 2e 30 2e 35 31 36 33 20  .0.5163 0040: 61 74 20 6f 66 66 73 65  at offse 0048: 74 20 30 30 30 33 62 31  t 0003b1 0050: 31 35 0d 0a        15..   I am struggling for about 6 weeks now to find a gaming experience with ArmA - a gaming experience which should at least endure for a bigger amount of time than 10 minutes. An experience that probably had the potential of actually enjoying an application instead of enduring serious trouble. As I am kind of tired of the whole troubleshooting - thing just to get a computer game running at the quality advertized at the time of purchase, I list A FEW of the latest funny events with ArmA. Possibly some other masochistic user has had experienced similarities with his/her accidentally purchased software and is able to advice a possible solution. The system specs: Asrock CoreDual VSTA, latest bios 2.00 Pentium D805 MDT DDRII 667 2x1GB Gainward GF 7800GS GLH 512MB (G71, 20/7) Windows XP Pro SP2, patched, hotfixed to 07/2007 Every hint towards a solution is welcome, menos PS: The latest quite funny fashion, the software mentioned above is performing, is an apruptly freeze of the application leading to a total crash of the computer. I dont get the nice little shiny ArmA "we are sorry for the inconvenience" buttons any more. Looks finally I have managed to get promoted and have reached the next level in computer crashing science. The funniest, and almost unknown to me, crash button was like "If you have something going on here, you might loose your data" - I had a good laugh, seeing this kind of new variety (I did laugh - really !.

I experience random CTDs too. I installed ArmA when the 1.08 patch was already out and patched directly to the latest version. Since the beginning I had CTDs with ArmA - and with ArmA only. I have experienced no problems whatsoever with any other application on this machine. Other games that were/ are installed and running fine are Quake 4, GTR2, netKar Pro, Falcon 4 AF, gunship!, and several OpenGL CAx software. I use WinXP Pro SP2 patched and fixed to 07/2007 , latest drivers and Bios versions for all installed components. Intel Pentium D805 @ 3.2 GHz, 2GB MDT DDRII 667 (2 x 1GB) Asrock coredual-VSTA mainboard Gainward GF 7800GS Bliss 512MB (G71 20/7) 500/700 MHz I have done anything, I could imagine and anything, this and other boards and websites propose to troubleshoot the annoying instability of ArmA. Everytime, you get the feeling, a new tweak could have some effect (you get some hope after about 10 minutes of playing without CTDs), there you are again. It´s almost impossible to improve yourself in this game, impossible to nearly enjoy this game, when all the time this fear of an CTD sits in your neck. Wouldn´t I payed money for this application, I would have trashed it already - if it not was the best you could get in this genre. After calming down after CTDs there is always the need of trying it again. Too bad, menos

Thank you all for the different ideas and kind comments. Regarding these I made some more testing and tweaking of my system only for ArmA. On 30.07.2007 Asrock released a new final bios for the Asrock CoreDual VSTA wich added a microcode update regarding dual core cpus wich seemed to boost performance alot in non dual cpu programmed games like ArmA  I studied further overclocking guides regarding my mainboard to raise some clocks - now the good old D805 runs at 3.2 GHz (with stock cooler, rockstable at 50°C under full load). My DDRII timings had been sharpened too, but lead to more CTDs in ArmA (and in ArmA only regardless superstable behaviour in other games at high settings and several stress programms, wich is very sad. ArmA seems very very problematic, when it comes to overclocking) The graphic cards hardware settings I left untouched. ALL THIS GAVE ME AN BOOST IN THE ARMA BENCHMARK FROM 1800 POINTS TO 2400 POINTS !!! I think this boost is quite impressive. The most distinctive difference was, that textures and LODs where loaded within splitseconds and ran very very smooth compared to my old setup, where mainly in the "heli flight over the runway - scene" the runway textures where only loaded, when the Cobra chopper in the end of the scene arrived almost in the middle of the screen. The first UAZ scene even jumped from around 22000 - 24000 to around 30000 !!! Then I did further testing with Rivatuner, new Nvidia betadrivers and the D3D Overrider 1.3, wich comes with Rivatuner. After taking over the driversettings with Rivatuner instead of the native control panel my ArmA score was messed up to 1800 again   - I did something wrong. I then used the D3D Overrider 1.3 settings to force to Vsync and tripple buffering in DX 9 and the game ran alot smoother but still in the bad 1800 region. Some comments on your kind ideas: Well I am used to have around 45 FPS with other demanding games at very high settings with this machine (when I built this PC out of curiosity and an experimental budget of 300€, the first software was Queke4 with latest patches and highest settings at 1680 x 1050.) Queke is one of the very fine games that introduced a multicore code later by patching.(HINT, HINT) You can enable and disable the multicore usage via menu. Queke ran totally awsome on this cheap Comp - even without multicore support I ran with about 45FPS and I was absolutely amazed by this good old Computer ! You have 2GB RAM, try this tweak http://www.flashpoint1985.com/cgi-bin....b+tweak As I stated, I did this pagefile tweak and it gave nothing to mention here - seems I had no caching trouble before and unless WinXP makes up its own invisible pagefile, wich is something between 1.5GB to 4.5GB in this machine while running different software and watching the pagefile rising in taskmanager. I am not aware whether this is a good or bad thing, Windows does but as you cannot prevent this its useless to temper with here. Question: Answer: I understand this is a low cost/performance dual core CPU with a slow FSB. Since ArmA only uses one core, your CPU is very likely to be the weak link. Well, you are right. This is a low cost CPU, wich happens to leak just 55,- € from my bank account. BUT it performes like hell on every single software I tried EXCEPT ArmA. The nice chart, Kevlar2007 showed us is unfortunately not meeting the problem of this thread, as my D805 performes around the benchmarks of an D940 (regarding its dry benchmarking and its raw clock speed) so in the game presented here (UNREAL TOURNAMENT - remember) I would land around 50FPS. But as the crux of my problem shows, and everyone who is involved with computers and gaming has learned ever single game with different engines, cpu usage and gpu, . . . runs different on ones machine. So as I am in the mood (what an asshole I can be in times   ) and just for a showoff I ll come around with another table: Btw, this test is a nice read even if one has no D805: A 4.1 GHz Dual Core at £79.95 - Can it be True? Win XP Pro SP2 patched and hotfixed to 07/2007 no  @Pulverizer: You shed light on an very interesting point here.  As it happens, the CPU runs only at about 68%, so something is slowing the game down, BUT NOT THE CPU (the core that is used, which runs at 3.2GHz) Ciao, menos

Thank you all for the different ideas and kind comments. Regarding these I made some more testing and tweaking of my system only for ArmA. On 30.07.2007 Asrock released a new final bios for the Asrock CoreDual VSTA wich added a microcode update regarding dual core cpus wich seemed to boost performance alot in non dual cpu programmed games like ArmA  I studied further overclocking guides regarding my mainboard to raise some clocks - now the good old D805 runs at 3.2 GHz (with stock cooler, rockstable at 50°C under full load). My DDRII timings had been sharpened too, but lead to more CTDs in ArmA (and in ArmA only regardless superstable behaviour in other games at high settings and several stress programms, wich is very sad. ArmA seems very very problematic, when it comes to overclocking) The graphic cards hardware settings I left untouched. ALL THIS GAVE ME AN BOOST IN THE ARMA BENCHMARK FROM 1800 POINTS TO 2400 POINTS !!! I think this boost is quite impressive. The most distinctive difference was, that textures and LODs where loaded within splitseconds and ran very very smooth compared to my old setup, where mainly in the "heli flight over the runway - scene" the runway textures where only loaded, when the Cobra chopper in the end of the scene arrived almost in the middle of the screen. The first UAZ scene even jumped from around 22000 - 24000 to around 30000 !!! Then I did further testing with Rivatuner, new Nvidia betadrivers and the D3D Overrider 1.3, wich comes with Rivatuner. After taking over the driversettings with Rivatuner instead of the native control panel my ArmA score was messed up to 1800 again   - I did something wrong. I then used the D3D Overrider 1.3 settings to force to Vsync and tripple buffering in DX 9 and the game ran alot smoother but still in the bad 1800 region. Some comments on your kind ideas: Well I am used to have around 45 FPS with other demanding games at very high settings with this machine (when I built this PC out of curiosity and an experimental budget of 300€, the first software was Queke4 with latest patches and highest settings at 1680 x 1050.) Queke is one of the very fine games that introduced a multicore code later by patching.(HINT, HINT) You can enable and disable the multicore usage via menu. Queke ran totally awsome on this cheap Comp - even without multicore support I ran with about 45FPS and I was absolutely amazed by this good old Computer ! You have 2GB RAM, try this tweak http://www.flashpoint1985.com/cgi-bin....b+tweak As I stated, I did this pagefile tweak and it gave nothing to mention here - seems I had no caching trouble before and unless WinXP makes up its own invisible pagefile, wich is something between 1.5GB to 4.5GB in this machine while running different software and watching the pagefile rising in taskmanager. I am not aware whether this is a good or bad thing, Windows does but as you cannot prevent this its useless to temper with here. Question: Answer: I understand this is a low cost/performance dual core CPU with a slow FSB. Since ArmA only uses one core, your CPU is very likely to be the weak link. Well, you are right. This is a low cost CPU, wich happens to leak just 55,- € from my bank account. BUT it performes like hell on every single software I tried EXCEPT ArmA. The nice chart, Kevlar2007 showed us is unfortunately not meeting the problem of this thread, as my D805 performes around the benchmarks of an D940 (regarding its dry benchmarking and its raw clock speed) so in the game presented here (UNREAL TOURNAMENT - remember) I would land around 50FPS. But as the crux of my problem shows, and everyone who is involved with computers and gaming has learned ever single game with different engines, cpu usage and gpu, . . . runs different on ones machine. So as I am in the mood (what an asshole I can be in times   ) and just for a showoff I ll come around with another table: Btw, this test is a nice read even if one has no D805: A 4.1 GHz Dual Core at £79.95 - Can it be True? Win XP Pro SP2 patched and hotfixed to 07/2007 no  @Pulverizer: You shed light on an very interesting point here.  As it happens, the CPU runs only at about 68%, so something is slowing the game down, BUT NOT THE CPU (the core that is used, which runs at 3.2GHz) Ciao, menos

So it seems I am quite on high hopes to get this software running without getting eye cancer and fried braincells by choppy 25FPS ? To bad - as I thought that a fluid running ArmA is absolutely essential for good aiming and long range shots aswell as flying helicopters without risking the crews life by only 5 to 10FPS. "Darn - this taxi is risky - sorry guys, missed 3FPS here, to see that rock" I really would like to have it running without touching the 30 FPS (from above of course). So thanx for some input so far Beagle Is this machine so bad ?

So it seems I am quite on high hopes to get this software running without getting eye cancer and fried braincells by choppy 25FPS ? To bad - as I thought that a fluid running ArmA is absolutely essential for good aiming and long range shots aswell as flying helicopters without risking the crews life by only 5 to 10FPS. "Darn - this taxi is risky - sorry guys, missed 3FPS here, to see that rock" I really would like to have it running without touching the 30 FPS (from above of course). So thanx for some input so far Beagle Is this machine so bad ?