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

Anyone have any suggestions for this console? After putting a 40nm on it im getting instant YLOD but it wont drop an error code. I normally swap the TOKINs after I get it booting but they were bad so I had to swap them first.

Code: 
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
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Previous error log info
Code: 
Bringup : 1451 times
Shutdown: 1359 times
Power-on: 2976day 06hour 29min 25sec


ofst[120]:err_code:0xffffffff, clock:0x10468ab0  2008/08/26 09:34:40
ofst[124]:err_code:0xa0801002, clock:0x10468ab6  2008/08/26 09:34:46
ofst[  0]:err_code:0xa0101001, clock:0x10468ab9  2008/08/26 09:34:49
ofst[  4]:err_code:0xa0801002, clock:0x10468ac0  2008/08/26 09:34:56
ofst[  8]:err_code:0xa0801002, clock:0x10468acf  2008/08/26 09:35:11
ofst[ 12]:err_code:0xa0801002, clock:0x10468ad4  2008/08/26 09:35:16
ofst[ 16]:err_code:0xa0801002, clock:0x10468afb  2008/08/26 09:35:55
ofst[ 20]:err_code:0xa0801002, clock:0x10468b01  2008/08/26 09:36:01
ofst[ 24]:err_code:0xa0801002, clock:0x10468b09  2008/08/26 09:36:09
ofst[ 28]:err_code:0xa0801002, clock:0x10468b0f  2008/08/26 09:36:15
ofst[ 32]:err_code:0xa0801002, clock:0x10468b16  2008/08/26 09:36:22
ofst[ 36]:err_code:0xa0801002, clock:0x10468b1d  2008/08/26 09:36:29
ofst[ 40]:err_code:0xa0101001, clock:0x10468b1f  2008/08/26 09:36:31
ofst[ 44]:err_code:0xa0801002, clock:0x10468b24  2008/08/26 09:36:36
ofst[ 48]:err_code:0xa0101001, clock:0x10468b26  2008/08/26 09:36:38
ofst[ 52]:err_code:0xa0611001, clock:0x10468b28  2008/08/26 09:36:40
ofst[ 56]:err_code:0xa0801002, clock:0x10468b31  2008/08/26 09:36:49
ofst[ 60]:err_code:0xa0801002, clock:0x10468b36  2008/08/26 09:36:54
ofst[ 64]:err_code:0xa0801002, clock:0x10468b3d  2008/08/26 09:37:01
ofst[ 68]:err_code:0xa0801002, clock:0x10468b43  2008/08/26 09:37:07
ofst[ 72]:err_code:0xa0801002, clock:0x10468b49  2008/08/26 09:37:13
ofst[ 76]:err_code:0xa0801002, clock:0x10468b50  2008/08/26 09:37:20
ofst[ 80]:err_code:0xa0801002, clock:0x10468b56  2008/08/26 09:37:26
ofst[ 84]:err_code:0xa0801002, clock:0x10468b5c  2008/08/26 09:37:32
ofst[ 88]:err_code:0xa0801002, clock:0x10468b62  2008/08/26 09:37:38
ofst[ 92]:err_code:0xa0801002, clock:0x10468b69  2008/08/26 09:37:45
ofst[ 96]:err_code:0xa0801002, clock:0x10468b6f  2008/08/26 09:37:51
ofst[100]:err_code:0xa0801002, clock:0x10468b84  2008/08/26 09:38:12
ofst[104]:err_code:0xa0801002, clock:0x10468b8b  2008/08/26 09:38:19
ofst[108]:err_code:0xa0101001, clock:0x10468b8d  2008/08/26 09:38:21
ofst[112]:err_code:0xa0801002, clock:0x10468b94  2008/08/26 09:38:28
ofst[116]:err_code:0xa0801002, clock:0x10468b9b  2008/08/26 09:38:35
 
Hi everyone
I have ps3 board kte-001 has errors A0404441 And A0403034
I reballed the cell/be the same thing.
Is it the problem with the rsx?
 
Hello everyone, this is my first experience about this.

PS3 Fat, CECHC04, COOK-002 backwards compatible.

It's my own console, it was never opened or attempted to be repaired, since it had the YLOD many years ago,
I kept it until now, when I opened it for the first time to try to fix it.

Syscon error codes, with becount and bringup:

errlog
ofst[104]:err_code:0xffffffff, clock:0x18a81865 2013/02/08 20:11:17
ofst[108]:err_code:0xa0403034, clock:0x18a81865 2013/02/08 20:11:17
ofst[112]:err_code:0xa0404421, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[116]:err_code:0xa0403034, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[120]:err_code:0xa0404421, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[124]:err_code:0xa0403034, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[ 0]:err_code:0xa0404421, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 4]:err_code:0xa0403034, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 8]:err_code:0xa0404421, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 12]:err_code:0xa0403034, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 16]:err_code:0xa0404421, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 20]:err_code:0xa0403034, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 24]:err_code:0xa0404421, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 28]:err_code:0xa0403034, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 32]:err_code:0xa0404421, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 36]:err_code:0xa0403034, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 40]:err_code:0xa0404421, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 44]:err_code:0xa0403034, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 48]:err_code:0xa0404421, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 52]:err_code:0xa0403034, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 56]:err_code:0xa0404421, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 60]:err_code:0xa0403034, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 64]:err_code:0xa0404421, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 68]:err_code:0xa0403034, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 72]:err_code:0xa0404421, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 76]:err_code:0xa0403034, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 80]:err_code:0xa0404421, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404421, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404421, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff

becount
Bringup : 1352 times
Shutdown: 1346 times
Power-on: 179day 05hour 39min 57sec

[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:0x21e2
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

According to the error code information, error 3034 is related to the RSX.
It's explained that a "pressure test" could be performed under the chip to check if the console turns on
by applying pressure (although I don't know how this could be done without applying too much force with
something that remains stable while the console turns on).

Since this is the first model of the console, it's most likely a solder problem and requires a reflow or reballing, I don't know.

There's no information about error 4421, it appears to be related to the Cell or the RSX.

If a reflow would work enough time to back up the hard drive, that would be enough for me, but I don't know
if this works for those two errors.

Best regards.
 
YLOD COK002

errlog
ofst[ 12]:err_code:0xffffffff, clock:0x0b633f54 2006/01/20 06:27:32
ofst[ 16]:err_code:0xa0902120, clock:0x0b633f54 2006/01/20 06:27:32
ofst[ 20]:err_code:0xa0404421, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 24]:err_code:0xa0403034, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 28]:err_code:0xa0902120, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 32]:err_code:0xa0404421, clock:0x0b633f5c 2006/01/20 06:27:40
ofst[ 36]:err_code:0xa0403034, clock:0x0b633f5c 2006/01/20 06:27:40
ofst[ 40]:err_code:0xa0404421, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 44]:err_code:0xa0403034, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 48]:err_code:0xa0902120, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 52]:err_code:0xa0404421, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 56]:err_code:0xa0403034, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 60]:err_code:0xa0902120, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 64]:err_code:0xa0404421, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 68]:err_code:0xa0403034, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 72]:err_code:0xa0902120, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 76]:err_code:0xa0404421, clock:0x0b633f6e 2006/01/20 06:27:58
ofst[ 80]:err_code:0xa0403034, clock:0x0b633f6e 2006/01/20 06:27:58
ofst[ 84]:err_code:0xa0404421, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 88]:err_code:0xa0403034, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 92]:err_code:0xa0902120, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 96]:err_code:0xa0404421, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[100]:err_code:0xa0403034, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[104]:err_code:0xa0902120, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[108]:err_code:0xa0404421, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404421, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404421, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0404421, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff


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
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

El_Patas said:
Hello everyone, this is my first experience about this.

PS3 Fat, CECHC04, COOK-002 backwards compatible.

It's my own console, it was never opened or attempted to be repaired, since it had the YLOD many years ago,
I kept it until now, when I opened it for the first time to try to fix it.

Syscon error codes, with becount and bringup:

errlog
ofst[104]:err_code:0xffffffff, clock:0x18a81865 2013/02/08 20:11:17
ofst[108]:err_code:0xa0403034, clock:0x18a81865 2013/02/08 20:11:17
ofst[112]:err_code:0xa0404421, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[116]:err_code:0xa0403034, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[120]:err_code:0xa0404421, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[124]:err_code:0xa0403034, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[ 0]:err_code:0xa0404421, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 4]:err_code:0xa0403034, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 8]:err_code:0xa0404421, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 12]:err_code:0xa0403034, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 16]:err_code:0xa0404421, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 20]:err_code:0xa0403034, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 24]:err_code:0xa0404421, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 28]:err_code:0xa0403034, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 32]:err_code:0xa0404421, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 36]:err_code:0xa0403034, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 40]:err_code:0xa0404421, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 44]:err_code:0xa0403034, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 48]:err_code:0xa0404421, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 52]:err_code:0xa0403034, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 56]:err_code:0xa0404421, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 60]:err_code:0xa0403034, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 64]:err_code:0xa0404421, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 68]:err_code:0xa0403034, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 72]:err_code:0xa0404421, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 76]:err_code:0xa0403034, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 80]:err_code:0xa0404421, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404421, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404421, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff

becount
Bringup : 1352 times
Shutdown: 1346 times
Power-on: 179day 05hour 39min 57sec

[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:0x21e2
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

According to the error code information, error 3034 is related to the RSX.
It's explained that a "pressure test" could be performed under the chip to check if the console turns on
by applying pressure (although I don't know how this could be done without applying too much force with
something that remains stable while the console turns on).

Since this is the first model of the console, it's most likely a solder problem and requires a reflow or reballing, I don't know.

There's no information about error 4421, it appears to be related to the Cell or the RSX.

If a reflow would work enough time to back up the hard drive, that would be enough for me, but I don't know
if this works for those two errors.

Best regards.
Click to expand...
do you find if was RSX DEAD or CPU ?
 
Last edited by a moderator:
El_Patas said:
Hello everyone, this is my first experience about this.

PS3 Fat, CECHC04, COOK-002 backwards compatible.

It's my own console, it was never opened or attempted to be repaired, since it had the YLOD many years ago,
I kept it until now, when I opened it for the first time to try to fix it.

Syscon error codes, with becount and bringup:

errlog
ofst[104]:err_code:0xffffffff, clock:0x18a81865 2013/02/08 20:11:17
ofst[108]:err_code:0xa0403034, clock:0x18a81865 2013/02/08 20:11:17
ofst[112]:err_code:0xa0404421, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[116]:err_code:0xa0403034, clock:0x18a8e8ef 2013/02/09 11:01:03
ofst[120]:err_code:0xa0404421, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[124]:err_code:0xa0403034, clock:0x18aa8d72 2013/02/10 16:55:14
ofst[ 0]:err_code:0xa0404421, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 4]:err_code:0xa0403034, clock:0x18aa8d82 2013/02/10 16:55:30
ofst[ 8]:err_code:0xa0404421, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 12]:err_code:0xa0403034, clock:0x18aa9831 2013/02/10 17:41:05
ofst[ 16]:err_code:0xa0404421, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 20]:err_code:0xa0403034, clock:0x18aab38e 2013/02/10 19:37:50
ofst[ 24]:err_code:0xa0404421, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 28]:err_code:0xa0403034, clock:0x18aab3a3 2013/02/10 19:38:11
ofst[ 32]:err_code:0xa0404421, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 36]:err_code:0xa0403034, clock:0x18abaac8 2013/02/11 13:12:40
ofst[ 40]:err_code:0xa0404421, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 44]:err_code:0xa0403034, clock:0x18ac0352 2013/02/11 19:30:26
ofst[ 48]:err_code:0xa0404421, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 52]:err_code:0xa0403034, clock:0x18ad6f15 2013/02/12 21:22:29
ofst[ 56]:err_code:0xa0404421, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 60]:err_code:0xa0403034, clock:0x18aefdde 2013/02/14 01:43:58
ofst[ 64]:err_code:0xa0404421, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 68]:err_code:0xa0403034, clock:0x18b2941f 2013/02/16 19:01:51
ofst[ 72]:err_code:0xa0404421, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 76]:err_code:0xa0403034, clock:0x18f723e9 2013/04/09 19:09:29
ofst[ 80]:err_code:0xa0404421, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404421, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404421, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff

becount
Bringup : 1352 times
Shutdown: 1346 times
Power-on: 179day 05hour 39min 57sec

[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:0x21e2
Press Ctrl+C to exit
>$
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

According to the error code information, error 3034 is related to the RSX.
It's explained that a "pressure test" could be performed under the chip to check if the console turns on
by applying pressure (although I don't know how this could be done without applying too much force with
something that remains stable while the console turns on).

Since this is the first model of the console, it's most likely a solder problem and requires a reflow or reballing, I don't know.

There's no information about error 4421, it appears to be related to the Cell or the RSX.

If a reflow would work enough time to back up the hard drive, that would be enough for me, but I don't know
if this works for those two errors.

Best regards.
Click to expand...

Those codes mean its the RSX. A reflow might work to get you drive backed up

Fanhais said:
YLOD COK002

errlog
ofst[ 12]:err_code:0xffffffff, clock:0x0b633f54 2006/01/20 06:27:32
ofst[ 16]:err_code:0xa0902120, clock:0x0b633f54 2006/01/20 06:27:32
ofst[ 20]:err_code:0xa0404421, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 24]:err_code:0xa0403034, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 28]:err_code:0xa0902120, clock:0x0b633f58 2006/01/20 06:27:36
ofst[ 32]:err_code:0xa0404421, clock:0x0b633f5c 2006/01/20 06:27:40
ofst[ 36]:err_code:0xa0403034, clock:0x0b633f5c 2006/01/20 06:27:40
ofst[ 40]:err_code:0xa0404421, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 44]:err_code:0xa0403034, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 48]:err_code:0xa0902120, clock:0x0b633f60 2006/01/20 06:27:44
ofst[ 52]:err_code:0xa0404421, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 56]:err_code:0xa0403034, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 60]:err_code:0xa0902120, clock:0x0b633f64 2006/01/20 06:27:48
ofst[ 64]:err_code:0xa0404421, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 68]:err_code:0xa0403034, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 72]:err_code:0xa0902120, clock:0x0b633f69 2006/01/20 06:27:53
ofst[ 76]:err_code:0xa0404421, clock:0x0b633f6e 2006/01/20 06:27:58
ofst[ 80]:err_code:0xa0403034, clock:0x0b633f6e 2006/01/20 06:27:58
ofst[ 84]:err_code:0xa0404421, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 88]:err_code:0xa0403034, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 92]:err_code:0xa0902120, clock:0x0b633f74 2006/01/20 06:28:04
ofst[ 96]:err_code:0xa0404421, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[100]:err_code:0xa0403034, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[104]:err_code:0xa0902120, clock:0x0b633f7c 2006/01/20 06:28:12
ofst[108]:err_code:0xa0404421, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404421, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404421, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0404421, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff


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
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>
[POWERSEQ] Error : BitTraining BE: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Click to expand...


Its the RSX
 
Last edited by a moderator:
Fanhais said:
ok nice at least is RSX if was Cell is more complicated to repair funny is the same error of El Patas what means is the same defect LOL and the same Motherboard
Click to expand...
@Fanhais, just to say that I did a reflow to the RSX and it worked, I turned it off and now I will prepare everything to make a backup of the hard drive, I hope that when I do it it lasts long enough.

Best regards.
 
El_Patas said:
@Fanhais, just to say that I did a reflow to the RSX and it worked, I turned it off and now I will prepare everything to make a backup of the hard drive, I hope that when I do it it lasts long enough.

Best regards.
Click to expand...
o
Nice ok is good to know i will send this console for repair for do an frankenstein here in Portugal
 
Hello guys, I harvested a 40-nm rsx from slim MB, some measurements look a bit low to me, can anyone confirm if this RSX is okay? Want to install it onto COK-001 board
rsx.png

Sorry I don't know how to hide image under a spolier, if moderator sees this - please do)

Anyways, I installed it. At first it had instant YLOD, but turns out for CXD5300CGB you need a EB command, not EC. Also somehow 10 kOhm resistor from that console MB was 6.1 kOhm, I didn't check resistor's value when moved it, and when soldered to a R2054 pad i had a GLOD. I harvested proper 10 kOhm resistor from SEM-001 donor board and console actually started
I hope my measurements and overall experience helps someone :)
 
Last edited by a moderator:
RIP-Felix said:
Originally, the GPU was not passing BitTraining. A calibration procedure that must complete for the system to properly communicate with it. The usualy reason is the soldering connection between the Die and the MB, which passes through 2 solder layers. The bumps and the ball grid array (BGA). Either one can cause those errors. The 90nm RSX (GPU) in your unit is know to have defective materials making the bumps prone to premature failures. And when you heated the console above the 70C Thermal glassification temperature of the underfill that supports the bumps it softened alowing the solder joints to make a microscopic shift in position and reconnect the break. Like touching 2 wires together.

It's not strong and when the strain of that heat dissipates over use and with thermal cycles, it'll fail again. It appears your codes also show CPU voltage regulation failures as well, which usually indicate the NEC/Tokins proadlizers are failing. In this case, I would focus on the GPU issue 1st and then asses the VRM afterwards. The impeedance equation will change after the GPU's connections are restores and the ripple/noise may lesson to the point the tokins are not bad. But TBH, it's likely the tokins are also going bad. I would use an oscilloscope to see, or just replace them cuz they looked at you cross.

Just curious. COK14 is a COK-001, but was this and A or B model?
Click to expand...

yeah so over a year later reply because i forgot about this ps3 xD. No clue if you're still around here or not but the system is an A01 launch model with very low hours actually, i think like 30 days max iirc. i dont have the skills or tools to test further. i used a heatgun once and it worked for a few days then it puked out these codes. tbh its been sitting in my closet since i made this post. frankie mod services are actually reasonable now and im considering having it done especially since your tantilizers mod is really commonplace now. so i checked back here to confirm the codes again.
 
wisi said:
I am getting A0213013 on DIA-001. There were more errors originally. What are the necessary prerequisites for the CELL BE to respond on the SPI bus to the SysCon? On DIA-001, 1.2V_MC2_VDDIO and 1.2V_BE_VCS are both available and the syscon does send /CS, clk and data to the BE, but there is no return data from the BE - BE_SPI_DI keeps high. BE_RESET goes correctly high too. Are any clocks or other supply voltages necessary for the BE to reply on the SPI bus?

Initial errors list (now, it is full of only A0213013):
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0213013 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0902203 FFFFFFFF
ERR 11: 00000000 A0902203 FFFFFFFF
ERR 12: 00000000 A0801200 FFFFFFFF
ERR 13: 00000000 A0801200 FFFFFFFF
ERR 14: 00000000 A0801200 FFFFFFFF
ERR 15: 00000000 A0902203 FFFFFFFF
ERR 16: 00000000 A0801200 FFFFFFFF
ERR 17: 00000000 A0801200 FFFFFFFF
ERR 18: 00000000 A0801200 FFFFFFFF
ERR 19: 00000000 A0801200 FFFFFFFF
Click to expand...
It turned-out this was due to partially-desoldered/lifted CELL BE. So until it is soldered right (if it at all still works and the PCB and substrate are ok) I won't know more about what was wrong with this PS3.


But I have another PS3 to ask about:
SEM-001 - it was originally stopping at 1200 syscon error due to fast overheating CELL BE, but after a delid it does start and reach constant green LED but there is no video. Enabling the syscon internal mode and the additional logs in SB UART, I get this on syscon:
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
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7

powerstate //done after the "update_manager::read_eprom(0x48c42)" line from SB UART
ATA Power : ON
PCI Power : OFF
RSX Power : ON
XDR Power : ON
Eurus Power : ON
SB Power : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor : AVAILABLE

[mullion]$
Click to expand...

and on South Bridge UART, a very long log ending in:
offset = 16
header is not cached
composite_region::allocate_buffer(16)
composite_region::read(0x0, 16, 0xa0007380)
composite_region::release_buffer(0xa0007380)
entry is not cached
composite_region::allocate_buffer(432)
composite_region::read(0x10, 432, 0xa0009b80)
composite_region::release_buffer(0xa0009b80)
composite_region::read(0x40600, 16, 0xfffff550)
composite_region::read(0x40610, 96, 0xa0009b80)
composite_region::read(0x40670, 2144, 0xa0009280)
lv2(2): entering stand-alone mode.
lv2(2): system software: PS3 console mode (game memsize=200MB)
lv2(2): creating the system software process : OK
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.
update_manager::read_eprom(0x48c42)
Click to expand...
It seems to stay in the above state for a long time. I don't have a well-cooled enough heatsink to let it run more than 30-50 sec, to see if it will display anything else. I could use the original heatsinks and fan if necessary. The above displays with or without its HDD. The optical drive is not connected. The wireless/bluetooth board is also not connected.

Also the RB4002 SW_PCI from SYSCON stays always low. I don't know if this is normal.
Errors:
errlog
ofst[ 60]:err_code:0xffffffff, clock:0x0b490e9e 2005/12/31 09:40:46
ofst[ 64]:err_code:0xa0002030, clock:0x0b490ea1 2005/12/31 09:40:49
ofst[ 68]:err_code:0xa0801200, clock:0x0b491024 2005/12/31 09:47:16
ofst[ 72]:err_code:0xa0002030, clock:0x0b491027 2005/12/31 09:47:19
ofst[ 76]:err_code:0xa0801200, clock:0x0b4913aa 2005/12/31 10:02:18
ofst[ 80]:err_code:0xa0902203, clock:0x0b4913aa 2005/12/31 10:02:18
ofst[ 84]:err_code:0xa0002030, clock:0x0b4913ae 2005/12/31 10:02:22
ofst[ 88]:err_code:0xa0801701, clock:0x0b4914b1 2005/12/31 10:06:41
ofst[ 92]:err_code:0xa0801001, clock:0x0b4914b1 2005/12/31 10:06:41
ofst[ 96]:err_code:0xa0801103, clock:0x0b4914c3 2005/12/31 10:06:59
ofst[100]:err_code:0xa0801103, clock:0x0b4917ca 2005/12/31 10:19:54
ofst[104]:err_code:0xa0801103, clock:0x0b4919e2 2005/12/31 10:28:50
ofst[108]:err_code:0xa0801200, clock:0x0b492515 2005/12/31 11:16:37
ofst[112]:err_code:0xa0801200, clock:0x0b49259b 2005/12/31 11:18:51
ofst[116]:err_code:0xa0801200, clock:0x0b492729 2005/12/31 11:25:29
ofst[120]:err_code:0xa0801200, clock:0x0b492975 2005/12/31 11:35:17
ofst[124]:err_code:0xa0801200, clock:0x0b49298a 2005/12/31 11:35:38
ofst[ 0]:err_code:0xa0801200, clock:0x0b49299d 2005/12/31 11:35:57
ofst[ 4]:err_code:0xa0801200, clock:0x0b4929a8 2005/12/31 11:36:08
ofst[ 8]:err_code:0xa0801200, clock:0x0b4929ae 2005/12/31 11:36:14
ofst[ 12]:err_code:0xa0801200, clock:0x0b4929b4 2005/12/31 11:36:20
ofst[ 16]:err_code:0xa0801200, clock:0x0b488682 2005/12/31 00:00:02
ofst[ 20]:err_code:0xa0801001, clock:0xffffffff
ofst[ 24]:err_code:0xa0801200, clock:0x0b488681 2005/12/31 00:00:01
ofst[ 28]:err_code:0xa0801200, clock:0x0b489bd5 2005/12/31 01:31:01
ofst[ 32]:err_code:0xa0801701, clock:0x0b48b105 2005/12/31 03:01:25
ofst[ 36]:err_code:0xa08014ff, clock:0x0b48b105 2005/12/31 03:01:25
ofst[ 40]:err_code:0xa0801001, clock:0x0b48b105 2005/12/31 03:01:25
ofst[ 44]:err_code:0xa0801001, clock:0x0b48b2dc 2005/12/31 03:09:16
ofst[ 48]:err_code:0xa08014ff, clock:0x0b48b420 2005/12/31 03:14:40
ofst[ 52]:err_code:0xa0801001, clock:0x0b48b420 2005/12/31 03:14:40
ofst[ 56]:err_code:0xa0801001, clock:0x0b48baef 2005/12/31 03:43:43
[mullion]$
I think the most recent errors at the bottom are from before the most recent runs because this was the error log before those runs (most recent at the top):

ERR 00: 00000000 A0801001 0B48BAEF
ERR 01: 00000000 A0801001 0B48B420
ERR 02: 00000000 A08014FF 0B48B420
ERR 03: 00000000 A0801001 0B48B2DC
ERR 04: 00000000 A0801001 0B48B105
ERR 05: 00000000 A08014FF 0B48B105
ERR 06: 00000000 A0801701 0B48B105
ERR 07: 00000000 A0801200 0B489BD5
ERR 08: 00000000 A0801200 0B488681
ERR 09: 00000000 A0801001 FFFFFFFF
ERR 10: 00000000 A0801200 0B492975
ERR 11: 00000000 A0801200 0B492729
ERR 12: 00000000 A0801200 0B49259B
ERR 13: 00000000 A0801200 0B492515
ERR 14: 00000000 A0801103 0B4919E2
ERR 15: 00000000 A0801103 0B4917CA
ERR 16: 00000000 A0801103 0B4914C3
ERR 17: 00000000 A0801001 0B4914B1
ERR 18: 00000000 A0801701 0B4914B1
ERR 19: 00000000 A0002030 0B4913AE
 
Bought a refurbished CECHA00 with 40nm RSX in decent price.
It has one problem though, when I turn it off, it beep 3 times and give me A0901001, only when I turn it off, the baby hasn't shut down by itself yet.

should I be worried of it and send the console back to seller who offer paid service, ask him to change capacitor of Cell? Seller said he had swapped all the NEC TOKIN with tantilizers but I haven't been able to open the console to confirm it by myself.

Here's the latest error log, it used to come with A0802120*10. BTW is there a way to correct the timestamp?

Error Log
01: A0901001 Thu Jan 12 05:59:13 2006
02: A0901001 Wed Jan 11 22:23:47 2006
03: A0901001 Tue Jan 10 20:41:54 2006
04: A0901001 Tue Jan 10 20:41:11 2006
05: A0901001 Tue Jan 10 15:37:31 2006
06: A0901001 Tue Jan 10 09:19:01 2006
07: A0802120 Tue Jan 10 01:00:53 2006
08: A0802120 Tue Jan 10 01:00:52 2006
09: A0802120 Tue Jan 10 01:00:51 2006
10: A0802120 Tue Jan 10 01:00:50 2006
11: A0802120 Tue Jan 10 01:00:50 2006
12: A0802120 Tue Jan 10 01:00:49 2006
13: A0802120 Tue Jan 10 01:00:48 2006
14: A0802120 Tue Jan 10 01:00:47 2006
15: A0802120 Tue Jan 10 01:00:46 2006
16: A0802120 Tue Jan 10 01:00:45 2006
17: A0801001 Tue Jan 10 01:00:44 2006
18: A0901001 Tue Jan 10 00:58:34 2006
19: A0802120 Tue Jan 10 00:53:45 2006
20: A0802120 Tue Jan 10 00:53:44 2006
21: A0802120 Tue Jan 10 00:53:43 2006
22: A0802120 Tue Jan 10 00:53:42 2006
23: A0802120 Tue Jan 10 00:53:41 2006
24: A0802120 Tue Jan 10 00:53:40 2006
25: A0802120 Tue Jan 10 00:53:40 2006
26: A0802120 Tue Jan 10 00:53:39 2006
27: A0802120 Tue Jan 10 00:53:38 2006
28: A0802120 Tue Jan 10 00:53:37 2006
29: A0801001 Tue Jan 10 00:53:36 2006
30: A0802120 Tue Jan 10 00:41:27 2006
31: A0802120 Tue Jan 10 00:41:26 2006
32: FFFFFFFF Tue Jan 10 00:41:25 2006
 
Last edited:
dumbass370 said:
Hello guys, I harvested a 40-nm rsx from slim MB, some measurements look a bit low to me, can anyone confirm if this RSX is okay? Want to install it onto COK-001 board
View attachment 45936
Sorry I don't know how to hide image under a spolier, if moderator sees this - please do)
Click to expand...

In my notes I only have the 90nm one and the difference was:
+1.2v_YC_RC_VDDIO: between 12.8 Ohm and 13.1 Ohm
+1.5v_RSX_VDDIO: between 43.2 Ohm and 44.9 Ohm
+1.8V_RSX_PLL_VDD: between 4.0K and 4.7k ohm
+1.8V_RSX_FBVDDQ: between 87.6 Ohm and 114.8 Ohm
Wouldn't +1.5V_RSX_RC_VDDA be the +1.5V_YC_RC_VDDA? If so, here it gave 4.3 Ohm
* all measurements were made with the RSX (90nm) soldered on the board (Cok-001/002)
 
I tried swapping the RSX on a VER-001 to the 40nm one but I'm getting errors 3034 and 4002. I've already patched the SYSCON with both the EB and EC commands, but still no luck. Do you guys have any ideas?

Code: 
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.

Press Ctrl+C to exit
>$
F0000003
# [SSM] PS2 ok.
# [PowSeq] Error:9103
# [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
>$ errlog
00000000
# CODE     CLOCK
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404422 FFFFFFFF
# A0403034 FFFFFFFF
# A0404422 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802131 0B49D823
# A0802131 10EBB419
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
 
Hello, I successfully replaced the caps of my phat model, and after a few seconds of turning it on, it turns off because of overheating. I don't think it's the CPU/GPU, since it is just really really quick. If I stick my PS3 to the AC, it takes longer to die, so I suspect it might have something to do with me missing a couple thermal pads on some components. I havent yet disassembled the console to check the new syscon errors, but if anyone happens to have a guide or chart or anything about where I should place new pads (and which size they should be), I'd really appreciate it :)
 
AFAIK the temp sensors are in CPU and GPU. You can check via syscon.

If it wasn't doing that before, check your assembly. You put thermal paste on the IHS right? When you remove the heatsink, check if the paste spread properly.

It could also be the paste UNDER the IHS, I had one myself, it would overheat within 2-3 seconds. If that is the case, you have to de-lid.
 
superprokill1 said:
Hello, I successfully replaced the caps of my phat model, and after a few seconds of turning it on, it turns off because of overheating. I don't think it's the CPU/GPU, since it is just really really quick. If I stick my PS3 to the AC, it takes longer to die, so I suspect it might have something to do with me missing a couple thermal pads on some components. I havent yet disassembled the console to check the new syscon errors, but if anyone happens to have a guide or chart or anything about where I should place new pads (and which size they should be), I'd really appreciate it :)
Click to expand...
Before it turns off does the fan goes turbo mode?
A couple of thermal pads usually won't overheat that quickly. Those are on the buck converter ICs and/or inductors. Unless you haven't properly repaste the heatsink or forget to install the bracket.
If your AC can allow the PS3 run a significant longer time, install CFW and check the syscon error code there.
 
superprokill1 said:
Hello, I successfully replaced the caps of my phat model, and after a few seconds of turning it on, it turns off because of overheating. I don't think it's the CPU/GPU, since it is just really really quick. If I stick my PS3 to the AC, it takes longer to die, so I suspect it might have something to do with me missing a couple thermal pads on some components. I havent yet disassembled the console to check the new syscon errors, but if anyone happens to have a guide or chart or anything about where I should place new pads (and which size they should be), I'd really appreciate it :)
Click to expand...

Did you delid the CELL?
 
You must log in or register to reply here.

Similar threads

Back
Top