PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
RIP-Felix
Senior Member
2130/31 is an elivated seriousness of 2030/31. Same error, more serious. Like occure sooner in the power on sequence.
In 25xx and later models it can be caused by a failing DCDC converter on the wifi/blutooth module. This is a common fault with these models. It makes them less reliable than the 20xx and 21xx models that preceeded them.
Since the 21xx has a 40nm RSX, but doesn't suffer from this issue, it's considered the most reliable PS3 ever made. 20xx has the 65nm RSX and tokins that tend to fail.
In 25xx and later models it can be caused by a failing DCDC converter on the wifi/blutooth module. This is a common fault with these models. It makes them less reliable than the 20xx and 21xx models that preceeded them.
Since the 21xx has a 40nm RSX, but doesn't suffer from this issue, it's considered the most reliable PS3 ever made. 20xx has the 65nm RSX and tokins that tend to fail.
Raidmax
Member
Noted. I suppose I'll run it for a bit longer and see what gives up first then. It seems a bit strange, since the fan and thermals seem to run normally (no anomaly detected so far) and the WiFi/BT side seems to work as well - basically the unit shows no signs of weirdness, so the log does come off a bit strange to me given all it had was lots of dust and dried paste (and a missing HDD flap lol). I had taken extra care not to rip its RSX when removing the heatsinks.
As for the other unit I had gotten along it, a 2003B, it seems to run fine as well. In its case, only 3x 1200 error codes were generated and the rest of the log is empty. I fully know what caused these 1200s... my cheap azz thought that a spare CECH-3000 top case would work on a 2000 - I somehow managed to obstruct the fan from running by using the 3000 top shell. I quickly swapped a 2500 shell the following morning after I found out the fan wasn't spinning, and so far it has been running fine - aside from the firmware installation taking absolutely unusually long.
(2500 took me short of 20-25 minutes, the 2000 took almost an entire hour to get past the firmware check and HDD format no matter what HDD I used. Once it went to the firmware's install screen (the one with a static wave) it ran smoothly.)
As for the other unit I had gotten along it, a 2003B, it seems to run fine as well. In its case, only 3x 1200 error codes were generated and the rest of the log is empty. I fully know what caused these 1200s... my cheap azz thought that a spare CECH-3000 top case would work on a 2000 - I somehow managed to obstruct the fan from running by using the 3000 top shell. I quickly swapped a 2500 shell the following morning after I found out the fan wasn't spinning, and so far it has been running fine - aside from the firmware installation taking absolutely unusually long.
(2500 took me short of 20-25 minutes, the 2000 took almost an entire hour to get past the firmware check and HDD format no matter what HDD I used. Once it went to the firmware's install screen (the one with a static wave) it ran smoothly.)
Last edited:
sin89rus
Member
thanks
>$ eepcsum
00000000
# csum = 0x2958
----------
fixed by
w 7fe 58 29
-----------
If dump eeprom form syscon 2.5k model and write it to 2k model syscon, will it work? Or EEPROM contains info about power sequences etc?
I cant find info about "can i just write CELL keys and other keys from one to another syscon" like only keys from another board model, not power sequence etc.
Simple: keep original SYCON on 2k board, take and solder CELL and NOR from 2.5k board, write KEYS info from 2.5k board Syscon to 2k board original Syscon.
Or its a bad idea?
Hi all, I am new to the scene and I accidentally received a YLOD ps3 from a friend and thought I would attempt a fix on it. It's a CECHC-03 model with backward compatibility and this is the logs of the syscons I pulled out from the PS3 initially:
Note: I tried to boot on when I just got it, so it could assume that ERR 00-03 are made by me and 04 onward are the past logs.
And then I took apart the console and done the pressure test on RSX, it either gets a 0xa0801701 or a combined 0xa0404432 + 0xa0403034. Here are the full logs:
1701:
4432 + 3034:
And without the pressure, it gives a steady 2102:
Any suggestions on the potential fixes?
Code:
===================================
ERR 00: 00000000 A0232102 FFFFFFFF
ERR 01: 00000000 A0403034 FFFFFFFF
ERR 02: 00000000 A0404002 FFFFFFFF
ERR 03: 00000000 A0801701 FFFFFFFF
ERR 04: 00000000 A0801701 FFFFFFFF
ERR 05: 00000000 A0801701 FFFFFFFF
ERR 06: 00000000 A0801701 FFFFFFFF
ERR 07: 00000000 A0801701 FFFFFFFF
ERR 08: 00000000 A0801701 FFFFFFFF
ERR 09: 00000000 A0801701 FFFFFFFF
ERR 10: 00000000 A0801701 FFFFFFFF
ERR 11: 00000000 A0801701 FFFFFFFF
ERR 12: 00000000 A0801701 FFFFFFFF
ERR 13: 00000000 A0801701 FFFFFFFF
ERR 14: 00000000 A0093003 FFFFFFFF
ERR 15: 00000000 A0093003 FFFFFFFF
ERR 16: 00000000 A0093003 FFFFFFFF
ERR 17: 00000000 A0093003 FFFFFFFF
ERR 18: 00000000 A0093003 FFFFFFFF
ERR 19: 00000000 A0093003 FFFFFFFF
===================================And then I took apart the console and done the pressure test on RSX, it either gets a 0xa0801701 or a combined 0xa0404432 + 0xa0403034. Here are the full logs:
1701:
Code:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SSM] Attention BE : Detected !
[SSM] BE Attention signal is detected !!
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801701
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)4432 + 3034:
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 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3: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]: 0xa0404432
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)And without the pressure, it gives a steady 2102:
Code:
>$ 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
Press Ctrl+C to exit
>$
[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)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)Any suggestions on the potential fixes?
FastZander101
Forum Noob
Hello, I have a CECHE01 MG and just performed a syscon error log scan. YLOD of death. Motherboard looks fine besides some bubbling on old thermal pads. Any help would be very appreciated.
Here is the the code:
Here is the the code:
Code:
eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x5555
sum:0x0100
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
w 39fe 38 00
w complete!
[mullion]$
errlog
ofst[ 24]:err_code:0xffffffff, clock:0x20420c9f 2017/02/23 21:11:59
ofst[ 28]:err_code:0xa0404411, clock:0x20420cde 2017/02/23 21:13:02
ofst[ 32]:err_code:0xa0403034, clock:0x20420cde 2017/02/23 21:13:02
ofst[ 36]:err_code:0xa0404411, clock:0x20420d5a 2017/02/23 21:15:06
ofst[ 40]:err_code:0xa0403034, clock:0x20420d5a 2017/02/23 21:15:06
ofst[ 44]:err_code:0xa0404411, clock:0x20420e01 2017/02/23 21:17:53
ofst[ 48]:err_code:0xa0403034, clock:0x20420e01 2017/02/23 21:17:53
ofst[ 52]:err_code:0xa0404411, clock:0x20420e3a 2017/02/23 21:18:50
ofst[ 56]:err_code:0xa0403034, clock:0x20420e3a 2017/02/23 21:18:50
ofst[ 60]:err_code:0xa0404411, clock:0x20420eb5 2017/02/23 21:20:53
ofst[ 64]:err_code:0xa0403034, clock:0x20420eb5 2017/02/23 21:20:53
ofst[ 68]:err_code:0xa0404411, clock:0x20420ec1 2017/02/23 21:21:05
ofst[ 72]:err_code:0xa0403034, clock:0x20420ec1 2017/02/23 21:21:05
ofst[ 76]:err_code:0xa0404411, clock:0x20420ecd 2017/02/23 21:21:17
ofst[ 80]:err_code:0xa0403034, clock:0x20420ecd 2017/02/23 21:21:17
ofst[ 84]:err_code:0xa0404411, clock:0x20420f1c 2017/02/23 21:22:36
ofst[ 88]:err_code:0xa0403034, clock:0x20420f1c 2017/02/23 21:22:36
ofst[ 92]:err_code:0xa0404411, clock:0x20420f24 2017/02/23 21:22:44
ofst[ 96]:err_code:0xa0403034, clock:0x20420f24 2017/02/23 21:22:44
ofst[100]:err_code:0xa0404411, clock:0x20420f32 2017/02/23 21:22:58
ofst[104]:err_code:0xa0403034, clock:0x20420f32 2017/02/23 21:22:58
ofst[108]:err_code:0xa0404411, clock:0x20420f42 2017/02/23 21:23:14
ofst[112]:err_code:0xa0403034, clock:0x20420f42 2017/02/23 21:23:14
ofst[116]:err_code:0xa0404411, clock:0x20420f5b 2017/02/23 21:23:39
ofst[120]:err_code:0xa0403034, clock:0x20420f5b 2017/02/23 21:23:39
ofst[124]:err_code:0xa0404411, clock:0x2042124b 2017/02/23 21:36:11
ofst[ 0]:err_code:0xa0403034, clock:0x2042124b 2017/02/23 21:36:11
ofst[ 4]:err_code:0xa0404411, clock:0x20421250 2017/02/23 21:36:16
ofst[ 8]:err_code:0xa0403034, clock:0x20421250 2017/02/23 21:36:16
ofst[ 12]:err_code:0xa0404411, clock:0x2042126b 2017/02/23 21:36:43
ofst[ 16]:err_code:0xa0403034, clock:0x2042126b 2017/02/23 21:36:43
ofst[ 20]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
becount
Bringup : 1629 times
Shutdown: 1557 times
Power-on: 243day 00hour 11min 59sec
[mullion]$
bringup
Do nothing. (FatalOff State)
tmp 00
*** Inaccurate Temperature:0.00(0x0000) ***
[mullion]$
tmp 01
*** Inaccurate Temperature:0.00(0x0000) ***
[mullion]$
DeadEnd
Senior Member
Indeed. So many folks here posting 3034 errors and asking what's the fix. How is this not common knowledge yet?
Raidmax
Member
Because of the snake oil that "reflows fix anything" that's been existing since the Geforce 8 days (actually, scratch that, I've been seeing chumps reflow cards as old as Geforce 6.), which has rooted itself so deep into people's brains that they manage to think a reflow will keep anything with a underfill defect for days on end.
As someone who blindly used to do that during the late 2010s(reflowing GF8 cards en masse) - very little chips manage to keep themselves alive for so long. The longest I have personally recorded was 8 years for a 90nm RSX inside a long-since-sold CECHC03 (which was sold for pretty cheap before the backwards compatibility mass purchase craze) and a Geforce 8400M GS that somehow still runs to this day inside a HP Pavilion dv6700, though I haven't powered that laptop on again for nearly 4-5 years already.
That being said - to anyone who comes across and reads this - DO NOT ATTEMPT REFLOWING PS3S OR ANY BUMPGATE RIDDEN BGA CHIP NO MATTER WHAT IT IS (GEFORCE 8, ATI X1900, PS3 RSX, XBOX 360 GPU, ANYTHING WITH A BAD UNDERFILL MATERIAL) - IT WON'T LAST FOR LONG AND YOU'RE WASTING YOUR TIME DRINKING SNAKE OIL THINKING THE UNDERFILL WILL KEEP ITSELF ALIVE ANY LONGER!
I'm forced to put this warning because people likely won't read any warnings until they're absolutely popping out in yer' eyes. My experience was just a happy case scenario (and probably a bit of silicon lottery too, but I'm not sure), and should NOT be followed.
And since it was mentioned somewhere else in these specific threads (either this one, or the tantalum replacing research thread.) - NO, A REFLOW WILL NOT HELP IN BACKING UP SAVES!!!!!
I've personally had TWO CECHG04 units that have been reflowed to fail DURING a backup through FTP, so reflowing to backup data IS NOT AN OPTION EITHER.
Learn to use Linux and @Berion 's guide on mounting and accessing your PS3 HDD from a PC to get your valuable data off the HDD. Like or hate it, Linux NEEDS to be a part of your PS3 tools at all costs.
As someone who blindly used to do that during the late 2010s(reflowing GF8 cards en masse) - very little chips manage to keep themselves alive for so long. The longest I have personally recorded was 8 years for a 90nm RSX inside a long-since-sold CECHC03 (which was sold for pretty cheap before the backwards compatibility mass purchase craze) and a Geforce 8400M GS that somehow still runs to this day inside a HP Pavilion dv6700, though I haven't powered that laptop on again for nearly 4-5 years already.
That being said - to anyone who comes across and reads this - DO NOT ATTEMPT REFLOWING PS3S OR ANY BUMPGATE RIDDEN BGA CHIP NO MATTER WHAT IT IS (GEFORCE 8, ATI X1900, PS3 RSX, XBOX 360 GPU, ANYTHING WITH A BAD UNDERFILL MATERIAL) - IT WON'T LAST FOR LONG AND YOU'RE WASTING YOUR TIME DRINKING SNAKE OIL THINKING THE UNDERFILL WILL KEEP ITSELF ALIVE ANY LONGER!
I'm forced to put this warning because people likely won't read any warnings until they're absolutely popping out in yer' eyes. My experience was just a happy case scenario (and probably a bit of silicon lottery too, but I'm not sure), and should NOT be followed.
And since it was mentioned somewhere else in these specific threads (either this one, or the tantalum replacing research thread.) - NO, A REFLOW WILL NOT HELP IN BACKING UP SAVES!!!!!
I've personally had TWO CECHG04 units that have been reflowed to fail DURING a backup through FTP, so reflowing to backup data IS NOT AN OPTION EITHER.
Learn to use Linux and @Berion 's guide on mounting and accessing your PS3 HDD from a PC to get your valuable data off the HDD. Like or hate it, Linux NEEDS to be a part of your PS3 tools at all costs.
RIP-Felix
Senior Member
Bad GPU. Needs replaced. This is difficult and expensive.
Bad GPU. Again, this is the most common cause of YLOD on these Bacakwards compatible models, due to a defective 90nm GPU.
RIP-Felix
Senior Member
Blanket statements like this do annoy me. For the convenience of reducing complexity to simplicity, they ignore nuance. Like junk food, it tastes good but has no value.
There are circumstances where a reflow is useful. Like after a reball and incomplete reflow. The balls are nice and fresh. Haven't had time to get caked in dust and grime that would contaminate the BGA. If the BGA crak is fresh, like after a deliding attempt or when separating the IHS from the HS while changing paste, there hasn't been enough time for the crack or sherared pad to oxidize and get gunked up. In this circumstance, a refow can last if the board is thoroughly cleaned 1st (ultrasonic cleaning). A reball in that circumstance is more advisable however, since it's easier to ensure the BGA is clean when you have access to it. And you can reball with eutectic lead alloy instead of the leaf free SAC-305 sony used.
But your point is that most people are using heatgun specials. And that is not repair.
A heat test, not to be confused with a reflow, can be used to retrieve saves. I'm not saying it will 100% work, or 100% not work. Except for this one, all or nothing statements are never true. IME a heat test often allows the console to start and while it's on, it usually will stay on. In the early stages at least. It is a time honored way to get your saves off a failing, but not yet completely failed console. It usually doesn't just occur out of the blue. There's usually some lead up to the full on 3034 that won't let you boot no matter how many times you attempt to turn it on.
FastZander101
Forum Noob
Is there anyway an average joe can fix this, or am I screwed and should just try to sell my broken console on ebay? I have a replacement GPU from a friends phat non backwards compatible ps3 that I can take out but I don't know if I have the equipment to perform a transplant.
Raidmax
Member
Not to be done by an average Joe. You need BGA rework tools, BGA rework experience, SMD soldering tools and experience as well as Linux experience is recommended.
Last edited:
RIP-Felix
Senior Member
You'd know if you had the right equipment. Afraid this is one of the highest levels of difficulty.
superprokill1
Member
@RIP-Felix Mentioning you suggested I bought ceramic caps as well for my model, could it be that I need to solder the small ceramic caps (MLCC iirc?) for it to boot? I was assuming I could do a test powerup without them just to see if I was doing something wrong and then install them, but I am honestly running out of ideas
Hi guys,
I recently bought a Ps3 C cheap on ebay with YLOD. The warranty seal was intact and I have found no other signs that the console has been opened before. When I test it, it sometimes has GLOD and sometimes YLOD. So I read the syscon and only get 1001 and 1002 errors. So according to the syscon they are defective nec tokins if I'm not mistaken. But why does the console sometimes have a GLOD? This is only triggered by a defective RSX, isn't it? Would you say it's worth replacing the NEC tokens? Since I get 1001 and 1002 I assume that I would have to replace all of them and that would be quite a lot of work just to find out that the GLOD is caused by a defective RSX so I wanted to ask beforehand.
I recently bought a Ps3 C cheap on ebay with YLOD. The warranty seal was intact and I have found no other signs that the console has been opened before. When I test it, it sometimes has GLOD and sometimes YLOD. So I read the syscon and only get 1001 and 1002 errors. So according to the syscon they are defective nec tokins if I'm not mistaken. But why does the console sometimes have a GLOD? This is only triggered by a defective RSX, isn't it? Would you say it's worth replacing the NEC tokens? Since I get 1001 and 1002 I assume that I would have to replace all of them and that would be quite a lot of work just to find out that the GLOD is caused by a defective RSX so I wanted to ask beforehand.
Similar threads
-
-
PS3 CECHA00 with several SYSCON errors (3004, 1001,1002, 2120,3011)
- Started by LSL
- Replies: 7
-
PS3 Interesting PS3 Errors (1802, 1701, 1601) and Capacitor Replacement- Started by Cheshire UK
- Replies: 2
-