I'm back...with a problem... 33 replies

Please wait...

The Typer

Formerly justincase3

50 XP

20th June 2006

0 Uploads

1,120 Posts

0 Threads

#1 10 years ago

I hope this qualifies for the tech discussion area. But with several games, just wait, I cannot run them without blue screens of death.

Certain Source engine games, Steam will not let me run saying I need a newer version of DirectX. I download from the Microsoft link provided but it still winds up not running. I cannot run Half-Life 2 or Episode One, but I can run Episode Two and Portal, surprisingly.

Now on other games, like Rainbow Six: Vegas, I can run quite well without a hitch. But there were one or two instances in which Vegas suddenly stopped and I got a blue screen of death.

And lastly, there is FEAR, which I would like to play. I got the demo, tried to play it but got crashes in several areas. During the introduction, I got a BSOD. But if I press something to skip the intro and go to the briefing, I can go a while through the briefing before the BSOD, somewhere where the leader starts suggesting me for the mission, and the other guy is skeptical about it. OR, I could try to skip that scene, press escape, and then click the skip dialogue sequence or whatever, and as I go to click yes, I get a BSOD.

Now whenever I go into DirectX Diagnosis it always says DirectX 9.0b. I figured the problem is because I need DirectX 9.0c. But on the BSOD, it says something about atiduag.3dl, or something like that. It is also mentioned in the error report, when the report cannot be found by Microsoft. So whenever I try to install the newer versions of DirectX 9.0c, either my PC does not recognize it, or it does not install right, or something else.

For general information: AMD Athlon XP 2400 2.0GHz Processor Visiontek Radeon HD 2600 PRO 512MB AGP 8x Card 2 GB of RAM (2x 1 GB sticks I believe) 380 Watt PSU by Antec

I currently am on the 8.1 drivers I think. I was switching between the 7.6 disc drivers, the 8.45 drivers at Visiontek, and the 8.1 drivers from ATI to see if this was helping the problem. It all had the same result. 8.1 has been working just fine except for the problems mentioned, such as the DX problem. I used the 8.1 hotfix for AGP cards that encounter screen flicker problems, something ATI did wrong many ATI releases ago.

Let me know if you guys come up with anything, thanks.




SteVen

"World's Best Boss"

50 XP

14th August 2004

0 Uploads

3,254 Posts

0 Threads

#2 10 years ago

Blue screens of death can be caused by many problems. Over-heating, Memory malfunctions, Driver issues, or even combinations of all or some of them. If newest ATI drivers and previous ATI drivers are not working for you I would try investigating over-heating. Does your PC have enough airflow going through it? Is the fan on your CPU or GPU possibly not spinning?




The Typer

Formerly justincase3

50 XP

20th June 2006

0 Uploads

1,120 Posts

0 Threads

#3 10 years ago

No, they spin. I don't think it is heat. Never had the problem before, I dust it out about every month. And my case keeps things pretty cool, an Antec case.

I think it's the drivers honestly because over-heating would come after certain amounts of time when I can go as long as I've ever gone (quite a long time) without any problems. Only problems are in games mentioned, I played through Bioshock without problems.




Guest

I didn't make it!

0 XP

 
#4 10 years ago

No, youre screwed if you have Directx9.0b.

The thing is, i had it and i tried to install programs that required it.

Fear requires:

· Windows® XP or 2000 with latest service pack installed · DirectX® 9.0c (April Edition) (included) · Pentium® 4 1.7 GHz or equivalent processor · 512 MB of RAM · 64 MB GeForce™ 4 Ti or ATI® Radeon® 9600 or equivalent with hardware T&L and pixel shader support · 5.0 GB free Hard Drive Space for installation · 4x CD-ROM drive (for Director's Edition, this will have to be DVD-ROM) · 16-bit DirectX® 9.0 compliant sound card with support for EAX™ 2.0 · Internet Connection Required · Mouse · Keyboard

(The space required arent the same as this is the real game and not demo, but rest ofthem are).

As you can see, i bolded the part that is impossible for you. I had it and i just couldnt install DirectX9.C as it wont let itself to reinstall itself. So the thing that i would suggest, is to reformat your computer with a Windows CD that has DirectX9.0C, as it is heavily required.

Im sorry to say it, but i think that it is the only solution. I tried in over a year to upgrade DirectX but it just did not work.




Bs|Archaon

I would die without GF

50 XP

15th March 2006

0 Uploads

5,910 Posts

0 Threads

#5 10 years ago

Having the wrong DirectX version should stop the game from running at worst; it shouldn't crash the computer.




The Typer

Formerly justincase3

50 XP

20th June 2006

0 Uploads

1,120 Posts

0 Threads

#6 10 years ago

Juggernut, you've had this problem before? I only got this when I installed the new drivers, I think. And yet, these drivers could be my only solution to get the games running. After a month of testing, they're the only ones to run everything.




Sgt. D. Pilla

Uber Geek

50 XP

23rd October 2007

0 Uploads

3,473 Posts

0 Threads

#7 10 years ago

Obviously im with Archaon here, 9.0B will not cause BSOD's just because its the wrong version. And I also disagree that its heat, heat is a rare issue for the most part Im going to go with either Memory Errors (Damaged Pin, Dirty Slot, cause's READ BSOD's) In this situation I have large amouts of doubt that it is anything to do with the ATI card, or its drivers, again, realisticaly, they shouldnt cause BSOD's (The Typical BSODS atleast).

Here's what I suggest, Force your system to BSOD again, but before you do that though, Turn OFF Automatic Restart on System Failure See how to turn off Automatic Restart.....

Spoiler: Show
Capture.JPG

After turning AR off, you can BSOD indefinate before the system restarts. Run FEAR again, get it to BSOD, and Record word for word what the BSOD says, Atleast the important parts such as the error codes, it should also say towards the start something that draws conclusion to what is causing the issue, for example, a RAM read error would be similar to "Read Allocation Error" or something like that, its been a while since I had one heh Doing this, and GETTING the error codes, even if it means taking a photo of the BSOD with a camera, then uploading it here for us to look at, makes it much easier to figure out the issue, and resolve it




The Typer

Formerly justincase3

50 XP

20th June 2006

0 Uploads

1,120 Posts

0 Threads

#8 10 years ago

Will doing this cause any harm to my hardware or software, just to be safe? Then I'll proceed with that and write it all down.




Guest

I didn't make it!

0 XP

 
#9 10 years ago

The thing is, DirectX9.0B might miss some things that are included in C, and when you come to a critical area where that thing is needed, you might get this error. For all sakes, i think that you should reformat anyway, because DirectX9.0C is needed for most of todays games.




Freyr VIP Member

A2Files Staff

46,875 XP

6th February 2005

11 Uploads

4,275 Posts

0 Threads

#10 10 years ago

By guess would be the ATI drivers. The filename of the DLL file quoted in the BSOD strongly suggests its an ATI driver file ( "atiduag.3dl" ) and your using an ATI card.

I did encounter a problem similar to this with a business machine last year. That was defiantly a driver problem and the only way of keeping the machine stable was to disable acceleration with the graphics card. On a desktop running word/excel thats not a problem. As your doing games its not going to be an option.

Personally I would try updating the ATI drivers before you do anything else. If this is to do with graphics drivers then while unlikely it is possible directx could have some effect on the problem.