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

[shado214]

Hey guys,

Looking for some help with this one board. I got a DIA-001 with a YLOD. I connected to syscon and I got the following:

ERR 00: 00000000 A0003001 FFFFFFFF
ERR 01: 00000000 A0003001 FFFFFFFF
ERR 02: 00000000 A0022110 FFFFFFFF
ERR 03: 00000000 A0022110 FFFFFFFF
ERR 04: 00000000 A0022110 FFFFFFFF
ERR 05: 00000000 A0022110 FFFFFFFF
ERR 06: 00000000 A0022110 FFFFFFFF
ERR 07: 00000000 A0022110 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0022110 FFFFFFFF
ERR 10: 00000000 A0022110 FFFFFFFF
ERR 11: 00000000 A0022110 FFFFFFFF
ERR 12: 00000000 A0022110 FFFFFFFF
ERR 13: 00000000 A0022110 FFFFFFFF
ERR 14: 00000000 A0022110 FFFFFFFF
ERR 15: 00000000 A0022110 FFFFFFFF
ERR 16: 00000000 A0022110 0B488B58
ERR 17: 00000000 A0022110 0B488B3C
ERR 18: 00000000 A0022110 0B48885B
ERR 19: 00000000 A0022110 0B48884F

I can't find a board diagram for this model so I'm not sure where to look. I used my thermal cam when on standby and I can see heat around the top right corner (rx, tx diag area) which is right above the syscon chip if I'm not mistaken. No other heat spots anywhere else. From my understanding it has something to do with IC5001. The wiki refers to C6019 and C6020 but I don't know where they are.

I should also mention that I reflowed the RSX and CPU previously and it turned on but the usb ports weren't working. After investigating I realised the board wasn't plugged so I did the noob thing and plugged it in before unplugging the power. After that I got the YLOD with the errors above. I also replaced the tokin caps on the top side of the board for good measure.

Any help would be greatly appreciated.

Never mind, I guess trying to find a fault at midnight is not the best idea. F6001 is blown so that is most likely my issue.

 

[Joel_]

I have attached a photo showing the IC5001. At least I think it is this one. It would fit because it is connected to the Southbridge and the Bluetooth board connector. The photo is of a DIA-001 so you can look for the right place. I would look for short circuits in the area of this IC or switch on the Ps3 and check with your thermal camera whether anything gets hot in this area during startup. If you find short circuits, remove the IC and see if they are gone. On the other side near IC5001 there is also the fuse F6001 which has probably tripped if the IC is defective. I would also test this.

 

[shado214]

I have attached a photo showing the IC5001. At least I think it is this one. It would fit because it is connected to the Southbridge and the Bluetooth board connector. The photo is of a DIA-001 so you can look for the right place. I would look for short circuits in the area of this IC or switch on the Ps3 and check with your thermal camera whether anything gets hot in this area during startup. If you find short circuits, remove the IC and see if they are gone. On the other side near IC5001 there is also the fuse F6001 which has probably tripped if the IC is defective. I would also test this.

Thanks for the info! No shorts around the IC and no heat coming from the bottom of the board anywhere. I replaced the fuse with a 3A 32V to test and the ps3 came back from the dead I will source a proper replacement but for now I believe this ps3 is on it's way to full recovery. Thanks for your help

 

[Guzza]

Hi all, its my first time attempting to investigate SYSCON on a CECHC02 a friend bought at a thrift store almost 2 years ago.

I'm hoping someone can tell me where F6001 on the COK-002 Board is? i have Errors 2110 atm and had 1001 in the year 2007? and then 2x more 1001 before the 2110 start.
psdevwiki com/ps3/Syscon_Error_Codes#2110_(Clock_Subsystems) mentions this F6001 should be checked i dont know where it is but i realise the capacitors are probably my issue.

mate said he plugged it in, turned it on and it YLOD in <5minutes.
I opened and cleaned it and got nothing so its been on a shelf since I got it but I have time now to try.

thanks in advance

eepcsum

Addr:0x000032fe should be 0x528c

Addr:0x000034fe should be 0x7115

sum:0x0100

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
w 3dfe ff 00

w complete!

[mullion]$
ERRLOG

*** Unknown Command ***

[mullion]$
errlog

ofst[ 36]:err_code:0xffffffff, clock:0x0d97d4cd  2007/03/24 12:23:41

ofst[ 40]:err_code:0xa0801001, clock:0x0d97d601  2007/03/24 12:28:49

ofst[ 44]:err_code:0xa0802022, clock:0x0d9a6b77  2007/03/26 11:31:03

ofst[ 48]:err_code:0xa0801001, clock:0x0da4cb7b  2007/04/03 08:23:23

ofst[ 52]:err_code:0xa0801001, clock:0x0da6305e  2007/04/04 09:46:06

ofst[ 56]:err_code:0xa0801001, clock:0x0e2cabb8  2007/07/15 09:56:08

ofst[ 60]:err_code:0xa0802022, clock:0x0e8fb02e  2007/09/28 12:29:34

ofst[ 64]:err_code:0xa0801001, clock:0x0ec7d207  2007/11/10 02:20:55

ofst[ 68]:err_code:0xa0801001, clock:0x0ec91a3b  2007/11/11 01:41:15

ofst[ 72]:err_code:0xa0802022, clock:0x0ec91b4c  2007/11/11 01:45:48

ofst[ 76]:err_code:0xa0801001, clock:0x0ee33cae  2007/11/30 21:27:10

ofst[ 80]:err_code:0xa0801001, clock:0x0eed174a  2007/12/08 08:50:18

ofst[ 84]:err_code:0xa0801001, clock:0x290d1527  2021/10/28 08:00:39

ofst[ 88]:err_code:0xa0801001, clock:0x29128227  2021/11/01 10:47:03

ofst[ 92]:err_code:0xa0022110, clock:0x29128253  2021/11/01 10:47:47

ofst[ 96]:err_code:0xa0022110, clock:0x291282b1  2021/11/01 10:49:21

ofst[100]:err_code:0xa0022110, clock:0x291282ca  2021/11/01 10:49:46

ofst[104]:err_code:0xa0022110, clock:0x291282df  2021/11/01 10:50:07

ofst[108]:err_code:0xa0022110, clock:0x2912832b  2021/11/01 10:51:23

ofst[112]:err_code:0xa0022110, clock:0x29128335  2021/11/01 10:51:33

ofst[116]:err_code:0xa0022110, clock:0x29128389  2021/11/01 10:52:57

ofst[120]:err_code:0xa0022110, clock:0x29128397  2021/11/01 10:53:11

ofst[124]:err_code:0xa0022110, clock:0x291284e7  2021/11/01 10:58:47

ofst[  0]:err_code:0xa0022110, clock:0x29128529  2021/11/01 10:59:53

ofst[  4]:err_code:0xa0022110, clock:0x29472066  2021/12/11 08:40:06

ofst[  8]:err_code:0xa0022110, clock:0x29472080  2021/12/11 08:40:32

ofst[ 12]:err_code:0xa0022110, clock:0x29472086  2021/12/11 08:40:38

ofst[ 16]:err_code:0xa0022110, clock:0xffffffff

ofst[ 20]:err_code:0xa0022110, clock:0xffffffff

ofst[ 24]:err_code:0xa0022110, clock:0xffffffff

ofst[ 28]:err_code:0xa0022110, clock:0xffffffff

ofst[ 32]:err_code:0xa0022110, clock:0xffffffff

ofst[ 36]:err_code:0xa0022110, clock:0xffffffff

[mullion]$

becount

Bringup : 1413 times

Shutdown: 1394 times

Power-on: 167day 23hour 24min 53sec

[mullion]$
bringup

[SSM] state: 0000 -> 0101

Bringup Mode #0 (0xFF)

[SSM] ssmCb_OnStartingBePowOn() called.

[SSM] First Boot.

[SSM] Bringup mode : syspm_stat=00000000/00000000

[POWSEQ] PowerSeq_Setup called.

Thanks.

 

[Guzza]

Here are pictures of my motherboard COK-002
I Found it, its open circuit F6001 printed on board i just had to look.

 

[Joel_]

Thanks for the info! No shorts around the IC and no heat coming from the bottom of the board anywhere. I replaced the fuse with a 3A 32V to test and the ps3 came back from the dead I will source a proper replacement but for now I believe this ps3 is on it's way to full recovery. Thanks for your help

I'm glad to hear that. Then the fuse seems to have done its job in your case and protected your console from major damage.

 

[Guzza]

yeah im glad that's the first diagnosis, it has the marking "YD" on it and I'm researching its fuse rating I'm finding 15A but I'm not sure. .

 

[Joel_]

yeah im glad that's the first diagnosis, it has the marking "YD" on it and I'm researching its fuse rating I'm finding 15A but I'm not sure. .

According to the Sony service manual, the F6001 has a 5A/32V fuse

 

[Guzza]

According to the Sony service manual, the F6001 has a 5A/32V fuse

Thank you, I found a copy of that manual now thanks to you, I should have looked for it idk why I didn't. i'm struggling to find a like replacement, i got alot to sus in the meantime the NECs are no good and lots else to check for shorts but im inexperienced fixing ps3s ill just be gentle

 

[Joel_]

Thank you, I found a copy of that manual now thanks to you, I should have looked for it idk why I didn't. i'm struggling to find a like replacement, i got alot to sus in the meantime the NECs are no good and lots else to check for shorts but im inexperienced fixing ps3s ill just be gentle

The fact that you are not very familiar with Ps3s is not a bad thing. It's better to ask too many questions than too few. I wouldn't do anything with the NEC tokens for now and just replace the fuse. The 1001 can also be caused by improper switching off and, like the 2022 errors, are even sometimes present in fully functional Ps3 consoles. However, it is very important to order several in case a defective component has destroyed the F6001 fuse and if you do not remove it, it will destroy it again, so it is better to order a few more. For the same reason, you should never bypass fuses in general. You can find these fuses in large quantities on ebay for little money.

 

[GalacticBatman]

First of all my console (Cech-42xxA) is in working condition, so I'm not sure if this is the right thread to post this, but I did look at the syscon error log of my console through the ps3toolset.com method and was wondering what that could mean. Here's the error log:

Error 0: 0xA0805FFF Time: Wed, 24 Apr 2024 21:07:44 GMT
Error 1: 0xA0805FFF Time: Mon, 20 Mar 2023 17:05:29 GMT
Error 2: 0xA0805FFF Time: Mon, 20 Feb 2023 22:14:37 GMT
Error 3: 0xA0805FFF Time: Thu, 09 Feb 2023 01:03:07 GMT
Error 4: 0xA0802130 Time: Thu, 05 Jan 2023 23:08:47 GMT
Error 5: 0xA0805FFF Time: Mon, 24 Oct 2022 00:54:29 GMT
Error 6: 0xA0802022 Time: Fri, 17 Jun 2022 01:24:44 GMT
Error 7: 0xA0802022 Time: Fri, 17 Jun 2022 01:24:11 GMT
Error 8: 0xA0805FFF Time: Fri, 17 Jun 2022 00:57:17 GMT
Error 9: 0xA0802022 Time: Mon, 06 Jun 2022 18:44:40 GMT
Error 10: 0xA0802022 Time: Mon, 06 Jun 2022 18:35:17 GMT
Error 11: 0xA0802022 Time: Sat, 28 May 2022 16:44:37 GMT
Error 12: 0xA0802022 Time: Sat. 28 May 2022 16:44:14 GMT
Error 13: 0xA0802022 Time: Sat, 28 May 2022 14:05:46 GMT
Error 14: 0xA0802022 Time: Sat, 28 May 2022 13:59:37 GMT
Error 15: 0xA0802022 Time: Thu, 26 May 2022 02:38:20 GMT
Error 16: 0xA0802022 Time: Thu, 26 May 2022 02:25:38 GMT
Error 17: 0xA0802131 Time: Mon, 29 Jun 2015 18:24:17 GMT
Error 18: 0xA0802130 Time: Mon, 29 Jun 2015 18:24:16 GMT
Error 19: 0xA0802131 Time: Mon, 29 Jun 2015 18:24:14 GMT
Error 20: 0xA0802130 Time: Mon, 29 Jun 2015 18:24:12 GMT
Error 21: 0xA0802131 Time: Mon, 29 Jun 2015 18:23:40 GMT
Error 22: 0xA0802131 Time: Mon, 29 Jun 2015 18:23:39 GMT
Error 23: 0xA0802030 Time: Mon, 29 Jun 2015 18:23:38 GMT
Error 24: 0xA0802131 Time: Mon, 29 Jun 2015 18:23:37 GMT
Error 25: 0xA0802131 Time: Mon, 29 Jun 2015 18:23:36 GMT
Error 26: 0xA0802031 Time: Mon, 29 Jun 2015 18:23:35 GMT
Error 27: 0xA0802030 Time: Mon, 29 Jun 2015 18:28:33 GMT
Error 28: 0xA0802130 Time: Mon, 29 Jun 2015 18:23:31 GMT
Error 29: 0xA0802130 Time: Mon, 29 Jun 2015 18:23:27 GMT
Error 30: 0xA0802130 Time: Mon, 29 Jun 2015 18:23:26 GMT

I bought the console used in 2022. Cumulative uptime of 220 days.
Some of the errors seem to indicate issues with temperature sensors although most of them curiously happened back in 2015 in a matter of a minute. According to the log it did reoccur once during my ownership of the console although I don't remember noticing anything wrong with the cooling. The 5FFF error is also very curious to me as there doesn't seem to be much info on it. I've had some issues with the console completely freezing, requiring a hard shutdown by holding the power button and it refused to properly turn off a couple of times, but other than that it runs perfectly fine 99% of the time. I'm wondering if the 5FFF error might be related to a small bug in the firmware, memory corruption or maybe an hdd issue since I do have some corrupted save games on the HDD for some reason.

Hopefully someone with some experience can interpret what an error log like this might suggest about prevention of future issues.

I'm also thinking about connecting to the syscon via hardware once I've read up on all the info about how to do that properly. I mainly wanted to do this to modify the syscon fan profile, but in case there is something you guys are still looking for from a Cech-42 console in regards to syscon readout, please let me know. I'm not sure how complete the database is at this point and if there is anything that still needs to be confirmed about certain models.

 

[5krilaN]

Hello,

I have bought console "....thermal paste was repalce and the console was cleaned....." never before have seen something like that

Prepare all to read syscon

Result is as below, some starts betwen the reading ( 3 times)
I have read the information from page 119, try find boardview COK-002, it seams do it wrongly cant find.

What I should start with? Replace F6302 and C6320?

1st
===================================
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0202120 FFFFFFFF
ERR 02: 00000000 A0202120 FFFFFFFF
ERR 03: 00000000 A0202120 FFFFFFFF
ERR 04: 00000000 A0202120 FFFFFFFF
ERR 05: 00000000 A0202120 FFFFFFFF
ERR 06: 00000000 A0202120 FFFFFFFF
ERR 07: 00000000 A0202120 FFFFFFFF
ERR 08: 00000000 A0202120 FFFFFFFF
ERR 09: none0000 A0202120 FFFFFFFF
ERR 10: 00000000 A0202120 FFFFFFFF
ERR 11: 00000000 A0202120 FFFFFFFF
ERR 12: 00000000 A0202120 FFFFFFFF
ERR 13: 00000000 A0202120 FFFFFFFF
ERR 14: 00000000 A0202120 FFFFFFFF
ERR 15: 00000000 A0202120 FFFFFFFF
ERR 16: 00000000 A0202120 FFFFFFFF
ERR 17: 00000000 A0012031 FFFFFFFF
ERR 18: 00000000 A0A02030 FFFFFFFF
ERR 19: 00000000 A0213013 FFFFFFFF
===================================
2nd
===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0202120 FFFFFFFF
ERR 03: 00000000 A0202120 FFFFFFFF
ERR 04: 00000000 A0202120 FFFFFFFF
ERR 05: 00000000 A0202120 FFFFFFFF
ERR 06: 00000000 A0202120 FFFFFFFF
ERR 07: 00000000 A0202120 FFFFFFFF
ERR 08: 00000000 A0202120 FFFFFFFF
ERR 09: 00000000 A0202120 FFFFFFFF
ERR 10: 00000000 A0202120 FFFFFFFF
ERR 11: 00000000 A0202120 FFFFFFFF
ERR 12: 00000000 A0202120 FFFFFFFF
ERR 13: 00000000 A0202120 FFFFFFFF
ERR 14: 00000000 A0202120 FFFFFFFF
ERR 15: 00000000 A0202120 FFFFFFFF
ERR 16: 00000000 A0202120 FFFFFFFF
ERR 17: 00000000 A0213013 FFFFFFFF
ERR 18: 00000000 A0202120 FFFFFFFF
ERR 19: 00000000 A0202120 FFFFFFFF
===================================
3rd
===================================
ERR 00: FFFFFFFF Magic
ERR 01: 00000000 A0202120 FFFFFFFF
ERR 02: 00000000 A0202120 FFFFFFFF
ERR 03: 00000000 A0202120 FFFFFFFF
ERR 04: 00000000 A0202120 FFFFFFFF
ERR 05: 00000000 A0202120 FFFFFFFF
ERR 06: 00000000 A0202120 FFFFFFFF
ERR 07: 00000000 A0202120 FFFFFFFF
ERR 08: 00000000 A0202120 FFFFFFFF
ERR 09: 00000000 A0202120 FFFFFFFF
ERR 10: 00000000 A0202120 FFFFFFFF
ERR 11: 00000000 A0202120 FFFFFFFF
ERR 12: 00000000 A0202120 FFFFFFFF
ERR 13: 00000000 A0202120 FFFFFFFF
ERR 14: 00000000 A0202120 FFFFFFFF
ERR 15: 00000000 A0202120 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
ERR 17: 00000000 A0202120 FFFFFFFF
ERR 18: 00000000 A0202120 FFFFFFFF
ERR 19: 00000000 A0202120 FFFFFFFF
===================================

 

[NeonBlack]

First time posting and thank you for your effort and perseverance in investigating the issues of the beloved PlayStation 3.

I have two 60GB launch consoles, PAL CECHC04, both death for YLOD.
For now I opened one and extracted the logs from the SYSCON.
They are as follows:

Spoiler: errlog

ofst[116]:err_code:0xffffffff, clock:0x0f415020 2008/02/10 06:03:12
ofst[120]:err_code:0xa0404432, clock:0x0f415041 2008/02/10 06:03:45
ofst[124]:err_code:0xa0403034, clock:0x0f415041 2008/02/10 06:03:45
ofst[ 0]:err_code:0xa0801701, clock:0x0f415256 2008/02/10 06:12:38
ofst[ 4]:err_code:0xa0801601, clock:0x0f415256 2008/02/10 06:12:38
ofst[ 8]:err_code:0xa0404432, clock:0x0f415316 2008/02/10 06:15:50
ofst[ 12]:err_code:0xa0403034, clock:0x0f415316 2008/02/10 06:15:50
ofst[ 16]:err_code:0xa0404432, clock:0x0f415329 2008/02/10 06:16:09
ofst[ 20]:err_code:0xa0403034, clock:0x0f415329 2008/02/10 06:16:09
ofst[ 24]:err_code:0xa0801802, clock:0x0f423b44 2008/02/10 22:46:28
ofst[ 28]:err_code:0xa0404432, clock:0x0f423b72 2008/02/10 22:47:14
ofst[ 32]:err_code:0xa0403034, clock:0x0f423b73 2008/02/10 22:47:15
ofst[ 36]:err_code:0xa0801701, clock:0x0f4a58fa 2008/02/17 02:31:22
ofst[ 40]:err_code:0xa0801601, clock:0x0f4a58fa 2008/02/17 02:31:22
ofst[ 44]:err_code:0xa0404432, clock:0x0f4a593c 2008/02/17 02:32:28
ofst[ 48]:err_code:0xa0403034, clock:0x0f4a593c 2008/02/17 02:32:28
ofst[ 52]:err_code:0xa0404432, clock:0x0f4a59cf 2008/02/17 02:34:55
ofst[ 56]:err_code:0xa0403034, clock:0x0f4a59cf 2008/02/17 02:34:55
ofst[ 60]:err_code:0xa0404432, clock:0x0f4a5a7c 2008/02/17 02:37:48
ofst[ 64]:err_code:0xa0403034, clock:0x0f4a5a7c 2008/02/17 02:37:48
ofst[ 68]:err_code:0xa0404432, clock:0x0f4a5a8f 2008/02/17 02:38:07
ofst[ 72]:err_code:0xa0403034, clock:0x0f4a5a8f 2008/02/17 02:38:07
ofst[ 76]:err_code:0xa0404432, clock:0x0f898ace 2008/04/05 00:56:46
ofst[ 80]:err_code:0xa0403034, clock:0x0f898ace 2008/04/05 00:56:46
ofst[ 84]:err_code:0xa0404432, clock:0x0f898b02 2008/04/05 00:57:38
ofst[ 88]:err_code:0xa0403034, clock:0x0f898b02 2008/04/05 00:57:38
ofst[ 92]:err_code:0xa0404432, clock:0x13e4b67a 2010/07/29 22:00:26
ofst[ 96]:err_code:0xa0403034, clock:0x13e4b67a 2010/07/29 22:00:26
ofst[100]:err_code:0xa0404432, clock:0x13e4b707 2010/07/29 22:02:47
ofst[104]:err_code:0xa0403034, clock:0x13e4b707 2010/07/29 22:02:47
ofst[108]:err_code:0xa0404432, clock:0x13e4b720 2010/07/29 22:03:12
ofst[112]:err_code:0xa0403034, clock:0x13e4b720 2010/07/29 22:03:12

Spoiler: becount

Bringup : 1896 times
Shutdown: 1873 times
Power-on: 102day 18hour 32min 40sec

Spoiler: 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:0x21e2

Those 3034 errors are clearly pointing in the faulty RSX way, don't you think?
That's why, yesterday I purchased a slim CECH-3004A, in order to get a 40 NM SRX.
I don't have the skills or tools for the frankenstein mod, though, but luckily I have found a local technician that is specialized in reballing that offers that service at a reasonable price.

So, my question is: should I ask him to also change the NEC Tokins as well?
I'd prefer to do every step that would fix the console and hopefully guarantee a long life in a single operation. I'm not sure about the Tokins and you have way more experience than me so I'd like to hear your thoughts.

Thanks again.

 

[OneFix]

CECHC console late YLOD. Syscon shows full list of 1701 error codes. However, SB uart shows lv2(2) rsx driver assert failed: device/fb.cc : 41.

Is this faulty RSX or could this be broken bga bumps under CELL as well?

 

[vyktormvmpay25]

Can be just a vrams issues with rsx or bump gate but as long as not many people can recover from ram bleed I'll say just swap rsx. Just for reference I can say over 2 ohms vddc rsx worth ram exchange and not high then 3.2 if we speak about 90nm and 40nm, for 65nm idk yet limits. For those struggling to get good working rsx they should build a rsx tester.
https://s.go.ro/8lcdk9cq

 

[1ev01]

Hi all

New to this legendary forum thread. I purchased a new CECHG02 Fat PS3 in 2008. It eventually threw the YLOD error in early 2014. The YLOD timing is always almost instant after switching on the console - there is hardly any delay. Recently I ran the syscon diagnostic and retrieved the results below.

After doing some research, my interpretation of the below 1002 and 3004 errors are that they're RTX power related, with 1002 being the less severe and 3004 being more severe (as you can see from my errorlog below, my console was throwing 1002 errors which eventually transitioned to 3004, which is consistent with the explanation provided on the psdevwiki syscon error codes page.

My end goal is to somehow retrieve the save file data on the console - 1000's of hours on Metal Gear Solid IV and GT5 and 6 which I don't want to repeat! So the console doesn't have to last too long - just long enough for me to extract the save file data to then use on another PS3.

Is my best bet to replace the NEC/Token caps and if so, which ones? I've read conflicting advice on cap replacement ranging from merely replacing the RTX side caps to replacing all NEC/Token caps on the mobo.

Any advice would be greatly appreciated.


01. becount:

Bringup : 1789 times
Shutdown: 1160 times
Power-on: 98day 14hour 13min 20sec
[mullion]$

02. bringup:

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004

03. errorlog:

errlog
ofst[ 56]:err_code:0xffffffff, clock:0x1a92c9bd  2014/02/16 00:58:37
ofst[ 60]:err_code:0xa0801701, clock:0x1a92c9c8  2014/02/16 00:58:48
ofst[ 64]:err_code:0xa0801001, clock:0x1a92c9c8  2014/02/16 00:58:48
ofst[ 68]:err_code:0xa0801002, clock:0x1a9315e1  2014/02/16 06:23:29
ofst[ 72]:err_code:0xa0801002, clock:0x1a9315ea  2014/02/16 06:23:38
ofst[ 76]:err_code:0xa0801002, clock:0x1a9315fa  2014/02/16 06:23:54
ofst[ 80]:err_code:0xa0801002, clock:0x1a931607  2014/02/16 06:24:07
ofst[ 84]:err_code:0xa0801002, clock:0x1a931a09  2014/02/16 06:41:13
ofst[ 88]:err_code:0xa0801002, clock:0x1a931a14  2014/02/16 06:41:24
ofst[ 92]:err_code:0xa0801002, clock:0x1b343828  2014/06/18 11:44:40
ofst[ 96]:err_code:0xa0801002, clock:0x1b343832  2014/06/18 11:44:50
ofst[100]:err_code:0xa0081002, clock:0x26f59475  2020/09/17 03:28:53
ofst[104]:err_code:0xa0801002, clock:0x26f59482  2020/09/17 03:29:06
ofst[108]:err_code:0xa0081002, clock:0x270046eb  2020/09/25 06:12:59
ofst[112]:err_code:0xa0093004, clock:0x2e4e4601  2024/08/13 16:27:45
ofst[116]:err_code:0xa0093004, clock:0x2e4e460a  2024/08/13 16:27:54
ofst[120]:err_code:0xa0093004, clock:0x2e4e4615  2024/08/13 16:28:05
ofst[124]:err_code:0xa0093004, clock:0x2e4e461f  2024/08/13 16:28:15
ofst[  0]:err_code:0xa0093004, clock:0x2e4e4627  2024/08/13 16:28:23
ofst[  4]:err_code:0xa0093004, clock:0x2e4e47c8  2024/08/13 16:35:20
ofst[  8]:err_code:0xa0093004, clock:0x2e4e47d2  2024/08/13 16:35:30
ofst[ 12]:err_code:0xa0093004, clock:0x2e4e47d8  2024/08/13 16:35:36
ofst[ 16]:err_code:0xa0093004, clock:0x2e4e47db  2024/08/13 16:35:39
ofst[ 20]:err_code:0xa0093004, clock:0x2e4e5040  2024/08/13 17:11:28
ofst[ 24]:err_code:0xa0093004, clock:0x2e4eea6b  2024/08/14 04:09:15
ofst[ 28]:err_code:0xa0093004, clock:0x2e552358  2024/08/18 21:25:44
ofst[ 32]:err_code:0xa0093004, clock:0x2e55235d  2024/08/18 21:25:49
ofst[ 36]:err_code:0xa0093004, clock:0x2e55d2fe  2024/08/19 09:55:10
ofst[ 40]:err_code:0xa0093004, clock:0x2e55d340  2024/08/19 09:56:16
ofst[ 44]:err_code:0xa0093004, clock:0x2e55d3a3  2024/08/19 09:57:55
ofst[ 48]:err_code:0xa0093004, clock:0x2e55d3b5  2024/08/19 09:58:13
ofst[ 52]:err_code:0xa0093004, clock:0x2e55d4b6  2024/08/19 10:02:30
[mullion]$

 

[Joel_]

Hi all

New to this legendary forum thread. I purchased a new CECHG02 Fat PS3 in 2008. It eventually threw the YLOD error in early 2014. The YLOD timing is always almost instant after switching on the console - there is hardly any delay. Recently I ran the syscon diagnostic and retrieved the results below.

After doing some research, my interpretation of the below 1002 and 3004 errors are that they're RTX power related, with 1002 being the less severe and 3004 being more severe (as you can see from my errorlog below, my console was throwing 1002 errors which eventually transitioned to 3004, which is consistent with the explanation provided on the psdevwiki syscon error codes page.

My end goal is to somehow retrieve the save file data on the console - 1000's of hours on Metal Gear Solid IV and GT5 and 6 which I don't want to repeat! So the console doesn't have to last too long - just long enough for me to extract the save file data to then use on another PS3.

Is my best bet to replace the NEC/Token caps and if so, which ones? I've read conflicting advice on cap replacement ranging from merely replacing the RTX side caps to replacing all NEC/Token caps on the mobo.

Any advice would be greatly appreciated.


01. becount:

Bringup : 1789 times
Shutdown: 1160 times
Power-on: 98day 14hour 13min 20sec
[mullion]$

02. bringup:

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004

03. errorlog:

errlog
ofst[ 56]:err_code:0xffffffff, clock:0x1a92c9bd  2014/02/16 00:58:37
ofst[ 60]:err_code:0xa0801701, clock:0x1a92c9c8  2014/02/16 00:58:48
ofst[ 64]:err_code:0xa0801001, clock:0x1a92c9c8  2014/02/16 00:58:48
ofst[ 68]:err_code:0xa0801002, clock:0x1a9315e1  2014/02/16 06:23:29
ofst[ 72]:err_code:0xa0801002, clock:0x1a9315ea  2014/02/16 06:23:38
ofst[ 76]:err_code:0xa0801002, clock:0x1a9315fa  2014/02/16 06:23:54
ofst[ 80]:err_code:0xa0801002, clock:0x1a931607  2014/02/16 06:24:07
ofst[ 84]:err_code:0xa0801002, clock:0x1a931a09  2014/02/16 06:41:13
ofst[ 88]:err_code:0xa0801002, clock:0x1a931a14  2014/02/16 06:41:24
ofst[ 92]:err_code:0xa0801002, clock:0x1b343828  2014/06/18 11:44:40
ofst[ 96]:err_code:0xa0801002, clock:0x1b343832  2014/06/18 11:44:50
ofst[100]:err_code:0xa0081002, clock:0x26f59475  2020/09/17 03:28:53
ofst[104]:err_code:0xa0801002, clock:0x26f59482  2020/09/17 03:29:06
ofst[108]:err_code:0xa0081002, clock:0x270046eb  2020/09/25 06:12:59
ofst[112]:err_code:0xa0093004, clock:0x2e4e4601  2024/08/13 16:27:45
ofst[116]:err_code:0xa0093004, clock:0x2e4e460a  2024/08/13 16:27:54
ofst[120]:err_code:0xa0093004, clock:0x2e4e4615  2024/08/13 16:28:05
ofst[124]:err_code:0xa0093004, clock:0x2e4e461f  2024/08/13 16:28:15
ofst[  0]:err_code:0xa0093004, clock:0x2e4e4627  2024/08/13 16:28:23
ofst[  4]:err_code:0xa0093004, clock:0x2e4e47c8  2024/08/13 16:35:20
ofst[  8]:err_code:0xa0093004, clock:0x2e4e47d2  2024/08/13 16:35:30
ofst[ 12]:err_code:0xa0093004, clock:0x2e4e47d8  2024/08/13 16:35:36
ofst[ 16]:err_code:0xa0093004, clock:0x2e4e47db  2024/08/13 16:35:39
ofst[ 20]:err_code:0xa0093004, clock:0x2e4e5040  2024/08/13 17:11:28
ofst[ 24]:err_code:0xa0093004, clock:0x2e4eea6b  2024/08/14 04:09:15
ofst[ 28]:err_code:0xa0093004, clock:0x2e552358  2024/08/18 21:25:44
ofst[ 32]:err_code:0xa0093004, clock:0x2e55235d  2024/08/18 21:25:49
ofst[ 36]:err_code:0xa0093004, clock:0x2e55d2fe  2024/08/19 09:55:10
ofst[ 40]:err_code:0xa0093004, clock:0x2e55d340  2024/08/19 09:56:16
ofst[ 44]:err_code:0xa0093004, clock:0x2e55d3a3  2024/08/19 09:57:55
ofst[ 48]:err_code:0xa0093004, clock:0x2e55d3b5  2024/08/19 09:58:13
ofst[ 52]:err_code:0xa0093004, clock:0x2e55d4b6  2024/08/19 10:02:30
[mullion]$

Yes, it will very probably be the NEC Tokin. It's best to use pre-assembled boards which you then just solder onto the mainboard. There are many different capacitors on these boards that are matched to the NEC Tokins in the best possible way. You can find them everywhere. I buy mine on ebay. Just type in Ps3 NEC Tokin on ebay and then the small ready assembled boards will be suggested to you. If you have replaced the NEC tokens, you don't need a new Ps3 as it will run again without any problems because you have fixed the fault.

 

[1ev01]

Yes, it will very probably be the NEC Tokin. It's best to use pre-assembled boards which you then just solder onto the mainboard. There are many different capacitors on these boards that are matched to the NEC Tokins in the best possible way. You can find them everywhere. I buy mine on ebay. Just type in Ps3 NEC Tokin on ebay and then the small ready assembled boards will be suggested to you. If you have replaced the NEC tokens, you don't need a new Ps3 as it will run again without any problems because you have fixed the fault.

Thank you! I will go ahead and replace them and see how we go.

 

[Joel_]

Thank you! I will go ahead and replace them and see how we go.

Good luck. I would first just replace the one on the back of the CELL and then see if it works. If not, read the Syscon again. If they are the same then replace the one next to the CELL. Then the error should be gone.

 

[Ganjo]

Thank you! I will go ahead and replace them and see how we go.

You need to replace the RSX TOKINs not the CELL. Also buy a tantalizer board, it will save you from doing board damage and causing shorts.

Also check the fuses in case the 3004 is from an actual power failure