6 réponses à ce sujet

[RaenImrahl]

Hi,

I may have come up with a workable solution for those of us who are having polygon/texture issues with Nvidia GeForce cards... I'd be interested if someone else would try this and see if they can duplicate success.

After heeding a lot of good advice on this forum about overheating, I did a pretty detailed cleaning of my case.  Alas, it did not solve the recent issue I was having with my GeForce GT 450 and massive graphical errors... which you can read about in the threads below:

http://social.biowar...8/index/88751/5
http://social.biowar...8/index/5562579

Anyway, I decided to play with the clocking on my graphics card.  The GT 450 (along with other problem cards, like the 8800 and 8600) come "factory overclocked".  So I downloaded Nvidia System Tools 6.06, and fiddled. 

Long story short... I found that *reducing* the GPU's Memory Clock (NOT the Core Clock) by about 20% solved the problem immediately!  I've played through for about an hour and also played through a few previously saved areas that were graphically intense... no spiky thingys!  I intend to put in a marathon session tonight to see if the results hold.

Why has this worked?  Frankly, I am a rank amatuer and have no idea.  I can only speculate that the problem comes from a disparity between my 2+ years-old CPU/RAM/Mobo and the new graphic card's DDR5 super Fermi whatsits.  DA seems very CPU intensive for graphics.

BTW... I am using the latest Nvidia driver (I have no choice with my card) and running the game at 1680x1050 with all of the in-game settings maxed (including vert sync).  I am getting about 30 fps for most play.

Hope this helps some of you who've been as frustrated as me with this long-standing problem.  Again, I'd be thrilled if someone wants to try and verify the results on their own system! 

Modifié par RaenImrahl, 29 décembre 2010 - 05:44 .

[RaenImrahl]

After four hours of intense game play last night, it appears this has worked, at least for me. No texture or weird polygon glitches.



It appears DA doesn't like some overclocked Nvidia cards, even those that are "factory overclocked" and have never been meddled with by their owners. Don't know why, don't really care. The game works great now!!

[Valethar]

After reading a reply in another thread, I've hopped over here to avoid clutter in that one... (No comments from the peanut gallery about Necroposts, a Mod made me do it )

As suggested, I adjusted the memory clock on my 465's. There was no change in the graphical anomalies mentioned. I ran the slider in Precision down to it's lowest setting of 1215, it's normally at 1620.

I even tried dropping the sliders down on the core and shader clocks along with the memory clock, all to the lowest settingr, and saw no changes.

There's are both factory stock EVGA GeForce GTX 465 Superclock (Fermi) cards. (www.newegg.com/Product/Product.aspx) that give me no issues in any other game, save DA:O/A.

I can't drop the memory clock any lower, even by manually entering a number in the field, so 1215 os as low as the sahder will go, at least with the Precision software.

Not really sure what else I can do to clear this up, save replacing hardware, which isn't an option in this economy.

I just find it odd that this is the only game that has any issues. Even older games, such as UT, Quake4, the first Crysis and Mass Effect games, all work flawlessly.  DAO, on the other hand, has a bad acid trip and becomes unplayable.

Modifié par Valethar, 01 mai 2011 - 05:06 .

[RaenImrahl]

Damn!  I hoped my magic bullet would also work for you....

Now, in the interest of full disclosure, had only one GTS450 when I tried this. By the time I added a second card in SLI configuration, I also had upgraded to a new CPU/Mobo/Ram. (In fact, I added the faster CPU *first* and ran the single card at factory overclock without problems).

As painful as this suggestion is... have you tried running this on just one card, underclocked, to see if the problem persists? Maybe just to test?

Also, are you running multiple displays?  If so, consider disabling one before launching the game. It *shouldn't* make a difference, but you never know....

Valethar wrote...

I just find it odd that this is the only game that has any issues. Even older games, such as UT, Quake4, the first Crysis and Mass Effect games, all work flawlessly.  DAO, on the other hand, has a bad acid trip and becomes unplayable.

Yeah, but the kick is that comparisons are iffy at best when it comes to DAO.  The Dragon Age games use their own engine, different from anything else, including other Bioware games like Mass Effect.  DAO is very CPU-piggish... my gut tells me it's still some sort of disparity between your CPU/RAM's processing power and the mega-graphic card array you're using.

One final thought... graphcis errors like you've reported can also be triggered by overheating.  Now, if this error is happening as soon as you start the game, then that's not likely.  Monitoring your cards' temps during gameplay would at least eliminate that variable.

RI

Modifié par RaenImrahl, 01 mai 2011 - 06:01 .

[Valethar]

I'll try disabling SLI as a test, just to see what happens. I know it's not overheating. Both cards start out at 70% fan, and are generally under 60 degrees C even at load.When the game starts, they're usually around 38-40C.

[CCanvas]

Hey guys! Here's an idea I'd recommend for anybody with problems that have been fixed by underclocking your GPU. This is targeted at anybody who has ever used any OC/monitoring programs like EVGA precision or MSI afterburner.

In safe mode uninstall your display drivers and sweep them as well (obvious) BUT before rebooting and reinstalling the drivers, uninstall any GPU OC software u have installed. Reboot into safe mode and reinstall your drivers, and after that boot into standard windows for the first time, use a registry cleaner like glary utilities and then reinstall your MSI afterburner or precision or whathav you.

Some guy once told me that apparently what can happen is that changes in the clock speeds can get mixed up in the registry or something and become stacked, so its possible that the card can be getting weird demands for the clock speed and cause it to do all kinds of silly things.
Now i dont know if that makes technical sense at all, but the fix worked for me on a ton of OC and stability related issue with my SLIed 580sc setup.

And RaenImrahl, If ur issues are being fixed by underclocking and this doesnt help you reach stock clockspeeds again, maybe RMA your card? all the factory OC cards are "guarenteed" to run stable at that clock speed. *shrug*

Good luck hope this helps!

[RaenImrahl]

CCanvas wrote...

And RaenImrahl, If ur issues are being fixed by underclocking and this doesnt help you reach stock clockspeeds again, maybe RMA your card? all the factory OC cards are "guarenteed" to run stable at that clock speed. *shrug*

Good luck hope this helps!

Thanks for the suggestion... in my case, I already had a rebuild in process, so I essentially built a new computer with a faster Mobo/CPU/RAM from the ground up, including a new Windows install.  So it probably had the same effect.

I don't recall if I had the Nvidia Ntune software installed at the time... it's outdated anyway, so anyone using it should probably follow your instructions and replace it with one of the programs you mentioned.

Best,

RI