Source Game Errors

Forum Games General : Games General Discussions - Source Game Errors

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

First of all I am not sure where to put this (Dont flame)

This is for steam games (source)

I some how got past the freezing when loading (I put something in the shortcut, but it is still very slow and tends to freeze at Parsing game info, or Sending client info) and I was in the game then I got that direct X 8 error or soemthing.

I get this

http://img49.imageshack.us/img49/5956/errorsteamsf7.png

Please help! It does this for every source game/mod except the CSS Zombie Mod.

1 gig RAM
7950 GT 512mb Nvidia
179 GB space
Pentium 4 3.20ghz


I also get
http://img467.imageshack.us/img467/2470/gmoderrorcw4.png

and
ENGINE ERROR - failed to lock vertex buffer in CMeshDX8::LockVertexBuffer

I tried calling Valve, but they said they don't accept phone support right now.. figures.

So I am looking for help! PLEASE.

Sponsored Links
Register or log in to remove.
- 0 +

dont use vista.

Reply to risk

I found another forum which I am going to quote several key posts with various fixes for this problem. Good luck.

Quote :


i got it sorted
i downloaded the latest dx9 (DirectX End-User Runtimes (April 2006) Full Download)
but didn`t seem to work then went to steams forums and it says to disable programs like p2p and stuff like that,so i switched off these progs
thunderbird
sysmatrix
msn messenger
and there you go back to workin better than ever happy days



Quote :


raduz
11-06-2006, 04:05 PM
One way to "fix" this is to start a game at 800x600 resolution and then change to previous higher resolution. This works for my laptop with a radeon 9600.


Quote :

wingwolf
11-06-2006, 04:37 PM
and how do we change that if we cant start the game?


Quote :

Beerdude26
12-06-2006, 12:31 PM
By putting -width 800 -height 600 in the game shortcut parameters.




Quote :

Hi to all!

I have just registered to help you. I found this page using Google when i get the same error than you all. But the answer was not here. I didn´t find the answer anywhere, it was all luck. What you have to do is to install the DirectX June update from here: http://www.microsoft.com/downloads [...] layLang=en and you will never get that error again.

Bye!



Quote :

fix found
put

-DXlevel 70

into the launch options. once your into the program feel free to go to your options and reset everything. :smoking:

Reply to infornography42

And one more that seems to be more accurate.

Quote :

OK GUYS, I'VE DISCOVED THE PROBLEM AND SOLUTION! HERES WHAT I HAVE FOUND! TRUST ME, READING THIS WILL NOT BE A WASTE OF TIME!

Alright, first off, the program that is causing the error is ATI's Catalyst. Here's my story. I discovered that there was a new 7.3 Catalyst, and decided to try installing it to see if it would fix the problem. I downloaded it, and then updated, but the Catalyst upgrade did absolutly nothing. I mean by the fact that it did not install anything new. I was confused when I opened my Catalyst Control Center, and it showed my old version (7.2) of Catalyst. I decided to uninstall the Catalyst Control Center, and to try installing 7.3 again. Guess what, the 7.3 upgrade does not include the Catalyst Control Center, so now I don't have the Control Center. HOWEVER, I decided to try my Half-Life 2 demo (as a test to see if source would work, since I have discovered that the IDirect3DDevice9:: Present() error is source related). It did not crash with directx 9. I then tryed my Dark Messiah. Usually, it would crash 10 seconds of my checkpoint that I last saved. However, this time, I managed to play Dark Messiah for 10 hours, as of right now, straight without any errors what so ever.

In conclusion, I have discovered the solution to the problem. It is either one of three things:

Either closing Catalyst Control Center (not uninstalling, just closing the program) fixes it, uninstalling the Catalyst Control Center fixes it, or 7.3 fixes the problem (which I doubt, even though I never tried it with Control Center).

Now for an explaination of the problem and why the many other (so called) temperary solutions on this forum topic worked for a while.

The problem is most likely due to the high graphical detail of Source. While playing Half-Life 2, the game would crash with the error only when a high graphical part of the game came, like mass explosions or graphical cutscenes, that would require alot of... graphics to be able to handle. The Catalyst, I assume, is not able to process Source correctly, and the Directx in Catalyst would be unable to process itself, resulting in the error. This is the reason the only people effected by this error is people with Radeon graphic cards, since Radeon uses Catalyst!

This is the reason to why the many other solutions posted on the forum worked... for a while. One solution I saw was that reducing the directx level worked. Another is reducing the video settings for graphical effects to low or medium. This is because it would cause the graphics to reduce, lowering the chance of meeting those high graphic scenes in the game. Another solution I saw was switching from Catalyst drivers to Omega drivers. This is obvious a workable fix, since Omega drivers require you to uninstall Catalyst, fixing the problem!

You can try testing around it to see what the real solution is, but if you are really eager to play whatever Source game you want to play (yes, all Source games are effected to this error), then just play it safe and uninstall Catalyst Control Center. If it does not work, then try uninstalling the driver, then installing it back using the Windows Device Manager in the Control Panal (I don't know about you, but it's there for my Vista). Just go find your Radeon, and click the install/update driver button when you click on it in the Device Manager. Good luck trying to fix the problem!

I think that would have been good 2 years ago. Unless someone else with the same problem needs it, then you bumped a thread and people here don't like bumped threads.

Reply to infornography42

One thing, I have Nvidia. I will try the others.

Reply to Shortstuff7

So you do! Eh, go fig.

Good luck anyway. One of those other work arounds might do it for you.

Reply to infornography42

Ok guys, I got the errors fixed (Some motherboard BIOS or something I needed) and now my games freeze while loading them! The task manage says their Not responding and I end up having to end them. Help please?

Reply to Shortstuff7
Tom's Hardware > Forum > Games General > Games General Discussions > Source Game Errors
Go to:

There are 516 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them