There's a post on it here; people are doing it with the CCC profiles.
-
-
Thanks mr cheese (Y)
Rep up. -
I am unable to set clocks lower than the half the original in CCC. if I do it just switches to default clocks, so the 300/300 guy should probably check if it is not a placebo effect..
Judging by the battery discharge rate, the voltage from ccc profile is not applied at all. If you have real wattmeter, prove me wrong.
EDIT
Also this ATI does the exact thing, that was p**ing me off on my old notebook - It throtles up core clocks, even on battery, when certain application are run. Well it seems theres quite improvement, this one does not throttle up on movie playback in MPCHC and throttles up only on startup of dosbox then goes down. Well we shall see when/if they fix powerplay
PS: "We will be releasing VBIOS for GX640 & GX740 owners soon." I would surely like to know their definition of "soon". -
Wha, thats not a problem, the GPU will throttle up for video, it will be to aid in the 2d clocks.
-
Yeah, I noticed the profiles seemed to have some trouble. I'm back to using the AMD GPU Clock tool to downclock to 200/300. Going lower than that doesn't save much power, and I had it crash once when I tried 50/75 for fun.
When I tried to use the CCC Profiles I couldn't get it to downclock to 200/300 easily so I didn't end up doing it that way. The voltage did seem to change according to the GPU Clock Tool, though.
PowerPlay definitely needs a lot of work. Above all, making it more configurable (and easily so) is in order. -
It wouldn't be a problem if this behaviour would be user definable. When I set 320Mhz I expect 320Mhz. You don't need more even for HD video and accelerated decoding and certainly you don't need halved <hour battery time when you have 100min movie. I like the i5... when I set max 50% in powerplan, then it stays on halved multiplier - on the other hand it seems it never goes 100% on battery.
EDIT +but as i said it isn't throtling up too frequently for my usual softvare codec and dosbox so meh...
Anyway clocking down to the CCC lowest(315/500) gives me nice 6C quite instantly( from 67 to 61 ), effectivly shifting temperature away from the switching point of the fan <- yipee. -
Switch to 100/150 with amd clock tool and you'll get other fan step down - to barely hearable.
-
Not in realtime for hardware it should be for a breeze and shouldnt need to clock up, but i find it does seem to throttle up even at the slightest which is strange,
Not sure really krooze, could be a deformed codec or something haha, although w7 has its own set that works quite nicely. -
Funny thing is that it applies overclocked clocks only on high load, and then returns to default when temperature goes too high(106C) (EDIT - with Overdrive). On default clocks it seems to drop frames to cool itself( my guess - I see more frequent gpu load drops in GPUZ while furmarking). It is simply oversmart for me, but I guess it is all good setting for common customers...
New beta VBIOS is available, but no changelog yet. Any labrats tried it already? -
Check the other thread. I think the guys over there are saying everythings just about fixed with it.
-
Oh, another new thread. golly!
-
Fixed wake up issues, and peoples vantage scores when overclocking have gone up (From what i read lol)
-
eh no need to be snotty, new threads for stuff like that are helpful. Putting them in a thread like this as the only source means it might get lost in the mud. Where a dedicated thread is more likely to be seen. And if clicking a virtual button is to hard for you to do perhap updating vbios's is to much.
-
The problem is that when there's so many threads, many of them will get relegated to the second or third page and so they'll lose a lot of visibility.
-
perhaps in other places but in this particular instance the info was literally one thing away. And we are all active enough that usually the important stuff like this stays on top.
-
Well it isn't hard, but it is unnecesserily hard... and I must add it to my watchlist too. And it isn't nice to search for new threads five times a day. I guess VBIOS is big enough thing to make a new thread... but it practicaly kills this thread, which already had big reading comunity.
But it certainly isn't oportunity to insult me(or anyone) Retto.(And FYI updating the BIOS seems now easy in comparsion to scanning for new threads).
Sorry for the OT guys but I consider this thread effectivly dead and duplicate of VBIOS thread, so I hope I have done no harm.
EDIT And I am not snotty, maybe snappy a little bit
. Also english is my 2nd language so not everything sound as I intend.
-
good msi
-
Maybe if you tried to be clear about what the problem is rather than just going on a rant with terrible spelling someone could help you with it?
-
Just noticed that you're another one of those users who comes on to post a complaint about a particular brand because you're having problems with it. Please post your issue before recommending against a brand--that's ignorant/biased. Plus, I'm sure someone in this thread can help ya
Good luck. -
yes i fix my problem.. now evrything is perfect hehe..
GX640 PCI-E x16 @ x1 problem and other driver problems
Discussion in 'MSI' started by buff-daddy, Apr 16, 2010.