Sajin

DENTNU

BioHazardSperm

disabled K-Boost and shut down Precision(set to not start with windows) and rebooted then installed new driver?

Well I just tested out your method and still having the same problem its strange because if I go back to driver 314.07 or older the downclocking fix works perfectly. Any newer driver seems to be having issues with this fix I wish someone could give it a try and post back if they are having the same problem as me. Till this issue gets sorted out guess I will have to keep moving my slider up or down when I boot my pc so i can fix the clock problem.  

No problems here & I'm running 3-way titans. You may need to uninstall precision x (select "NO" to saving profile data when asked, reboot machine, re-install precision x, disable sli, enable kboost & reboot, enable sli.) to correct your problem. 

 
Thanks for the reply will give that a try later on its good to know that its not a driver problem.
 
Update 1: Nope still having the same issue you sure that when you boot up your machine and click the force constant boost your cards clocks are hitting your set overclock settings ? What version of windows are you running ?  

DENTNU

Sajin

DENTNU

BioHazardSperm

disabled K-Boost and shut down Precision(set to not start with windows) and rebooted then installed new driver?

Well I just tested out your method and still having the same problem its strange because if I go back to driver 314.07 or older the downclocking fix works perfectly. Any newer driver seems to be having issues with this fix I wish someone could give it a try and post back if they are having the same problem as me. Till this issue gets sorted out guess I will have to keep moving my slider up or down when I boot my pc so i can fix the clock problem.  

No problems here & I'm running 3-way titans. You may need to uninstall precision x (select "NO" to saving profile data when asked, reboot machine, re-install precision x, disable sli, enable kboost & reboot, enable sli.) to correct your problem. 

Thanks for the reply will give that a try later on its good to know that its not a driver problem.

Update 1: Nope still having the same issue you sure that when you boot up your machine and click the force constant boost your cards clocks are hitting your set overclock settings ? What version of windows are you running ?  

Yep, everything is working correctly on my end. I'm running Windows 7 Home Premium 64-bit. Glad you got it fixed.

Duarian

Can't seem to get this to work for my 680 >.<.

Followed directions exactly..trying to do it with an oc of +100 core/+595 memory with 131% power target. With K-boost the card does run at non-boost stocks constantly (until I load a 3d Application), but the card still throttles down when it hits 70 degrees C. Not at home right now but I figured i'd post and see if anyone still pays attention to this thread that could offer some assistance :-)

The card is suppose to throttle down 13MHz at 70, 80 & 90C. What do your clocks hold before it hits 70C?

Duarian

Well I feel stupid. It does only throttle down 13 MHz at 70 degrees C.

I guess I thought that's what this fix was for, but I probably misinterpreted the original post.

This guide was originally created to correct throttling under 70C. It seems to no longer work as NVIDIA has changed something in their drivers which cause 670's & 680's to throttle down while running 3dmark11 even when under the 70C mark, I experienced this myself when I had my 680, a friend of mine also experienced this. The only way to correct the problem is to use this guide a long with forcing prefer maximum performance under the NVCP and a custom BIOS flash.

Hey man been using for for awhile still and 0 problems so i just got a question for ya, the new drivers look pretty tastey and i plan on updating soon as Skyrim modder updates his ENB .dll to be compatible with the new driver. Question is, do i just follow same procedure on new drivers on ur guide on first page? Just double checking

Ya be meaning to get back to ya..i actually sold my 680, 780 finally just arrived today, is this method still safe and all to use with the 780s or dont work correctly?

I've just replaced my trusty 2 year-old EVGA GTS 450 with an EVGA GTX 660 3GB Superclocked+ (P/N: 03G-P4-2666-KR), only to find out that my frame rates in some spots in the game Wolfenstein: Enemy Territory (and a few other 3D applications) actually got lower. I then noticed on EVGA Precision X v4.2.1.2143 that while the game was running the GPU was clocked at only ~700-800 MHz and the actual power used hovered around 50%. Temps never got higher than 60 celsius at load so that was not the issue.

Knowing this was due to the fact that Wolf:ET is an old game and, most importantly, that NVIDIA's 600 series are plagued by the wretched GPU boost "feature", I tried using the K-Boost feature on Precision X to stop the card from downclocking. Unfortunately, it had no effect whatsoever, not even after restarting the computer (which should not be necessary with that version).

So a few hours ago I wrote EVGA's support asking about it and they just sent me the following reply:

Hello

Unfortunately the developer of this software has announced that he has no plans to provide 64 bit support at this time. Once the demand for this type of software is needed it will be developed. However at this time it is felt that EVGA Precision will be 32 bit only at this time. I sincerely apologize for any inconvenience this matter has caused.
Regards
 
EVGA

I found the answer confusing at least, because setting the power target, setting the GPU and the memory clock offsets, saving profiles, etc., works just fine (I'm on XP 64). Maybe the person who replied was referring to the RivaTuner Statistic Server, which only works on 32-bit OS's? And if he was, is K-Boost linked to RTSS and so unavailable for people on 64-bit OS's? I find this quite strange because I'm pretty sure I've seen quite a few posts by people using K-Boost and 64-bit OS's.

eternitykh
try to set the game's profile to use "Prefer Maximum Performance"

Thank you for taking the time to reply. However, that option has only been implemented on NVIDIA drivers for VistaTrash and later Microsoft's dumbed-down-bloated-NSA-friendly so-called "operating systems" like 7Garbage and the 8th Abomination. Anyways, does that mean then that K-Boost is linked to that driver option and won't work without it?

eternitykh
unfortunately i do not have any experience with precision x nor k-boost under windows XP environment, it works fine for me in win7 x64.
maybe someone else can shed some light on this matter.

Thanks a lot anyway, and I apologize if I sounded a little rude in my reply to you. For well over 5 years I've been buying exclusively EVGA graphics cards, and the EVGA support representative I've been exchanging messages with about this issue is completely clueless, so I'm feeling really let down by the company. I'll continue buying EVGA products because of their great quality overall, but my impression of the support offered by the company to its customers has plummeted.

FF beta or reg versions? i run dual screens and it happens once in awhile but nothing that doesn't settle back after sometime .FF is now GPU accelerated i believe ,try un-checking  this in  FF settings (see pic) ,should solve it if it is such a issue,mine goes back to 324 then back up sometimes while browsing

Slider6996
Well sad to say after updating to latest drivers, i cant no longer get this trick to work :/ i followed same steps as i always did, im on a fresh install of windows and installed latest drivers for first time and put inspector where it was suppose to go, dragged out my backup of my force idle and force constant.bat files, enabled kboost and all. Hit downclock and i get weird colors all overlapping screen and have to do a hard reset :/ little sad to be honest lol, ive been using this method for months. Reason is on firefox is my gpu will go up to 900mhz when it dont even need to. So maybe something im missing or not doing right?

You get weird colors all over your screen when you use force idle? Is this inside FF? 

I think I may know what the issue is... the power states aka p-states on the video card could have changed due to the newer driver. To check and make sure you have the proper p-state set inside the idle.bat simply open nvidia inspector, locate the show overclocking tab (at the bottom right) and click on it, the overclocking window will pop open, you should now see a drop down menu that says "performance level [2] - (P0)" or similar, open the menu and find the correct p-state for your card, you want the p-state that reads 324MHz, the current p-state that is set inside the idle.bat is P8 aka 0,8. Edit the idle.bat to the correct p-state.

Slider6996

Sajin
I think I may know what the issue is... the power states aka p-states on the video card could have changed due to the newer driver. To check and make sure you have the proper p-state set inside the idle.bat simply open nvidia inspector, locate the show overclocking tab (at the bottom right) and click on it, the overclocking window will pop open, you should now see a drop down menu that says "performance level [2] - (P0)" or similar, open the menu and find the correct p-state for your card, you want the p-state that reads 324MHz, the current p-state that is set inside the idle.bat is P8 aka 0,8. Edit the idle.bat to the correct p-state.

 
Ya i had thought it might be something related to that but just didnt know what to look for, u gave spot on instructions and followed/test and i still got the weird colors, did the voltage max increase with new drivers too cuz i know the voltage settings has to be spot on too but from what i could tell it does match. Below ill list what my .bats show.
 
Idle.bat > "C:\Program Files (x86)\nvidiainspector\nvidiaInspector.exe" -forcepstate:0,8
 
Boost.bat > "C:\Program Files (x86)\nvidiainspector\nvidiaInspector.exe" -forcepstate:0,16 -setVoltageOffset:0,0,162500
 
 
In Nvidia Inspecter i have the top P0 option selected and my voltage shows +3.75 Mv when maxed to the right and 1162.5 Mv in the little box to top left of the slider.
In Precision when i crank voltage up it shows 38..so is there a issue with that? Or think u or someone can look at the bats and maybe i got something wrong?
Thanks for help so far regardless :)

For my boost.bat I don't have the setVoltageOffset:0,0,162500 even listed all I have is the forcepstate:0,16. I use precision to adjust the voltage when needed. Does your P8 state list the clocks as 324MHz inside inspector?

 

Ya my gpu idels at 324mhz, it was just goofed up when using the boost file without turning on kboost and all, i can actually downclock it fine without kboost but issue is it stays locked there which i mean is good thing but when i hit the boost bat it only goes up to 575 and without kboost enabled dont think it will go above 575.
 
And no i hadnt tried a older driver yet cuz to be honest, when i reformated few days ago and reinstalled windows, i wasnt sure what driver i was using sadly at the time. i wanna say it was 2 or 3 drivers ago i was on but eh ya not sure.
 
 
And yes inside inspector my P8 lists 324
 
 
EDIT: Ya idk man, i had been enabling Kboost and over voltage but i changed the .bat without voltage lines and just enabled kboost and when screen goes black for a sec my max boost is 575, and again i hit idle bat and it does the color flicker, if i restart i get max clock speed but again it will show the color glitch if i hit idle, so eh idk what issue is :/

Ya not sure where issue is at, only thing i can maybe think of is when i reinstalled windows i copied my App Data folder back over, idk if precision has any settings it stores in app folder but ya. Had a issue before with a game when i did that so thought maybe it might be that. oh well, will mess around more tomorrow after work, gonna zzz now but ty for help man, will keep at it and see.