PS3 Syscon errors A0403034 A0404002 A0902120

xanadu247

xanadu247

Member
Hi to all! Some of you may know me. Im known for my self powering teensy 2.0 guide referenced in judges github. Glad to see this forum now has a hardware section and that members ive known in the past are active here!

Ive been focusing on binned ps3s lately that unfortunately were failed repairs and lacked this current syscon reading element. Would have been great to have this years ago, as needless reflows and reballs were the main repair.

As this is syscon reading is relatively new to me, i wouldnt mind some input from those more experienced at it.

The current console i have on my workbench is a cok-002 that was reflowed unsuccessfully in the past.

first syscon read revealed alternating A0403034 A0404002
===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404002 FFFFFFFF
ERR 02: 00000000 A0403034 FFFFFFFF
ERR 03: 00000000 A0404002 FFFFFFFF
ERR 04: 00000000 A0403034 FFFFFFFF
ERR 05: 00000000 A0404002 FFFFFFFF
ERR 06: 00000000 A0403034 FFFFFFFF
ERR 07: 00000000 A0404002 FFFFFFFF
ERR 08: 00000000 A0403034 FFFFFFFF
ERR 09: 00000000 A0404002 FFFFFFFF
ERR 10: 00000000 A0403034 FFFFFFFF
ERR 11: 00000000 A0404002 FFFFFFFF
ERR 12: 00000000 A0403034 FFFFFFFF
ERR 13: 00000000 A0404002 FFFFFFFF
ERR 14: 00000000 A0403034 FFFFFFFF
ERR 15: 00000000 A0404002 FFFFFFFF
ERR 16: 00000000 A0801701 0BE5E6E1
ERR 17: 00000000 A08014FF 0BE5E6E1
ERR 18: 00000000 A0403034 0B99C7BE
ERR 19: 00000000 A0404002 0B99C7BE
===================================

I proceeded to reflow the gpu and encoder. Maybe I should have left the encoder alone in hindsight as it triggered A0902120 error.

===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404002 FFFFFFFF
ERR 02: 00000000 A0403034 FFFFFFFF
ERR 03: 00000000 A0404002 FFFFFFFF
ERR 04: 00000000 A0902120 FFFFFFFF
ERR 05: 00000000 A0403034 FFFFFFFF
ERR 06: 00000000 A0404002 FFFFFFFF
ERR 07: 00000000 A0403034 FFFFFFFF
ERR 08: 00000000 A0404002 FFFFFFFF
ERR 09: 00000000 A0902120 FFFFFFFF
ERR 10: 00000000 A0403034 FFFFFFFF
ERR 11: 00000000 A0404002 FFFFFFFF
ERR 12: 00000000 A0403034 FFFFFFFF
ERR 13: 00000000 A0404002 FFFFFFFF
ERR 14: 00000000 A0403034 FFFFFFFF
ERR 15: 00000000 A0404002 FFFFFFFF
ERR 16: 00000000 A0403034 FFFFFFFF
ERR 17: 00000000 A0404002 FFFFFFFF
ERR 18: 00000000 A0403034 FFFFFFFF
ERR 19: 00000000 A0404002 FFFFFFFF


=================================

I reflowed the encoder and the A0902120 dissappeared.

Here is the final log
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\PentiumD>python c://PS3_Syscon_(Mullion_Sherwood)_script.py com5 CXR
> AUTH
Auth successful
> EEP GET 3961 01
00000000 FF
> EEP SET 3961 01 00
00000000
> EEP GET 3961 01
00000000 00
> exit

C:\Users\PentiumD>python c://PS3_Syscon_(Mullion_Sherwood)_script.py com5 CXRF
> AUTH
Auth successful
> eepcsum
eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
> lasterrlog
lasterrlog
Last Error Code:0xa0403034, Time:0xffffffff
[mullion]$
> errlog
errlog
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0404002, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0404002, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0404002, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0404002, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0404002, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0404002, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0404002, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0404002, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0404002, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404002, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0902120, clock:0xffffffff
ofst[ 88]:err_code:0xa0404002, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404002, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0902120, clock:0xffffffff
ofst[108]:err_code:0xa0404002, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404002, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>
[mullion]$
> eepcsum
eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
> w 39FE 38 00
w 39FE 38 00
w complete!
[mullion]$
> eepcsum
eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
> becount
becount
Bringup : 4142 times
Shutdown: 3915 times
Power-on: 232day 04hour 07min 25sec
[mullion]$
> powersw
powersw
[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
> bringup
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bringup
Do nothing. (FatalOff State)
> powersw
powersw
> powersw
powersw
> powersw
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
powersw
[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
> powerstate
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
powerstate
ATA Power : OFF
PCI Power : OFF
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
> powerstate
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
powerstate
ATA Power : OFF
PCI Power : OFF
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
> 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
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
> bringup
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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
> powerstate
[SSM] state: 0103 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)


whats going on with this console? is gpu culprit or silicon image encoder??? How would you proceed? I can start reballing chips but hate to spend all that time without succcess.

Also, i dont appear to have any shorts in the usual places. Cap around gpu on nec tokin side is 92ohm, cap near gpu other side is 72ohm. No shorts around silicon image encoder.

Thanks for reading and thanks for the input.
 
Last edited:
Hello! Glad to see you here.
3034 /4402 like usual I do reball both. One thing is nek capacitors exchange but can't say without 1002/1001.
Now what resistance do you have on cpu power line and rsx?
I still have your old phone number if you need WhatsApp support.
 
Last edited:
vyktormvmpay25 said:
Hello! Glad to see you here.
3034 /4402 like usual I do reball both. One thing is nek capacitors exchange but can't say without 1002/1001.
Now what resistance do you have on cpu power line and rsx?
I still have your old phone number if you need WhatsApp support.
Click to expand...

Hi Buddy. Number hasnt changed but others may learn from this if we keep the posts here.

I changed all nec caps on opposite side of cpu/ gpu as a preventative measure anyway. I tested each tantalum cap before installing and they were all close to 490uF. They came off a binned ps4 board. I installed 7 caps on gpu (bridged) and 6 on cpu (unbridged). nec caps on cpu side were untouched. The logs above are with the tantalum caps installed.

I get 4.0 ohms between ground and nec caps above cpu and 3.0 ohms for gpu.

Reflow was done with ihs lifted. Cpu and gpu were reflowed back when it was binned. Now just gpu was reflowed as syscon log told me it could be the likely culprit. No delamination appears to have occurred.

Is reballing both chips what you suggest at this point. How successful is all that work going to be. Is it possible it needs a new gpu. Ive heard of those samsung ram chips on the gpu bleeding solder balls from excess heat
, which could be the case with multiple reflows.
 
Yes reball both. You probably have your method by now. If you can use any silicone and let ihs to cure before desolder. I use AG TermoGlue kind of silicone to stick ihs back in order to protect ic's. My station is to strong and can fry those. After desolder rsx can be reballed without ihs but cpu is better handled with ihs so I recommand to reball like that and delid it back and exchange thermal paste on ic die and add new silicone and paste after reball. I know is a pain but for me is only way. When I see 3034/44xx I don't even bother with delid, reball and delid after. Av/Hdmi ic error may come back if they are really there. Or after few days 1002/1001 if caps aren't exchanged. So I do exchange caps while ic's are out of board.
As much as I hate those boards I've started to fix them. Are not so easy as slims but not many ps3 left so doing what is left cheap, not more than 15 euros per unit.
Last resort if rsx really don't want to start you can opt for modchip exchange then one 40nm rsx will test your board. Don't bother to much with his 90nm (looking on good rsx values should work).
This days got another board with 65nm rsx and modchip working and for test purposes.
If you remember years ago there was someone who claimed rsx can be ported from new to old boards. We did not believe that then, well it was true. Even Sony did it.
Read Frankenstein thread and you can have one of my modchip if you think to order, I will ask DeadEnd to send you one for test purposes from my order.
f146e474d2b9e7b6da499b8f3abce6a7.jpg
 
Last edited:
vyktormvmpay25 said:
Yes reball both. You probably have your method by now. If you can use any silicone and let ihs to cure before desolder. I use AG TermoGlue kind of silicone to stick ihs back in order to protect ic's. My station is to strong and can fry those. After desolder rsx can be reballed without ihs but cpu is better handled with ihs so I recommand to reball like that and delid it back and exchange thermal paste on ic die and add new silicone and paste after reball. I know is a pain but for me is only way. When I see 3034/44xx I don't even bother with delid, reball and delid after. Av/Hdmi ic error may come back if they are really there. Or after few days 1002/1001 if caps aren't exchanged. So I do exchange caps while ic's are out of board.
As much as I hate those boards I've started to fix them. Are not so easy as slims but not many ps3 left so doing what is left cheap, not more than 15 euros per unit.
Last resort if rsx really don't want to start you can opt for modchip exchange then one 40nm rsx will test your board. Don't bother to much with his 90nm (looking on good rsx values should work).
This days got another board with 65nm rsx and modchip working and for test purposes.
If you remember years ago there was someone who claimed rsx can be ported from new to old boards. We did not believe that then, well it was true. Even Sony did it.
Read Frankenstein thread and you can have one of my modchip if you think to order, I will ask DeadEnd to send you one for test purposes from my order.
f146e474d2b9e7b6da499b8f3abce6a7.jpg
Click to expand...
Thanks for the advice. If im understanding you properly, you have seen some false positives with the hdmi encoder reporting an error that was actually gpu and or cpu related.

I will start with reballing the gpu and hope for the best but will have to do so when i can free up some more time. Thanks again! Ive got about 30 of these binned ps3s on hand and will slowly start sorting through them to see if a frankenstein candidate exists!
 
I have a PS3 here w/ the same error codes.

I did notice that vyktormvmpay25 may have misread OP's errors. We're getting 3034, 2120 and 4002, but he keeps referring to "3034/44xx".

I'm assuming it's the same reball fix, but I just want to be sure. Can either of you confirm?
 
I can confirm I never managed to fix any of those reball codes when rsx vddc to gnd will show less than 2.5 ohm for 90nm model. Just by reball another newer model of rsx with that Frankenstein modchip working all. Very low chance to find miself one that can be fixed and recover 90nm rsx. I have made many tests around those models and I often fix slims rather then phats. Even slim models jsd /jtp slim models with glod state and 1.8 ohms can't get them fixed, after reball both cpu/rsx same state of glod without any errors on syscon and SB debugging started fine, have about 6 cases, all sorted with rsx exchanged.
I can't say reball will fix everything but at least I'm sure that ic is getting good connection, on reflow I'm not confident.
 
Last edited:
4002 with 3034 is always a dead RSX unless you have just implemented the Frankenstein mod and have not adjusted the Syscon to suit.
The backyard repair attempt has overcooked it!!
 
True, 4002 can come in bumped boards or merged balls near corner were thermal sensor is but in bittraining data line to cell orientation imo.
 
Guys I know long time from last post,Slim here CECH 2503B ON OFF.ERROR CODES:
===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404003 FFFFFFFF
ERR 02: 00000000 A0403034 FFFFFFFF
ERR 03: 00000000 A0404003 FFFFFFFF
ERR 04: 00000000 A0403034 FFFFFFFF
ERR 05: 00000000 A0404003 FFFFFFFF
ERR 06: 00000000 A0403034 FFFFFFFF
ERR 07: 00000000 A0404003 FFFFFFFF
ERR 08: 00000000 A0403034 FFFFFFFF
ERR 09: 00000000 A0404003 FFFFFFFF
ERR 10: 00000000 A0403034 FFFFFFFF
ERR 11: 00000000 A0404003 FFFFFFFF
ERR 12: 00000000 A0403034 FFFFFFFF
ERR 13: 00000000 A0404003 FFFFFFFF
ERR 14: 00000000 A0403034 FFFFFFFF
ERR 15: 00000000 A0404003 FFFFFFFF
ERR 16: 00000000 A0403034 FFFFFFFF
ERR 17: 00000000 A0404003 FFFFFFFF
ERR 18: 00000000 A0403034 FFFFFFFF
ERR 19: 00000000 A0404003 FFFFFFFF
===================================
RSX dead ?Thx.
 
You must log in or register to reply here.

Similar threads

Back
Top