Personal computing discussed
Moderators: renee, morphine, SecretSquirrel
auxy wrote:Is anyone else familiar with this?
I used to get this bug on my GTX 460(s) where sometimes they'd get stuck in P1 state, which is the second-fastest state. On my GTX 460s, which were at 822Mhz, it was 411Mhz. Nothing I would do could raise or lower the P-state, until I rebooted.
I assumed they'd fixed it in drivers because it hadn't come up in a long time, but I've just recently noticed my GTX Titan is doing it! And HAS BEEN doing it for awhile now!
What the heck is the deal? Has anyone else had this problem?
Deanjo wrote:I haven't noticed anything on my Titans behaving like this (I do run them in linux however). Are you sure they are actually only running in P1 or is it just what is displayed on the control panel? I would try a 3rd party monitoring program to verify that it is actually being "stuck" in P1 and not just the panel not updating.
Arclight wrote:I've used every driver, Beta and WHQL, since 290 series, but I've only confirmed this since 314. I have confirmed it on all since 314, though. It's intermittent, but it seems guaranteed to happen after ~60-70 hours of uptime.What driver version? I would recommend trying the driver version 331.93.
auxy wrote:Arclight wrote:I've used every driver, Beta and WHQL, since 290 series, but I've only confirmed this since 314. I have confirmed it on all since 314, though. It's intermittent, but it seems guaranteed to happen after ~60-70 hours of uptime.What driver version? I would recommend trying the driver version 331.93.
I tend to leave a game running all the time; maybe that's related?
I'm also using my Titan alongside two displays connected to my Intel HD; however, this also happened on my GTX 460s when I wasn't using any other adapters (besides those), and a 260 before that. It was REALLY bad on my 260 where I first noticed it, but they did fix something that was causing it in a later driver (that is, it was in the patch notes.)
Arclight wrote:Have you or have you not tried 331.93? If you have and the issue persists then do one last test by installing the card in another system. If the issue can be reproduced then RMA the card.
NVIDIA 331.93 release notes wrote:I use GPU-accelerated PhysX all the time despite having Intel graphics enabled. How amusing.NVIDIA GPU PhysX acceleration is not available if there is a non-NVIDIA graphics processor in the system, even if it is not used for rendering.
Arclight wrote:auxy wrote:Arclight wrote:I've used every driver, Beta and WHQL, since 290 series, but I've only confirmed this since 314. I have confirmed it on all since 314, though. It's intermittent, but it seems guaranteed to happen after ~60-70 hours of uptime.What driver version? I would recommend trying the driver version 331.93.
I tend to leave a game running all the time; maybe that's related?
I'm also using my Titan alongside two displays connected to my Intel HD; however, this also happened on my GTX 460s when I wasn't using any other adapters (besides those), and a 260 before that. It was REALLY bad on my 260 where I first noticed it, but they did fix something that was causing it in a later driver (that is, it was in the patch notes.)
Have you or have you not tried 331.93? If you have and the issue persists then do one last test by installing the card in another system. If the issue can be reproduced then RMA the card.
auxy wrote:Are you suggesting that it can't possibly be a persistent driver bug and that somehow my card has failed/is failing? Isn't it awfully coincidental that a Tesla arch card, a Fermi arch card (and then a pair of them), and a Kepler arch card have all had the same problem?[...]
ClickClick5 wrote:60-70 hours? How about a restart? Problem solved
JohnC wrote:There is no "bug". My Titan SC is always idling at 324MHz, using any recently released driver version, beta or WHQL. You either have something (game, program or some OS service) running in background which uses "GPU acceleration" or there is an issue with some setting in your modified BIOS (if you flashed your Titan with it) which may also cause the card to get stuck at certain P-state. Most likely the former, considering that the problem disappears after you reboot.
Arclight wrote:If the issue can be reproduced then RMA the card.
JohnC wrote:I'm not talking about lower p-states -- that is, lower clocks and power-saving modes. I'm talking about p0 state. My problem is that I can't get the card to go into p0 state (to raise clock above ~600Mhz) without rebooting. It also doesn't go into the lower p-states (100Mhz etc) but I'm not that worried about that.I did read your thread, did you read mine? :roll:
auxy wrote:The only overclocking tool I use is MSI Afterburner, and in any case, background apps shouldn't keep my GPU from going up to P0 state when I am running a fullscreen game. It would make sense if they kept it from dropping to a lower p-state, but that's not my problem.Isn't it awfully coincidental that a Tesla arch card, a Fermi arch card (and then a pair of them), and a Kepler arch card have all had the same problem?
ClickClick5 wrote:Do you restart your desktop every few days? I sure don't. I prefer to leave it up constantly. When I reboot, I have to restart a bunch of apps and put all my windows exactly the way I like them, so rebooting is an inconvenience for me, and I'd prefer to avoid it. Aside from this stupid NVIDIA ... thing, there's no reason for me to reboot.60-70 hours? How about a restart? Problem solved.
auxy wrote:How exactly do my modifications to my Titan affect my older GPUs that had this same problem?
auxy wrote:ClickClick5 wrote:Do you restart your desktop every few days? I sure don't. I prefer to leave it up constantly. When I reboot, I have to restart a bunch of apps and put all my windows exactly the way I like them, so rebooting is an inconvenience for me, and I'd prefer to avoid it. Aside from this stupid NVIDIA ... thing, there's no reason for me to reboot.60-70 hours? How about a restart? Problem solved.
auxy wrote:Okay, well, anyway, I can't be bothered to keep restating things if people won't read. Thanks for your replies everyone. This thread served well enough to answer the question that "no, nobody on Techreport knows what I'm talking about".
Arclight wrote:You are dumb. It's not my card. Please stop posting. Or breathing.It's not our fault your card has issues.
JohnC wrote:I'm just going to deal with it. It's not THAT big a deal restarting every few days. It's just annoying. As someone else said above, it's not "first world problems", it's just that things aren't working as they should and that frustrates and irritates me.Good luck reading the same answers at different places.
auxy wrote:Arclight wrote:You are dumb. It's not my card. Please stop posting. Or breathing.It's not our fault your card has issues.
auxy wrote:Is anyone else familiar with this?
I used to get this bug on my GTX 460(s) where sometimes they'd get stuck in P1 state, which is the second-fastest state. On my GTX 460s, which were at 822Mhz, it was 411Mhz. Nothing I would do could raise or lower the P-state, until I rebooted.
I assumed they'd fixed it in drivers because it hadn't come up in a long time, but I've just recently noticed my GTX Titan is doing it! And HAS BEEN doing it for awhile now!
What the heck is the deal? Has anyone else had this problem?
auxy wrote:If the card is the problem, why did it happen on three other cards, across two more (three total) generations of cards...? (in different motherboards, different processors, different operating systems...)
auxy wrote:You are dumb. It's not my card. Please stop posting. Or breathing.