Coldblackice
[H]ard|Gawd
- Joined
- Aug 14, 2010
- Messages
- 1,156
I hear people comment about GPU memory/ram "dying" from an overclock. Is this possible? Is there an objective way to tell, besides circumstantial blue screens?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
gddr5 will most certainly artifact and will crash if clocked too high. on my 670 there was a spot where performance would degrade just slightly and any higher would artifact and then crash. on my 660ti it seems to level off at a certain spot then any higher will artifact and crash. by crash I mean what ever I am testing will lock up or just stop if I let it keep running after seeing artifacts.Yes, it can... on older cards it would artifact (GDDR3/below), but with GDDR5's error correction it won't, rather it will just degrade performance unless you push it extremely far, where it can just overstress the memory controller and/or VRAM and the card will have issues (i.e. not POST, have artifacts, cause crashes, or any other number of things).
gddr5 will most certainly artifact and will crash if clocked too high
Yes, it can... on older cards it would artifact (GDDR3/below), but with GDDR5's error correction it won't, rather it will just degrade performance unless you push it extremely far, where it can just overstress the memory controller and/or VRAM and the card will have issues (i.e. not POST, have artifacts, cause crashes, or any other number of things).
By using the word "dying," I assume you're asking about permanent damage. In that case it's very difficult to kill a component, even something more sensitive like vRAM, simply with overclocking. Overvolting is really what damages hardware. That said, you can shorten the lifespan of vRAM by overclocking if it's not adequately cooled. The increased speeds and heat accelerate electro migration.I hear people comment about GPU memory/ram "dying" from an overclock. Is this possible? Is there an objective way to tell, besides circumstantial blue screens?