• Failed index buffer, Memory could not be read, and other woes...
    3 replies, posted
I have consistent crashes when spawning sweps, I have 2 packs of sweps, mad cows weapons (dods , css and ffof included), and all of kermites weapons. I try to spawn these weapons, and after awhile when I spawn one it crashes to the desktop with a random error message such as; "failed to lock index buffer in dx8" or "indexed memory could not be 'read'" and other such messages. Is this a gmod problem or maybe I don't have enough memory to support 100+ weapons at one time? This happens when spawning to much of anything not just sweps, it's like I can only spawn so much stuff before I have to restart to "clean the slate" as it were. Do I have some kind of selective memory leak? Is there some kind of ceiling to gmod that is dangerously close to begin with? This has been going on for as long as I can remember. I have Microsoft Windows XP Home edition service pack 3 nVidia GeForce 8800 GTS Intel Core 2 Duo CPU E 6750 running at 2.66 GHz And 4 gigs of RAM I don't think it's related but I'm using default drivers on my video card, I never update my video drivers because the last 8 TIMES I tried it made all 3D related programs very very unstable. Halp
I'm sorry to say you have to update your drivers or Gmod become "very very unstable" Also [QUOTE=cashman123;21014302]crashes to the desktop with a random error message such as; "failed to lock index buffer in dx8[/QUOTE] That looks like you're DirectX is on version 8. It's never a good idea to have and old version of DirectX. Update it to Version 9 if you're going to update anything
I'm on directx 9.0c
I have this problem and I definitely have DX9.0+ (using DX10 card and have DX10 installed on other games). EDIT: I was able to bypass it.
Sorry, you need to Log In to post a reply to this thread.