PS3-HW Hardware Questions/Issues? - Post Syscon Logs/details here

[animation_is_always_taken]

hi, so bought a broken CECHH/dia-001 motherboard with these errors
A0902120
A0801201
A0801200
A0002031
A0002030
A0902203
(that more or less just the summary of both files)
i think that it's either a dead capacitor or fuse somewhere on the board or that a thermal sensor is dead, and i can't find any info on the sensors, something weird is that A0902203 only showed up in 2 of the 3 times i used the syscon to log the errors (i didn't save the third log)
it has the standard YLOD symptoms turns on for 2-5 seconds and then the blinking red light shows up, i'm genuinely lost with this one because the thermal chips (the ones right on top of the cell and rsx) seem to be fine, on standby the have 3.3v of input and output on the pins they should, and the fan works
does anyone know what's going on here?

 

[Mateogt]

Hello everyone
I haven't repaired a ps3 before or posted on this forum, so I guess I'm not allowed to post in the appropiate forum.
I did ran the Syscom diagnostics so I still want to ask for advice
I bought this CECHL ps3 not working and the light turns green for about 20-30 seconds but theres no display
According to the wiki it could be a faulty hdmi encoder
What do you guys think?
Here are the error codes

>$ ERRLOG GET 00
00000000 A0802124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0802024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0802024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0802124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0802024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0112024 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0112124 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit

 

[Saint-Fall]

Hi, I have a peculiar case with my PS3 CECHA00 and maybe someone has an idea.

The console:

• Official Sony Frankenstein with 40nm RSX
• All NEC/TOKINs replaced with Tantalizer boards assembled with 470uF Tantalum caps and MLCCs

Most of the time the console starts normally but intermittently I get a YLOD only when the console boots. If the console starts normally, it is stable and I've never had a YLOD while in XMB or in a game.

Spoiler: Syscon error log:

01: A08014FF Sun Jan 1 00:09:36 2006
02: A08014FF Sun Jan 1 00:09:02 2006
03: A08014FF Sun Jan 1 00:05:13 2006
04: A08014FF Sun Jan 1 00:04:46 2006
05: A08014FF Sun Jan 1 00:04:08 2006
06: A0002033 Sun Jan 1 00:03:56 2006
07: A08014FF Sun Jan 1 00:03:49 2006
08: A08014FF Sun Jan 1 00:03:21 2006
09: A08014FF Sun Jan 1 00:02:43 2006
10: A08014FF Sun Jan 1 00:02:21 2006
11: A0002033 Sun Jan 1 00:02:08 2006
12: A08014FF Sun Jan 1 00:01:59 2006
13: A0002033 Sat Dec 31 23:53:34 2005
14: A08014FF Sat Dec 31 19:15:23 2005
15: A08014FF Fri Jan 6 05:03:42 2006

Regarding the two error codes:

• A08014FF: YLOD happens between 10 and 20 seconds after turning the console on (last time it happend I saw the Evilnat bootup logo and then the console shut off). Since it's a very generic error it's hard to pinpoint the fault exactly and there has never been a accompanying error A0801601/A0801701 as described in the Wiki.

• A0002033: YLOD happens immediately after turning the console on. According to the Wiki a fault concerning the Southbridge thermal sensor. Step number 00 indicates that it fails directly at the start of the POST process. I haven't seen burnt traces or ICs in the area (or on the board at all btw) so nothing that points to excessive use of heat.

Could the 14FF error maybe be dependent on the 2033? I can't really tell because there's instances where 14FF just appears alone. I'm inclined to just replace the SB thermal sensor AD51 (IC3101) as a next step. Does anyone have another idea? Thanks.

 

[Snardash]

Hey everyone!
Got this PS3 slim (25xx) that will shutdown after a few seconds of successfully booting. It even goes into XMB and eventually dies. Sometimes it's instant and sometimes it takes seconds to shut off. Checked with good power supply and new HDD, same outcome. Inspecting the board doesn't show anything obvious, upon checking syscon I only get 1701's and 14FF. My current suspicion is that a component for the power delivery of the cell has gone bad, I don't think a BGA defect is likely with the behavior its showing. Anybody has any pointers? I'll try and find the problem in the circuit, if nothing comes up will call it a BGA defect.

it
>$ auth
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0801701 309728F4
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A08014FF 309728F4
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0801701 309728F4
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A08014FF 309728CF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0801701 309728CE
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A08014FF 309728B5
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801701 309728B5
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A08014FF 30940FB4
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801701 30940FB3
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A08014FF 30940814
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801701 30940814
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A08014FF 30940806
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801701 30940806
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A08014FF 309407DF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801701 309407DE
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A08014FF 308C5E2B
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801701 308C5E2A
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A08014FF 308C5DB2
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0801701 308C5DB1
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A08014FF 308C5CF0
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801701 308C5CF0
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A08014FF 308C5C51
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801701 308C5C51
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A08014FF 308B2B9D
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801701 308B2B9C
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A08014FF 308B286D
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801701 308B286D
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A08014FF 308B2846
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801701 308B2846
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A08014FF 308B2835
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801701 308B2834
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A08014FF 308B27CE
Press Ctrl+C to exit
>$ ERRLOG GET 1F

 

[Samsensei]

Sorry, i also posted in the main starting line, not realizing this was there.

I believe this is a perfect candidate for a frankie. I do have what i believe a 40nm slim ps3 which is being donated by a friend. So will attempt that after practicing my soddering and reballing on a launch xbox360.
Gathering all the tools i've seen RIP Felix, Amateur Hardware Repair and others use. But more of a scuff, broke boy set up for now.
I will be getting that delid-ing tool.

I also believe there were NEC/TOKEN issues with this as well so those require updating.
Any advise would be good, and let me know if i am on the right track.

So, RSX Swap, and NEC/TOKEN replacement. With some Hard Drive issues, but will see if there is some PS Home content on there, which i can back up to an external HDD.

Syscon Error Logs, for PS3_CECHA01

ofst[ 40]:err_code:0xffffffff, clock:0x1cb610d3  2015/04/07 03:51:47
ofst[ 44]:err_code:0xa0801001, clock:0x1cb6a448  2015/04/07 14:20:56
ofst[ 48]:err_code:0xa0801001, clock:0x1d602ff9  2015/08/14 04:50:01
ofst[ 52]:err_code:0xa0801001, clock:0x1da2ac73  2015/10/03 15:10:43
ofst[ 56]:err_code:0xa0801001, clock:0x1e690e76  2016/03/02 02:37:42
ofst[ 60]:err_code:0xa0801001, clock:0x23356300  2018/09/19 19:41:52
ofst[ 64]:err_code:0xa0801001, clock:0x24b7746d  2019/07/09 15:51:09
ofst[ 68]:err_code:0xa0801001, clock:0x25b0c373  2020/01/14 18:22:43
ofst[ 72]:err_code:0xa0801701, clock:0x25b569a8  2020/01/18 07:00:56
ofst[ 76]:err_code:0xa0801601, clock:0x25b569a8  2020/01/18 07:00:56
ofst[ 80]:err_code:0xa0801001, clock:0x25d9a43e  2020/02/14 18:32:30
ofst[ 84]:err_code:0xa0801701, clock:0x2618d594  2020/04/02 16:55:48
ofst[ 88]:err_code:0xa0801601, clock:0x2618d594  2020/04/02 16:55:48
ofst[ 92]:err_code:0xa0403034, clock:0x261aa33d  2020/04/04 01:45:33
ofst[ 96]:err_code:0xa0401001, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0x261d7107  2020/04/06 04:48:07
ofst[104]:err_code:0xa0403034, clock:0x261d72f2  2020/04/06 04:56:18
ofst[108]:err_code:0xa0403034, clock:0x262540ed  2020/04/12 03:01:01
ofst[112]:err_code:0xa0403034, clock:0x262540f6  2020/04/12 03:01:10
ofst[116]:err_code:0xa0403034, clock:0x2675f799  2020/06/12 08:21:45
ofst[120]:err_code:0xa0403034, clock:0x26cd959d  2020/08/17 19:23:09
ofst[124]:err_code:0xa0403034, clock:0x270a63f4  2020/10/02 22:19:32
ofst[  0]:err_code:0xa0403034, clock:0x271f6234  2020/10/18 20:29:40
ofst[  4]:err_code:0xa0403034, clock:0x27549855  2020/11/28 05:10:45
ofst[  8]:err_code:0xa0403034, clock:0x308318ed  2025/10/16 02:46:05
ofst[ 12]:err_code:0xa0403034, clock:0x30831900  2025/10/16 02:46:24
ofst[ 16]:err_code:0xa0403034, clock:0x30992e4c  2025/11/01 20:47:08
ofst[ 20]:err_code:0xa0403034, clock:0x30992e55  2025/11/01 20:47:17
ofst[ 24]:err_code:0xa0403034, clock:0x30992e60  2025/11/01 20:47:28
ofst[ 28]:err_code:0xa0403034, clock:0x30992e6d  2025/11/01 20:47:41
ofst[ 32]:err_code:0xa0403034, clock:0x30992e86  2025/11/01 20:48:06
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff

>$ ERRLOG GET 00
00000000 A0403034 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0403034 30992E86
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0403034 30992E6D
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0403034 30992E60
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0403034 30992E55
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0403034 30992E4C
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0403034 30831900
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0403034 308318ED
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0403034 27549855
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0403034 271F6234
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0403034 270A63F4
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0403034 26CD959D
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0403034 2675F799
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0403034 262540F6
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0403034 262540ED
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0403034 261D72F2
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0403034 261D7107
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0401001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0403034 261AA33D
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801601 2618D594
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801701 2618D594
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801001 25D9A43E
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801601 25B569A8
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801701 25B569A8
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801001 25B0C373
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801001 24B7746D
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0801001 23356300
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801001 1E690E76
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801001 1DA2AC73
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801001 1D602FF9
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801001 1CB6A448
Press Ctrl+C to exit

Becount

Bringup : 2029 times
Shutdown: 2009 times
Power-on: 245day 14hour 42min 00sec

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:0x20e2

[mullion]$ [POWERSEQ] Error : BitTraining RSX:RRAC:RX0: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]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Press Ctrl+C to exit

 

[kyiscray]

I have a CECHK01 with error 2113, i posted about this in the wrong place earlier without realizing it, but anyways heres the background: i first saw problems with it not turning on the first try about 6 years ago, where it would ylod. i got it and tested it 2 years ago, and after like 20 power cycles and letting it run was able to stay on the XMB, before launching a game and it crashing once it had enough load on the RSX. 2 years ago (a few months ago) it was an instant ylod, and seemed basically dead, but i have no history of any of the original faults, only the current one.

this is the error log and other things, ignore 3034 because i shorted out the vrms by accident then:

errlog
ofst[104]:err_code:0xffffffff, clock:0x30a044c7  2025/11/07 05:48:55
ofst[108]:err_code:0xa0092113, clock:0x30a044c9  2025/11/07 05:48:57
ofst[112]:err_code:0xa0092113, clock:0x30a044cb  2025/11/07 05:48:59
ofst[116]:err_code:0xa0092113, clock:0x30a04516  2025/11/07 05:50:14
ofst[120]:err_code:0xa0092113, clock:0x30a04533  2025/11/07 05:50:43
ofst[124]:err_code:0xa0092113, clock:0x30a04536  2025/11/07 05:50:46
ofst[  0]:err_code:0xa0092113, clock:0x30a04557  2025/11/07 05:51:19
ofst[  4]:err_code:0xa0092113, clock:0x30a0455e  2025/11/07 05:51:26
ofst[  8]:err_code:0xa0092113, clock:0x30a045c2  2025/11/07 05:53:06
ofst[ 12]:err_code:0xa0092113, clock:0x30a04651  2025/11/07 05:55:29
ofst[ 16]:err_code:0xa0092113, clock:0x30a04662  2025/11/07 05:55:46
ofst[ 20]:err_code:0xa0092113, clock:0x30a04664  2025/11/07 05:55:48
ofst[ 24]:err_code:0xa0092113, clock:0x30a04673  2025/11/07 05:56:03
ofst[ 28]:err_code:0xa0092113, clock:0x30a0469d  2025/11/07 05:56:45
ofst[ 32]:err_code:0xa0092113, clock:0x30a0469f  2025/11/07 05:56:47
ofst[ 36]:err_code:0xa0092113, clock:0x30a046a1  2025/11/07 05:56:49
ofst[ 40]:err_code:0xa0092113, clock:0x30a046eb  2025/11/07 05:58:03
ofst[ 44]:err_code:0xa0092113, clock:0x30a046fd  2025/11/07 05:58:21
ofst[ 48]:err_code:0xa0092113, clock:0x30a04707  2025/11/07 05:58:31
ofst[ 52]:err_code:0xa0093004, clock:0x30a04729  2025/11/07 05:59:05
ofst[ 56]:err_code:0xa0093004, clock:0x30a04735  2025/11/07 05:59:17
ofst[ 60]:err_code:0xa0092113, clock:0x30a43c4f  2025/11/10 06:01:51
ofst[ 64]:err_code:0xa0092113, clock:0x30a43c53  2025/11/10 06:01:55
ofst[ 68]:err_code:0xa0092113, clock:0x30a43d58  2025/11/10 06:06:16
ofst[ 72]:err_code:0xa0092113, clock:0x30a43dd6  2025/11/10 06:08:22
ofst[ 76]:err_code:0xa0092113, clock:0x30a43dd8  2025/11/10 06:08:24
ofst[ 80]:err_code:0xa0092113, clock:0x30a43dde  2025/11/10 06:08:30
ofst[ 84]:err_code:0xa0092113, clock:0x30a43de0  2025/11/10 06:08:32
ofst[ 88]:err_code:0xa0092113, clock:0x30a43de2  2025/11/10 06:08:34
ofst[ 92]:err_code:0xa0092113, clock:0x30a43dea  2025/11/10 06:08:42
ofst[ 96]:err_code:0xa0092113, clock:0x30a43ded  2025/11/10 06:08:45
ofst[100]:err_code:0xa0092113, clock:0x30a43fe8  2025/11/10 06:17:12

becount
Bringup : 7404 times
Shutdown: 7218 times
Power-on: 401day 03hour 43min 58sec

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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0092113

should note i was an idiot and tried replacing the nec/tokin capacitors with cheap aliexpress tantalums without ever checking syscon first, so if thats a cause let me know. the cell and rsx heat up after enough cycles so they are getting some voltage at least, and my multimeter does show a relatively stable enough voltage that shouldn't damage it. when i didnt add enough the voltage did spike up to about 1.6v on the rsx for a millisecond and i don't know if thats another factor

 

[Samsensei]

I have a CECHK01 with error 2113, i posted about this in the wrong place earlier without realizing it, but anyways heres the background: i first saw problems with it not turning on the first try about 6 years ago, where it would ylod. i got it and tested it 2 years ago, and after like 20 power cycles and letting it run was able to stay on the XMB, before launching a game and it crashing once it had enough load on the RSX. 2 years ago (a few months ago) it was an instant ylod, and seemed basically dead, but i have no history of any of the original faults, only the current one.

this is the error log and other things, ignore 3034 because i shorted out the vrms by accident then:

errlog
ofst[104]:err_code:0xffffffff, clock:0x30a044c7  2025/11/07 05:48:55
ofst[108]:err_code:0xa0092113, clock:0x30a044c9  2025/11/07 05:48:57
ofst[112]:err_code:0xa0092113, clock:0x30a044cb  2025/11/07 05:48:59
ofst[116]:err_code:0xa0092113, clock:0x30a04516  2025/11/07 05:50:14
ofst[120]:err_code:0xa0092113, clock:0x30a04533  2025/11/07 05:50:43
ofst[124]:err_code:0xa0092113, clock:0x30a04536  2025/11/07 05:50:46
ofst[  0]:err_code:0xa0092113, clock:0x30a04557  2025/11/07 05:51:19
ofst[  4]:err_code:0xa0092113, clock:0x30a0455e  2025/11/07 05:51:26
ofst[  8]:err_code:0xa0092113, clock:0x30a045c2  2025/11/07 05:53:06
ofst[ 12]:err_code:0xa0092113, clock:0x30a04651  2025/11/07 05:55:29
ofst[ 16]:err_code:0xa0092113, clock:0x30a04662  2025/11/07 05:55:46
ofst[ 20]:err_code:0xa0092113, clock:0x30a04664  2025/11/07 05:55:48
ofst[ 24]:err_code:0xa0092113, clock:0x30a04673  2025/11/07 05:56:03
ofst[ 28]:err_code:0xa0092113, clock:0x30a0469d  2025/11/07 05:56:45
ofst[ 32]:err_code:0xa0092113, clock:0x30a0469f  2025/11/07 05:56:47
ofst[ 36]:err_code:0xa0092113, clock:0x30a046a1  2025/11/07 05:56:49
ofst[ 40]:err_code:0xa0092113, clock:0x30a046eb  2025/11/07 05:58:03
ofst[ 44]:err_code:0xa0092113, clock:0x30a046fd  2025/11/07 05:58:21
ofst[ 48]:err_code:0xa0092113, clock:0x30a04707  2025/11/07 05:58:31
ofst[ 52]:err_code:0xa0093004, clock:0x30a04729  2025/11/07 05:59:05
ofst[ 56]:err_code:0xa0093004, clock:0x30a04735  2025/11/07 05:59:17
ofst[ 60]:err_code:0xa0092113, clock:0x30a43c4f  2025/11/10 06:01:51
ofst[ 64]:err_code:0xa0092113, clock:0x30a43c53  2025/11/10 06:01:55
ofst[ 68]:err_code:0xa0092113, clock:0x30a43d58  2025/11/10 06:06:16
ofst[ 72]:err_code:0xa0092113, clock:0x30a43dd6  2025/11/10 06:08:22
ofst[ 76]:err_code:0xa0092113, clock:0x30a43dd8  2025/11/10 06:08:24
ofst[ 80]:err_code:0xa0092113, clock:0x30a43dde  2025/11/10 06:08:30
ofst[ 84]:err_code:0xa0092113, clock:0x30a43de0  2025/11/10 06:08:32
ofst[ 88]:err_code:0xa0092113, clock:0x30a43de2  2025/11/10 06:08:34
ofst[ 92]:err_code:0xa0092113, clock:0x30a43dea  2025/11/10 06:08:42
ofst[ 96]:err_code:0xa0092113, clock:0x30a43ded  2025/11/10 06:08:45
ofst[100]:err_code:0xa0092113, clock:0x30a43fe8  2025/11/10 06:17:12

becount
Bringup : 7404 times
Shutdown: 7218 times
Power-on: 401day 03hour 43min 58sec

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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0092113

should note i was an idiot and tried replacing the nec/tokin capacitors with cheap aliexpress tantalums without ever checking syscon first, so if thats a cause let me know. the cell and rsx heat up after enough cycles so they are getting some voltage at least, and my multimeter does show a relatively stable enough voltage that shouldn't damage it. when i didnt add enough the voltage did spike up to about 1.6v on the rsx for a millisecond and i don't know if thats another factor

hi I believe those are all clock errors. Your battery that holds time just needs replacing. The issue is something else. But that would have removed any old issues in the syscon. Maybe add a new one, I believe they are cr2032 battery same as the air tags and try again. See what the issue is after replacing the battery.

if anyone else can reply with a better answer feel free to advise.

 

[Saint-Fall]

Hi, I have a peculiar case with my PS3 CECHA00 and maybe someone has an idea.

The console:

• Official Sony Frankenstein with 40nm RSX
• All NEC/TOKINs replaced with Tantalizer boards assembled with 470uF Tantalum caps and MLCCs

Most of the time the console starts normally but intermittently I get a YLOD only when the console boots. If the console starts normally, it is stable and I've never had a YLOD while in XMB or in a game.

Spoiler: Syscon error log:

01: A08014FF Sun Jan 1 00:09:36 2006
02: A08014FF Sun Jan 1 00:09:02 2006
03: A08014FF Sun Jan 1 00:05:13 2006
04: A08014FF Sun Jan 1 00:04:46 2006
05: A08014FF Sun Jan 1 00:04:08 2006
06: A0002033 Sun Jan 1 00:03:56 2006
07: A08014FF Sun Jan 1 00:03:49 2006
08: A08014FF Sun Jan 1 00:03:21 2006
09: A08014FF Sun Jan 1 00:02:43 2006
10: A08014FF Sun Jan 1 00:02:21 2006
11: A0002033 Sun Jan 1 00:02:08 2006
12: A08014FF Sun Jan 1 00:01:59 2006
13: A0002033 Sat Dec 31 23:53:34 2005
14: A08014FF Sat Dec 31 19:15:23 2005
15: A08014FF Fri Jan 6 05:03:42 2006

Regarding the two error codes:

• A08014FF: YLOD happens between 10 and 20 seconds after turning the console on (last time it happend I saw the Evilnat bootup logo and then the console shut off). Since it's a very generic error it's hard to pinpoint the fault exactly and there has never been a accompanying error A0801601/A0801701 as described in the Wiki.

• A0002033: YLOD happens immediately after turning the console on. According to the Wiki a fault concerning the Southbridge thermal sensor. Step number 00 indicates that it fails directly at the start of the POST process. I haven't seen burnt traces or ICs in the area (or on the board at all btw) so nothing that points to excessive use of heat.

Could the 14FF error maybe be dependent on the 2033? I can't really tell because there's instances where 14FF just appears alone. I'm inclined to just replace the SB thermal sensor AD51 (IC3101) as a next step. Does anyone have another idea? Thanks.

In the meantime i replaced the SB thermal monitor and the 3.3V LDO for thermal, but sporadic YLODs remained and most of the time I get them now frequently after the console has been on for a few minutes. It's almost always a sole 14FF and only sometimes accompanied by 2203 and 2120, even a 2111 has been logged at one point:

Spoiler: Syscon error log:

01: A08014FF Sat Dec 31 04:26:59 2005
02: A08014FF Sat Dec 31 04:26:24 2005
03: A08014FF Sat Dec 31 04:26:01 2005
04: A08014FF Sat Dec 31 04:25:30 2005
05: A08014FF Sat Dec 31 04:24:56 2005
06: A08014FF Sat Dec 31 04:17:03 2005
07: A08014FF Sat Dec 31 04:12:20 2005
08: A08014FF Sat Dec 31 04:11:37 2005
09: A08014FF Sat Dec 31 04:08:54 2005
10: A08014FF Sat Dec 31 02:31:38 2005
11: A08014FF Sat Dec 31 02:28:04 2005
12: A08014FF Sat Dec 31 02:27:38 2005
13: A0902203 Sat Dec 31 02:27:31 2005
14: A0902203 Sat Dec 31 02:27:31 2005
15: A0902203 Sat Dec 31 02:27:31 2005
16: A08014FF Sat Dec 31 02:27:31 2005
17: A0902120 Sat Dec 31 02:27:24 2005
18: A08014FF Sat Dec 31 02:27:24 2005
19: A08014FF Sat Dec 31 02:27:09 2005
20: A08014FF Sat Dec 31 02:25:07 2005
21: A0902120 Sat Dec 31 01:47:48 2005
22: A0902111 Sat Dec 31 01:47:48 2005
23: A0902111 Sat Dec 31 01:47:48 2005
24: A08014FF Sat Dec 31 01:47:48 2005
25: A08014FF Sat Dec 31 01:47:44 2005
26: A08014FF Sat Dec 31 01:47:37 2005
27: A08014FF Sat Dec 31 01:47:31 2005
28: A08014FF Sat Dec 31 01:47:24 2005
29: A08014FF Sat Dec 31 01:47:08 2005
30: A08014FF Sat Dec 31 01:46:48 2005
31: A08014FF Sat Dec 31 01:46:37 2005
32: FFFFFFFF Sat Dec 31 01:45:54 2005

A disp_err in in Syscon UART reaveals the following:

CheckStop: asserted (SB:IOIFEVTST=00000000 COE=4EFF7FF6 CHKSTS=00000000)
PLLUnlock: 0
RSX Int: None
PowerSeq: ff

If I read this correctly the Southbridge is responsible for the CheckStop. Last thing I'll do is check all the voltages according PS3 Power Control Topology (Part 2 - Voltage Regulation & Power Good). If that shows up normal I may be up for a Southbridge reball or even complete replacement, however those don't seem that common at all. I'd appreciate if someone has other ideas or information concerning this error pattern.

 

[Dictator Tom]

Hello!
This is not a syscon error log, but a question about my problem.
I have a cechc04 ps3 and its artifacting, but only if hdmi is used, if i use av I get no problem at all in 576i, I played tlou till the part where they go outside of the wall and there was no problem and temp didn't go over 58°C.
Is this rsx issue or a bad hdmi ic?
Thanks in advance

 

[wulftrick]

Hello! I have a CECH-4001C presenting me with the error codes 0xA08014FF and 0xA0801701 in ps3toolset. I was told this is the sign of a cpu failure, and manifests itself in the form of the PS3 shutting off to no light on the front of the system (as if someone pulled the plug) when a game is too heavy (Heavy Rain and Metal Gear Rising cause a shutdown, while Sonic 06 shows no problems whatsoever). What are the odds of this happening because I've been informed it could be a BGA issue and that seems kind of rare on my model from my understanding. But I'm a noob so like, what do I know.

 

[clank23]

Here is my error log.

>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0x19710099  2013/07/11 05:35:21
ofst[ 72]:err_code:0xa0802022, clock:0x19710099  2013/07/11 05:35:21
ofst[ 76]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 80]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 84]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 88]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 92]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[ 96]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[100]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[104]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[108]:err_code:0xa0801001, clock:0x19d9357a  2013/09/28 06:36:42
ofst[112]:err_code:0xa0801001, clock:0x1cca79f4  2015/04/22 15:25:40
ofst[116]:err_code:0xa0801201, clock:0x1cdee049  2015/05/08 02:47:37
ofst[120]:err_code:0xa0801201, clock:0x1cdef63a  2015/05/08 04:21:14
ofst[124]:err_code:0xa0801201, clock:0x1cdf1198  2015/05/08 06:18:00
ofst[  0]:err_code:0xa0801103, clock:0x1ce028ca  2015/05/09 02:09:14
ofst[  4]:err_code:0xa0002031, clock:0x1ce029f6  2015/05/09 02:14:14
ofst[  8]:err_code:0xa0801201, clock:0x1ce2f8c2  2015/05/11 05:21:06
ofst[ 12]:err_code:0xa0801201, clock:0x1ce2f94d  2015/05/11 05:23:25
ofst[ 16]:err_code:0xa0801103, clock:0x1ce3023c  2015/05/11 06:01:32
ofst[ 20]:err_code:0xa0002031, clock:0x1ce30368  2015/05/11 06:06:32
ofst[ 24]:err_code:0xa0801201, clock:0x1ce309c8  2015/05/11 06:33:44
ofst[ 28]:err_code:0xa0801201, clock:0x1ce45baa  2015/05/12 06:35:22
ofst[ 32]:err_code:0xa0801201, clock:0x1cf2b638  2015/05/23 03:53:28
ofst[ 36]:err_code:0xa0801201, clock:0x1cf2d195  2015/05/23 05:50:13
ofst[ 40]:err_code:0xa0801201, clock:0x2fba8f84  2025/05/17 00:06:28
ofst[ 44]:err_code:0xa0801201, clock:0x2fba8fd4  2025/05/17 00:07:48
ofst[ 48]:err_code:0xa0002031, clock:0x2fba8fdd  2025/05/17 00:07:57
ofst[ 52]:err_code:0xa0801201, clock:0x2fba902d  2025/05/17 00:09:17
ofst[ 56]:err_code:0xa0801201, clock:0x2fc16d71  2025/05/22 05:06:57
ofst[ 60]:err_code:0xa0801201, clock:0x2fc16de1  2025/05/22 05:08:49
ofst[ 64]:err_code:0xa0801201, clock:0x0b488895  2005/12/31 00:08:53

PS3 turns on and will run before hitting YLOD producing a single new 1201 RSX overheating error. Now to troubleshoot,
I modified the fan curve to allow the fan to ramp up at a lower temp. Both CELL and RSX are delidded. Sometimes the console will stabilize and continue to run while other times it will YLOD again. Checking the temps the Cell stays nice and stable while the RSX bounces around quite a bit. I noticed the cooling assembly heatsinks that sits and holds on the RSX IHS wasn't perfectly flat and was quite bent and had to be bent back into shape in order to get back on. Constantly checking with tmp 1 command shows the RSX will jump up in temp very quickly once reaching 65C or so. I have it set to shutdown once reaching 80C. Anyone have thoughts? I was thinking the error code 2031 in the log may be pointing to defects with the RSX thermal sensor which is a diode may be dead or dying and to check C2103, R2101/2 & replace IC2101. My next step will be to put a different cooling assembly from another console on and see if I can get a stable temp on the RSX. I will post my results after using a different cooling assembly.

Updating this.
After putting a different cooling assembly on the results are the same. RSX temp just keeps fluctuating. I was able to get another 2031 error this time. My analysis is that the components C2103, R2101/2, and IC2101 may be faulty. If not those then the RSX is defective and probably needs replacing or a reball. I don't think I'll even attempt a reflow as that is generally not recommended and is only a band aid fix.

Here is my error log.

>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0x19710099  2013/07/11 05:35:21
ofst[ 72]:err_code:0xa0802022, clock:0x19710099  2013/07/11 05:35:21
ofst[ 76]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 80]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 84]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 88]:err_code:0xa0802022, clock:0x1999bcb8  2013/08/11 03:08:40
ofst[ 92]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[ 96]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[100]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[104]:err_code:0xa0802022, clock:0x19c7eb4f  2013/09/15 03:51:43
ofst[108]:err_code:0xa0801001, clock:0x19d9357a  2013/09/28 06:36:42
ofst[112]:err_code:0xa0801001, clock:0x1cca79f4  2015/04/22 15:25:40
ofst[116]:err_code:0xa0801201, clock:0x1cdee049  2015/05/08 02:47:37
ofst[120]:err_code:0xa0801201, clock:0x1cdef63a  2015/05/08 04:21:14
ofst[124]:err_code:0xa0801201, clock:0x1cdf1198  2015/05/08 06:18:00
ofst[  0]:err_code:0xa0801103, clock:0x1ce028ca  2015/05/09 02:09:14
ofst[  4]:err_code:0xa0002031, clock:0x1ce029f6  2015/05/09 02:14:14
ofst[  8]:err_code:0xa0801201, clock:0x1ce2f8c2  2015/05/11 05:21:06
ofst[ 12]:err_code:0xa0801201, clock:0x1ce2f94d  2015/05/11 05:23:25
ofst[ 16]:err_code:0xa0801103, clock:0x1ce3023c  2015/05/11 06:01:32
ofst[ 20]:err_code:0xa0002031, clock:0x1ce30368  2015/05/11 06:06:32
ofst[ 24]:err_code:0xa0801201, clock:0x1ce309c8  2015/05/11 06:33:44
ofst[ 28]:err_code:0xa0801201, clock:0x1ce45baa  2015/05/12 06:35:22
ofst[ 32]:err_code:0xa0801201, clock:0x1cf2b638  2015/05/23 03:53:28
ofst[ 36]:err_code:0xa0801201, clock:0x1cf2d195  2015/05/23 05:50:13
ofst[ 40]:err_code:0xa0801201, clock:0x2fba8f84  2025/05/17 00:06:28
ofst[ 44]:err_code:0xa0801201, clock:0x2fba8fd4  2025/05/17 00:07:48
ofst[ 48]:err_code:0xa0002031, clock:0x2fba8fdd  2025/05/17 00:07:57
ofst[ 52]:err_code:0xa0801201, clock:0x2fba902d  2025/05/17 00:09:17
ofst[ 56]:err_code:0xa0801201, clock:0x2fc16d71  2025/05/22 05:06:57
ofst[ 60]:err_code:0xa0801201, clock:0x2fc16de1  2025/05/22 05:08:49
ofst[ 64]:err_code:0xa0801201, clock:0x0b488895  2005/12/31 00:08:53

PS3 turns on and will run before hitting YLOD producing a single new 1201 RSX overheating error. Now to troubleshoot,
I modified the fan curve to allow the fan to ramp up at a lower temp. Both CELL and RSX are delidded. Sometimes the console will stabilize and continue to run while other times it will YLOD again. Checking the temps the Cell stays nice and stable while the RSX bounces around quite a bit. I noticed the cooling assembly heatsinks that sits and holds on the RSX IHS wasn't perfectly flat and was quite bent and had to be bent back into shape in order to get back on. Constantly checking with tmp 1 command shows the RSX will jump up in temp very quickly once reaching 65C or so. I have it set to shutdown once reaching 80C. Anyone have thoughts? I was thinking the error code 2031 in the log may be pointing to defects with the RSX thermal sensor which is a diode may be dead or dying and to check C2103, R2101/2 & replace IC2101. My next step will be to put a different cooling assembly from another console on and see if I can get a stable temp on the RSX. I will post my results after using a different cooling assembly.

Updating this.
After putting a different cooling assembly on the results are the same. RSX temp just keeps fluctuating. I was able to get another 2031 error this time. My analysis is that the components C2103, R2101/2, and IC2101 may be faulty. If not those then the RSX is defective and probably needs replacing or a reball. I don't think I'll even attempt a reflow as that is generally not recommended and is only a band aid fix.

Update:
Changing the cooling assembly out did not make a difference. I actually used ChatGPT and it suggested using a different power supply. Crazily enough this actually worked. I stopped seeing yellow light of death on XMB. I was even able to get the Last of Us to play and not overheat. It was getting close though. ChatGBT suggested this because of the 2031 error which suggested RSX temperature control but ChatGPT was saying that the power supply could be the problem instead. So I didn't get any problems until I was trying to put custom firmware on where YLOD came back but with only 1201. And then I tried to play The Last of Us again and then got the YLOD with 1201 only. Note that I monitor the temperatures with the UART and I can always see that the RSX temps just start to fly through the roof just before the 1201 error. CELL stays incredibly cool the whole time. Fan is set to 40-50% with my custom fan curve.

My final conclusion for now is that the RSX has just become defective and can sometimes function and other times won't. So I am going to undervolt to see if the RSX can stay stabilized and will update this again.

 

[MrBwamMan]

Syscon error log I got from a PS3 I bought a while back off of ebay, thought it'd be fun to mess with.
I think last time I heard it was a corrupted NOR or something, but I wanted to make sure and then figure out how the hell to actually fix it.
It's a KTE 001 motherboard if that helps.

00000000
# CODE CLOCK
# A0805FFF 2F78B20F
# A0805FFF 2F78B1DB
# A0805FFF 2F78B1A1
# A0805FFF 2F78B141
# A0805FFF 2F7247A0
# A0805FFF 2F70908E
# A0805FFF 2F709058
# A0805FFF 2F709024
# A0805FFF 2F708FF8
# A0805FFF 2F708D13
# A0805FFF 2F708CD6
# A0805FFF 2F708C8F
# A0805FFF 2F64750F
# A0805FFF 2F6474CD
# A0805FFF 2F647487
# A0805FFF 2A01A773
# A0805FFF 2A01A203
# A0805FFF 2A01A082
# A0805FFF 2A01A04C
# A0805FFF 2A007A46
# A0805FFF 2A0079E9
# A0805FFF 2A0079A3
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

 

[mrn3oc]

Just followed RIP Felix's diagnostic tutorial video. Any insight/help highly appreciate it, here is the codes:

C:\Users\CoJe\Desktop\ps3syscon-master\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM3 SW
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0801200 FFFFFFFF
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0801200 FFFFFFFF
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 0B49D9DC
# A0801002 0B49D9DC
# A0802124 0B49D808
# A0801002 0B49D807
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 0B49D819
# A0802124 0B49D818
# A0801002 0B49D818
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 29DDF1D8
# A0801002 29DDF1D8
# A0802124 29DDE821
# A0802124 29DDE820
# A0801002 29DDE820
# A0802124 29DDE680
# A0801002 29DDE680
# A0802124 29DDE53D
# A0802124 29DDE53C
# A0801002 29DDE53C

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
Exiting...

 

[santorfo]

Hi, my CECH-2004B that I replaced the tokins on with tantalizers is triple beeping again (after 20 minutes of gameplay, LittleBigPlanet 2 in this case) and showing 1002 errors on ps3toolset.
When I replaced the tokins I used 3x330uF caps instead of 3x470uF. Could this be the cause for this? I also didn't include all the other smaller components that Felix recommended as I didn't feel capable of soldering them.
Is it more likely that it's insufficient capacitance or that I did a shoddy solder job and that maybe the solder isn't making proper contact and the RSX is cutting out because of that?

 

[happenstance]

After replacing the thermal paste on my CECHK01, I was no longer getting video out after re-assembly. I spent a few minutes today getting the logs from the syscon, hoping one of you all could make sense of them for me! I fear I might have caused cracks in the bga when removing the motherboard. It was quite a hot system. Idling at 75 at the XMB.

>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0801001 256F7002
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit

Here is a bringup attempt after removing the motherboard and to install the syscon wires.

>$ 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

Also grabbed the results of becount! The system has had a long life. Who knows how much of that was running hot.

>$ becount
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
becount
Bringup : 1517 times
Shutdown: 1466 times
Power-on: 770day 13hour 40min 46sec
[mullion]$
Press Ctrl+C to exit

 

[552eden]

I think my syscon is dead / has a short

Ps3 cechA00 with cok001 board has instant blinking red light

On syscon access I can get errlog sometime but when trying to enter internal mode (EEP set 3961 01 00) I get error E00000A0 which means write failed

Any ideas? Maybe voltages to check around the chip?

Thanks

Edit: by pure luck I managed to find a dead cap on the 3v3 rail and that fixed the above issue

But now the cell is sure it's over hearing in 5 seconds after boot (syscon error a0801200) what should I check? It's is not hot and I tested with heatsink + fan connected

Thanks all

 

[go_brrrrr]

Hi Everyone, my PS3 has been randomly turning off during games but fine otherwise with ps2 and ps1 with red flashing led but still turns on afterwards this is my syscon err log with bring up count extracted to usb from cfw will I need UART to extract more information? I am uncertain whether RSX or tokins have gone kaput unit is a CECHA00


Bringup Count: 2408, Shutdown Count: 2305
Runtime: 162 Days, 4 Hours, 31 Minutes, 56 Seconds
Error Log
01: A0801001 Sun Aug 13 00:10:24 2006
02: A0801001 Sat Aug 12 05:01:47 2006
03: A0802022 Thu Aug 10 04:19:44 2006
04: A0802022 Thu Aug 10 04:18:30 2006
05: A0802022 Tue Aug 8 03:18:28 2006
06: A0802022 Tue Aug 8 03:17:51 2006
07: A0801002 Wed Aug 2 01:24:13 2006
08: A0801001 Wed Aug 2 00:40:32 2006
09: A0801001 Sat Jul 29 03:25:35 2006
10: A0801001 Fri Jul 28 21:35:05 2006
11: A0802022 Wed Jul 19 02:00:53 2006
12: A0802022 Wed Jul 19 01:57:40 2006
13: A0802022 Wed Jul 19 01:46:18 2006
14: A0802022 Wed Jul 19 01:45:33 2006
15: A0802022 Sun Jul 16 04:33:50 2006
16: A0802022 Sun Jul 16 04:16:39 2006
17: A0802022 Sun Jul 16 04:15:17 2006
18: A0802022 Sun Jul 16 04:11:20 2006
19: A0801001 Sat Jul 8 10:56:29 2006
20: A0801001 Fri Mar 31 14:37:54 2006
21: A0801001 Fri Mar 31 11:40:25 2006
22: A0801001 Thu Mar 30 22:31:29 2006
23: A0801001 Thu Mar 30 22:31:06 2006
24: A0902120 Thu Mar 2 04:28:20 2006
25: A0801001 Thu Mar 2 04:28:20 2006
26: A0802022 Wed Feb 1 03:14:55 2006
27: A0802022 Wed Feb 1 03:04:39 2006
28: A0801001 Mon Jan 16 22:48:15 2006
29: A0801001 Thu Jan 5 04:22:27 2006
30: A0801001 Thu Jan 5 04:16:49 2006
31: A0801001 Thu Jan 5 04:14:27 2006
32: FFFFFFFF Thu Jan 5 02:31:47 2006

 

[santorfo]

Hi, my CECH-2004B that I replaced the tokins on with tantalizers is triple beeping again (after 20 minutes of gameplay, LittleBigPlanet 2 in this case) and showing 1002 errors on ps3toolset.
When I replaced the tokins I used 3x330uF caps instead of 3x470uF. Could this be the cause for this? I also didn't include all the other smaller components that Felix recommended as I didn't feel capable of soldering them.
Is it more likely that it's insufficient capacitance or that I did a shoddy solder job and that maybe the solder isn't making proper contact and the RSX is cutting out because of that?

I replaced the caps with 470uF caps but I still get the triple beep after 15 minutes of LittleBigPlanet 2, what's the most likely culprit now?

 

[552eden]

I think my syscon is dead / has a short

Ps3 cechA00 with cok001 board has instant blinking red light

On syscon access I can get errlog sometime but when trying to enter internal mode (EEP set 3961 01 00) I get error E00000A0 which means write failed

Any ideas? Maybe voltages to check around the chip?

Thanks

Edit: by pure luck I managed to find a dead cap on the 3v3 rail and that fixed the above issue

But now the cell is sure it's over hearing in 5 seconds after boot (syscon error a0801200) what should I check? It's is not hot and I tested with heatsink + fan connected

Thanks all

FIXED!

Heres how:


I had some weird issues with my ps3 syscon. It would not let me write the internal mode value (w 3961 01 00) and would not boot the system
I found out this capacitor (C4069 ) was shorted. Removed it and the issue is solved!
I spent literally 2 years hunting for this solution so if your syscon is acting up check the 1.8 and 3.3 v rails for any shorts!!

 

[Bines]

Syscon error log I got from a PS3 I bought a while back off of ebay, thought it'd be fun to mess with.
I think last time I heard it was a corrupted NOR or something, but I wanted to make sure and then figure out how the hell to actually fix it.
It's a KTE 001 motherboard if that helps.

00000000
# CODE CLOCK
# A0805FFF 2F78B20F
# A0805FFF 2F78B1DB
# A0805FFF 2F78B1A1
# A0805FFF 2F78B141
# A0805FFF 2F7247A0
# A0805FFF 2F70908E
# A0805FFF 2F709058
# A0805FFF 2F709024
# A0805FFF 2F708FF8
# A0805FFF 2F708D13
# A0805FFF 2F708CD6
# A0805FFF 2F708C8F
# A0805FFF 2F64750F
# A0805FFF 2F6474CD
# A0805FFF 2F647487
# A0805FFF 2A01A773
# A0805FFF 2A01A203
# A0805FFF 2A01A082
# A0805FFF 2A01A04C
# A0805FFF 2A007A46
# A0805FFF 2A0079E9
# A0805FFF 2A0079A3
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

I'm getting much the same error but on a JSD-001 board. The best info I can find is at the very very bottom of this page https://www.psdevwiki.com/ps3/Syscon_Error_Codes#Data_Errors. It's even specific to your board but has a bit extra error info suggesting it's a problem with the XDR (memory).

I managed to replicate the extra info from the link by running errlog, followed by bringup (in my case the ps3 shuts itself off again after roughly 40s) and then running errlog again. Looks like this:

>$ errlog
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 3.5.0
#!(Build ID: 4002,46268,
#!Build Date: 2010-09-21_18:48:40)
#!
#!Copyright(C) 2010 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.

There's a whole bunch of other lines below that all containing 4 digits/letters so you might have to scroll up a bit but the important bit seems to be the "XDR Link not initilized". If you get the same thing the best I can suggest is have a look around the memory chips on your board see if there's any gunk or damage.

From what I can tell it could be a CPU/CELL problem too as the error isn't overly specific and just means the CELL isn't able to communicate with the XDR, so could be either one or the connections between.