• 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.

980 ti woes

Sounds like the all or nothing approach to reach 1500+. Wouldn't you be better off settling for 1450-1480 ensuring peace of mind? :eek:

I wouldn't say so, the card is designed for LN2 overclocking and the current setup sees a max temperature of 74c on air. I would be more than happy to run it stock (it boosts to 1418 at stock), but it seems to run fine with the overclock. I could probably push the memory twice as much, but the gains are nothing really.

As I said previously, these cards run close to the 100% power target and they also throttle at 65c when it's not exactly hot. I think the auto throttle feature has a lot to do with instability, and upping the temp and power target seems to stop the throttling.

The voltage slider in AB only adds a minor boost. Only a BIOS mod can open up voltage properly.
 
Last edited:
I'm a senior techie in IT, I've grown to love and hate the troubleshooting side of life... After a decade in this career though, it can be a bit monotonous.

That must help, but as you say I don't suppose you want to have to continue doing it at home. I quite enjoy the process for small issues, by the end of a year of intermittent problems with the 780 I was tearing my hair out!
 
Try running the card using K boost in PX. It will fix the voltage and prevent any down clocking. It is what fixed my 980 random crashes.... Worth a try.
 
Well, all weekend I've been playing games and not one crash, so upping the power target to 105% and adding an addition 18mV on has certainly helped!

Which means, sadly I have to RMA :(
 
Or you could leave the settings in place and just enjoy?

Why? Clearly the card is faulty if it crashes at stock. Surely this will just give me more headaches later on? And not to mention, I won't be able to sell?

Why bodge when I have a solution in place?
 
Why? Clearly the card is faulty if it crashes at stock. Surely this will just give me more headaches later on? And not to mention, I won't be able to sell?

Why bodge when I have a solution in place?

As I said earlier, I run my card at those settings and I don't get any crash. I also don't get any throttling.

I think it might be driver related and you could end up with the same situation with a new card?
 
Why? Clearly the card is faulty if it crashes at stock. Surely this will just give me more headaches later on? And not to mention, I won't be able to sell?

Why bodge when I have a solution in place?

RMA it, its not fit for purpose if it cannot run at stock speeds. Mine is running at 1500 with that voltage increase (full block) so it should be more than capable at stock speeds.

I wouldn't run it under K boost personally, full clock (boost) at all times is not a good thing in my eyes, there is a setting in the Nvidia Control Panel which is something around optimising for performance not dynamic (forget the wording and i'm not home). This fixes it at full clock, but not full boost clock like K Boost - K boost is more designed for benchmarking to avoid anything down clocking whilst it runs - either way its not ideal to be sat idle in Windows and have it running flat out for no reason.
 
Last edited:
RMA it, its not fit for purpose if it cannot run at stock speeds. Mine is running at 1500 with that voltage increase (full block) so it should be more than capable at stock speeds.

I wouldn't run it under K boost personally, full clock (boost) at all times is not a good thing in my eyes, there is a setting in the Nvidia Control Panel which is something around optimising for performance not dynamic (forget the wording and i'm not home). This fixes it at full clock, but not full boost clock like K Boost - K boost is more designed for benchmarking to avoid anything down clocking whilst it runs - either way its not ideal to be sat idle in Windows and have it running flat out for no reason.

You've misunderstood the workaround. It reduces its clock speed at idle. It's the targets that have been raised, as in the upper limits.
 
You've misunderstood the workaround. It reduces its clock speed at idle. It's the targets that have been raised, as in the upper limits.

K Boost does not reduce its clock at idle though, which was my point (someone else mentioned ahead of your comment) it fixes it as it would be at full load at all times. Unless you create multiple profiles and switch between them when you are not in need of full power its running on max.

Unless you didnt save your profile and set to start with windows, in which case its not doing anything.
 
K Boost does not reduce its clock at idle though, it fixes it as it would be at full load at all times. Unless you create multiple profiles and switch between them when you are not in need of full power its running on max.

Unless you didnt save your profile and set to start with windows, in which case its not doing anything.

Profile saved, starts with windows, temp target all the way to the right, voltage slider all the way to the right... It goes down to 135Mhz when idle.
 
Profile saved, starts with windows, temp target all the way to the right, voltage slider all the way to the right... It goes down to 135Mhz when idle.

K Boost mate, you are not using K boost. What you're saying is correct, what i'm referring to is the post a few earlier with someone running K boost to resolve it - which is full clock 24/7.

Adding an OC, voltage, more power target is not K Boost.
 
K Boost mate, you are not using K boost. What you're saying is correct, what i'm referring to is the post a few earlier with someone running K boost to resolve it - which is full clock 24/7.

Adding an OC, voltage, more power target is not K Boost.

Yes. We're talking about the same thing. If you look at Agnes last post you'll see that they are using my method to solve it, and I think it may be driver related which is why I would be wary of RMA.
 
Back
Top Bottom