Author

Topic: Computer Caught Fire! (Read 2118 times)

hero member
Activity: 1246
Merit: 501
May 21, 2013, 05:06:37 AM
#19
Friends don't let friends use Gigashyte. 
newbie
Activity: 56
Merit: 0
May 20, 2013, 08:42:40 PM
#18
Who said btc isn't hot?
legendary
Activity: 1316
Merit: 1000
Varanida : Fair & Transparent Digital Ecosystem
May 20, 2013, 08:40:09 PM
#17
God, be safe, you should move your mining rig to underground.
hero member
Activity: 574
Merit: 500
May 20, 2013, 08:31:25 PM
#16
Hope that is not normal. I don't want to see in the news "bitcoiners are burning all the cities"  Sad

WE ARE GOING TO BURN ALL THE CITYS DOwn !!!!

Anarchy !@!!!!

Well as much as a group of nerds with video cards will achieve ..lol
newbie
Activity: 35
Merit: 0
May 20, 2013, 08:18:53 PM
#15
LOL we had a gigabyte motherboard at work have that happen, except it burnt directly through the PCB.  It was still ammusing.
It was replaced with another gigabyte motherboard (RMA - but upgraded from a 1157 to a 1155 motherboard and a new chip, so it was a nice upgrade for a 2 year old MB).
No troubles with any other gigabyte stuff so far.
copper member
Activity: 2310
Merit: 1032
May 20, 2013, 04:02:39 PM
#14
Unfortunately, this does happen once in a while. I had the exact same thing happen to my First AsRock P55 Extreme board but the replacement has been running fine for years now and I've abused it pretty bad lol. I'd RMA it and grab a multimeter to test the PSU. Hopefully it didn't fry your other components when it went.

I have a PSU tester but I've got a 750 watt power supply test good but nothing I plug into it will work.  I'm a little skeptical of my PSU tester.  How do I test w/a multimeter?

You just did test it, If nothing it plugs into works, It does not work.
hero member
Activity: 742
Merit: 500
May 20, 2013, 03:36:58 PM
#13
Unfortunately, this does happen once in a while. I had the exact same thing happen to my First AsRock P55 Extreme board but the replacement has been running fine for years now and I've abused it pretty bad lol. I'd RMA it and grab a multimeter to test the PSU. Hopefully it didn't fry your other components when it went.

I have a PSU tester but I've got a 750 watt power supply test good but nothing I plug into it will work.  I'm a little skeptical of my PSU tester.  How do I test w/a multimeter?
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
May 20, 2013, 02:28:45 PM
#12
Comp deaths like this are not uncommon. I've had many a brand spanking new motherboard die during a 24 hour burn in. Motherboards dying are pretty tame, bit of a smell.

But compares to a fully loaded KW power supply exploding while your head is in the case looking for fan vibration -_-
legendary
Activity: 1190
Merit: 1001
May 20, 2013, 02:22:59 PM
#11
Hope that is not normal. I don't want to see in the news "bitcoiners are burning all the cities"  Sad
full member
Activity: 142
Merit: 100
May 20, 2013, 02:16:16 PM
#10
Unfortunately, this does happen once in a while. I had the exact same thing happen to my First AsRock P55 Extreme board but the replacement has been running fine for years now and I've abused it pretty bad lol. I'd RMA it and grab a multimeter to test the PSU. Hopefully it didn't fry your other components when it went.
sr. member
Activity: 452
Merit: 250
May 20, 2013, 11:36:41 AM
#9
Do the AMD APUs have separate vcore for the iGPU? Usually the whole CPU only has a single voltage but either way it looks like the stress caused some of your vcore switching MOSFETs to die catastrophically.

Based on the fact that the vcore regulators don't have any kind of heatsinking I imagine it was probably a cheaper board. Usually cheaper boards only use the minimum for the CPU regulator (usually only 2-3 regulator phases) but enthusiast grade boards will have 6-9 phases or more.

Edit - just looked up the board, looks like it has a pretty decent cpu regulation layout so it was likely just an unlucky failure
hero member
Activity: 742
Merit: 500
May 20, 2013, 11:15:23 AM
#8
well that component is part of the VRM for the CPU, which part of the CPU can be the tough part to figure out. If its a phase for the cores, RAM or integrated graphics.
Was the CPU / RAM or integrated GPU oc'd? the phases could have been pumping more current than designed if so.

Nothing oc'd (although the board supposedly supports easy oc with 3 oc levels).

yeah, Im gonna go out on a limb and say the mfr skimped somewhere on the RAM / integrated GPU VRM current handling capabilities(if scrypt mining both of those would be heavily under load, if just sha256 then the integrated GPU would be)
Or, alternatively, one of those mosfets was just defective to begin with.

I did have Litecoin running.  I was actually catching up the Litecoin blockchain when it caught fire.  I'm wondering if the integrated mining was set to start on startup; could have done it.  I'm going to stop mining using the GPU; 80 MH/s isn't worth this kind of headache.
full member
Activity: 347
Merit: 100
May 20, 2013, 10:31:56 AM
#7
Hope you solve ASAP. I had lot of Gigabyte mobo at home and sold many, but no problem.
Maybe a bad stock of some boards.
legendary
Activity: 2450
Merit: 1002
May 20, 2013, 09:57:52 AM
#6
well that component is part of the VRM for the CPU, which part of the CPU can be the tough part to figure out. If its a phase for the cores, RAM or integrated graphics.
Was the CPU / RAM or integrated GPU oc'd? the phases could have been pumping more current than designed if so.

Nothing oc'd (although the board supposedly supports easy oc with 3 oc levels).

yeah, Im gonna go out on a limb and say the mfr skimped somewhere on the RAM / integrated GPU VRM current handling capabilities(if scrypt mining both of those would be heavily under load, if just sha256 then the integrated GPU would be)
Or, alternatively, one of those mosfets was just defective to begin with.
hero member
Activity: 742
Merit: 500
May 20, 2013, 09:51:21 AM
#5
well that component is part of the VRM for the CPU, which part of the CPU can be the tough part to figure out. If its a phase for the cores, RAM or integrated graphics.
Was the CPU / RAM or integrated GPU oc'd? the phases could have been pumping more current than designed if so.

Nothing oc'd (although the board supposedly supports easy oc with 3 oc levels).
legendary
Activity: 2450
Merit: 1002
May 20, 2013, 09:49:03 AM
#4
well that component is part of the VRM for the CPU, which part of the CPU can be the tough part to figure out. If its a phase for the cores, RAM or integrated graphics.
Was the CPU / RAM or integrated GPU oc'd? the phases could have been pumping more current than designed if so.
hero member
Activity: 742
Merit: 500
May 20, 2013, 09:38:34 AM
#3
wow! hope you and your property are safe... looks like some defective components.

Yep, I caught it as it was happening, no big issue (except for about 5 seconds of abject terror).  I'm just trying to figure out which components were faulty.
hero member
Activity: 675
Merit: 507
Freedom to choose
May 20, 2013, 09:36:02 AM
#2
wow! hope you and your property are safe... looks like some defective components.
hero member
Activity: 742
Merit: 500
May 20, 2013, 09:30:57 AM
#1
Here's my build:

Power: CORSAIR Enthusiast Series TX650 V2 650W ATX12V v2.31/ EPS12V v2.92 80 PLUS BRONZE Certified Active PFC High Performance Power Supply

Motherboard: GIGABYTE GA-F2A55M-HD2 FM2 AMD A55

APU: AMD A10-5800K Trinity 3.8GHz FM2 100W Quad-Core Desktop APU (CPU + GPU) with DirectX 11 Graphic AMD Radeon HD 7660D

Video Card: SAPPHIRE 100314-5L Radeon HD 6870 1GB GDDR5 PCI Express Video Card (One of the rebranded 5870s)


I was mining on the 6870 @ 950 MHz with around 400 MH/s using GUIMiner
I was mining on the APU with around 80 MH/s

Saturday evening, this happened to my motherboard:



These are two chips labeled DEQ1 and DEQ2 just above the CPU socket.

I've RMA'd the board, but I was only using 1 video card (two if you count the onboard one).  One other thing, my power supply would run even if the power switch was switched to off, so maybe my power supply is doing something funky.  I'm wondering wtf went wrong here, this build is only 4 months old and has been running just about nonstop since then with no issues. 
Jump to: