Page 1 of 2 12 LastLast
Results 1 to 16 of 21

Thread: Less than 6 months and my new PC caught on fire

  1. #1
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Unhappy Less than 6 months and my new PC caught on fire

    No, I do not jest.





    Also did some damage to the GPU above it, but the card appears to still work as I'm using it in my old machine, although I haven't tested the 3D capabilities yet. (sadly I didn't take a picture of this before I put it back in my case, and right now I want to get this answered first)

    So where do I stand? I know the mobo is fried (literally), but I can't check the CPU and RAM in my old machine as the old mobo won't support them. Everything else appears to be OK though. Can I only RMA the mobo as it's the only obvious item that is faulty?

  2. #2
    Senior Member
    Join Date
    Jul 2003
    Posts
    11,599
    Thanks
    763
    Thanked
    476 times in 328 posts

    Re: Less than 6 months and my new PC caught on fire

    Did you get a PSU cable with the machine, there was a thread the otherday about one that burnt a hole in itself, could be connected.

  3. #3
    Oh Crumbs.... Biscuit's Avatar
    Join Date
    Feb 2007
    Location
    N. Yorkshire
    Posts
    11,193
    Thanks
    1,394
    Thanked
    1,091 times in 833 posts
    • Biscuit's system
      • Motherboard:
      • MSI B450M Mortar
      • CPU:
      • AMD 2700X (Be Quiet! Dark Rock 3)
      • Memory:
      • 16GB Patriot Viper 2 @ 3466MHz
      • Storage:
      • 500GB WD Black
      • Graphics card(s):
      • Sapphire R9 290X Vapor-X
      • PSU:
      • Seasonic Focus Gold 750W
      • Case:
      • Lian Li PC-V359
      • Operating System:
      • Windows 10 x64
      • Internet:
      • BT Infinity 80/20

    Re: Less than 6 months and my new PC caught on fire

    Quote Originally Posted by [GSV]Trig View Post
    Did you get a PSU cable with the machine, there was a thread the otherday about one that burnt a hole in itself, could be connected.
    i doubt its a connected issue. I think the issue with the power cables is that they are not truly specced for the currents being sent down them, this is internal to the system so if the 'cable' on the circuit board isnt up to scratch then its a manufacturing fault in the hardware rather than a dodgily thrown in power cable

    Looking at the pic, it looks to me like a capacitor is the cause of the issue.

  4. #4
    Senior Moment blueball's Avatar
    Join Date
    Aug 2005
    Location
    Edinburgh
    Posts
    2,426
    Thanks
    846
    Thanked
    379 times in 294 posts
    • blueball's system
      • Motherboard:
      • Asus Z390A
      • CPU:
      • i9-9900KS
      • Memory:
      • Kingston 64GB (2x32GB) DDR4 2400MHz
      • Storage:
      • 2TB Samsung 970 EVO Plus NVMe PCIE M.2 plus Samsung 860 EVO 4TB SSD
      • Graphics card(s):
      • ASUS TUF RTX 3080 Ti GAMING OC
      • PSU:
      • Corsair HX850 850 W Full Modular 80 Plus Platinum
      • Case:
      • Corsair Carbide 330R Ultra Silent Midi Tower
      • Operating System:
      • Win 10 Pro x64
      • Monitor(s):
      • IIYAMA 3461WQ IPS 34" 3440x1440 plus BenQ GW2765HT IPS 27" 2560x1440
      • Internet:
      • Plusnet 28Mb

    Re: Less than 6 months and my new PC caught on fire

    It is possible that the USB cables have been damaged by heat, you might need to check them and include it in claim if they are.

    TBH I would return case as well
    Rgds,

    BB
    Hexus Trust here and here

  5. #5
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Re: Less than 6 months and my new PC caught on fire

    Well, the front USB ports haven't been working for some time, I think I physically damaged it on the case, so I cannot check.

    Here are some more pics of the damage caused by the fire:



    I am very concerned about the GPU, it has clearly charred the metal casing and I have no clear indication of damage done to the internals, if any.



    It's only a case, so it's only aesthetic damage, but still it shows how worryingly hot the fire was (I didn't mention earlier this happened whilst the PC was idling and I was not in the house, I dread to think what could've happened had the fire been any worse).



    Just another pic of the mobo, hopefully a bit clearer of the damage caused.

  6. #6
    Senior Moment blueball's Avatar
    Join Date
    Aug 2005
    Location
    Edinburgh
    Posts
    2,426
    Thanks
    846
    Thanked
    379 times in 294 posts
    • blueball's system
      • Motherboard:
      • Asus Z390A
      • CPU:
      • i9-9900KS
      • Memory:
      • Kingston 64GB (2x32GB) DDR4 2400MHz
      • Storage:
      • 2TB Samsung 970 EVO Plus NVMe PCIE M.2 plus Samsung 860 EVO 4TB SSD
      • Graphics card(s):
      • ASUS TUF RTX 3080 Ti GAMING OC
      • PSU:
      • Corsair HX850 850 W Full Modular 80 Plus Platinum
      • Case:
      • Corsair Carbide 330R Ultra Silent Midi Tower
      • Operating System:
      • Win 10 Pro x64
      • Monitor(s):
      • IIYAMA 3461WQ IPS 34" 3440x1440 plus BenQ GW2765HT IPS 27" 2560x1440
      • Internet:
      • Plusnet 28Mb

    Re: Less than 6 months and my new PC caught on fire

    There is no telling how much the life of the GPU has been shortened by the heat damage so I would claim for that as well.
    Rgds,

    BB
    Hexus Trust here and here

  7. #7
    HEXUS.social member Agent's Avatar
    Join Date
    Jul 2003
    Location
    Internet
    Posts
    19,168
    Thanks
    735
    Thanked
    1,607 times in 1,045 posts

    Re: Less than 6 months and my new PC caught on fire

    http://images.anandtech.com/doci/401...PRO_2D_H_x.jpg

    Its hard to tell from the pics, but it looks like the voltage regulator between the 2 slots has gone. You can see the square that should be there in the pic I've linked.

    If this has gone, then they do go with a boom. It's really one of the parts you don't want to fail on a PCB
    Quote Originally Posted by Saracen View Post
    And by trying to force me to like small pants, they've alienated me.

  8. #8
    Moderator Mick@SCAN's Avatar
    Join Date
    Aug 2007
    Posts
    585
    Thanks
    35
    Thanked
    79 times in 64 posts
    • Mick@SCAN's system
      • Motherboard:
      • Gigabyte GA-Z87X-OC
      • CPU:
      • i5 4670k @ 4.7 Ghz
      • Memory:
      • 16GB Corsair Vengeance LP 1600
      • Storage:
      • 120GB Samsung 840 / 2TB Seagate SATA III ST2000DM001 / 120GB Vertex Plus
      • Graphics card(s):
      • 8GB MSI 290X
      • PSU:
      • Enermax Modular Infiniti 650Watt
      • Case:
      • Fractal Design ARC MIDI R2 Tower Case
      • Operating System:
      • Windows 10
      • Monitor(s):
      • Iiyama ProLite G2773HS-2
      • Internet:
      • Virgin Media 200Mb

    Re: Less than 6 months and my new PC caught on fire

    Quote Originally Posted by Allen View Post
    No, I do not jest.





    Also did some damage to the GPU above it, but the card appears to still work as I'm using it in my old machine, although I haven't tested the 3D capabilities yet. (sadly I didn't take a picture of this before I put it back in my case, and right now I want to get this answered first)

    So where do I stand? I know the mobo is fried (literally), but I can't check the CPU and RAM in my old machine as the old mobo won't support them. Everything else appears to be OK though. Can I only RMA the mobo as it's the only obvious item that is faulty?
    Allen,

    I am sorry to hear about the issues you are having, management are currently looking into this issue for you and will be in contact shortly.

    Kind regards,

  9. #9
    Moderator Mick@SCAN's Avatar
    Join Date
    Aug 2007
    Posts
    585
    Thanks
    35
    Thanked
    79 times in 64 posts
    • Mick@SCAN's system
      • Motherboard:
      • Gigabyte GA-Z87X-OC
      • CPU:
      • i5 4670k @ 4.7 Ghz
      • Memory:
      • 16GB Corsair Vengeance LP 1600
      • Storage:
      • 120GB Samsung 840 / 2TB Seagate SATA III ST2000DM001 / 120GB Vertex Plus
      • Graphics card(s):
      • 8GB MSI 290X
      • PSU:
      • Enermax Modular Infiniti 650Watt
      • Case:
      • Fractal Design ARC MIDI R2 Tower Case
      • Operating System:
      • Windows 10
      • Monitor(s):
      • Iiyama ProLite G2773HS-2
      • Internet:
      • Virgin Media 200Mb

    Re: Less than 6 months and my new PC caught on fire

    Allen,

    Having taken a look at your submitted photos it would appear that the USB connecters have been attached to the firewire port on the motherboard, this has in no doubt caused the damaged components. In this instance Scan would not be liable for replacement of any damage components caused by end user error.

    Kind regards,

  10. #10
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Re: Less than 6 months and my new PC caught on fire

    Why the hell do they make FW connectors identical to USB if plugging the wrong cable in can cause so much damage?!?!

    There's no way I can afford to replace this for at least a few months what with moving out soon, and the components won't work on my old mobo, so I feel right now like I've thrown away a few hundred quid.


  11. #11
    King of the Juice Platinum's Avatar
    Join Date
    Jul 2003
    Location
    Chesterfield
    Posts
    3,769
    Thanks
    713
    Thanked
    89 times in 74 posts
    • Platinum's system
      • Motherboard:
      • Asus X99 Deluxue
      • CPU:
      • Core i7 5930k @ 4GHz
      • Memory:
      • 32gb Crucial 2400MHz
      • Storage:
      • 256gb Samsung SP941, 1tb MX500 Crucial SSD, 240gb Intel 730 SSD
      • Graphics card(s):
      • Sapphire R9 Fury OC
      • PSU:
      • 750 Watt Corsair HX
      • Case:
      • Corsiar 750D
      • Operating System:
      • Windows 10 Pro
      • Monitor(s):
      • Dell 2408WFP
      • Internet:
      • 18Mb

    Re: Less than 6 months and my new PC caught on fire

    I thought the pinout on Firewire headers was different from USB but looking at the pics that's not the case, still they are a different colour and are clearly labelled on the mobo...
    Salazaar : <Touching wood as I write this...>


  12. #12
    G4Z
    G4Z is offline
    I'dlikesomebuuuurgazzzzzz G4Z's Avatar
    Join Date
    Sep 2003
    Location
    geordieland
    Posts
    3,172
    Thanks
    225
    Thanked
    141 times in 93 posts
    • G4Z's system
      • Motherboard:
      • Gigabyte GA 965P-DS3
      • CPU:
      • Intel Core 2 Quad Q6600
      • Memory:
      • 4gb DDR2 5300
      • Storage:
      • 2.5Tb
      • Graphics card(s):
      • Gigabyte HD4870 512mb
      • PSU:
      • Tagan 470W
      • Case:
      • Thermaltake Tsunami Dream
      • Operating System:
      • Vista 64bit
      • Monitor(s):
      • Dual Acer 24" TFT's
      • Internet:
      • 16mb sky ADSL2

    Re: Less than 6 months and my new PC caught on fire

    Yeah but does it say in the manual that plugging in USB to firewire pins can cause a fire?

    I doubt it.
    HEXUS FOLDING TEAM It's EASY

  13. #13
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Re: Less than 6 months and my new PC caught on fire

    Mick, can you please confirm that this would definitely be the cause even if nothing was plugged into the front USB ports? As far as I am aware, there would've been no draw on the power if nothing was plugged in?

    I haven't had the front ports working for ages, I thought it was to do with me knocking them when the fascia of the case was off, don't even know why I bothered plugging the damn USB header cable in...

    Does anyone know if I would have any luck raising a complaint with Asus directly?

  14. #14
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Re: Less than 6 months and my new PC caught on fire

    Quote Originally Posted by G4Z View Post
    Yeah but does it say in the manual that plugging in USB to firewire pins can cause a fire?

    I doubt it.
    I just checked, it says:
    Never connect a USB cable to the IEEE 1394a connector. Doing so will damage the motherboard.
    Damage the motherboard != cause a fire which has the potential of doing a lot more damage than it did.

    As I said, I am willing to hold my hands up and admit fault here, I plugged the wrong cable in. But I still think it's terrible that they use identical connectors, especially when even under zero load it can cause a fire!

    I think I am going to write to Asus. I may get nowhere, but they need to know this is possible.

  15. #15
    Registered+
    Join Date
    Sep 2003
    Location
    Bolton
    Posts
    1,478
    Thanks
    168
    Thanked
    90 times in 74 posts

    Re: Less than 6 months and my new PC caught on fire

    The exact warning in the manual is:

    Never connect a USB cable to the IEEE 1394a connector. Doing so will damage the motherboard!

    That's an exact quote from the manual word for word its on page 2-23, under header 6.

  16. #16
    HEXUS.social member Allen's Avatar
    Join Date
    Nov 2003
    Location
    Brighton
    Posts
    8,536
    Thanks
    363
    Thanked
    262 times in 168 posts
    • Allen's system
      • Motherboard:
      • ASUS Maximus VIII Gene
      • CPU:
      • Intel Core i5 6600K
      • Memory:
      • 2 x 8GB Kingston HyperX Predator DDR4-3000
      • Storage:
      • 256GB Samsung 950 PRO NVMe M.2 (OS) + 2 x 512GB Samsung 960 EVO in RAID 0 (Games)
      • Graphics card(s):
      • ASUS ROG Strix GeForce GTX 1080 Ti OC
      • PSU:
      • XFX P1-650X-NLG9 XXX 650W Modular
      • Case:
      • Fractal Design Node 804
      • Operating System:
      • Windows 10 Home 64-bit
      • Monitor(s):
      • 27" BenQ XL2730Z + 23" Dell U2311H
      • Internet:
      • Virgin Media 200Mbps

    Re: Less than 6 months and my new PC caught on fire

    Hi Wesley,

    I see that, but don't you think "damage the motherboard" is a slight understatement in this case? It burnt the case and the graphics card too and I can't tell if it's working or not, neither can I confirm if the CPU or RAM are working, although as long as this fire didn't cause a short I doubt they will be affected.

    Please don't get me wrong, I may be continuing this thread on the Scan area of the forums, but my replies do not reflect my attitude towards Scan. I have been a long and happy customer of Scan and this has not changed that.

    If indeed the fault is my own then I will end up paying for it, but I just cannot see how plugging in a USB connector to the wrong port can cause a fire, especially since there was nothing plugged in to the USB port and the line should've been dead.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •