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

[superprokill1]

Hello. I dumped syscon log via ps3 advanced tools . I have ps3 slim cech 2004A with cfw rebug 4.84.2. I want to know if it is anything wrong with my console or not. I worry very much because of ylod on first slims. Please help me if anything is wrong. I am about to change thermal paste and clean the console from the dust inside if any. Here is the log. Should I worry or there is nothing wrong ?

Firmware Version: 4.84 (build 50696)
Platform ID: CokG11
Product Code: 00 85
Product Sub Code: 00 09
Hardware Config: 4E00FFFF0203BC3C
Syscon Fimware Version: 0832.00010002083E0832 (EEPROM: 00010002083E0832)

Bringup Count: 3867, Shutdown Count: 3779
Runtime: 217 Days, 10 Hours, 18 Minutes, 29 Seconds

Error Log
01: A0802022  Fri Feb  2 08:39:52 2024
02: A0802022  Fri Feb  2 08:37:59 2024
03: A0802022  Wed Jan  3 20:16:29 2024
04: A0802022  Wed Jan  3 20:08:17 2024
05: A0802022  Wed Jan  3 20:07:03 2024
06: A0802022  Wed Jan  3 20:05:28 2024
07: A0802022  Mon Jan  1 21:20:45 2024
08: A0802022  Mon Jan  1 21:09:01 2024
09: A0802022  Mon Dec 18 23:04:59 2023
10: A0802022  Mon Dec 18 22:45:41 2023
11: A0802022  Sun Dec 17 08:12:41 2023
12: A0802022  Sun Dec 17 08:06:00 2023
13: A0802022  Wed Nov 22 06:37:03 2023
14: A0802022  Wed Nov 22 06:03:14 2023
15: A0802022  Mon Oct 30 22:25:36 2023
16: A0802022  Mon Oct 30 22:12:36 2023
17: A0802022  Sat Oct 28 05:55:55 2023
18: A0802022  Tue Oct 24 06:55:11 2023
19: A0802022  Tue Oct 24 06:02:55 2023
20: A0801200  Tue Oct 24 05:53:54 2023
21: A0802022  Tue Oct 24 05:34:56 2023
22: A0802022  Mon Oct 23 07:10:57 2023
23: A0802022  Mon Oct 23 05:44:34 2023
24: A0802022  Fri Oct 20 05:49:34 2023
25: A0802022  Fri Oct 20 04:39:25 2023
26: A0802022  Thu Oct 19 06:52:40 2023
27: A0802022  Thu Oct 19 04:29:01 2023
28: A0802022  Mon Oct 16 20:22:17 2023
29: A0802022  Mon Oct 16 18:28:33 2023
30: A0802022  Sun Oct 15 21:43:26 2023
31: A0802022  Sun Oct 15 21:13:33 2023
32: FFFFFFFF  Fri Dec 31 23:59:59 1999

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#2022_(DVE)
do you know in which circumstances those 2022 errors happened?
there's a 1200 error, which means the CPU overheated. clean it up, replace the thermal paste, and you should be good to go on that. I still don't know what's causing your 2022

 

[xristos1925]

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#2022_(DVE)
do you know in which circumstances those 2022 errors happened?
there's a 1200 error, which means the CPU overheated. clean it up, replace the thermal paste, and you should be good to go on that. I still don't know what's causing your 2022

I think that I know what caused 1200 error . On webman settings on PS2 emulator the fan was low percentage, I think 25% or 30% and When It reached Above 68 Celcius it shut down when I was playing a PS2 game. When I changed to 40% then It did not happened again when playing ps2 games.
2022 (DVE) errors I don't know either. I don't see any graphical artifacts on the screen either. Other users on other sites reported about that error that it's normal and I can ignore it and they have seen it on a perfectly working console.
I don't know if is true or not. I hope it is true.I plan on taking it to an expert so he can change thermal paste and clean it..I am afraid for doing delidding because many users reported that they destroyed their consoles on trying.Even for an expert I have fear for doing..Because I don't want to buy another ps3 if this is working and with cleaning and change paste can maintain it's functionality.

 

[superprokill1]

You want low esr caps. Less than 9mOhms. And you need to make sure the'll fit under the RF shield. You can source good polymers caps on most junk electronics. So my advice is to seek out a local electronics repair shop and ask if they have any junk motherboards or graphics cards. You can salvage the polymer caps off their core voltage line, which should have low ESR decoupling capacitors that will work.

New caps would last longer and you can be sure they still met specifications, but in a pinch or hard to ship to location like you say, salvage may be your best bet. BTW, you don't need my tanatlizer board. It's just to make soldering easier, since it has the + bridge built in. But you can still use jumper wires NP. I would recommend replacing all the tokins if you replace any, to remove any effects of impedance mismatches and lesson the chances of antiresonance peaks. You can try a parasite cap to confirm the diagnosis if you want, but 1002 is about as diagnostic as these codes get.

not sure if this counts as a necro reply, but you recommended replacing all the tokins. If by all of them you mean the RSX's and CELL's, totalling 8, and judging from the estimated price tag on your 0.6b then that would end up costing about $200 USD.
How terrible would it realistically be to cheap out on this and completely skip the MLCC ones, despite me having an early model (CECHE11) and OE128 caps, and also replace as little of them as possible (maybe just the ones for the RSX, one or two of them)? To be honest, I'm not concerned if it dies again in 5 or 7 years, at least at that point I'd very possibly have enough money to buy my own caps, I feel guilty asking a relative to pay for caps that expensive lol

 

[roy76]

not sure if this counts as a necro reply, but you recommended replacing all the tokins. If by all of them you mean the RSX's and CELL's, totalling 8, and judging from the estimated price tag on your 0.6b then that would end up costing about $200 USD.
How terrible would it realistically be to cheap out on this and completely skip the MLCC ones, despite me having an early model (CECHE11) and OE128 caps, and also replace as little of them as possible (maybe just the ones for the RSX, one or two of them)? To be honest, I'm not concerned if it dies again in 5 or 7 years, at least at that point I'd very possibly have enough money to buy my own caps, I feel guilty asking a relative to pay for caps that expensive lol

I bought 30 of the EEFGX0E471L this week which was £45 from Farnell if that helps.

 

[IDontSpagett]

Hello All,

I'm new to this forum, so please forgive me for any mistakes that I make in this post.

Firstly, @RIPFelix, thanks a lot for your guides & videos on the YLOD issue.
Your videos are one of the reasons why I took a leap into this rabbit hole.

So, I recently took apart a PS3 Fat (CECHK Model) which I had bought for just messing around as I am electronics engineering student.

The person who sold the console clearly stated that it's broken.

It's in a semi-decent physical state and I am pretty sure that someone has already taken it apart before (due to missing screws & broken tape for the antenna wire), but no work has been done on the motherboard.

There are a few odd things that I noticed in the syscon log, mainly the bring up & shutdown count difference followed by the low usage time. I was also not able to get the dates for the error log list, but that could be accounted for due to the CMOS battery dying out.

I am attaching the Syscon error log along this post.
Please help me understand how I can go about fixing this console.

Thanks in advance.

PS3 Fat CECHK Model

Motherboard Revision : DIA-002

Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ ERRLOG GET 00
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$


Internal Mode

>$ errlog
errlog
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xa0093004, clock:0xffffffff
ofst[124]:err_code:0xa0093004, clock:0xffffffff
ofst[  0]:err_code:0xa0093004, clock:0xffffffff
ofst[  4]:err_code:0xa0093004, clock:0xffffffff
ofst[  8]:err_code:0xa0093004, clock:0xffffffff
ofst[ 12]:err_code:0xa0093004, clock:0xffffffff
ofst[ 16]:err_code:0xa0093004, clock:0xffffffff
ofst[ 20]:err_code:0xa0093004, clock:0xffffffff
ofst[ 24]:err_code:0xa0093004, clock:0xffffffff
ofst[ 28]:err_code:0xa0093004, clock:0xffffffff
ofst[ 32]:err_code:0xa0093004, clock:0xffffffff
ofst[ 36]:err_code:0xa0093004, clock:0xffffffff
ofst[ 40]:err_code:0xa0093004, clock:0xffffffff
ofst[ 44]:err_code:0xa0093004, clock:0xffffffff
ofst[ 48]:err_code:0xa0093004, clock:0xffffffff
ofst[ 52]:err_code:0xa0093004, clock:0xffffffff
ofst[ 56]:err_code:0xa0093004, clock:0xffffffff
ofst[ 60]:err_code:0xa0093004, clock:0xffffffff
ofst[ 64]:err_code:0xa0093004, clock:0xffffffff
ofst[ 68]:err_code:0xa0093004, clock:0xffffffff
ofst[ 72]:err_code:0xa0093004, clock:0xffffffff
ofst[ 76]:err_code:0xa0093004, clock:0xffffffff
ofst[ 80]:err_code:0xa0093004, clock:0xffffffff
ofst[ 84]:err_code:0xa0093004, clock:0xffffffff
ofst[ 88]:err_code:0xa0093004, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0093004, clock:0xffffffff
ofst[100]:err_code:0xa0093004, clock:0xffffffff
ofst[104]:err_code:0xa0093004, clock:0xffffffff
ofst[108]:err_code:0xa0093004, clock:0xffffffff
ofst[112]:err_code:0xa0093004, clock:0xffffffff
[mullion]$

>$ becount
becount
Bringup : 727 times
Shutdown: 172 times
Power-on: 9day 06hour 16min 42sec

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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004

>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

 

[xristos1925]

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#2022_(DVE)
do you know in which circumstances those 2022 errors happened?
there's a 1200 error, which means the CPU overheated. clean it up, replace the thermal paste, and you should be good to go on that. I still don't know what's causing your 2022

Now I remember. My cousin gave me a ps3 fat to jailbreak it. I remember that some time I was switching hdmi cables on ps3 slim and fat while both consoles were turned on for copying some packages to usb and install it on another and then I was trying to connect the two ps3s together via ethernet and multiman net_host0 method so I was switching hdmi cables for setting up and testing each console.

 

[RIP-Felix]

not sure if this counts as a necro reply, but you recommended replacing all the tokins. If by all of them you mean the RSX's and CELL's, totalling 8, and judging from the estimated price tag on your 0.6b then that would end up costing about $200 USD.
How terrible would it realistically be to cheap out on this and completely skip the MLCC ones, despite me having an early model (CECHE11) and OE128 caps, and also replace as little of them as possible (maybe just the ones for the RSX, one or two of them)? To be honest, I'm not concerned if it dies again in 5 or 7 years, at least at that point I'd very possibly have enough money to buy my own caps, I feel guilty asking a relative to pay for caps that expensive lol

It should only cost between $25 and $50 to replace all 8. If it costs 200, keep shopping! Hint, try LCSC.

 

[RIP-Felix]

I think that I know what caused 1200 error . On webman settings on PS2 emulator the fan was low percentage, I think 25% or 30% and When It reached Above 68 Celcius it shut down when I was playing a PS2 game. When I changed to 40% then It did not happened again when playing ps2 games.
2022 (DVE) errors I don't know either. I don't see any graphical artifacts on the screen either. Other users on other sites reported about that error that it's normal and I can ignore it and they have seen it on a perfectly working console.
I don't know if is true or not. I hope it is true.I plan on taking it to an expert so he can change thermal paste and clean it..I am afraid for doing delidding because many users reported that they destroyed their consoles on trying.Even for an expert I have fear for doing..Because I don't want to buy another ps3 if this is working and with cleaning and change paste can maintain it's functionality.

2022 I wouldnt worry about until it's been cleaned, repasted, and potentially delided depending on the result.

2022 is usually not diagnostic on it's own. It tends to be associated with a more diagnostic code, in this case 1200. I usually reccomended taking care of the diagnostic code 1st and seeing if the other one doesn't just disappear.

The webman explanation doesnt make sense. That sounds like a red herring.

20xx models are among the most reliable models. 65nm RSX is a tank, doesnt have bad underfill or bumpgate issues AFAICT. RSX tokins do age and die, but if maintained can last a VERY long time. Doesn't seem to be as prone to wifi/BT issues as 30xx consoles...etc.

That model is very common and inexpensive to replace, so I wouldnt be too afraid to attempt a DIY repair, especially if you are familiar with electronics. Just do your research about the right tools and methods. Do not use cutting wire, dental floss, razor blades...etc to delid. A #2 painters palate knife will work if you sand the lower edge to round it. I'd reccomend attempting on a donor 1st. Or make a proper delidding tool.

 

[xristos1925]

2022 I wouldnt worry about until it's been cleaned, repasted, and potentially delided depending on the result.

2022 is usually not diagnostic on it's own. It tends to be associated with a more diagnostic code, in this case 1200. I usually reccomended taking care of the diagnostic code 1st and seeing if the other one doesn't just disappear.

The webman explanation doesnt make sense. That sounds like a red herring.

20xx models are among the most reliable models. 65nm RSX is a tank, doesnt have bad underfill or bumpgate issues AFAICT. RSX tokins do age and die, but if maintained can last a VERY long time. Doesn't seem to be as prone to wifi/BT issues as 30xx consoles...etc.

That model is very common and inexpensive to replace, so I wouldnt be too afraid to attempt a DIY repair, especially if you are familiar with electronics. Just do your research about the right tools and methods. Do not use cutting wire, dental floss, razor blades...etc to delid. A #2 painters palate knife will work if you sand the lower edge to round it. I'd reccomend attempting on a donor 1st. Or make a proper delidding tool.

Thank you very much for your reply and your help. For 2022, the console was turned off and I removed several times the hdmi and plugged in another ps3 fat and then again on ps3 slim. This happened several times because I was trying to test something for a ps3 fat of my cousin. on 1200 I played a ps2 game but on webmanmod fan settings for ps2 it was not 40% on fan settings, it was lower so It reached a certain temprature and It shut down. When I put 40% on fan on ps2 emulator on webman it did not happened again. Because I read on ps3devwiki that 2022 can be reproduced by hdmi when I remove the hdmi and put in another console. For change thermal paste or delidding if it is needed, I will take it to an expert that is a friend of mine for that because I can't do it on my own because I don't have the skills for that and I am afraid to try for the fear of break or brick something.

 

[superprokill1]

It should only cost between $25 and $50 to replace all 8. If it costs 200, keep shopping! Hint, try LCSC.

Oh! I know what I got wrong then in my calcs. In another thread, the one about the experimental NEC/TOKIN replacement methods, where you posted the release of your Tantalizer mod 0.6b, you gave a list of capacitors to use.

• 3x 470uF 2.5v 7mΩ Panasonic 2R5TPE470M7 TaPol caps.

• 1x 47uF 10v X5R 0805 MLCC (Example)

• 1x 22uF 10v X5R 0805 MLCC (Example)

• 1x 10uF 10v X5R 0805 MLCC (Example)

• 1x 4.7uF 10v X5R 0805 MLCC (Example)

• 1x 2.2uF 10v X5R 0805 MLCC (Example)

• 1x 1uF 10v X5R 0805 MLCC (Example)

• Total cost = About $25

Now, I am not gonna use your PCB since all I have is a soldering iron to do the job, but I assume those capacitors are the actual important part of the fix, and therefore should be common even if not using the PCB and just manually soldering them.
Those 3x 470uF, 1x 47uF, 1x 2uF and so on and so on, I can safely assume that's to replace a single TOKIN. I thought the "Total cost" below was the cost for one TOKIN, so I multiplied that by 8 and got $200... Whoopsie.
After actually checking the sites you linked with examples on where to buy those caps, I can tell that now 24x 470uF caps are just ~$24, nearly not as much as the triple digits number I had in mind :^)
Thank you so much, I guess I can now safely order those caps. Appreciated

 

[Josue Guevara]

First of all, excuse my bad English, I am translating from Spanish to English.
I don't know if anyone could help me with the repair of my super slim PS3 with MPX-001 board. When I turn it on, it turns off after about 3 seconds, it connects to the uart syscon, and I get errors 3034 and 4401. So investigating it is due to problems in the BGA and I did the test of placing pressure on each of the processors to see if there were some difference in the shutdown time, but no, it kept turning off after 3 seconds, checking further I found a short in the 1.8 V regulator of the bluetooh and in turn the entire bluetooh module shorted, both quite a bit, and the console continued with the same problem that it turns off after 3 seconds, I thought that maybe the short bluetooh had made my south britghe bad so I changed it successfully with another one that I know was operational and the result was the same, the same errors, then Looking at some forums, a person said that he had these errors because the Ethernet IC was bad and caused the southbridge to be blocked and the CPU was not able to go to the next stage, resulting in those errors. Then I started measuring capacitors and everything related to the Ethernet IC, comparing values with another operating board and the values were similar, so I discarded the Ethernet IC. So I don't know what else to measure or test. But I'm sure it's not a problem with the BGA soldering because I've had other consoles that when I put pressure on the RSX, they stayed with the green light for longer, which doesn't happen with this one here... By the way, I already measured values of the RSX and del Cell and they all show correct values. Unless I'm missing measuring something else. That's why here I am today looking for advice and help on what the problem could be.

 

[philhalo66]

Hello PSX place users. I dumped my syscon error log and im really struggling to figure out what caused my YLoD a few years ago. System was working fine but ran hot around 2020ish. in 2022 i pulled it out of storage and it was giving the YLoD. I applied heat to the board and it brought it back but i was afraid to use it so i put it in my closet again till last week and i dumped the syscon and this is what i got. Any help would be much appreciated.
It just died again while copying some memory cards. 3 beeps and red blinking light then YLoD.

Firmware Version: 4.90 (build 50747)
Platform ID: Cok14
Product Code: 00 84
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1423, Shutdown Count: 1353
Runtime: 92 Days, 6 Hours, 54 Minutes, 9 Seconds
Error Log
01: A0801001 Fri Dec 31 23:59:59 1999
02: A0801601 Tue Jul 21 21:34:13 2009
03: A0801701 Tue Jul 21 21:34:13 2009
04: A0801001 Tue Jul 21 21:13:21 2009
05: A0801001 Tue Jul 21 20:46:19 2009
06: A0801001 Thu Jul 2 16:51:53 2009
07: A0801001 Thu Jul 2 16:19:02 2009
08: A0801001 Thu Jul 2 16:16:42 2009
09: A0801001 Thu Jul 2 16:15:54 2009
10: A0801001 Thu Jul 2 16:15:49 2009
11: A0801001 Sun Mar 2 20:29:38 2008
12: A0801001 Wed Feb 20 05:36:49 2008
13: A0801001 Fri Feb 15 05:18:53 2008
14: A0801001 Fri Feb 15 05:07:30 2008
15: A0801001 Mon Jan 28 11:17:21 2008
16: A0801001 Mon Jan 28 08:47:11 2008
17: A0801001 Mon Jan 28 08:46:51 2008
18: A0801001 Wed Sep 5 06:33:38 2007
19: A0801001 Tue Sep 4 10:08:12 2007
20: A0801001 Sat Sep 1 16:36:32 2007
21: A0801001 Mon Feb 20 10:28:13 2006
22: A0801001 Fri Feb 17 12:29:58 2006
23: A0801001 Sun Feb 12 10:30:41 2006
24: A0801001 Sun Feb 12 08:11:05 2006
25: A0902203 Tue Feb 7 06:10:53 2006
26: A0801001 Tue Feb 7 06:10:53 2006
27: A0801001 Sun Jan 1 22:48:07 2006
28: A0801001 Sat Dec 31 00:31:47 2005
29: A0801001 Sat Dec 31 00:00:09 2005
30: A0403034 Sun Jul 9 10:57:01 2006
31: A0403034 Thu Jul 6 00:27:06 2006
32: A0403034 Fri Dec 31 23:59:59 1999

 

[superprokill1]

Hello PSX place users. I dumped my syscon error log and im really struggling to figure out what caused my YLoD a few years ago. System was working fine but ran hot around 2020ish. in 2022 i pulled it out of storage and it was giving the YLoD. I applied heat to the board and it brought it back but i was afraid to use it so i put it in my closet again till last week and i dumped the syscon and this is what i got. Any help would be much appreciated.
It just died again while copying some memory cards. 3 beeps and red blinking light then YLoD.

Firmware Version: 4.90 (build 50747)
Platform ID: Cok14
Product Code: 00 84
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1423, Shutdown Count: 1353
Runtime: 92 Days, 6 Hours, 54 Minutes, 9 Seconds
Error Log
01: A0801001 Fri Dec 31 23:59:59 1999
02: A0801601 Tue Jul 21 21:34:13 2009
03: A0801701 Tue Jul 21 21:34:13 2009
04: A0801001 Tue Jul 21 21:13:21 2009
05: A0801001 Tue Jul 21 20:46:19 2009
06: A0801001 Thu Jul 2 16:51:53 2009
07: A0801001 Thu Jul 2 16:19:02 2009
08: A0801001 Thu Jul 2 16:16:42 2009
09: A0801001 Thu Jul 2 16:15:54 2009
10: A0801001 Thu Jul 2 16:15:49 2009
11: A0801001 Sun Mar 2 20:29:38 2008
12: A0801001 Wed Feb 20 05:36:49 2008
13: A0801001 Fri Feb 15 05:18:53 2008
14: A0801001 Fri Feb 15 05:07:30 2008
15: A0801001 Mon Jan 28 11:17:21 2008
16: A0801001 Mon Jan 28 08:47:11 2008
17: A0801001 Mon Jan 28 08:46:51 2008
18: A0801001 Wed Sep 5 06:33:38 2007
19: A0801001 Tue Sep 4 10:08:12 2007
20: A0801001 Sat Sep 1 16:36:32 2007
21: A0801001 Mon Feb 20 10:28:13 2006
22: A0801001 Fri Feb 17 12:29:58 2006
23: A0801001 Sun Feb 12 10:30:41 2006
24: A0801001 Sun Feb 12 08:11:05 2006
25: A0902203 Tue Feb 7 06:10:53 2006
26: A0801001 Tue Feb 7 06:10:53 2006
27: A0801001 Sun Jan 1 22:48:07 2006
28: A0801001 Sat Dec 31 00:31:47 2005
29: A0801001 Sat Dec 31 00:00:09 2005
30: A0403034 Sun Jul 9 10:57:01 2006
31: A0403034 Thu Jul 6 00:27:06 2006
32: A0403034 Fri Dec 31 23:59:59 1999

Your GPU is likely dead, RIP.
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3034

 

[philhalo66]

Your GPU is likely dead, RIP.
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3034

guess that makes it a good candidate for the Frankenstein mod.

 

[Ganjo]

Do these codes point towards the cell processor? Also, why cant I use BECOUNT or BRINGUP? The guide says they might need to be patched but doesnt show how. Thanks
errlog
ofst[ 76]:err_code:0xffffffff, clock:0x1ea9669e 2016/04/19 21:58:54
ofst[ 80]:err_code:0xa0403034, clock:0x1ea9669e 2016/04/19 21:58:54
ofst[ 84]:err_code:0xa0404422, clock:0x1ea966a6 2016/04/19 21:59:02
ofst[ 88]:err_code:0xa0403034, clock:0x1ea966a6 2016/04/19 21:59:02
ofst[ 92]:err_code:0xa0404422, clock:0x1ea966ac 2016/04/19 21:59:08
ofst[ 96]:err_code:0xa0403034, clock:0x1ea966ac 2016/04/19 21:59:08
ofst[100]:err_code:0xa0404422, clock:0x1ecaaffe 2016/05/15 03:56:46
ofst[104]:err_code:0xa0403034, clock:0x1ecaaffe 2016/05/15 03:56:46
ofst[108]:err_code:0xa0404422, clock:0x25b7550e 2020/01/19 17:57:34
ofst[112]:err_code:0xa0403034, clock:0x25b7550e 2020/01/19 17:57:34
ofst[116]:err_code:0xa0404422, clock:0x25b75530 2020/01/19 17:58:08
ofst[120]:err_code:0xa0403034, clock:0x25b75530 2020/01/19 17:58:08
ofst[124]:err_code:0xa0404422, clock:0x26578913 2020/05/20 06:22:11
ofst[ 0]:err_code:0xa0403034, clock:0x26578913 2020/05/20 06:22:11
ofst[ 4]:err_code:0xa0404422, clock:0x2657891e 2020/05/20 06:22:22
ofst[ 8]:err_code:0xa0403034, clock:0x2657891e 2020/05/20 06:22:22
ofst[ 12]:err_code:0xa0404422, clock:0x29bda986 2022/03/11 06:32:38
ofst[ 16]:err_code:0xa0403034, clock:0x29bda986 2022/03/11 06:32:38
ofst[ 20]:err_code:0xa0404422, clock:0x2a37bf7a 2022/06/11 21:02:50
ofst[ 24]:err_code:0xa0403034, clock:0x2a37bf7a 2022/06/11 21:02:50
ofst[ 28]:err_code:0xa0404422, clock:0x2cf2e973 2023/11/24 04:56:19
ofst[ 32]:err_code:0xa0403034, clock:0x2cf2e973 2023/11/24 04:56:19
ofst[ 36]:err_code:0xa0404422, clock:0x2cf2e987 2023/11/24 04:56:39
ofst[ 40]:err_code:0xa0403034, clock:0x2cf2e987 2023/11/24 04:56:39
ofst[ 44]:err_code:0xa0404422, clock:0x2cf3ecd4 2023/11/24 23:23:00
ofst[ 48]:err_code:0xa0403034, clock:0x2cf3ecd4 2023/11/24 23:23:00
ofst[ 52]:err_code:0xa0404422, clock:0x2cf41c6d 2023/11/25 02:46:05
ofst[ 56]:err_code:0xa0403034, clock:0x2cf41c6d 2023/11/25 02:46:05
ofst[ 60]:err_code:0xa0404422, clock:0x2cf41c84 2023/11/25 02:46:28
ofst[ 64]:err_code:0xa0403034, clock:0x2cf41c84 2023/11/25 02:46:28
ofst[ 68]:err_code:0xa0404422, clock:0x2d5ee1f5 2024/02/14 02:29:09
ofst[ 72]:err_code:0xa0403034, clock:0x2d5ee1f5 2024/02/14 02:29:09
[mullion]$

 

[Ganjo]

I was trying this on another console (A01) and I accidentally input the eepcsum values into 0x39f3 instead of 0x39fe. I tried fixing 39fe again and for some reason it didnt input, I power cycled and now it says the value should be 0xffffd728 (sum0x3910). Should I input w 39fe 28 d7 ff ff? I was fairly certain I did input 38 0f as it said it should be 0x0f38. Is it fixable or did I brick it?

 

[Ganjo]

This is the third console im trying to fix. I tried the orbis mod but it wouldnt work on this or the one I screwed up. These error codes point to an HDMI error?? I was gonna put a 90nm back on to test but I only have dead ones right now. Am I supposed to hit power then hit send command to use bringup?

[mullion]$
errlog
ofst[ 0]:err_code:0xa0202120, clock:0xffffffff
ofst[ 4]:err_code:0xa0202120, clock:0xffffffff
ofst[ 8]:err_code:0xa0202120, clock:0xffffffff
ofst[ 12]:err_code:0xa0202120, clock:0xffffffff
ofst[ 16]:err_code:0xa0202120, clock:0xffffffff
ofst[ 20]:err_code:0xa0202120, clock:0xffffffff
ofst[ 24]:err_code:0xa0202120, clock:0xffffffff
ofst[ 28]:err_code:0xa0202120, clock:0xffffffff
ofst[ 32]:err_code:0xa0202120, clock:0xffffffff
ofst[ 36]:err_code:0xa0213013, clock:0xffffffff
ofst[ 40]:err_code:0xa0202120, clock:0xffffffff
ofst[ 44]:err_code:0xa0202120, clock:0xffffffff
ofst[ 48]:err_code:0xa0202120, clock:0xffffffff
ofst[ 52]:err_code:0xa0202120, clock:0xffffffff
ofst[ 56]:err_code:0xa0202120, clock:0xffffffff
ofst[ 60]:err_code:0xa0202120, clock:0xffffffff
ofst[ 64]:err_code:0xa0202120, clock:0xffffffff
ofst[ 68]:err_code:0xa0202120, clock:0xffffffff
ofst[ 72]:err_code:0xa0202120, clock:0xffffffff
ofst[ 76]:err_code:0xa0202120, clock:0xffffffff
ofst[ 80]:err_code:0xa0213013, clock:0xffffffff
ofst[ 84]:err_code:0xa0202120, clock:0xffffffff
ofst[ 88]:err_code:0xa0202120, clock:0xffffffff
ofst[ 92]:err_code:0xa0202120, clock:0xffffffff
ofst[ 96]:err_code:0xa0202120, clock:0xffffffff
ofst[100]:err_code:0xa0202120, clock:0xffffffff
ofst[104]:err_code:0xa0202120, clock:0xffffffff
ofst[108]:err_code:0xa0202120, clock:0xffffffff
ofst[112]:err_code:0xa0202120, clock:0xffffffff
ofst[116]:err_code:0xa0202120, clock:0xffffffff
ofst[120]:err_code:0xa0202120, clock:0xffffffff
ofst[124]:err_code:0xa0213013, clock:0xffffffff
[mullion]$
becount
Bringup : 884 times
Shutdown: 444 times
Power-on: 34day 13hour 31min 03sec
[mullion]$
bringup
Do nothing. (FatalOff State)
bringup
*** Unknown Command ***
[mullion]$
bringup
*** Unknown Command ***
[mullion]$
becount
*** Unknown Command ***
[mullion]$
becount
Bringup : 885 times
Shutdown: 445 times
Power-on: 34day 13hour 31min 04sec
[mullion]$
bringup
Do nothing. (FatalOff State)
bringup
Do nothing. (FatalDown State)
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Sorry if im asking too many questions at once.

post 1 = First console = untouched E01 - putting 40nm 5301DGB or 5302DGB
post 2 = Second console = opened A01 - was trying orbis mod will do franken instead - has 65nm 2991GGB
post 3 = Third console = opened E01 - was trying orbis mod will do franken instead - 65nm 2991GGB

 

[RIP-Felix]

Oh! I know what I got wrong then in my calcs. In another thread, the one about the experimental NEC/TOKIN replacement methods, where you posted the release of your Tantalizer mod 0.6b, you gave a list of capacitors to use.

Now, I am not gonna use your PCB since all I have is a soldering iron to do the job, but I assume those capacitors are the actual important part of the fix, and therefore should be common even if not using the PCB and just manually soldering them.
Those 3x 470uF, 1x 47uF, 1x 2uF and so on and so on, I can safely assume that's to replace a single TOKIN. I thought the "Total cost" below was the cost for one TOKIN, so I multiplied that by 8 and got $200... Whoopsie.
After actually checking the sites you linked with examples on where to buy those caps, I can tell that now 24x 470uF caps are just ~$24, nearly not as much as the triple digits number I had in mind :^)
Thank you so much, I guess I can now safely order those caps. Appreciated

Those were example that have the correct specifications. MLCCs prices chage alot and their performance is pretty much the same. You were not meant to buy the ones linked. Simply use the linked product as a template to then go and find a good deal on a cap that has similar specifications. Also, the MLCCs are optional.

 

[RIP-Felix]

Hello PSX place users. I dumped my syscon error log and im really struggling to figure out what caused my YLoD a few years ago. System was working fine but ran hot around 2020ish. in 2022 i pulled it out of storage and it was giving the YLoD. I applied heat to the board and it brought it back but i was afraid to use it so i put it in my closet again till last week and i dumped the syscon and this is what i got. Any help would be much appreciated.
It just died again while copying some memory cards. 3 beeps and red blinking light then YLoD.

Firmware Version: 4.90 (build 50747)
Platform ID: Cok14
Product Code: 00 84
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1423, Shutdown Count: 1353
Runtime: 92 Days, 6 Hours, 54 Minutes, 9 Seconds
Error Log
01: A0801001 Fri Dec 31 23:59:59 1999
02: A0801601 Tue Jul 21 21:34:13 2009
03: A0801701 Tue Jul 21 21:34:13 2009
04: A0801001 Tue Jul 21 21:13:21 2009
05: A0801001 Tue Jul 21 20:46:19 2009
06: A0801001 Thu Jul 2 16:51:53 2009
07: A0801001 Thu Jul 2 16:19:02 2009
08: A0801001 Thu Jul 2 16:16:42 2009
09: A0801001 Thu Jul 2 16:15:54 2009
10: A0801001 Thu Jul 2 16:15:49 2009
11: A0801001 Sun Mar 2 20:29:38 2008
12: A0801001 Wed Feb 20 05:36:49 2008
13: A0801001 Fri Feb 15 05:18:53 2008
14: A0801001 Fri Feb 15 05:07:30 2008
15: A0801001 Mon Jan 28 11:17:21 2008
16: A0801001 Mon Jan 28 08:47:11 2008
17: A0801001 Mon Jan 28 08:46:51 2008
18: A0801001 Wed Sep 5 06:33:38 2007
19: A0801001 Tue Sep 4 10:08:12 2007
20: A0801001 Sat Sep 1 16:36:32 2007
21: A0801001 Mon Feb 20 10:28:13 2006
22: A0801001 Fri Feb 17 12:29:58 2006
23: A0801001 Sun Feb 12 10:30:41 2006
24: A0801001 Sun Feb 12 08:11:05 2006
25: A0902203 Tue Feb 7 06:10:53 2006
26: A0801001 Tue Feb 7 06:10:53 2006
27: A0801001 Sun Jan 1 22:48:07 2006
28: A0801001 Sat Dec 31 00:31:47 2005
29: A0801001 Sat Dec 31 00:00:09 2005
30: A0403034 Sun Jul 9 10:57:01 2006
31: A0403034 Thu Jul 6 00:27:06 2006
32: A0403034 Fri Dec 31 23:59:59 1999

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?

 

[RIP-Felix]

Does anyone know how to enable internal permissions in sherwood to allow the use of INT commands? Such as `hversion` to get the Platform_ID. @M4j0r ? Devwiki says it needs to be patched, but doesn't say how.

Edit: Found this which says `r 0 1` is the byte that has the hex value of the Platform_ID. But there was a bit about it only being for SW3 in KTE or later. I just tried it on a 2001a and it returned 61 (CECH-20xxA/B | DYN-001 | CokG11) which is correct, but I wasn't expecting it to work since this model predates the KTE. So now I'm wondering if it would work for all SW?