View Full Version : Problem with ATI
Bahamut2218
3rd Jun 06, 3:15 AM
I had the problem that DoW would hang, so I installed the latest AGI catalyst driver (6.5). Now DoW runs smoothly exept for 1 thing. The screen keeps flimmers. It's like black dots and rektangles keep appearing on the screen. The game runs fine except for this. Maybe it isn't the Catalyst, but the orblem is driving me crazy. I experience this in other games, like Warcraft 3. If I could get some help it would be really nice.
PS. I cannot uninstall the driver, cause the the hole RADEON driver will dissapear.
Your Problem sounds like a burnt graphics card.
If your get artifacts you can be sure that your graphics card is somehow damaged, you also get those artifacts in other games, so it's not DoW specific
and it's called ATI =)
Bahamut2218
3rd Jun 06, 4:28 AM
Yeah yeah, sry for the misspelling.
Strangly, these artifacts doesn't appear in Winter Assault, so I'm wondering if it really is a grafic card damage. Adn these artifacts did not appear before i installed the ATI catalyst. But maybe you're right.
Let's see a warnings.log and dxdiag.txt please.
Bahamut2218
3rd Jun 06, 4:58 AM
12:41:21.53 W40K started at 2006-06-03 12:41
12:41:21.53 OS NT 5.1, 1023MB Physical Memory
12:41:21.53 RUN-OPTIONS
12:41:21.53 WORKING-DIR D:\Program\THQ\Dawn of War
12:41:21.53 USER Emanuel
12:41:21.53
12:41:24.98 MATHBOX -- Version=5, Cpu=INTEL Pentium-IV:f=15,m=3, Mode=SSE
12:41:24.98 FILESYSTEM -- filepath failure, path does not exist 'Engine\Locale\english\Data'
12:41:24.98 GAME -- Warning: Failed to map folder 'Engine\Locale\english\Data'.
12:41:24.98 GAME -- Warhammer, 1.41, Build 82463.63883
12:41:24.98 GAME -- Available memory: 1022MB RAM, 3946MB Pagefile
12:41:24.98 State::State - set socket send buffer to 131072
12:41:24.98 State::State - set socket receive buffer to 131072
12:41:24.98 HostState - 10.2.0.8:6112 / 10.2.0.8:6112
12:41:24.98 Session : Now Host
12:41:24.98 Session : We are now a Host
12:41:24.98 PeerState - 10.2.0.8:6112 / 10.2.0.8:6112
12:41:24.98 PeerState::ConnectCallbackHost - connecting to host at 255.255.255.255:6112
12:41:24.98 GSTransport::Connect - GT2AddressError
12:41:24.98 SPOOGE - Driver[Dx9 : Hardware TnL] on adapter[0], version[4,32]
12:41:24.98 SPDx9 -- Driver Name = ati2dvag.dll Device = \\.\DISPLAY1 (file://./DISPLAY1) Desc = RADEON X800 XT
12:41:24.98 SPDx9 -- Driver Vendor = 0x1002 Device = 0x5D57 SubSys = 0x03021002 Rev = 0x0000
12:41:24.98 SPDx9 -- Driver Version Product = 0x0006 Version = 0x000E SubVersion = 0x000A Build = 0x1992 (6546)
12:41:24.98 SPDx9 -- Driver GUID = {D7B71EE2-1E17-11CF-206A-0823A1C2CB35}
12:41:24.98 SPOOGE -- 489.00MB available texture memory
12:41:24.98 SPOOGE -- 489.00MB available texture memory
12:41:24.98 GAME -- Beginning FE
12:41:25.12 MOVIE -- Opening movie 'movies:relic_intro.lua'
12:41:29.23 MOVIE -- Closing movie 'movies:relic_intro.lua'
12:41:29.23 MOVIE -- Opening movie 'movies:dow_intro.lua'
12:41:29.59 MOVIE -- Closing movie 'movies:dow_intro.lua'
12:41:31.85 MOD -- Initializing Mod w40k, 1.0
12:41:31.85 MOD -- Warning: Failed to load archive 'W40k\W40kDataGOTY.sga'
12:41:31.85 MOD -- Warning: Failed to open folder 'W40k\Locale\english\Data'.
12:41:31.85 MOD -- Warning: Failed to open folder 'W40k\Data_Shared_Textures\Full'.
12:41:31.85 MOD -- Warning: Failed to open folder 'W40k\Data_Sound\Full'.
12:41:31.85 MOD -- Warning: Failed to open folder 'W40k\Data_Whm\High'.
12:41:31.85 GAME -- Warning: Campaign 'DATA:SCENARIOS\SP\DAWNOFWAR.CAMP': the section CampaingIntro is missing!
12:41:35.28 RENDER ANIM -- Art/UI/3D_Models/Campaign_Menu: Unable to open file!
12:41:35.28 Unable to load CampaignFrontendModels.lua!
12:41:35.28 GAME -- Using player profile Bahamut
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame0.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame1.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame10.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame11.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame12.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame13.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame14.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame15.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame16.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame2.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame3.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame4.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame5.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame6.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame7.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame8.sav', unsupported old file
12:41:52.90 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame9.sav', unsupported old file
12:41:55.26 APP -- Game Load
12:41:55.26 GAME -- Ending FE
12:41:55.26 GAME -- Beginning FE
12:41:55.35 APP -- Game Start
12:41:55.35 GAME -- Ending FE
12:41:55.35 GAME -- Beginning single player mission 'savegame25' (5 Computers)
12:41:55.35 GAME -- Initializing sync checking...
12:41:55.35 GAME -- Initializing FX Manager...
12:41:55.37 GAME -- Initializing Rendering Systems...
12:41:55.39 GAME -- Initializing NISLets...
12:41:55.43 GAME -- Initializing World Blueprints...
12:41:55.43 GAME -- Initializing Scene Graph...
12:41:55.43 GAME -- Initializing MOD systems...
12:42:00.07 GAME -- Initializing Session...
12:42:00.07 GAME -- Initializing Players...
12:42:00.14 GAME -- Initializing SCAR (Pre-Sim) systems...
12:42:00.20 GAME -- Initializing Team Colour Systems...
12:42:01.39 GAME -- Preloading all models...
12:42:01.95 GAME -- Applying Team Colours...
12:42:02.68 GAME -- Initializing UI...
12:42:02.68 GAME -- Initializing LUA...
12:42:02.70 GAME -- Initializing SCAR (Post SIM)...
12:42:11.84 GAME -- Precaching Events...
12:42:11.84 GAME -- Initializing Sim-Vis Handlers...
12:42:12.09 GAME -- Initializing AI...
12:42:12.09 GAME -- Initializing SCAR...
12:42:12.26 GAME -- Preparing Sim-Vis...
12:42:12.26 SIM -- Setting SyncErrorChecking level to Low
12:42:12.26 GAME -- Local player (Bahamut, 0) finished loading (67a76993) (17 seconds)
12:42:14.00 GAME -- Starting mission...
12:42:39.48 GAME -- SimulationController::Pause 0
12:42:47.06 GAME -- SimulationController::Pause 1
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame0.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame1.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame10.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame11.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame12.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame13.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame14.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame15.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame16.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame2.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame3.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame4.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame5.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame6.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame7.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame8.sav', unsupported old file
12:45:38.68 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame9.sav', unsupported old file
12:45:38.68 GAME - Autosave savegame26 complete.
12:47:37.98 GAME -- SimulationController::Pause 0
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame0.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame1.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame10.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame11.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame12.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame13.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame14.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame15.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame16.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame2.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame3.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame4.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame5.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame6.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame7.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame8.sav', unsupported old file
12:47:39.81 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame9.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame0.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame1.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame10.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame11.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame12.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame13.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame14.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame15.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame16.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame2.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame3.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame4.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame5.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame6.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame7.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame8.sav', unsupported old file
12:47:50.56 GAME -- (worldmanager) Failed to read header from scenario 'CAMPAIGN:savegame9.sav', unsupported old file
12:47:50.56 GAME -- SimulationController::Pause 1
12:47:51.71 GAME -- SimulationController::Pause 0
12:47:55.46 GAME -- SimulationController::Pause 1
12:47:55.46 GAME -- Ending mission (?)
12:47:55.46 GAME -- Resetting SIM...
12:47:55.46 MOD -- Shutting down Mod 'w40k'...
12:47:56.73 SPOOGE -- 489.00MB available texture memory
12:47:56.73 SPOOGE -- 489.00MB available texture memory
12:47:56.78
Application closed without errors
DxDiag won't save the txt, but in the program it says that no problem were detected.
What do you mean, it wont save the txt? What does it say when you try and save it?
Bahamut2218
3rd Jun 06, 10:43 AM
Well, I don't know. But it doesn't matter since that probably isn't the problem, right?
It could suggest that your directx install is corrupt...it certainly suggests that something is wrong.
Anyway, in your first post you say you cant uninstall your graphics drivers - you can, uninstall them completely and reboot then install them again.
Bahamut2218
3rd Jun 06, 11:29 AM
Well, I don't have the install disk for the grafics driver, and I don't wanna use another catalyst.
Sorringly, i cannot use system restore to undo the installation of the driver, cause it's to far away on the scheme.
you dont need an install disk for graphics card drivers - you should always use the latest ones from the manufacturer's website.
Bahamut2218
3rd Jun 06, 12:18 PM
But the latest one is The Catalyst 6.5 driver, the one that cause the flickering artifacts!
I didn't use the catalyst before, I just installed it because DoW said i needed to.
"Catalyst" is the name of the official drivers for ATI graphics cards, if you have an ATI card you must have been using some form of the catalyst drivers.
Bahamut2218
3rd Jun 06, 1:36 PM
Maybe, but then i must had something that worked...
Look, the most likely explanation is that the drivers didnt install properly - uninstall them completely and reinstall.
PS. I cannot uninstall the driver, cause the the hole RADEON driver will dissapear.
That's the deal with uninstalling drivers. There is also the Catalyst Cleaner on the ATI page.
Get rid of the drivers and reinstall them like TBS said.
Cldmani
4th Jun 06, 9:11 PM
If you don't like the official ATI Driver release, you try the OmegaDrivers. Basically, what it is, its modified catalyst driver files for a better performance and stability.
more info: http://www.omegadrivers.net/
Bahamut2218
4th Jun 06, 11:13 PM
I've tried the omega driver, and it didn't work. The screen couldn't show more than 4 colours and the resolution was as low as it could be.
What kind of graphics card do you have?
Druidika
5th Jun 06, 6:54 AM
According to his warnings.log, he has a Radeon X800 XT.
Bahamut2218
5th Jun 06, 6:55 AM
Absolutely right.
Interestingly, in his other thread (http://forums.relicnews.com/showthread.php?t=95252) the dxdiag shows a x300.
Bahamut2218
5th Jun 06, 9:21 AM
Maybe because that dxdiag came from another computer. Sry for that.
Why did you show a dxdiag from another computer? Thats not going to help us.
I still think its odd that you cant show the dxdiag from this computer - tell us exactly what error it gives when you try to.
Bahamut2218
6th Jun 06, 7:52 AM
Nah, Better close this thread. I'm gonna get some free support from Dell (Meaning new video card)
ok then, post back when you have your new card.
You may still have software issues that need sorting.
vBulletin v3.0.7, Copyright ©2000-2009, Jelsoft Enterprises Ltd.