- Apr 23, 2014
- 14
- 0
- 4,510
Hey guys. I have a pretty new pc built only a couple months ago. I've got it overclocked (CPU and GPU), but it has always ran pretty darn stable.
CPU: i7 4770K
GPU: ASUS Strix GTX 970
Mobo: ASUS Maximus VII Hero
RAM: 16gb Corsair (8GB x2)
I have had the GPU clocked at:
1400MHz Core Clock
7600MHz Memory Clock
+23V? (Whatever the max is)
Now, I know overclocking is taxing on your GPU, but I spent a ton of time testing and this O/C hasn't so much as crashed a driver since I began using it. Some overclocks that were slightly higher did, but I down-tuned until I achieved stability. It has never ran super hot, and the case is well ventilated.
I have put a fair amount of hours into games with this config, but nothing crazy... (maybe ~2hrs a day average). And nothing has led me to believe the O/C was unsafe. No artifacting, etc.
So, today I installed a new game (MX vs. ATV Reflex via Steam). I set the resolution to my monitor's and cranked the graphics quality up and set AA to x4. I launched the game and noticed their was some crazy motion blur (it is actually enabled by default by the game itself). I thought "wow, this is a bit much- I should shut that blur off!" but before I could, the screen went blank (my monitor showed "No Signal...") I don't believe the computer froze, but I could not get a picture to show on the display. SO- hard rebooted.
Now I have been trying to diagnose what is wrong for hours. I could not get anything to show on the display after rebooting over and over. So, I removed the GPU and plugged my display into the on-board port. Finally, got a picture. I uninstalled the nVidia display driver, then the game and the Microsoft Visual Redistr... 2010???? whatever that it installed alongside the game. I then powered down and re-installed the GPU, plugged the display back into the GPU port and powered on the PC.
I had picture!!! So, I began re-installing the nVidia drivers. Well, half way through- the screen shut off. I didn't want to disrupt the driver installation, so I started a remote desktop connection and finished the installation. After that, I rebooted. And I have not been able to get a picture on the display for more than a minute or two before it either shuts off, or goes completely green or pink. Like solid green or solid pink. The same thing happens whether I boot windows normally, in safe mode, boot into bios or even to a linux live cd. The display simply dies or turns solid green or pink.
So, considering the fact that the symptoms stretch into the bios and live cd, is it safe to assume that my GPU is dead? Is it really possible to kill a GPU that quickly with what seemed to be a stable O/C? What can I do (if anything) to make sure the GPU is actually shot before buying a new one?
I know that overclocking can destroy hardware. I knew that I risked burning up hardware before I did it. But it always seemed like a disclaimer more so than an actual risk. I truly believed that the driver would crash or the GPU would power down before any harm came to it.
CPU: i7 4770K
GPU: ASUS Strix GTX 970
Mobo: ASUS Maximus VII Hero
RAM: 16gb Corsair (8GB x2)
I have had the GPU clocked at:
1400MHz Core Clock
7600MHz Memory Clock
+23V? (Whatever the max is)
Now, I know overclocking is taxing on your GPU, but I spent a ton of time testing and this O/C hasn't so much as crashed a driver since I began using it. Some overclocks that were slightly higher did, but I down-tuned until I achieved stability. It has never ran super hot, and the case is well ventilated.
I have put a fair amount of hours into games with this config, but nothing crazy... (maybe ~2hrs a day average). And nothing has led me to believe the O/C was unsafe. No artifacting, etc.
So, today I installed a new game (MX vs. ATV Reflex via Steam). I set the resolution to my monitor's and cranked the graphics quality up and set AA to x4. I launched the game and noticed their was some crazy motion blur (it is actually enabled by default by the game itself). I thought "wow, this is a bit much- I should shut that blur off!" but before I could, the screen went blank (my monitor showed "No Signal...") I don't believe the computer froze, but I could not get a picture to show on the display. SO- hard rebooted.
Now I have been trying to diagnose what is wrong for hours. I could not get anything to show on the display after rebooting over and over. So, I removed the GPU and plugged my display into the on-board port. Finally, got a picture. I uninstalled the nVidia display driver, then the game and the Microsoft Visual Redistr... 2010???? whatever that it installed alongside the game. I then powered down and re-installed the GPU, plugged the display back into the GPU port and powered on the PC.
I had picture!!! So, I began re-installing the nVidia drivers. Well, half way through- the screen shut off. I didn't want to disrupt the driver installation, so I started a remote desktop connection and finished the installation. After that, I rebooted. And I have not been able to get a picture on the display for more than a minute or two before it either shuts off, or goes completely green or pink. Like solid green or solid pink. The same thing happens whether I boot windows normally, in safe mode, boot into bios or even to a linux live cd. The display simply dies or turns solid green or pink.
So, considering the fact that the symptoms stretch into the bios and live cd, is it safe to assume that my GPU is dead? Is it really possible to kill a GPU that quickly with what seemed to be a stable O/C? What can I do (if anything) to make sure the GPU is actually shot before buying a new one?
I know that overclocking can destroy hardware. I knew that I risked burning up hardware before I did it. But it always seemed like a disclaimer more so than an actual risk. I truly believed that the driver would crash or the GPU would power down before any harm came to it.
Facebook
Twitter
Instagram