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

[RIP-Felix]

hi, after a reflow (320°C for like 10 minutes) for fixing code A0801002, my ps3 didn't turn on anymore, so checking syscon codes two times it gave me that errors:
===================================
ERR 00: 00000000 A0A02131 FFFFFFFF
ERR 01: 00000000 A0A02131 FFFFFFFF
ERR 02: 00000000 A0A02130 FFFFFFFF
ERR 03: 00000000 A0A02130 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02131 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0A02130 FFFFFFFF
ERR 08: 00000000 A0A02131 FFFFFFFF
ERR 09: 00000000 A0A02131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0112130 FFFFFFFF
ERR 12: 00000000 A0902130 FFFFFFFF
ERR 13: 00000000 A0112130 FFFFFFFF
ERR 14: 00000000 A0112131 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0112130 FFFFFFFF
===================================
and
===================================
ERR 00: 00000000 A0112131 FFFFFFFF
ERR 01: 00000000 A0112130 FFFFFFFF
ERR 02: 00000000 A0112130 FFFFFFFF
ERR 03: 00000000 A0A02131 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02130 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0112131 FFFFFFFF
ERR 08: 00000000 A0112130 FFFFFFFF
ERR 09: 00000000 A0112131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0A02131 FFFFFFFF
ERR 12: 00000000 A0A02131 FFFFFFFF
ERR 13: 00000000 A0A02130 FFFFFFFF
ERR 14: 00000000 A0A02130 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0A02131 FFFFFFFF
===================================
looking for informations seems that i broke temperature sensors of RSX and CELL, do i?
its sure that i also fixed A0801002?
and whats the fix for these errors?

its a DYN-001 CECH-2004A.

This is why you cannot use a fixed temperature for a set period of time. 1st 320 is too hot. You clearly fried the thermal monitor and very likely many onter things. Second, the joints even if reflowed will be oxidized and brittle. The goal of a reflow is to achieve molten balls, with flux, using the least amount of heat as possable. And not to every other component on the board.

Reflows dont remove old oxidized balls or contaminats underneath the BGA. You will just contaminate the balls.

Moreover, they assume the BGA is at fault. That model has a reliable 65nm GPU that does not have the same defect 90nm models suffer from. Error code 1002 indicated your NEC/Tokins had failed. A reflow would not solve that issue. They needed replaced.

Now, it's very likely dead.

Not to worry, it happens. This is how you learn. It's not like it was a very desirable model. I hope this provides closure.

 

[RIP-Felix]

Hi, I have a CECHC with GLOD with multiple A0202120 and some A0802020 error. Fuses, 1.7V_MISC, 1.5V_YC_RC_VDDIO are OK.
any idea?

errlog
ofst[ 12]:err_code:0xffffffff, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 16]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 20]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 24]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 28]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 32]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 36]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 40]:err_code:0xa0802020, clock:0x0b51cf90 2006/01/07 01:02:08
ofst[ 44]:err_code:0xa0802020, clock:0x0b51cf90 2006/01/07 01:02:08
ofst[ 48]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 52]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 56]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 60]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 64]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 68]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 72]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 76]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 80]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 84]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 88]:err_code:0xa0802020, clock:0x0b51cfd1 2006/01/07 01:03:13
ofst[ 92]:err_code:0xa0802020, clock:0x0b51cfd1 2006/01/07 01:03:13
ofst[ 96]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[100]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[104]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[108]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[112]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[116]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[120]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[124]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 0]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 4]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 8]:err_code:0xa0802020, clock:0x0b6193f7 2006/01/19 00:04:07

[mullion]$
becount
Bringup : 3789 times
Shutdown: 3164 times
Power-on: 196day 03hour 57min 00sec

[mullion]$
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
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120

That is very likelt a bad HDMI transmitter, or one of the chokes. Compare them to a good board and if fine, replace the HDMI IC.

2020/2120 that come in groups like that are indicative of a bad HDMI transmitter. It's different than how a bad RSX triggers those same errors. Usually, when there's a bad GPU causing 2020/2120 or 2024/2124, it will have 3034, 2120, and potentially 1601/1701 in the log. You will almost never get more than one 2120 per YLOD event.

That's how you can tell them apart.

 

[RIP-Felix]

So I'm pretty fearful around electrical stuff so I was wondering if I can to plug anything to the ps3 or screw in the "ground" to anything. My ps3 is a cecha01. If you respond thank you in advance!

Sorry, you're going to have to provide us with more to answer your question. Are you asking if there's a easy way to fix your PS3? If so, most likely not. That model most likely has bad tokins, if it has the YLOD. But I'm just guessing at what you might mean.

The best case scenario is the PSU died and that can just be replaced by "plugging in" a new one. But that's quite rare in my experiance.

Again, we'll need more details to help you.

 

[RIP-Felix]

Hi, I bought a CECHG model which wasn't working (YLOD after 6 seconds). The seller said it has been open at least twice, one time having the thermal paste replaced. The CPU and GPU were absolutely caked in thermal paste, so I don't think the guy who did it was very good and thermal paste was low quality. This is my first ps3 I've taken apart but there was this blue foam attached to I think the NEC tokens and some other stuff, idk if that is normal but I don't think I saw it in disassembly videos. Any ideas on what the issue is please?

ofst[  8]:err_code:0xffffffff, clock:0x0b4f6c05  2006/01/05 05:32:53
ofst[ 12]:err_code:0xa0801002, clock:0x0b4f6c0f  2006/01/05 05:33:03
ofst[ 16]:err_code:0xa0801002, clock:0x0b4f6d06  2006/01/05 05:37:10
ofst[ 20]:err_code:0xa0801002, clock:0x0b4f7381  2006/01/05 06:04:49
ofst[ 24]:err_code:0xa0801002, clock:0x0b4f7394  2006/01/05 06:05:08
ofst[ 28]:err_code:0xa0801002, clock:0x0b4f73d4  2006/01/05 06:06:12
ofst[ 32]:err_code:0xa0801002, clock:0x0b4f7544  2006/01/05 06:12:20
ofst[ 36]:err_code:0xa0801002, clock:0x0b4f755c  2006/01/05 06:12:44
ofst[ 40]:err_code:0xa0801002, clock:0x0b4f758f  2006/01/05 06:13:35
ofst[ 44]:err_code:0xa0801002, clock:0x0b4f76c3  2006/01/05 06:18:43
ofst[ 48]:err_code:0xa0801002, clock:0x0b4f792b  2006/01/05 06:28:59
ofst[ 52]:err_code:0xa0801002, clock:0x0b4f79b9  2006/01/05 06:31:21
ofst[ 56]:err_code:0xa0801002, clock:0x0b4f7a8c  2006/01/05 06:34:52
ofst[ 60]:err_code:0xa0801002, clock:0x0b4f7ad2  2006/01/05 06:36:02
ofst[ 64]:err_code:0xa0801002, clock:0x0b4f7b44  2006/01/05 06:37:56
ofst[ 68]:err_code:0xa0801002, clock:0x0b4f7c41  2006/01/05 06:42:09
ofst[ 72]:err_code:0xa0801002, clock:0x0b4f7ea8  2006/01/05 06:52:24
ofst[ 76]:err_code:0xa0801002, clock:0x0b4f81e3  2006/01/05 07:06:11
ofst[ 80]:err_code:0xa0801002, clock:0x0b4f87df  2006/01/05 07:31:43
ofst[ 84]:err_code:0xa0801002, clock:0x0b4f8c53  2006/01/05 07:50:43
ofst[ 88]:err_code:0xa0801002, clock:0x0b4f8c89  2006/01/05 07:51:37
ofst[ 92]:err_code:0xa0801002, clock:0x0b4f8c95  2006/01/05 07:51:49
ofst[ 96]:err_code:0xa0801002, clock:0x0b4f8cae  2006/01/05 07:52:14
ofst[100]:err_code:0xa0801002, clock:0x0b4f8ce3  2006/01/05 07:53:07
ofst[104]:err_code:0xa0801002, clock:0x0b4f8cee  2006/01/05 07:53:18
ofst[108]:err_code:0xa0801002, clock:0x0b4f8d02  2006/01/05 07:53:38
ofst[112]:err_code:0xa0801002, clock:0x0b4f8d91  2006/01/05 07:56:01
ofst[116]:err_code:0xa0801002, clock:0x0b4f8da5  2006/01/05 07:56:21
ofst[120]:err_code:0xa0801002, clock:0x0b4f8eb6  2006/01/05 08:00:54
ofst[124]:err_code:0xa0801002, clock:0x0b4f909a  2006/01/05 08:08:58
ofst[  0]:err_code:0xa0801002, clock:0x0b4f90a8  2006/01/05 08:09:12
ofst[  4]:err_code:0xa0801002, clock:0x0b4f9178  2006/01/05 08:12:40
[mullion]$

Bringup : 1973 times
Shutdown: 1257 times
Power-on: 81day 02hour 04min 09sec
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
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.9.0 (Build ID: 2398,24722, Build Data: 2007-07-22_15:55:29)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

That one has bad RSX tokins, currently.

 

[RIP-Felix]

Hello everyone. A few years ago I bought a secondhand CECHG04. After some time I decided to take it apart since it was very loud, so I changed the thermal paste and cleaned the dust. When I powered it up after assembly I was welcomed by the nefarious YLOD. I did my due diligence before embarking on this task, the console came apart and back together very nicely, nothing was forced. I took it apart afterwards to try the hair drayer method and indeed the console did boot up into XMB but after a minute or two the YLOD came back.
Now I wanted to take another look at it so I followed the Uart guide to pull up the error codes:

ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404421, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404421, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404421, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404421, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404421, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0404421, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0404421, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0404421, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[  0]:err_code:0xa0404421, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0404421, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0404421, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0404421, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404421, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0404421, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0404421, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff

Bringup : 1240 times
Shutdown: 1130 times
Power-on: 119day 20hour 54min 12sec

power on command

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
Press Ctrl+C to exit
>$
[mullion]$ [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 BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

That one has a failed 90nm RSX (defective). G models aren't worth wasting a 40 or 65nm GPU that could be used to fix a BC model. So in your case, if you intend to fix it, a working 90nm Replacment could fix the console. It will still have a defective GPU, but no mre defective than SONY made it.

 

[RIP-Felix]

Hello. I have a cechg08 fat console with 3 beeps.
So I got these code errors 3032

where should I start looking for the problem?

Spoiler: xternal

Auth successful
> ERRLOG GET 00
00000000 A0313032 FFFFFFFF
> ERRLOG GET 01
00000000 A0313032 FFFFFFFF
> ERRLOG GET 02
00000000 A0313032 FFFFFFFF
> ERRLOG GET 03
00000000 A0313032 FFFFFFFF
> ERRLOG GET 04
00000000 A0313032 FFFFFFFF
> ERRLOG GET 05
00000000 A0313032 FFFFFFFF
> ERRLOG GET 06
00000000 A0313032 FFFFFFFF
> ERRLOG GET 07
00000000 A0313032 FFFFFFFF
> ERRLOG GET 08
00000000 A0313032 FFFFFFFF
> ERRLOG GET 09
00000000 A0313032 FFFFFFFF
> ERRLOG GET 10
00000000 A0313032 FFFFFFFF
> ERRLOG GET 11
00000000 A0313032 FFFFFFFF
> ERRLOG GET 12
00000000 A0313032 FFFFFFFF
> ERRLOG GET 13
00000000 A0313032 FFFFFFFF
> ERRLOG GET 14
00000000 A0313032 FFFFFFFF
> ERRLOG GET 15
00000000 A0313032 FFFFFFFF
> ERRLOG GET 16
00000000 A0313032 FFFFFFFF
> ERRLOG GET 17
00000000 A0313032 FFFFFFFF
> ERRLOG GET 18
00000000 A0313032 FFFFFFFF
> ERRLOG GET 19
00000000 A0313032 FFFFFFFF
>

and

Spoiler: internal

> errlog
errlog
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xa0313032, clock:0xffffffff
ofst[104]:err_code:0xa0313032, clock:0xffffffff
ofst[108]:err_code:0xa0313032, clock:0xffffffff
ofst[112]:err_code:0xa0313032, clock:0xffffffff
ofst[116]:err_code:0xa0313032, clock:0xffffffff
ofst[120]:err_code:0xa0313032, clock:0xffffffff
ofst[124]:err_code:0xa0313032, clock:0xffffffff
ofst[ 0]:err_code:0xa0313032, clock:0xffffffff
ofst[ 4]:err_code:0xa0313032, clock:0xffffffff
ofst[ 8]:err_code:0xa0313032, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0313032, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313032, clock:0xffffffff
ofst[ 60]:err_code:0xa0313032, clock:0xffffffff
ofst[ 64]:err_code:0xa0313032, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
ofst[ 88]:err_code:0xa0313032, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>

That one may have a dead CPU, BGA damage to it, cracked die, or a missing SMD near the CPU. That 3032 is a voltage feeing to the CPU and step #31 is when it's initialized. So the likelyhood this console is dead is high.

That's a bad code.

 

[Ash11143]

Hi just imported a CECHL ps3 sold as junk its giving me a delayed YLOD here are the codes
ERR 00: 00000000 A0802124 FFFFFFFF
ERR 01: 00000000 A0801002 FFFFFFFF
ERR 02: 00000000 A0802124 FFFFFFFF
ERR 03: 00000000 A0802124 FFFFFFFF
ERR 04: 00000000 A0801002 FFFFFFFF
ERR 05: 00000000 A0801200 FFFFFFFF
ERR 06: 00000000 A0801200 FFFFFFFF
ERR 07: 00000000 A0802124 FFFFFFFF
ERR 08: 00000000 A0802124 FFFFFFFF
ERR 09: 00000000 A0801002 FFFFFFFF
ERR 10: 00000000 A0801002 2D8E49D6
ERR 11: 00000000 A0802124 2D8E4985
ERR 12: 00000000 A0802124 2D8E4985
ERR 13: 00000000 A0801002 2D8E4984
ERR 14: 00000000 A0802124 2D8E4958
ERR 15: 00000000 A0801002 2D8E4957
ERR 16: 00000000 A0802124 2D8E4930
ERR 17: 00000000 A0801002 2D8E4930
ERR 18: 00000000 A0802124 2D5156CD
ERR 19: 00000000 A0802124 2D5156CD
Startup 4558 Shutdown 4535 Power on Hours 7420.63
I expected the 1002 and have a pair of tantalizers coming and some extra low esr tantalums coming in the mail but I'm worried about those 2124s as that error code seems to be the AV encoder which i suspect is above my soldering skill to swap. do you think it would be worth swapping some of the Tokins to see if that resolves it?

 

[RIP-Felix]

I wish the error codes worked like we assume they should...where if you see it, it means one thing. "2124? HDMI encoder. Replace and no more 2124!"

BUT SONY doesn't work that way. The SYSCON records error conditions no matter how they occured. And there are many fault mechanisms that can trigger an AV subsystem IO error. Like, for example, poor voltage filtering on the GPU. OR a dying HDMI transmitter. Or a dying RSX, Or any number of SMDs. ALL of these things can and do cause 2020/2120, 2024/2124.

This is what I mean when I say they are not diagnostic. They are associative. They provide context in combination with the other errors that are occuring at the same timestamp. like more than one per YLOD event, or if a different timestamp, then maybe on one boot you get this error and on another yiu get a different set, but usually that same set or combo.

In your case, a 2124/1002 combo. The 1002 is diagnostic, the 2124 is associative. In this case, poor RSX filtering, most likely caused by bad tokins, is indicated by 1002. And the AV IO error is registered at the same time because the GPU couldn't render and deliver a frame properly to the HDMI transmitter without errors. It does not mean the HDMI transmitter needs replaced. If it did, you would get multiple 2124's occuring at the same timestamp, and most likely would not have a 1002 at all. That is how you can tell them apart.

You also have a CPU overheat (A0801200). Which may have been caused by testing the console without the heatsink, judging by the lack of a timestamp, indicating the CMOS battery was removed. If it wasn't, this very likely will require delidding to solve. That is a diagnostic code.

 

[RIP-Felix]

... if I apply a little bit of pressure on the top it somehow turns on normally...when I open the PS3 and close it again, the problem goes away...until it inevitably returns. It's pretty random.

01: A0805FFF Fri Dec 31 23:59:59 1999
02: A0801601 Fri Dec 31 23:59:59 1999
03: A0801701 Fri Dec 31 23:59:59 1999

That is the classic behavior of a BGA defect. Judging by the 5FFF, I would suspect the CPU. Has it been delided? was an eraser mod ever used? Is there evidence of drop damage or excessive force being used to break the suction caused by some thermal pastes which are like glue? All of these things can cause a solder ball to crack.

It will need reballed. While a reflow is more DIY'able, it's not going to last and not recommended.

 

[Ash11143]

I wish the error codes worked like we assume they should...where if you see it, it means one thing. "2124? HDMI encoder. Replace and no more 2124!"

BUT SONY doesn't work that way. The SYSCON records error conditions no matter how they occured. And there are many fault mechanisms that can trigger an AV subsystem IO error. Like, for example, poor voltage filtering on the GPU. OR a dying HDMI transmitter. Or a dying RSX, Or any number of SMDs. ALL of these things can and do cause 2020/2120, 2024/2124.

This is what I mean when I say they are not diagnostic. They are associative. They provide context in combination with the other errors that are occuring at the same timestamp. like more than one per YLOD event, or if a different timestamp, then maybe on one boot you get this error and on another yiu get a different set, but usually that same set or combo.

In your case, a 2124/1002 combo. The 1002 is diagnostic, the 2124 is associative. In this case, poor RSX filtering, most likely caused by bad tokins, is indicated by 1002. And the AV IO error is registered at the same time because the GPU couldn't render and deliver a frame properly to the HDMI transmitter without errors. It does not mean the HDMI transmitter needs replaced. If it did, you would get multiple 2124's occuring at the same timestamp, and most likely would not have a 1002 at all. That is how you can tell them apart.

You also have a CPU overheat (A0801200). Which may have been caused by testing the console without the heatsink, judging by the lack of a timestamp, indicating the CMOS battery was removed. If it wasn't, this very likely will require delidding to solve. That is a diagnostic code.

Yeah the thermal overload was testing without thermal paste. I added a pair of spare thermal pads to the cpu and rsx temporarily just to slow the overheat to get the correct error codes. thanks for the advice! will give an update when the parts get in

 

[RIP-Felix]

This is what I dumped yesterday
[mullion]$
errlog
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0202120, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0213013, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0202120, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0213013, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0202120, clock:0xffffffff
ofst[ 96]:err_code:0xa0202120, clock:0xffffffff
ofst[100]:err_code:0xa0202120, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0213013, clock:0xffffffff
[mullion]$

That is a 10x 2120/3013 error combo occuring at step number 20/21. Litterally interprited, it's a Dual Video Amp Error (IC6301) during initialize CPU/RSX Core. Commonly a short (Eg. C6319-22) & blown fuse (Eg. F6301/2). IC6301 forms 1.7v_MISC & 1.8v_RSX_FBVDDQ. Measure all downstream voltages which rely on 1.7v_MISC (refer to voltage tree), lacking any one could cause a 3013 error.

 

[Gansey]

That is the classic behavior of a BGA defect. Judging by the 5FFF, I would suspect the CPU. Has it been delided? was an eraser mod ever used? Is there evidence of drop damage or excessive force being used to break the suction caused by some thermal pastes which are like glue? All of these things can cause a solder ball to crack.

It will need reballed. While a reflow is more DIY'able, it's not going to last and not recommended.

no delids, no drops, no eraser mod and it actually started happening after like 7 months of not opening the PS3. What did fix it for the time being was putting a small piece of plastic covered in thick layers of tape under the metal plate through that hole just next to the blu-ray drive in order to put a little bit of pressure there and flex the board. Been playing normally for hours straight in a while now and it never turned off again, the temperature seems to be a lot lower after the procedure too. idk if it'll last though

 

[RIP-Felix]

what you just described is an eraser mod. This can crack the die FYI. It's been happening to a lot of people. Even when using something squishy like a thermal pad.

 

[Subrosa]

That one may have a dead CPU, BGA damage to it, cracked die, or a missing SMD near the CPU. That 3032 is a voltage feeing to the CPU and step #31 is when it's initialized. So the likelyhood this console is dead is high.

That's a bad code.

ok, sorry to hear(
Where can I check the voltage on the board to make sure? where is the place

 

[RIP-Felix]

You can probe all the voltage if you want, but it's unlikely be the cause of the error. The way we find errors like this has been from deliberatly sabotaging voltages and seeing what code it generates, or when someone reports knocking off a resistor, etc. So there are many ways an error code can be generated.

For example, disabling IC6304 can cause that error. you could try ohm testing YC_RC _VDDA to see if it's short. You could try replacing the controller and mosfet. Seeing if a discreted SMD is missing or short. But if all that is fine (chances are they are fine) the issue is with the solder joints on the BGA or inside the Cell. That also feeds VDDA voltage the RSX. I'm not sure what error is generated if RSX VDDA goes bad. It could be the same or different. Haven't selectivly sabotauged them to find out.

However, a G model has a 90nm RSX with it's defective materal set. So that increases suspicion.

 

[Subrosa]

That one may have a dead CPU, BGA damage to it, cracked die, or a missing SMD near the CPU. That 3032 is a voltage feeing to the CPU and step #31 is when it's initialized. So the likelyhood this console is dead is high.

That's a bad code.

Sorry to interrupt again. I think I found something. The r6357 is clearly missing or exploded.
Is it possible to replace something without a donor? or make something a temporary one to check if it is?


if it is impossible without a donor?
, my board sem01, should I look for the same one to remove the capacitor or any from ps3 will do?
I apologize for many questions, I just saw an opportunity to fix it)

Spoiler: here

 

[Subrosa]

https://www.digikey.com/en/products/detail/susumu/RR0510P-913-D/1249815

looks alike

 

[Ash11143]

well good news is despite my trash soldering job the PS3 is now just complaining about not having a drive because it's still disassembled instead of YLOD. Bad news is I just realized I knocked off the 2 small components below the tokin. Do you happen to know what these specific parts are and wether I need to replace them immediately or wait or if they are not necessary?

 

[Stefan Wagner]

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.

 

[RIP-Felix]

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.