RSX 100%
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
Bertus van Zyl
Member
I triple checked and then on the wiki this is the section I read:
1b02 (RSX Initialization)
RSX Thermal Sense Error. Thermal Monitor (IC2101) external sense line. Check C2103, R2101/2 & replace IC2101 (COK-00x) before reballing/Replacing RSX. If all else fails the GPU's thermal diode is dead.
This error tends to occur at step number 20, during core initialization.
Confirmed that removing R2101/2 or the GPU itself causes A0201b02/A0A02031 errors.
https://github.com/db260179/ps3syscon
Typical recorded errors (errlog) in the syscon shell:
A = Fixed value
00-7F = Step number of power on sequence
80 = Poweron state
90 = Poweroff state
A0 = Power on immediatley after syscon reset
Categories:
1 = System error 2 = Fatal error 3 = Fatal booting error 4 = Data error
Recorded errors:
A0022110 = MK I2C ERROR (OR OTHER CLOCK's ERRORS)
A0A02031 = Thermal monitor DI/DO not communicating to RSX (possible dead Diodes in RSX)
A0201B02 = RSX VRAM FAIL - Faulty vrams - Borked RSX VRAM, VDDIO reading on RSX is infinite - Dead RSX
A0201B01 = CELL - Low resistance on VDDIO (reading should be in megaohms), resistance readings near the tokins read higher than 4.5ohms = Dead core on the CELL
A0203010 = BE_INIT OR BE_POWGOOD OR CLOCK ERRORS
A0213011 = BE_SPI CS ERROR
A0213013 = BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?
A0232102 = IC6301 possible faulty - check other DC converters, caps etc in that power line from the schematics
A0003001 = POW_FAIL
A0302203 = SB_SPI DI/DO ERROR
A0313032 = SB_CLOCK OR INIT ERROR (can be related to the CELL solder balls not making proper connection and will most likely had previous errors like A0403034, A0404401) - check for voltages first!
A0401001 = BE VRAM Power Fail - running state possible tokins issues
A0401002 = RSX VRAM Power Fail - running state possible tokins issues
A0401301 = BE PLL Unlock
A0402120 = HDMI Error (IC2502)
A0403034, A0404402,A0404411 (RSX) = Poor BGA solder connections for RSX need reflow or reball ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
A0403034, A0404401 (CELL) = Poor BGA solder connections for CELL need reflow or reball ( you will see errors like - [POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS ) (With the above errors you will get other errors with the BitTraining they are all related to the poor BGA connection or broken traces under the chips)
A0404002 = RSX_SPI DI/DO ERROR (Poor BGA connection for RSX can cause this error or DEAD RSX)
A0404411 = ERROR ON RSX SPI?
A0801001 = CELL Power on VRAM failure (Potential NEC tokins issue and VCC)
A0801002 = RSX Power on VRAM failure (Potential NEC tokins issue and VCC)
A0801200 = CELL overheating - poor thermal paste or no heatsink attached, GLOD symptoms
A0821200 = HDMI Power on failure (IC2502) - Sil9132CBU chip failure or related power line failure - check diodes,fuses and regulator IC2501
A0902203 = SB GLOD issues, system update to repair nand/nor hashes
A0093003 = CELL_POW_FAIL poweroff state (Potential NEC tokins issue and VCC or Dead/Short in the CELL)
A0093004 = RSX_POW_FAIL poweroff state (Potential NEC tokins issue and VCC or Dead/Short in the RSX (core reads 0.2 ohms))
Notes on error codes
A0093003 and A0093004 (usually associate with nec tokin faults) have found to have issues with shorts on the PCB layer - COKxx boards seems to have a defect of the pcb layers (too much heating stresses the pcb layers) shorting on the VDD line to the Buck controllers (5v) which causes leaking voltage.
Sometimes an error code can have an associate error code with it as seen with A0403034 (data error) and RS:RRAC:BX0:BX:FLEXIO_ID Bittraining errors = CELL cant talk or understand the RSX ID code (seen in swapping an 90nm to 65nm or 40nm)
Typical recorded errors (errlog) in the syscon shell:
A = Fixed value
00-7F = Step number of power on sequence
80 = Poweron state
90 = Poweroff state
A0 = Power on immediatley after syscon reset
Categories:
1 = System error 2 = Fatal error 3 = Fatal booting error 4 = Data error
Recorded errors:
A0022110 = MK I2C ERROR (OR OTHER CLOCK's ERRORS)
A0A02031 = Thermal monitor DI/DO not communicating to RSX (possible dead Diodes in RSX)
A0201B02 = RSX VRAM FAIL - Faulty vrams - Borked RSX VRAM, VDDIO reading on RSX is infinite - Dead RSX
A0201B01 = CELL - Low resistance on VDDIO (reading should be in megaohms), resistance readings near the tokins read higher than 4.5ohms = Dead core on the CELL
A0203010 = BE_INIT OR BE_POWGOOD OR CLOCK ERRORS
A0213011 = BE_SPI CS ERROR
A0213013 = BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?
A0232102 = IC6301 possible faulty - check other DC converters, caps etc in that power line from the schematics
A0003001 = POW_FAIL
A0302203 = SB_SPI DI/DO ERROR
A0313032 = SB_CLOCK OR INIT ERROR (can be related to the CELL solder balls not making proper connection and will most likely had previous errors like A0403034, A0404401) - check for voltages first!
A0401001 = BE VRAM Power Fail - running state possible tokins issues
A0401002 = RSX VRAM Power Fail - running state possible tokins issues
A0401301 = BE PLL Unlock
A0402120 = HDMI Error (IC2502)
A0403034, A0404402,A0404411 (RSX) = Poor BGA solder connections for RSX need reflow or reball ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
A0403034, A0404401 (CELL) = Poor BGA solder connections for CELL need reflow or reball ( you will see errors like - [POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS ) (With the above errors you will get other errors with the BitTraining they are all related to the poor BGA connection or broken traces under the chips)
A0404002 = RSX_SPI DI/DO ERROR (Poor BGA connection for RSX can cause this error or DEAD RSX)
A0404411 = ERROR ON RSX SPI?
A0801001 = CELL Power on VRAM failure (Potential NEC tokins issue and VCC)
A0801002 = RSX Power on VRAM failure (Potential NEC tokins issue and VCC)
A0801200 = CELL overheating - poor thermal paste or no heatsink attached, GLOD symptoms
A0821200 = HDMI Power on failure (IC2502) - Sil9132CBU chip failure or related power line failure - check diodes,fuses and regulator IC2501
A0902203 = SB GLOD issues, system update to repair nand/nor hashes
A0093003 = CELL_POW_FAIL poweroff state (Potential NEC tokins issue and VCC or Dead/Short in the CELL)
A0093004 = RSX_POW_FAIL poweroff state (Potential NEC tokins issue and VCC or Dead/Short in the RSX (core reads 0.2 ohms))
Notes on error codes
A0093003 and A0093004 (usually associate with nec tokin faults) have found to have issues with shorts on the PCB layer - COKxx boards seems to have a defect of the pcb layers (too much heating stresses the pcb layers) shorting on the VDD line to the Buck controllers (5v) which causes leaking voltage.
Sometimes an error code can have an associate error code with it as seen with A0403034 (data error) and RS:RRAC:BX0:BX:FLEXIO_ID Bittraining errors = CELL cant talk or understand the RSX ID code (seen in swapping an 90nm to 65nm or 40nm)
Gurwinder Singh
Forum Noob
Can someone explain me how to solve yellow light of death issue? I have ps3 fat 80gb (DIA-002) Model motherboard. I diagnosed the syscon error codes and it shows that RSX Core Power Failure (3004).
Error codes
errlogofst[ 44]:err_code:0xffffffff, clock:0xffffffffofst[ 48]:err_code:0xa0093004, clock:0xffffffffofst[ 52]:err_code:0xa0093004, clock:0xffffffffofst[ 56]:err_code:0xa0093004, clock:0xffffffffofst[ 60]:err_code:0xa0093004, clock:0xffffffffofst[ 64]:err_code:0xa0093004, clock:0xffffffffofst[ 68]:err_code:0xa0093004, clock:0xffffffffofst[ 72]:err_code:0xa0093004, clock:0xffffffffofst[ 76]:err_code:0xa0093004, clock:0xffffffffofst[ 80]:err_code:0xa0093004, clock:0xffffffffofst[ 84]:err_code:0xa0093004, clock:0xffffffffofst[ 88]:err_code:0xa0093004, clock:0xffffffffofst[ 92]:err_code:0xa0093004, clock:0xffffffffofst[ 96]:err_code:0xa0093004, clock:0xffffffffofst[100]:err_code:0xa0093004, clock:0xffffffffofst[104]:err_code:0xa0093004, clock:0xffffffffofst[108]:err_code:0xa0093004, clock:0xffffffffofst[112]:err_code:0xa0093004, clock:0xffffffffofst[116]:err_code:0xa0093004, clock:0xffffffffofst[120]:err_code:0xa0093004, clock:0xffffffffofst[124]:err_code:0xa0093004, clock:0xffffffffofst[ 0]:err_code:0xa0093004, clock:0xffffffffofst[ 4]:err_code:0xa0093004, clock:0xffffffffofst[ 8]:err_code:0xa0093004, clock:0xffffffffofst[ 12]:err_code:0xa0093004, clock:0xffffffffofst[ 16]:err_code:0xa0093004, clock:0xffffffffofst[ 20]:err_code:0xa0093004, clock:0xffffffffofst[ 24]:err_code:0xa0093004, clock:0xffffffffofst[ 28]:err_code:0xa0093004, clock:0xffffffffofst[ 32]:err_code:0xa0093004, clock:0xffffffffofst[ 36]:err_code:0xa0093004, clock:0xffffffffofst[ 40]:err_code:0xa0093004, clock:0xffffffff
Error codes
errlogofst[ 44]:err_code:0xffffffff, clock:0xffffffffofst[ 48]:err_code:0xa0093004, clock:0xffffffffofst[ 52]:err_code:0xa0093004, clock:0xffffffffofst[ 56]:err_code:0xa0093004, clock:0xffffffffofst[ 60]:err_code:0xa0093004, clock:0xffffffffofst[ 64]:err_code:0xa0093004, clock:0xffffffffofst[ 68]:err_code:0xa0093004, clock:0xffffffffofst[ 72]:err_code:0xa0093004, clock:0xffffffffofst[ 76]:err_code:0xa0093004, clock:0xffffffffofst[ 80]:err_code:0xa0093004, clock:0xffffffffofst[ 84]:err_code:0xa0093004, clock:0xffffffffofst[ 88]:err_code:0xa0093004, clock:0xffffffffofst[ 92]:err_code:0xa0093004, clock:0xffffffffofst[ 96]:err_code:0xa0093004, clock:0xffffffffofst[100]:err_code:0xa0093004, clock:0xffffffffofst[104]:err_code:0xa0093004, clock:0xffffffffofst[108]:err_code:0xa0093004, clock:0xffffffffofst[112]:err_code:0xa0093004, clock:0xffffffffofst[116]:err_code:0xa0093004, clock:0xffffffffofst[120]:err_code:0xa0093004, clock:0xffffffffofst[124]:err_code:0xa0093004, clock:0xffffffffofst[ 0]:err_code:0xa0093004, clock:0xffffffffofst[ 4]:err_code:0xa0093004, clock:0xffffffffofst[ 8]:err_code:0xa0093004, clock:0xffffffffofst[ 12]:err_code:0xa0093004, clock:0xffffffffofst[ 16]:err_code:0xa0093004, clock:0xffffffffofst[ 20]:err_code:0xa0093004, clock:0xffffffffofst[ 24]:err_code:0xa0093004, clock:0xffffffffofst[ 28]:err_code:0xa0093004, clock:0xffffffffofst[ 32]:err_code:0xa0093004, clock:0xffffffffofst[ 36]:err_code:0xa0093004, clock:0xffffffffofst[ 40]:err_code:0xa0093004, clock:0xffffffff
Gurwinder Singh
Forum Noob
My ps3 suffers from 3004 error and it causes ylod can you tell me how can I solve this?
Should I replace NEC tokins to the tantalum capacitor from rsx side?
Should I replace NEC tokins to the tantalum capacitor from rsx side?
Hello.
I have received CECHA revision recently from Japan. It had sealed sticker. But after tearing it down I noticed wet thermal paste under the radiator. And, more important, signs of melting on certain NEC TOKINs, other damage on them and two very strange elements near two TOKINs for RSX.
I made maintenance and delided RSX. After all procedures most of games run well, the temperatures are fine (CELL: 68; RSX: 55; fan: 35%). But it shuts down quickly with red lights and beeps (not sure about yellow) in Gran Turismo 6. It looks like frequent behaviour in case of power supply issues with chips.
Should I replace NEC TOKINs? For CPU and GPU? On both sides of the motherboard (8 total)?
And do you have any ideas who and why added two capacitors (?) near two TOKINs?
I have received CECHA revision recently from Japan. It had sealed sticker. But after tearing it down I noticed wet thermal paste under the radiator. And, more important, signs of melting on certain NEC TOKINs, other damage on them and two very strange elements near two TOKINs for RSX.
I made maintenance and delided RSX. After all procedures most of games run well, the temperatures are fine (CELL: 68; RSX: 55; fan: 35%). But it shuts down quickly with red lights and beeps (not sure about yellow) in Gran Turismo 6. It looks like frequent behaviour in case of power supply issues with chips.
Should I replace NEC TOKINs? For CPU and GPU? On both sides of the motherboard (8 total)?
And do you have any ideas who and why added two capacitors (?) near two TOKINs?
Hi not to sound like a noob but does this mean my ps3 is DOA?
Hi all. Glad to be joining such a great community. I have received a PS3 with YLOD and trying to bring it to life again for my son. It does not boot at all. I have managed to connect to the board via SYSCOM. Here is the error report. Would anyone be able to advise me where do I start fixing and is it actually worth the hassle. Is it the NEC tokens or GPU or something else. Thanks in advance all. I have a Mullion SEM - 001 board. When you turn it on, it beeps 3 times within like 3 seconds and dies with YLOD.
Code:
becount
Bringup : 1676 times
Shutdown: 1547 times
Power-on: 74day 23hour 43min 10sec
Bringup errlog
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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
Press Ctrl+C to exit
>$
[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:RX2:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404422
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
>$ 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] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
Press Ctrl+C to exit
>$
[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:RX2:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404422
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Internal errlog:
ofst[108]:err_code:0xffffffff, clock:0x2e4a8400 2024/08/10 20:03:12
ofst[112]:err_code:0xa0403034, clock:0x2e4a8400 2024/08/10 20:03:12
ofst[116]:err_code:0xa0404422, clock:0x2e4a8407 2024/08/10 20:03:19
ofst[120]:err_code:0xa0403034, clock:0x2e4a8407 2024/08/10 20:03:19
ofst[124]:err_code:0xa0404422, clock:0x2e4a840a 2024/08/10 20:03:22
ofst[ 0]:err_code:0xa0403034, clock:0x2e4a840a 2024/08/10 20:03:22
ofst[ 4]:err_code:0xa0404422, clock:0x2e4a840f 2024/08/10 20:03:27
ofst[ 8]:err_code:0xa0403034, clock:0x2e4a840f 2024/08/10 20:03:27
ofst[ 12]:err_code:0xa0404422, clock:0x2e4a8413 2024/08/10 20:03:31
ofst[ 16]:err_code:0xa0403034, clock:0x2e4a8413 2024/08/10 20:03:31
ofst[ 20]:err_code:0xa0404422, clock:0x2e4a8418 2024/08/10 20:03:36
ofst[ 24]:err_code:0xa0403034, clock:0x2e4a8418 2024/08/10 20:03:36
ofst[ 28]:err_code:0xa0404422, clock:0x2e4a841e 2024/08/10 20:03:42
ofst[ 32]:err_code:0xa0403034, clock:0x2e4a841e 2024/08/10 20:03:42
ofst[ 36]:err_code:0xa0404422, clock:0x2e4fdefb 2024/08/14 21:32:43
ofst[ 40]:err_code:0xa0403034, clock:0x2e4fdefb 2024/08/14 21:32:43
ofst[ 44]:err_code:0xa0404422, clock:0x2e4fdf00 2024/08/14 21:32:48
ofst[ 48]:err_code:0xa0403034, clock:0x2e4fdf00 2024/08/14 21:32:48
ofst[ 52]:err_code:0xa0404422, clock:0x2e4fdf06 2024/08/14 21:32:54
ofst[ 56]:err_code:0xa0403034, clock:0x2e4fdf06 2024/08/14 21:32:54
ofst[ 60]:err_code:0xa0404422, clock:0x2e6b4bcc 2024/09/04 16:48:12
ofst[ 64]:err_code:0xa0403034, clock:0x2e6b4bcc 2024/09/04 16:48:12
ofst[ 68]:err_code:0xa0404422, clock:0x2e6b4be3 2024/09/04 16:48:35
ofst[ 72]:err_code:0xa0403034, clock:0x2e6b4be3 2024/09/04 16:48:35
ofst[ 76]:err_code:0xa0404422, clock:0x2e6b4bf3 2024/09/04 16:48:51
ofst[ 80]:err_code:0xa0403034, clock:0x2e6b4bf3 2024/09/04 16:48:51
ofst[ 84]:err_code:0xa0404422, clock:0x2e6b4d55 2024/09/04 16:54:45
ofst[ 88]:err_code:0xa0403034, clock:0x2e6b4d55 2024/09/04 16:54:45
ofst[ 92]:err_code:0xa0404422, clock:0x2e6b4d74 2024/09/04 16:55:16
ofst[ 96]:err_code:0xa0403034, clock:0x2e6b4d74 2024/09/04 16:55:16
ofst[100]:err_code:0xa0404422, clock:0x2e6b4f11 2024/09/04 17:02:09
ofst[104]:err_code:0xa0403034, clock:0x2e6b4f11 2024/09/04 17:02:09
External errlog
>$ ERRLOG GET 00
00000000 A0403034 2E6B4F11
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0404422 2E6B4F11
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0403034 2E6B4D74
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0404422 2E6B4D74
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0403034 2E6B4D55
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0404422 2E6B4D55
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0403034 2E6B4BF3
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0404422 2E6B4BF3
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0403034 2E6B4BE3
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0404422 2E6B4BE3
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0403034 2E6B4BCC
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0404422 2E6B4BCC
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0403034 2E4FDF06
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0404422 2E4FDF06
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0403034 2E4FDF00
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0404422 2E4FDF00
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0403034 2E4FDEFB
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0404422 2E4FDEFB
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0403034 2E4A841E
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0404422 2E4A841E
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0403034 2E4A8418
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0404422 2E4A8418
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0403034 2E4A8413
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0404422 2E4A8413
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0403034 2E4A840F
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0404422 2E4A840F
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0403034 2E4A840A
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0404422 2E4A840A
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0403034 2E4A8407
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0404422 2E4A8407Help Needed!
I have a DECH-2000A slim with YLOD all looks good inside the metal parts holding the MB did have a bit of rust on the edge not a lot though.
This is what i got from the error logs.
I don't know much about this kind of stuff so any help would be much appreciated 
I have a DECH-2000A slim with YLOD all looks good inside the metal parts holding the MB did have a bit of rust on the edge not a lot though.
This is what i got from the error logs.
Code:
>$ auth
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
Press Ctrl+C to exit
>$ errlog
00000000
# CODE CLOCK
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ bringup
FFFFA605
Press Ctrl+C to exit
>$ bringup
FFFFA605
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [SSM] Bringup Start.
# [PowSeq] Error:A103
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
Press Ctrl+C to exit
>$
RIP-Felix
Senior Member
This is an RSX (GPU) issue that will not be worth the repair attempt. You will be better off buying a working replacment. May I suggest a 21xx model? That is the most reliable, non-PS2 backwards compatible model. If you like the phat model's look better, then a J, K, L, or P model are the ones to get, as they don't have the defective 90nm GPU. But they do have NEC/Tokins which can fail (the 21xx does not).
Hello.
I have received CECHA revision recently from Japan. It had sealed sticker. But after tearing it down I noticed wet thermal paste under the radiator. And, more important, signs of melting on certain NEC TOKINs, other damage on them and two very strange elements near two TOKINs for RSX.
I made maintenance and delided RSX. After all procedures most of games run well, the temperatures are fine (CELL: 68; RSX: 55; fan: 35%). But it shuts down quickly with red lights and beeps (not sure about yellow) in Gran Turismo 6. It looks like frequent behaviour in case of power supply issues with chips.
Should I replace NEC TOKINs? For CPU and GPU? On both sides of the motherboard (8 total)?
And do you have any ideas who and why added two capacitors (?) near two TOKINs?
I can't telly you who, but I can tell you why. Those "parasite" capacitors help to decouple some of the ripple voltage on the RSX (GPU) Vcore. The type of behavior you are experiancing in game is caused by core voltage dropout protection. The voltage controller experianced a voltage "wave" that was larger than it will allow. It informed the system controller, which to protect the console, shut it down and logged the error code 1001. That is the CPU side.
So, here's the diagnosis. At some point this console was experiancing an issue similar to yours. In order to fix it a previous owner added a couple parasite caps to the RSX side, but not the CPU side. They may not have checked the SYSCON errorlogs like you did before assuming it was the RSX side that needed caps. Or perhaps at that time it was a 1002, which would indicate RSX side caps. So either they attemped to fix the RSX side caps and it fixed it for awhile until the CPU side failed. Or they missdiagnosed which side needed the caps.
How to fix. You will need to remove the CPU side tokins and replace them with an appropriate array of polymer caps. That'll fix the 1001 errors. I reccomend preplacing the RSX side at the same time, since all of them have worn down and it makes sense to just get it done once.
If replacing them, I reccomend replacing all of them and not mixing parasites woth old tokins. However, if you are only interested in a temporary patch, then you could copy what they did on the CPU side. That will very likely fix the issue in the short term.
Most likely, yes.
This looks to be bad Tokins. RSX side for sure, possably CPU side as well. However, if you have to replace one side the other side will need to be replaced soon anyway. So may as well get them both replaced.
Last edited:
RIP-Felix
Senior Member
That's an unreported error. Clearly a sherwood code, which is why. We don't get as many reports from slims.
Can you please provide details about the console history, behavior, and condition of the motherboard?
Was it sealed? Did the motherboard have any repairs done? Flux on the board? Shell damage indicating it may have fell or been abused in shipping. What have you tried? Checked fuses, voltages, etc.
These may help in the future figure out what that code means when someone else comse across it.
EDIT:
- Likely the 1200 was from testing without the HS attached. Please confirm.
- 1004 and 3001s were likely from testing without the 12v connected and forcing improper shutdowns. Please confirm.
- Judging from the timestamps you or someone then removed the clock batt and reflowed "soemthing" (please confirm what you reflowed) on the board resulting in the thermal monitor errors 2130/2131.
- Judging by the timestamp and order of the error codes I would guess the A0012310 occurred at the same time as the A0801200 or on the next boot attempt. It may not prevent a boot, but I have no idea, since I've never seen it before. The 2310 is interesting and never reported before.
- A GLOD that pairs, sounds like a GPU issue. Like when VRAM dies.
Last edited:
Adriaan Couchez
Member
I recently ordered a CECHA00 from Japan, which was delivered at the end of last week. After about 5 minutes of use, it froze (just in the XMB). Since then, it has shown a YLOD.
Before that, I briefly had a display, but with some artifacts (see photo). The cost of sending it back to Japan and requesting a return would be more than half of what I paid for it.
I replaced the thermal paste myself and cleaned out the dust (as it was very dirty), but this didn't seem to help.
After doing some research online (thnx rip felix), I found out how to read the syscon. I did that for this console, and it showed errors that seem related to the RSX/GPU.
Error log:
becount
Bringup : 251 times
Shutdown: 239 times
Power-on: 9day 19hour 45min 17sec
Boot Sequence:
Any help would be greatly appreciated.
Before that, I briefly had a display, but with some artifacts (see photo). The cost of sending it back to Japan and requesting a return would be more than half of what I paid for it.
I replaced the thermal paste myself and cleaned out the dust (as it was very dirty), but this didn't seem to help.
After doing some research online (thnx rip felix), I found out how to read the syscon. I did that for this console, and it showed errors that seem related to the RSX/GPU.
Error log:
Code:
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0403034 0B48AC17
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0902120 0B48AC08
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0403034 0B48AC08
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0232102 0B488B48
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0232102 0B488B3D
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0232102 0B488B18
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0232102 0B488ACB
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0232102 0B488ABE
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0902120 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0403034 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0403034 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0403034 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0403034 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801001 2E7A304D
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801001 2E7A2F87
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801001 2E7A2EFE
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801001 2E7A2A4B
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0801001 2E73FDF2
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801001 2E45D9B3
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0801001 2E45D914
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801001 2E45D8F1
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0801001 24D6D779
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0801001 24B1AA58
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801001 24A9BA5E
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801001 24A8CD9F
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exitbecount
Bringup : 251 times
Shutdown: 239 times
Power-on: 9day 19hour 45min 17sec
Boot Sequence:
Code:
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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)Any help would be greatly appreciated.
Adriaan Couchez
Member
Image of last time it has an image:
Gurwinder Singh
Forum Noob
______________________________________________
In my opinion either you use 330uf or 470uf but you have to check the capacitance of it the tokins has most likely 1200uf capacitance which is the result you have to use 330uf×4 or 470uf×3 in my opinion otherwise @rip_felix can help you.
RIP-Felix
Senior Member
The RSX needs replaced. Difficult repair, expensive service. It is what it is. Sorry I don't have better news.
Hello everyone. PS3 slim, shutting down after 3-4 seconds. It appears to me as a short somewhere outside rsx or cell. Would appreciate any help.
Code:
C:\Users\MEMPHIS\Desktop\ps3\syscon\ps3syscon-master\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM4 SW
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0403034 2E846F17
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0404403 2E846F16
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0403034 2E845FD8
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0404441 2E845FD8
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0403034 2E845A3E
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0404441 2E845A3E
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0403034 2E845A26
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0404441 2E845A25
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0403034 2E354423
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0404441 2E354422
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0403034 2E33E363
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0404403 2E33E363
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0403034 2E33E2B6
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0404403 2E33E2B5
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0403034 2E33E2AC
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0404403 2E33E2AB
Press Ctrl+C to exit
>$ ERRLOG GET 0G
F0000006
# [UCMD] Invalid arg.
Press Ctrl+C to exit
>$ ERRLOG
00000000
# CODE CLOCK
# A0403034 2E846F17
# A0404403 2E846F16
# A0403034 2E845FD8
# A0404441 2E845FD8
# A0403034 2E845A3E
# A0404441 2E845A3E
# A0403034 2E845A26
# A0404441 2E845A25
# A0403034 2E354423
# A0404441 2E354422
# A0403034 2E33E363
# A0404403 2E33E363
# A0403034 2E33E2B6
# A0404403 2E33E2B5
# A0403034 2E33E2AC
# A0404403 2E33E2AB
# A0403034 2E295F8D
# A0404441 2E295F8D
# A0403034 2E295F84
# A0404441 2E295F83
# A0403034 2E295EC6
# A0404441 2E295EC5
# A0403034 2E295EAA
# A0404441 2E295EA9
# A0403034 2E295E9F
# A0404441 2E295E9E
# A0403034 2E294A92
# A0404441 2E294A91
# A0403034 2E294A81
# A0404441 2E294A81
# A0403034 2E2936FE
Press Ctrl+C to exit
>$ BECOUNT
F0000003
# [UCMD] Unknown command.
Press Ctrl+C to exit
>$ becount
F0000003
# [UCMD] Unknown command.
Press Ctrl+C to exit
>$ becount
F0000003
# [UCMD] Unknown command.
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9203
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [UCMD] Unknown command.
Press Ctrl+C to exit
>$ powerstate
00000000
# ATA :OFF
# PCI :OFF
# PCIex:OFF
# RSX :OFF
# GDDR :OFF
# XDR :OFF
# EURUS:OFF
# SB :OFF
# LAN :OFF
# WLAN :ON
Press Ctrl+C to exit
>$Similar threads
-
PS3 Kohada - A repair & tuning toolkit for the PS3 syscon- Started by sagemono
- Replies: 2
-
PS3 [Tutorial] How to use an ESP32 as a SYSCON UART Bridge- Started by GrGeorge
- Replies: 0
-
-
