Aller au contenu

Photo

[Fix] HD 3870 (No-Signal) crash. [stickie plox]


1 réponse à ce sujet

#1
Zethell

Zethell
  • Members
  • 127 messages
A Warning to all of you who needs this guide.
!CHECK YOUR WARRANTIES BEFORE CLOCKING YOUR CARD!
!CLOCKING THE CARD COULD REMOVE YOUR WARRANTY!


---

This is ONLY for HD 3870 cards.
If you have a HD 4000 series or HD 5000 series card with this problem, then underclocking it might work.
But i wouldnt know the Clock Values needed.

If a MOD sees this, then perhaps a stickie would be in order until the problem has been solved?

---

Zethell's Underclocking Guide.
HD 3870 cards ONLY

FIRST THING FIRST:
IF YOU'RE NOT SURE WHAT YOU'RE DOING.
THEN GET SOMEONE THAT KNOWS WHAT HE'S DOING TO HELP YOU.


PREPERATIONS:
1. Download Riva Tuner 2.2.4 2009. ( downloads.guru3d.com/RivaTuner-v2.24c-download-163.html )
2. Install Riva Tuner 2.2.4 2009.
3. Start Riva Tuner 2.2.4 2009.

4. Write down your default (current settings) Core & Memory clock values. (for manual clock reset)


Ok, lets get started!

UNDERCLOCKING GUIDE: Follow the steps carefully and in the right order.
1. In Riva Tuner, click the [Customize] button, right next to your graphics card, drop-down menu.
2. Click the [Low-Level system settings] button (looks like a graphics card, icon furthest to the left).
3. Check "Enable low-level hardware overclocking".
f.imagehost.org/0424/Riva1.jpg

4. Set Core clock to 740.0 (finetune with arrowkeys Left-Right)
5. Set Memory clock to 1100.0 (finetune with arrowkeys Left-Right)
OPTIONAL STEP. Check "Apply overclocking at Windows startup" to keep the clock from resetting after reboot.
f.imagehost.org/0411/Riva2.jpg

6. Click Apply then OK.
7. Click OK to close Riva tuner.

8. Start CCC and view overdrive to check that the card has been successfully underclocked.
9. Monitor the heat for a while in IDLE, if it stays around 60-63 or lower, then you're safe. Close CCC.
f.imagehost.org/0811/overdrive.jpg

CCC = Catalyst Control Center.

10. Start Dragon Age: Origins.
11. Go to the game graphics settings.
12. Un-Check "Play in Full-screen mode".
13. Un-Check Vertical Sync.
14Un-Check Frame-Buffer Effects.
15. Set Anti-Aliasing to off.
16. Set Desired Resolution, Graphics Detail and Texture Detail.
17. Apply the settings.

18. If you have a singlecore CPU, then you are done now. enjoy playing if it works.

----

For everyone with a DualCore CPU or QuadCore CPU, do this as well. (everytime you start the game)
1. Start Dragon Age: Origins.
2
. Start taskmanager (CTRL+ALT+DEL)
3. Right Click DAOrigins.exe and select "Set Affinity".
4. Un-check "All Processors"
5. Check ONLY CPU 0.
f.imagehost.org/0992/Affinity.jpg

Exit Task Manager & enjoy the game.


OTHER NOTES:
This is how i fixed this problem with my HD 3870 card, using the latest 9.12 drivers and Win7 Ultimate x86.

This might make the game more playable, but it MIGHT still crash now and then, so remember.
Press F5 to save, often..

Share this guide with everyone that has the problem.

* Removed hate, we all have it, but we dont need it.
* Added pictures to guide.

If the game still crashes, try lowering the "graphics detail".
If the fix works, or doesnt work for you, let me know by posting a response to this thread.

KNOWN BUGGED AREAS:
Ostegar (Works with Fix)
Korcari Wilds (Works with Fix)
Flemeth's Hut (Works with Fix)
Encounters on WorldMap (Works with Lower Graphics and this Fix)
Honnleath - The stone prisoner [DLC] (Area is too bugged, does not work with Fix or Lowest Graphics)

FIX STATS:
Fix worked for.. 4 people.
Fix didnt Work for.. 1 person.

SAD STORY:
This guide/fix proves that the problem lies with Dragon Age: Origins.
Problem is that the game isnt fully compatible with Multi-Core CPU's and the HD Radeon Cards.
It's such a shame that everyone has decided to play the "blamegame", even BioWare.

Modifié par Zethell, 12 janvier 2010 - 11:53 .


#2
Nathan Willis

Nathan Willis
  • BioWare Employees
  • 69 messages

Zethell wrote...

http://megagames.com...-graphics-cards

At least Blizzard admits it, BioWare should learn from them.


WE ADMIT NOTHING!!! RAARRRRRrr...

...but seriously, the problem that Blizzard was reporting is an interesting one and I've (prior to reading this thread) forwarded that along to the devs to make sure that our games don't suffer from something similar in the future or otherwise.

We have not encountered that particular problem in-house at all, even when the game has been left running (in some cases!) over the weekend on our menu screens, idling in-game, etcetera. Our systems primarily used for testing are pretty middle-of-the-road by today's standards, no aftermarket cooling, not top of the line...

As Gorath has alluded to, we don't really have control over specific system builds, cooling, whether or not your case is dusty, or in some cases of certain graphics card cooling solutions have failed... the list goes on and on. That doesn't mean that we don't make an honest effort to try and accomodate people with heat issues, of course. We want people to be able to play our game! I would hope that would go without saying. It's not like there's an evil man in charge of hardware testing that's all, "Hmm.. let's test every combination EXCEPT for these 5! Muahahah!".

What I can tell you is that the 3870 is one of the reference cards that we did test DA:O on prior to release, and we had no issues with it. I recognize that some people have had problems, and I've personally catalogued that among other issues to forward along to the nice devs that fix things like this -- but if the problem is solely hardware related (as it would seem to be, ESPECIALLY if a fix is to underclock your video card) then there's not much we can do.