A strange display error?

[CSpannerz]

Hey guys, first time posting on these forums but not my first time on Nexus. I have a feeling the issue may be related to my GFX card, the MSi AMD HD6770. I have looked everywhere online, alas it seems I may be the only person to ever have this issue.

 

PC Specs:

AMD Phenom II - 3.2GHZ x6 (1090t Black edition)

Corsair 4GB memory

Thermaltake 430W PSU

MSi AMD HD6770

Silencio 550 Case

Apple cinema display

Everything else is irrelevant.

 

http://www.youtube.com/watch?v=q0UUirmliiA&feature=youtube_gdata

(Apologies if linking to Youtube isn't allowed, but you really do have to see the problem...) (Also my voice sounds like s--t because I am sick)

 

This issue occurs on both stock clock (800mhz), Overclock (up to 950mhz and everywhere inbetween) and underclock (<800mhz)

I doubt it's a graphics card bug as I ran Furmark maxed-out overnight and card proved stable even at 950mhz. Memory and CPU are not overclocked, neither is RAM. Everything stock. Can't be a power issue - recommended I believe is a 500W PSU but I have a 430W Thermaltake. I tried my friend's generic 700W PSU and alas same issue, and I tried my PSU in his computer (GTX590) and FO3 ran fine. So power is not an issue here... I've even taken it back to the store and it was tested, 0 memory faults/issues etc.

 

The only issues out of 20 of the games installed on my PC is MCEditor (which does precisely the same thing), and Crysis 1's Editor (which every 20 minutes crashes the display driver and I have to restart the application) - Other than that everything runs a-okay...

 

Does anyone have any ideas or suggestions, or am I forever haunted with 5 minutes FO3 Gameplay each day?

Thanks...

~Julian

[CSpannerz]

*bump*

 

Also, it seems to be at it's worst when NOT overclocked... at 830mhz (default 800mhz) clockspeed and 1200mhz (default 1100mhz) memory speed, it seems to be -less- problematic... But still there. :confused: Any ideas...?

 

I really, really want to sort this issue out. FO3 is probably mu #1 played game.

(Also, Crysis Editor didn't crash ONCE all day when non-overclocked)

 

*EDIT*

 

Okay guys, I seem to have fixed it by doing all (trying one at at a time didn't work but all together they did);

1-Run it windowed. it doesn't seem to matter what resolution, I'm running it windowed at my screen's resolution and it's running fine. Fullscreen, s--t hits the fan.

2-Antialiasing - seems to work wether this is on or off. I keep it off (Not just performance, just a preference)

3-Run a high Anisotropy level (trust me on this)

4-HDR/Bloom. Results may vary but I found it tore a little less fullscreen with HDR disabled. Might just be a driver issue.

Edited June 5, 2012 by CSpannerz

[BlackRampage]

and Crysis 1's Editor (which every 20 minutes crashes the display driver and I have to restart the application)

Is your operating system 32 or 64 bit? The Crysis editor isn't meant to be run on a 32 OS. (yes, I once had the same problem)

 

1-Run it windowed. it doesn't seem to matter what resolution, I'm running it windowed at my screen's resolution and it's running fine. Fullscreen, s--t hits the fan.

Hmm. There's an interesting little mod that might help with that: Fake Fullscreen Mode Windowed (no guarantees of course)

 

Related to that and the earlier mentioned Crysis sandbox editor problem: Did you update your graphics card drivers to the latest version? (yes, of course you did, but one can never be too certain)

And, if you have multiple graphics cards, did you try disabling SLI/Crossfire? (so your graphics run on 1 card instead of 2 or more)

 

Also, try running a memory test on your RAM / swapping your RAM modules with others if you have any spares. Could be that one of the RAM modules is faulty.

[CSpannerz]

and Crysis 1's Editor (which every 20 minutes crashes the display driver and I have to restart the application)

Is your operating system 32 or 64 bit? The Crysis editor isn't meant to be run on a 32 OS. (yes, I once had the same problem)

 

1-Run it windowed. it doesn't seem to matter what resolution, I'm running it windowed at my screen's resolution and it's running fine. Fullscreen, s--t hits the fan.

Hmm. There's an interesting little mod that might help with that: Fake Fullscreen Mode Windowed (no guarantees of course)

 

Related to that and the earlier mentioned Crysis sandbox editor problem: Did you update your graphics card drivers to the latest version? (yes, of course you did, but one can never be too certain)

And, if you have multiple graphics cards, did you try disabling SLI/Crossfire? (so your graphics run on 1 card instead of 2 or more)

 

Also, try running a memory test on your RAM / swapping your RAM modules with others if you have any spares. Could be that one of the RAM modules is faulty.

 

64-bit, Win7 Ultimate. I had many issues with 32-bit Editor myself, so I went to x64. My Core 2 Quad at the time just died on x64, so I went to AMD. (Being the poor student, haha)

 

Updated to the definite absolute latest drivers, and I only sport one GFX card (All I really need, haha).

Thanks for the link to the mod BTW, Mega kudos to you - running FO3 'windowed' at my native resolution (which usually cut the bottom bit off the game thanks to the border/taskbar) and then using the Mod actually seemed to have fixed it :D Thanks!