Internal driver error in IDirect3DDevice9::Present()

  • Thread starter Thread starter aum
  • Start date Start date
Maddawg70 said:
I also have this problem, I have the DirectX August update and the 6.8 driver for my ATI card and it still keeps giving me the error. Any other suggestions are aprecciated.
Click to expand...
Could you specify your card, please?
 
I just registered to tell you how I solved my problem.

I've got an overclocked (OC) AMD64 3500+ @ 2.65GHz and a Sapphire Radeon X1800GTO @ core: 575 / memory: 1100 (2x550) MHz.

I use the Source SDK Base "Video Test" in Steam Tools to test changes with every Advanced Video at the recommended settings. And after each change I usually reboot.

I've been running the Catalyst 6.8 a couple of days without any problems, but also without noticing any of the 'fantastic' changes. I use ATi tools to find a suitable OC level and RivaTuner for OC and ajusting the fan speed as well.

I just noticed that the Catalyst version said 06.7 and not 6.8, so I just assumed that I had failed the update somehow. I reinstalled 6.8 and then turned of the hotkeys from ATi tools. Normally I just leaves it at that, but this time I also turned off ATi Smart and ATi Hotkey Poller from Services.

...and then I saw this error. Hm??! I went back and enabled those two services without any luck. It still crash at the funny blurry window, ahem...

Now, If you look past that annoying little pop-up "Internal driver error" and examine the details of the subsequent error of hl2.exe; If datacache.dll is mentioned it usually refers to data corruption caused by some overload or defectiveness of system or gpu ram. I've seen this error quite often, when adjusting and testing memory timings or when using defective ram.

Before attempting to update ATi drivers I think it's a good idea to turn off any OC of GPU with ATi Tools and 3rd party apps like RivaTuner. Sometimes updates clear these settings, but if they don't you have to yank 'em both back in place at default settings first and then OC from there. Better safe than sorry. Even if you don't OC, I think a little yank might help still just to confirm settings.

Well, I turned off OC of GPU core and mem and... it worked. I turned OC back on above mentioned settings and it still works!

Soo... Well... That affirmative reset obviously helped clearing whatever caused the problem - maybe.
 
all I did was go back to catalyst 6.7 and the problem is gone for me. (radeon x300) granted, the problem only appeared for me after this latest Steam update several days ago.
 
i get the same problem, i have a ati x3oo with 6.8 catalyst.

when i'm trying to play episode 1 i can play for a few minutes then it frose on me with the looping sound, so i reinstalled directx and updated my drivers again. now teh program closes at a certain point and goes to that error message.

i got no problems when i play gmod though
 
i have this problem seince i got my gpu.
before i had intergrated intel graphics. when i played css and dods i lagged so bad so i went out and bought myself a kickass gpu. i got a sapphire x1600pro 256mb. since sapphire is such a good and respectable brand i should have no hardware problems.(BTW it costs me $300au so it better work).

i dl the latest dx9.0c aug2006 update and the lastest ati drivers and catalyst 6.8 as well as microsoft.net framework 2.0, so it should have worked all fine. then these stupid problems hit me.i was chatting with my friend who works at addictpc(a online gaming pc company)( www.addictpc.com ) for almost 4days, trying to fix my problems. first it went halfscreen and wouldent load, then this error. so i tryed to load it in dx8.1, and bingo it worked. the next morning i went to play dods and this error came up again. i have been on and off all week, and i've had enough. so finally someone posted something on my clans forums( [BDS] ) that i thought would be usefull, he said try downloading the last three drivers, and work my way backwards to see which one worked. i tryed that and nothing happerned. so im now back to square 1, and i dont know what to do untill a new ati or steam updates come out.

~morgo
 
Im having the same Problem.

I started playing half life 2 on Xbox and loved it so i figured i would play Ep. 1 on pc.


This is looking like the first and last valve game i will ever buy for pc again. What a waste of 20$ when i cant even play past the part where the train rides out of the exploding City.
 
Reinstall DX9 I think fixes it, or reinstall Drivers.
EDIT: The train is endgame, anyways.
 
GordonFreeman911 said:
Reinstall DX9 I think fixes it, or reinstall Drivers.
EDIT: The train is endgame, anyways.
Click to expand...

I seriously dought the part after the stryder where u hop on the train and the citedal starts to blow is the end. If it is, i still want to watch it.

Edit: ok i did this to fix it

-Updated Vid Drivers
-Complained to Valve
-Installed DirectX 9.0c Optional Compondents from Microsofts Site.
-Changed in game Res to a lower one.
-Turn off, from in-game Advanced Video Options, the High Dynamic Range.
-Watch Ending movie.


Crashes included, and the crap i had to go through to watch the missing 30 seconds. I say it was a waste of 20$, Valve needs to fix their stuff.
 
i have the latest ati drivers and other window drivers i have dx9.0c and dx sdk aug 2006, and nothing still happerns.
 
morgo_mpx said:
i have the latest ati drivers and other window drivers i have dx9.0c and dx sdk aug 2006, and nothing still happerns.
Click to expand...

Start the game and Turn off the HDR thingy under video>Advanced. that will fix it. Trust me. And if it doesnt work i will buy you a virtual cookie.
 
if i turn down the reso the game crashes, and if i put it in to a window it crashes aswell, btw im at the sending client box.

and im pritty sure its jst that my card doesnt work well with the drivers because i cant play battlefield 2 eather and thats made by ea games so its not a steam problem
 
Demon Stroke said:
I say it was a waste of 20$, Valve needs to fix their stuff.
Click to expand...

I say you need to fix your stuff, quit blaming them when its your pc's problem. I've had it before and its definantly not anything of VALVe's fault, its mainly your display driver, I suggest trying older/newer driver sets for your pc.
 
How do i install that driver from http://www.microsoft.com/downloads/...75-7B26-4916-8E5F-6F88A5BC09C5&displaylang=en ?

It just extracks some files...where should i put them?

EDIT: nvm, i found the installation file lol

EDIT AGAIN: Hm it didnt solve the problem. Any ideas? Seems like alot of users are having this problems, might be some update or something. Can someone like, email gabe?

This is very irretating.
 
It's a hardware issue, usually deals with your video card drivers, I suggest you try older ones if you have the newest version, and when changing drivers make sure to use driver cleaner.
 
thats what i done. i went back to catalyst 6.3 and non of them . work i sposse ill have to wait for the next ati driver, cause i know its not my pc.

even though its a intel piece of crap.
 
-DXlevel 70 Option

FYI, I did try to add the -DXlevel 70, (as suggested way above) to the launch options and that did help quite a bit.

I do have an ATI (850XT) and in my case, this problem began to arise once I installed DirectX 9C.
 
k, i have found out the problem for this. if you run the direct3d test in dxdiag before you go into steam games etc, the test works but after it doesnt. the problem is that your Direct3D crashes when overpower or something like that. it does the same thing with battlefield2.
now there are two things you can do.
1. try opening your game and playing it with openGL
2. find a sollution

so far i have found nothing, but i am close.
 
DiSTuRbEd said:
I say you need to fix your stuff, quit blaming them when its your pc's problem. I've had it before and its definantly not anything of VALVe's fault, its mainly your display driver, I suggest trying older/newer driver sets for your pc.
Click to expand...

I seriously disagree. My computer is up to date in every way possible. As far as im concerned forcing a lower DX version in order to run or some s*** is a problem on THEIR part. I shouldnt be forced to roll back drivers to play games because i have other games that need them up to date.
 
Demon Stroke said:
I seriously disagree. My computer is up to date in every way possible. As far as im concerned forcing a lower DX version in order to run or some s*** is a problem on THEIR part. I shouldnt be forced to roll back drivers to play games because i have other games that need them up to date.
Click to expand...

If you have issues with Valve, inform them and stop wasting your time on these forums moaning at us. As far as I'm concerned you shouldn't even be playing episode one if you have no idea as to why it's called an "EPISODE"
Twenty pounds is practically giving it away for a game as good as that. If you're so eager to play past the train scene be patient and wait for episode two. Half life 2 is not "some sh*t" and it's not their problem. It's yours. So stop wasting your time and our time.
 
I had the same problem where it told me the halflife2 exe had an internal error with directx9 present...

I downloaded and installed the june update that was suggested... and it didnt fix it. I then changed the rez to 800X600, and the graphics were a bit more choppy, but so far it works fine. I know some people said it crashed for them somewhere in the later chapters... so I will just have to wait and see when i get there.

But I just wanted to state how helpful the thread was and god bless forums.
 
I just tried the direct x 8.1 fix and it worked well for me so far. Just registered to say thanks for the help
 
...

well ... i have a





Intel Pentium 4 3.4GHz Dual Core pros...
and an
ATI Radeon x 1600 pro .. made by sapphire ...

theirs no reason this should be happning(internal driver error in IDIRECT3DDevice9:: presnt()
 
omega

I downloaded the Omega Drivers and it worked for me so far.
Just gotta see if it'll work every time...

This is my first post here. Hi all.
 
Idirect3DDevice9

Had the same problem. Loading game & IDirect3DDevice messgae came up & it bombed. Went to Microsoft & loaded latest versions of DirectX9c & assocciated plugin ins & game now loads. Problem is after a minute action freezes & sound goes all jumpy & have to reboot pc.
 
After trying everything already said. I tried the following?

Run ? dxdiag

Click on the display tab

Then click disable by ?AGP Texture Acceleration

Then exit

Seems to worked for me so far and no crashes for over 2 hours of dod

Hope it works for others
 
ati x300 driver

when day of defeat source it always crashes

I have a acer ATI mobility radeon x300 and i cant find suitable drivers
can someone pls help

i already tried catalyst 7.1. and it doesnt work?
 
Stream needs to fix this

I obtained HL2_E1 when it was first released. Installed only the single player module (stuck with 28.8Kbs dial-up here). After the initial registration and mandatory updates through STEAM, I played the game, 4 times through, without a single crash.

Setting HL2_E1 aside for awhile while playing F.E.A.R (no crashes there), I then visited STEAM again and was barraged with a slew of platform file and game updates. After all that downloading and updating, I decided to play HL2_E1 again for giggles.

Not so fun now with constant "Internal driver error in IDirect3DDevice9:Present()" crashes.

Yes, I read all the above posts, downloaded the DX9.0c drives mentioned, updated to the latest Forecware graphics drivers, and nothing fixes this mess. I can't help but believe that the "updated" game engine broke things.

It's a sure bet I won't waste time/money on buying HL2_E2 when it's available unless and until this problem is resolved.

Edit: "Stream" in title header should read: STEAM

PaulM
 
Mine finally works!

I read about this on another site. I changed to Open in Window Mode, Medium Audio & Video Setting. It came right up. I changed back to Full Screen, and still working. Just changing the A&V may do the trick. I updated to DirectX9.0c before, and it didn't help.
 
Temporary Fix

Hello. I have come with a breaking discovery to temporarily stop the crashing (I had to sign up on the forums to tell you). Before all this, I used to run Counter-Strike Source, and try to join any server but the error message would come up and crash.

Go to your Start Menu. Click on Run. Then type in DXDIAG. Go over to the Display tab. And click on Test Direct3D (you can do Test DirectDraw too but I dunno what that does and never tried it). Everytime for me, when I know I can't join a CSS server without crashing, the first test (Direct 7) will say that you accidentally canceled the test by pressing a key when you didn't. That's what's happened to me; not sure if it'd be teh same for you. But after that, just run the last two tests, DirectX 8 and 9. Afterward, I would test them all again just to be sure that DirectX is working perfectly.

Now go back to your game and voila! It works... for now. Then it'll crash another random time and you'll have to do the DirectX tests again.

Ps. Omega drivers do jack crap. ATiTool overclocking is not the problem, nor is cpu overclocking (I have mine overclocked 24/7 and CSS still works).
 
cjcobra's suggestion worked for me

Before reading cjcobra's (2 above) remedy, I reinstalled hl2_ep1 on top of itself. Couldn't play the game at all after that (wouldn't get past the main menu screen). I then vaporized everything VALVE and STEAM from my hd and did a fresh install of the game. No joy. This time with a different error msg when trying to launch into the game.

When the problem first started for me (after valve/steam updated the game engine) one of the precursors to a pending crash was at game bootup. Of the 3 intro menu screens, the Citadel scene displayed OK, but the other 2, destroyed City17 and underground parking garage, had a sick green cast. The new install displayed the same color distortion problem.

The game set my video and audio options to HIGH by default (GeForce 6800GS chipset gpu, Audigy 2 ZS soundcard) at 1024 X 768 resolution. Following cjcobra's suggestion, I set the video and audio to medium/low quality and to run in a window before launching. Although the opening cut scene played in that same sick green cast, it launched and ran without an error msg.

Once past the opening cut scene and into the game, with colors back to normal now, I went to options and changed everything back to the original settings and then resumed the game. Ran fine. As a further test, I did a quick save, exited the game, restarted and loaded from the quick save and it didn't give any complaints.

Whether you need to change both or one or the other of the "fixes" I don't know. But until Valve/Steam fixes their broken game engine code, this work-a-round should let you play the game. Another thing they "broke" in the upgrade code was in setting the GAMMA (brightness) in the video options menu. Though sliding the bar to the right does increase brightness in the game, in the adjustment box itself it works backwards, darkening instead of brightening.

Thanks for the tip cjcobra...

PaulM
 
Solution Discovered with Explaination (Partial)

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!
 
profetecartless said:
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!
Click to expand...

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.
 
...um can you make a post of just the solutions because i read the post like 10 times and i cant find 3 solutions. Im still have this error it just started at random, and i cant play any steam game also while its loading it stops at 15 blocks on the loading bar and freezes and i have to control alt delete and the times when the doesn't happen it crashes with that error message
 
ive uninstalled my catalyst drivers, reinstalled css, reinstalled catalyst drivers, (by the way ATI 7.2 drivers has MOM.exe keylogger in it) so i jumped to 7.1, didnt work, repeated this process, installed omega drivers, ddint work still the same thing, cant play counter strike or anything under steam. i can play any other game with no problem what so ever unless its under steam. i really dont want to reformat my whole dam pc just to play css and i would still probably get this internal error because i was getting it before and actually for reminding myself i did and now its getting it again. anyone else know of a solution becuase ive heard it all for 1 month now and all they can say is "i dont know umm reinstall video drivers" that link does not work otherwise i would go to the solution page.

AMD FX-57 3.0ghz
4gb Corsair SXMS PRO LED CL2
Radeon X1950XTX
MSI Neo Platinum 4 939
 
You must log in or register to reply here.

Similar threads

bbson john
Hi everyone. I am new to this forum!
Replies
11
Views
6K
Tollbooth Willie
Tollbooth Willie
MFL
Fascinating look at the ongoing psychological evolution of flat hieirarchies.
Replies
2
Views
2K
Tollbooth Willie
Tollbooth Willie
B
Who's left or joined Valve in recent history
Replies
4
Views
32K
MFL
MFL
M
Dota 2 in VR (Need help with shaders and textures)
Replies
0
Views
1K
mrpresidentb
M
B
Marc Laidlaw talks more about his Half-Life 2: Episode Three ideas
Replies
3
Views
21K
Tollbooth Willie
Tollbooth Willie
Back
Top