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

[vyktormvmpay25]

Thanks for the comments @vyktormvmpay25 ! Console does not enter to recovery/safe mode. I have now reballed cell, but no differences. I am using ACHI IR PRO station with elstein's heaters (2400w + 400w). Next I will check corruption of nands.

Yes really good rework, like I said it has to be more software issue not so good there but will see.

 

[STRAWCROW]

Hello I recently bought a A01 off ebay with the seller saying that it was overheating. When I first turned it on it ran for a few minutes then shut off just being on the home screen. When I turned it on next it turned off after a bit, when I turned it back on it YLOD I waited a bit and it turned back on eventually turning back off. I decided to replace the thermal paste as a low risk way of hopefully getting it to run, I also replaced the power unit with a 231 as i heard it was more efficient and I thought maybe the reason that the ps3 was overheating was a z unit power supply ( it had a 226 but I still decided to replace it as i heard 231 was still less hot). When put back together it ran for a while and turned off again. I waited just in case it needed to cool down some and tried turning it on but it YLOD. I decided to open it back up so i could wire it up for syscon. I got the external error logs and the internal error logs but the internal was not letting me do other commands and now when I try to authorize in internal I get: scopen response invalid. ( my 3961 01 is still set to 00) so sorry if more info is needed to help diagnose my system.
Here are the Error Logs:

>$ ERRLOG GET 00
00000000 A0231004 0B4B4980
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0011004 0B48C396
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0801004 0B48C2D4
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0021004 0B48B506
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0051004 0B48A656
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801004 0B48A0DB
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0801004 0B48A073
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801004 0B489F4D
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0031004 0B48981E
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801004 0B489814
Press Ctrl+C to exit
>$ ERRLOG GET 0a
00000000 A0011004 0B48951B
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801004 0B489284
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801004 0B48911F
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801004 0B488FFD
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0041004 0B488F69
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801004 0B488CD8
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801004 0B488CAD
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0011004 0B488C07
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801004 0B488B69
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801004 0B488B5B
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801004 0B4888CA
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801004 0B4887FB
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801004 0B4886A0
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801004 2D1FC236
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801004 2D1FC20E
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801004 2D1FC205
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0081004 2D1FC1F8
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801004 2D1F6029
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801004 2D1F5FF2
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801004 2D1F5FEA
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801004 2D1F5F07
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF 2D13DB27
Press Ctrl+C to exit

ofst[ 52]:err_code:0xffffffff, clock:0x2d1f5f07  2023/12/27 22:17:43

ofst[ 56]:err_code:0xa0801004, clock:0x2d1f5fea  2023/12/27 22:21:30

ofst[ 60]:err_code:0xa0801004, clock:0x2d1f5ff2  2023/12/27 22:21:38

ofst[ 64]:err_code:0xa0801004, clock:0x2d1f6029  2023/12/27 22:22:33

ofst[ 68]:err_code:0xa0081004, clock:0x2d1fc1f8  2023/12/28 05:19:52

ofst[ 72]:err_code:0xa0801004, clock:0x2d1fc205  2023/12/28 05:20:05

ofst[ 76]:err_code:0xa0801004, clock:0x2d1fc20e  2023/12/28 05:20:14

ofst[ 80]:err_code:0xa0801004, clock:0x2d1fc236  2023/12/28 05:20:54

ofst[ 84]:err_code:0xa0801004, clock:0x0b4886a0  2005/12/31 00:00:32

ofst[ 88]:err_code:0xa0801004, clock:0x0b4887fb  2005/12/31 00:06:19

ofst[ 92]:err_code:0xa0801004, clock:0x0b4888ca  2005/12/31 00:09:46

ofst[ 96]:err_code:0xa0801004, clock:0x0b488b5b  2005/12/31 00:20:43

ofst[100]:err_code:0xa0801004, clock:0x0b488b69  2005/12/31 00:20:57

ofst[104]:err_code:0xa0011004, clock:0x0b488c07  2005/12/31 00:23:35

ofst[108]:err_code:0xa0801004, clock:0x0b488cad  2005/12/31 00:26:21

ofst[112]:err_code:0xa0801004, clock:0x0b488cd8  2005/12/31 00:27:04

ofst[116]:err_code:0xa0041004, clock:0x0b488f69  2005/12/31 00:38:01

ofst[120]:err_code:0xa0801004, clock:0x0b488ffd  2005/12/31 00:40:29

ofst[124]:err_code:0xa0801004, clock:0x0b48911f  2005/12/31 00:45:19

ofst[  0]:err_code:0xa0801004, clock:0x0b489284  2005/12/31 00:51:16

ofst[  4]:err_code:0xa0011004, clock:0x0b48951b  2005/12/31 01:02:19

ofst[  8]:err_code:0xa0801004, clock:0x0b489814  2005/12/31 01:15:00

ofst[ 12]:err_code:0xa0031004, clock:0x0b48981e  2005/12/31 01:15:10

ofst[ 16]:err_code:0xa0801004, clock:0x0b489f4d  2005/12/31 01:45:49

ofst[ 20]:err_code:0xa0801004, clock:0x0b48a073  2005/12/31 01:50:43

ofst[ 24]:err_code:0xa0801004, clock:0x0b48a0db  2005/12/31 01:52:27

ofst[ 28]:err_code:0xa0051004, clock:0x0b48a656  2005/12/31 02:15:50

ofst[ 32]:err_code:0xa0021004, clock:0x0b48b506  2005/12/31 03:18:30

ofst[ 36]:err_code:0xa0801004, clock:0x0b48c2d4  2005/12/31 04:17:24

ofst[ 40]:err_code:0xa0011004, clock:0x0b48c396  2005/12/31 04:20:38

ofst[ 44]:err_code:0xa0231004, clock:0x0b4b4980  2006/01/02 02:16:32

ofst[ 48]:err_code:0xa0021004, clock:0x0b4bac34  2006/01/02 09:17:40

 

[superprokill1]

ey! I bought a broken, YLOD launch model CECHE11. I was able to get internal mode working. Here is my errlog:

[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
errlog
ofst[ 72]:err_code:0xffffffff, clock:0x0b499c13  2005/12/31 19:44:19
ofst[ 76]:err_code:0xa0801002, clock:0x0b499c5a  2005/12/31 19:45:30
ofst[ 80]:err_code:0xa0801002, clock:0x0b499c72  2005/12/31 19:45:54
ofst[ 84]:err_code:0xa0801002, clock:0x0b499c8a  2005/12/31 19:46:18
ofst[ 88]:err_code:0xa0801002, clock:0x0b499c9a  2005/12/31 19:46:34
ofst[ 92]:err_code:0xa0801002, clock:0x0b499ca2  2005/12/31 19:46:42
ofst[ 96]:err_code:0xa0801002, clock:0x0b499cbb  2005/12/31 19:47:07
ofst[100]:err_code:0xa0801002, clock:0x0b499cc2  2005/12/31 19:47:14
ofst[104]:err_code:0xa0801002, clock:0x0b499cd3  2005/12/31 19:47:31
ofst[108]:err_code:0xa0801002, clock:0x0b499cf6  2005/12/31 19:48:06
ofst[112]:err_code:0xa0801002, clock:0x0b499d1f  2005/12/31 19:48:47
ofst[116]:err_code:0xa0801002, clock:0x0b499d46  2005/12/31 19:49:26
ofst[120]:err_code:0xa0801002, clock:0x0b499e6d  2005/12/31 19:54:21
ofst[124]:err_code:0xa0801002, clock:0x0b499e84  2005/12/31 19:54:44
ofst[  0]:err_code:0xa0101002, clock:0x1495c706  2010/12/11 05:22:14
ofst[  4]:err_code:0xa0101002, clock:0x1495c798  2010/12/11 05:24:40
ofst[  8]:err_code:0xa0801002, clock:0x1495c79f  2010/12/11 05:24:47
ofst[ 12]:err_code:0xa0101002, clock:0x1495c7a2  2010/12/11 05:24:50
ofst[ 16]:err_code:0xa0101002, clock:0x1495c7a9  2010/12/11 05:24:57
ofst[ 20]:err_code:0xa0801002, clock:0x159fe621  2011/07/01 01:57:53
ofst[ 24]:err_code:0xa0101002, clock:0x15a0090f  2011/07/01 04:26:55
ofst[ 28]:err_code:0xa0101002, clock:0x15a00916  2011/07/01 04:27:02
ofst[ 32]:err_code:0xa0801002, clock:0x15a0093b  2011/07/01 04:27:39
ofst[ 36]:err_code:0xa0801002, clock:0x15a00960  2011/07/01 04:28:16
ofst[ 40]:err_code:0xa0101002, clock:0x15a0096c  2011/07/01 04:28:28
ofst[ 44]:err_code:0xa0101002, clock:0xffffffff
ofst[ 48]:err_code:0xa0101002, clock:0xffffffff
ofst[ 52]:err_code:0xa0101002, clock:0xffffffff
ofst[ 56]:err_code:0xa0101002, clock:0xffffffff
ofst[ 60]:err_code:0xa0101002, clock:0xffffffff
ofst[ 64]:err_code:0xa0101002, clock:0xffffffff
ofst[ 68]:err_code:0xa0101002, clock:0xffffffff

Here's a couple of them that also didn't get added to the mix because I ran the command a bit too many times:

ofst[ 44]:err_code:0xffffffff, clock:0x0b499bc6  2005/12/31 19:43:02ofst[ 48]:err_code:0xa0801002, clock:0x0b499bcf  2005/12/31 19:43:11
ofst[ 52]:err_code:0xa0801002, clock:0x0b499bd9  2005/12/31 19:43:21ofst[ 56]:err_code:0xa0801002, clock:0x0b499bee  2005/12/31 19:43:42
ofst[ 60]:err_code:0xa0801002, clock:0x0b499bf7  2005/12/31 19:43:51ofst[ 64]:err_code:0xa0801002, clock:0x0b499c02  2005/12/31 19:44:02

Here is the output of bringup:

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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101002
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000

I will read the syscon error codes wiki page and look for more information, but it would definitely be a bonus if actually skilled people could help me with this. Thank you so much dear reader!

 

[superprokill1]

ey! I bought a broken, YLOD launch model CECHE11. I was able to get internal mode working. Here is my errlog:

[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
errlog
ofst[ 72]:err_code:0xffffffff, clock:0x0b499c13  2005/12/31 19:44:19
ofst[ 76]:err_code:0xa0801002, clock:0x0b499c5a  2005/12/31 19:45:30
ofst[ 80]:err_code:0xa0801002, clock:0x0b499c72  2005/12/31 19:45:54
ofst[ 84]:err_code:0xa0801002, clock:0x0b499c8a  2005/12/31 19:46:18
ofst[ 88]:err_code:0xa0801002, clock:0x0b499c9a  2005/12/31 19:46:34
ofst[ 92]:err_code:0xa0801002, clock:0x0b499ca2  2005/12/31 19:46:42
ofst[ 96]:err_code:0xa0801002, clock:0x0b499cbb  2005/12/31 19:47:07
ofst[100]:err_code:0xa0801002, clock:0x0b499cc2  2005/12/31 19:47:14
ofst[104]:err_code:0xa0801002, clock:0x0b499cd3  2005/12/31 19:47:31
ofst[108]:err_code:0xa0801002, clock:0x0b499cf6  2005/12/31 19:48:06
ofst[112]:err_code:0xa0801002, clock:0x0b499d1f  2005/12/31 19:48:47
ofst[116]:err_code:0xa0801002, clock:0x0b499d46  2005/12/31 19:49:26
ofst[120]:err_code:0xa0801002, clock:0x0b499e6d  2005/12/31 19:54:21
ofst[124]:err_code:0xa0801002, clock:0x0b499e84  2005/12/31 19:54:44
ofst[  0]:err_code:0xa0101002, clock:0x1495c706  2010/12/11 05:22:14
ofst[  4]:err_code:0xa0101002, clock:0x1495c798  2010/12/11 05:24:40
ofst[  8]:err_code:0xa0801002, clock:0x1495c79f  2010/12/11 05:24:47
ofst[ 12]:err_code:0xa0101002, clock:0x1495c7a2  2010/12/11 05:24:50
ofst[ 16]:err_code:0xa0101002, clock:0x1495c7a9  2010/12/11 05:24:57
ofst[ 20]:err_code:0xa0801002, clock:0x159fe621  2011/07/01 01:57:53
ofst[ 24]:err_code:0xa0101002, clock:0x15a0090f  2011/07/01 04:26:55
ofst[ 28]:err_code:0xa0101002, clock:0x15a00916  2011/07/01 04:27:02
ofst[ 32]:err_code:0xa0801002, clock:0x15a0093b  2011/07/01 04:27:39
ofst[ 36]:err_code:0xa0801002, clock:0x15a00960  2011/07/01 04:28:16
ofst[ 40]:err_code:0xa0101002, clock:0x15a0096c  2011/07/01 04:28:28
ofst[ 44]:err_code:0xa0101002, clock:0xffffffff
ofst[ 48]:err_code:0xa0101002, clock:0xffffffff
ofst[ 52]:err_code:0xa0101002, clock:0xffffffff
ofst[ 56]:err_code:0xa0101002, clock:0xffffffff
ofst[ 60]:err_code:0xa0101002, clock:0xffffffff
ofst[ 64]:err_code:0xa0101002, clock:0xffffffff
ofst[ 68]:err_code:0xa0101002, clock:0xffffffff

Here's a couple of them that also didn't get added to the mix because I ran the command a bit too many times:

ofst[ 44]:err_code:0xffffffff, clock:0x0b499bc6  2005/12/31 19:43:02ofst[ 48]:err_code:0xa0801002, clock:0x0b499bcf  2005/12/31 19:43:11
ofst[ 52]:err_code:0xa0801002, clock:0x0b499bd9  2005/12/31 19:43:21ofst[ 56]:err_code:0xa0801002, clock:0x0b499bee  2005/12/31 19:43:42
ofst[ 60]:err_code:0xa0801002, clock:0x0b499bf7  2005/12/31 19:43:51ofst[ 64]:err_code:0xa0801002, clock:0x0b499c02  2005/12/31 19:44:02

Here is the output of bringup:

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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101002
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000

I will read the syscon error codes wiki page and look for more information, but it would definitely be a bonus if actually skilled people could help me with this. Thank you so much dear reader!

alright I forgot to make a follow up to my original comment, excuse me. From what I could gather online, I think I might be lucky enough to just have a faulty RSX NEC/TOKIN capacitor, judging from the 1002 error code. What would be my best approach at replacing it? RIP-Felix's Tantalizer mod? Thanks.

 

[N3Star]

Hello, I need help in figuring out what's wrong with my COK-002 frankenstein. The history is: I got only a motherboard with what seems to be moisture residue. I began by soaking the motherboard in IPA and cleaning the worst parts of damage, though it definitely looked better than it seemed - nothing was shorted, nothing was not making contact.
At first syscon indicated 3004 - so I replaced 2 NECs with 12x470uF tantalum caps with ESR <0.05Ohm, while leaving 2 other NECs alone. After that I got a GLOD - but the console didn't shut down 1 minute later. It was working for ~5 minutes and after that I got 14FF without any other error code. Never got YLOD on this one.

After this I thought that the RSX died and frankied it - the RSX is CXD5300AGB, I bought with 2 other units, both are working flawlessly as frankies. This RSX had a bit lower resistance at VDDQ at ~300ohms.
Meanwhile I was getting 1001, so again, replaced 2 NEC with same 12x470uF caps, didn't change anything. Still GLOD, still 14FF, but this time after random amount of time, sometimes 5 minutes, sometimes 15 minutes. I was also getting 1103.

Spoiler

CPU isn't delidded, so that's that, but there is one interesting thing - SYSCON always reports weird temperature - it's always 0x0110 for RSX (same on both 90nm and 40nm chips) and 0x002c for CELL, obviously checked while console is on. I don't think that the overheating protection is handled by SYSCON, but it seems to work - leaving CELL and RSX without heatsinks quickly ends in emergency shutdown.

SB UART says that everything seems to be fine.

Spoiler

Hdmi chstat command returns "WaitResolution", so likely either RSX is bad or something prevents it from working.

Spoiler

Any help would be greatly appreciated.

EDIT:
I tried changing the EC to EB and that changed nothing.
Also, the console started throwing 14FF error almost immediately. There also was one x 1601 and two 1701, as well as two 3013. This thing is giving me mixed signals, but for now I think I'll start with replacing the RSX with 65nm one to see what happens.

 

[Incursio]

Hello I got CECHG with YLOD <1 second.
This is the error log and bringup

$ bringup
bringup
[SSM] state 0000 - 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode  syspm_stat=0000000000000000
[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_Half0x20e7
Press Ctrl+C to exit
$
[SSM] state 0104 - 0204
[SSM] state 0204 - 0105
[SSM] state 0105 - 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.9.0 (Build ID 2398,24722, Build Data 2007-07-22_155529)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR] 0xb0000004 lv0 authentication fail
[SERV NVS] WRITE CMD
[SERV NVS] WRITE CMD
[SSM]  FATAL ERROR requested by OS
[SSM] state 0400 - 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode  syspm_stat=0000000000000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state 0700 - 0600
(PowerOff State) (Fatal)

[mullion]$
Press Ctrl+C to exit
$ shutdown
shutdown
[SSM] state 0600 - 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
$ errlog
errlog
ofst[  4]err_code0xffffffff, clock0x20b725e2  20170523 165458
ofst[  8]err_code0xa08014ff, clock0x20b725e2  20170523 165458
ofst[ 12]err_code0xa0801001, clock0x20b725e2  20170523 165458
ofst[ 16]err_code0xa08014ff, clock0x20b725f9  20170523 165521
ofst[ 20]err_code0xa0801001, clock0x20b725f9  20170523 165521
ofst[ 24]err_code0xa0801001, clock0x20b72618  20170523 165552
ofst[ 28]err_code0xa08014ff, clock0x20b72634  20170523 165620
ofst[ 32]err_code0xa0801001, clock0x20b72634  20170523 165620
ofst[ 36]err_code0xa08014ff, clock0x20b726b7  20170523 165831
ofst[ 40]err_code0xa0801001, clock0x20b726b7  20170523 165831
ofst[ 44]err_code0xa0801701, clock0x20b726df  20170523 165911
ofst[ 48]err_code0xa08014ff, clock0x20b726df  20170523 165911
ofst[ 52]err_code0xa0801001, clock0x20b726df  20170523 165911
ofst[ 56]err_code0xa0801701, clock0x2219914f  20180216 125543
ofst[ 60]err_code0xa08014ff, clock0x2219914f  20180216 125543
ofst[ 64]err_code0xa0801001, clock0x2219914f  20180216 125543
ofst[ 68]err_code0xa0801701, clock0x22355d87  20180309 145815
ofst[ 72]err_code0xa08014ff, clock0x22355d87  20180309 145815
ofst[ 76]err_code0xa0801001, clock0x22355d87  20180309 145815
ofst[ 80]err_code0xa0801701, clock0x22674d7b  20180416 120307
ofst[ 84]err_code0xa0801001, clock0x22674d7b  20180416 120307
ofst[ 88]err_code0xa08014ff, clock0x22676f73  20180416 142803
ofst[ 92]err_code0xa0801001, clock0x22676f73  20180416 142803
ofst[ 96]err_code0xa08014ff, clock0x226773ea  20180416 144706
ofst[100]err_code0xa0801001, clock0x226773ea  20180416 144706
ofst[104]err_code0xa08014ff, clock0x22679a65  20180416 173117
ofst[108]err_code0xa0801001, clock0x22679a65  20180416 173117
ofst[112]err_code0xa0801701, clock0x226f7ecb  20180422 171139
ofst[116]err_code0xa08014ff, clock0x226f7ecb  20180422 171139
ofst[120]err_code0xa0801001, clock0x226f7ecb  20180422 171139
ofst[124]err_code0xa0801701, clock0x226f9ff9  20180422 193313
ofst[  0]err_code0xa0801001, clock0x226f9ff9  20180422 193313

 

[MasterYuri95]

Hello! so I modified the default syscon fan value on my A01 following Paco's tutorial here in the forum. I am having problems with the 34fe address line refusing to change no matter how many times I've written it. It should be 0x9415 but it still generates this weird value where I have no Idea where it came from. What did I do wrong and what should I change?

eepcsum

Addr:0x000032fe should be 0x52b7

sum:0x1cf9

Addr:0x000034fe should be 0x771c

Addr:0x000039fe should be 0x0f38

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
r 34fe 2

+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F

-----------------------------------------------

15 94

[mullion]$
r 3300 200

+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F

-----------------------------------------------

33 40 48 4D 5A 66 73 80 99 FF 00 4A 00 4B 00 4C

00 4D 00 4E 00 4F 00 50 00 51 00 52 00 55 00 00

00 3C 00 3D 00 43 00 44 00 47 80 47 00 48 80 48

00 49 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 47 4D 54 5A 73 80 99 FF 00 30 00 3A 00 40

00 44 00 48 00 4A 00 59 00 4E 00 5B 00 5F 00 00

00 28 00 2E 00 36 00 38 00 3C 80 50 00 46 80 51

00 52 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF 00 3C 00 3D 00 3E

00 3F 00 40 00 41 00 42 00 43 00 44 00 47 00 00

00 27 00 30 00 36 00 37 80 3A 00 3B 00 3C 80 3C

00 3D 33 FF 01 00 FF FF FF FF FF FF FF FF FF FF

33 40 48 4D 5A 66 73 80 99 FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF 00 4D 14 FF FF FF FF FF FF FF 00 FF 00 FF

54 00 55 00 02 00 5E 00 5F 00 02 00 FF FF FF FF

02 00 46 00 47 00 02 00 FF FF FF FF 02 00 FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF FF FF FF 15 94



[mullion]$
fantbl setini 1 p0 00.00 48.00 0x33
fantbl setini 1 p1 40.00 58.00 0x40
fantbl setini 1 p2 46.00 64.00 0x47
fantbl setini 1 p3 54.00 68.00 0x4d
fantbl setini 1 p4 56.00 72.00 0x54
fantbl setini 1 p5 60.00 74.00 0x5a
fantbl setini 1 p6 66.00 76.00 0x66
fantbl setini 1 p7 70.00 78.00 0x80
fantbl setini 1 p8 72.00 80.00 0x99
fantbl setini 1 p9 73.00 85.00 0xff
tshutdown setini 1 85
fantbl setini 0 p0 00.00 58.00 0x33
fantbl setini 0 p1 48.00 68.00 0x40
fantbl setini 0 p2 60.00 72.00 0x47
fantbl setini 0 p3 66.00 76.00 0x4d
fantbl setini 0 p4 67.00 77.00 0x54
fantbl setini 0 p5 68.00 78.00 0x5a
fantbl setini 0 p6 70.00 80.00 0x66[mullion]$


fantbl setini 1 p0 00.00 48.00 0x33

fancon No:01

P0: TempD:0.0(0x0000) - TempU:48.0(0x3000) duty:20%(0x33)

[mullion]$
fantbl getini 1

fancon No:01

P0: TempD:0.0(0x0000) - TempU:48.0(0x3000) duty:20%(0x33)

P1: TempD:40.0(0x2800) - TempU:58.0(0x3a00) duty:25%(0x40)

P2: TempD:46.0(0x2e00) - TempU:64.0(0x4000) duty:27%(0x47)

P3: TempD:54.0(0x3600) - TempU:68.0(0x4400) duty:30%(0x4d)

P4: TempD:56.0(0x3800) - TempU:72.0(0x4800) duty:32%(0x54)

P5: TempD:60.0(0x3c00) - TempU:74.0(0x4a00) duty:35%(0x5a)

P6: TempD:80.50(0x5080) - TempU:89.0(0x5900) duty:45%(0x73)

P7: TempD:70.0(0x4600) - TempU:78.0(0x4e00) duty:50%(0x80)

P8: TempD:81.50(0x5180) - TempU:91.0(0x5b00) duty:60%(0x99)

P9: TempD:82.0(0x5200) - TempU:95.0(0x5f00) duty:100%(0xff)

[mullion]$
fantbl setini 1 p6 66.00 76.00 0x66

fancon No:01

P6: TempD:66.0(0x4200) - TempU:76.0(0x4c00) duty:40%(0x66)

[mullion]$
fantbl getini 1

fancon No:01

P0: TempD:0.0(0x0000) - TempU:48.0(0x3000) duty:20%(0x33)

P1: TempD:40.0(0x2800) - TempU:58.0(0x3a00) duty:25%(0x40)

P2: TempD:46.0(0x2e00) - TempU:64.0(0x4000) duty:27%(0x47)

P3: TempD:54.0(0x3600) - TempU:68.0(0x4400) duty:30%(0x4d)

P4: TempD:56.0(0x3800) - TempU:72.0(0x4800) duty:32%(0x54)

P5: TempD:60.0(0x3c00) - TempU:74.0(0x4a00) duty:35%(0x5a)

P6: TempD:66.0(0x4200) - TempU:76.0(0x4c00) duty:40%(0x66)

P7: TempD:70.0(0x4600) - TempU:78.0(0x4e00) duty:50%(0x80)

P8: TempD:81.50(0x5180) - TempU:91.0(0x5b00) duty:60%(0x99)

P9: TempD:82.0(0x5200) - TempU:95.0(0x5f00) duty:100%(0xff)

[mullion]$
fantbl setini 1 p8 72.00 80.00 0x99

fancon No:01

P8: TempD:72.0(0x4800) - TempU:80.0(0x5000) duty:60%(0x99)

[mullion]$
fantbl setini 1 p9 73.00 85.00 0xff

fancon No:01

P9: TempD:73.0(0x4900) - TempU:85.0(0x5500) duty:100%(0xff)

[mullion]$
fantbl getini 1

fancon No:01

P0: TempD:0.0(0x0000) - TempU:48.0(0x3000) duty:20%(0x33)

P1: TempD:40.0(0x2800) - TempU:58.0(0x3a00) duty:25%(0x40)

P2: TempD:46.0(0x2e00) - TempU:64.0(0x4000) duty:27%(0x47)

P3: TempD:54.0(0x3600) - TempU:68.0(0x4400) duty:30%(0x4d)

P4: TempD:56.0(0x3800) - TempU:72.0(0x4800) duty:32%(0x54)

P5: TempD:60.0(0x3c00) - TempU:74.0(0x4a00) duty:35%(0x5a)

P6: TempD:66.0(0x4200) - TempU:76.0(0x4c00) duty:40%(0x66)

P7: TempD:70.0(0x4600) - TempU:78.0(0x4e00) duty:50%(0x80)

P8: TempD:72.0(0x4800) - TempU:80.0(0x5000) duty:60%(0x99)

P9: TempD:73.0(0x4900) - TempU:85.0(0x5500) duty:100%(0xff)

[mullion]$
fantbl getini 0

fancon No:00

P0: TempD:0.0(0x0000) - TempU:74.0(0x4a00) duty:20%(0x33)

P1: TempD:60.0(0x3c00) - TempU:75.0(0x4b00) duty:25%(0x40)

P2: TempD:61.0(0x3d00) - TempU:76.0(0x4c00) duty:28%(0x48)

P3: TempD:67.0(0x4300) - TempU:77.0(0x4d00) duty:30%(0x4d)

P4: TempD:68.0(0x4400) - TempU:78.0(0x4e00) duty:35%(0x5a)

P5: TempD:71.0(0x4700) - TempU:79.0(0x4f00) duty:40%(0x66)

P6: TempD:71.50(0x4780) - TempU:80.0(0x5000) duty:45%(0x73)

P7: TempD:72.0(0x4800) - TempU:81.0(0x5100) duty:50%(0x80)

P8: TempD:72.50(0x4880) - TempU:82.0(0x5200) duty:60%(0x99)

P9: TempD:73.0(0x4900) - TempU:85.0(0x5500) duty:100%(0xff)

[mullion]$
fantbl setini 0 p0 00.00 58.00 0x33

fancon No:00

P0: TempD:0.0(0x0000) - TempU:58.0(0x3a00) duty:20%(0x33)

[mullion]$
fantbl getini 0

fancon No:00

P0: TempD:0.0(0x0000) - TempU:58.0(0x3a00) duty:20%(0x33)

P1: TempD:60.0(0x3c00) - TempU:75.0(0x4b00) duty:25%(0x40)

P2: TempD:61.0(0x3d00) - TempU:76.0(0x4c00) duty:28%(0x48)

P3: TempD:67.0(0x4300) - TempU:77.0(0x4d00) duty:30%(0x4d)

P4: TempD:68.0(0x4400) - TempU:78.0(0x4e00) duty:35%(0x5a)

P5: TempD:71.0(0x4700) - TempU:79.0(0x4f00) duty:40%(0x66)

P6: TempD:71.50(0x4780) - TempU:80.0(0x5000) duty:45%(0x73)

P7: TempD:72.0(0x4800) - TempU:81.0(0x5100) duty:50%(0x80)

P8: TempD:72.50(0x4880) - TempU:82.0(0x5200) duty:60%(0x99)

P9: TempD:73.0(0x4900) - TempU:85.0(0x5500) duty:100%(0xff)

[mullion]$
fantbl setini 0 p1 48.00 68.00 0x40

fancon No:00

P1: TempD:48.0(0x3000) - TempU:68.0(0x4400) duty:25%(0x40)

[mullion]$
fantbl setini 0 p2 60.00 72.00 0x47

fancon No:00

P2: TempD:60.0(0x3c00) - TempU:72.0(0x4800) duty:27%(0x47)

[mullion]$
fantbl setini 0 p3 66.00 76.00 0x4d

fancon No:00

P3: TempD:66.0(0x4200) - TempU:76.0(0x4c00) duty:30%(0x4d)

[mullion]$
fantbl setini 0 p4 67.00 77.00 0x54

fancon No:00

P4: TempD:67.0(0x4300) - TempU:77.0(0x4d00) duty:32%(0x54)

[mullion]$
fantbl setini 0 p5 68.00 78.00 0x5a

fancon No:00

P5: TempD:68.0(0x4400) - TempU:78.0(0x4e00) duty:35%(0x5a)

[mullion]$
fantbl setini 0 p6 70.00 80.00 0x66

fancon No:00

P6: TempD:70.0(0x4600) - TempU:80.0(0x5000) duty:40%(0x66)

[mullion]$
fantbl getini 0

fancon No:00

P0: TempD:0.0(0x0000) - TempU:58.0(0x3a00) duty:20%(0x33)

P1: TempD:48.0(0x3000) - TempU:68.0(0x4400) duty:25%(0x40)

P2: TempD:60.0(0x3c00) - TempU:72.0(0x4800) duty:27%(0x47)

P3: TempD:66.0(0x4200) - TempU:76.0(0x4c00) duty:30%(0x4d)

P4: TempD:67.0(0x4300) - TempU:77.0(0x4d00) duty:32%(0x54)

P5: TempD:68.0(0x4400) - TempU:78.0(0x4e00) duty:35%(0x5a)

P6: TempD:70.0(0x4600) - TempU:80.0(0x5000) duty:40%(0x66)

P7: TempD:72.0(0x4800) - TempU:81.0(0x5100) duty:50%(0x80)

P8: TempD:72.50(0x4880) - TempU:82.0(0x5200) duty:60%(0x99)

P9: TempD:73.0(0x4900) - TempU:85.0(0x5500) duty:100%(0xff)

[mullion]$
r 34fe 2

+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F

-----------------------------------------------

15 94

[mullion]$
eepcsum

Addr:0x000032fe should be 0x52b7

sum:0x9c58

Addr:0x000034fe should be 0xfffff7bd

Addr:0x000039fe should be 0x0f38

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
w 34fe 15 94

w complete!

[mullion]$
eepcsum

Addr:0x000032fe should be 0x52b7

sum:0x9c58

Addr:0x000034fe should be 0xfffff7bd

Addr:0x000039fe should be 0x0f38

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff

 

[superprokill1]

@RIP-Felix hallo o/
I'm tempted to try out your Tantalizer mod on a dead CECHE I bought that seems to have 1002 errors (a bit more info some comments above). Thing is, after a quick trip downtown where all the electronics shops are in my city (I live in Argentina), I came to the conclusion that there aren't any caps that get nowhere as close as the ones needed to replace the tokins as a definitive solution, and it also seems like there isn't any PCB makers around here. PCBWay and eBay can ship to here, but the final price tag is absolutely ludicrous. AliExpress too, but I don't have an oscilloscope near me to test them (that is, if I even get through the 3-4 months delivery time without forgetting it exists at all)
I have a family member living in the US that is willing to help me out and purchase + mail me both the PCBs and the caps, but they want me to first try and temporarily solder a cap in parallel that is good enough to just make the console boot and reassure that the problem is the tokins and that there isn't something else that could be causing issues. If my only intention is to boot in the XMB and nothing else (not open any games or anything that would make the RSX skyrocket in power consumption), what capacitance value would I be targeting or what types of caps would I be looking for?
Thank you, and by the way, I absolutely loved your videos covering the YLoD/RRoD/Frankie, I came looking on how to potentially fix this console and I ended up spending the entire afternoon enjoying Star Wars memes AND learning about historical big oopsies by big corps :^)

 

[xxxmarioxxx]

3034 error caused by bad HDMI connector?

So I bought a broken ps3 from facebook marketplace the other day, the seller says it has ylod. When I turn it on it does have ylod, but it's a delayed one and I can see the hdd indicator flashing before power cuts out. I tried to power it on a few more times, sometimes it lasts longer (about 10 seconds), some lines flash on the screen and I can hear the boot sound. The console isn't stored properly as I can see some oxidation marks on chrome edges, so I used some deoxit to clean the hdmi connector to fix the display issue first. And to my surprise the console actually boots up and it's on firmware 3.50. I tried a few disc games and the ps3 plays them just fine. After installing latest 4.90 cfw i got a dump of syscon error log, and I can see a lot of 3034 errors:

Error Log
01: A0901001 Sun Jan 1 09:00:31 2006
02: A0801002 Sun Jan 1 09:00:07 2006
03: A0403034 Sat Jan 1 08:59:59 2000
04: A0403034 Sun Dec 26 14:19:53 2010
05: A0403034 Sun Dec 26 14:19:43 2010
06: A0403034 Sun Dec 26 14:19:40 2010
07: A0403034 Sun Dec 26 14:19:33 2010
08: A0403034 Sun Dec 26 14:19:27 2010
09: A0403034 Sun Dec 26 14:19:21 2010
10: A0403034 Sun Dec 26 13:13:48 2010
11: A0403034 Sun Dec 26 13:13:38 2010
12: A0403034 Sun Dec 26 13:13:31 2010
13: A0403034 Sun Dec 26 13:13:26 2010
14: A0403034 Sun Dec 26 13:13:19 2010
15: A0801601 Sun Dec 26 13:12:54 2010
16: A0801701 Sun Dec 26 13:12:54 2010
17: A0403034 Sun Dec 26 13:11:21 2010
18: A0403034 Sun Dec 26 12:30:32 2010
19: A0403034 Sun Dec 26 12:30:28 2010
20: A0403034 Sun Dec 26 12:30:20 2010
21: A0403034 Sun Dec 26 12:30:02 2010
22: A0403034 Sun Dec 26 12:29:49 2010
23: A0403034 Sun Dec 26 12:29:44 2010
24: A0403034 Sun Dec 26 12:29:40 2010
25: A0403034 Sun Dec 26 12:29:32 2010
26: A0403034 Sun Dec 26 12:29:27 2010
27: A0403034 Sun Dec 26 12:29:12 2010
28: A0403034 Sun Dec 26 12:29:03 2010
29: A0403034 Sun Dec 26 12:28:53 2010
30: A0403034 Sun Dec 26 12:28:44 2010
31: A0403034 Sun Dec 26 12:28:21 2010
32: FFFFFFFF Sun Dec 26 12:28:08 2010

I then tried to trigger the 3034 ylod myself, played the last of us for one hour straight and the console doesn't show ylod. I disabled webman control and used syscon fan curve, RSX/CELL temperature reached about 70C and still no ylod. Knocked on the rsx clip while the game is running, nothing. After removing the motherboard, it seems the rsx was replaced before as it has some flux around it, along with some hand written numbers on motherboard. The warranty seal was intact when I bought it so I supposed sony did the repair themselves. I then let the ps3 sitting in the last of us at an intense scene where fps dips to 25 for 6 hours straight, still no ylod.

I searched psdevwiki and couldn't find any mention of 3034 error caused by bad HDMI connector. Is it possible for bad HDMI connector to cause ylod?

 

[RIP-Felix]

3034 error caused by bad HDMI connector?

So I bought a broken ps3 from facebook marketplace the other day, the seller says it has ylod. When I turn it on it does have ylod, but it's a delayed one and I can see the hdd indicator flashing before power cuts out. I tried to power it on a few more times, sometimes it lasts longer (about 10 seconds), some lines flash on the screen and I can hear the boot sound. The console isn't stored properly as I can see some oxidation marks on chrome edges, so I used some deoxit to clean the hdmi connector to fix the display issue first. And to my surprise the console actually boots up and it's on firmware 3.50. I tried a few disc games and the ps3 plays them just fine. After installing latest 4.90 cfw i got a dump of syscon error log, and I can see a lot of 3034 errors:

Error Log
01: A0901001 Sun Jan 1 09:00:31 2006
02: A0801002 Sun Jan 1 09:00:07 2006
03: A0403034 Sat Jan 1 08:59:59 2000
04: A0403034 Sun Dec 26 14:19:53 2010
05: A0403034 Sun Dec 26 14:19:43 2010
06: A0403034 Sun Dec 26 14:19:40 2010
07: A0403034 Sun Dec 26 14:19:33 2010
08: A0403034 Sun Dec 26 14:19:27 2010
09: A0403034 Sun Dec 26 14:19:21 2010
10: A0403034 Sun Dec 26 13:13:48 2010
11: A0403034 Sun Dec 26 13:13:38 2010
12: A0403034 Sun Dec 26 13:13:31 2010
13: A0403034 Sun Dec 26 13:13:26 2010
14: A0403034 Sun Dec 26 13:13:19 2010
15: A0801601 Sun Dec 26 13:12:54 2010
16: A0801701 Sun Dec 26 13:12:54 2010
17: A0403034 Sun Dec 26 13:11:21 2010
18: A0403034 Sun Dec 26 12:30:32 2010
19: A0403034 Sun Dec 26 12:30:28 2010
20: A0403034 Sun Dec 26 12:30:20 2010
21: A0403034 Sun Dec 26 12:30:02 2010
22: A0403034 Sun Dec 26 12:29:49 2010
23: A0403034 Sun Dec 26 12:29:44 2010
24: A0403034 Sun Dec 26 12:29:40 2010
25: A0403034 Sun Dec 26 12:29:32 2010
26: A0403034 Sun Dec 26 12:29:27 2010
27: A0403034 Sun Dec 26 12:29:12 2010
28: A0403034 Sun Dec 26 12:29:03 2010
29: A0403034 Sun Dec 26 12:28:53 2010
30: A0403034 Sun Dec 26 12:28:44 2010
31: A0403034 Sun Dec 26 12:28:21 2010
32: FFFFFFFF Sun Dec 26 12:28:08 2010

I then tried to trigger the 3034 ylod myself, played the last of us for one hour straight and the console doesn't show ylod. I disabled webman control and used syscon fan curve, RSX/CELL temperature reached about 70C and still no ylod. Knocked on the rsx clip while the game is running, nothing. After removing the motherboard, it seems the rsx was replaced before as it has some flux around it, along with some hand written numbers on motherboard. The warranty seal was intact when I bought it so I supposed sony did the repair themselves. I then let the ps3 sitting in the last of us at an intense scene where fps dips to 25 for 6 hours straight, still no ylod.

I searched psdevwiki and couldn't find any mention of 3034 error caused by bad HDMI connector. Is it possible for bad HDMI connector to cause ylod?

BAsed on the timestamps, the console had 3034 (bad GPU presumably) in 2010 and was repaired. It lasted until experiencing a 1002 (RSX VRM filtering, presumably tokins). the 901001 can occur from failing tokins too, but many other causes. I do not believe the 3034's are connected with the event's you described. Perhaps the 1001 was and a dodgy connection causing it wouldn't suprise me.

 

[RIP-Felix]

@RIP-Felix hallo o/
I'm tempted to try out your Tantalizer mod on a dead CECHE I bought that seems to have 1002 errors (a bit more info some comments above). Thing is, after a quick trip downtown where all the electronics shops are in my city (I live in Argentina), I came to the conclusion that there aren't any caps that get nowhere as close as the ones needed to replace the tokins as a definitive solution, and it also seems like there isn't any PCB makers around here. PCBWay and eBay can ship to here, but the final price tag is absolutely ludicrous. AliExpress too, but I don't have an oscilloscope near me to test them (that is, if I even get through the 3-4 months delivery time without forgetting it exists at all)
I have a family member living in the US that is willing to help me out and purchase + mail me both the PCBs and the caps, but they want me to first try and temporarily solder a cap in parallel that is good enough to just make the console boot and reassure that the problem is the tokins and that there isn't something else that could be causing issues. If my only intention is to boot in the XMB and nothing else (not open any games or anything that would make the RSX skyrocket in power consumption), what capacitance value would I be targeting or what types of caps would I be looking for?
Thank you, and by the way, I absolutely loved your videos covering the YLoD/RRoD/Frankie, I came looking on how to potentially fix this console and I ended up spending the entire afternoon enjoying Star Wars memes AND learning about historical big oopsies by big corps :^)

You want low esr caps. Less than 9mOhms. And you need to make sure the'll fit under the RF shield. You can source good polymers caps on most junk electronics. So my advice is to seek out a local electronics repair shop and ask if they have any junk motherboards or graphics cards. You can salvage the polymer caps off their core voltage line, which should have low ESR decoupling capacitors that will work.

New caps would last longer and you can be sure they still met specifications, but in a pinch or hard to ship to location like you say, salvage may be your best bet. BTW, you don't need my tanatlizer board. It's just to make soldering easier, since it has the + bridge built in. But you can still use jumper wires NP. I would recommend replacing all the tokins if you replace any, to remove any effects of impedance mismatches and lesson the chances of antiresonance peaks. You can try a parasite cap to confirm the diagnosis if you want, but 1002 is about as diagnostic as these codes get.

 

[xxxmarioxxx]

BAsed on the timestamps, the console had 3034 (bad GPU presumably) in 2010 and was repaired. It lasted until experiencing a 1002 (RSX VRM filtering, presumably tokins). the 901001 can occur from failing tokins too, but many other causes. I do not believe the 3034's are connected with the event's you described. Perhaps the 1001 was and a dodgy connection causing it wouldn't suprise me.

Thanks for the info. I tried to ask the seller about the console's history, only thing he remembers is sending it back to sony for repair in 2009-2010 around slim's launch, then didn't use it as much since he bought a slim model. He did try to power on the console and get it working for several times before listing it as broken/parts on facebook, and he claims it was working before he put it in storage.

So it seems those error codes are old, but it still confuses me that those YLODs caused bad HDMI connection aren't recorded at all, I tried at least 5-10 times and so does seller. Anyway the console seems to be fully functional, doesn't show any sign of bad RSX or capacitor, except the oxidation in HDMI port.

 

[dvnlhnt]

Hello I got CECHG with YLOD <1 second.

Same here.

eepcsum

Addr:0x000032fe should be 0x1596

Addr:0x000034fe should be 0x86d6

sum:0x0100

Addr:0x000039fe should be 0x7360

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
errlog

ofst[  0]:err_code:0xa0404411, clock:0xffffffff

ofst[  4]:err_code:0xa0403034, clock:0x0ffc1d72  2008/06/30 22:40:50

ofst[  8]:err_code:0xa0404411, clock:0x0ffc1d88  2008/06/30 22:41:12

ofst[ 12]:err_code:0xa0403034, clock:0x0ffc1d88  2008/06/30 22:41:12

ofst[ 16]:err_code:0xa0404411, clock:0x0ffc1d8e  2008/06/30 22:41:18

ofst[ 20]:err_code:0xa0403034, clock:0x0ffc1d8e  2008/06/30 22:41:18

ofst[ 24]:err_code:0xa0404411, clock:0x0ffc1dad  2008/06/30 22:41:49

ofst[ 28]:err_code:0xa0403034, clock:0x0ffc1dad  2008/06/30 22:41:49

ofst[ 32]:err_code:0xa0404411, clock:0x0ffc1dbc  2008/06/30 22:42:04

ofst[ 36]:err_code:0xa0403034, clock:0x0ffc1dbc  2008/06/30 22:42:04

ofst[ 40]:err_code:0xa0404411, clock:0x0ffc1df0  2008/06/30 22:42:56

ofst[ 44]:err_code:0xa0403034, clock:0x0ffc1df0  2008/06/30 22:42:56

ofst[ 48]:err_code:0xa0404411, clock:0x0ffc1e04  2008/06/30 22:43:16

ofst[ 52]:err_code:0xa0403034, clock:0x0ffc1e04  2008/06/30 22:43:16

ofst[ 56]:err_code:0xa0404411, clock:0x0ffc1e0a  2008/06/30 22:43:22

ofst[ 60]:err_code:0xa0403034, clock:0x0ffc1e0a  2008/06/30 22:43:22

ofst[ 64]:err_code:0xa0404411, clock:0x0ffca89f  2008/07/01 08:34:39

ofst[ 68]:err_code:0xa0403034, clock:0x0ffca89f  2008/07/01 08:34:39

ofst[ 72]:err_code:0xa0404411, clock:0x1003c269  2008/07/06 17:50:33

ofst[ 76]:err_code:0xa0403034, clock:0x1003c269  2008/07/06 17:50:33

ofst[ 80]:err_code:0xa0404411, clock:0x19c67330  2013/09/14 01:06:56

ofst[ 84]:err_code:0xa0403034, clock:0x19c67330  2013/09/14 01:06:56

ofst[ 88]:err_code:0xa0404411, clock:0x19c67345  2013/09/14 01:07:17

ofst[ 92]:err_code:0xa0403034, clock:0x19c67345  2013/09/14 01:07:17

ofst[ 96]:err_code:0xa0404411, clock:0x2044645e  2017/02/25 15:50:54

ofst[100]:err_code:0xa0403034, clock:0x2044645e  2017/02/25 15:50:54

ofst[104]:err_code:0xa0404411, clock:0x20446469  2017/02/25 15:51:05

ofst[108]:err_code:0xa0403034, clock:0x20446469  2017/02/25 15:51:05

ofst[112]:err_code:0xa0404411, clock:0x20446482  2017/02/25 15:51:30

ofst[116]:err_code:0xa0403034, clock:0x20446482  2017/02/25 15:51:30

ofst[120]:err_code:0xa0404411, clock:0x2044648a  2017/02/25 15:51:38

ofst[124]:err_code:0xa0403034, clock:0x2044648a  2017/02/25 15:51:38

[mullion]$

becount

Bringup : 1689 times

Shutdown: 1521 times

Power-on: 130day 13hour 10min 05sec

[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.

[SSM] state: 0101 -> 0201

[POWSEQ] AV Backend Setup

[SSM] state: 0201 -> 0102

[SSM] state: 0102 -> 0202

[SSM] state: 0202 -> 0103

[SSM] state: 0103 -> 0203

[SSM] ssmCb_BeforeBeOn() called.

[SSM] state: 0203 -> 0104

Psbd_SbTransMode_Half:0x20e7

 

[Incursio]

This is RSX failure based on all the 3034 and 4401.

 

[4laZr3d]

Hi !
First post here after long time of reading. Thanks all of you for the amazing and crazy work of reasearching, testing and sharing.

I have finally got the logs of the internal mode of a YOLDed CECHG ( board SEM-001) with an Arduino Leonardo (its the only thing in my hand for serial communication) and a little voltage adjustment as follows ...

Spoiler

The code need a little adjustment of baud rate when we change from internal to external but it work with Leonardo (with my poor experience of serial, i have read 15200 in the guide page 4 and firstly believe i have problem elsewhere)

And please don't judge my wiring, i have read after it can be important and the awg30 is preferable :p

So for the records and diagnosis confirmation here it is :

$> becount

Bringup : 1934 times
Shutdown: 1424 times
Power-on: 125day 12hour 14min 11sec

$> errlog

ofst[ 24]:err_code:0xffffffff, clock:0x1375933f  2010/05/06 14:48:31
ofst[ 28]:err_code:0xa080 1001, clock:0x13ae789f  2010/06/18 18:34:07
ofst[ 32]:err_code:0xa080 1002, clock:0x13d4423b  2010/07/17 10:28:11
ofst[ 36]:err_code:0xa080 1001, clock:0x142f8545  2010/09/24 15:50:29
ofst[ 40]:err_code:0xa080 1001, clock:0x144af587  2010/10/15 11:20:39
ofst[ 44]:err_code:0xa080 1001, clock:0x1456a547  2010/10/24 08:05:27
ofst[ 48]:err_code:0xa080 1001, clock:0x14a4ffff  2010/12/22 18:29:19
ofst[ 52]:err_code:0xa080 1001, clock:0x15160be0  2011/03/18 12:26:08
ofst[ 56]:err_code:0xa080 1001, clock:0x15160beb  2011/03/18 12:26:19
ofst[ 60]:err_code:0xa080 1001, clock:0x15852dc4  2011/06/10 19:32:20
ofst[ 64]:err_code:0xa080 1001, clock:0x15a04fca  2011/07/01 09:28:42
ofst[ 68]:err_code:0xa080 1001, clock:0x17e0d2b6  2012/09/10 16:32:54
ofst[ 72]:err_code:0xa080 1001, clock:0x1950b0d2  2013/06/16 17:22:26
ofst[ 76]:err_code:0xa080 1001, clock:0x195f44be  2013/06/27 18:45:18
ofst[ 80]:err_code:0xa080 1001, clock:0x19bcd84e  2013/09/06 18:15:42
ofst[ 84]:err_code:0xa080 1701, clock:0x1a7ff78b  2014/02/01 18:20:59
ofst[ 88]:err_code:0xa080 14ff, clock:0xffffffff
ofst[ 92]:err_code:0xa080 1001, clock:0x1d89ffa6  2015/09/14 21:59:02
ofst[ 96]:err_code:0xa080 1001, clock:0x1d8a0156  2015/09/14 22:06:14
ofst[100]:err_code:0xa080 1001, clock:0x1f81b53e  2016/09/30 23:43:58
ofst[104]:err_code:0xa080 1001, clock:0x1fb9054c  2016/11/11 22:40:12
ofst[108]:err_code:0xa080 1001, clock:0x2c9e287f  2023/09/20 22:02:39

ofst[112]:err_code:0xa080 1701, clock:0x2cc59c17  2023/10/20 20:14:15
ofst[116]:err_code:0xa080 1601, clock:0x2cc59c17  2023/10/20 20:14:15
ofst[120]:err_code:0xa040 4402, clock:0x2cc59c2e  2023/10/20 20:14:38
ofst[124]:err_code:0xa040 3034, clock:0x2cc59c2e  2023/10/20 20:14:38
ofst[  0]:err_code:0xa080 1701, clock:0x2cc5a46b  2023/10/20 20:49:47
ofst[  4]:err_code:0xa080 1601, clock:0x2cc5a46b  2023/10/20 20:49:47
ofst[  8]:err_code:0xa040 4402, clock:0x2cc84630  2023/10/22 20:44:32
ofst[ 12]:err_code:0xa040 3034, clock:0x2cc84630  2023/10/22 20:44:32
ofst[ 16]:err_code:0xa040 4402, clock:0x2cff6c98  2023/12/03 16:43:04
ofst[ 20]:err_code:0xa040 3034, clock:0x2cff6c98  2023/12/03 16:43:04

$> bringup

[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

$> lasterrlog

Last Error Code:0xa0403034, Time:0x2d3de1e9  2024/01/20 01:44:09

The first YOLD sign have occurred when i was playing, total freezing, need to force reboot with holding power button.
If i have understanding good, It correspond to the two 1701 followed by 1601.

After that, dramatically, the booting is always aborted by a fairly fast YOLD which ...ouch end to the 4402 then 3034.

With that we have the BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS so sadly it seems to be the classic RSX solder defect ?

Need reball ? Maybe probing component around rsx with little hope it is something else ?
The ohms measurement need to be done between gnd and a certain point ?

 

[RIP-Felix]

Yes, RSX.

G models are nonBC and kinda a waste to repair this sort of issue. So the question is why you want to.

If there's a reason that makes it worth it, then a GPU replacment is reccomended. But if you want to prevent it from occuring again, it would be necessary to use a non-Decefective 65 or 40nm GPU. Which, due to the VDDR voltage mods needed make that hard. We haven't confirmed how to do it yet, tho I'm working on it and have ideas.

You can try a reball, but if it's the bumps (likely IMO) then it'll come back...not immediately and anger whatever poor sap you sell it to.

 

[4laZr3d]

Yes, RSX.

G models are nonBC and kinda a waste to repair this sort of issue. So the question is why you want to.

If there's a reason that makes it worth it, then a GPU replacment is reccomended. But if you want to prevent it from occuring again, it would be necessary to use a non-Decefective 65 or 40nm GPU. Which, due to the VDDR voltage mods needed make that hard. We haven't confirmed how to do it yet, tho I'm working on it and have ideas.

You can try a reball, but if it's the bumps (likely IMO) then it'll come back...not immediately and anger whatever poor sap you sell it to.

I want to repair this mostly for learning but also for the satisfaction of just don't trash it, maybe when the pcb will have burned i can trash it with the peace in mind.

When i said "need a reball" i mean of course with a 40nm (it can't be much more complicated so if i success, much as with a non defective GPU). However i thought it was the same voltage mod for all fat PS3. Maybe it can be more an experimentation/testing board than a real hope, as a starting point in this engineering sea .. or some other model are best for this type of sacrifice ?

I don't know the availability of a 40nm maybe if i found one it will be more advised to keep it for a BC ps3 ?

 

[roy76]

Hi, I've just aquired a PS3 CECHJ03 which wont boot up. I've got into the syscon & retrieved the details, if anyone could point me in the right direction I would be grateful. Cheers

errlog
ofst[ 32]:err_code:0xffffffff, clock:0x2c557d8c  2023/07/27 19:10:04
ofst[ 36]:err_code:0xa0202120, clock:0x2c557d8d  2023/07/27 19:10:05
ofst[ 40]:err_code:0xa0202120, clock:0x2c557d8e  2023/07/27 19:10:06
ofst[ 44]:err_code:0xa0202120, clock:0x2c557d8f  2023/07/27 19:10:07
ofst[ 48]:err_code:0xa0202120, clock:0x2c557d90  2023/07/27 19:10:08
ofst[ 52]:err_code:0xa0101002, clock:0x2c55831c  2023/07/27 19:33:48
ofst[ 56]:err_code:0xa0102113, clock:0x2c55831c  2023/07/27 19:33:48
ofst[ 60]:err_code:0xa0101002, clock:0x2c55862c  2023/07/27 19:46:52
ofst[ 64]:err_code:0xa0202120, clock:0x2c55862d  2023/07/27 19:46:53
ofst[ 68]:err_code:0xa0202120, clock:0x2c55862e  2023/07/27 19:46:54
ofst[ 72]:err_code:0xa0202120, clock:0x2c55862f  2023/07/27 19:46:55
ofst[ 76]:err_code:0xa0202120, clock:0x2c558630  2023/07/27 19:46:56
ofst[ 80]:err_code:0xa0202120, clock:0x2c558631  2023/07/27 19:46:57
ofst[ 84]:err_code:0xa0202120, clock:0x2c558632  2023/07/27 19:46:58
ofst[ 88]:err_code:0xa0202120, clock:0x2c558633  2023/07/27 19:46:59
ofst[ 92]:err_code:0xa0202120, clock:0x2c558634  2023/07/27 19:47:00
ofst[ 96]:err_code:0xa0202120, clock:0x2c558634  2023/07/27 19:47:00
ofst[100]:err_code:0xa0202120, clock:0x2c558635  2023/07/27 19:47:01
ofst[104]:err_code:0xa0091002, clock:0x2c558689  2023/07/27 19:48:25
ofst[108]:err_code:0xa0102014, clock:0x2c558689  2023/07/27 19:48:25
ofst[112]:err_code:0xa0101002, clock:0x2c5586bc  2023/07/27 19:49:16
ofst[116]:err_code:0xa0102113, clock:0x2c5586bc  2023/07/27 19:49:16
ofst[120]:err_code:0xa0101002, clock:0x2c5586e6  2023/07/27 19:49:58
ofst[124]:err_code:0xa0102014, clock:0x2c5586e6  2023/07/27 19:49:58
ofst[  0]:err_code:0xa0101002, clock:0x2c558721  2023/07/27 19:50:57
ofst[  4]:err_code:0xa0102113, clock:0x2c558721  2023/07/27 19:50:57
ofst[  8]:err_code:0xa0101002, clock:0x2d42ad60  2024/01/23 17:01:20
ofst[ 12]:err_code:0xa0102014, clock:0x2d42ad60  2024/01/23 17:01:20
ofst[ 16]:err_code:0xa0091002, clock:0x2d42ad6c  2024/01/23 17:01:32
ofst[ 20]:err_code:0xa0102014, clock:0x2d42ad6c  2024/01/23 17:01:32
ofst[ 24]:err_code:0xa0091002, clock:0x2d42ad7b  2024/01/23 17:01:47
ofst[ 28]:err_code:0xa0102014, clock:0x2d42ad7b  2024/01/23 17:01:47
[mullion]$
becount
Bringup : 2915 times
Shutdown: 2478 times
Power-on: 160day 13hour 00min 38sec
[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.
[SSM] fatalreq delayed.
[SSM] state: 0101 -> 0301
[SSM] *** Power Fail RS ***
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0101002
[ERROR]: 0xa0102114

 

[superprokill1]

@RIP-Felix
Several attempts later at desoldering, a few broken caps, a cut hand, several (probably) unhealthy fumes entering my respiratory system and me wasting the only copper wick I had until I figured I didn't need it at all for this, these are my results at scavenging for anything that looked like tantalum/aluminium caps:

tbh I'm proud of myself.
There were some other capacitors, some massive 1000uF ones that were the big cylindrical ones, or very small tantalum ones like top left that I assumed wouldn't be enough (if they are lmk so I can desolder some more of them). I also have two motherboards with what seems like 2x330uF aluminium ones each, which I guess would be perfect for this, but I believe the mobas still work, so I don't want to kill them just yet :^)
If I wanted to parasite solder any of them to see if it reaches the XMB and stops YLOD'ing, which one should I go for? I'm not exactly sure which of these are useful for the job and which aren't, I'd really appreciate it if you could enlighten me. Non sarcastically, thanks for forcing me to learn desoldering!

 

[RIP-Felix]

I want to repair this mostly for learning but also for the satisfaction of just don't trash it, maybe when the pcb will have burned i can trash it with the peace in mind.

When i said "need a reball" i mean of course with a 40nm (it can't be much more complicated so if i success, much as with a non defective GPU). However i thought it was the same voltage mod for all fat PS3. Maybe it can be more an experimentation/testing board than a real hope, as a starting point in this engineering sea .. or some other model are best for this type of sacrifice ?

I don't know the availability of a 40nm maybe if i found one it will be more advised to keep it for a BC ps3 ?

So here's my ethical dilemma with wasting a 40nm or 65nm RSX on a G model.

1. It's not a backwards compatible model. Meaning you can easily and cheaply replace it with another noBC model that is reliable.
2. A leaded 90nm reball can last a good long time. So while yes, it's defective, that model isn't desirable or worth wasting good GPU on. So the SEM-001 and DIA-001 motherboards are the 2 revisions I would argue for a reball/90nm GPU replacment. Which require no special hacks. Replace GPU and pray it works. If it breaks again in a couple years...well, it's a 90nm nonBC model. Who cares?! It not any more defective than it was off the line. And just as undesirable. Which makes it a good candidate for practicing.
3. The supply of 40nm and 65nm chips will shrink as more and more are harvested to salvage BC modles. There are 6M BC ps3s. And at many multuples more nonBC/slims to harvst from...BUT, that assumes we only need 1 GPU to fix a BC and we're finding it's taking 2 or 3 harvested chips to get 1 frankie working. The NOS chips were great while they lasted, but now we have to pull from the used old stock...which is aparently hit or miss. If it takes half the slims to save all the BC models, is that massacre worth it? Ethically? IDK.
4. Now if we waste those 40nm or 65nm chips on pointless consoles it only dilutes the supply and means more living slims have to die. Which now is pushing my ethical buttons.