I bought a SV25 a while ago. After some time I discovered that many FV25 MB's have had problems with bad caps... but mine was still running just fine. But to be safe I decided to recap my board anyway.
I ordered a kit from Topcat and then recapped the board with the received Rubycon caps. Everything seemed fine - nice soldering, correct polarization and no visible damages.
Now to the problem... after the recap I now have frequent problems with that the computer hangs in the "Verifying DMI Pool Data" state.
BUT, if I disable the L2 cache - the computer boots (read that tip in
a forum). The person/persons that had this problem SOLVED it by changing
caps...
I have tried booting with an other PSU, and with an other CPU - but the problem persist... I even resoldered the caps.
Maybe the problem is one of the new caps? What suggestions do you have?
The capacitance of the new caps differ from the old caps. Maybe thats a problem?
The new caps:
3x 4700uF 10v 12,5mm
3x 3300uF 6.3v 10mm
5x 1000uF 10v 8mm
The original caps:
3x 3900uF 10v 12,5mm
3x 2700uF 6.3v 10mm
5x 1000uF 10v 8mm
I ordered a kit from Topcat and then recapped the board with the received Rubycon caps. Everything seemed fine - nice soldering, correct polarization and no visible damages.
Now to the problem... after the recap I now have frequent problems with that the computer hangs in the "Verifying DMI Pool Data" state.
BUT, if I disable the L2 cache - the computer boots (read that tip in
a forum). The person/persons that had this problem SOLVED it by changing
caps...
I have tried booting with an other PSU, and with an other CPU - but the problem persist... I even resoldered the caps.
Maybe the problem is one of the new caps? What suggestions do you have?
The capacitance of the new caps differ from the old caps. Maybe thats a problem?
The new caps:
3x 4700uF 10v 12,5mm
3x 3300uF 6.3v 10mm
5x 1000uF 10v 8mm
The original caps:
3x 3900uF 10v 12,5mm
3x 2700uF 6.3v 10mm
5x 1000uF 10v 8mm

Every CPU is known to be working before the testings.
.
But today, I’m making an exception here. Why? No idea. Perhaps only because the repair details are still “fresh” in my head… which is ironic, given this is a 16 year old monitor that hardly anyone will care about today. It is new to me, though.
Comment