- Dec 22, 2013
- 3
- 0
- 10,510
I have an Nvidia GTX 660 in my rig that I recently updated the drivers on (the last one was for Aassassin's Creed 4 optimization), and after the driver was applied I noticed in Afterburner that the GPU power usage was holding at 100%, which seemed abnormal. Restarting my computer seemed to fix it and I chalked it up to being a little bug due to the drivers just installing.
Now a few days later I played the Just cause 2 multiplayer mod, which likes to heat my card up a little over 50C on average. Before this I played Civ 5 for a few hours, but that doesn't really raise the temp on my system too much. I shut JC2 down (or it might have crashed as it seems to do frequently, I'm not totally sure which), and let the system idle for about three hours. When I began using it again all I did was pull open a screen shot from a game, and after a bit aero terminated. I pulled open afterburner to find my card running at 58C despite nothing being open that should reasonably make it that hot.
I opened the case up, gave it a deep cleaning, it seems to idle back at 30-33C now which is what it typically is at. I'm curious what might have caused something like that, if it's possibly the driver messing it up (I've had no issues until that power boost during the last install) or if it's possible a crashed game can still trick the driver into operating as it had been. I just want to get a handle on if this is something more serious or possibly just an error due to a buggy driver/game.
Now a few days later I played the Just cause 2 multiplayer mod, which likes to heat my card up a little over 50C on average. Before this I played Civ 5 for a few hours, but that doesn't really raise the temp on my system too much. I shut JC2 down (or it might have crashed as it seems to do frequently, I'm not totally sure which), and let the system idle for about three hours. When I began using it again all I did was pull open a screen shot from a game, and after a bit aero terminated. I pulled open afterburner to find my card running at 58C despite nothing being open that should reasonably make it that hot.
I opened the case up, gave it a deep cleaning, it seems to idle back at 30-33C now which is what it typically is at. I'm curious what might have caused something like that, if it's possibly the driver messing it up (I've had no issues until that power boost during the last install) or if it's possible a crashed game can still trick the driver into operating as it had been. I just want to get a handle on if this is something more serious or possibly just an error due to a buggy driver/game.
Facebook
Twitter
Instagram