|
fattypig
|
 |
October 09, 2013, 03:52:32 PM |
|
This is what happened to my 3 weeks old gigabyte today, had to put out a fire  It poped while i turned on the PC, not while mining   That sucks, imagine what would happen if its mining and no one is around. |
|
|
|
|
|
|
|
|
"Your bitcoin is secured in a way that is physically impossible for others to access, no matter for what reason, no matter how good the excuse, no matter a majority of miners, no matter what." -- Greg Maxwell
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
l3jmr (OP)
Member
 Offline
Activity: 99
Merit: 10
|
|
October 09, 2013, 05:17:58 PM |
|
Haha nice one that you got it on tape Looks like you jumped, so did i when it happened to mine |
⚫ ⚫ ⚫ Listen to the weekly altcoinsidekick.com podcast to understand what cryptocurrency is really all about. ⚫ ⚫ ⚫ |
|
|
l3jmr (OP)
Member
Offline
Activity: 99
Merit: 10
|
|
October 09, 2013, 05:20:30 PM |
|
This is what happened to my 3 weeks old gigabyte today, had to put out a fire It poped while i turned on the PC, not while mining That sucks, imagine what would happen if its mining and no one is around. |
⚫ ⚫ ⚫ Listen to the weekly altcoinsidekick.com podcast to understand what cryptocurrency is really all about. ⚫ ⚫ ⚫ |
|
|
|
wedge
|
|
October 09, 2013, 05:34:18 PM |
|
Haha nice one that you got it on tape Looks like you jumped, so did i when it happened to mine Lol, yeah, I jump every time. Even when I know it's going to happen. |
|
|
|
|
wedge
|
|
October 09, 2013, 05:38:55 PM |
|
That sucks, imagine what would happen if its mining and no one is around.
It's not a problem. The failure happens the exact same way every time. It goes like this: 1. Rig is mining its own business, working along nicely 2. Rig completely shuts down for no apparent reason 3. Owner sees the rig is off and goes to check it out 4. Inspect the rig, everything looks fine, confused as to why it shut off 5. Thinking everything is OK, switches the rig back on 6. BANG! The pop doesn't happen until someone physically turns the machine back on after the actual failure. So there's no risk of causing a fire while nobody is around. |
|
|
|
98a234umf89rw3rahrjih
Newbie
Offline
Activity: 6
Merit: 0
|
|
October 09, 2013, 09:47:54 PM |
|
The pop doesn't happen until someone physically turns the machine back on after the actual failure. So there's no risk of causing a fire while nobody is around.
Most of the pops really happen when the machine is getting powered on, but it's not always the case. I had one card under frequent monitoring because of the 2 already failed capacitors, when I noticed the sudden stop of fan noise followed by the strong burnt smell. Third pop... it was time to kill it, because I didn't plan to get one more barely alive card back from the shitty RMA process. Powering the computer on caused the fourth capacitor to pop so hard that a GLOWING chunk flew at least 10 cm before landing on a wooden furniture (ouch). Don't underestimate gigabyte, next time we may hear about one of their products just catching fire. It's time for them to get rid of the only temperature sensor to shave off even some more cents per card. |
|
|
|
|
l3jmr (OP)
Member
Offline
Activity: 99
Merit: 10
|
|
October 09, 2013, 10:15:51 PM |
|
That sucks, imagine what would happen if its mining and no one is around.
It's not a problem. The failure happens the exact same way every time. It goes like this: 1. Rig is mining its own business, working along nicely 2. Rig completely shuts down for no apparent reason 3. Owner sees the rig is off and goes to check it out 4. Inspect the rig, everything looks fine, confused as to why it shut off 5. Thinking everything is OK, switches the rig back on 6. BANG! The pop doesn't happen until someone physically turns the machine back on after the actual failure. So there's no risk of causing a fire while nobody is around. This is the exact way it happened to me  |
⚫ ⚫ ⚫ Listen to the weekly altcoinsidekick.com podcast to understand what cryptocurrency is really all about. ⚫ ⚫ ⚫ |
|
|
l3jmr (OP)
Member
Offline
Activity: 99
Merit: 10
|
|
October 09, 2013, 10:18:54 PM |
|
Haha nice one that you got it on tape Looks like you jumped, so did i when it happened to mine Lol, yeah, I jump every time. Even when I know it's going to happen. So you expected this? I thought you was just recording randomly |
⚫ ⚫ ⚫ Listen to the weekly altcoinsidekick.com podcast to understand what cryptocurrency is really all about. ⚫ ⚫ ⚫ |
|
|
|
fattypig
|
|
October 10, 2013, 01:37:41 AM |
|
Haha nice one that you got it on tape Looks like you jumped, so did i when it happened to mine Did you just tape by luck or you actually know it? !!!! |
|
|
|
Wipeout2097
Sr. Member
Offline
Activity: 840
Merit: 255
SportsIcon - Connect With Your Sports Heroes
|
|
October 13, 2013, 01:51:31 AM |
|
My advice is to not run these cards above 1000 mV
This is a damn fine advice. I'm running my cards at 950 |
|
|
|
Wipeout2097
Sr. Member
Offline
Activity: 840
Merit: 255
SportsIcon - Connect With Your Sports Heroes
|
|
October 13, 2013, 01:53:07 AM |
|
Thermaltake 850w, no powered riser on this one, there is only one more 7950 currenty in the mobo so power should be sufficent.
Thermaltake is a terrible, terrible brand. |
|
|
|
|
redtwitz
|
|
October 13, 2013, 05:43:41 PM |
|
The pop doesn't happen until someone physically turns the machine back on after the actual failure. So there's no risk of causing a fire while nobody is around.
This isn't true. My computer restarted itself. |
|
|
|
|
|
wedge
|
|
October 13, 2013, 06:05:32 PM |
|
This isn't true. My computer restarted itself.
There's always going to be exceptions I suppose. Every mobo/power supply combo might behave differently. But that does appear to be the exception. I even have my bios set to always turn back on after a power outage. And that works, it turns itself back on if I unplug and re-plug the power supply. But when this failure happens, it turns off and stays off until manually switched on. |
|
|
|
|
wedge
|
|
October 13, 2013, 06:06:40 PM |
|
Thermaltake 850w, no powered riser on this one, there is only one more 7950 currenty in the mobo so power should be sufficent.
Thermaltake is a terrible, terrible brand. +1 Buy a Seasonic. Or a rebranded Seasonic. |
|
|
|
|
Quix
|
|
October 13, 2013, 06:56:19 PM |
|
Make sure to tell them it died while playing Cysis 3 and that you never overclock  . |
|
|
|
|
|
wedge
|
|
October 13, 2013, 07:13:58 PM |
|
Make sure to tell them it died while playing Cysis 3 and that you never overclock . They never asked.  |
|
|
|
Don007
Legendary
Offline
Activity: 1050
Merit: 1007
Live like there is no tomorrow!
|
|
November 03, 2013, 10:09:35 PM |
|
I own the same one. What max temperature do you guys add in CGMiner? I mean the --temp-overheat command, which makes the fans go to 100% when they hit the chosen temperature.
As I have only 1 GPU, I really don't want to fire up.
|
{Curently quite inactive as I'm really busy in my private life. I will get back soon!} -> Your line here during my inactivity? Feel free to PM <- |
|
|
|
redtwitz
|
|
November 03, 2013, 11:43:00 PM |
|
I own the same one. What max temperature do you guys add in CGMiner? I mean the --temp-overheat command, which makes the fans go to 100% when they hit the chosen temperature.
As I have only 1 GPU, I really don't want to fire up.
--temp-overheat won't prevent this kind of failure. CGMiner monitors the GPU temperature, not the VRM temperature. |
|
|
|
|
Don007
Legendary
Offline
Activity: 1050
Merit: 1007
Live like there is no tomorrow!
|
|
November 03, 2013, 11:45:32 PM |
|
Allright, but doesn't there is a kind of relation between those two?
I'm still wondering which --temp-overheat you guys use, because i set mine on 82. Which is just a randomly chosen number I feel confortable with, but I haven't based it on any research or logic.
|
{Curently quite inactive as I'm really busy in my private life. I will get back soon!} -> Your line here during my inactivity? Feel free to PM <- |
|
|
|
wedge
|
|
November 04, 2013, 12:20:23 AM
Last edit: November 04, 2013, 12:40:05 AM by wedge |
|
Allright, but doesn't there is a kind of relation between those two?
I'm still wondering which --temp-overheat you guys use, because i set mine on 82. Which is just a randomly chosen number I feel confortable with, but I haven't based it on any research or logic.
82 is fine for the gpu. But my vrm's have been blowing up when the gpu is running in the mid 70's. I've got them running in the 60's right now for a couple weeks, and have been issue free. The changes I've made to prevent this issue: Reduced intensity from 20 to 18. Reduced powertune from 20 to -13. Reduced overclock from 1075 to 1050. With these changes, each card is running 10 to 15 degrees cooler, and the whole system (4 cards total) is running at 50 watts less. It's also hurt my hashrate by about 40Kh/s per card. But, I'm now getting much fewer rejects than before. I've also added a heatsink on the back of the cards along the metal support for the vrm's. Not sure how much difference that makes, but those heatsinks are getting hot, so that means they're doing some good. I just don't know how much good. intensity 18 was chosen because 19 had no affect at all. 18 decreased hashrate just slightly. powertune -13 was chosen because that is the highest setting that made a difference to hashrate. -12 and they still ran at the same speed as +20. -13 was the first setting that actually did something. So by using those settings, I know that they will improve power usage and temperature for the better. gpu clock 1050 was chosen somewhat randomly. |
|
|
|
|
