Good article here.
Retail AMD Fury X Sound Testing - Pump Whine Investigation
http://www.pcper.com/reviews/Graphics-Cards/Retail-AMD-Fury-X-Sound-Testing-Pump-Whine-Investigation
"Closing Thoughts
There are few things to take away from this testing. First,
the currently selling and shipping AMD Radeon R9 Fury X cards do not include any kind of fix for the pump whine or sound levels of the cooler. Though AMD tells me that we just had a miscommunication or misinterpretation of the comments they shared with us prior to our NDA, I think it is at the very least fair to say that AMD was hoping to deflect the issue on launch day. Now that retail cards are out and end users (not just us) are getting their hands on them, I think its obvious that the sound issues are more of a problem than AMD would like to admit.
Second, the sound of the Fury X cards is very different than the sounds you are used to seeing associated with current flagship graphics cards. Even though the NVIDIA GTX 980 Ti reference cooler is louder than the Fury X under a gaming load, the high frequency of the sounds we are hearing on the Fury X make it more annoying and grating. Everyone's tolerance for this kind of thing is going to be slightly different, but all three people in our office agreed that we would rather hear the more "white-noise-like" sounds of air movement at a constant rate than the high pitched squeal that AMD is dealing with."
I'm pretty disappointed with AMD for the lack of communication regarding this, I'm happy to forgive an error - but they could at least hold their hands up, apologise & agree to replace/fix all cards with the issue.
Pretending it's not a problem & potentially causing people to pay restocking fees can't be worth a few extra sales, if anything a direct & honest approach would make people more comfortable purchasing (knowing a replacement/fix is no problem at all).
On a side note -
http://forums.guru3d.com/showthread.php?t=400333
"Originally Posted by Unwinder
That's actually a good thing. Assuming that AMD driver's I2C API is not completely broken and not cause a crash after using it as is, black screen is most likely a result of accessing some I2C device critical to scanning. So at least I2C is not completely locked and some device is actually being accessed."
Implying voltage unlock may indeed be likely to be possible.