RIP-Felix
Senior Member
Tokins are the most likely diagnosis. I have since confirmed the 65nm RSX is not affected by bumpgate. At least not the bad underfill. And if there is a lacking polyamide stress layer, it doesn't appear to cause premature failure. So you'll be fine.Hey guys, I have a PS3 Slim CECH-2004B that over the course of I'd say 2 months started showing the usual symptoms, sudden shutoffs after the console was on for a bit, that I thought were overheating at first, then I thought I'd found a way to mitigate them by first playing a less demanding game for a bit to "warm up" the console then jumped on a more demanding game and it worked for a while then eventually it started happening more and more, the "warm up" wasn't working and eventually I got into the red blinking light state every time I tried powering on the PS3, after about 5 seconds.
This was all in 2019 I believe. After the immediate shutoffs started happening I left the console alone for a long time thinking that it was dead. When RIPFelix posted his YLOD history video in September 2022, it got to my recommended pretty early on (it had something like 4k views) and I was obsessed for a while with the issue, especially the bumpgate issue cut off which made me almost certain that my 65nm RSX kicked the can because the manfacturing dates lined up.
After this, I went back to the attic and tried turning the PS3 on. Sure enough, the same symptoms ocurred but I kept trying. I sat it on its side, I held it upside down, and then eventually sat it on its topside, in a frustrated attempt to get a boot. To my absolute shock it actually booted into the XMB and I left it alone for like 10 minutes to see if it would stick. Came back, it was still on. I used webman to check temps and a bunch of other stuff and it seemed like the console was on fine. I didn't play any games and I was sure that as soon as I turned it off it wouldn't turn back on again, and that's exactly what happened. Defeated, I put it back in the attic and it remained there for a few more months.
So when I found out about the SYSCON method, I got into soldering. Fixed some other stuff, like cables and controllers first and then opened my PS3 up for the second time ever. I soldered the RX and TX leads and sure enough I got my SYSCON codes:
Microsoft Windows [Version 10.0.22000.1696]
(c) Microsoft Corporation. All rights reserved.
C:\Users\roliveira\Downloads\PS3-main\Syscon Connection Drivers and Diagrams ByNSC>python "PS3_Syscon_(Mullion_Sherwood)_script.py" COM4 SW
> AUTH
Auth successful
> ERRLOG
00000000
# CODE CLOCK
# A0801002 15A8FF8E
# A0801002 15A8FF74
# A0801002 15A8FF5F
# A0801002 15A8FF3A
# A0801002 15A8FF29
# A0801002 15A8FF16
# A0801002 15A8FF01
# A0801002 15A8FEEC
# A0801002 14082CF6
# A0801002 14082CD2
# A0801002 14082CC2
# A0801002 14082CB5
# A0801002 14082CA1
# A0801002 14082C6E
# A0801002 14082C5D
# A0801002 14082C47
# A0801002 14082C2A
# A0801002 134A616D
# A0802022 134A613B
# A0802022 134A6139
# A0801002 134A5B9B
# A0801002 134A5AED
# A0801002 134A5665
# A0801002 134A5639
# A0801002 134A5620
# A0801002 134A53BD
# A0801002 134A530E
# A0801002 134A529D
# A0801002 134A5260
# A0801002 133D3BC4
# A0801002 133D3BB2
> ERRLOG GET 00
00000000 A0801002 15A8FF8E
> ERRLOG GET 01
00000000 A0801002 15A8FF74
> ERRLOG GET 02
00000000 A0801002 15A8FF5F
> ERRLOG GET 03
00000000 A0801002 15A8FF3A
> ERRLOG GET 04
00000000 A0801002 15A8FF29
> ERRLOG GET 05
00000000 A0801002 15A8FF16
> ERRLOG GET 06
00000000 A0801002 15A8FF01
> ERRLOG GET 07
00000000 A0801002 15A8FEEC
> ERRLOG GET 08
00000000 A0801002 14082CF6
> ERRLOG GET 09
00000000 A0801002 14082CD2
> ERRLOG GET 0A
00000000 A0801002 14082CC2
> ERRLOG GET 0B
00000000 A0801002 14082CB5
> ERRLOG GET 0C
00000000 A0801002 14082CA1
> ERRLOG GET 0D
00000000 A0801002 14082C6E
> ERRLOG GET 0E
00000000 A0801002 14082C5D
> ERRLOG GET 0F
00000000 A0801002 14082C47
> ERRLOG GET 10
00000000 A0801002 14082C2A
> ERRLOG GET 11
00000000 A0801002 134A616D
> ERRLOG GET 12
00000000 A0802022 134A613B
> ERRLOG GET 13
00000000 A0802022 134A6139
> ERRLOG GET 14
00000000 A0801002 134A5B9B
> ERRLOG GET 15
00000000 A0801002 134A5AED
> ERRLOG GET 16
00000000 A0801002 134A5665
> ERRLOG GET 17
00000000 A0801002 134A5639
> ERRLOG GET 18
00000000 A0801002 134A5620
> ERRLOG GET 19
00000000 A0801002 134A53BD
> ERRLOG GET 1A
00000000 A0801002 134A530E
> ERRLOG GET 1B
00000000 A0801002 134A529D
> ERRLOG GET 1C
00000000 A0801002 134A5260
> ERRLOG GET 1D
00000000 A0801002 133D3BC4
> ERRLOG GET 1E
00000000 A0801002 133D3BB2
> exit
C:\Users\roliveira\Downloads\PS3-main\Syscon Connection Drivers and Diagrams ByNSC>python "PS3_Syscon_(Mullion_Sherwood)_script.py" COM4 SW
> auth
Auth successful
> errlog
00000000
# CODE CLOCK
# A0801002 15A8FF8E
# A0801002 15A8FF74
# A0801002 15A8FF5F
# A0801002 15A8FF3A
# A0801002 15A8FF29
# A0801002 15A8FF16
# A0801002 15A8FF01
# A0801002 15A8FEEC
# A0801002 14082CF6
# A0801002 14082CD2
# A0801002 14082CC2
# A0801002 14082CB5
# A0801002 14082CA1
# A0801002 14082C6E
# A0801002 14082C5D
# A0801002 14082C47
# A0801002 14082C2A
# A0801002 134A616D
# A0802022 134A613B
# A0802022 134A6139
# A0801002 134A5B9B
# A0801002 134A5AED
# A0801002 134A5665
# A0801002 134A5639
# A0801002 134A5620
# A0801002 134A53BD
# A0801002 134A530E
# A0801002 134A529D
# A0801002 134A5260
# A0801002 133D3BC4
# A0801002 133D3BB2
So it seems to be A0801002, which, from what I can tell from my short reading of this thread, is usually the fault of the tokins. I knew that replacing the tokins had a chance of bringing it back to life but I never bothered to actually try it because I thought I should take more precautions and actually ask in here first before doing it. So here I am. Is it worth it? Slim PS3s where I live sell for around 50€ and I wouldn't mind buying one but I would really like to give it a shot and try to repair it, it's not about the money, it's about the pride of (maybe) being able to fix it, even if it's only for a short while.
I found post #3546 in page 178 from @Pacorretaco in which he soldered what I think is a tantalum capacitor? to the tokins and didn't replace any of the original ones and got a CECH-20XX to work again, so if that's something that I could maybe do then that seems like the least destructive way to attempt to fix this console. Thanks in advance and thank you Felix for all the investigation and help you've given to people regarding these issues, the world needs more people like you.
I reccomend tantalizers for beginners. Since you want to fix it for the sake of fixing it, not becauae it's econimically viable to do so (it'll cost roughly the same to fix as it does to replace), then I'd say have at it!
PS: for the information effort the power on useage would be great to have. becount is the command but it doesnt work on sherwood syscon. So you'll have to check bgtoolset's errorcode under system management tab (same tab as if you were going to jailbreak). Or use ps3advancedtools I linked in my syscon tutorial.
I'm curious how long it lasted before toking out. Also, THX for the backstory. That context is useful and rarely provided.
Last edited:
.