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

Jeff Lonestar said:
Error Log
01: A0802022 Sat Mar 18 02:03:07 2023
02: A0802022 Sat Mar 18 01:46:53 2023
Click to expand...

Funny thing i forgot to mention about error log 1 & 2, it was actually Fri Mar 17 07:46 & 08:03 when i dumped syscon thru CFW. the Time in the syscon dump jumped ahead by 6 hours in the dump, but was still the correct time on my XMB. Dont know if thats helpful, Just found that funny / weird.
 
Jeff Lonestar said:
Funny thing i forgot to mention about error log 1 & 2, it was actually Fri Mar 17 07:46 & 08:03 when i dumped syscon thru CFW. the Time in the syscon dump jumped ahead by 6 hours in the dump, but was still the correct time on my XMB. Dont know if thats helpful, Just found that funny / weird.
Click to expand...
the fact that you have 2022 error is the reason you can't do 480p your av controller is gonna die get it replaced and error will be gone
 
Any second opinions on this? I took a look at the error codes and it seems like it's dead / needs a reball / frankenstein GPU.

Hoping it just needs tantalum capacitors, but that seems like a dream according to the errors.

CECHH01
>$ ERRLOG GET 00
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0403034 0CB2B0EF
>$ ERRLOG GET 1B
00000000 A0404401 0CB2B0EF
>$ ERRLOG GET 1C
00000000 A0403034 0CB2AF87
>$ ERRLOG GET 1D
00000000 A0404401 0CB2AF87
>$ ERRLOG GET 1E
00000000 A0403034 0CB2AF7D
>$ ERRLOG GET 1F
00000000 FFFFFFFF 0CB2AF7D

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

>$ becount
103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404401
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
becount
Bringup : 3003 times
Shutdown: 2901 times
Power-on: 145day 18hour 55min 14sec
[mullion]$
 
Master801 said:
Any second opinions on this? I took a look at the error codes and it seems like it's dead / needs a reball / frankenstein GPU.

Hoping it just needs tantalum capacitors, but that seems like a dream according to the errors.
Click to expand...
3034 bga error inspect if it's already worked on or droped if not than get rsx swapped with 40mm
 
EPDC6zl
l just got 3034 error code on my ps3 and l want to reball my cpu and gpu but when l showed my ps3 to ps3 repair sevices they said that l scratched my cpu and it's unfixable what you guys think?

https://imgur.com/a/EPDC6zl

Edit: Cell and Rsx already reflowed
 
Last edited:
CrazyRati0n said:
These errors are not recorded in SYSCON for no reason. I suspect previous owner must have experienced YLOD in the past, but he merely didn't tell you that.
Click to expand...
1001 errors occur normally when you turn the console off incorrectly or it power goes out. It's a cpu power failure resulting from an unexpected shutdown. Could mean nothing more than the owner lived in an area that experiances frequent power outages. It does not necessarily mean tokins. It would only mean that, if you observed the console die, during normal operation with that code. And only that code.

The 1002 is indicative of RSX tokins. So I'm inclind to suspect the tokins in that console are potentially getting close to failure. He should stress test the console in TLOU to see if the YLOD occurs and what new code it generates. If 1001, then it's CPU tokins. If 1002, it's RSX tokins.
 
solaralex said:
Hi, I am getting the following errlog after delidding a CECHE01 this month:

ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0x0de3f771 2007/05/21 06:23:45
ofst[ 4]:err_code:0xa0801004, clock:0x0de3f8e3 2007/05/21 06:29:55
ofst[ 8]:err_code:0xa0801004, clock:0x0de3f961 2007/05/21 06:32:01
ofst[ 12]:err_code:0xa0801004, clock:0x0de3f9e7 2007/05/21 06:34:15
ofst[ 16]:err_code:0xa0801004, clock:0x0de3fabd 2007/05/21 06:37:49
ofst[ 20]:err_code:0xa0801004, clock:0x0de3fd74 2007/05/21 06:49:24
ofst[ 24]:err_code:0xa0801004, clock:0x0de3fe34 2007/05/21 06:52:36
ofst[ 28]:err_code:0xa0801004, clock:0x10e609db 2008/12/25 09:07:39
ofst[ 32]:err_code:0xa0801001, clock:0x11f15b0e 2009/07/16 03:29:18
ofst[ 36]:err_code:0xa0801004, clock:0x11f15c7c 2009/07/16 03:35:24
ofst[ 40]:err_code:0xa0801004, clock:0x11f15cb2 2009/07/16 03:36:18
ofst[ 44]:err_code:0xa0801004, clock:0x129916b2 2009/11/20 08:58:26
ofst[ 48]:err_code:0xa0801004, clock:0x2b57e0a5 2023/01/16 10:17:09 <---PS3 was working until here
ofst[ 52]:err_code:0xa0404411, clock:0xffffffff <---after delid

I thought I was really careful :( The only info I could find about 4411 was from the quote below. But this error is seen here by itself, without 3034 etc. Any ideas?
Click to expand...
would you mind posting the full errorlog and the bringup please? I only see 14 errors there. There should be 32. And the bringup string would show more info about it. I am confident there is a 3034 there.
 
Max777x said:
Help me People's!

Errors no
Click to expand...

we need more information than that. What model PS3? What have you tried? How does it act? Are you getting tripple beep? Yellow LED before flashing red?

It turns off and no errors doesn't give us enough to go off of.
 
Jeff Lonestar said:
Getting that weird 2022 error on my working ps3 slim 2001a, mentioned a few post back by other ppl. I bought this console recently off ebay, just needed a new laser which has been replaced. Upon further testing it cant do 480p anymore via the multiAV cord, 480i does work tho. Other than that the console works fine, Thoughts?

Bringup Count: 2470, Shutdown Count: 2102
Runtime: 237 Days, 5 Hours, 17 Minutes, 55 Seconds
Error Log
01: A0802022 Sat Mar 18 02:03:07 2023
02: A0802022 Sat Mar 18 01:46:53 2023
03: A0802022 Wed Mar 15 17:59:53 2023
04: A0802022 Wed Mar 15 17:59:50 2023
05: A0802022 Wed Mar 15 05:17:38 2023
06: A0802022 Wed Mar 15 04:54:43 2023
07: A0802022 Thu Mar 9 04:46:40 2023
08: A0802022 Thu Mar 9 04:13:31 2023
09: A0802022 Sat Sep 3 12:08:44 2011
10: A0802022 Sat Sep 3 12:08:44 2011
11: A0802022 Sat Sep 3 12:08:43 2011
12: FFFFFFFF Fri Dec 31 16:59:59 1999
13: FFFFFFFF Fri Dec 31 16:59:59 1999
14: FFFFFFFF Fri Dec 31 16:59:59 1999
15: FFFFFFFF Fri Dec 31 16:59:59 1999
16: FFFFFFFF Fri Dec 31 16:59:59 1999
17: FFFFFFFF Fri Dec 31 16:59:59 1999
18: FFFFFFFF Fri Dec 31 16:59:59 1999
19: FFFFFFFF Fri Dec 31 16:59:59 1999
20: FFFFFFFF Fri Dec 31 16:59:59 1999
21: FFFFFFFF Fri Dec 31 16:59:59 1999
22: FFFFFFFF Fri Dec 31 16:59:59 1999
23: FFFFFFFF Fri Dec 31 16:59:59 1999
24: FFFFFFFF Fri Dec 31 16:59:59 1999
25: FFFFFFFF Fri Dec 31 16:59:59 1999
26: FFFFFFFF Fri Dec 31 16:59:59 1999
27: FFFFFFFF Fri Dec 31 16:59:59 1999
28: FFFFFFFF Fri Dec 31 16:59:59 1999
29: FFFFFFFF Fri Dec 31 16:59:59 1999
30: FFFFFFFF Fri Dec 31 16:59:59 1999
31: FFFFFFFF Fri Dec 31 16:59:59 1999
32: FFFFFFFF Fri Dec 31 16:59:59 1999
Click to expand...
DVE might be going out, or an SMD it needs to have a stable signal is failing. Hard to know.
 
Master801 said:
Any second opinions on this? I took a look at the error codes and it seems like it's dead / needs a reball / frankenstein GPU.

Hoping it just needs tantalum capacitors, but that seems like a dream according to the errors.

CECHH01
>$ ERRLOG GET 00
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0403034 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0404401 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0403034 0CB2B0EF
>$ ERRLOG GET 1B
00000000 A0404401 0CB2B0EF
>$ ERRLOG GET 1C
00000000 A0403034 0CB2AF87
>$ ERRLOG GET 1D
00000000 A0404401 0CB2AF87
>$ ERRLOG GET 1E
00000000 A0403034 0CB2AF7D
>$ ERRLOG GET 1F
00000000 FFFFFFFF 0CB2AF7D

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

>$ becount
103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404401
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
becount
Bringup : 3003 times
Shutdown: 2901 times
Power-on: 145day 18hour 55min 14sec
[mullion]$
Click to expand...
It's an H model. So yeah, GPU issues. And IMO not worth repairing. But perhaps it is sentimental to you...IDK.
 
Erim said:
EPDC6zl
l just got 3034 error code on my ps3 and l want to reball my cpu and gpu but when l showed my ps3 to ps3 repair sevices they said that l scratched my cpu and it's unfixable what you guys think?

https://imgur.com/a/EPDC6zl

Edit: Cell and Rsx already reflowed
Click to expand...
Looks like you scratched the traces by the XDR. Currently if it has a 3034, it may not get far enough into the boot sequence for an XDR not initialized GLOD to occur (which can result from a scratch like that). So until the tech reballs the RSX to fix the 3034, he wont know for sure. But it looks likely the attempt will be doomed to fail regardless.

It's hard to see how bad the scratch is from the photo, but I'd trust the tech on this one. He's trying to save you a pointless attempt fee! Good on him for not just attempting and charging you anyway, knowing full well it would fail regardless.
 
Hey, first time posting. Please be gentle on me... haha This thread is crazy amazing and so much information. Makes it almost hard to digest it all but based on what I have read and the syscon errors codes I have pulled from one of the fat PS3's I am working on with the following codes:

===================================
ERR 00: 00000000 A0093003 FFFFFFFF
ERR 01: 00000000 A0051002 FFFFFFFF
ERR 02: 00000000 A0093003 FFFFFFFF
ERR 03: 00000000 A0061002 FFFFFFFF
ERR 04: 00000000 A0093003 FFFFFFFF
ERR 05: 00000000 A0051002 FFFFFFFF
ERR 06: 00000000 A0093003 FFFFFFFF
ERR 07: 00000000 A0061002 FFFFFFFF
ERR 08: 00000000 A0093003 FFFFFFFF
ERR 09: 00000000 A0061002 FFFFFFFF
ERR 10: 00000000 A0093003 2B6ABFB0
ERR 11: 00000000 A0061002 2B6ABFB0
ERR 12: 00000000 A0093003 2B69C9E4
ERR 13: 00000000 A0051002 2B69C9E4
ERR 14: 00000000 A0093003 2B69C9DA
ERR 15: 00000000 A0051002 2B69C9DA
ERR 16: 00000000 A0801002 22CE6DE5
ERR 17: 00000000 A0801002 22CE6DD2
ERR 18: 00000000 A0801002 22CE6DBE
ERR 19: 00000000 A0801002 22CE6D97
===================================

Based on what most have posted here, The 1002 = RSX power filter channel (most like TOKIN) needs to be checked.
3003 = CELL power filter channel (most likely TOKINS) needs to be checked.

I replaced the power supply and no change. I can let the system sit without any power at all and can get it to boot once. I have checked voltages at various spots in the path and its OK until I try to power on, that is when the VDDC drops and the system beeps and turns off.

Should I just change out the TOKINs at this point and work backwards through the circuit paths for the CELL and RSX VDDC channels?

EDIT: I have had the system boot to the OS and interacted with it with a controlled connected. Since being taken completely apart and only the heatsinks and fan connected, I have not been able to get it to boot to the OS again.
 
RIP-Felix said:
with those errors, the CPU and RSX tokins appear to be at fault. Most likely. Start there and if that doesn't do it, cross that bridge when you come to it. You may find this useful, but it's not required.
Click to expand...
Thank you RIP-Felix. I suspected that was probably the best path since its related to voltages and I have seen it run idle at OS. Nice little board there, no need for the jumper wire anymore if you use that.
 
Hi guys!

This is my first post in the forum, so first of all, sorry if this is not the proper place to post this.

I would like to thank all the people for publishing all the ps3 debug stuff (information, schematics, syscon and so on).

I've just recovered three ps3 I had in a storage room for long time all of them model CECHC04 and motherboard COK-002 having YLOD. I've been checking them and I've reach a dead end for all of them, so here I am asking for some advice.

PS3 A
I checked the syscon error log and I got multiple a0403034 and a0404432 errors (mostly RSX bga issue), so I tried a home reflow (the flux + heat gun procedure).

It worked!!! but it heated a lot. Just in the XMB it reached more than 70ºC having the fan at 100%, so I decided to delid it. Afterwards I started getting the error a0801200 (Thermal CELL issue) just 2 secs after power on and the CELL was not hot at all.

May I have broken anything in the delid process? I've read in this thread at page 68 that replacing IC1101 from other PS3 worked, does it worth a try or is it more possible that the CELL is just dead now?

PS3 B
Same here, I had multiple a0403034 and a0404432 errors and proceed the same way doing a reflow. Now I get the error a0093004 (RSX power line) I've read this could be related to the NEC/TOKINs or anything in between. How do you recommend me to proceed?

PS3 C
I've no even checked the syscon here. After a quick visual inspection I realized this unit has Q6010 (SI4943BDY-T1-E3) burnt. I've found this replacement at aliexpress ( Item number 2023838548 - I'm not allowed to post links ) , does it look good to you? Is there any chance to fix this by replacing Q6010 or being it burnt could mean that there's other unseen issues? Being that the case what do you recommend me to do?

Any advice is welcome. Thank you
 
Last edited:
Hi, anybody can help me plz? I´m so confused about the solder points. I have the rx, tx, diag.
But i found nothing where to connect the diag that comes from ps3 board. And have i to solder a ground wire to the serial ttl ground pin?

EDIT: Got it.... it worked ....
P.S: In the pic the rx is green and tx is white. On mine usb to serial its opposite.
So i soldered the rx (white on mine) like the pic but it was wrong. The colors on the pic are correct. Only white must be named rx and green tx
 
Last edited:
LopoTRI said:
Hi, anybody can help me plz? I´m so confused about the solder points. I have the rx, tx, diag.
But i found nothing where to connect the diag that comes from ps3 board. And have i to solder a ground wire to the serial ttl ground pin?
Click to expand...

Yes, you need to connect the TTL ground to the ps3 board ground.

First leave diag unconnected, and use syscon CXR as explained in the PDF manual at github db260179/ps3syscon to set EEP 3961

Afterwards fully power off the ps3 (remove powercable) and connect diag also to ps3 ground, reconnect the power and use the CXRF mode
 
You must log in or register to reply here.

Similar threads

Back
Top