PS3 PS3 FAT delid and thermal paste question

If the 3 beeps of the CECHL happened only one time maybe is just something related with a video misconfiguration, run the app in it to see the syscon errors
And the 20xx slim... well... you can check the syscon errors in it too, but you need to solder 3 wires to the motherboard and buy a "TTL 2 USB" programmer (are cheap, less than 5$) because the motherboard doesnt boots

As you can see in both methods the goal is to read the syscon error codes, if the PS3 boots you can use the app... otherway you need to use the programmer
That error codes are going to tell if is worthy to mess around with the tokins or not
 
If the 3 beeps of the CECHL happened only one time maybe is just something related with a video misconfiguration, run the app in it to see the syscon errors
And the 20xx slim... well... you can check the syscon errors in it too, but you need to solder 3 wires to the motherboard and buy a "TTL 2 USB" programmer (are cheap, less than 5$) because the motherboard doesnt boots

As you can see in both methods the goal is to read the syscon error codes, if the PS3 boots you can use the app... otherway you need to use the programmer
That error codes are going to tell if is worthy to mess around with the tokins or not
Thanks, gotta definitely check out these errors!
 
Thanks, gotta definitely check out these errors!
yeah, exactly. there's a variety of other things that can prevent a boot… I popped a fuse once, while probing the board. I was still getting ylod, but I had a completely different error code! You just never know for sure until you get the error code.
 
Through this tool -- https://www.psx-place.com/threads/release-ps3-advanced-tools.34104/ (You do need to have your system on either HEN or CFW, however). Once you have it installed, plug a usb drive in and then run the tool (as seen in the attachment). Your screen will go blank for a minute and then return to XMB. You should have a file in the USB with the syscon dump.
Error Log
01: A0801001 Sat Dec 31 03:43:37 2005
02: A0801001 Sat Dec 31 03:41:17 2005
03: A0801001 Sat Dec 31 00:01:07 2005
04: A0801002 Sat Dec 31 00:00:15 2005
05: A0801001 Sat Dec 31 12:10:40 2005
06: A0801001 Sat Dec 31 11:52:14 2005
07: A0801002 Sat Dec 31 00:28:20 2005
08: A0801002 Sat Dec 31 00:00:29 2005
09: A0901001 Sat May 28 07:57:30 2022
10: A0901001 Sat May 28 07:57:09 2022
11: A0801001 Wed May 25 05:42:35 2022
12: A0901001 Wed May 25 05:17:34 2022
13: A0901001 Wed Apr 20 09:43:10 2022
14: A0801002 Fri Apr 8 12:46:23 2022
15: A0801001 Mon Aug 10 14:04:01 2015
16: A0801001 Sat Mar 22 13:19:04 2014
17: A0801001 Mon Dec 16 15:25:13 2013
18: A0801001 Wed Aug 21 16:22:25 2013
19: A0801001 Thu Dec 27 05:05:08 2012
20: A0801001 Sat Nov 17 21:54:30 2012
21: A0801001 Wed Nov 14 00:09:58 2012
22: A0801001 Thu Jun 28 21:15:40 2012
23: A0801001 Mon Jan 16 01:55:23 2012
24: A0801001 Tue Sep 27 13:21:39 2011
25: A0801001 Wed Sep 22 13:04:21 2010
26: A0801001 Sat Jun 12 13:30:57 2010
27: A0801001 Sun Jun 6 03:00:20 2010
28: A0801001 Tue May 6 09:26:20 2008
29: A0801001 Tue Jan 15 03:23:24 2008
30: A0801004 Sun Nov 4 12:16:07 2007
31: A0801001 Tue Oct 9 01:26:47 2007
32: FFFFFFFF Tue Oct 9 01:05:51 2007

This is the log file for CECHB01, the console shuts down after 5 minutes of Resistance 3, but doesn't during MGS4 gameplay.

I cannot dump CECHL01 because it's on OFW 4.89, i have to wait BGTOOLSET update...
 
Last edited:
If the 3 beeps of the CECHL happened only one time maybe is just something related with a video misconfiguration, run the app in it to see the syscon errors
And the 20xx slim... well... you can check the syscon errors in it too, but you need to solder 3 wires to the motherboard and buy a "TTL 2 USB" programmer (are cheap, less than 5$) because the motherboard doesnt boots

As you can see in both methods the goal is to read the syscon error codes, if the PS3 boots you can use the app... otherway you need to use the programmer
That error codes are going to tell if is worthy to mess around with the tokins or not
Besides the logs i have just posted, i wanted to ask a question.
Now, this CECHB01 its not intended to be used as main console to play heavy and newer games like Resistance 3 or Last of US, i wanted a BC console to literally read and use my collection of ancient games.
Now with all the repaste and RSX delid only, i get decent temperatures and with a fan speed around 30 to 40%, but here is also summer and incredibly hot, and the console doesn't have much space for air intake.
Should i really operate on the tokins ? Or simply use it as is , the capacitors have already been shipped to me for 5 euros so i can install them anytime i want, but in which case ?
I guess sooner or later the console won't be able to play MGS4 or these PS2/PS1 titles, at that point maybe or its going to be late and just plain broken ?
Also on a side note, while i'm playng PS1 or PS2 i cannot control the fans, should i leave them at 40% fixed ?
 
Besides the logs i have just posted, i wanted to ask a question.
Now, this CECHB01 its not intended to be used as main console to play heavy and newer games like Resistance 3 or Last of US, i wanted a BC console to literally read and use my collection of ancient games.
Now with all the repaste and RSX delid only, i get decent temperatures and with a fan speed around 30 to 40%, but here is also summer and incredibly hot, and the console doesn't have much space for air intake.
Should i really operate on the tokins ? Or simply use it as is , the capacitors have already been shipped to me for 5 euros so i can install them anytime i want, but in which case ?
I guess sooner or later the console won't be able to play MGS4 or these PS2/PS1 titles, at that point maybe or its going to be late and just plain broken ?
Also on a side note, while i'm playng PS1 or PS2 i cannot control the fans, should i leave them at 40% fixed ?
The error codes ending in 100x are related with power lines, 1001 is CELL and 1002 is RSX
I would try to replace the PSU just incase (not sure if you already tryed), a problematic PSU could be the source of all kind of problems related with power lines
You should try with other games known to be special sensitive to this problem (gran turismo, TLOU) just to have another confirmation, if you use the forum search engine you are going to find some posts with accurate descriptions to trigger the crash/error... and after triggering the error you could use the app again to dump the error codes just for another confirmation that the new error is another 1001

You can also solder a couple of the tantalum capacitors you bought next to the CELL tokins, but dont remove or damage the tokins (yet)
If the experiment adding the tantalum caps in the CELL is successful it means you found the culprit for sure (the CELL tokins) and after having this final confirmation you could consider removing the tokins

Im suggesting all this cautions mostly becaue the console works, so is not really needed to fix it by now... is just this kind of shutdowns are going to go for worst, eventually the console is not going to boot and your only option will be to start messing around with the tokins... but you are not in that point yet
 
Last edited:
yep! here's the reference page - https://www.psdevwiki.com/ps3/Syscon_Error_Codes

1001 is believed to be a forced shutdown, as in, you switched the power rocker at the back. It's probably when you had a ylod and flipped the switch to reset the system.

1002 is potentially a tokin issue, but I agree with Sandungas -- the piggy-back is easier to install and not as destructive as replacing the tokin altogether. Some people have had sufficient results with just the piggy-back, but then YMMV. If it works, might be worth it just leaving it alone until it gets worse (if/when).
 
I'm going to test the last of us today, but also mass effect 3 didn't shutdown the console, and that game was one of the last ones released on PS3.
My PSU i believe is the very first, and hot, model APS226, i don't really know which models should be compatible with my CECHB01, i also have as said another CECHL01, but that console has never been opened and its almost brand new, kinda don't want to even remove the sticker :D
 
Ok, so The Last of Us lasted exactly 5 minutes like Resistance 3, so definitely same issue going on, but this time the console struggled to keep 68c , and went as high as 42% fanspeed.
The logs are the same, i suspect that more than 32 won'be save and i have no clue on how to clear them, so no new logs.
Again, play MGS4 or PS2games for hours nothing happens, same for Mass Effect 3, but these new PS3 exclusives i suppose use CELL or RSX somewhat differently and require quite more power.
At this point, since this console won't be utilized for heavy-new games, but rather old ones and Ps2/Ps1 i will keep it this way, and once the capacitors arrive i'll organize with my friend to solder them as "piggy-back" if the console starts to fail on PS2 games too, at that point it will be kinda mandatory to do i guess.
"piggy-back" is not permanent , right ? Its more like temporary, and tokins eventually have to be completely changed ?
 
The logs are the same, i suspect that more than 32 won'be save and i have no clue on how to clear them, so no new logs.

It only keeps the last 32, with the oldest ones getting removed as new ones get added in. I don't know that there's a way to clear them through the UI, but I wouldn't anyway. It's a good way to keep track of changes over time.

"piggy-back" is not permanent , right ? Its more like temporary, and tokins eventually have to be completely changed ?

In theory, yes, it's not permanent -- the log indicates your tokins are starting to fail, so you're just helping them along with additional caps. It might also prolong the tokin's lifespan, since you'll be off-loading some of the load through the additional mlcc caps (I think that's all I've seen used so far). @RIP-Felix has been keeping track of sucess rates, so he might have a better idea of the longevity.
 
About the candidate games to run this kind of stress tests... the release date and the graphics quality is not an accurate indicator of the workload. In general we can say a game with nice graphics is going to have a big workload, but as usually in programming there are tenths of different ways to achieve something, where one of them is "the good one" (the kind of thing everybody is going to agree because achieves the goal in the most simple and efficient way), there are also a couple of "aceptable" solutions, and tenths of "bad ideas"
Sometimes it happens there is a average game that is generating a huge workload because the game developers implemented a few of that "bad ideas", lol

In the case of naughty dog, his game engine is demanding but is not caused by "bad ideas", there are some educational documents released by them where they explains how they was splitting the threads to the PS3 SPU's in uncharted (using a SPU dedicated to detect the collisions of poligonal objects, etc...)... what happens is they are "squeezing" the CELL very well because they are using the CELL SPUs for graphic tasks
And gran turismo... well... is a sony studio, we can assume the game company had direct help from sony sony engineers too, so they also knew very well how to squeeze the PS3 hardware :D
*In te last of us... the most demanding task is when the game engine render waters (there are 2 spots in the game with water that triggers huge temperatures), personally i consider his game engine for PS3 had a flaw with that... but the game engine from grand theft auto seems suffers from this same problem too. Lets say... the RSX and the game engines for PS3 was in the borderline to simulate realistic waters, game devs tryed to achieve the best quality but at the cost of generating huge workloads

-------
The tokins have a dual function, the total capacitance is reduced with time, but they also cleans the interferences/noise in the power rail, if you add the tantalums piggy backing you are increasing the total capacitance but you are not removing the noise (the tokins does it, this is why im suggesting to dont remove the tokins yet)
And old PSU could generate noise over an aceptable level (the tokins are not going to be able to clean it), you can use a PC ATX PSU temporally to do a test, there are a couple of tutorials in the forum, if this test solves the problem then the culprit is the PSU (not the tokins)

Anyway... is a CECHB/COK-001 and contains PS2 hardware components, so... while playing PS2 games (without netemu) a lot of the workload is offloaded to the PS2 EE/GS, and i guess the EE/GS is not taking power from the tokins
PS1 is emulated in the CELL but i guess is not so demanding

The error codes log does a "loop", after is filled with 32 errors it starts overwriting them in oder "older to newer"... but you can identify them with the timestamps
Basically, if you make an stress test resulting in a crash, at the next reboot you should dump the error codes and search the error with a timestamp of today
Eventually your tokins are going to throw the towell, the PS3 will not boot (andyou will not be able to dump the error codes with the app), if this happens and you fix it by piggy-backing a tantalum that would be another proof that the tokin have a problem (and yeah, it would be about time to remove them, lol)
 
About the candidate games to run this kind of stress tests... the release date and the graphics quality is not an accurate indicator of the workload. In general we can say a game with nice graphics is going to have a big workload, but as usually in programming there are tenths of different ways to achieve something, where one of them is "the good one" (the kind of thing everybody is going to agree because achieves the goal in the most simple and efficient way), there are also a couple of "aceptable" solutions, and tenths of "bad ideas"
Sometimes it happens there is a average game that is generating a huge workload because the game developers implemented a few of that "bad ideas", lol

In the case of naughty dog, his game engine is demanding but is not caused by "bad ideas", there are some educational documents released by them where they explains how they was splitting the threads to the PS3 SPU's in uncharted (using a SPU dedicated to detect the collisions of poligonal objects, etc...)... what happens is they are "squeezing" the CELL very well because they are using the CELL SPUs for graphic tasks
And gran turismo... well... is a sony studio, we can assume the game company had direct help from sony sony engineers too, so they also knew very well how to squeeze the PS3 hardware :D
*In te last of us... the most demanding task is when the game engine render waters (there are 2 spots in the game with water that triggers huge temperatures), personally i consider his game engine for PS3 had a flaw with that... but the game engine from grand theft auto seems suffers from this same problem too. Lets say... the RSX and the game engines for PS3 was in the borderline to simulate realistic waters, game devs tryed to achieve the best quality but at the cost of generating huge workloads

-------
The tokins have a dual function, the total capacitance is reduced with time, but they also cleans the interferences/noise in the power rail, if you add the tantalums piggy backing you are increasing the total capacitance but you are not removing the noise (the tokins does it, this is why im suggesting to dont remove the tokins yet)
And old PSU could generate noise over an aceptable level (the tokins are not going to be able to clean it), you can use a PC ATX PSU temporally to do a test, there are a couple of tutorials in the forum, if this test solves the problem then the culprit is the PSU (not the tokins)

Anyway... is a CECHB/COK-001 and contains PS2 hardware components, so... while playing PS2 games (without netemu) a lot of the workload is offloaded to the PS2 EE/GS, and i guess the EE/GS is not taking power from the tokins
PS1 is emulated in the CELL but i guess is not so demanding

The error codes log does a "loop", after is filled with 32 errors it starts overwriting them in oder "older to newer"... but you can identify them with the timestamps
Basically, if you make an stress test resulting in a crash, at the next reboot you should dump the error codes and search the error with a timestamp of today
Eventually your tokins are going to throw the towell, the PS3 will not boot (andyou will not be able to dump the error codes with the app), if this happens and you fix it by piggy-backing a tantalum that would be another proof that the tokin have a problem (and yeah, it would be about time to remove them, lol)
Hi, thank you all for these insightful explanations, i have the situation much clearer now, essentially the LOGS we're not different except for the first one that was still a 1001, but dated in 2006 (i suppose the cmos battery is also almost dead), and therefore at this point i will simply solder the caps when the console gives up in piggy mode, since buyng a new PSU for it requires to look at some compatible options that either cost or have to be shipped in from china (takes months anyway).
Using ATX psu? I have some spare here, but i'm not that confident in tryng this option :D
Anyway, i can look on ebay for some used PSUs, can you point me towards compatible models with my board ? Some used PSU come cheap (like less than 10 euros, but used!), i have to look for one that is compatible.
 
Bringup Count: 1157, Shutdown Count: 1123
Runtime: 182 Days, 6 Hours, 28 Minutes, 0 Seconds
Error Log
01: A0801001 Tue Jan 3 23:04:31 2006
02: A0801001 Sat Dec 31 03:43:37 2005
03: A0801001 Sat Dec 31 03:41:17 2005
04: A0801001 Sat Dec 31 00:01:07 2005
05: A0801002 Sat Dec 31 00:00:15 2005
06: A0801001 Sat Dec 31 12:10:40 2005
07: A0801001 Sat Dec 31 11:52:14 2005
08: A0801002 Sat Dec 31 00:28:20 2005
09: A0801002 Sat Dec 31 00:00:29 2005
10: A0901001 Sat May 28 07:57:30 2022
11: A0901001 Sat May 28 07:57:09 2022
12: A0801001 Wed May 25 05:42:35 2022
13: A0901001 Wed May 25 05:17:34 2022
14: A0901001 Wed Apr 20 09:43:10 2022
15: A0801002 Fri Apr 8 12:46:23 2022
16: A0801001 Mon Aug 10 14:04:01 2015
17: A0801001 Sat Mar 22 13:19:04 2014
18: A0801001 Mon Dec 16 15:25:13 2013
19: A0801001 Wed Aug 21 16:22:25 2013
20: A0801001 Thu Dec 27 05:05:08 2012
21: A0801001 Sat Nov 17 21:54:30 2012
22: A0801001 Wed Nov 14 00:09:58 2012
23: A0801001 Thu Jun 28 21:15:40 2012
24: A0801001 Mon Jan 16 01:55:23 2012
25: A0801001 Tue Sep 27 13:21:39 2011
26: A0801001 Wed Sep 22 13:04:21 2010
27: A0801001 Sat Jun 12 13:30:57 2010
28: A0801001 Sun Jun 6 03:00:20 2010
29: A0801001 Tue May 6 09:26:20 2008
30: A0801001 Tue Jan 15 03:23:24 2008
31: A0801004 Sun Nov 4 12:16:07 2007
32: FFFFFFFF Tue Oct 9 01:26:47 2007

As you can see, we are in JUNE but no errors in JUNE 2022
The console is connected to the internet and has correct date/hour format.
The fact that no errors show up recently is weird , maybe it could be a bad PSU that cannot provide enough power mmmm
 
By comparing the error log from your 2 posts... it seems the error you had today was recorded as:
A0801001 Tue Jan 3 23:04:31 2006

Are you sure you have the date/time settings correctly configured in the XMB ?
The way how this timestamps works is a bit weird, i dont understand it completly, but yeah, it depends of the XMB date/time settings, and the state of the battery (present and working, present and empty, or not present)

The suggestion of a test with an ATX PSU is motly because i assume most people have one at home (even if is already used in a desktop PC), and because is just a temporal test that can be made for free
I mean... if you buy PS3 PSU right now is ilke a blind shoot because you are not sure if thats the problem, so it could be a waste of money
 
By comparing the error log from your 2 posts... it seems the error you had today was recorded as:
A0801001 Tue Jan 3 23:04:31 2006

Are you sure you have the date/time settings correctly configured in the XMB ?
The way how this timestamps works is a bit weird, i dont understand it completly, but yeah, it depends of the XMB date/time settings, and the state of the battery (present and working, present and empty, or not present)

The suggestion of a test with an ATX PSU is motly because i assume most people have one at home (even if is already used in a desktop PC), and because is just a temporal test that can be made for free
I mean... if you buy PS3 PSU right now is ilke a blind shoot because you are not sure if thats the problem, so it could be a waste of money
Yes, date and time are correct.
 
Yes, date and time are correct.
Then is the battery that is empty ?, try to do this sequence of actions:
1) disconnect the main power cord at the PS3 back, wait 1 minute and connect it again
2) go to XMB date/time settings and check if they reverted back to default (around 2006 ?)

That would mean the battery cell is empty
 
Then is the battery that is empty ?, try to do this sequence of actions:
1) disconnect the main power cord at the PS3 back, wait 1 minute and connect it again
2) go to XMB date/time settings and check if they reverted back to default (around 2006 ?)

That would mean the battery cell is empty
Bad battery has to be replaced ?
 
Also a quick update, i have left the PS3 unplugged for hours and after this the battery was showing the proper hour and date, so it still works (without internet connection).
 
Also a quick update, i have left the PS3 unplugged for hours and after this the battery was showing the proper hour and date, so it still works (without internet connection).
Weird, then i dont understand it
Right now is recording errors with a timestamp from year 2006, but in your log there are other weird details, as example:
04: A0801001 Sat Dec 31 00:01:07 2005
05: A0801002 Sat Dec 31 00:00:15 2005
06: A0801001 Sat Dec 31 12:10:40 2005
07: A0801001 Sat Dec 31 11:52:14 2005
08: A0801002 Sat Dec 31 00:28:20 2005
09: A0801002 Sat Dec 31 00:00:29 2005
Ok, that timestamps with year 2005 are not true, but in theory they should follow a progression (always increasing)
The problem here is there are 2 errors with hours=00... then 2 more with hours=11 and 12... and then 2 more with hours=00. All them in the same day

You are having the "delorean effect", lol, in your log the timer has been reset several times to default (and default seems to be Sat Dec 31 00:00:00 2005)
This is usually caused by a missing battery (or empty?, im not sure what happens with empty batteries but probably the same)

Anyway, the timestamps doesnt matters much, are going to confuse you a bit because you are not sure about when it happened, but are just informative
 
Basically, it seems it was reset to default 2 times
01: A0801001 Tue Jan 3 23:04:31 2006
02: A0801001 Sat Dec 31 03:43:37 2005
03: A0801001 Sat Dec 31 03:41:17 2005
04: A0801001 Sat Dec 31 00:01:07 2005
05: A0801002 Sat Dec 31 00:00:15 2005
<--------------------------------------------------------- timer reset to default here (Sat Dec 31 00:00:00 2005)
06: A0801001 Sat Dec 31 12:10:40 2005
07: A0801001 Sat Dec 31 11:52:14 2005
08: A0801002 Sat Dec 31 00:28:20 2005
09: A0801002 Sat Dec 31 00:00:29 2005
<--------------------------------------------------------- timer reset to default here (Sat Dec 31 00:00:00 2005)
10: A0901001 Sat May 28 07:57:30 2022
11: A0901001 Sat May 28 07:57:09 2022
12: A0801001 Wed May 25 05:42:35 2022
13: A0901001 Wed May 25 05:17:34 2022
14: A0901001 Wed Apr 20 09:43:10 2022
15: A0801002 Fri Apr 8 12:46:23 2022
16: A0801001 Mon Aug 10 14:04:01 2015
17: A0801001 Sat Mar 22 13:19:04 2014
18: A0801001 Mon Dec 16 15:25:13 2013
19: A0801001 Wed Aug 21 16:22:25 2013
20: A0801001 Thu Dec 27 05:05:08 2012
21: A0801001 Sat Nov 17 21:54:30 2012
22: A0801001 Wed Nov 14 00:09:58 2012
23: A0801001 Thu Jun 28 21:15:40 2012
24: A0801001 Mon Jan 16 01:55:23 2012
25: A0801001 Tue Sep 27 13:21:39 2011
26: A0801001 Wed Sep 22 13:04:21 2010
27: A0801001 Sat Jun 12 13:30:57 2010
28: A0801001 Sun Jun 6 03:00:20 2010
29: A0801001 Tue May 6 09:26:20 2008
30: A0801001 Tue Jan 15 03:23:24 2008
31: A0801004 Sun Nov 4 12:16:07 2007
32: FFFFFFFF Tue Oct 9 01:26:47 2007
The error 09 happened 29 seconds after the first timer reset
And error 05 happened 15 seconds after the second timer reset

We dont know the exact timestamp, but we know they should be higher than error 10, with a timestamp of Sat May 28 07:57:30 2022
Thats the last realistic timestamp, so all the errors with year 2005 or 2006 happened in the last 20 days or so
 

Similar threads

Back
Top