Having Clock issues for 5870m for Asus G73Jh-rbbx05

I've had my Asus G73-rbbx05 for about a year and a half now and recently my 5870m won't down-clock itself back to 405/1000 after gaming or just non intensive such as basic web browsing. It's constantly staying at 700/1000 mhz. And it's gather temperatures really fast and is always around 77 C + for the GPU instead of 52 C when idle at the normal auto down-clock of 405/1000. I tested to see if my GPU overheats after playing BF3, but funny thing is that it stays cooler when running games than on idle with this clock sticking problem. It never goes past 77 + but instead hovers slightly cooler. When I log into windows, about a minute or so the GPU and the fan start up and get louder. My CPU seems fine with the range of about 45 C not on load.

This all started after I updated my AMD CCC driver from 12.6 to 13.1. I've tried reverting back to 12.6 and 12.1 but my clocks temporary down-clock but after a restart, it stays stuck again at 700/1000. I've tried using powerplay/activating and deactivating. Manually down-clocking my GPU to 405 barely has any affect on my temperature about 4 C difference. My Bios is 211 and I believe my vBios is v93 last time I checked. If anyone can help this would be great, cause I'm starting to get frustrated trying to figure this out. I'm a college student so I desperately need to make sure my notebook stays in shape not just for gaming but for school intensive purposes.

 

Try the latest 13.2 beta drivers. Maybe they help.

 

I've tried, still no solution. 5870m still starts up at 700mhz refuses to auto-downclock and fans continue on running.

 

What happens if you close all running programs, including the ones running in background?

 

1. Install hwinfo64 and look at fan RPM (under Asus G73 EC) at idle- it S/B ~ 2600 RPM. If you are using Asus power4gear remove it and try a standard windows power plan (I recommend balanced but even high perf. will clock down to 400/1000 at idle)
Also take a look at your clock settings with RBE - Radeon BIOS editor (this allow you to look at the settings in the BIOS file you loaded
2. Try AMD clock tool as a work around I know this version works download from Guru3D.com
3. Create a new user account and login with it for testing
4. You could also try a clean install http://forum.notebookreview.com/ali...st-11-2-mobility-released-get-yours-here.html see "how to setup" just substitute whatever version you prefer.

 

That happened to me after I installed Far Cry 3 strangely enough, Would be stuck on max clocks on bootup, and GPU usage was 90% when idle (that was before loading anything, including Far Cry 3). I fixed it by updating Far Cry 3 to the latest version, and then at the same time did a total clean install of latest catalyst. Weird as it seems the game seemed to stuff up the clocks on the card. Check GPU usage in HWinfo on boot, if it isn't on practically zero then something is clocking up the card in the background.

 

Uninstall the Catalyst drivers, and then run Sweeper after a reboot. Then install current. You have a bad install of the Catalyst.

 

Tried doing the sweeper after the reboot. Had no effect, the GPU is still running 699/1000 at 72 C idle temperatures.

 

Have you checked if there are any strange programs loading at startup? Worth checking your msconfig startup section. Same time as I did the reinstall I also recall removing a dodgy looking program that had mysteriously appeared there! What was the result with checking GPU usage with HWinfo32? If you have >1% GPU utilisation on bootup then might be a program running forcing clock up. When I had the problem my GPU utilisation was 90% right after bootup with nothing supposed to be using the card.

 

Also, check the Catalyst PowerPlay settings. Make sure PP is enabled. You can also use Preferences to restore Factory defaults.

 

It took me awhile, since I've been busy. But I think I actually was able to solve the clock sticking problem. I had to re install about 2 times for CC, and I enabled PP as you said. It's been about a week or so and everything has been normal so far. Thanks for the Help.