CreateIndexBuffer failed (8876017c) Problem

[Gremlin0790 0]

Hey Everyone,

I've had a really aggravating time trying to get ArmA to work on my PC. It seems to be crashing after a certain amount of time playing (it goes into the Error Report box). But the most annoying problem of is with the Campaign.

Every time I try to play the first mission, when you are riding around in the Humvee through the various towns, it always crashes at different points - I haven't reached the point where you get out.

It seems to be the same problem, but most of the time it just crashes to my desktop, other times it comes up with an error box saying: "CreateIndexBuffer failed (8876017c)". I have tried everything - overclocking my GPU, turning down my graphics, inserting the -maxmem=512 into the command line. I cannot figure out what is going on with the game.

As I said before, on all the other levels the game works alright but CTD at random times (or at least it seems). I really want to enjoy ArmA, but right now I really wish I hadn't dropped $40 on a paperweight.

My System Specs:

2.6 Ghz P4

128 mb Radeon 9800

1.5 Gb of RAM

I understand my specs aren't that much higher than the minmum, but I doubt this is causing the problem. Any help would be GREATLY appreciated.

-Thanks, Gremlin

*EDIT* Could this be due to the ATI handle leak? I just saw a post on it and I have Catalyst 7.2, which is affected by this problem.

[suma 8]

The error code is 8876017c "D3DERR_OUTOFVIDEOMEMORY".

As you card is just meeting the minimum requirements with 128 MB of VRAM, I recommend you to set a reasonably high AGP aperture in your BIOS (128 or 256 MB should do) to make sure the game has some space for vertex and index buffers.

In case you would feel like upgrading the video card for a 256 MB or better model, it is quite likely it would made the game much smoother for you, as the graphics card you have seem to be the weakest link in your performance chain.

[Gremlin0790 0]

Thanks for your help Suma. How do I set the AGP aperture in the BIOS?

-Thanks, Gremlin

[StormbringerGT 0]

This varies from motherboard to motherboard, do you know the brand and model of what you currently have?

[B-C 0]

Im having this exact same problem. I play for about 20mins then it crashes and gives me the 8876017c code.

I also do not know how to change the apeture. I have the following.

Intel Core 2 Duo. 1.8 (800mhz)

Asus P5N-E SLI Mobo

Asus 7600GT. 256MB VRAM.

G.Skill 1GB Ram (800mhz)

550W PSU

320GB SATA HHD 16MB Cache.

I have check the bios and can not find any option to change it. Is this only available with AGP V.Cards as my Video Cards is PCI.

Thanks

I have just played ARMA again and was flying a helicopter for about 30 seconds and it CTD again. Tried loading up ARMA again and it gave this:

Creating Error Direct3D 9 Graphical Engine.

Not sure what it means but is mostly linked with the error i mentioned before.

[B-C 0]

Anyone had this issue and resolved it?

In addition to what i said above i have been monitoring FPS and it seems to be ok with a rate of 20-25fps but after about 10mins of playing FPS become unstable and jump from 25fps to 9-10fps then back up to 20fps then shortly CTD.

[brokekneck 0]

Same problem here.....

CreateIndexBuffer failed (8876017c)

Athlon 64 3700+

1 gig of RAM

nVidia 7800GT 256 vRam

[B-C 0]

I havent found any fix yet. Hopefully patch 1.08 fixes it. Anyone else had this problem and solved it?

[binkster 0]

I just recently have the same problem. Ive been playing on vista and now I play on XP and all of a sudden I get this CTD and I have 8800gtx. Im playing on v 106 so I may give the beta a round and see. First time it happen it was night and I was using NV in a town. Second time it did it I was in a boat on the water. Seemed when I was using the NV my game started getting choppy, I alt tabbed to check temps and it was reading about 80C... When i went back in it was the same then it crashed..

[1436 1]

I Also had this same problum aswell but i fixed it open youre arma.cfg in notepad if the memorey settings look like this

localVRAM=261169152;

nonlocalVRAM=0;

You Got my problum you need to Update youre Chipset Drivers and delete C:\WINDOWS\Prefetch then delete that arma.cfg file again so teh game can Reditect youre Hardware. Not sure if it is a Nvidia 7.5 bug

[pchaxor 0]

I did the fix CodeSky recommended and still after 1 hour 22 min of play I get ...

Long FREEZE PAUSE in the game, like placing the game on "pause" for 15-30 seconds....

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

No alive in 10000

===FROZEN====>>>>>>BEG

Version 1.08.5163

Fault address: 7C90EB94 01:0000DB94 C:\WINDOWS\system32\ntdll.dll

Prev. code bytes: 49 00 90 90 90 90 90 8B D4 0F 34 90 90 90 90 90

Fault code bytes: C3 8D A4 24 00 00 00 00 8D 64 24 00 90 90 90 90

Registers:

EAX:01C5EBE8 EBX:01C5F07C

ECX:00000000 EDX:01C5EBEC

ESI:01C5EFE0 EDI:01C5EFE4

CS:EIP:001B:7C90EB94

SS:ESP:0023:01C5EE14 EBP:01C5EF08

DS:0023 ES:0023 FS:003B GS:0000

Flags:00000206

Windows Side:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

Event Type: Error

Event Source: Application Error

Event Category: None

Event ID: 1000

Date: 6/10/2007

Time: 12:22:59 PM

User: N/A

Computer: REMOVED

Description:

Faulting application arma.exe, version 1.7.0.5157, faulting module ntdll.dll, version 5.1.2600.2180, fault address 0x00018fea.

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: 37 2e 30 2e 35 31 35 37 7.0.5157

0028: 20 69 6e 20 6e 74 64 6c in ntdl

0030: 6c 2e 64 6c 6c 20 35 2e l.dll 5.

0038: 31 2e 32 36 30 30 2e 32 1.2600.2

0040: 31 38 30 20 61 74 20 6f 180 at o

0048: 66 66 73 65 74 20 30 30 ffset 00

0050: 30 31 38 66 65 61 0d 0a 018fea..

Then a few Moments later .....

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

===FROZEN====>>>>>>END

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 2:4770 (type UpdateAIUnit) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 2:4770 (type UpdateAIUnit) not found.

Client: Object 2:4770 (type UpdateAIUnit) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Client: Object 6:2 (type AIStatsMPRowUpdate) not found.

Virtual memory total 2047 MB (2147352576 B)

Virtual memory free 254 MB (266690560 B)

Physical memory free 1015 MB (1065136128 B)

Page file free 1056 MB (1107472384 B)

Process working set 377 MB (395665408 B)

Process page file used 391 MB (410226688 B)

Runtime reserved 1260 MB (1322057728 B)

Runtime committed 287 MB (301572096 B)

Longest free VM region: 17879040

ErrorMessage: CreateIndexBuffer failed (8876017c)

Object id 9e67d17c (380) not found in slot 250,243

w:\c\Poseidon\lib\landSave.cpp(1692) : Link cannot be resolved

Object id 9e47dfae (1966) not found in slot 251,242

w:\c\Poseidon\lib\landSave.cpp(1692) : Link cannot be resolved

Object id 9ea7dc71 (1137) not found in slot 251,245

w:\c\Poseidon\lib\landSave.cpp(1692) : Link cannot be resolved

Object id 9e47dfa6 (1958) not found in slot 251,242

w:\c\Poseidon\lib\landSave.cpp(1692) : Link cannot be resolved

Object id 9ea7e468 (1128) not found in slot 252,245

Then ArmA Crashes to desktop and a lil ArmA box pops up saying: CreateIndexBuffer failed (8876017c)

[pchaxor 0]

It seems like the more vRam a card has and the lower your settings are; the longer it takes the error to occur.

It also seems as if ArmA doesn't know when to FLUSH the vRam or when to stop writing to the vRam when it is "Out Of Memory".

Temp Fix:

A friend of mine told me to do <Left-SHIFT> + <NUM PAD> <-> then type 'FLUSH' to clear vRam during game, this seems to have minimized my crashes.

There is CLEARLY a problem that needs to be resolved with vRam in ArmA v1.08. It is neither an ATI or Nvidia issue, it is a vRam issue.

[B-C 0]

Thanks pchaxor, however when i tried to flush it made my game CTD anyway lol.

Thought they made this to help prevent CTD but all it did was make it CTD faster

I wish i could play online without this CTD crap. Last time it CTD it changed my monitor display to 680x480 or whatever it is. Couldnt change it back to my native 22inch monitor resolution, had to restart the computer.

Anyone worked out a solution. My PC spec are listed up higher on this page.

[pchaxor 0]

Last time it CTD it changed my monitor display to 680x480 or whatever it is. Couldnt change it back to my native 22inch monitor resolution, had to restart the computer.

I have had this issue also ... 22" Sceptre at 640x480 ... (not even supported by the monitor is why.) But a reboot fixes it.

You know there is a similar issue with ATI cards, just a different error code with the same meaning.

I rolled back to a OLD Nvidia driver to see if it makes a diff.

Have any of you tried this yet?

[B-C 0]

Hi pchaxor,

Yeah i have used several drivers now. I have used the one before 94.2 or whatever it is and i have also used 158 from 3d guru (which is not a 7*** series driver.

I have also tried everything else:

changing graphic settings

forcing off recommend settings such as v.snyc etc

page file

cant remember half the stuff but i can assure you if its written in this forum i have done it!

i have no other problems except fps going from a stable 30 to 5 and then CTD. As you said its a V-ram issue that needs to be fixed.

thanks for your help. maybe they will have a fix around time lol at version 3.9 lol ....peace!

[macguba 0]

I am also suffering from this CTD and createindexbuffer failed error.

This is the best thread I can find on this issue and Suma has made a helpful suggestion in the first reply. However, I have not the faintest clue how to implement it. I know it varies from motherboard to motherboard, and no doubt graphics card to graphics card, but would somebody be kind enough to point me in the right direction? I daresay I might be able to change my AGP Aperture if knew how to edit my BIOS.

Many thanks.

[B-C 0]

Hi Macguba,

You will need to look at your MB instruction manual in setting AGP apetures. Its in your bios so maybe bios settings in your MB manual.

For me i have a PCI card and cant change it so im left with a little fix that i found works for me until they fix it.

What i do is i run my game in windowed mode and use Nvidas monitor to watch the percentage of graphics card memory used. if it gets above 94% i just change the Post Processing to high and it decreases it to 90% when it gets to 94% again i change it back to low and keep going with this method.

Dont ask me why increasing PP from low to high makes it run better for a little while... seems wierd to me!!!!! but at least i can play for hours now!!!!

[(1VB)Chaos 0]

Forget it - increasing the AGP size in BIOS just delays the problem for a short time!

This is a problem that BIS should be adressing ASAP, rather than wasting time on an expansion pack for a game that doesn't currently work!!

[(1VB)Chaos 0]

OK - quick workaround / fix (works for me anyway). If you've got one of the maxmem / memsize commands running, get rid of them - I did and now I get at least a bit more time (just had 40 minutes without a crash - at which point the lack of skill/frames/having a life made me switch off.......)

If neither apply - then I'm sorry - just keep on at BIS - after all they ARE supposed to know how to fix this stuff, right??

[NetWalker 0]

Same problem here. I got a 512MB video card, and after 30-40min of game play my ArmA crashes with that error. This is a problem that happens for a long time now for a lot of users. That's a shame BIS did not fix it!!!!

[armasteri 0]

yep, create index buffer(8876017c) - paperweight now, my PC too..

[ozog 0]

were do i put the maxmem thing cause i have tried to put it in here ............."C:\Program Files\Atari\ArmA\arma.exe" which is the target and i get an error that it cant find it ...............plz help

[B-C 0]

were do i put the maxmem thing cause i have tried to put it in here ............."C:\Program Files\Atari\ArmA\arma.exe" which  is the target and i get an error that it cant find it ...............plz help

You have to right click on the desktop icon (arma icon) and then click properties and it will have a line which says target. add it to the end of what already written there

[FTWalker 0]

New to the board, because I've got the same problem

Specs:

Win XP Home SP2

AMD XP3200+ (Non-OC'd)

ATI 1950PRO AGP (256MB) w/ 7.7 drivers

1GB system memory

latest DirectX9.0c

USB sound (LTB 5.1 headphones)

ArmA v.1.08 Eng.

I can usually run it about 10 mins. before the game stutters to a halt and the "CreateIndexBuffer failed (8876017c)" message pops up as I CTD, though sometimes it's just the Windows "Program must now close" box. There's no apparent difference from before the patch (v.1.06) to now, no difference if I use the "-maxmem" switch, higher GFX settings bring the end a little faster, and the "flush" technique might buy me a couple more minutes of time.

The only proposed fix that I haven't tried is bumping the AGP aperture up to 256 (it's currently 128). I may get ambitious and try it, but I'm not going to hold my breath.

Hopefully, with so many of us having the same (or similar) problems, BI will be able to plug that memory leak.

Edit: Added sound capability info.

[Pempel 0]

Hey everybody,

unfortunately here the same problem.

But as far as it concerns me, it only appeared after I upgraded to v1.08. Under 1.05 or lower this error never occured!!!

I always thought it is a problem caused by the new patch.

Can anyone confirm this?

regards

Pempel