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

Anyone seen this error when sending commands? It doesnt seem to do it all the time. I did a CELL swap and 40nm on this A01. This started after the CELL swap. System had 403034 and nothing else after a RSX reball and with another RSX, CELL system that was swapped in only had 902120 and 403034 errors. System currently has 203010, not sure if the WmDiscOpr_ChuckOnEvent errors are due to the current CELL problem or not. Will try reflowing the CELL and then delid it to see if the die is cracked. Thanks
[mullion]$
clearerrlog
WmDiscOpr_ChuckOnEvent
ERRLOG CLEARED
[mullion]$ WmDiscOpr_ChuckOffEvent
w 3242 03 61 82 80 01 91
w complete!
WmDiscOpr_ChuckOnEvent
[mullion]$ WmDiscOpr_ChuckOffEvent
w 3242 03 61 82 80 01 91
w complete!
[mullion]$ WmDiscOpr_ChuckOnEvent
WmDiscOpr_ChuckOffEvent
w 3254 21 EC
w complete!
[mullion]$
w 348B 8B
w complete!
[mullion]$
w 34AF 8B
w complete!

EDIT: Fme. Took the IHS off and it looks like someone tried to delid it then stopped but the damaged wasnt visible until I moved the adhesive out of the way. I normally use my scope to inspect it but didnt see anything that would suggest a delid was attempted. Will put another CELL on it and see if that was the cause of the weird errors.
 
Last edited:
Hi I found an old PS3 in my uncle's house and he gave it to me it has YLOD and it seems like someone has opened it so I read the syscon and I got these results
Code:
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] Msg 2663 : being delayed.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] Msg 2663 : being delayed.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
 
1001 can be from the GLOD due to turning the switch off at the back of the console. Id try the RSX TOKINs first and see if that helps with the GLOD.
Yes, that makes sense. I switch off the Ps3 with the switch at the back in the event of a GLOD because nothing helps. Okay then I'll order 2 of the small pre-assembled boards that replace the NEC tokens and see if it boots.
 
Hi I found an old PS3 in my uncle's house and he gave it to me it has YLOD and it seems like someone has opened it so I read the syscon and I got these results
Code:
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] Msg 2663 : being delayed.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [SSM] Msg 2663 : being delayed.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$
These error codes are usually caused by a defective AV and/or HDMI encoder. I would replace them and then see if the Ps3 boots. You can replace just one at first and see if it comes on, if not replace the other one. Or you can replace both at the same time.
 
Hallo all. New member first time poster. I got a couple of PS3 in a joblot i bought and one of the is a CECHL04. From googling and reading a bit it seems it's not a very popular model but I would like to try and revive it.

It powers on and stays on but no display. It does not have YLOD. Can this model be diagnosed with the syscon uart log reading method?
If not, any ideas where I can start looking?
 
Hallo all. New member first time poster. I got a couple of PS3 in a joblot i bought and one of the is a CECHL04. From googling and reading a bit it seems it's not a very popular model but I would like to try and revive it.

It powers on and stays on but no display. It does not have YLOD. Can this model be diagnosed with the syscon uart log reading method?
If not, any ideas where I can start looking?
Yes, you can also read out the Syscon. However, this will probably only show you 1001 and 1004 as these occur when the Ps3 is not switched off. Have you tried resetting the Video Signal? If so, it is probably a GLOD. You could try to start it without the hard disk. With a very small number of Ps3 consoles, a GLOD can come from a defective hard disk to rule this out, simply remove the hard disk as the Ps3 without a hard disk at least displays a picture.
 
These error codes are usually caused by a defective AV and/or HDMI encoder. I would replace them and then see if the Ps3 boots. You can replace just one at first and see if it comes on, if not replace the other one. Or you can replace both at the same time.
thx for your help but i don't know what and HDMI or an AV encoder are they the ports or they are ICs in the motherboard can you explain to me
 
thx for your help but i don't know what and HDMI or an AV encoder are they the ports or they are ICs in the motherboard can you explain to me
These are the large ICs behind the HDMI and AV ports. The one behind the HDMI port should be from Panasonic and the one behind the AV port should be a Sony IC if i'm not mistaken.You can easily find them by following the ladder tracks from the RSX. But I'm not sure what number they have and whether you can reorder them. But in the worst case you would have to buy a YLOD motherboard and take them down, otherwise I could also see if I still have a defective CechG and could then send you the iCs.
 
These are the large ICs behind the HDMI and AV ports. The one behind the HDMI port should be from Panasonic and the one behind the AV port should be a Sony IC if i'm not mistaken.You can easily find them by following the ladder tracks from the RSX. But I'm not sure what number they have and whether you can reorder them. But in the worst case you would have to buy a YLOD motherboard and take them down, otherwise I could also see if I still have a defective CechG and could then send you the iCs.
thank you very much and the model that I have is an CECHL04
 
thank you very much and the model that I have is an CECHL04
Okay, I don't own that model but I do own a CechK which I think has the same mainboard as a CechL. The best thing to do is to take the console apart and see what the ICs are called. With a bit of luck you'll find them new on eBay or something.
 
Friend (Original owner) has a CECHA01 with YLOD. Turns off within 2 seconds of pressing on button. I've opened it up and found retrieved the following error codes.

My initial research is pointing to a reball. That's not in my toolset yet. Anyone have any advice on things I could try before jumping to a reball?


Code:
===================================
ERR 00: 00000000 A0403034 2E27663D
ERR 01: 00000000 A0403034 2E27663A
ERR 02: 00000000 A0403034 2E276636
ERR 03: 00000000 A0403034 2E276633
ERR 04: 00000000 A0403034 2E27662F
ERR 05: 00000000 A0403034 2E27662C
ERR 06: 00000000 A0403034 2E276628
ERR 07: 00000000 A0403034 2E276624
ERR 08: 00000000 A0403034 2E276620
ERR 09: 00000000 A0403034 2E27661A
ERR 10: 00000000 A0403034 1E160975
ERR 11: 00000000 A0403034 15BC6504
ERR 12: 00000000 A0403034 15B890D6
ERR 13: 00000000 A0403034 15B890D2
ERR 14: 00000000 A0403034 15B890BF
ERR 15: 00000000 A0403034 15B890B9
ERR 16: 00000000 A0403034 15B282A7
ERR 17: 00000000 A0403034 15B2829F
ERR 18: 00000000 A0403034 15AFEFC9
ERR 19: 00000000 A0403034 15AFEFC4
===================================
errlog
ofst[116]:err_code:0xffffffff, clock:0x1288f9e7  2009/11/08 03:39:19
ofst[120]:err_code:0xa0801701, clock:0x15a26285  2011/07/02 23:13:09
ofst[124]:err_code:0xa0801601, clock:0x15a26285  2011/07/02 23:13:09
ofst[  0]:err_code:0xa0403034, clock:0x15afefa2  2011/07/13 05:54:42
ofst[  4]:err_code:0xa0403034, clock:0x15afefb6  2011/07/13 05:55:02
ofst[  8]:err_code:0xa0403034, clock:0x15afefbe  2011/07/13 05:55:10
ofst[ 12]:err_code:0xa0403034, clock:0x15afefc4  2011/07/13 05:55:16
ofst[ 16]:err_code:0xa0403034, clock:0x15afefc9  2011/07/13 05:55:21
ofst[ 20]:err_code:0xa0403034, clock:0x15b2829f  2011/07/15 04:46:23
ofst[ 24]:err_code:0xa0403034, clock:0x15b282a7  2011/07/15 04:46:31
ofst[ 28]:err_code:0xa0403034, clock:0x15b890b9  2011/07/19 19:00:09
ofst[ 32]:err_code:0xa0403034, clock:0x15b890bf  2011/07/19 19:00:15
ofst[ 36]:err_code:0xa0403034, clock:0x15b890d2  2011/07/19 19:00:34
ofst[ 40]:err_code:0xa0403034, clock:0x15b890d6  2011/07/19 19:00:38
ofst[ 44]:err_code:0xa0403034, clock:0x15bc6504  2011/07/22 16:42:44
ofst[ 48]:err_code:0xa0403034, clock:0x1e160975  2015/12/30 03:18:13
ofst[ 52]:err_code:0xa0403034, clock:0x1e16097f  2015/12/30 03:18:23
ofst[ 56]:err_code:0xa0403034, clock:0x1e160991  2015/12/30 03:18:41
ofst[ 60]:err_code:0xa0403034, clock:0x2e273650  2024/07/15 01:22:24
ofst[ 64]:err_code:0xa0403034, clock:0x2e27366a  2024/07/15 01:22:50
ofst[ 68]:err_code:0xa0403034, clock:0x2e274021  2024/07/15 02:04:17
ofst[ 72]:err_code:0xa0403034, clock:0x2e275e30  2024/07/15 04:12:32
ofst[ 76]:err_code:0xa0403034, clock:0x2e27661a  2024/07/15 04:46:18
ofst[ 80]:err_code:0xa0403034, clock:0x2e276620  2024/07/15 04:46:24
ofst[ 84]:err_code:0xa0403034, clock:0x2e276624  2024/07/15 04:46:28
ofst[ 88]:err_code:0xa0403034, clock:0x2e276628  2024/07/15 04:46:32
ofst[ 92]:err_code:0xa0403034, clock:0x2e27662c  2024/07/15 04:46:36
ofst[ 96]:err_code:0xa0403034, clock:0x2e27662f  2024/07/15 04:46:39
ofst[100]:err_code:0xa0403034, clock:0x2e276633  2024/07/15 04:46:43
ofst[104]:err_code:0xa0403034, clock:0x2e276636  2024/07/15 04:46:46
ofst[108]:err_code:0xa0403034, clock:0x2e27663a  2024/07/15 04:46:50
ofst[112]:err_code:0xa0403034, clock:0x2e27663d  2024/07/15 04:46:53
=======================================================================
becount
Bringup : 1252 times
Shutdown: 1127 times
Power-on: 247day 19hour 00min 29sec
======================================
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
=======================================
>$ shutdown
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3: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)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
======================================
 
Friend (Original owner) has a CECHA01 with YLOD. Turns off within 2 seconds of pressing on button. I've opened it up and found retrieved the following error codes.

My initial research is pointing to a reball. That's not in my toolset yet. Anyone have any advice on things I could try before jumping to a reball?


Code:
===================================
ERR 00: 00000000 A0403034 2E27663D
ERR 01: 00000000 A0403034 2E27663A
ERR 02: 00000000 A0403034 2E276636
ERR 03: 00000000 A0403034 2E276633
ERR 04: 00000000 A0403034 2E27662F
ERR 05: 00000000 A0403034 2E27662C
ERR 06: 00000000 A0403034 2E276628
ERR 07: 00000000 A0403034 2E276624
ERR 08: 00000000 A0403034 2E276620
ERR 09: 00000000 A0403034 2E27661A
ERR 10: 00000000 A0403034 1E160975
ERR 11: 00000000 A0403034 15BC6504
ERR 12: 00000000 A0403034 15B890D6
ERR 13: 00000000 A0403034 15B890D2
ERR 14: 00000000 A0403034 15B890BF
ERR 15: 00000000 A0403034 15B890B9
ERR 16: 00000000 A0403034 15B282A7
ERR 17: 00000000 A0403034 15B2829F
ERR 18: 00000000 A0403034 15AFEFC9
ERR 19: 00000000 A0403034 15AFEFC4
===================================
errlog
ofst[116]:err_code:0xffffffff, clock:0x1288f9e7  2009/11/08 03:39:19
ofst[120]:err_code:0xa0801701, clock:0x15a26285  2011/07/02 23:13:09
ofst[124]:err_code:0xa0801601, clock:0x15a26285  2011/07/02 23:13:09
ofst[  0]:err_code:0xa0403034, clock:0x15afefa2  2011/07/13 05:54:42
ofst[  4]:err_code:0xa0403034, clock:0x15afefb6  2011/07/13 05:55:02
ofst[  8]:err_code:0xa0403034, clock:0x15afefbe  2011/07/13 05:55:10
ofst[ 12]:err_code:0xa0403034, clock:0x15afefc4  2011/07/13 05:55:16
ofst[ 16]:err_code:0xa0403034, clock:0x15afefc9  2011/07/13 05:55:21
ofst[ 20]:err_code:0xa0403034, clock:0x15b2829f  2011/07/15 04:46:23
ofst[ 24]:err_code:0xa0403034, clock:0x15b282a7  2011/07/15 04:46:31
ofst[ 28]:err_code:0xa0403034, clock:0x15b890b9  2011/07/19 19:00:09
ofst[ 32]:err_code:0xa0403034, clock:0x15b890bf  2011/07/19 19:00:15
ofst[ 36]:err_code:0xa0403034, clock:0x15b890d2  2011/07/19 19:00:34
ofst[ 40]:err_code:0xa0403034, clock:0x15b890d6  2011/07/19 19:00:38
ofst[ 44]:err_code:0xa0403034, clock:0x15bc6504  2011/07/22 16:42:44
ofst[ 48]:err_code:0xa0403034, clock:0x1e160975  2015/12/30 03:18:13
ofst[ 52]:err_code:0xa0403034, clock:0x1e16097f  2015/12/30 03:18:23
ofst[ 56]:err_code:0xa0403034, clock:0x1e160991  2015/12/30 03:18:41
ofst[ 60]:err_code:0xa0403034, clock:0x2e273650  2024/07/15 01:22:24
ofst[ 64]:err_code:0xa0403034, clock:0x2e27366a  2024/07/15 01:22:50
ofst[ 68]:err_code:0xa0403034, clock:0x2e274021  2024/07/15 02:04:17
ofst[ 72]:err_code:0xa0403034, clock:0x2e275e30  2024/07/15 04:12:32
ofst[ 76]:err_code:0xa0403034, clock:0x2e27661a  2024/07/15 04:46:18
ofst[ 80]:err_code:0xa0403034, clock:0x2e276620  2024/07/15 04:46:24
ofst[ 84]:err_code:0xa0403034, clock:0x2e276624  2024/07/15 04:46:28
ofst[ 88]:err_code:0xa0403034, clock:0x2e276628  2024/07/15 04:46:32
ofst[ 92]:err_code:0xa0403034, clock:0x2e27662c  2024/07/15 04:46:36
ofst[ 96]:err_code:0xa0403034, clock:0x2e27662f  2024/07/15 04:46:39
ofst[100]:err_code:0xa0403034, clock:0x2e276633  2024/07/15 04:46:43
ofst[104]:err_code:0xa0403034, clock:0x2e276636  2024/07/15 04:46:46
ofst[108]:err_code:0xa0403034, clock:0x2e27663a  2024/07/15 04:46:50
ofst[112]:err_code:0xa0403034, clock:0x2e27663d  2024/07/15 04:46:53
=======================================================================
becount
Bringup : 1252 times
Shutdown: 1127 times
Power-on: 247day 19hour 00min 29sec
======================================
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
=======================================
>$ shutdown
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3: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)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
======================================
Unfortunately not. You only have 3034 errors. Unfortunately, this means that there is no alternative but to replace the GPU in order to permanently repair the console.
There is of course a small possibility that it is the cell or the southbridge. But most of the time it is a defective GPU, especially in the first models. But if it's the cell or the southbridge, you'll have to replace it or reball it.
 
Last edited:
A friend asked me to try to fix a problem with his PS3 CECH-2008A. It turns on and works. If you don't connect the HDMI, it works for about 10 minutes. If you connect it and perform actions, it turns off after a minute. It turns off with a second YLOD, and then the RLOD flashes. A cold console works for some time, after warming up and the first shutdown it turns off immediately and so on until it cools down. Looking at the temperature right before turning off the CELL 68C and RSX 58C. Help please.

Code:
CECH-2008A

# CODE     CLOCK
# A08014FF 0B4D76E7
# A0801701 0B4D76E6
# A08014FF 0B4D76B9
# A0801701 0B4D76B8
# A0801701 0B4D76AA
# A08014FF 0B4D76AA
# A0801701 0B4D76A2
# A08014FF 0B4D76A1
# A0801701 0B4D769A
# A08014FF 0B4D769A
# A08014FF 0B4D7691
# A0801701 0B4D7691
# A0801701 0B4D7684
# A08014FF 0B4D7683
# A0801701 0B4D767B
# A08014FF 0B4D767A
# A0801701 0B4D7664
# A08014FF 0B4D7663
# A08014FF 0B4D764A
# A0801701 0B4D764A
# A08014FF 0B4BDB9B
# A0801701 0B4BDB9A
# A08014FF 0B4B600B
# A0801701 0B4B600B
# A0801701 0B4B5C07
# A08014FF 0B4B5C06
# A08014FF 0B4B5BFC
# A0801701 0B4B5BFB

>$ EEP GET 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 06 95 06 44 00 73 63 81

Bringups = 1695
Shutdowns = 1604
Days of uptime = 87(7562113 seconds)

>$ bringup
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$
F0000003
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.8.5
#!(Build ID: 3640,40665,
#!Build Date: 2009-06-29_21:04:39)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=24AE.
# [SSM] Fataldown Start.
# [SSM] Msg 24AC : being delayed.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Msg 24AC : ignored.
# [UCMD] Unknown command.

# CODE     CLOCK
# A08014FF 0B4A9EE5
# A0801701 0B4A9EE5
# A08014FF 0B4A9E1B
# A0801701 0B4A9E1A
# A08014FF 0B4A99D2
# A0801701 0B4A99D2
 
A friend asked me to try to fix a problem with his PS3 CECH-2008A. It turns on and works. If you don't connect the HDMI, it works for about 10 minutes. If you connect it and perform actions, it turns off after a minute. It turns off with a second YLOD, and then the RLOD flashes. A cold console works for some time, after warming up and the first shutdown it turns off immediately and so on until it cools down. Looking at the temperature right before turning off the CELL 68C and RSX 58C. Help please.

Code:
CECH-2008A

# CODE     CLOCK
# A08014FF 0B4D76E7
# A0801701 0B4D76E6
# A08014FF 0B4D76B9
# A0801701 0B4D76B8
# A0801701 0B4D76AA
# A08014FF 0B4D76AA
# A0801701 0B4D76A2
# A08014FF 0B4D76A1
# A0801701 0B4D769A
# A08014FF 0B4D769A
# A08014FF 0B4D7691
# A0801701 0B4D7691
# A0801701 0B4D7684
# A08014FF 0B4D7683
# A0801701 0B4D767B
# A08014FF 0B4D767A
# A0801701 0B4D7664
# A08014FF 0B4D7663
# A08014FF 0B4D764A
# A0801701 0B4D764A
# A08014FF 0B4BDB9B
# A0801701 0B4BDB9A
# A08014FF 0B4B600B
# A0801701 0B4B600B
# A0801701 0B4B5C07
# A08014FF 0B4B5C06
# A08014FF 0B4B5BFC
# A0801701 0B4B5BFB

>$ EEP GET 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 06 95 06 44 00 73 63 81

Bringups = 1695
Shutdowns = 1604
Days of uptime = 87(7562113 seconds)

>$ bringup
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$
F0000003
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.8.5
#!(Build ID: 3640,40665,
#!Build Date: 2009-06-29_21:04:39)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=24AE.
# [SSM] Fataldown Start.
# [SSM] Msg 24AC : being delayed.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Msg 24AC : ignored.
# [UCMD] Unknown command.

# CODE     CLOCK
# A08014FF 0B4A9EE5
# A0801701 0B4A9EE5
# A08014FF 0B4A9E1B
# A0801701 0B4A9E1A
# A08014FF 0B4A99D2
# A0801701 0B4A99D2
Looks like a defective RSX or one of its solder connections. It will probably display 3034 errors at some point if you continue to switch it on. A faulty solder connection would also fit with the fact that you said it works when it is cold but not when it is warm.
 
Looks like a defective RSX or one of its solder connections. It will probably display 3034 errors at some point if you continue to switch it on. A faulty solder connection would also fit with the fact that you said it works when it is cold but not when it is warm.
Okay, thank you. This means need to reball the RSX, I was hoping to avoid this.
 
Not as far as I know. YLOD and RLOD are not defects but the console says that something is wrong during the self-test and then switches off. It can be anything from a defective power supply unit to a defective cell or a defective fuse. Theoretically, any component can cause an RLOD or YLOD.
 
I followed your guide with the same adapter and i still cant auth in, i know for sure its grounded correctly and i also swapped the two cables around and it still didnt work, Is there something else i can do or is my Ps3 just dead?
 
PS3 Slim 2000
Syscon error code A0802022 freeze and artifacts.
The error may appear immediately or after some time of playing (usually a few minutes). The console simply freezes without any error message. Artifacts are also random.
Now I connected the console via composite and no problems for several hours. Could the problem be not in the RSX, but in the HDMI output chip? Has anyone encountered something similar?
 

Similar threads

Back
Top