Bad Rubycons...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Super Nade
    Badcaps Veteran
    • Jun 2006
    • 294

    #1

    Bad Rubycons...

    A board arrived yesterday with a solitary bad cap. It was a Dell, S478 board. To my surprise, it was a Rubycon MCZ that had failed.






    So I fired up the soldering Iron and replaced it with a 1500uF, 16V UCC- LXZ. I didn't have a 6.3V in hand so I just had to make do with what was available. I'm not sure why the Rubycon failed? Possibilities include random chance, it being under-rated i.e needed a 16V instead of a 6.3V or just a bad batch.

    I exclusively use UCC/NCC in all my recap jobs (PSU's, MB's other devices..etc) and they have never failed me till date.





    The astute reader would observe the snake like trace on the PCB. I suspect it has something to do with minimizing EMI along that trace. Never seen anything like that before. Have a snake like pattern is not generally good due to the additional stray capacitance it introduces, but I suppose that does not matter here...
    Q6700 @ 3.6 GHz
    Zippy GSM-6600P
    Curcial Ballistix PC6400 (4 x 1Gb) Micron D9GMH
    Abit IP35Pro
    ATi HD4870
  • gonzo0815
    Badcaps Legend
    • Feb 2006
    • 1600

    #2
    Re: Bad Rubycons...

    May be this snaky traces are necessary, to keep signaling time in check wit the other lines.
    Have seen them often since i owned my first computer.

    Comment

    • gonzo0815
      Badcaps Legend
      • Feb 2006
      • 1600

      #3
      Re: Bad Rubycons...

      Regarding the MCZ i think it is a hot area, due too the linear voltage regulator heating up the cap.
      It is well known that high water low endurance caps are not suited very well for such applications.
      Most Asrock boards are famous for using linear voltage regulators vor Vmem & Vagp and indeed have this problem.
      On my Asrock DS II they alleviated this problem by using three not so low ESR caps at the same place instead of using just one.
      Last edited by gonzo0815; 10-05-2007, 06:20 AM.

      Comment

      • Phenos
        Member
        • Oct 2006
        • 46

        #4
        Re: Bad Rubycons...

        i've heared they use snake patterns to give the traces equal length with the other traces because the memory is paralel. It has something to do with latency sync i think. same as above post.

        Comment

        • Super Nade
          Badcaps Veteran
          • Jun 2006
          • 294

          #5
          Re: Bad Rubycons...

          Gonzo, why didn't the other three Caps on the opposite side blow up then? Also, wouldn't the RAM stick shield the cap from the heat?
          Q6700 @ 3.6 GHz
          Zippy GSM-6600P
          Curcial Ballistix PC6400 (4 x 1Gb) Micron D9GMH
          Abit IP35Pro
          ATi HD4870

          Comment

          • Per Hansson
            Super Moderator
            • Jul 2005
            • 5895
            • Sweden

            #6
            Re: Bad Rubycons...

            All memory controllers have "snake" traces

            This is because they are parallell interfaces, they are incredibly difficult to layout and the timing is paramount, all 168 traces times as many memory slots you have must have equal lengths else the board will have memory problems

            This is the sole reason mainboard layout is very difficult. Most of these designs are only made by Intel or AMD, the third party contractor just use their design (with a few rare exceptions)

            On the flip side the serial interfaces being introduced have none of these problems, and most of the time can cram more data through only 1/10 of the ammount of traces!
            "The one who says it cannot be done should never interrupt the one who is doing it."

            Comment

            • Super Nade
              Badcaps Veteran
              • Jun 2006
              • 294

              #7
              Re: Bad Rubycons...

              Good info fellas! Thanks!

              Now, the VRM seems a bit far from the Rubycon. Any other ideas on why it failed? I hope the problem is not intrinsic to the board and hopefully the UCC replacement stays alive longer than the poor Rubycon.
              Q6700 @ 3.6 GHz
              Zippy GSM-6600P
              Curcial Ballistix PC6400 (4 x 1Gb) Micron D9GMH
              Abit IP35Pro
              ATi HD4870

              Comment

              • severach
                Badcaps Legend
                • Aug 2007
                • 1055
                • USA

                #8
                Re: Bad Rubycons...

                That's a GX270 SFF board. Rubycons there fail quite often. Panasonics fail much less often which makes Panasonic outfitted boards more desirable.

                If it was under voltage it would have blown immediately.

                Every large Rubycon cap around the memory slots, processor, and heat sink are failure prone.

                Perhaps you're looking at the wrong VRM. Heat damage always surrounds the 13N03LA pair, Q1067 and Q22 which is visible in your picture. Q1067 barely visible behind the right memory slot is nearly touching your failed cap.

                My GX270 board has two short Rubycon 1500's at the other end of the memory slot.
                sig files are for morons

                Comment

                • gonzo0815
                  Badcaps Legend
                  • Feb 2006
                  • 1600

                  #9
                  Re: Bad Rubycons...

                  From your pic`s i see that the MOSFET between the Intel chip and the AGP? port is very close to the bad MCZ cap.
                  Furthermore it is clearly visible, that a massive coper layer is leading from the MOSFET to the bad cap too.
                  And there is my assumption, that probably several other massive coper layers are buried within the epoxied.

                  A linear converter does produce much more heat, then e.g. a MOSFET in a switching buck converter, i think this is obvious.
                  The MOSFEt is probably providing the 1,5v to the AGP port or it may supply the memory.
                  I have seen this design on countless low end boards from Asrock, ECS and probably from any other budget board producer.
                  And at least for the Asrock boards, most are developing problems with caps near those circuits after several years.

                  Combining the fact, that the MCZ series is a 2000h series @105°C i think the failure is inevitable, if my conclusions are correct and the cap was running hot.

                  From the pic`s provided, i can`t say much above the other caps, but i think it should not that hard to check the temperature either with your finger or may be with a thermometer may be after running some 3d apps with a beefy (power consumption wise) GFX card.
                  This could either support my theory or not.

                  Personally i would not assume, that any other cap, from a comparable series would last much longer then a Rubycon.
                  The only comparable series from Panasonic would be the FJ ones, which has yet to proof better at such applications, then those already widely used.
                  Last edited by gonzo0815; 10-05-2007, 07:35 PM.

                  Comment

                  • severach
                    Badcaps Legend
                    • Aug 2007
                    • 1055
                    • USA

                    #10
                    Re: Bad Rubycons...

                    Panasonic FL is what Dell is using.
                    sig files are for morons

                    Comment

                    • linuxguru
                      Badcaps Legend
                      • Apr 2005
                      • 1564

                      #11
                      Re: Bad Rubycons...

                      Aqueous electrolytics in high-temperature applications are bound to fail eventually. If the application doesn't call for ultra-low ESR or high ripple current, a non-aqueous cap like the Panasonic FC, Nichicon PW or NCC LXZ is a more durable alternative in hot-running SFF motherboards.

                      Comment

                      • Computer-Tech
                        New Member
                        • Aug 2009
                        • 6

                        #12
                        Re: Bad Rubycons...

                        Super Nade,
                        The Capacitor (C259) is the filter cap for the board video chip set.
                        ..
                        You should also replace C257 and C258 as well. If one of these caps is bad, then the other two are most likely bad (or will fail shortly).
                        ..
                        By the way you also need to replace C392 and C1194 (on the other side of the Memory/DIM slots). These should be 1,800 uF 6.3V 105 degree Caps with a dimension of 8mm x 20mm and 3.0mm lead spacing.
                        ..
                        The other high failure caps are the 1,800 uF 6.3V caps located between the CPU and Regulator heatsink. There are 9 each (easy to figure out which ones).
                        ...
                        There are also three 1,800 uF 16V 105 degree Caps hidden behind the Regulator heat sink. They have dimensions of 10mm wide x 20mm high and a 4 mm lead spacing. These are the Voltage Regulator Supply Filter Caps. These are the ones that give you the dual solid amber indicator lamps during power on self test.
                        ..
                        The only other problem caps are the three 820 uF 6.3 V caps, and the 680 uF 10V caps. these are also 105 degree caps. They should be replaced if visibly bulging or visibly damaged. If not leave them alone. NOTE: If a board has all of the 1,500 uF and 1,800 uF caps bad and visibly distorted and ruptured - I would replace the 820 uF and 680 uF caps as assurance that the board will not come back.
                        ..
                        God luck
                        ..
                        Dave Mason
                        Computer-Tech@phoenixcomputerlabs.com
                        ...

                        Comment

                        Related Topics

                        Collapse

                        • chth96
                          Is it possible bridging tiny broken trace
                          by chth96
                          When I assembled dreamcast I mistakenly fastened long bolt and It resulted in
                          cutting tiny trace.
                          This tiny trace(Total width of white coating is 5.5mm) is between R337,R343 and IC101 and it is covered with white coating in the below screenshot.


                          Firstly I tried to bridging tiny broken trace with my own eyes...But it is totally impossible..So a week ago, I ordered G1200 Digital Microscope and I magnified this tiny broken trace with it.

                          But It seems that It is really very tiny trace So I plan to order 0.1mm coper wire from aliexpress in order to bridging...
                          12-03-2022, 11:32 PM
                        • DXseekerMO
                          Failed UCC and Rubycon replacement on a Dell XPS410, equivalent?
                          by DXseekerMO
                          Hello, I'm working on an old Dell XPS410 with burst capacitors. I'm trying to source either an equivalent replacement, or a replacement that will work. It's been suggested to me to use Poly caps as a replacement, but I have no idea what to order or what will work.

                          If anyone has a link to where I can buy what I need that would be even better.

                          These are the caps that have burst:

                          Board location: C8BV, C26BV, C43BV
                          Brand: United Chemi Con
                          Series: KZG
                          Size: 10mm dia X 25mm height
                          Impedance: (ohms max/20c, 100kHz) .012
                          Ripple: 2800...
                          02-04-2022, 04:48 PM
                        • OOF DIO
                          ASUS FX505DV no power shorted at PWM controller Pin 3 VREG3 TPS51225C, need pinpointing of the short.
                          by OOF DIO
                          (If anyone has a functional boardview file of FX505DV/DU that would be helpful)
                          (Had 3 problems, now just 1)

                          I have no experience or knowledge and usage of tools to repair devices besides the entire past 12-10 days of researching, watching YouTube repair videos and troubleshooting this laptop motherboard. ChatGPT was used as a guide to ask questions.
                          I used boardviews of mostly FX505GD-M, and some FX505DU, FX505DD. Used schematics of FX505DU.

                          I had originally intended to replace the BQ24780s first (due to previous battery removal while benchmarking) but I...
                          04-19-2025, 05:03 PM
                        • Friend4Cap
                          Tuf gaming b550-pro damage circuit trace help!
                          by Friend4Cap
                          If anyone can help it will be very appreciate!!
                          Motherboard - (TUF GAMING B550-PRO) client connected Floppy Drive 4-Pin Power Connector to RGB_Header_1 +12V G . R . B and Burn one N6V8 and Damage all circuit trace, please check pictures, Motherboard not turning on & everything check ok, no short to ground, I need to repair all circuit trace and replace burn N6V8 but don't know where this 5 circuit trace connect to N6V8. If anyone with TUF GAMING B550-PRO can check. “Thank you in advance”...
                          05-07-2023, 05:38 PM
                        • modtool
                          Lenovo Legion 5 15ARH05H, NM-D281 Rev 1.0, "BIInitializeLibrary failed 0xc0000185" and bios freezing
                          by modtool
                          Dear members,
                          I have a problem with this machine that still I can't solve, I hope some of you can suggest me something.
                          I was the first one to open the machine and touch the mainboard, in fact the Lenovo seal was intact the first time that I unscrewed all the internal screws.
                          The ower told me that it was working very good until Windows kicked "something like a firmware update" (owner's words) then the system started acting weird.
                          When you try to start it, some seconds after having pressed the power button, Lenovo splashscreen appears, then after 1 second, in the...
                          01-15-2024, 08:56 PM
                        • Loading...
                        • No more items.
                        Working...