Jump to content
Sign in to follow this  
ddraig

Error during v-buffer creation: error 8876017c, Need some advice Please

Recommended Posts

Hello, A little background:

Running vanilla DayZ 1.7.6.1 as mod on Chernarus. My rig is Radeon HD 4870 x2 1G total on PCIe, i7 960 quad core 2.67GHz OC'd to 3.81GHZ, 6 Gig ddr3 1333Ram running at 1066Mhz, GA-X58A-UD5 GIGABYTE mobo. Running Windows XP.

Ok, I am absolutely stumped, have tried everything within reason to get this error to go, including scouring these forums for solutions. What happens, is that I will play, and within 5 minutes, I get the Black 'Receiving...' for 10 to 30 seconds, typically when I am in Electro or Cherno, larger cities. I look at ArmaOA.rpt and I see the errors pasted at the bottom of this post. It will always be 'Error during v-buffer creation: error 8876017c', sometimes it will be the same, but with 'i-buffer', there is no specific cause mentioned in the logs, unlike some others who have had this error, just a memory dump. The only thing that seemed to help was rolling back my catalyst drivers to 10.9, which seemed to delay the error to about every 10-15 minutes. . Note, the game keeps running, it does not CTD, but it makes it unplayable as it seems to happen during heavy action (as well as not), so I end up dead! :)

And I have tried everything: memtested my ram (checked out OK), scandsk and defragged my HD with pagefile off, increased my pagefile from 2-4G, to 6G constant, ran anti-virus (bitdefender, found nothing), ran video memory stress test (vmt.exe) on my video card (I did the middle 15% test rather than the hours long one since I heard vmt is out of date and my video card & system runs stable on other games), checked out OK. Increased my GPU fan via CCC, I even ran Dayz pbos, and most of the arm0a pbos on a ramdisk. I also ran checks on my CPU, GPU & system temperatures, and it is nowhere near overheating, so I have not removed the overclocking on my CPU & system, since other games seem to run stably. Oh yeah, and I have tried all the command line options with various values, like -vrammax, -maxmem, -exthreads, -cpucount, turned down in-game settings to bare minimum, and set in-game video mem to very high/default etc...

Can anyone see what is going on in the logs? Everything 'looks' ok to me in terms of memory. Also any suggestions and what it could be or what to try? Whats odd is that I thought I ran Dayz ok 2 years ago when playing on other servers, perhaps I didnt notice the 'receiving...' error as much back then, which is why I reverted to older drivers, which has been the only thing that has shown improvement! So are there any catalyst drivers in particular that anyone can recommend for my rig & Arma2OA engine?

Some more info while I am it: I am running a private dayz control center server on a laptop on my lan, and playing dayz 1.7.6.1 over my lan. During testing, I would play locally on the laptop by connecting as localhost, and the dayz/armaoa client laptop would eventually CTD, sometimes after 10 minutes, sometimes after 1/2 hour, but I put this down due to overheating, as there was nothing in the armaoa.rtp about the crash, nor any black 'recieving..' screen . The lap top is a dell latitude e6530 ,hd4000 video card, i7 quad core 8 gigs of ram and running windows 7. Its not a games machine, and would get extremely hot. Is it possible that a network/server issue is causing it? I fixed most of the script errors in the sqf files, but some still do get generated.

Thanks for any help, I really love these game engines and what they try to achieve, loved OpFor back in the day as well, just at a complete loss here :confused:

Here are the errors, mostly get one at a time which causes the black screen 'recieving..' screen to come on for 10-30 seconds.

3 in a row here, what is going on?

(EDIT: Going down through all 3 errors, I notice that in the 'VID' section, the 'free: local' memory keeps decreasing. I presume that that this means that it is video card/graphics memory that is being allocated?)

:

Error during v-buffer creation: error 8876017c
Virtual memory total 2047 MB (2147352576 B)
Virtual memory free 1277 MB (1340047360 B)
Physical memory free 689 MB (723353600 B)
Page file free 6014 MB (6307041280 B)
Process working set 444 MB (466247680 B)
Process page file used 438 MB (460091392 B)
Longest free VM region: 182427648 B
VM busy 1143115776 B (reserved 266031104 B, committed 877084672 B,
mapped 33153024 B), free 1004236800 B
Small mapped regions: 24, size 135168 B
VID: alloc 584467520, limit 1140745832, free: local 364544628,
nonlocal 123076608, DX9 487587840, virt. 1339981824

Error during v-buffer creation: error 8876017c
Virtual memory total 2047 MB (2147352576 B)
Virtual memory free 1277 MB (1340047360 B)
Physical memory free 689 MB (723333120 B)
Page file free 6014 MB (6307033088 B)
Process working set 444 MB (466145280 B)
Process page file used 438 MB (460091392 B)
Longest free VM region: 182427648 B
VM busy 1142984704 B (reserved 266031104 B, committed 876953600 B,
mapped 33021952 B), free 1004367872 B
Small mapped regions: 24, size 135168 B
VID: alloc 584467520, limit 1140745832, free: local 364510284,
nonlocal 123076608, DX9 487587840, virt. 1340047360

Error during v-buffer creation: error 8876017c
Virtual memory total 2047 MB (2147352576 B)
Virtual memory free 1277 MB (1340047360 B)
Physical memory free 689 MB (723353600 B)
Page file free 6014 MB (6307074048 B)
Process working set 444 MB (466161664 B)
Process page file used 438 MB (460091392 B)
Longest free VM region: 182427648 B
VM busy 1142984704 B (reserved 266031104 B, committed 876953600 B,
mapped 33021952 B), free 1004367872 B
Small mapped regions: 24, size 135168 B
VID: alloc 584467520, limit 1140745832, free: local 364496460,
nonlocal 123076608, DX9 487587840, virt. 1340047360

Edited by ddraig

Share this post


Link to post
Share on other sites

FWIW, after posting this, I decided to go out and get a new video card, an MSI GTX 970 :)

Have not had a problem since, so it must of been the HD 4870X2 card.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×