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

I'm getting a 2022 on a CECHL01 too. I tested the AV cable and it worked. The HDMI works, but it does not display in 1080p at all. It will display in 480p, 720p, and 1080i. If Deep Color Output is on, 720p and 1080i have very bad screen flickering.

Firmware Version: 4.89 (50740)
Platform ID: CokF10
Hardware Config: 4E00FFFF0307BCBF
Syscon Fimware Version: 065D.0000000000000000 (0000000000000000)

Bringup Count: 2755, Shutdown Count: 2618
Runtime: 264 Days, 14 Hours, 51 Minutes, 7 Seconds

Error Log
01: A0802022 Thu Nov 7 08:59:03 2019
02: A0802022 Thu Nov 7 08:53:25 2019
03: A0802022 Thu Nov 7 08:51:00 2019
04: A0802022 Thu Nov 7 08:45:57 2019
05: A0802022 Thu Nov 7 06:47:41 2019
06: A0802022 Thu Nov 7 06:36:55 2019
07: A0802022 Wed Nov 6 11:41:14 2019
08: A0802022 Wed Nov 6 11:37:48 2019
09: A0802022 Wed Nov 6 11:27:01 2019
10: A0802022 Wed Nov 6 11:23:51 2019
11: A0802022 Wed Nov 6 11:19:19 2019
12: A0802022 Wed Nov 6 11:10:41 2019
13: A0802022 Wed Nov 6 11:03:38 2019
14: A0802022 Wed Nov 6 11:02:21 2019
15: A0802131 Sun Mar 15 05:53:40 2015
16: A0802031 Sun Mar 15 05:53:34 2015
17: A0802022 Sun Mar 15 05:26:39 2015

I bought this one used, so I don't know what the issue was or how it was fixed. All I know is how it works now, and I've turned it on and was able to install custom firmware. The bluray drive is also bad on this one. The previous owner took it apart and applied thermal paste to chip lids. I wonder what led to the 2031/2131 error, and if the system was ever booted up/played long enough to trigger it again or not. It's a mystery! Anything I should try to do? Try to overheat it by playing a game or something?
 
I can also confirm error 2022 being reported appearing, on different firmware versions and from different years.

Firmware Version: 4.89 (build 50740)
Platform ID: CokB10
Product Code: 00 85
Product Sub Code: 00 03
Hardware Config: 20000000FFFFFEFF
Syscon Fimware Version: 0C16.0001000100030003 (EEPROM: 0001000100030003)
Bringup Count: 499, Shutdown Count: 491
Runtime: 31 Days, 3 Hours, 41 Minutes, 21 Seconds
Error Log
01: A0801001 Fri Dec 6 14:54:00 2013
02: A0801001 Fri Nov 15 22:00:18 2013
03: A0801004 Sun Feb 3 17:53:30 2008
04: A0801004 Sun Nov 25 18:25:34 2007
05: A0802022 Sat Jul 28 15:45:52 2007
06: A0802022 Sat Jul 28 15:31:45 2007
07: A0802022 Sun Jul 22 09:32:16 2007
08: A0802022 Sat Jul 14 19:52:43 2007
09: A0802022 Thu Jul 12 17:38:17 2007
10: A0802022 Sat Jul 7 13:58:28 2007
11: A0802022 Thu Jul 5 16:05:11 2007
12: A0802022 Sun Jun 3 16:10:29 2007
13: A0802022 Sat Jun 2 18:33:04 2007
14: A0802022 Sat Jun 2 17:08:07 2007
15: A0802022 Sat Jun 2 17:03:34 2007
16: A0802022 Sat Jun 2 13:36:18 2007
17: A0802022 Sat May 26 16:12:04 2007
18: A0802022 Sat May 26 14:36:10 2007
19: A0802022 Thu May 24 21:41:28 2007
20: A0802022 Thu May 24 19:03:20 2007
21: A0802022 Thu May 24 06:08:55 2007
22: A0802022 Sat May 19 00:00:32 2007
23: A0802022 Sat May 19 00:00:32 2007
24: A0802022 Fri May 18 16:49:11 2007
25: A0802022 Fri May 18 16:49:11 2007
26: A0802022 Fri May 18 13:36:25 2007
27: A0802022 Fri May 18 13:36:25 2007
28: A0801004 Wed Feb 14 11:44:16 2007
29: A0801004 Wed Feb 14 11:37:01 2007
30: A0801001 Wed Feb 14 11:28:32 2007
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999

Firmware Version: 4.84 (build 50696)
Platform ID: CokF10
Product Code: 00 82
Product Sub Code: 00 08
Hardware Config: 4E00FFFF0307BCBF
Syscon Fimware Version: 065D.0000000000000000 (EEPROM: 0000000000000000)
Bringup Count: 2013, Shutdown Count: 1948
Runtime: 202 Days, 13 Hours, 0 Minutes, 27 Seconds
Error Log
01: A0801601 Sun Jan 1 00:46:26 2006
02: A0801701 Sun Jan 1 00:46:25 2006
03: A0802022 Sun Jan 1 00:14:10 2006
04: A0802022 Sun Jan 1 00:12:56 2006
05: A0801601 Sun Jan 1 00:01:08 2006
06: A0801701 Sun Jan 1 00:01:08 2006
07: A0801601 Sun Jan 1 01:32:42 2006
08: A0801701 Sun Jan 1 01:32:42 2006
09: A0801601 Sun Jan 1 01:24:13 2006
10: A0801701 Sun Jan 1 01:24:13 2006
11: A0801601 Sun Jan 1 01:22:51 2006
12: A0801701 Sun Jan 1 01:22:50 2006
13: A0801601 Sun Jan 1 01:21:22 2006
14: A0801701 Sun Jan 1 01:21:21 2006
15: A0802022 Sun Jan 15 05:42:11 2006
16: A0802022 Sun Jan 15 05:35:23 2006
17: A0802022 Sun Jan 1 00:09:16 2006
18: A0802022 Sun Jan 1 00:08:31 2006
19: A0802022 Thu Jan 5 01:13:23 2006
20: A0802022 Thu Jan 5 01:10:03 2006
21: A0802022 Wed Jan 4 02:37:34 2006
22: A0802022 Wed Jan 4 02:36:29 2006
23: A0802022 Tue Jan 3 03:05:30 2006
24: A0802022 Tue Jan 3 03:04:04 2006
25: A0802022 Tue Jan 3 01:16:13 2006
26: A0802022 Tue Jan 3 01:11:34 2006
27: A0802022 Sun Jan 1 22:52:27 2006
28: A0802022 Sun Jan 1 22:51:40 2006
29: A0802130 Wed Mar 3 02:51:02 2010
30: A0802130 Wed Mar 3 02:51:00 2010
31: A0802130 Wed Mar 3 02:50:54 2010
32: FFFFFFFF Fri Dec 31 23:59:59 1999

Both users reported issues with the console not being able to start (YLOD), but both confirmed that the HDMI video output worked just fine prior to the YLOD. There's unfortunately no information about the analog output.

Also when I bought a Super Slim model quite recently, it had error 2022 three times in the log from the year 2014:
Error Log
01: A0802022 Tue Nov 25 22:17:50 2014
02: A0802022 Tue Nov 25 22:17:50 2014
03: A0802022 Tue Nov 25 22:17:49 2014
04: FFFFFFFF Fri Dec 31 23:59:59 1999
05: FFFFFFFF Fri Dec 31 23:59:59 1999
06: FFFFFFFF Fri Dec 31 23:59:59 1999
07: FFFFFFFF Fri Dec 31 23:59:59 1999
08: FFFFFFFF Fri Dec 31 23:59:59 1999
09: FFFFFFFF Fri Dec 31 23:59:59 1999
10: FFFFFFFF Fri Dec 31 23:59:59 1999
11: FFFFFFFF Fri Dec 31 23:59:59 1999
12: FFFFFFFF Fri Dec 31 23:59:59 1999
13: FFFFFFFF Fri Dec 31 23:59:59 1999
14: FFFFFFFF Fri Dec 31 23:59:59 1999
15: FFFFFFFF Fri Dec 31 23:59:59 1999
16: FFFFFFFF Fri Dec 31 23:59:59 1999
17: FFFFFFFF Fri Dec 31 23:59:59 1999
18: FFFFFFFF Fri Dec 31 23:59:59 1999
19: FFFFFFFF Fri Dec 31 23:59:59 1999
20: FFFFFFFF Fri Dec 31 23:59:59 1999
21: FFFFFFFF Fri Dec 31 23:59:59 1999
22: FFFFFFFF Fri Dec 31 23:59:59 1999
23: FFFFFFFF Fri Dec 31 23:59:59 1999
24: FFFFFFFF Fri Dec 31 23:59:59 1999
25: FFFFFFFF Fri Dec 31 23:59:59 1999
26: FFFFFFFF Fri Dec 31 23:59:59 1999
27: FFFFFFFF Fri Dec 31 23:59:59 1999
28: FFFFFFFF Fri Dec 31 23:59:59 1999
29: FFFFFFFF Fri Dec 31 23:59:59 1999
30: FFFFFFFF Fri Dec 31 23:59:59 1999
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999

Since then, the same error appeared at least twice (with proper timestamp) when the screen went to black (HDMI) during homebrew / game startup and never came back. I had to pull the power cord to reboot it, and it got caught instantly together with error 1004 on the next startup (by my own VSH plugin). No problems since then, HDMI works just fine. Don't have the cables required to test AV output, though.
 
Hello all,

Can I please pick your brains for an issue I'm having with a SEM-001 board.

The board has YLOD, error 3034. I de-lidded both the RSX and the CELL (successfully this time!) then attempted a reflow on the RSX. However, still YLOD at power up.

I tried re-connecting to Syscon but it would not connect. The Syscon wires were a bit mangled by the reflow so I replaced them.

At first, the PS3 would go from RED to GREEN after power was applied (no action on my end) with a beep, but no fan, no activity.
I checked the Syscon cables multiple times (under the microscope). Eventually I decided to remove them to test.

The IHS have not moved. I do not see anything shorting or misplaced.

Any ideas please?
Thank you!
 
Last edited:
Adding a quick video to show the issue. I can tell you that 12V is not being switched on. The green light comes up by itself and nothing happens: no fans, no nothing. Buttons are not working. I am unable to connect to syscon either.

 
Tony359 said:
Hello all,
...attempted a reflow on the RSX. However, still YLOD at power up.
Click to expand...

"Attempted" ?

Sucessfully or not? By that I mean, did you confirm the balls actually reflowed by gently nudging the chip to see if it wiggles? It can be difficult to get the chip to reflow, so it is important the know for sure it did flow.

Of course, reflows suck. You know that. It should go without saying at this point. Yet you chose to do it anyway. SMH, but I'll just move on from that point.

I had something similar happen with a dodgy pwr/ejt board in COK-001, which was solved by replacing it. Can't do that with sem tho. Another possability id the BD ribbon cable. I've seen it autostart the console when not seated correctly. Try a different ribbon cable, or if BD isn't plugged in, check the pins aren't shorting somewhere.

As for not being able to connect to syscon, I've had that happen when the pads degrade, have a bad connection. I had it on one console that was totally effed by reflows. Must have been catastrophic interlayer delam, or something...I never got a real answer.
 
Thank you!

Let me be honest with you: when it's time to nudge the chip I get so nervous that my hands start shaking and I don't want to touch the chip as I would surely misplace it. :)
But I don't think I managed to flow it and then I had to stop to avoid damage.

I think I made a couple of mistakes in my reflow:
1. hot air temp was too low (I didn't account for the massive 45x45 nozzle, temps would be much lower when reaching the chip
2. Nozzle slightly smaller than needed - mine was 45x45 but externally. Internally it was JUST the size of the chip so the nozzle had to be just above the chip.
3. Given the size of the nozzle I should have pushed the air to the max 200L/m probably. I stayed around 100/120 and I feel that that was not enough.

That said I've read of people able to reball with my older Ayoue station which is 40L/m and of exceptional uneven heat uniformity!

Pre-heating was on and the board was at 180C when started.

I know re-flowing those large chips is not easy. Just out of curiosity, did I have another choice?

The board worked as usual (YLOD) when I first tested it. Then it started doing that. BD was not connected, I can check the pins but I suspect that would start the whole board (12V and fans) while in my case that is what happens: green light and that's it. I can still check that though.

I re-soldered the syscon wires three times (under the microscope). I can try again of course but I am not optimistic.
 
Last edited:
Hey guys. I currently am working on diagnosing and fixing a COK-001 motherboard and I keep receiving 2030 and 2031 errors indicating a thermal sensor error. I know that both of those sensors are powered by the 3.3V misc line, but when I measured the voltage on the regulator, it said 2.9v. Is this voltage close enough or did I locate part of the problem? If the latter, how do I fix the voltage?
 
Hey,

About "Voltage and Regulation" and "Power Control", as @RIP-Felix found out 1.0V_BE_VDDC and 1.2V_RSX_VDDC
are converted with the IC6103 and IC6201 converter.

Seems like the syscon is controlling those. I've got the console booting up, and showing the boot animation but the
1.0V_BE_VDDC stick to 1.14V (I think it should be 1.0V). The feedback seems ok, the 1.2V_RSC_VDDC is correct at 1.2V.

VID0-5 for the BE is the following: 010110b does that rings a bell to anybody? I don't have that PS3 version working to compare.

This is a COK-002 CECHC04 which where previously YLOD (a0403034, a0404412).
I wanted to try a reball and pre-bake it for 8hrs to avoid VRAM to jump out :).. but finally just repowered it just to see..
 
katmai said:
Hey,

About "Voltage and Regulation" and "Power Control", as @RIP-Felix found out 1.0V_BE_VDDC and 1.2V_RSX_VDDC
are converted with the IC6103 and IC6201 converter.

Seems like the syscon is controlling those. I've got the console booting up, and showing the boot animation but the
1.0V_BE_VDDC stick to 1.14V (I think it should be 1.0V). The feedback seems ok, the 1.2V_RSC_VDDC is correct at 1.2V.

VID0-5 for the BE is the following: 010110b does that rings a bell to anybody? I don't have that PS3 version working to compare.

This is a COK-002 CECHC04 which where previously YLOD (a0403034, a0404412).
I wanted to try a reball and pre-bake it for 8hrs to avoid VRAM to jump out :).. but finally just repowered it just to see..
Click to expand...
RSX will often measure 1.3v and CPU around 1.2v. It's normal.

That VID can be checked in the data sheet for the buck controller IC. The way the datasheet lists them is annoying. They have it in the order of 4, 3, 2, 1, 0, 5. So your VID would corespond to 110100 which has a nominal voltage of 1.2125v. But there are other factors that influence your reading. Regardless, it seems fine.

The CPU and RSX will dynamically request the voltage they require to remain stable.
 
I'm going to ask a silly question here I guess. Are there schematics or guides on what to measure and what to look for on a PS3 PCB?
 
Alright, after digging a little further into the Pulse CLK guide written by RIP-Felix (thank you for that btw), I can see that the test point in question doesn't receive any voltage kick at all. While this does help eliminate some scenarios, where should I be looking next for the real problem?
 
So I have a PlayStation 3 backwards compatible model showing a GLOD and sometimes a YLOD 2102 error. A little investigation indicates that this code is believed to be a RSX issue.

Now please hear me out, why has pressure on the CPU booted the console?? It not only boots the console it's running really well with very low temperatures. It boots when it's cold, it boots when it's hot, it always boots I have played it now for over 20 hours with no sign of it failing. My aim was to get to the bottom of why a console that supposedly has a failing RSX is running GOW3 and TLOU with no issues at all after pressure has been clamped in behind the CPU, (see link at the end of this post)

So what's going on?? Have we missed something because all I hear about is how the RSX is definitely responsible and people just tell me I'm a fool for even suggesting the CPU may have a bigger part to play in this than people seem to realise.

I now have 10 consoles that friends and family are using and they all still work with this modification. I have had some that needed a video reset but after that the console continues to work. (webman is used in all 10 consoles keeping both the cpu and RSX under 64 degrees) What's going here?? How can pressure behind the CPU fix a failing RSX issue??

I have now had this mod work on consoles showing graphic anomalies, consoles that won't boot or can not connect to a controller and now a console showing both a YLOD and a GLOD. These consoles are clocking up hundreds of hours of gaming and the only downside was in the summer months when it was hot 3 out of the 10 consoles needed a video reset to boot up again.

Is this a spanner in the works, has anyone to date had a frankenstian die again, and if they haven't will they because it seems that the CPU may also need a re-ball and the heat from the frankie is temporarily fixing the CPU BGA issue.

And yes I know this is not a true fix, a true fix is a re-ball but what this highlights is that the re-ball maybe required on the CPU as well as the RSX, or frankie

 
Last edited:
Heya, i have a PS3 phat CECHK03 that ive been working on.
Its problem: When turned on, fan goes full speed for a few sec then dies down, but slowly ramps up over a couple min until it shuts off with flashing red light
bought a serial chip and soldered it in to check the errors on the syscon chip. heres what i found:
  1. ofst[ 84]:err_code:0xffffffff, clock:0x2afb6061 2022/11/07 06:21:21
    ofst[ 88]:err_code:0xa0202120, clock:0x2afb6062 2022/11/07 06:21:22
    ofst[ 92]:err_code:0xa0202120, clock:0x2afb6063 2022/11/07 06:21:23
    ofst[ 96]:err_code:0xa0202120, clock:0x2afb6064 2022/11/07 06:21:24
    ofst[100]:err_code:0xa0801200, clock:0x2afb6064 2022/11/07 06:21:24
    ofst[104]:err_code:0xa0902203, clock:0x2afb6064 2022/11/07 06:21:24
    ofst[108]:err_code:0xa0202120, clock:0x2afb6070 2022/11/07 06:21:36
    ofst[112]:err_code:0xa0202120, clock:0x2afb6071 2022/11/07 06:21:37
    ofst[116]:err_code:0xa0202120, clock:0x2afb6072 2022/11/07 06:21:38
    ofst[120]:err_code:0xa0202120, clock:0x2afb6073 2022/11/07 06:21:39
    ofst[124]:err_code:0xa0202120, clock:0x2afb6074 2022/11/07 06:21:40
    ofst[ 0]:err_code:0xa0202120, clock:0x2afb6075 2022/11/07 06:21:41
    ofst[ 4]:err_code:0xa0202120, clock:0x2afb6076 2022/11/07 06:21:42
    ofst[ 8]:err_code:0xa0202120, clock:0x2afb6076 2022/11/07 06:21:42
    ofst[ 12]:err_code:0xa0202120, clock:0x2afb6077 2022/11/07 06:21:43
    ofst[ 16]:err_code:0xa0202120, clock:0x2afb6078 2022/11/07 06:21:44
    ofst[ 20]:err_code:0xa0801200, clock:0x2afb6078 2022/11/07 06:21:44
    ofst[ 24]:err_code:0xa0202120, clock:0x2b0b6d43 2022/11/19 10:32:35
    ofst[ 28]:err_code:0xa0202120, clock:0x2b0b6d44 2022/11/19 10:32:36
    ofst[ 32]:err_code:0xa0202120, clock:0x2b0b6d45 2022/11/19 10:32:37
    ofst[ 36]:err_code:0xa0202120, clock:0x2b0b6d46 2022/11/19 10:32:38
    ofst[ 40]:err_code:0xa0202120, clock:0x2b0b6d46 2022/11/19 10:32:38
    ofst[ 44]:err_code:0xa0202120, clock:0x2b0b6d47 2022/11/19 10:32:39
    ofst[ 48]:err_code:0xa0202120, clock:0x2b0b6d48 2022/11/19 10:32:40
    ofst[ 52]:err_code:0xa0202120, clock:0x2b0b6d49 2022/11/19 10:32:41
    ofst[ 56]:err_code:0xa0202120, clock:0x2b0b6d4a 2022/11/19 10:32:42
    ofst[ 60]:err_code:0xa0202120, clock:0x2b0b6d4b 2022/11/19 10:32:43
    ofst[ 64]:err_code:0xa0802020, clock:0x2b0b6d55 2022/11/19 10:32:53
    ofst[ 68]:err_code:0xa0802020, clock:0x2b0b6d56 2022/11/19 10:32:54
    ofst[ 72]:err_code:0xa0802020, clock:0x2b0b6d57 2022/11/19 10:32:55
    ofst[ 76]:err_code:0xa0801200, clock:0x2b0b6d57 2022/11/19 10:32:55
    ofst[ 80]:err_code:0xa0902020, clock:0x2b0b6d58 2022/11/19 10:32:56


    So codes 2020, 1200 and 2120:
    2020 (HDMI)
    2120 (HDMI)
    1200 (Thermal CELL)

    Alright, easy. HDMI chip is busted, but console should boot without that right?
    CPU however is the issue im assuming. I put the console back together enough to test (with thermal paste) and it still did the
fan ramping up thing. so now i suspect its the thermal compound under the IHS, which means i need to delid the chip and replace that
Would you agree? thoughts?
I also did fan test by holding eject and turning on PSU, and then tried to get into LED diagnostic mode but it wouldnt work.
 
Yes, you definitely need the CELL to be de-lidded, however if you haven't de-lidded a CELL before I strongly suggest you don't, unless you have some scrap boards to practice on.

The other errors codes I have had on another console and both HDMI and AV worked fine, so although it's possible your HDMI is faulty you may find it boots once the CELL issue has been resolved.
 
Timbo9876 said:
Yes, you definitely need the CELL to be de-lidded, however if you haven't de-lidded a CELL before I strongly suggest you don't, unless you have some scrap boards to practice on.

The other errors codes I have had on another console and both HDMI and AV worked fine, so although it's possible your HDMI is faulty you may find it boots once the CELL issue has been resolved.
Click to expand...
Alright sounds good. i have a bunch of other PS3s to fix so ill practice de-lidding on any of those that arent fixable.
for the HDMI, just replacing the controller chip is usually the fix to do?
 
I am getting a A0403034 22CBF29E error message at address 00 in SYSCON external access mode. I assume this means the RSX needs to be reballed or reflowed. I do not have the required equipment to even attempt this operation.
I have enabled internal access mode, but when attempting to AUTH, I get the following response:

"scopen response invalid"

Any ideas on what may be wrong and how I can correct it?

Thanks!
 
RIP-Felix,
Thank you for your reply, and I wish you and yours a Happy Thanksgiving!
I thought the 3034 was the RSX/CPU communications failure, more related to the RSX bumps failing than the CPU.
Am I incorrect about this?
At any rate, I cannot for the life of me connect to the UART on the COK-001 board in internal mode. I continually get the "scopen response invalid" error no matter what I try.
I AM ABLE to connect to the UART in external mode, and I did change the 3961 01 bit to enable internal mode successfully.
Technically speaking, I am able to remove/replace either the RSX or the CPU, but do not possess the proper equipment or a replacement CPU/RSX to even attempt this procedure.
I would appreciate ANY and ALL assistance in:

1) determining why I am getting a "scopen response invalid" when attempting to connect to the UART is internal mode, and:
2) locating a repair person in the United States who has the requisite equipment, parts, and expertise to affect a proper repair of my COK-001 motherboard.

Failing that, I will have no choice but to junk the board and the PS3 due to frustration.

Thanks again for your help and assistance!
 
swannobiwan said:
RIP-Felix,
Thank you for your reply, and I wish you and yours a Happy Thanksgiving!
I thought the 3034 was the RSX/CPU communications failure, more related to the RSX bumps failing than the CPU.
Am I incorrect about this?
At any rate, I cannot for the life of me connect to the UART on the COK-001 board in internal mode. I continually get the "scopen response invalid" error no matter what I try.
I AM ABLE to connect to the UART in external mode, and I did change the 3961 01 bit to enable internal mode successfully.
Technically speaking, I am able to remove/replace either the RSX or the CPU, but do not possess the proper equipment or a replacement CPU/RSX to even attempt this procedure.
I would appreciate ANY and ALL assistance in:

1) determining why I am getting a "scopen response invalid" when attempting to connect to the UART is internal mode, and:
2) locating a repair person in the United States who has the requisite equipment, parts, and expertise to affect a proper repair of my COK-001 motherboard.

Failing that, I will have no choice but to junk the board and the PS3 due to frustration.

Thanks again for your help and assistance!
Click to expand...

1: 99% of the time it is a wiring issue. Have you grounded "DIAG"?
2: Computer Booter can help you with that.
 
You must log in or register to reply here.

Similar threads

Back
Top