"Failed to Lock Vertex Buffer", Half Life 2 DM error

[Joshmcmillan]

Hi,
recently I have been getting an error whilst playing half life 2 deathmatch. It crashed the game and comes up with an engine error saying, "failed to lock vertex buffer in CMesh DX8", or something similar to that. Does anyone know how to stop this?

Also, I'm getting an HD3850 on Saturday and reformatting, is there any chance of this error still being there, because people on the internet say that reformat and it stays?..

 

[wtf8269]

The fact that it mentions DX8 is interesting. Are your graphic drivers up to date?

 

[Joshmcmillan]

I had a couple of month old display drivers on my intergrated 6150 and I upgraded as an attempt to fix the problem but it didn't. I have Direct X 9.0c.

I don't too much it not working now, I just REALLY hope it works when I get my HD3850.

 

[Joshmcmillan]

Anyone else have any ideas?

 

[erocker]

Sorry, but your integrated graphics just can't handle the game. The 3850 will solve that problem. Just be sure to install the new drivers correctly.

 

[wiak]

3850 will fix it easly

 

[Kreij]

Many people with different configurations are seeing this error on various games.
This was posted on one site ... might be worth a try.

ok this is a simple fix and i stumbled upon it while searching other forums for a os page pool memory problem.
BE WARNED THIS SOLUTION, IF NOT DONE CORRECTLY MAY BE HARMFUL TO YOUR COMPUTER.
Heres the solution:
Start Menu > Run > regedit

Surf down to this key. The REG_DWORD "PagedPoolSize"
Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Double click on "PagedPoolSize". Hexadecimal is listed first.
Change the "Value Data" to one of these below:
Note: You only need to enter EITHER Hexadecimal or Decimal.
They both are the same. I recomend using 256Mb should solve the problem.
Code:

Megabytes Hexadecimal Decimal
192Mb 0c000000 201326592
256Mb 10000000 268435456
384Mb 18000000 402653184

You do not need anything bigger than 400Mb... in most cases 300Mb is too much as well.

Once you are done, make sure you reboot your computer.

 

[howells1]

Thanks Kreij for providing your registry edit. I noticed that the original post regards the CmeshDX8 error in the steam engine, but the edit also solves the notorious nv4_disp infinite loop BSOD error that many people with nvidia cards have been getting. I was certainly getting crashes on all source games until I tried your instructions, and voila: all nv4_disp BSOD errors, crashes, and stalls in loading vanished. Now my new Dell Inspiron is truly showing off its new hardware. And this is after I tried updating drivers, reverting back, trying third party modifications, pretty much everything short of returning the computer.

I have posted your instructions in the nvidia forum and linked my thread over there to this one. If there are people out there that still have the problems I had, I want to make sure they try this one!

 

[Ketxxx]

You own a Dell....? :shadedshu

 

[Tric0ps]

Kreij: Value data

Kreij,

So what how do i right in the value data?


Reply plz

 

[yogurt_21]

Hi,
recently I have been getting an error whilst playing half life 2 deathmatch. It crashed the game and comes up with an engine error saying, "failed to lock vertex buffer in CMesh DX8", or something similar to that. Does anyone know how to stop this?

Also, I'm getting an HD3850 on Saturday and reformatting, is there any chance of this error still being there, because people on the internet say that reformat and it stays?..

directx issue, I actually got it with my 2900xt on Pirates of the carribean online. had to go to older drivers and force my directx in the game to get it to work. then magically one of their updates fixed it.

Haven't had the issue on my 9600gt.

you might wanna try forcing directx9

in steam right click HL2 deathmatch> properties > set launch options > type in "-dxlevel 90" without the quotes.

 

[Joshmcmillan]

Ancient thread. I've had my HD3850 for AGES, never had this problem since.