Well, i've got news from you, this has been confirmed from AMD themselves now, according to hardware.fr, a reference in france as you can tell by the name. Here's the article :
http://www.hardware.fr/news/10235/ra...-probleme.html
They reproduced the problem, and here is AMD's official position, which is interesting (let me translate interesting parts for you, besides the "we confirm the issue" for you, you can check it with google trad if you want) : (oh, and TDP = Thermal design power =
http://en.wikipedia.org/wiki/Thermal_design_power )
...
"This test (GPU:3D from OCCT) loads the Radeon with a charge so well balanced between texturing units, ROPs, computing units and memory that they all function to a very high percentage. The power supply stage wasn't designed to handle such a charge. It's thus shutting down, in security mode, to protect the card, which requires a reboot of the computer.
AMD indicated us that this is a deliberate choice to protect the power supply stage components from overheating or overintensity (? don't know if this term is correct), both being obviously linked. If AMD GPUs can protect themselves in case the TDP is being surpassed, by reducing their frequency, they are incapable of communicating with the power supply stage controler, and cannot act if this one is surpassed by the load, its sole resort being of shutting down the card.
It has been a few years since the VRM have been switching from analogical to numerical, providing a full monitoring. RivaTuner provides plugin that can give you access to those values. AMD was the first one to use such VRM on the X1950Pro, and it seems unconceivable that AMD didn't think it would be useful to use those values. AMD indicates that this problem will be fixed in later GPUs.
For AMD, it is normal to design a Power supply stage that is not in function of the maximum power consumption of the GPU, because there's a huge difference between the theorical maximum and the maximum that is usually seen in practical applications. All the recent chips can draw more current than their TDP and have mecanism that can maintain them between these limits. However, what is not normal, is to have conceived a a power supply stage that does not correspond to the TDP. With the HD4870, 4870x2 and 4890, AMD fixed a limit to the TDP that is not possible to attain with the reference PCB. Imagine, for instance, a GPU that is capable of drawing 100A before going into protection mode and a power supply stage that is going into protection mode at 90A.
To justify themselves, AMD insist on the fact that that no practical case will charge the GPU as much. You have to want it to be able to do it, and use a very specific code. Nothing says that it is not possible to have such code on a GeForce (BTW, I'm working on it, seeing if i cannot optimize it for GeForce. it'll probably be a different algorithm). Note that the problem is highly unlikely to appear in GPGPU computing, as in this mode, most GPU units are Idling, thus drawing less current.
Those justifications from AMD changes nothing to the design error they made. Even if the problem appearing is very unlikely, nothing tell it won't happen again. And this is a door open to viruses and such malicious softwares."
...
(they say they did not reproduce the problem on a 4 phase card and on a 3 phase non-reference design card, that were using different components).
Nonetheless, the fact that we did not reproduce it on those cards might be due to two things : either the VRMs are more powerful, or they are unprotected. While nothing indicates that the VRMs are going over their limits,in the doubt, we advise you not to abuse of this test on your Radeon cards.
AMD told us he is not planning any modification to solve the problem on existing products. However, AMD may review its limits on the GPU so that it could go into protection mode before the power supply stage. AMD may also use, in asoftware way, the values sent by the VRM monitoring to reduce the GPU frequencies automatically and avoid the crash. AMD may also propose a new reference design, especially for the HD4890. AMD insist on the fact that the problem foes not occur on any existing application (other than OCCT, of course). A justification which doesn't sound right to us because the Radeon switch from the "reliable" category to the "almost reliable" category.
Should you avoid those Radeons ? We won't go as far, even if it would be logical for somebody who would like to avoid any potential problem to let aside the reference boards from AMD, or even, in doubt, buy a GeForce.
Needless to say that Overclocked cards will encounter this problem or different ones in OCCT. In that case, neither AMD or the manufacturer is responsible if at stock values the card doesn't show any problems".
As for the "don't abuse from the test", i'd say that by default, the shader complexity 0 is selected, and that value will never provoke the bug Radeons are encountering. That's the safety measure i took. Don't ditch my test ;)
Sorry for the quality of my translation. I'm doing my best... it's not that easy you know ;) And my english is far from perfect, as you may have already seen.
What's important to note (IMHO) :
- AMD acknowledges the problem on very specific app code
- The problem will be fixed in later cards by linking the Power supply stage monitoring info to the GPU info. I still find it weird to design a GPU that cannot function at 100% of its capabilities... truly, this is leaving me... abashed. However, they did not say they're planning to castrate OCCT. If that's true, i'm happy they're not doing it "app by app". Their approach is the good approach IMHO. The best approach would be a card that can handle everything at full speed. Which is what, marketingly, everybody boasts. I wonder why 3d cards functions differently than any other hardware in the PC field...
- The tester did reproduced it, and did a very great job at isolating the problem
- AMD is planning alot of modification to get around the problem. It is important to them. Even a new reference board ! Wow. So much for a problem that does not exist... sorry, i'm savoring a bit the moment after the flame war we had here, even recently ;) Please, just let me pass this line ;) It's the only one i will write about it.
That's all about it. Sorry for the poor quality of the trad, perhaps google trad will do a better job at it, i'll let you read the one you like better ;) Trust me, i tried to do my best, and to be as close to the original test as possible.