Jump to content

Ati Card Solid Color Screens/lockups/game Crashes


18 replies to this topic

#1 scgt1

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 291 posts
  • Facebook: Link
  • LocationArlington, TX

Posted 24 January 2013 - 05:07 AM

Something I may have discovered somewhat on accident is (so far anyway) MWO Doesn't like anything newer then Catalyst 12.11 Beta.

Just prior to patch I went from 12.11 B to 13.1 WHQL Had the above mentioned problems. Went newer with 13.2 B still same thing. So today I went back to 12.11 B and haven't had any problems since.

Just had my first black screen then back to client during a match on the 12.11 B drivers. So the drivers aren't the cause its the game itself. Come on PGI. Either put in a hot fix to fix the problem or take out the DC fix you put in so we get credit for what we kill.

Yesterday I had a wild hair and clicked the Default tab in the Catalyst Control for the 3d settings. I was playing MWO the rest of the day and night fine and have had a few matches this morning also.

Mind you I never did anything in the CCC so who knows but the Black screens and solid color screens have stopped for me now. May give it a try.

In client I have 1920x1080
full
Everything up and Vsync on

Again with all CCC on default.

Edited by scgt1, 25 January 2013 - 05:21 AM.


#2 MechGorilla

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 33 posts
  • LocationFishers, Indiana, USA

Posted 24 January 2013 - 06:31 AM

View Postscgt1, on 24 January 2013 - 05:07 AM, said:

Something I may have discovered somewhat on accident is (so far anyway) MWO Doesn't like anything newer then Catalyst 12.11 Beta.

Just prior to patch I went from 12.11 B to 13.1 WHQL Had the above mentioned problems. Went newer with 13.2 B still same thing. So today I went back to 12.11 B and haven't had any problems since.


I had the exact same problem that you were describing (in the patch feedback stability thread), and like you I was using 12.11B, then went to 13.1 when it released. I have never had any problems with MWO crashing until this patch. I will try going back to 12.11B when I get home from work to see if this solves the problem for me.

I also have a support ticket open (via email) with PGI, so I'll let you know if anything comes from that.

#3 ElliottHD

    Member

  • PipPipPip
  • The 1 Percent
  • The 1 Percent
  • 86 posts
  • LocationPhiladelphia, PA

Posted 24 January 2013 - 06:52 AM

The bug occurs with Anti Aliasing enabled on both the card and in the program. If you turn the card controlled Anti Aliasing off and let the program control it, or vise versa, this should fix the problem. I gaurantee nothing, but switching the Anti Aliasing off in the game and setting Catalyst to override application settings letting the card control all Anti Aliasing operations really seamed to fix 99.9% of these problems for me.

AMD Radeon 6950 2GB Factory OCed.

#4 MechGorilla

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 33 posts
  • LocationFishers, Indiana, USA

Posted 24 January 2013 - 07:15 AM

View PostElliottHD, on 24 January 2013 - 06:52 AM, said:

The bug occurs with Anti Aliasing enabled on both the card and in the program. If you turn the card controlled Anti Aliasing off and let the program control it, or vise versa, this should fix the problem. I gaurantee nothing, but switching the Anti Aliasing off in the game and setting Catalyst to override application settings letting the card control all Anti Aliasing operations really seamed to fix 99.9% of these problems for me.

AMD Radeon 6950 2GB Factory OCed.


I have the following settings: (in AMDCC)
Anti-Aliasing Mode: Use Application Settings
Anti-Aliasing Samples: Use Application Settings
Filter: Standard
Anti-Aliasing Method: Multisampling
Mophological Filtering: Off

I do have AA turned on in game, so mabe just turning it off in game might help? I can't test this for about another 8 hours or so, when I get home from work.

#5 ElliottHD

    Member

  • PipPipPip
  • The 1 Percent
  • The 1 Percent
  • 86 posts
  • LocationPhiladelphia, PA

Posted 24 January 2013 - 07:51 AM

Maybe MechGorilla. I went the opposite of letting the game control my AA settings and it cleared the problem up with the exception of slight pop in textures when tracking heavily in either direction in a skirmish. I was told that doing one OR the other should work by a corp mate, but it was easier for me to just turn off AA in game since I already had AMDCC setup for gaming applications. I can't give you exact setting right now since I'm at work. I can edit this post later with my AMDCC settings.

Also note, this did not in anyway effect my frame rates. They are still between 45 and 50fps dropping to 25 to 30 during a firefight. Caustic Valley still provides the best performance for me with an overall match average of 45fps, running at almost 80fps if I have no other mech's in view while moving, and only ever dipping below 30fps during heavy fighting while multiple mechs are withing view. This was standard fair previously for me, with exception of constant texture load failures.

All game settings are High, AA off. Motion Blur low, V-Sync off.

EDIT:

AMDCC Settings

AA: Override Application Settings
AA 4XEQ
Antroscopic Filtering 16X
Tessellation AMD Optimized
Catalyst A.I. High Quality
Wait for V-Sync Performance
AA Mode Quality

Edited by ElliottHD, 24 January 2013 - 08:43 AM.


#6 MechGorilla

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 33 posts
  • LocationFishers, Indiana, USA

Posted 24 January 2013 - 04:07 PM

I just tried a match with the game on lowest settings (so AA was completely off), same problem. I'm working with support to try a few different things, so I'm going to see how that plays out before I try going back to the 12.11 beta drivers. I would rather help PGI figure out the root problem (and presumably get that out into a patch).

EDIT:

Changed the settings in the CCC to override the game settings, made it thru one whole match! Second match, made it about 5 mins and blam crashed again.

Edited by MechGorilla, 24 January 2013 - 04:24 PM.


#7 ElliottHD

    Member

  • PipPipPip
  • The 1 Percent
  • The 1 Percent
  • 86 posts
  • LocationPhiladelphia, PA

Posted 25 January 2013 - 04:58 AM

I don't know then. Maybe we have similar, but different issues? Unfortuanetly I only have three computers to test against. Yours, mine, and my corp mates. And two of the three had the above fix work for them. I have to assume that these issues are maybe stemmed from the same bug, but are actually two different bugs in reality. Or, they are the same bug, but there is some setting within the Catalyst drivers that is different between the two of us that is cause the game to continue to hang for you.

Then there is always the issue of, did the game crash because of your video drivers, or did your game crash because of some other crash to desktop bug?

I'm not using AMD Overdrive on the card at all. It's a factory OCed card, so I can't find a justifiable reasont o push it further. And all that adds is instability to the mix.

#8 scgt1

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 291 posts
  • Facebook: Link
  • LocationArlington, TX

Posted 25 January 2013 - 05:21 AM

Check my first post I've updated information which has fixed it for me. Go figure.

#9 MechGorilla

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 33 posts
  • LocationFishers, Indiana, USA

Posted 25 January 2013 - 03:02 PM

No luck so far, if I override the application settings in the CCC the graphics are seriously messed up. Everything is semi-transparent and inverted.

Support has had me download some different pak files too, but so far nothing has fixed it for me.

scgt1 - Did you go back to 13.1 or are you still on 12.11 beta?

#10 scgt1

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 291 posts
  • Facebook: Link
  • LocationArlington, TX

Posted 25 January 2013 - 03:10 PM

View PostMechGorilla, on 25 January 2013 - 03:02 PM, said:

No luck so far, if I override the application settings in the CCC the graphics are seriously messed up. Everything is semi-transparent and inverted.

Support has had me download some different pak files too, but so far nothing has fixed it for me.

scgt1 - Did you go back to 13.1 or are you still on 12.11 beta?

completely removed all catalyst drivers and such
rebooted
reinstalled 12.11 B
Rebooted
Ran game
****
went into ccc
Clicked the default tab under the 3d settings
Started game
Been playing since.......

Beats me I'm lucky I guess.

#11 scgt1

    Member

  • PipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 291 posts
  • Facebook: Link
  • LocationArlington, TX

Posted 25 January 2013 - 10:14 PM

Just had the Black screen after a few minutes in game and back to client. So dropped another match the same thing only right after the power up. Got black screen with and error finally...

Problem signature:
Problem Event Name: APPCRASH
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 50fdabac
Fault Module Name: CryRenderD3D9.DLL
Fault Module Version: 3.4.1.4418
Fault Module Timestamp: 50fdab29
Exception Code: c0000005
Exception Offset: 001192f4
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Edited by scgt1, 25 January 2013 - 10:15 PM.


#12 MechGorilla

    Member

  • PipPip
  • Legendary Founder
  • Legendary Founder
  • 33 posts
  • LocationFishers, Indiana, USA

Posted 26 January 2013 - 05:29 AM

Going into the weekend completely unable to play, not sure if I'll get more support (from support) over the weekend or not.

Guess I'll roll back to 12.11 or maybe 12.10 and see if that helps.

Update

Rolled drivers back to 12.11, played one match actually made it almost all the way to the end. Just before the last mech died (and the round was over), BLAM - Black screen and kicked out to the lab. ;)

Edited by MechGorilla, 26 January 2013 - 05:58 AM.


#13 shotokan5

    Member

  • PipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 550 posts
  • Google+: Link
  • Locationvirginia

Posted 04 February 2013 - 07:15 AM

Did this begin after the last patch?

#14 Ursus Prime

    Rookie

  • 3 posts
  • LocationLas Vegas, NV

Posted 05 February 2013 - 07:29 PM

View Postshotokan5, on 04 February 2013 - 07:15 AM, said:

Did this begin after the last patch?

I had this issue start on me since the last patch, i am unable to render the map details fully. I haven't crashed yet or had a black screen. I did reset my CCP to default settings and was able to render about 90% of the map. Hope this get fixed soon.

#15 Julian Tifflor

    Member

  • PipPipPip
  • 63 posts

Posted 07 February 2013 - 05:08 PM

the black screen thing is known...even on nvidia systems...like my friend has...game starts...and if he doesnt get the black screen the first seconds it will run fine.

after this patch i got issues myself with 13.1 from amd...before the patch i had not even one crash for the time the last patch was up. i crashed and did freeze in 2 games of around 20....but caustic valley where i got freezes for like 2-4 seconds a lot...they disappeared. so it got faster...but unstable.

sadly yesterday i switched to nvidia so cant test anymore for amd.

#16 Megrimm

    Rookie

  • 5 posts

Posted 09 February 2013 - 04:47 AM

Never had graphical problems and always update to the newest drivers, even beta drivers. Game runs perfectly on a 6870.

#17 F lan Ker

    Member

  • PipPipPipPipPipPipPip
  • 827 posts
  • LocationArctic Circle

Posted 11 February 2013 - 01:57 PM

S!

The funny thing is that that the latest patch boosted my FPS significantly. For example on River City when looking at the Citadel I got usually 45fps or so, now I am going over 80fps! And running 1920x1080 with Very High except Motion Blur OFF, AA Off and PArticles High. But then comes this freezing spoiling it all :(

#18 Corrado

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 817 posts
  • Locationfinale emilia, italy

Posted 11 February 2013 - 11:01 PM

on my main rig, i had to reinstall windows since i swapped the raid0 from the marvell to the intel controller.

i had the 12.1B before (HD 6970) and i experienced occasional CTDs every 15-20 matches. after i reinstalled windows7, i installed the latest catalysts 13.1 WHQL 64bit and the game runs fine.

only things i have in my config file:

i_mouse_inertia = 0
i_mouse_smooth = 0
i_mouse_accel = 0
i_mouse_accel_max = 0
cl_fov = 75
gp_omicron_allow_c3voip = 0
gp_mech_view_zoom_transitiontime = 0.05
r_DepthOfField = 0
r_HDRBloomMul = 0.4
r_HDRBrightOffset = 10
r_HDRBrightThreshold = 6
r_HDRGrainAmount = 0
r_EyeAdaptationBase = 0.1
r_EyeAdaptationSpeed = 0.5
r_HDREyeAdaptionCache = 10


medium details, high object details (for view range) and AA off.

#19 Corvus Antaka

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Knight Errant
  • Knight Errant
  • 8,310 posts
  • Twitch: Link
  • LocationInner Sphere

Posted 13 February 2013 - 03:09 PM

13.4 beta is working awesome for me.





5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users