Getting very confused, can someone help?

[Jonney Napalm 10]

Hi all,

Can someone explain what this means please:-

'Error during v-buffer creation: error 8876017c'

I'm having no end of problems trying to get ArmA2 to run, and run well, as it seems are quite a few others.

I've trawled through the forums and tried a miriad of different setting, adding this and that to the exe target, downloading and updating then rolling back of video drivers etc.

I just really want to play this game as the few times that I have got it to work properly I think it looks just stunning.

It seems my hardware choices have made me one of the afflicted as I have:-

Intel core i7920 at stock

6Gb of DDR3 ram

Asus Rampage II Extreme

GTX 295 gfx card

All running Vista 64 Home premium.

ArmA2 patched to 1.02.58134

Nvidia 182.50 video driver

Am I right in presuming that the above message is something to do with video ram? or is it system ram?

I'm starting to get quite confused.

Basically the ArmA2.RPT file is just a long list of the above message with a smattering of 'Vertex Buffer too small (19819<16384)' and finally ending with either

'Cannot commit

ErrorMessage: Cannot commit

Cannot commit

Link to 94c9a0ba (Obj-308,166:186) not released'

or

Exception code: C0000005 ACCESS_VIOLATION at 71D49985

Version 1.02.58134

Fault address: 71D49985 01:00008985 C:\Windows\system32\d3d9.dll

file:

world: Chernarus

Prev. code bytes: 00 00 85 FF 8B 86 10 2A 00 00 0F 84 CE 6A 02 00

Fault code bytes: 8B 4F 64 8B 9E 0C 2A 00 00 0B 9E 08 2A 00 00 8B

Registers:

EAX:00000C00 EBX:49CA5D04

ECX:09E57FC6 EDX:49CA5D00

ESI:06F03B80 EDI:0000000B

CS:EIP:0023:71D49985

SS:ESP:002B:49C6FE9C EBP:49C6FEC0

DS:002B ES:002B FS:0053 GS:002B

Flags:00010202

Now I understand that 'Fault address: 71D49985 01:00008985 C:\Windows\system32\d3d9.dll' is refering to video related things and that sometimes before I CTD my textures go all funked up and framerate drops.

Also, in my cfg file I have 'localVRAM=924581888; nonlocalVRAM=1337501696;' Is the local vram my video card? if so it's only seeing about half of what is there, and the nonlocal vram my system ram?

I presume those numbers are in bytes?

I have the -winxp currently in my exe target.

Can someone explain to me what numbers I should be seeing running a GTX295 and having 6GB of system ram (I know that ArmA2 is hard coded to 2GB of memory, but surely that's less that 2 GB)

I'm basically just trying to understand which bit of my system is falling over so I can concentrate on looking for the solution for that, and not getting drawn in to changing a load of other stuff that isn't needed.

Yours confusedly,

Jonney

Edited July 4, 2009 by Jonney Napalm

[Bulldogs 10]

error 8876017c is a Windows error code usually relating to an error while attempting to access video memory.

It's very hard to troubleshoot, but installing the latest DirectX update generally helps, as well as disabling anti-aliasing in game.

If you can get in game then I suggest disabling anti-aliasing and anistopic filtering.

If you can't get in then you could change it in a cfg file but I'm not sure how to myself sorry.

I should note that Arma 2 seems to have issues addressing memory in certain situations (especially 64 bit OS situations) Running a 32bit OS may help but not definite. If you can't get it to work your best bet is to post in the bug report thread and hopefully it'll be addressed next patch.

[beugnen 10]

Hi all,

Can someone explain what this means please:-

'Error during v-buffer creation: error 8876017c'

Basically the ArmA2.RPT file is just a long list of the above message with a smattering of 'Vertex Buffer too small (19819<16384)' and finally ending with either

'Cannot commit

ErrorMessage: Cannot commit

Cannot commit

Link to 94c9a0ba (Obj-308,166:186) not released'

hi jonney,

as you have probably guessed, the application is trying to allocate graphical memory but sadly the buffer is too small. not all vertex buffers are the same, some are just the 3D co-ordinates, some have extra colour information and some have additional vertex normals. if the application specifices a request for vertex-cord+colour+normals for a coord-only buffer then well...boom.:eek:

sadly i dont know what you can do to get around it. is it happening in a particular mission or save game?

[Jonney Napalm 10]

Thanks for your replies.

I think it's because ArmA2 only see's about half my video memory.

The GTX295 has 1792Mb of video ram (I think, off the top of my head), but according to my cfg file, it's only seeing approx 880Mb.

localVRAM=922484736;

nonlocalVRAM=2143780864;

As far as I understand, it's essentially 2 gfx cards stuck together, each having half the v-ram, so approx 896Mb per card.

It see's and uses both GPU's as far as I can tell as the second GPU is throttled back until Arma is started and then ramps up to match the first GPU.

I may be barking up the wrong tree completely, but as arma2 is only detecting half my v-ram and I'm having issues adressing v-ram, I suspect the 2 may go hand in hand.

Still got absolutely no idea as to how to go about fixing it though.

[Jonney Napalm 10]

Right, I've updated the drivers to 186.18 and run the EVGA enhancement patch.

My cfg file now reads:-

localVRAM=1948971008;

nonlocalVRAM=1948971008;

So surely that means that it has detected my GFX card more accurately?

Still can't get the game to run though, as after a few minutes the textures start to corrupt and then it CTD's with a 'Cannot Commit' error box.