EVGA

Overclocking Problems EVGA Precision X OC 6.0.2

Author
Epsilon_Knight
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2016/07/02 09:25:38
  • Status: offline
  • Ribbons : 0
2016/07/02 09:57:33 (permalink)
Windows 10 Pro x64
EVGA Precision X OC 6.0.2 for Pascal
Nvidia 368.39 Drivers
08G-P4-6183-KR
 
 
Brand new 1080 SC
Stock settings out of the box:
1708 gpu clock
1847 boost clock
Awesome!
 
Time to download EVGA's tools and bump it up a notch.  Say what you will, I was only going to aim for 1950-2000 for the boost clock.  Pushing hardware to the absolute limits of its stability feels like it's asking for electromigration damage but maybe I underestimate modern hardware tolerances.  That's besides the point.  I can't change the core clock at all.
 
Overclocking the core by any amount, using any power or thermal target, has no effect.
(Overclocking the RAM works straight away and simply.)

The settings ARE conserved through application restarts and reboots.
 
Starting KBoost throws the card way above the intended settings.

Also, I'm not sure what the power target is measured against, but 1062 is more than a 20% gain over the 843mv it was showing at stock.  It's more like 25%, and at one point jumped to 1080 (>127.5% of 843mv).  Really hope I didn't hurt the card.  I'm the abundance of caution type when it comes to overvolting.
 
Checked with EVGA support, was told this isn't a known issue, suggested that I reinstall or try MSI Afterburner.  I tried both.  I'm getting the same behavior, even in the MSI software.  
 
Anyone else having this issue?  Solved this problem?
 
EDIT:
 
I am not sure, but KBoost seems to have messed something up with settings.  Since the original post, I have:
1) Uninstalled the OC software
2) Used Display Driver Uninstaller to purge the Nvidia driver from safemode
3) Reinstalled the driver
4) Reinstalled Precision X
5) Saw the same issues with EVGA Precision X ignoring clock settings
6) Uninstalled Precision X, rebooted per the uninstall instructions
7) Installed MSI Afterburner
8) Made the adjustments, which appeared to move both the core and boost clock settings, however no 3D application was running, so couldn't be determined to be working based on the current clock frequency.
9) Launched Rise of the Tomb Raider (DISPLAY DRIVER CRASH!)
10) Launched Rise of the Tomb Raider (DISPLAY DRIVER CRASH!)
11) Caught MSI Afterburner claiming the core clock was at 2200 Mhz well over the core and boost clock arrows.
12) Tried to catch it again.  This is all I got, which still does not match settings.  MSI Afterburner is the only OC tool on the system presently.

 
Presently I cannot launch games without the clock going completely nuts.
post edited by Epsilon_Knight - 2016/07/02 11:57:53
#1

3 Replies Related Threads

    RandyRick
    iCX Member
    • Total Posts : 446
    • Reward points : 0
    • Joined: 2016/05/11 16:03:29
    • Status: offline
    • Ribbons : 0
    Re: Overclocking Problems EVGA Precision X OC 6.0.2 2016/07/02 10:27:54 (permalink)
    I believe this has been reported on the forum before. The feeling being that the SC and perhaps the FTW are OC'd too near the upper edge out of the box, and Kboost pushes (some of) them over the upper limit.
    #2
    Epsilon_Knight
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2016/07/02 09:25:38
    • Status: offline
    • Ribbons : 0
    Re: Overclocking Problems EVGA Precision X OC 6.0.2 2016/07/02 12:43:27 (permalink)
    RandyRick
    I believe this has been reported on the forum before. The feeling being that the SC and perhaps the FTW are OC'd too near the upper edge out of the box, and Kboost pushes (some of) them over the upper limit.




    I'll admit I was surprised, but now I just want my card to take clock settings at all.
    #3
    Signal64
    New Member
    • Total Posts : 27
    • Reward points : 0
    • Joined: 2016/06/02 07:42:54
    • Status: offline
    • Ribbons : 0
    Re: Overclocking Problems EVGA Precision X OC 6.0.2 2016/07/03 01:52:03 (permalink)
    Precision OCX 6.0.2 had enough issues that I went back to 6.0.1. 
    I'd uninstall it and give it a shot.
     
     
    #4
    Jump to:
  • Back to Mobile