PS3 (Research/Experimental) - NEC/TOKIN Capacitors Replacement - YLOD

Timbo9876 said:
Unfortunately, it looks like a BGA issue. So a reball of the RSX or replacement of the RSX is required
Click to expand...
replaced 2nd rsx tokins get no signal about 15 seconds than ylod, sometimes 576p black screen with ylod. sometimes ylod immidately, after few times of powering on console gets hot, fan get louder (thats all with heatsink installed). can it be another issue and not rsx?
sorry for my bad english)
 
From the combination of error codes that your console is reporting (1601,1701 14FF) points strongly towards a BGA defect or faulty RSX chip. So it's highly unlikely to be anything else I'm afraid

Sent from my SM-F936B using Tapatalk
 
I have just received a CECHA00.

I have 31 error codes 1701, with the last code being given 2022, which I believe is the southbridge error.

1701 would normally report another code indicating the cause. This doesn't, so what are we to make of this?

Console has no damage and has never been opened.

Has 74 hours runtime.

Console has played the first two chapters of TLOU with no issues.

On Syscon, the fan is very quiet, with webman fan speed test to 32 percent, console stays under 65 degrees, so doesn't seem to have any overheating issues.

Any ideas, anyone?






Sent from my SM-F936B using Tapatalk
 
I don't have much experience with this, but I've used bottom preheater and a heat gun on top. at the end I touched the chip a little to make sure that it fell into place
 
karenjan99 said:
I don't have much experience with this, but I've used bottom preheater and a heat gun on top. at the end I touched the chip a little to make sure that it fell into place
Click to expand...
Did it move when you nudged it? If not, it's likely the RSX has been temporarily revived.

Either way, the 1002 error is likely to be tokins on the RSX side.

Sent from my SM-F936B using Tapatalk
 
not it not nudged. is it neccesary replace tokins of the rsx side? i tried put 5x 820 uf aluminium caps just for tests but nothing changed
i forget to say ylod is immidately
 
If it's immediate the the board may have a short caused by the reflow. Otherwise it maybe a faulty power supply.

Sent from my SM-F936B using Tapatalk
 
karenjan99 said:
i also tried psu from my old console still nothing, just try reflow again?
Click to expand...
No, the reflow isn't doing the motherboard any good. You now have a short somewhere on the board. You would now need to use a multimeter to try and find what's causing the short.

Sent from my SM-F936B using Tapatalk
 
Hey guys I followed Felix's delidding steps for the CELL and I believe my ps3 is overheating now. After about 20 min in game, I get the 3 beeps with red light. I'm wondering if I didn't use enough thermal paste on the IHS when he says to put the IHS on the heat sink first or if I just damaged the chip in some way. I ordered a TTL usb thing to solder to the board to see what exactly is going on, but should I continue with stress testing for the full 2hrs (i.e. turning the console back on after it overheats and loading a game) or just leave it alone for now?
 
i dont think you need to read syscon looks to me an overheat issue redo the steps. if you havent glue back ihs is very easy to see if the thermal paste cover all the diy.
 
So delidding again was pretty easy. Anything immediately stand out as wrong with is? Did I not use enough glue?
RV81zQG
 
need_ps3_help said:
Hey guys I followed Felix's delidding steps for the CELL and I believe my ps3 is overheating now. After about 20 min in game, I get the 3 beeps with red light. I'm wondering if I didn't use enough thermal paste on the IHS when he says to put the IHS on the heat sink first or if I just damaged the chip in some way. I ordered a TTL usb thing to solder to the board to see what exactly is going on, but should I continue with stress testing for the full 2hrs (i.e. turning the console back on after it overheats and loading a game) or just leave it alone for now?
Click to expand...
Is there thermal paste in between the die and the IHS?
 
no your overheat has nothing to do with poor ihs glue. (if it was poor and simply didnt dry completly) what is mater is the diy to be fully covered with paste. dont go cheap or poor there, use arctic mx-6 put a good amount on the diy. apply thermal silicone around the cpu substait and put ihs as better you can on the cpu put mx6 on ihs and as straight as you can slowly screw the heatsink
 
truemaster said:
no your overheat has nothing to do with poor ihs glue. (if it was poor and simply didnt dry completly) what is mater is the diy to be fully covered with paste. dont go cheap or poor there, use arctic mx-6 put a good amount on the diy. apply thermal silicone around the cpu substait and put ihs as better you can on the cpu put mx6 on ihs and as straight as you can slowly screw the heatsink
Click to expand...

I have interesting developments. I thought I knew what the issue was but not so anymore. I have a spare broken ps3 with an APS-226 power supply and the ps3 that I'm working on has the Z series one. I switched the Z in the working ps3 for the 226 at the same time I delidded and just for shits and giggles, I put its original psu back in and it was running fine for almost 30 min. I also accessed the SYSCON and my temps were around 78 - RSX and 76 - CPU while in game (ambient is probably 69-71 F). But all of a sudden it just shut off without the standby light coming back on. After about 5 min with the power cable out, I plugged it back in and the standby is on and I got to the xmb. I turned it off just in case, but here is the error log from SYSCON. I think a lot of these errors are from when I had the other psu in and kept trying to play a game, so the one error that sticks out to me is 1004 because it just shut off without any warning or sound. Is there any way to know for certain if it was the 1004 error?

at the time of this error log, the console thinks its 01-02-2012 8:50ish AM
Code: 
ofst[ 12]:err_code:0xffffffff, clock:0x0fe42c57  2008/06/12 18:49:59
ofst[ 16]:err_code:0xa0801004, clock:0x0fe43362  2008/06/12 19:20:02
ofst[ 20]:err_code:0xa0801004, clock:0x10940da5  2008/10/24 04:37:57
ofst[ 24]:err_code:0xa0801200, clock:0x122d48a9  2009/08/30 14:26:49
ofst[ 28]:err_code:0xa0801200, clock:0x1247dc00  2009/09/19 18:14:24
ofst[ 32]:err_code:0xa0801200, clock:0x1267cf2b  2009/10/13 23:52:11
ofst[ 36]:err_code:0xa0801200, clock:0x12c121c5  2009/12/20 17:56:21
ofst[ 40]:err_code:0xa0801200, clock:0x14185fce  2010/09/07 02:28:30
ofst[ 44]:err_code:0xa0801200, clock:0x1514ef17  2011/03/17 16:11:03
ofst[ 48]:err_code:0xa0801200, clock:0x15aa32cc  2011/07/08 21:27:40
ofst[ 52]:err_code:0xa0801200, clock:0x15b61b66  2011/07/17 22:15:02
ofst[ 56]:err_code:0xa0801200, clock:0x15c71170  2011/07/30 19:01:04
ofst[ 60]:err_code:0xa0801200, clock:0x15d9e024  2011/08/14 01:23:48
ofst[ 64]:err_code:0xa0801200, clock:0x161bd4a8  2011/10/03 02:04:24
ofst[ 68]:err_code:0xa0801200, clock:0x163ceee1  2011/10/28 04:41:05
ofst[ 72]:err_code:0xa0802022, clock:0x1723946e  2012/04/20 03:28:46
ofst[ 76]:err_code:0xa0802022, clock:0x172db490  2012/04/27 19:48:32
ofst[ 80]:err_code:0xa0802022, clock:0x172e0d7f  2012/04/28 02:07:59
ofst[ 84]:err_code:0xa0802022, clock:0x1735d5df  2012/05/03 23:48:47
ofst[ 88]:err_code:0xa0802022, clock:0x17372c60  2012/05/05 00:10:08
ofst[ 92]:err_code:0xa0802022, clock:0x17542e59  2012/05/27 00:14:17
ofst[ 96]:err_code:0xa0802022, clock:0x1773e19f  2012/06/20 01:19:27
ofst[100]:err_code:0xa0802022, clock:0x18c5455a  2013/03/02 23:18:50
ofst[104]:err_code:0xa0802022, clock:0x193ced63  2013/06/01 17:35:31
ofst[108]:err_code:0xa0801001, clock:0x0b488ddd  2005/12/31 00:31:25
ofst[112]:err_code:0xa0801001, clock:0x0b489066  2005/12/31 00:42:14
ofst[116]:err_code:0xa0801001, clock:0x0b489fc0  2005/12/31 01:47:44
ofst[120]:err_code:0xa0801001, clock:0x0b488932  2005/12/31 00:11:30
ofst[124]:err_code:0xa0801001, clock:0x0b489839  2005/12/31 01:15:37
ofst[  0]:err_code:0xa0801001, clock:0x0b494a33  2005/12/31 13:54:59
ofst[  4]:err_code:0xa0801001, clock:0x0b4887f2  2005/12/31 00:06:10
ofst[  8]:err_code:0xa0801001, clock:0x0b488b4b  2005/12/31 00:20:27

edited: changed error log to the response from internal command "errlog"
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top