you not looking in the right places then
that quote i added up above is from an answer to the exact same question i asked over the new year
moment of maddness, it happens from time to time
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
The bullet has been bitten [2nd 6950]
- Thread starter 413x
- Start date
you not looking in the right places then
that quote i added up above is from an answer to the exact same question i asked over the new year
moment of maddness, it happens from time to time
Soldato
Associate
wow, you joined in January and almost 1000 post already
It's only about 3 posts a day lol
, not that i have much right to say this *looks at post count* .... *looks at join date*It's only about 3 posts a day lol
He must have thought January 2011.
Doh!.
Soldato
al4x, When did gpu observer start working with 69 series? It wouldn't work for me. I just found 3.7, is that the one your using? I'm at work so I can't try it yet
.
.yeah ive changed registry before,
like before the main bits im unfamiliar with is bios stuff and overclocking [as well as being over cautious cause one wrong figure followed by 'enter' ruined hardware]
id like to say thanks to all the people who have helped me out with this in this thread.
also as far as i know thats the last thing i have to mess with to achieve this
like before the main bits im unfamiliar with is bios stuff and overclocking [as well as being over cautious cause one wrong figure followed by 'enter' ruined hardware]
id like to say thanks to all the people who have helped me out with this in this thread.
also as far as i know thats the last thing i have to mess with to achieve this
Last edited:
Soldato
al4x: In afterburner config (the same one that's in your screen shot above) you should add this to it
Last edited:
Soldato
If your happy with 6 then cool, but iirc powerplay only works on 7.2.
Associate
- Joined
- 6 Dec 2010
- Posts
- 703
Close, it's 2.1.0 Beta 7
But yes, you should use it because, as tommybhoy said, it is the first version that powerpaly works with.
Haven't you noticed your cards don't downclock automatically.
ok if powerplay doesnt work im using beta 7
have applied the fix and its all working now, the BSODs no no longer happen, everything in afterburner works
im clocking each card in non crossfire mode as yet as i dont know if you can do it with crossfire enabled, [im guessing you can]
i knew the g15 mini lcd display would come in handy for something.. amd its displaying the stats of each card [V,clock,temps]
i guess apart form the crossfire or not when OCing thats this done!
thanks to everyone for walking me through this, i expect ive tried your patience at some points!
have applied the fix and its all working now, the BSODs no no longer happen, everything in afterburner works
im clocking each card in non crossfire mode as yet as i dont know if you can do it with crossfire enabled, [im guessing you can]
i knew the g15 mini lcd display would come in handy for something.. amd its displaying the stats of each card [V,clock,temps]
i guess apart form the crossfire or not when OCing thats this done!
thanks to everyone for walking me through this, i expect ive tried your patience at some points!
Sometimes I think this has not been worth it
Now msi boots at start up but one of the 2 cards goes to 100% gpu usage,(that's what msi is reporting along with temp increase)
I then load gpu z and it drops back to zero like it should but card one doesn't then click any higher that stock 810 and 1200
Driving me mad.. I don't want to have to boot gpu z every time I load the pc
to elaborate further..
with CF enabled
Card one will not go above stock 1.0mV, and stock clocks, soon as i click apply in AB it just defaults back
card 2 will but sticks at 100% GPU until gpu Z is activated
with the above opening a 3D app .. ie a game.. card 1 jumps only to 810/1250 but card 2 does show what i request including voltage
im going to try with CF disabled tomorrow, otherwise im just gonna sell the second 6950 and wait for a better single card from amd later in the 7xxx series
[tried something else, now card 2 will not clock but card 1 will, and without CF i cant get AB to work at all, clocks are set at 0/0 no matter what i do]
Now msi boots at start up but one of the 2 cards goes to 100% gpu usage,(that's what msi is reporting along with temp increase)
I then load gpu z and it drops back to zero like it should but card one doesn't then click any higher that stock 810 and 1200
Driving me mad.. I don't want to have to boot gpu z every time I load the pc
to elaborate further..
with CF enabled
Card one will not go above stock 1.0mV, and stock clocks, soon as i click apply in AB it just defaults back
card 2 will but sticks at 100% GPU until gpu Z is activated
with the above opening a 3D app .. ie a game.. card 1 jumps only to 810/1250 but card 2 does show what i request including voltage
im going to try with CF disabled tomorrow, otherwise im just gonna sell the second 6950 and wait for a better single card from amd later in the 7xxx series
[tried something else, now card 2 will not clock but card 1 will, and without CF i cant get AB to work at all, clocks are set at 0/0 no matter what i do]
Last edited: