I am certain it is the module, after messing around with it for a while I started to smell that infamous burning electronics smell. To further prove it's the module, I saw it spark up pretty good upon flipping the switch on... scared the crap out of me lol.
This just happened to me too.
On mine it's clearly the chip near the center of a miner with a big + sign and "680 e31" - it looks and smells burnt
In my unit two modules are connected and two are not. The problem is on one of the connected modules, though it looks like I could separate it fairly easily.
Still searching... is there a warranty or some way to get this fixed?
What frequency were you running?
It was set to 325 mhz and oc'd using --avalon-auto
It's a b3 with ckolivas's 20130821 firmware and for options "--real-quiet --avalon-auto --avalon-fan 100 --avalon-freq 325-370 --avalon-cutoff 90 --avalon-temp 70"
Previously it would get up to the high 340's, sometimes hover around 350/351. I never did any forced or "crazy" oc'ing, just used avalon-auto.
Last week it was stuck at 325 most of the time, and put up the expected hash rate (measured at the pool).
I got in today and found the red light on, fans not spinning, toggled the power switch, and got a loud pop and the burnt smell, I immediately shut it off and started pulling it apart. The PSU is good, per the two testers I tried on it.
I have my a/c feeding four b3's 24/7 and the other three are doing well (no slowdown or other signs of trouble) all with temp2 in the mid 60's.
I disconnected the bad module and have the remaining three running now. I tried changing the miner count from 32 down to 24, but that made it run like only two modules were installed. I put it back to 32 and it's doing about 78 GH/s @325 Mhz. Also interesting is that avalon-auto doesn't seem to be kicking in. It's been stuck at 325 Mhz for almost half an hour now (since my last restart), just like last week. I tried setting avalon-freq to 330-370 just to get it to move and it won't.
Could this be due to a bad flash? I haven't seen anyone else report that problem.
It's a b3 with ckolivas's 20130821 firmware and for options "
--real-quiet --avalon-auto
--avalon-fan 100 --avalon-freq 325-370
--avalon-cutoff 90 --avalon-temp 70"
Don't the two highlighted in red contradict each other as settings? How can it run "real quiet" when the fan speed is forced to 100%?
The settings highlighted in blue seem to be pretty extreme settings. 70C temperatures and 90C as the cutoff temp? Thats pretty crazy....
Did I wake up today in a different universe where running these at 70+ degrees is a good thing with a cutoff temp of 90C? The temp on these is being measured by a cheapy temp sensor that rests on the heatsink rather than on the chip. With temps like those it is almost certain to fry....
