BSOD and Gigabyte Capacitors
Collapse
X
-
Re: BSOD and Gigabyte Capacitors
Looks like Sanyo WF caps are the new Chemicon KZG - just took them a bit longer to go bad. Like the KZGs, all of the WF ones that went bad on my stuff have gone high capacitance (high internal leakage), especially the ones that sat more in storage. So I can confirm what Wester547 said above.
So I too doubt that those bulged WF caps were a result of a bad PSU.
Moreover, I've seen systems with completely gutless PSUs filled with bulged crap caps, and the motherboards crap caps survived and were within spec - multiple times.
I have found two socket 939 motherboards with Nichicon HM caps with a date code of year 2004 week 53. Yes. I said week 53, not a typo. Still working just fine on a Gigabyte motherboard. Must be a transitional production batch before the standard run of 2005 came out. Very strange indeed.
The only conclusion I can come to is that all electrolytics (according to the documents provided by the manufacturers), insofar as their useful life, are rated with 60% confidence (or -/+ 40% confidence). So even if you calculate the formula for useful life (based on the endurance life spec), it may not provide an accurate idea of how long the cap will actually last in the real world (although good caps will last longer than their rated lifespan).Last edited by Wester547; 06-02-2018, 10:37 PM.Comment
-
Re: BSOD and Gigabyte Capacitors
So KZG are prone to failing high capacitance / high leakage current in your experience, like bad Nichicon HM, HN, HZ, and Suncon WF? In my experience, most KZG (and KZJ) just go open circuit when they fail, and the capacitance plummets dramatically, although I've seen a few exceptions to that rule of thumb.
Yes, me too, but I don't doubt that when the PSU's output filter caps go bad, it puts significantly more stress on the general filter capacitors (and VRM input filtering capacitors) on the motherboard, somewhat shortening their lifespan. What I have also noticed about VRM input caps on many boards with poorly designed VRM sections is that they are pigeonholed right next to hot MOSFETs (the VRM output caps are located away from the FETs, closer to the CPU), which doesn't help at all.
Interesting. Some time ago, I happened across this image on the internet, which was posted ten years ago now, and it shows two bad 3300uF 6.3V Nichicon HM with the exact datecodes that yours have (H0453? Week 53, 2004, made in Ohno, Japan), along with a bulged and leaking 1000uF 16V KZJ (with a datecode of February 2nd, 2005). Alongside them was obviously a Rubycon MBZ which appeared fine.
The only conclusion I can come to is that all electrolytics (according to the documents provided by the manufacturers), insofar as their useful life, are rated with 60% confidence (or -/+ 40% confidence). So even if you calculate the formula for useful life (based on the endurance life spec), it may not provide an accurate idea of how long the cap will actually last in the real world (although good caps will last longer than their rated lifespan).Comment
-
Re: BSOD and Gigabyte Capacitors
So KZG are prone to failing high capacitance / high leakage current in your experience, like bad Nichicon HM, HN, HZ, and Suncon WF? In my experience, most KZG (and KZJ) just go open circuit when they fail, and the capacitance plummets dramatically, although I’ve seen a few exceptions to that rule of thumb.
But I can't say that applies for the smaller KZG caps, like the notoriously bad 6.3V, 820 uF. I think those loose capacitance and go O/C or high ESR more often, like you said.
The MOSFETs aren't always the hottest parts. Sometimes, it's the coils/inductor that run much hotter than the FETs. I find that on newer boards, it's these square "enclosed" inductors that run very hot, whereas the FETs may or may not run hot. On older boards, especially with large toroidal inductors, it's the other way around: FETs are usually hot (and on that note, usually the high-side FETs too, it seems, as they like to make the high-side filter caps toasty) and the inductors just warm.Last edited by momaka; 06-04-2018, 07:58 PM.Comment
-
Re: BSOD and Gigabyte Capacitors
The MOSFETs aren't always the hottest parts. Sometimes, it's the coils/inductor that run much hotter than the FETs. I find that on newer boards, it's these square "enclosed" inductors that run very hot, whereas the FETs may or may not run hot. On older boards, especially with large toroidal inductors, it's the other way around: FETs are usually hot (and on that note, usually the high-side FETs too, it seems, as they like to make the high-side filter caps toasty) and the inductors just warm.
I was referencing older boards when I meant sinkless, hot high side VRM FETs. Those will bake any adjacent electrolytics dry. What's also concerning is that many boards tend to use freestanding FETs, which is even worse for heat dissipation.Comment
-
Re: BSOD and Gigabyte Capacitors
I just had a ECS AM2 motherboard with input kzg's that showed no signs of going bad, but all the output caps (Sanyo WF's) were bloated. The computer would boot, and win7 started up, and in the middle, it would power off, with the power button still lit up but fans and system down. The KGZ's probably dried out and killed most of the sanyos
I replaced the bad WF's with used MCZ's and it booted fine. Just enough to change some windows devices so I could boot it off another motherboard that was a much higher quality (but different chipset, AMD AM3 Phenom II X4 955, where the ECS was nvidia, Athlon X2 5600+). Worked Great, no bluescreens. Reactivation went well (did have the sticker on the case.)
the old one also had a 160GB PATA, I cloned it to a 250SATA and enabled AHCI. Worked even better after that.Cap Datasheet Depot: http://www.paullinebarger.net/DS/
^If you have datasheets not listed PM meComment
-
Re: BSOD and Gigabyte Capacitors
I just had a ECS AM2 motherboard with input kzg's that showed no signs of going bad, but all the output caps (Sanyo WF's) were bloated. The computer would boot, and win7 started up, and in the middle, it would power off, with the power button still lit up but fans and system down. The KGZ's probably dried out and killed most of the sanyos
Those Sanyo WF failed because they are not so great, as stated earlier.
That said, was the original mobo an ECS MCP61PM-AM or MCP61SM-GM by any chance?? If yes, those also have lots of problems with the nVidia 6100/6150 chipset going bad over time (and really, any mobo with that chipset will have problems, unless it has a really nice big heatsink on it). The only way to stop or slow down that is to install a fan on the existing chipset heatsink or upgrade to a much bigger one (which can be a problem if you want to use the PCI and PCI-E slots, as that can block them).
In any case, don't chuck those boards, even if you see a dead one. A reflow of the chipset can get them going again. It was a widely-used board back in the day, so there is still a bit of demand for it from folks who are trying to get older PCs going again.
I replaced the bad WF's with used MCZ's and it booted fine. Just enough to change some windows devices so I could boot it off another motherboard that was a much higher quality (but different chipset, AMD AM3 Phenom II X4 955, where the ECS was nvidia, Athlon X2 5600+). Worked Great, no bluescreens. Reactivation went well (did have the sticker on the case.)Comment
Related Topics
Collapse
-
by DynaxSCHi,
I discovered a strange behaviour of GIGABYTE GA-H110M-S2 board.
General test conditions:
- Tested with Core i5 6500 and Core I7 6700K - no difference
- Default BIOS settings, but tried also altering several memory setting - does not change anything
What is wrong:
With BIOS F1 and F2 the board normally POST's and boots to Windows 11 with 2 x Patriot Viper Steel PVS416G440C9K RAM (4400MHZ, Samsung B-Die chips)
When BIOS upgraded to anything above F2 (ie. F20-F27b) the board POST stucks after 3 Debug Codes on Code C2... -
Thermal pad thickness for various laptop GPU / Graphics Cards
ASUS Dual RTX 2070 OC 8GB
ASUS ROG STRIX RTX 3080 OC
ASUS ROG STRIX RTX 3090
ASUS TUF Gaming RTX 3080 OC Edition
ASUS TUF GTX 1660 S-O6G GAMING
EVGA RTX 3060 Ti XC GAMING 8GB
EVGA RTX 3060 XC GAMING 12GB GDDR6
EVGA RTX 3080 FTW3 ULTRA GAMING
EVGA RTX 3080 TI FTW3 ULTRA GAMING
EVGA RTX 3090 XC3 ULTRA GAMING 24GB
Gainward RTX 2080 Phoenix GS Specs
Gainward RTX 3070 Phoenix 8GB
Gainward RTX 3080 Ti Phoenix
GIGABYTE AORUS RTX 3080 MASTER 10G
...-
Channel: Schematics and Boardviews
02-09-2024, 08:08 AM -
-
by dragon3xHi, I have some 32 bits computer motherboards that need repair, as they fail to
power on.
Here are some examples :
(N.B. "capacitors" indicated here are electrolytic capacitors located in the onboard
switching supply area).
(N.B. #2 : I could not find a 3300 microF aluminum-polymer with a higher voltage
than 6.3 V.)
1 - Motherboard #1 : this is an Asrock K7VT2 (socket A) that still works well. To put it on test
I replaced capacitors with aluminum-polymer.
3300 microF/6.3 V. x 4 replaced by 3300 microF/6.3 V. (KYOCERA... -
by momakaMore eBay specials: this time a Gigabyte GP-P450b 450W ATX PSU for $8 with free S&H. Listed “For part/not working”, as usual. Showed up in a beat up EVGA box without any padding… but that's understandable given the total price. PSU made it out fine without damage. It's a non-modular (yay!), pretty modern-day looking PSU with a black paint and all black cables (meh, not my favorite, but figure it's good to keep a few of these in case I do need one for a more modern PC build, just so my old gray boxes don't look too odd in there.)
And a shot of the label:... -
Hi Everyone,I need help with this strange Gigabyte laptop,it turns on with black screen and after 30sec fans on the Max for few seconds and it shuts down,I think the bios is bricked,They say it is Clevo under the hood,there is nowhere on motherboard what is the model which is strange,i will write S/N and P/N from the motherboard,thats only what is writen there and upload old bios,if anyone can help,Thanks!
Gigabyte A5 X1
From motherboard:
S/N: 1TNH55ER1350895
P/N: 6-77-NH55ERQY-D02-2CGB
On sticker from the back of the laptop:
S/N: SN21351J000657...-
Channel: BIOS Requests ONLY!
-
- Loading...
- No more items.
Comment