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

[Fallen777]

yes i know but the trace ends up under a chip then I lose it. I was talking about finding the cause by myself maybe checking the board for voltage and resistence around chips.

UPDATE: ok i found it in the service manual

you found the fault or the rx pin trace of you don't found the trace then maybe I can help

 

[Fallen777]

Hey everyone i want to know the meaning of this error code on my superslim cech 42003-A (16gb emmc) with glod issue and courrpted firmware failded installation. The error log on my superslim has only two errors repeated :
A0801200
A0802022

AND My Fat cechk04 i have ylod and these errors codes:
A0093004
A0093003
A0061002
I am attaching both error logs too.
I want to know the best cap combo for nec and also what these error codes mean.
And Thanks to Devs for the syscon uart work

 

[Fallen777]

Lots of 1200 errors, there is another cause to overheating CELL, and thats the IC buck chips. These regulate the power.
When these go bad, can cause overvoltage - causing the CELL to overheat.

That would the solution to fat and slim but superslim cell has soldered ihs then what would cause A0801200 error and glod Also if its the buck ics and is left running for atmost 2 hours or less then would cell be damaged and does the multi av ic has anything to do with hdmi display

 

[sandungas]

I just made a new page in wiki for the Syscon Error Codes

@db260179 @RIP-Felix or others interested in it, is just a draft to show other wiki editors how i think the page should be structured, there is lot of room to discuss every error code
It could be made even like the service manuals of some TV that have a "troubleshooting" sequence to follow
If error xxxx = then check this component ---> if that component is good = check this other component ---> etc...

 

[sandungas]

Hey everyone i want to know the meaning of this error code on my superslim cech 42003-A (16gb emmc) with glod issue and courrpted firmware failded installation. The error log on my superslim has only two errors repeated :
A0801200
A0802022

AND My Fat cechk04 i have ylod and these errors codes:
A0093004
A0093003
A0061002
I am attaching both error logs too.
I want to know the best cap combo for nec and also what these error codes mean.
And Thanks to Devs for the syscon uart work

Wait a bit for others to reply, they knows the error codes better than me
Btw, the superslim motherboard is a PQX-001 by any chance ?, im asking because we are trying to complete the list of Platform ID names
There is a syscon command to show the platform ID, type "hversion" and syscon will reply with the name "Cok..."

Edit: i just reminded the command "hversion" is not available (exists, but is locked) for the syscon models used in superslims, mhhh

 

[Fallen777]

Yes the motherboard of my superslim is pqx-001 with the 16gb emmc.
Ok I'll wait a bit longer afterall I finally got a clue to what made unusable after whole two years just held on it hoping someday I'll finally be able to fix it instead of giving it to some repair person or in junk just great work for syscon guys fantastic.

 

[RIP-Felix]

The error log on my superslim has only two errors repeated :
A0801200
A0802022

1200 is a CPU Overheat. Replace paste and see if it's fixed. If the repaste fails, often it's because the paste between the die/IHS is old and you have to delid to reapply. It's a common problem on Phat models. However, I'm not sure about SS. I'm not sure if SS started soldering the IHS onto the die or not? Does anyone know if you can delid a SS? I mean, if it is soldered on then the repaste will work as the solder is great thermal interface material and won't degrade, so there's no need.

2022 is a DVE Error, the CXM4024 MultiAV controller for analog out. At least it is for A models. I would clear up the overheating issue first, clear the errorlog, and try again to see if the error reappears. If it doesn't it was probably an old error. It it does return, then the AV subsystem needs troubleshooting.

EDIT: just saw you said it had corrupted FW and GLOD. If the GLOD is FW related that needs to be HW flashed to fix. And yes, I've heard of faulty VRM overvolting processors causing overheats. If that's the case the processors could be damaged. The only way to know is to probe voltages to see if they are withing proper levels, replace the VRM and any faulty SMDs if not. Double check the voltages are correct and try powering on.

AND My Fat cechk04 i have ylod and these errors codes:
A0093004
A0093003
A0061002

1002 = Filter Noise: NEC/TOKINs & Related SMD's
3003 = VDDC BE Failure.
3004 = VDDC RSX PWR Failure. NEC/TOKINs & related SMDs.

This is consistent with bad tokins. It is unusual for the tokins to get bad enough to cause the more serious 3000 errors. Usually people stop using their console once they can't play their games for more than a few minutes at a time. So the tokins either continued to degrade on their own or they were damaged.

It's important to note that the error is about the filter, which include more than just the tokins. There are other SMDs in the filter that can go bad.

 

[Fallen777]

1200 is a CPU Overheat. Replace paste and see if it's fixed. If the repaste fails, often it's because the paste between the die/IHS is old and you have to delid to reapply. It's a common problem on Phat models. However, I'm not sure about SS. I'm not sure if SS started soldering the IHS onto the die or not? Does anyone know if you can delid a SS? I mean, if it is soldered on then the repaste will work as the solder is great thermal interface material and won't degrade, so there's no need.

2022 is a DVE Error, the CXM4024 MultiAV controller for analog out. At least it is for A models. I would clear up the overheating issue first, clear the errorlog, and try again to see if the error reappears. If it doesn't it was probably an old error. It it does return, then the AV subsystem needs troubleshooting.

EDIT: just saw you said it had corrupted FW and GLOD. If the GLOD is FW related that needs to be HW flashed to fix. And yes, I've heard of faulty VRM overvolting processors causing overheats. If that's the case the processors could be damaged. The only way to know is to probe voltages to see if they are withing proper levels, replace the VRM and any faulty SMDs if not. Double check the voltages are correct and try powering on.


1002 = Filter Noise: NEC/TOKINs & Related SMD's
3003 = VDDC BE Failure.
3004 = VDDC RSX PWR Failure. NEC/TOKINs & related SMDs.

This is consistent with bad tokins. It is unusual for the tokins to get bad enough to cause the more serious 3000 errors. Usually people stop using their console once they can't play their games for more than a few minutes at a time. So the tokins either continued to degrade on their own or they were damaged.

It's important to note that the error is about the filter, which include more than just the tokins. There are other SMDs in the filter that can go bad.

Ok so 1200 will cpu overheat i did changed the thermal paste and dusted the whole board before it glodded you will have to find one of my thread to know my complete story. As for the 2022 error what will be it in ss model ihs is indeed soldered. and if vrm is overloaded how much runtime would it require to damage cpu also any photo indicating such parts.
As for the fat model i see two errors are nec related what is the be vddc failure. I assume bothe cell and rsx need nec replacement a photo telling 1002 parts would be great for all users.What about the electrolytic capacitor on nec tocheck if they are the fault,i have seen my mate vince doing thatbut not much info about specifications of those caps.

 

[RIP-Felix]

As for the 2022 error what will be it in ss model ihs is indeed soldered. and if vrm is overloaded how much runtime would it require to damage cpu also any photo indicating such parts.

After you repasted the CPU did you clear the errorlog and trigger a YLOD again? We need to be sure these are current errors.

As for the fat model i see two errors are nec related what is the be vddc failure. I assume bothe cell and rsx need nec replacement a photo telling 1002 parts would be great for all users.

VDDC is the core voltage. BE is CPU. Bad tokins can trigger a core voltage failure. That's what your 3004 RSX PWR failure is. So 3003 is the same error, but for the CPU.

In other words, all the tokins need replaced. To make this easier for people I made a PCB I call the PS3 Tantalizer. How to use it and suggested caps are linked in the release notes.

Here is a general flowchart of the CPU's VDDC filter. Please use the schematic to cross-reference everything. If you are going to fix electronics you need to get into the habit of looking at schematics and datasheets anyway.

Just to explain in a nutshell what's going on here.

1. 12v Mains comes in at the top through the electrolytic and large MLCC caps to provide power for the IOR switching VRM. Those caps filter the noise out for the VRM.
2. The iP2003APbF IOR buck converters (switching VRM) are controlled by the NCP5318 Buck CPU controller. In the picture it's on the back side of where the arrow is pointing. The arrow is actually pointing to a TC7SG08FU AND Logic gate. Anyway, It's sensing the voltage feedback and deciding when to provide power and how much. This controller is communicating with the SYSCON and other ICs and can be a source of issues. So the surrounding SMD'c need to be operating correctly (no shorts or blown fuses).
3. The VRM regulate the 12v --> 1.3v (ish). The problem is that they are noisy and introduce voltage ripple that needs to be reduced to an acceptable level (attenuated).
4. The 1st stage RC (Resistor-Capacitor) filter is a small cap/resistor whose value was deliberatly chosen to amplify the attenuation of the 2nd stage filter. If these go bad it will have a very large effect on the filter and likely cause a 3003/3004 syscon error. So these are important. Probe their resistance and check them against a working board to be sure they are not way off. If so replace them.
   
5. The 2nd stage LRC filter (Inductor-Resistor-Capacitor, where the NEC/TOKIN's are the C) is responsible for the bulk filtering. That's to remove the voltage ripple. The 1st and 2nd stages work together to amplify this reduction and all components need to be chosen (calculated) carefully to achieve optimal results. An issue here will usually cause a 1002 error. 1001 is still mysterious, but could be caused by this as well. However, it seems that 1001 is commonly caused by other issues too and is not diagnostic of bad tokins in the same way 1002 is.
   
6. Noise is filtered by an array of 36x 0.1uF MLCC capacitors on the bottom side of the PCB underneath the CPU. The caps are placed as close the he processor as possible to provide an low inductance path to ground for the noise (most efficient). They reduce coupled in noise from other electronics, radio and microwave radiation, and etc. That's why they are usually refereed to as decoupling or bypass caps.

What about the electrolytic capacitor on nec tocheck if they are the fault,i have seen my mate vince doing thatbut not much info about specifications of those caps.

Do not use electrolytic caps as a substitute for cpu decoupling capacitors! They do not have an ESR low enough for the job! Their high ESR will cause them to heat up and die. They will not last very long, if they work at all. I have seen tests work using them, and I've seen tests fail. They are totally inappropriate choice for this job anyway.

 

[Fallen777]

After you repasted the CPU did you clear the errorlog and trigger a YLOD again? We need to be sure these are current errors.



VDDC is the core voltage. BE is CPU. Bad tokins can trigger a core voltage failure. That's what your 3004 RSX PWR failure is. So 3003 is the same error, but for the CPU.

In other words, all the tokins need replaced. To make this easier for people I made a PCB I call the PS3 Tantalizer. How to use it and suggested caps are linked in the release notes.

Here is a general flowchart of the CPU's VDDC filter. Please use the schematic to cross-reference everything. If you are going to fix electronics you need to get into the habit of looking at schematics and datasheets anyway.
View attachment 35210
Just to explain in a nutshell what's going on here.

1. 12v Mains comes in at the top through the electrolytic and large MLCC caps to provide power for the IOR switching VRM. Those caps filter the noise out for the VRM.
2. The iP2003APbF IOR buck converters (switching VRM) are controlled by the NCP5318 Buck CPU controller. In the picture it's on the back side of where the arrow is pointing. The arrow is actually pointing to a TC7SG08FU AND Logic gate. Anyway, It's sensing the voltage feedback and deciding when to provide power and how much. This controller is communicating with the SYSCON and other ICs and can be a source of issues. So the surrounding SMD'c need to be operating correctly (no shorts or blown fuses).
3. The VRM regulate the 12v --> 1.3v (ish). The problem is that they are noisy and introduce voltage ripple that needs to be reduced to an acceptable level (attenuated).
4. The 1st stage RC (Resistor-Capacitor) filter is a small cap/resistor whose value was deliberatly chosen to amplify the attenuation of the 2nd stage filter. If these go bad it will have a very large effect on the filter and likely cause a 3003/3004 syscon error. So these are important. Probe their resistance and check them against a working board to be sure they are not way off. If so replace them.
   
5. The 2nd stage LRC filter (Inductor-Resistor-Capacitor, where the NEC/TOKIN's are the C) is responsible for the bulk filtering. That's to remove the voltage ripple. The 1st and 2nd stages work together to amplify this reduction and all components need to be chosen (calculated) carefully to achieve optimal results. An issue here will usually cause a 1002 error. 1001 is still mysterious, but could be caused by this as well. However, it seems that 1001 is commonly caused by other issues too and is not diagnostic of bad tokins in the same way 1002 is.
   
6. Noise is filtered by an array of 36x 0.1uF MLCC capacitors on the bottom side of the PCB underneath the CPU. The caps are placed as close the he processor as possible to provide an low inductance path to ground for the noise (most efficient). They reduce coupled in noise from other electronics, radio and microwave radiation, and etc. That's why they are usually refereed to as decoupling or bypass caps.

Do not use electrolytic caps as a substitute for cpu decoupling capacitors! They do not have an ESR low enough for the job! Their high ESR will cause them to heat up and die. They will not last very long, if they work at all. I have seen tests work using them, and I've seen tests fail. They are totally inappropriate choice for this job anyway.

Yay great post I'll test when I get a multimeter current one has LCD ghosting problem. But as I said

you will have to find one of my thread to know my complete story

I'll post a my sad story link here that will give the entire detail my superslim model.
https://www.psx-place.com/threads/ps3-cech4203a-super-slim-firmware-halted.27178/#post-218393

Its really long read but still will help both of us in some way.

 

[sandungas]

Yes the motherboard of my superslim is pqx-001 with the 16gb emmc.

Ohh, then is one of the unknown platform ID models, please can you run this command ?

> r 1 6

The command is going to display 6 bytes, copy and paste them here
Or paste them in a hexeditor to convert them to "readable" format, it should tell "Cok something"


I reminded we was doing it that way before, is a handy trick to bypass the restriction of the missing "hversion" command
https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/page-4#post-292692

 

[Fallen777]

Ohh, then is one of the unknown platform ID models, please can you run this command ?

> r 1 6

The command is going to display 6 bytes, copy and paste them here
Or paste them in a hexeditor to convert them to "readable" format, it should tell "Cok something"


I reminded we was doing it that way before, is a handy trick to bypass the restriction of the missing "hversion" command
https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/page-4#post-292692

Ok I can try but will have to told how after getting auth and what software to be installed first I have no python or anything right now and this command is just readonly and harmless right and I wanted to know of there's any command to clear/reset syscon error log on Sherwood sys ons.

 

[Fallen777]

After you repasted the CPU did you clear the errorlog and trigger a YLOD again? We need to be sure these are current errors.



VDDC is the core voltage. BE is CPU. Bad tokins can trigger a core voltage failure. That's what your 3004 RSX PWR failure is. So 3003 is the same error, but for the CPU.

In other words, all the tokins need replaced. To make this easier for people I made a PCB I call the PS3 Tantalizer. How to use it and suggested caps are linked in the release notes.

Here is a general flowchart of the CPU's VDDC filter. Please use the schematic to cross-reference everything. If you are going to fix electronics you need to get into the habit of looking at schematics and datasheets anyway.
View attachment 35210
Just to explain in a nutshell what's going on here.

1. 12v Mains comes in at the top through the electrolytic and large MLCC caps to provide power for the IOR switching VRM. Those caps filter the noise out for the VRM.
2. The iP2003APbF IOR buck converters (switching VRM) are controlled by the NCP5318 Buck CPU controller. In the picture it's on the back side of where the arrow is pointing. The arrow is actually pointing to a TC7SG08FU AND Logic gate. Anyway, It's sensing the voltage feedback and deciding when to provide power and how much. This controller is communicating with the SYSCON and other ICs and can be a source of issues. So the surrounding SMD'c need to be operating correctly (no shorts or blown fuses).
3. The VRM regulate the 12v --> 1.3v (ish). The problem is that they are noisy and introduce voltage ripple that needs to be reduced to an acceptable level (attenuated).
4. The 1st stage RC (Resistor-Capacitor) filter is a small cap/resistor whose value was deliberatly chosen to amplify the attenuation of the 2nd stage filter. If these go bad it will have a very large effect on the filter and likely cause a 3003/3004 syscon error. So these are important. Probe their resistance and check them against a working board to be sure they are not way off. If so replace them.
   
5. The 2nd stage LRC filter (Inductor-Resistor-Capacitor, where the NEC/TOKIN's are the C) is responsible for the bulk filtering. That's to remove the voltage ripple. The 1st and 2nd stages work together to amplify this reduction and all components need to be chosen (calculated) carefully to achieve optimal results. An issue here will usually cause a 1002 error. 1001 is still mysterious, but could be caused by this as well. However, it seems that 1001 is commonly caused by other issues too and is not diagnostic of bad tokins in the same way 1002 is.
   
6. Noise is filtered by an array of 36x 0.1uF MLCC capacitors on the bottom side of the PCB underneath the CPU. The caps are placed as close the he processor as possible to provide an low inductance path to ground for the noise (most efficient). They reduce coupled in noise from other electronics, radio and microwave radiation, and etc. That's why they are usually refereed to as decoupling or bypass caps.

Do not use electrolytic caps as a substitute for cpu decoupling capacitors! They do not have an ESR low enough for the job! Their high ESR will cause them to heat up and die. They will not last very long, if they work at all. I have seen tests work using them, and I've seen tests fail. They are totally inappropriate choice for this job anyway.

By the way @RIP-Felix on the pqx-001 motheboard emmc model is the vrm on top of cell and rsx and can I just replace the parts from a dead board probably one that been taken to direct reflow . I pretty myc think playing ps2 classics did the strain on my boards vrm .I remember reading cell and rex both have to work too much for playing ps2.

 

[Shawn Shakir]

Hey all, this is my current errors from Syscon.

===================================
ERR 00: 00000000 A0092113 0B55F683
ERR 01: 00000000 A0092113 0B55F33B
ERR 02: 00000000 A0092113 0B55AE06
ERR 03: 00000000 A0092113 0B55AE02
ERR 04: 00000000 A0092113 0B548C12
ERR 05: 00000000 A0092113 0B548AD8
ERR 06: 00000000 A0092113 0B548AD3
ERR 07: 00000000 A0092113 0B548A73
ERR 08: 00000000 A0092113 0B548A70
ERR 09: 00000000 A0092113 0B548A6B
ERR 10: 00000000 A0092113 0B5489DB
ERR 11: 00000000 A0092113 0B5489C7
ERR 12: 00000000 A0092113 0B5489BF
ERR 13: 00000000 A0092113 0B5489B5
ERR 14: 00000000 A0092113 0B5489AF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0202120 FFFFFFFF
ERR 17: 00000000 A0202120 FFFFFFFF
ERR 18: 00000000 A0202120 FFFFFFFF
ERR 19: 00000000 A0202120 FFFFFFFF
===================================

Console was YLOD, reballed it about 2 weeks ago from previous syscon readings showing bad RSX. Didnt have time to really test it until earlier this week. Ran it for about 2 hours and it ran fine, no issues. Turned it on yesterday at instant YLOD. I don't see anything on the 2113 other than clock 4, just not sure what that means. Any advice?

 

[sandungas]

By the way @RIP-Felix on the pqx-001 motheboard emmc model is the vrm on top of cell and rsx and can I just replace the parts from a dead board probably one that been taken to direct reflow . I pretty myc think playing ps2 classics did the strain on my boards vrm .I remember reading cell and rex both have to work too much for playing ps2.

I dont know any link for a tutorial specific for sherwood syscons (the syscons with pins all around) but in short... are this steps:

1) Install python v2.7 (as far i remember the python script that you need to run later was updated to work on python 3.x too, but i would install v2.7 just incase)

2) Download the python script named ps3_syscon_uart_script.py from this link https://github.com/db260179/ps3syscon

3) Go to the "device manager" in windows with the USB-to-UART adapter connected to ther PC... and search for it to find his port name... lets say is named COM3

4) Open a terminal window and type "ps3_syscon_uart_script.py COM3 SW"... this should authenticate you with your syscon SW located at port COM3

If everything went fine you can run the commands that appears in this lists https://www.psdevwiki.com/ps3/Syscon_Firmware#Command_list
Keep in mind some of the commands in mullion (the syscons without pins all around) was removed in sherwoord (the syscons with pins all around), and some others are locked
To show the errors you need to type "errlog"... and to delete them type "clearerrlog" (or ERRLOG CLEAR in uppercase)


*You can also make a dump of all the accesible areas by running the other script in github named SysconEEPdumpSW.py

 

[RIP-Felix]

Hey all, this is my current errors from Syscon.

===================================
ERR 00: 00000000 A0092113 0B55F683
ERR 01: 00000000 A0092113 0B55F33B
ERR 02: 00000000 A0092113 0B55AE06
ERR 03: 00000000 A0092113 0B55AE02
ERR 04: 00000000 A0092113 0B548C12
ERR 05: 00000000 A0092113 0B548AD8
ERR 06: 00000000 A0092113 0B548AD3
ERR 07: 00000000 A0092113 0B548A73
ERR 08: 00000000 A0092113 0B548A70
ERR 09: 00000000 A0092113 0B548A6B
ERR 10: 00000000 A0092113 0B5489DB
ERR 11: 00000000 A0092113 0B5489C7
ERR 12: 00000000 A0092113 0B5489BF
ERR 13: 00000000 A0092113 0B5489B5
ERR 14: 00000000 A0092113 0B5489AF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0202120 FFFFFFFF
ERR 17: 00000000 A0202120 FFFFFFFF
ERR 18: 00000000 A0202120 FFFFFFFF
ERR 19: 00000000 A0202120 FFFFFFFF
===================================

Console was YLOD, reballed it about 2 weeks ago from previous syscon readings showing bad RSX. Didnt have time to really test it until earlier this week. Ran it for about 2 hours and it ran fine, no issues. Turned it on yesterday at instant YLOD. I don't see anything on the 2113 other than clock 4, just not sure what that means. Any advice?

2113 is a Clock Generator Error on IC5004. Probe the caps and resistors around it. Check voltages are present when turning on. Check against a working board to see what nominal values are and get a feel for when the voltages are supposed to appear.

A 3013 has been reported to be BE_SPI DI/DO ERROR. CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead? @Kleon1876 had one on a CPU he damaged while deliding.

My guess is that the Reball on the RSX may have damaged the BGA on the CPU, based on the history of the console you provided. How was the reball performed?

 

[Shawn Shakir]

2113 is a Clock Generator Error on IC5004. Probe the caps and resistors around it. Check voltages are present when turning on. Check against a working board to see what nominal values are and get a feel for when the voltages are supposed to appear.

A 3013 has been reported to be BE_SPI DI/DO ERROR. CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead? @Kleon1876 had one on a CPU he damaged while deliding.

My guess is that the Reball on the RSX may have damaged the BGA on the CPU, based on the history of the console you provided. How was the reball performed?

Console was a gamestop refurb but looks like I was the first person to repair it. Used my ACHI IR PRO, ended up using a replacement RSX from Aliexpress. Not sure if that would be the culrpit or not. As i stated, after reflowing on new RSX, console worked fine for a few hours and then I turned it off. Turned it on yesterday to YLOD. Didn't attempt to delid CELL while doing the repair. Hadn't done one before, so I didn't want to try on a backwards console. Will check voltages and see what I can get going.

 

[Fallen777]

I dont know any link for a tutorial specific for sherwood syscons (the syscons with pins all around) but in short... are this steps:

1) Install python v2.7 (as far i remember the python script that you need to run later was updated to work on python 3.x too, but i would install v2.7 just incase)

2) Download the python script named ps3_syscon_uart_script.py from this link https://github.com/db260179/ps3syscon

3) Go to the "device manager" in windows with the USB-to-UART adapter connected to ther PC... and search for it to find his port name... lets say is named COM3

4) Open a terminal window and type "ps3_syscon_uart_script.py COM3 SW"... this should authenticate you with your syscon SW located at port COM3

If everything went fine you can run the commands that appears in this lists https://www.psdevwiki.com/ps3/Syscon_Firmware#Command_list
Keep in mind some of the commands in mullion (the syscons without pins all around) was removed in sherwoord (the syscons with pins all around), and some others are locked
To show the errors you need to type "errlog"... and to delete them type "clearerrlog" (or ERRLOG CLEAR in uppercase)


*You can also make a dump of all the accesible areas by running the other script in github named SysconEEPdumpSW.py

Or to make it short and simple I'll just have to install python and connect ps3 superslim to ttl Hart converter to PC and authenticate with syscon reader gui then run both the command you requested and the syscon dump script right.Well there's few question for you will dumping whole syscon also dumps your requested id too and does clearing errorlog gonna make console both for once too.Any way storage memory contents can be read and flashed via syscon just curious.I do it today hope it works.Anything science right.

 

[RIP-Felix]

Hmm...I do like that station. I'm actually looking into making my own DIY station using that PC410 process controller. How do you like it?

As for the errors, is the 2113 the only error occurring? Can you clear the log and be sure what the current error is.

I have been suspecting clock generator errors with bad/dying cpu's, but that's only a hypothese (a weak hunch at that). It's possable the RSX was dodgy (I wouldnt trust ali express RSX chips). What model PS3 was this again? Because if it was a 90nm rsx Im suprised you even found one. If it was one of those NOS CXD5301's then that's another story. I got some from ebay and have good results. However while watching a LTT video recently they brought up a good point about binned PS5 APU's that concerns me about NOS processors. Chips that dont meet the quality standards for a PS5 are still good chips and could be used. So some PC manufacturers are integrating them into desktop motherboards Pretty bad computers (not enough pcie lanes), but they're e-waste otherwise. Anyway that could explain the NOS 40nm RSX chips still out there. If they didnt meet quality standards necessary to be integrated into a slim model PS3 they would be left over. That may not be an issue for frankenstein consoles actually, since they can handle extra voltage and heat dissipation less efficient chips might require. But they may not work on slim consoles. This is just a hypothesis, but I thought Id mention it.

 

[Shawn Shakir]

Hmm...I do like that station. I'm actually looking into making my own DIY station using that PC410 process controller. How do you like it?

As for the errors, is the 2113 the only error occurring? Can you clear the log and be sure what the current error is.

I have been suspecting clock generator errors with bad/dying cpu's, but that's only a hypothese (a weak hunch at that). It's possable the RSX was dodgy (I wouldnt trust ali express RSX chips). What model PS3 was this again? Because if it was a 90nm rsx Im suprised you even found one. If it was one of those NOS CXD5301's then that's another story. I got some from ebay and have good results. However while watching a LTT video recently they brought up a good point about binned PS5 APU's that concerns me about NOS processors. Chips that dont meet the quality standards for a PS5 are still good chips and could be used. So some PC manufacturers are integrating them into desktop motherboards Pretty bad computers (not enough pcie lanes), but they're e-waste otherwise. Anyway that could explain the NOS 40nm RSX chips still out there. If they didnt meet quality standards necessary to be integrated into a slim model PS3 they would be left over. That may not be an issue for frankenstein consoles actually, since they can handle extra voltage and heat dissipation less efficient chips might require. But they may not work on slim consoles. This is just a hypothesis, but I thought Id mention it.

I've actually had it for probably well over 5 years now. I have reflowed and reballed a ton of 360's throughout the years. I think in total I reflowed about 3 PS3 consoles and this was my first reball, well in guess replacement RSX. I was going to try the Frankenstein on it, but I couldn't delid the CXD5301 and ended up breaking the chip in half. As for the 90nm, I got a few from Aliexpress and I tested the Ohm's on them and they looked like they were in range of working from what I gathered from YouTube videos, but this is also my true first time getting into the entire world of PS3 repairs, so all of this is truley new to me.

The console is a CECHA01. How would I go about clearing the log, is that like just deleting the .txt file generated and running a new read or is it something more in depth?

I have another A01 that I beleive is YLOD that i'm gonna try frankensteing. I saw you mentioned in the thread about leaving the IHS on, just gonna have to go alittle passed 225 on my top heat to get it down, but it's worth the shot!