PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

Please help!

I have a CECHH01 with a recent YLOD (first time it happened in March 2024) after 16 years of use. Only opened for thermal paste replacement around year 4 with no other issue. I retrieved error log and performed a bringup following Felix Syscon tutorial. I noticed the timestamps in the log are quite old (2009, 2010, 2014 when the PS3 was working), so I am not sure if those are real or if there is something wrong with the internal clock.

Any help would be much appreciated!

Code: 
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0802203, clock:0x145cd24a  2010/10/29 00:31:06
ofst[  4]:err_code:0xa0801004, clock:0x1257f783  2009/10/01 23:28:03
ofst[  8]:err_code:0xa0801002, clock:0x1ba243dd  2014/09/09 23:03:57
ofst[ 12]:err_code:0xa0801701, clock:0x1ba2454c  2014/09/09 23:10:04
ofst[ 16]:err_code:0xa0801601, clock:0x1ba2454c  2014/09/09 23:10:04
ofst[ 20]:err_code:0xa0404412, clock:0x1ba24ae0  2014/09/09 23:33:52
ofst[ 24]:err_code:0xa0403034, clock:0x1ba24ae0  2014/09/09 23:33:52
ofst[ 28]:err_code:0xa0404412, clock:0x1ba24af2  2014/09/09 23:34:10
ofst[ 32]:err_code:0xa0403034, clock:0x1ba24af2  2014/09/09 23:34:10
ofst[ 36]:err_code:0xa0404412, clock:0x1ba25051  2014/09/09 23:57:05
ofst[ 40]:err_code:0xa0403034, clock:0x1ba25051  2014/09/09 23:57:05
ofst[ 44]:err_code:0xa0404412, clock:0x1ba2518b  2014/09/10 00:02:19
ofst[ 48]:err_code:0xa0403034, clock:0x1ba2518b  2014/09/10 00:02:19
ofst[ 52]:err_code:0xa0404412, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0404412, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$

>$ becount
becount
Bringup : 2657 times
Shutdown: 2637 times
Power-on: 147day 21hour 41min 44sec
[mullion]$
Press Ctrl+C to exit
>$

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404412
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$



>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404412
[ERROR]: 0xa0403034

[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$
 
RIP-Felix said:
There is a service manual for the COK-002. In it you can find wiring shematic and labels for all the SMDs in the console. Please refer to it and tell use which components you knocked off. A picture would be helpful, but until you reach 10 posts on the forum you cannot upload them directly. You will have to use imgur or another picture hosting service and link.

2110 is a clock subsystem error usually stemming from an issue at or around 3.3v/5v Misc. It's very likely caused by whatever SMD you knocked off.
Click to expand...
Thanks. From the motherboard diagram, it's COK002 side B and the values of the parts are C1158 and C1438. I can't find any other reference to them aside from there. Another test I did this evening was checking F6001, F6303 and F6301. The latter two checked out ok with a beep on the continuity test and low resistance readings. F6001 was into the kilo and M Ohms and didn't beep so that's blown. I'm trying to source a replacement fuse, are the specs I need 5A 32VDC and 3216 shell? If there's anymore or you can recommend some, please let me know. Also if you can let me know the values of the other two SMD's C1158 and C1438, I'll get replacements if necessary. Again, any help is appreciated. I'm going to check C6019 and C6020 now.
 
RIP-Felix said:
A thermal camera is helpful in finding shorts. I had a similar set of those errors on a KTE-001 with a voltage regulator related short. It feeds to the bluetooth/wifi chip. Which are prone to fail. IMO the most common issue with slim/SS models (except 20xx and 21xx, which have a different, more reliable version).


In my case that step down converter was so bad off it was throwing A0A02124 and A0002124. Immediately after plugging in or after power on. It didnt make it into XMB where the error message could show.
Click to expand...

Thanks RIP-Felix. I believe the regulator might have just died in this case. I had the regular wifi/bluetooth standby regulator fail which I replaced. Everything worked (but just the av) for a day and then the current problem of no display and the regulator reading low output.

At this point I've removed the filter from the output of that rail on the regulator with no change so I believe the regulator itself is damaged. I don't measure any shorts on the hdmi or av chip though so at this point I'm just guessing whether the hdmi chip failed and took out the regulator or the av chip did. I'm going to leave the filter off for now and replace the regulator to ensure that part of the circuit is working before I go replacing the chips.

I agree, I might want to invest in thermal imaging to determine which chip is at fault to avoid parts swapping though. Strange issue though.

JRm1rkS
 
Stefan Wagner said:
Thanks RIP-Felix. I believe the regulator might have just died in this case. I had the regular wifi/bluetooth standby regulator fail which I replaced. Everything worked (but just the av) for a day and then the current problem of no display and the regulator reading low output.

At this point I've removed the filter from the output of that rail on the regulator with no change so I believe the regulator itself is damaged. I don't measure any shorts on the hdmi or av chip though so at this point I'm just guessing whether the hdmi chip failed and took out the regulator or the av chip did. I'm going to leave the filter off for now and replace the regulator to ensure that part of the circuit is working before I go replacing the chips.

I agree, I might want to invest in thermal imaging to determine which chip is at fault to avoid parts swapping though. Strange issue though.

JRm1rkS
Click to expand...

As an update, looks like there is no suitable replacement for the part. Can someone confirm it actually should be 5V at that pin? I want to make sure this is actually the problem before I go digging. I really need to invest in a working unit just used for comparison....
 
i recently started my cechl04 that have worked flawlessly before, but now i get ylod when i start any game.
please help me figure what these codes mean

Error Log
01: A0802124 Sun Jan 1 00:33:05 2006
02: A0801002 Sun Jan 1 00:33:04 2006
03: A0802124 Sun Jan 1 00:09:05 2006
04: A0801002 Sun Jan 1 00:09:04 2006
05: A0802124 Sun Jan 1 03:11:19 2006
06: A0801002 Sun Jan 1 03:11:18 2006
07: A0802124 Sun Jan 1 03:03:32 2006
08: A0802124 Sun Jan 1 03:03:32 2006
09: A0801002 Sun Jan 1 03:03:31 2006
10: A0802124 Sun Jan 1 00:31:07 2006
11: A0802124 Sun Jan 1 00:31:07 2006
12: A0801002 Sun Jan 1 00:31:06 2006
13: A0802022 Sun Jan 1 00:30:47 2006
14: A0802124 Sun Jan 1 00:28:23 2006
15: A0802124 Sun Jan 1 00:28:23 2006
16: A0801002 Sun Jan 1 00:28:22 2006
17: A0802022 Sun Jan 1 00:28:03 2006
18: A0802124 Sun Jan 1 00:00:10 2006
19: A0801002 Sun Jan 1 00:00:10 2006
20: A0802022 Tue Jun 18 16:18:01 2019
21: A0802022 Tue Jun 18 16:12:21 2019
22: A0801200 Mon Jun 17 21:02:20 2019
23: A0802022 Mon Jun 17 20:58:23 2019
24: A0802022 Mon Jun 17 20:53:52 2019
25: A0802022 Mon Jun 17 20:52:55 2019
26: FFFFFFFF Fri Dec 31 23:59:59 1999
27: FFFFFFFF Fri Dec 31 23:59:59 1999
28: FFFFFFFF Fri Dec 31 23:59:59 1999
29: FFFFFFFF Fri Dec 31 23:59:59 1999
30: FFFFFFFF Fri Dec 31 23:59:59 1999
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999
 
Krieger said:
Did I destroy this motherboard or can this still be saved? The Rx solder came off.

ps3-fat-crop.jpg
Click to expand...
This is why you dont want to solder the breadboard pins directly to the pads. There's no strain relief. It tears right off if it gets levered.

The trace is still there. So you could repair the pad or connect to it at the via. But be careful at this point it'll be hanging on by a thread
 
Last edited:
wizar said:
i recently started my cechl04 that have worked flawlessly before, but now i get ylod when i start any game.
please help me figure what these codes mean

Error Log
01: A0802124 Sun Jan 1 00:33:05 2006
02: A0801002 Sun Jan 1 00:33:04 2006
03: A0802124 Sun Jan 1 00:09:05 2006
04: A0801002 Sun Jan 1 00:09:04 2006
05: A0802124 Sun Jan 1 03:11:19 2006
06: A0801002 Sun Jan 1 03:11:18 2006
07: A0802124 Sun Jan 1 03:03:32 2006
08: A0802124 Sun Jan 1 03:03:32 2006
09: A0801002 Sun Jan 1 03:03:31 2006
10: A0802124 Sun Jan 1 00:31:07 2006
11: A0802124 Sun Jan 1 00:31:07 2006
12: A0801002 Sun Jan 1 00:31:06 2006
13: A0802022 Sun Jan 1 00:30:47 2006
14: A0802124 Sun Jan 1 00:28:23 2006
15: A0802124 Sun Jan 1 00:28:23 2006
16: A0801002 Sun Jan 1 00:28:22 2006
17: A0802022 Sun Jan 1 00:28:03 2006
18: A0802124 Sun Jan 1 00:00:10 2006
19: A0801002 Sun Jan 1 00:00:10 2006
20: A0802022 Tue Jun 18 16:18:01 2019
21: A0802022 Tue Jun 18 16:12:21 2019
22: A0801200 Mon Jun 17 21:02:20 2019
23: A0802022 Mon Jun 17 20:58:23 2019
24: A0802022 Mon Jun 17 20:53:52 2019
25: A0802022 Mon Jun 17 20:52:55 2019
26: FFFFFFFF Fri Dec 31 23:59:59 1999
27: FFFFFFFF Fri Dec 31 23:59:59 1999
28: FFFFFFFF Fri Dec 31 23:59:59 1999
29: FFFFFFFF Fri Dec 31 23:59:59 1999
30: FFFFFFFF Fri Dec 31 23:59:59 1999
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999
Click to expand...

Bad RSX tokin, most likely.
 
Stefan Wagner said:
Can someone confirm that pin 5 of Mitsumi 348A is 5V and pin 4 is 3.3V? I'm measuring 3.3V on pin 4 and 1.1-1.2V on pin 5. I desoldered the filter right under the regulator and it's still outputting 1.1V. I also tried de-soldering the HDMI IC MN8647091 with no change. Unless one of the capacitors or resistors in that circuit are defective, it sounds like it could be the regulator?

My board is a JSD-001 and the only syscon logs are 2124 and 2024. It appears to boot fine but there is no display on either HDMI or AV. It worked for a while on AV only then that stopped working too. Not sure where to troubleshoot. I've got a good spare HDMI IC, but wanting to troubleshoot more before going through the hassle of swapping it in.
Click to expand...
Refer here to find Datasheet for that regulator. Yes, it would make sense for Vout 1 (pin4) to be 3.3v. Possible for Vout 2 to be 5v. Wiki doesn't seem to be sure which is supposed to be which. Pins 4 & 5 are marked with a question mark as to which is 3.3 and which is 5v. But 1.2v doesn't seem correct according to the wiki. From the datasheet, the lowest it can output is 1.2v, which may be why you are getting 1.2v on that pin. The Regulator may be defective, or one of the resistors that set the output voltage could be.

I don't have a JSD-001 board to check. Or at least I don't think I do.
 
Henry Jones Jr said:
Please help!

I have a CECHH01 with a recent YLOD (first time it happened in March 2024) after 16 years of use. Only opened for thermal paste replacement around year 4 with no other issue. I retrieved error log and performed a bringup following Felix Syscon tutorial. I noticed the timestamps in the log are quite old (2009, 2010, 2014 when the PS3 was working), so I am not sure if those are real or if there is something wrong with the internal clock.

Any help would be much appreciated!

Code: 
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[  0]:err_code:0xa0802203, clock:0x145cd24a  2010/10/29 00:31:06
ofst[  4]:err_code:0xa0801004, clock:0x1257f783  2009/10/01 23:28:03
ofst[  8]:err_code:0xa0801002, clock:0x1ba243dd  2014/09/09 23:03:57
ofst[ 12]:err_code:0xa0801701, clock:0x1ba2454c  2014/09/09 23:10:04
ofst[ 16]:err_code:0xa0801601, clock:0x1ba2454c  2014/09/09 23:10:04
ofst[ 20]:err_code:0xa0404412, clock:0x1ba24ae0  2014/09/09 23:33:52
ofst[ 24]:err_code:0xa0403034, clock:0x1ba24ae0  2014/09/09 23:33:52
ofst[ 28]:err_code:0xa0404412, clock:0x1ba24af2  2014/09/09 23:34:10
ofst[ 32]:err_code:0xa0403034, clock:0x1ba24af2  2014/09/09 23:34:10
ofst[ 36]:err_code:0xa0404412, clock:0x1ba25051  2014/09/09 23:57:05
ofst[ 40]:err_code:0xa0403034, clock:0x1ba25051  2014/09/09 23:57:05
ofst[ 44]:err_code:0xa0404412, clock:0x1ba2518b  2014/09/10 00:02:19
ofst[ 48]:err_code:0xa0403034, clock:0x1ba2518b  2014/09/10 00:02:19
ofst[ 52]:err_code:0xa0404412, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0404412, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$

>$ becount
becount
Bringup : 2657 times
Shutdown: 2637 times
Power-on: 147day 21hour 41min 44sec
[mullion]$
Press Ctrl+C to exit
>$

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404412
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$



>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404412
[ERROR]: 0xa0403034

[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$
Click to expand...
Please RIP-Felix don't forget about my case. Your expert opinion is appreciated!
 
RIP-Felix said:
This is why you dont want to solder the breadboard pins directly to the pads. There's no strain relief. It tears right off if it gets levered.

The trace is still there. So you could repair the pad or connect to it at the via. But be careful at this point it'll be hanging on by a thread
Click to expand...

Can I leave it like this? I know I would loose access to SYSCON until I fix it. But would the PS3 boot normally if everything else works?
 
Henry Jones Jr said:
[POWERSEQ] Error : BitTraining RSX:RRAC:RX1:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404412
[ERROR]: 0xa0403034
Click to expand...
You have a failed 90nm GPU (RSX).
 
RIP-Felix said:
You have a failed 90nm GPU (RSX).
Click to expand...
Thank you. So should I go for a reballing assuming it won't last? I could contribute to your poll… I see that the very first error before 3034s was a 1002… should I consider also replacing the NEC Tokins? Or in this case the 1002 was for a different reason? The chances of Tokins and RSX BGA/bump issues happening simultaneously is very low, right?
 
Henry Jones Jr said:
Thank you. So should I go for a reballing assuming it won't last? I could contribute to your poll… I see that the very first error before 3034s was a 1002… should I consider also replacing the NEC Tokins? Or in this case the 1002 was for a different reason? The chances of Tokins and RSX BGA/bump issues happening simultaneously is very low, right?
Click to expand...

An H model is nonBC, so not worth wasting a reliable 65 or 40nm GPU on IMO. Unless it was a special edition or has sentimental value to you. You could try a reball if you want. You would have more lasting results replacing it with a known working 90nm. Could last a good long time. Many have lived 15 years without issue. YLOD isn't as prevelent as RROD.

Tokins can be failing for a while and then the RSX finally dies. Reflows and rework can damae them and hasten their death. Depending on the history of the console, it's not unusual. Conicidence can happen too.

There's a remote possability the 1002 was triggered by the RSX joint failure. It only occured once and with the 1601/1701 that are indicative of a GPU joint failure while the console was on at the time. It may have been associatve, not diagnostic in this case.
 
2nd PS3 I've took to this forum, CECHH02 YLOD, with some small damage similar to liquid damage that has caused some minor corrosion to a small section of the ground plane. Have unlocked the syscon and run the necessary commands.
Code: 
becount

Bringup : 1586 times

Shutdown: 1566 times

Power-on: 123day 17hour 30min 51sec

[mullion]$

Code: 
errlog

ofst[ 32]:err_code:0xffffffff, clock:0x1896170d  2013/01/26 04:24:45

ofst[ 36]:err_code:0xa0902203, clock:0x1896170d  2013/01/26 04:24:45

ofst[ 40]:err_code:0xa0902203, clock:0x1896170d  2013/01/26 04:24:45

ofst[ 44]:err_code:0xa0902203, clock:0x1896170d  2013/01/26 04:24:45

ofst[ 48]:err_code:0xa0801802, clock:0x18961712  2013/01/26 04:24:50

ofst[ 52]:err_code:0xa0801701, clock:0x18961747  2013/01/26 04:25:43

ofst[ 56]:err_code:0xa0801601, clock:0x18961747  2013/01/26 04:25:43

ofst[ 60]:err_code:0xa0404422, clock:0x190fd4eb  2013/04/28 12:39:07

ofst[ 64]:err_code:0xa0403034, clock:0x190fd4eb  2013/04/28 12:39:07

ofst[ 68]:err_code:0xa0404422, clock:0x190fd4f5  2013/04/28 12:39:17

ofst[ 72]:err_code:0xa0403034, clock:0x190fd4f5  2013/04/28 12:39:17

ofst[ 76]:err_code:0xa0404422, clock:0x2da10cdd  2024/04/04 07:01:49

ofst[ 80]:err_code:0xa0403034, clock:0x2da10cdd  2024/04/04 07:01:49

ofst[ 84]:err_code:0xa0404422, clock:0x2da10cf6  2024/04/04 07:02:14

ofst[ 88]:err_code:0xa0403034, clock:0x2da10cf6  2024/04/04 07:02:14

ofst[ 92]:err_code:0xa0404422, clock:0x2da24cf4  2024/04/05 05:47:32

ofst[ 96]:err_code:0xa0403034, clock:0x2da24cf4  2024/04/05 05:47:32

ofst[100]:err_code:0xa0404422, clock:0x2da24cfc  2024/04/05 05:47:40

ofst[104]:err_code:0xa0403034, clock:0x2da24cfc  2024/04/05 05:47:40

ofst[108]:err_code:0xa0404422, clock:0xffffffff

ofst[112]:err_code:0xa0403034, clock:0xffffffff

ofst[116]:err_code:0xa0404422, clock:0xffffffff

ofst[120]:err_code:0xa0403034, clock:0xffffffff

ofst[124]:err_code:0xa0404422, clock:0xffffffff

ofst[  0]:err_code:0xa0403034, clock:0xffffffff

ofst[  4]:err_code:0xa0404422, clock:0xffffffff

ofst[  8]:err_code:0xa0403034, clock:0xffffffff

ofst[ 12]:err_code:0xa0404422, clock:0xffffffff

ofst[ 16]:err_code:0xa0403034, clock:0xffffffff

ofst[ 20]:err_code:0xa0404422, clock:0xffffffff

ofst[ 24]:err_code:0xa0403034, clock:0xffffffff

ofst[ 28]:err_code:0xa0003001, clock:0xffffffff

[mullion]$

Code: 
bringup

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[POWERSEQ] Error : BitTraining RSX:RRAC:RX2:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404422
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
My suspicion is a bumpgate issue according to the error code page, could also be a rotted trace (unlikely).
Any ideas?
 
Last edited:
Hey everyone. New member here. I tried posting a thread but I think being a new account means my posts are hidden.

I recently purchased a used PS3 Phat (CECHH02) from eBay that was listed as for parts/not working. When I received it I learned it has the YLOD, after finding @RIP-Felix 's tutorials I did a diagnosis and learned the capacitors were bad. I replaced two of them today and the PS3 now turns on with a solid green light but refuses to display an image. I tried HDMI and Composite, neither work. I also held the power button while the PS3 was off to reset the video settings. Still nothing.

Could this be the result of bridged capacitor connections? I soldered them as carefully as I could and it all looks fine, but I can't say for sure if there's a hidden bridge underneath them.

Some stuff that might be relevant: Sometimes the PS3 will beep twice while turning on, and the LED still stays green. Sometimes the power button does nothing, and the workaround is flicking the rocker switch off and back on. The PS3 happily accepts and ejects discs.

As I was writing this I realised that this is the exact same behavior as after enabling internal access and doing the checksum fix. Did I miss a critical step in the diagnostic tutorial? Was I supposed to change something back to default to allow boot?

Thanks for any input

Update: Cleaned up the capacitor soldering. Definitely no bridged connections now. Still the same problem :/

I ran more diagnostics but there were no recent errors apart from the old 1002.
 
Last edited:
Should note that I only replaced two capacitors so far as I still have to wait a couple weeks to receive some I ordered from AliExpress (Could not find a single local shop selling them). I ran the powerstate command and it's saying PCI Power : Off.

Maybe I have to replace the other capacitors?

Aside from this, the current replacement capacitors are from a dead PC motherboard. "470" is printed on them, so I assume they're 470uF but have no idea on their voltage tolerance. Using 4 each in place of the tokins
 
Last edited:
That's a GLOD. Does bluetooth connect on the controller?

The most common cause of GLOD such as yours is the GPU. H models have the defective 90nm RSX, so that's most likely what's going on here. Unfortunate it was hiding behind failed tokins.
 
You must log in or register to reply here.

Similar threads

Back
Top