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

Anyone have any suggestions for this one? Have an A01 that was opened but showed no signs of being worked on before. I thought it needed a CELL reballl but after doing a reball it still has A0233020, once it also had A0902120. I see no shorts or anything abnormal in the CELL power circuit. All fuses are good. PSU is good. Its only shown the 902120 error once in syscon but it always shows 233020

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

Bringup : 2452 times
Shutdown: 2417 times
Power-on: 256day 18hour 42min 26sec

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

NEW SYSCON ERRORS
ofst[  0]:err_code:0xa0233020, clock:0xffffffff
ofst[  4]:err_code:0xa0902120, clock:0xffffffff
 
First time try to fix broken Ps3 with Model: CECHL, I follow the UART steps got following syscon errors

So I need to replace NEC Tokin right ? or any advise before proceed?


===================================
ERR 00: 00000000 A0093004 FFFFFFFF
ERR 01: 00000000 A0093004 FFFFFFFF
ERR 02: 00000000 A0093004 FFFFFFFF
ERR 03: 00000000 A0093004 FFFFFFFF
ERR 04: 00000000 A0093004 FFFFFFFF
ERR 05: 00000000 A0093004 FFFFFFFF
ERR 06: 00000000 A0093004 FFFFFFFF
ERR 07: 00000000 A0093004 FFFFFFFF
ERR 08: 00000000 A0093004 FFFFFFFF
ERR 09: 00000000 A0093004 FFFFFFFF
ERR 10: 00000000 A0093004 FFFFFFFF
ERR 11: 00000000 A0093004 FFFFFFFF
ERR 12: 00000000 A0093004 FFFFFFFF
ERR 13: 00000000 A0093004 FFFFFFFF
ERR 14: 00000000 A0093004 FFFFFFFF
ERR 15: 00000000 A0093004 FFFFFFFF
ERR 16: 00000000 A0093004 FFFFFFFF
ERR 17: 00000000 A0802124 1A5D9F25
ERR 18: 00000000 A0802124 1A5D9F25
ERR 19: 00000000 A0801002 1A5D9F24
===================================
 
RetroPSNX said:
First time try to fix broken Ps3 with Model: CECHL, I follow the UART steps got following syscon errors

So I need to replace NEC Tokin right ? or any advise before proceed?


===================================
ERR 00: 00000000 A0093004 FFFFFFFF
ERR 01: 00000000 A0093004 FFFFFFFF
ERR 02: 00000000 A0093004 FFFFFFFF
ERR 03: 00000000 A0093004 FFFFFFFF
ERR 04: 00000000 A0093004 FFFFFFFF
ERR 05: 00000000 A0093004 FFFFFFFF
ERR 06: 00000000 A0093004 FFFFFFFF
ERR 07: 00000000 A0093004 FFFFFFFF
ERR 08: 00000000 A0093004 FFFFFFFF
ERR 09: 00000000 A0093004 FFFFFFFF
ERR 10: 00000000 A0093004 FFFFFFFF
ERR 11: 00000000 A0093004 FFFFFFFF
ERR 12: 00000000 A0093004 FFFFFFFF
ERR 13: 00000000 A0093004 FFFFFFFF
ERR 14: 00000000 A0093004 FFFFFFFF
ERR 15: 00000000 A0093004 FFFFFFFF
ERR 16: 00000000 A0093004 FFFFFFFF
ERR 17: 00000000 A0802124 1A5D9F25
ERR 18: 00000000 A0802124 1A5D9F25
ERR 19: 00000000 A0801002 1A5D9F24
===================================
Click to expand...
Yes, you need to replace the RSX TOKINs
 
GOOD MORNING,
I HAVE A JSD-001 GLOD PLATE.
IT TURNES ON, STAYS ON AND WORKS, BUT WITHOUT VIDEO. CI HDMI DOESN'T HAVE A SHORT, I REMOVED IT TO SEE IF THE VIDEO APPEARS ON THE AV, AND THE VIDEO DOES NOT APPEAR ON THE AV.
WHEN TURNED ON, THE HD LED WORKS, THE DUALSHOCK 3 SYNCS TOO. I CAN TURN IT OFF BY KEEPING THE POWER BUTTON PRESSED, I DON'T NEED TO PULL THE CABLE TO TURN IT OFF. SYSCON DISPLAYED ERROR 2022 A FEW TIMES IN A ROW.
I ALSO DID A REFLOW ON THE BOARD AND NOTHING, COULD SOMEONE HELP ME?
 
GOOD AFTERNOON,
FOLLOW THE ERRLOG:

# A0801200 FFFFFFFF
# A0012310 FFFFFFFF
# A0001004 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0802131 FFFFFFFF
# A0802131 FFFFFFFF
# A0802130 FFFFFFFF
# A0802131 FFFFFFFF
# A0802031 FFFFFFFF
# A0802131 FFFFFFFF
# A0802130 FFFFFFFF
# A0802022 0EF606F0
# A0802022 0EF606E0
# A0802022 0E7E48C3
# A0802022 0E7E26BD
# A0802022 0E649E72
# A0802022 0E649E38
# A0802022 0E45D462
# A0802022 0E45C930
# A0805FFF 0D1E5DFD
# A0805FFF 0BBB9D4B
# A0801200 0B49E11D
# A0801200 0B49DBDD
# A0801004 0B49D861
# A0801004 0B49D832
# A0801004 0B49D81B
# A0801004 0B49D801
# A0801004 0F41DA9E
# A0801004 0F41DA4F

I NOW REALIZED THAT BEFORE THE SEQUENCE OF ERROR 2022, THERE WERE TWO 5FFF ERROR, FROM WHAT I SAW IT COULD BE THE NOR OF THE PS3 BRICKED.
WOULD THIS BE THE SAME?
 
Hello, im working on a COK-002 motherboard. Im getting 3010 error on startup. It happend after CELL and RSX delid.
Somebody already replaced NEC TOKIN capacitors with tantalums. CELL has been delided, I checked under the microscope and it looks ok, has some scratches on the interposer, but there are no traces in the area. I made resistance mesurments around CELL and RSX and everything looks ok, but i have only 83 ohms on FBVDDQ. Console has previously 3034 error if this matters. Board doesn't have any sign of BGA rework.​
Here is bringup log:
Code: 
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[POWERSEQ] Error : wait attention timeout.(SEQ1)
[SSM] state: 0102 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0203010
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Can somebody give me hint what to check next? Any help will be appreciated.
 
Hi, I'm new here, I got some problems with my ps3, I have bought it about 3 or 4 month ago and yet (2 weeks ago) it was working great, now it turns off by itself absolutely randomly without light or anything, and if I attempt to pressing button on the light turns red, I have watched some videos and it seems like it's the NLOD/YLOD. It also has some error codes and I'm wondering if there is a way to fix it.
These are what errors happend while I used ps3
# 0xA0805fff (cell rsx)
# 0xA08014ff (check stop)
# 0xA0801701 (Cell be Attention)

These are before I bought ps3

# 0xA0802131 (thermal sensor rsx)
# 0xA0802031 (thermal sensor rsx)
# 0xA0802130 (thermal sensor cell)
 
Chmielu77 said:
Hello, im working on a COK-002 motherboard. Im getting 3010 error on startup. It happend after CELL and RSX delid.
Somebody already replaced NEC TOKIN capacitors with tantalums. CELL has been delided, I checked under the microscope and it looks ok, has some scratches on the interposer, but there are no traces in the area. I made resistance mesurments around CELL and RSX and everything looks ok, but i have only 83 ohms on FBVDDQ. Console has previously 3034 error if this matters. Board doesn't have any sign of BGA rework.​
Here is bringup log:
Code: 
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[POWERSEQ] Error : wait attention timeout.(SEQ1)
[SSM] state: 0102 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0203010
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Can somebody give me hint what to check next? Any help will be appreciated.
Click to expand...

It's a very early step in the sequence, so it's most likely voltage related. I would suspect delid gone wrong or somebody had done eraser mod. Cell is damaged, most likely. Your FBVDDQ is ok.
 
Hey everyone!

I have a PS3 Slim CECH-2501A board model JSD-001 with no signal - green light stays on but no picture from AV or HDMI. I got the error log from SYSCON to know where to start but all I'm getting is FFFFFFFF. Not sure but maybe this has something with the battery being dead. I swapped the battery but still all FFFFFFFF. Is there a way to encrypt this?
Or do I need to reassemble the console again and get a new errlog? I'd rather not do this.

Any help is appreciated!

Code: 
>$ errlog
00000000
# [SSM] Shutdown ok.
# (PowerOff State)
OK 00000000
# CODE     CLOCK
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
 
DeadEnd said:
It's a very early step in the sequence, so it's most likely voltage related. I would suspect delid gone wrong or somebody had done eraser mod. Cell is damaged, most likely. Your FBVDDQ is ok.
Click to expand...
Thank you for your response.
I think only thing done by previous owner/technician working on this console was tantalum mod and replacing thermalpaste on IHS. I again looked under the microscope and CELL die is intact, no missing components nearby. no scratched on traces. So im wondering, what could gone wrong with delid process? I I've done it before multiple times with sucess, so that makes mi curios. Before delid console had YLOD with 3034 error code, and I was preparing it for RSX replacement. You said it's most likely voltage issue, and then you suspected CELL damage. Can CELL damage be responsible for voltage related issues? Do I understand correctly, or i misunderstood something?
 
Chmielu77 said:
Thank you for your response.
I think only thing done by previous owner/technician working on this console was tantalum mod and replacing thermalpaste on IHS. I again looked under the microscope and CELL die is intact, no missing components nearby. no scratched on traces. So im wondering, what could gone wrong with delid process? I I've done it before multiple times with sucess, so that makes mi curios. Before delid console had YLOD with 3034 error code, and I was preparing it for RSX replacement. You said it's most likely voltage issue, and then you suspected CELL damage. Can CELL damage be responsible for voltage related issues? Do I understand correctly, or i misunderstood something?
Click to expand...

Well, I've googled similar errors and it seems to happen most commonly due to Cell damage. But I have not personally had it. I just could not see anybody who fixed it. You can see a few examples here https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3010

Voltage related, because of the step 20, which means if voltages are ok then the processors can begin to initialize (I may be wrong). However, 3010 seems to mean that CPU or RSX core cannot initialize. So whatever the reason, it may be that voltages are ok but the core is damaged. If you look at felix's explanations of steps, step 20 is related to RSX core. so I suppose you could try replacing RSX. But I am not sure if syscon always follows the exact pattern as described. Maybe @RIP-Felix Can share if he has ever seen step 20 3010 fixed by rsx replacement?

step20-21.png
 
Last edited:
DeadEnd said:
Well, I've googled similar errors and it seems to happen most commonly due to Cell damage. But I have not personally had it. I just could not see anybody who fixed it. You can see a few examples here https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3010

Voltage related, because of the step 20, which means if voltages are ok then the processors can begin to initialize (I may be wrong). However, 3010 seems to mean that CPU or RSX core cannot initialize. So whatever the reason, it may be that voltages are ok but the core is damaged. If you look at felix's explanations of steps, step 20 is related to RSX core. so I suppose you could try replacing RSX. But I am not sure if syscon always follows the exact pattern as described. Maybe @RIP-Felix Can share if he has ever seen step 20 3010 fixed by rsx replacement?

View attachment 44262
Click to expand...
Thank you for the explanations. Now i understand. I will try RSX replacement, but im currently out of 65/40 nm ones, and waiting for the delivery of slim donors. When i replace RSX i will come back with result.
 
DeadEnd said:
¨

Oh lord, DO NOT use chipquik. I learned the hard way. The only good ones are the genuine AMTECH NC-559-V2-TF or Stirri.
.
Click to expand...
Personaly i can recomend a geniue Warton Future HF Jelly flux. Works great for me on BGA and SMD reworks, easy to clean and doesn't smell like death xD. Atlest in Poland it's not that expensive and widely avaliable.
 
Ksqy said:
Hi guys, I have a CECH Q00 (DIA-001, they are NOT VER-001 like some say, so 90nm RSX) YLOD. Sometimes 3 seconds, sometimes longer. It seems to be going into recovery mode by itself on the longer ones. No obvious signs of damage. Warranty seal was void however, original Sony thermal paste was present. Seems like the system was last used in 2010, which is crazy being a 2009 system with 314 days LOL

Error log is as follows: Im assuming this is NEC Tokins but would appreciate a 2nd opinion
Code: 
ofst[ 36]:err_code:0xffffffff, clock:0x132a378a  2010/03/10 10:57:14
ofst[ 40]:err_code:0xa0802022, clock:0x132a3faa  2010/03/10 11:31:54
ofst[ 44]:err_code:0xa0802022, clock:0x132a44cd  2010/03/10 11:53:49
ofst[ 48]:err_code:0xa0802022, clock:0x132f2fe0  2010/03/14 05:25:52
ofst[ 52]:err_code:0xa0802022, clock:0x132f3076  2010/03/14 05:28:22
ofst[ 56]:err_code:0xa0802022, clock:0x13487bd9  2010/04/02 09:56:41
ofst[ 60]:err_code:0xa0802022, clock:0x13487d6e  2010/04/02 10:03:26
ofst[ 64]:err_code:0xa0801002, clock:0x2e1148a0  2024/06/28 10:10:40
ofst[ 68]:err_code:0xa0801002, clock:0x2e1148b3  2024/06/28 10:10:59
ofst[ 72]:err_code:0xa0801002, clock:0x2e114910  2024/06/28 10:12:32
ofst[ 76]:err_code:0xa0801002, clock:0x2e2685f3  2024/07/14 12:49:55
ofst[ 80]:err_code:0xa0801002, clock:0x2e26860d  2024/07/14 12:50:21
ofst[ 84]:err_code:0xa0801002, clock:0x2e26863d  2024/07/14 12:51:09
ofst[ 88]:err_code:0xa0801002, clock:0x2e2818b6  2024/07/15 17:28:22
ofst[ 92]:err_code:0xa0801002, clock:0x2e4fc52b  2024/08/14 19:42:35
ofst[ 96]:err_code:0xa0801002, clock:0x2e6372c2  2024/08/29 17:56:18
ofst[100]:err_code:0xa0801002, clock:0x2e6372e1  2024/08/29 17:56:49
ofst[104]:err_code:0xa0801002, clock:0x2e63731b  2024/08/29 17:57:47
ofst[108]:err_code:0xa0801002, clock:0x2e637325  2024/08/29 17:57:57
ofst[112]:err_code:0xa0001004, clock:0x2e637570  2024/08/29 18:07:44
ofst[116]:err_code:0xa0801002, clock:0x2e63757c  2024/08/29 18:07:56
ofst[120]:err_code:0xa0801002, clock:0x2e63758a  2024/08/29 18:08:10
ofst[124]:err_code:0xa0801002, clock:0x2e637591  2024/08/29 18:08:17
ofst[  0]:err_code:0xa0801002, clock:0x2e637598  2024/08/29 18:08:24
ofst[  4]:err_code:0xa0801002, clock:0x2e6375b0  2024/08/29 18:08:48
ofst[  8]:err_code:0xa0801002, clock:0x2e6375c9  2024/08/29 18:09:13
ofst[ 12]:err_code:0xa0801002, clock:0x2e6375fc  2024/08/29 18:10:04
ofst[ 16]:err_code:0xa0801002, clock:0x2e63763e  2024/08/29 18:11:10
ofst[ 20]:err_code:0xa0801002, clock:0x2e6376ab  2024/08/29 18:12:59
ofst[ 24]:err_code:0xa0801002, clock:0x2e66391c  2024/08/31 20:27:08
ofst[ 28]:err_code:0xa0801002, clock:0x2e66393a  2024/08/31 20:27:38
ofst[ 32]:err_code:0xa0801002, clock:0x2e6651d5  2024/08/31 22:12:37

>$ becount
becount
Bringup : 710 times
Shutdown: 689 times
Power-on: 314day 04hour 06min 31sec
Click to expand...

Can confirm RSX Tokins have got the system working (removed without heat and installed with soldering iron only to avoid heating unnecessary points on the board. I will update if it fails again. Another Japanese limited edition unit saved
 
RetroPSNX said:
First time try to fix broken Ps3 with Model: CECHL, I follow the UART steps got following syscon errors

So I need to replace NEC Tokin right ? or any advise before proceed?


===================================
ERR 00: 00000000 A0093004 FFFFFFFF
ERR 01: 00000000 A0093004 FFFFFFFF
ERR 02: 00000000 A0093004 FFFFFFFF
ERR 03: 00000000 A0093004 FFFFFFFF
ERR 04: 00000000 A0093004 FFFFFFFF
ERR 05: 00000000 A0093004 FFFFFFFF
ERR 06: 00000000 A0093004 FFFFFFFF
ERR 07: 00000000 A0093004 FFFFFFFF
ERR 08: 00000000 A0093004 FFFFFFFF
ERR 09: 00000000 A0093004 FFFFFFFF
ERR 10: 00000000 A0093004 FFFFFFFF
ERR 11: 00000000 A0093004 FFFFFFFF
ERR 12: 00000000 A0093004 FFFFFFFF
ERR 13: 00000000 A0093004 FFFFFFFF
ERR 14: 00000000 A0093004 FFFFFFFF
ERR 15: 00000000 A0093004 FFFFFFFF
ERR 16: 00000000 A0093004 FFFFFFFF
ERR 17: 00000000 A0802124 1A5D9F25
ERR 18: 00000000 A0802124 1A5D9F25
ERR 19: 00000000 A0801002 1A5D9F24
===================================
Click to expand...
update: after replaced 2 NEC/TOKIN with 8 tantalum(bottom side, leave another 2 NEC/TOKIN near RSX), Now PS3 can boot (but it hard to boot, like 10 attempts only 2 times can boot) no more error 3004, but got error 2124 and 2024, according to wiki its Green Light Of Death (GLOD) ) or Red Light Of Death (RLOD). 2124 and 2024 related AV and HDMI encoders,should I change HDMI encorder ? which IC is HDMI encoder ? please advise thanks.
below is errlog mostly 2124.

>$ errlog
00000000
# CODE CLOCK
# A0112124 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
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
 
Hello Every one!
I am new here!

I have a fat PS3 C0K-001A
near instant YLOD
All errors:
A0201B02 FFFFFFFF

I did read online but am not sure what to do.
Thanks!
 
So I recently purchased a broken PS3 Fat (CECHE01) that wouldn't power on. To my surprise, it seemed to just be a faulty power supply, as there was no red power light when the console was plugged in. I also checked the 12v power rail with a multi-meter and it clearly wasn't receiving any voltage.

After swapping out the power supply with a confirmed working one, the PS3 booted, and everything seemed to be fine. A couple of days later, and after around 10 hours of use, however, I ran in to a YLOD while playing a game. The system would still boot, and stay on for a couple of minutes until shutting back down and giving the same YLOD error.

I went through the process of getting the syscon errors off of the system, and it all seems to be 14FF, 1601, and 1701 errors. Here's the latest log I've gotten:

Code: 
#errlog
#ofst[ 24]:err_code:0xffffffff, clock:0x0b6d8765 2006/01/28 01:37:41
#ofst[ 28]:err_code:0xa0801601, clock:0x0b6d8765 2006/01/28 01:37:41
#ofst[ 32]:err_code:0xa0801701, clock:0x0b6d87b2 2006/01/28 01:38:58
#ofst[ 36]:err_code:0xa08014ff, clock:0x0b6d87b2 2006/01/28 01:38:58
#ofst[ 40]:err_code:0xa0801601, clock:0x0b6d87b2 2006/01/28 01:38:58
#ofst[ 44]:err_code:0xa0801701, clock:0x0b6d899a 2006/01/28 01:47:06
#ofst[ 48]:err_code:0xa08014ff, clock:0x0b6d899a 2006/01/28 01:47:06
#ofst[ 52]:err_code:0xa0801601, clock:0x0b6d899a 2006/01/28 01:47:06
#ofst[ 56]:err_code:0xa0801701, clock:0x0b6d89c8 2006/01/28 01:47:52
#ofst[ 60]:err_code:0xa08014ff, clock:0x0b6d89c8 2006/01/28 01:47:52
#ofst[ 64]:err_code:0xa0801601, clock:0x0b6d89c8 2006/01/28 01:47:52
#ofst[ 68]:err_code:0xa0801701, clock:0x0b6d8a9c 2006/01/28 01:51:24
#ofst[ 72]:err_code:0xa08014ff, clock:0x0b6d8a9c 2006/01/28 01:51:24
#ofst[ 76]:err_code:0xa0801601, clock:0x0b6d8a9c 2006/01/28 01:51:24
#ofst[ 80]:err_code:0xa0801701, clock:0x0b6d8c2e 2006/01/28 01:58:06
#ofst[ 84]:err_code:0xa08014ff, clock:0x0b6d8c2e 2006/01/28 01:58:06
#ofst[ 88]:err_code:0xa0801601, clock:0x0b6d8c2e 2006/01/28 01:58:06
#ofst[ 92]:err_code:0xa0801701, clock:0x0b6e15d0 2006/01/28 11:45:20
#ofst[ 96]:err_code:0xa08014ff, clock:0x0b6e15d0 2006/01/28 11:45:20
#ofst[100]:err_code:0xa0801601, clock:0x0b6e15d0 2006/01/28 11:45:20
#ofst[104]:err_code:0xa0801701, clock:0x0b6ec998 2006/01/29 00:32:24
#ofst[108]:err_code:0xa08014ff, clock:0x0b6ec998 2006/01/29 00:32:24
#ofst[112]:err_code:0xa0801601, clock:0x0b6ec998 2006/01/29 00:32:24
#ofst[116]:err_code:0xa0801701, clock:0x0b74469c 2006/02/02 04:27:08
#ofst[120]:err_code:0xa08014ff, clock:0x0b74469c 2006/02/02 04:27:08
#ofst[124]:err_code:0xa0801601, clock:0x0b74469c 2006/02/02 04:27:08
#ofst[ 0]:err_code:0xa0801701, clock:0x0b7446c0 2006/02/02 04:27:44
#ofst[ 4]:err_code:0xa0801601, clock:0x0b7446c0 2006/02/02 04:27:44
#ofst[ 8]:err_code:0xa0404401, clock:0x0b7446cc 2006/02/02 04:27:56
#ofst[ 12]:err_code:0xa0403034, clock:0x0b7446cd 2006/02/02 04:27:57
#ofst[ 16]:err_code:0xa0404401, clock:0x0b7446d6 2006/02/02 04:28:06
#ofst[ 20]:err_code:0xa0403034, clock:0x0b7446d6 2006/02/02 04:28:06
#[mullion]$

Uptime is only about 66 days.

The system no longer powers on, and just throws a YLOD error.

I was hoping someone could help me make sense of the error messages. From what I've read, things point mostly to the RSX chip, but may also be the CELL processor. I've been working on troubleshooting a repairing retro consoles for a while now, but I have no experience working with a IR solder rework station.

If it's what the system needs, I may look in to buying a rework station and taking a crack at making a "Frankenstein" PS3 with a more modern and non-bumpgate affected RSX chip. It's very much something I'd like to learn to do.
 
Last edited:
Hello everyone, I recently found my old fat PS3 (CECHK01) and it was stuck in the "fixing corrupted files" loop so I changed out the hard drive to a larger one. Since I did that it will boot up and runs fine on the XMB or while watching movies but it won't stay on for very long when I try playing games, and it instantly shuts off if I try to run any PS2 games. I've searched online but I am still confused on what I should try first. Here's the error log

Code: 
Firmware Version: 4.91 (build 50754)
Platform ID: CokE10
Product Code: 00 84
Product Sub Code: 00 07
Hardware Config: 000000000107BCBF
Syscon Firmware Version: 0E69.0000000000040002 (EEPROM: 0000000000040002)

Bringup Count: 3057, Shutdown Count: 1762
Runtime: 230 Days, 16 Hours, 14 Minutes, 53 Seconds

Error Log
01: A0801002  Mon Sep 16 03:42:44 2024
02: A0802022  Mon Sep 16 03:33:59 2024
03: A0802022  Mon Sep 16 03:33:57 2024
04: A0802022  Mon Sep 16 03:25:23 2024
05: A0802022  Mon Sep 16 03:25:22 2024
06: A0802022  Mon Sep 16 03:21:22 2024
07: A0802022  Mon Sep 16 03:21:21 2024
08: A0801002  Tue Sep  3 15:06:09 2024
09: A0801001  Sun Oct 22 14:58:28 2017
10: A0002120  Sun Sep 24 21:22:08 2017
11: A0801002  Sun Sep 24 21:22:07 2017
12: A0002120  Sun Sep 24 17:56:13 2017
13: A0801002  Sun Sep 24 17:56:12 2017
14: A0003001  Sun Aug 27 20:17:02 2017
15: A0003001  Thu Aug 17 13:45:52 2017
16: A0003001  Wed Aug 16 11:37:50 2017
17: A0003001  Tue Aug 15 13:55:58 2017
18: A0003001  Mon Aug 14 18:29:53 2017
19: A0003001  Sun Aug  6 22:28:57 2017
20: A0003001  Sat Aug  5 05:13:07 2017
21: A0003001  Thu Aug  3 12:58:25 2017
22: A0003001  Tue Aug  1 16:38:41 2017
23: A0003001  Tue Aug  1 16:38:30 2017
24: A0003001  Mon Jul 31 23:36:16 2017
25: A0003001  Sat Jul 29 00:56:50 2017
26: A0003001  Sat Jul 29 00:56:40 2017
27: A0003001  Fri Jul 21 11:05:06 2017
28: A0003001  Thu Jul 20 11:53:36 2017
29: A0003001  Wed Jul 19 11:03:12 2017
30: A0003001  Wed Jul 19 11:02:53 2017
31: A0003001  Tue Jul 18 17:28:47 2017
32: FFFFFFFF  Mon Jul 17 12:27:58 2017
 
You must log in or register to reply here.

Similar threads

Back
Top