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

[RIP-Felix]

Hi guys, i have a question. I have fat model CECHK04, and there is no video, only with AV scart i have video. I read somewhere that coulprit could be Silicon image chip on those models, since i couldn't find anything wrong with HDMI port. My question is: can syscon find errors with HDMI port or chip if i pull errorlog on usb from pkg syscon reader? Or will syscon even show those errors? Thank you in advance.

Yeah, since your console turns on and you cans see through AV (not HDMI), you can go to ps3toolset.com on the web browser, on the system managment tab, at the bottom under errors, to check the errorlog. My guess is there are a bunch of A0802120s. The behavior you describe is consistant with the HDMI transmitter (what most people call and HDMI encoder).

 

[RIP-Felix]

...adding pressure behind the CELL is a last resort, when the correct fix is simply not an option financially and learning to perform a re-ball or frankenstian mod is beyond the users capabilities.

This isn't about accessibility. As if a skill or financhal barrier forces people to put a thermal pad behind the CPU, when it's not the even the CPU.

A hairdryer can achieve the same result without even opening the console or placing the CPU's BGA at risk! I don't like that method either, but at least it doesnt FUBAR the CPU. It just melts plastic when idiot think they're gonn actually reflow the balls doing that.

People have gotten the console to boot by just trying to power it on 50 times in a row. Once it warms up, the thermal expansion keeps it connected long enough to retrieve their saves.

Long before that tho, they should have backed up their saves. Usually, when a console is dying you have plenty of warning. It'll randomly start artifactig, freezing, YLOD. But in this initial state of YLOD progression, it'll usually start back up after cooling. Or can be easily started back up by changing the pressure situation. Like tapping the console (if it's a BGA fault). Or attempting several times.

That's the time to back up, and start shopping for a new console.

Alternatively, you can use CFW to dump the ERK and keep that safe. There is a HDD tool that allows you to plug a HDD into your computer and retrieve your saves from the filesystem directly, but you need the ERK to do it. So before the console ever dies, you can back yhat up along with your NAND/NOR flash and keep them safe for the eventual day the console dies.

There are so many other ways, if you are truely just trying to retrieve the saves. I honestly don't think bolt modding the CPU, which has nothing to do with the RSX is even a consideration. It is simply harmful. And directed at a chip that's not even involved.

That it works is beside the point. If a spider is walking on your arm, you can...

1. Flick it off
2. Blow it off
3. Swat it
4. Or pour acid on it

They all get rid of the spider, but why would you reccomend the option that burns your skin?

I cannot reccomend an option that "can" damage the console in a way that cannot be repaired, when there are plenty of better ways to achieve the same goal.

 

[Timbo9876]

This isn't about accessibility. As if a skill or financhal barrier forces people to put a thermal pad behind the CPU, when it's not the even the CPU.

A hairdryer can achieve the same result without even opening the console or placing the CPU's BGA at risk! I don't like that method either, but at least it doesnt FUBAR the CPU. It just melts plastic when idiot think they're gonn actually reflow the balls doing that.

People have gotten the console to boot by just trying to power it on 50 times in a row. Once it warms up, the thermal expansion keeps it connected long enough to retrieve their saves.

Long before that tho, they should have backed up their saves. Usually, when a console is dying you have plenty of warning. It'll randomly start artifactig, freezing, YLOD. But in this initial state of YLOD progression, it'll usually start back up after cooling. Or can be easily started back up by changing the pressure situation. Like tapping the console (if it's a BGA fault). Or attempting several times.

That's the time to back up, and start shopping for a new console.

Alternatively, you can use CFW to dump the ERK and keep that safe. There is a HDD tool that allows you to plug a HDD into your computer and retrieve your saves from the filesystem directly, but you need the ERK to do it. So before the console ever dies, you can back yhat up along with your NAND/NOR flash and keep them safe for the eventual day the console dies.

There are so many other ways, if you are truely just trying to retrieve the saves. I honestly don't think bolt modding the CPU, which has nothing to do with the RSX is even a consideration. It is simply harmful. And directed at a chip that's not even involved.

That it works is beside the point. If a spider is walking on your arm, you can...

1. Flick it off
2. Blow it off
3. Swat it
4. Or pour acid on it

They all get rid of the spider, but why would you reccomend the option that burns your skin?

I cannot reccomend an option that "can" damage the console in a way that cannot be repaired, when there are plenty of better ways to achieve the same goal.

Hello again, Felix!

I agree with you. Prevention is most definitely better than the cure. But we are only human , so saying we must all be responsible and have our saves backed up is obviously correct, but the reality is quite the opposite.

I do disagree with you on reviving a GLOD console with heat. I have not been able to do this, and I have tried on many different motherboards. The only way to reliabily get a boot was to either add pressure or to do the correct fix, which is a frankie or a reball.

I'm not asking for your recommendation or approval, I am merely sharing my experiences that I have had with this console.

Peace [emoji3577] I look forward to your next video [emoji846]



Sent from my SM-F936B using Tapatalk

 

[Snake_Plissken92]

Yeah, since your console turns on and you cans see through AV (not HDMI), you can go to ps3toolset.com on the web browser, on the system managment tab, at the bottom under errors, to check the errorlog. My guess is there are a bunch of A0802120s. The behavior you describe is consistant with the HDMI transmitter (what most people call and HDMI encoder).

Thank you so much for reply. I was looking at syscon page on psdevwiki yesterday and saw codes 2120 you were mentioning and 2020. Both are tied to HDMI, that's why i asked if syscon can detect that fault. Anyway, i will continue to search for a solution, first going to get that errorlog and see if it can help me and then rule out one by one.

 

[RIP-Felix]

I do disagree with you on reviving a GLOD console with heat. I have not been able to do this, and I have tried on many different motherboards. The only way to reliabily get a boot was to either add pressure or to do the correct fix, which is a frankie or a reball.

I have tried pressure tests on GLOD consoles and it is by no means a reliable method to get them to boot. Personal experiance doesn't matter. If it isn't repeatable it's meaningless. I've asked others to perform the same thing and one of them had to reball the CPU afterwards IIRC. That's when I concluded not only was it meritless, it was dangerous.

I'm not asking for your recommendation or approval, I am merely sharing my experiences that I have had with this console.

Presenting only your sucesses, and not mentioning the dangers, to a new, inexperianced member, looking for advice, is obviously going to cause them to listen to it and try it. Especially if it seems easy and harmless.

Your reccomendation influenced a him to attempt it and he had errors indicating further damage in much the same way as I and others have seen happen as a result. I'll be honest. That irritated me. Not because it was an honest mistake, but because we've been over this before and you did it again.

I hope you'll stop reccomending this to people. You don't have to, of course. You do you. Just know I will defend this community against false claims whenever I have data to suggest it is. Or at least warn them of that possibility.

I'm not reccomending you stop as much as I am warning others not to follow your advice on this particular red herring.

I wont always be here to defend them. I hope this oasis of knowlege doesn't devolve into the mire that is reddit. Filled with trolls and egotists pushing dangerous pet theories for their own enjoymet, and at the expense of others. If you go on reddit you're asking for it. But that's not what we've built here.

 

[Timbo9876]

I have tried pressure tests on GLOD consoles and it is by no means a reliable method to get them to boot. Personal experiance doesn't matter. If it isn't repeatable it's meaningless. I've asked others to perform the same thing and one of them had to reball the CPU afterwards IIRC. That's when I concluded not only was it meritless, it was dangerous.

Presenting only your sucesses, and not mentioning the dangers, to a new, inexperianced member, looking for advice, is obviously going to cause them to listen to it and try it. Especially if it seems easy and harmless.

Your reccomendation influenced a him to attempt it and he had errors indicating further damage in much the same way as I and others have seen happen as a result. I'll be honest. That irritated me. Not because it was an honest mistake, but because we've been over this before and you did it again.

I hope you'll stop reccomending this to people. You don't have to, of course. You do you. Just know I will defend this community against false claims whenever I have data to suggest it is. Or at least warn them of that possibility.

I'm not reccomending you stop as much as I am warning others not to follow your advice on this particular red herring.

I wont always be here to defend them. I hope this oasis of knowlege doesn't devolve into the mire that is reddit. Filled with trolls and egotists pushing dangerous pet theories for their own enjoymet, and at the expense of others. If you go on reddit you're asking for it. But that's not what we've built here.

Hi Felix

I actually feel you are verbally attacking me.

Like I said, it's a last resort mod that has helped lots of people to revive a dead console. I have kept in contact with these people to monitor what happens.

I have made it very clear that this is a last resort and to only be attempted if you have no other choice. You're right in respect. I should have warned the newcomer about possible damage, but at this point, I didn't realise it could damage the motherboard. (Thanks for the education)

I will take what you have said on board and warn others that it's a last resort that could damage the console if attempted.

PS. I have taken a lot of criticism by promoting your recommendations when it comes to de-lidding. I now recommend reattaching the IHS with thermal plaster and high trmp silicone (Gasket Maker). I refer to yourself as a highly respected member of the PS3 community which is why I am highlighting your recommendations. I wouldn't dream of saying that you do all this for your own gratification, I feel insulted that you have insinuated that I do.










Sent from my SM-F936B using Tapatalk

 

[Pacorretaco]

Nobody needs to be or feel insulted.

@Timbo9876 is not here just making false claims. I see that mostly he is trying to help ... And actually he is right when he says GLOD/artifacts can be affected by pressure (more than heat). I have seen it often myself also, because it is a common thing as his video shows. Nobody can deny his experience, or anybody elses. Furthermore, there may be a specific reason or explanation for this too.

Spoiler

From my experience and observations, GLOD/artifacts are probably the most common manifestation of a BGA issue under RSX. (Not an issue inside the RSX) but a bad connection to the board. This is probably made common because of structural design reasons. The RSX IHS/heatsink are glued with rigid cement to the VRAM corners of the chip. Then only held by 2 screws and with an odd weight distribution and shape similar to a lever...
This is transferring any shock, inertia or vibrations directly to the corners of the RSX chip. Particularly those opposite to the screws and towards the CPU. Thats where there are connections that cause GLOD/artifacts once they eventually fatigue and get broken. (Or when people simply break them by pulling to open when it is stuck)


Playing with pressure under the CPU can indeed work (as @Timbo9876 has rightly shown) because the board is being deformed in the way that closes these connections.
Alternatively, as a test the board could be flipped upside down (because the chips are upside down) the fan removed and then lightly pushing or moving the heatsink/rsx against the board. (While the board is carefully supported)
Heat may or may not work because of thermal expansion or contraction, but this is the key distinction between the BGA or the chip itself. The BGA reacts more to pressure than to heat.

On the other hand, Felix is right too. Even if it may seem to work in some cases... Playing with pressure under the CPU die is dangerous and can result in unrepairable damage that is worse than the original fault. And theres no need for that because normally it is not even related to the CPU in the first place.
If you put something under the CPU, it should be no more than 1 mm thickness. Same as the 4 nylon dots for safe and even pressure. More than that can be a risk.
09 3003 error can be bad news for that CPU after the pressure.

Good luck

 

[RIP-Felix]

I laid it on a bit thicker, but I didn't mean it as an insult. I know you meant well. You took time out to help your fellow. That I want to encourage. My statments were meant as constructive criticism. Criticism, yes. But meant to help build up the quality of information presented here.

The rhetoric escalated because I sensed a dismissive tone. We don't have to agree on everything. But some things we have to draw the line at. For me that's at mods that harm the HW.

Perhaphs I could have been more tactful.

 

[Timbo9876]

I laid it on a bit thicker, but I didn't mean it as an insult. I know you meant well. You took time out to help your fellow. That I want to encourage. My statments were meant as constructive criticism. Criticism, yes. But meant to help build up the quality of information presented here.

The rhetoric escalated because I sensed a dismissive tone. We don't have to agree on everything. But some things we have to draw the line at. For me that's at mods that harm the HW.

Perhaphs I could have been more tactful.

Hi Felix,

That's good to know, I am only human and was really upset by some of the personal comments you made towards me.

Like I have said throughout our correspondence, it's not a fix and should only be considered as a last resort. What I wasn't aware of is the fact that thermal pads can cause damage to the hardware. I have put this in the description for now, and I plan to do another video in the future where I highlight the potential damage that could be caused.

Although it's not what I wanted to hear, I value the education and feel this warning should be made common knowledge to everyone on this site. I must admit, having looked through the eraser mod posts, I don't think there s enough information on the potential dangers of this mod. This is more widespread than my variation, is more dangers as it doesn't use thermal pads, and could potentially turn a working console into a faulty one.

Thanks for your advise, it's valued as always and more importantly. it's taken on board.

Peace [emoji3577]







Sent from my SM-F936B using Tapatalk

 

[Timbo9876]

I have just received a CECHA00.

I have 31 error codes 1701, with the last code being given 2022, which I believe is the southbridge error.

1701 would normally report another code indicating the cause. This doesn't, so what are we to make of this?

Console has no damage and has never been opened.

Has 74 hours runtime.

Console has played the first two chapters of TLOU with no issues.

On Syscon, the fan is very quiet, with webman fan speed test to 32 percent, console stays under 65 degrees, so doesn't seem to have any overheating issues.

Any ideas, anyone?

Sent from my SM-F936B using Tapatalk

 

[Timbo9876]

Below is the Syscon dump for a CECHA00 Revision. The console works and runs fine. It's never been opened, has no damage and is 74 days old in runtime.

Console runs well and played TLOU for a few hours no issues.

Should I be concerned with the 1701 error??

HELP !!!!

Firmware Version: 4.90 (build 50747)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0F38.0001000500010001 (EEPROM: 0001000500010001)
Bringup Count: 738, Shutdown Count: 647
Runtime: 73 Days, 6 Hours, 46 Minutes, 28 Seconds
Error Log
01: A0802203 Fri Aug 4 17:58:52 2023
02: A0801701 Sun Dec 5 12:49:33 2021
03: A0801701 Sun Dec 5 12:41:39 2021
04: A0801701 Fri Dec 29 14:12:47 2017
05: A0801701 Mon Dec 25 13:56:26 2017
06: A0801701 Tue Dec 24 02:56:18 2019
07: A0801701 Sun Nov 10 06:31:51 2019
08: A0801701 Tue Oct 29 11:48:14 2019
09: A0801701 Tue Oct 22 06:30:12 2019
10: A0801701 Mon Oct 14 11:18:05 2019
11: A0801701 Sat Mar 23 11:29:58 2019
12: A0801701 Sat Oct 20 10:00:52 2018
13: A0801701 Sun Oct 14 03:34:55 2018
14: A0801701 Mon Aug 27 15:06:35 2018
15: A0801701 Sun Aug 26 14:55:22 2018
16: A0801701 Tue Aug 7 09:21:31 2018
17: A0801701 Fri Jul 20 13:44:19 2018
18: A0801701 Sat Jul 14 14:18:32 2018
19: A0801701 Fri Jul 13 14:48:33 2018
20: A0801701 Sun Jun 10 13:38:35 2018
21: A0801701 Sun Jun 10 08:27:25 2018
22: A0801701 Thu Apr 5 15:29:27 2018
23: A0801001 Sun Mar 25 03:08:42 2018
24: A0801701 Sat Mar 24 12:15:37 2018
25: A0801701 Mon May 22 22:35:40 2017
26: A0801701 Wed Aug 10 00:18:25 2011
27: A0801701 Sat Mar 24 06:02:23 2018
28: A0801701 Wed Mar 21 09:34:36 2018
29: A0801701 Tue Mar 6 13:19:53 2018
30: A0801701 Sun Feb 11 10:09:57 2018
31: A0801701 Sat Feb 3 08:18:32 2018
32: FFFFFFFF Wed Jan 17 03:11:22 2018

 

[RIP-Felix]

1701 is a general error the CPU will throw whenever it freaks out. It's often generated by software crashes and not really something to worry about on it's own.

Enabeling FPS in webman for example has sometimes caused it. You can get it from the BD ribbon cable not being fully inserted or clipped. A HDD failing...many things.

The 2203 is the SB complaining about not being able to shutdown a paripheral during the power down sequence (where syscon reverses the power on sequence). Sometimes they coincide with 1701, because the YLOD didn't allow the shutdown sequence to complete and the SB was in the middle of something and voiced it's disaprooval of being rushed. "Fine! I'll force it off, but I'm lodging a complaint with managment! (SYSCON)."

Also nothing to worry about. 2203 often occurs with 1200 (CPU overheat) because the SYSCON had to shutdown too quickly for the SB to gracefully complete its shutdown.

If the console is working, these codes wouldn't worry me. I would of course use an oscilloscope to measure the voltage ripple and noise on VDDC to check the health of the NEC/Tokins before calling it good, but if it's stable in a variety of difficult games it's probably got much life left.

 

[Timbo9876]

1701 is a general error the CPU will throw whenever it freaks out. It's often generated by software crashes and not really something to worry about on it's own.

Enabeling FPS in webman for example has sometimes caused it. You can get it from the BD ribbon cable not being fully inserted or clipped. A HDD failing...many things.

The 2203 is the SB complaining about not being able to shutdown a paripheral during the power down sequence (where syscon reverses the power on sequence). Sometimes they coincide with 1701, because the YLOD didn't allow the shutdown sequence to complete and the SB was in the middle of something and voiced it's disaprooval of being rushed. "Fine! I'll force it off, but I'm lodging a complaint with managment! (SYSCON)."

Also nothing to worry about. 2203 often occurs with 1200 (CPU overheat) because the SYSCON had to shutdown too quickly for the SB to gracefully complete its shutdown.

If the console is working, these codes wouldn't worry me. I would of course use an oscilloscope to measure the voltage ripple and noise on VDDC to check the health of the NEC/Tokins before calling it good, but if it's stable in a variety of difficult games it's probably got much life left.

Thanks felix, turns out it's a Sony referbishment with a 40nm RSX chip, thread is in general PS3 discussion

 

[vyktormvmpay25]

Something that came to my attention, 1701 only on a Sony refurbishment mobo. Is a bit strange nothing else is happening. Like a rsx error from ram only.
Not to be concluded /final decision but it looks like.
Why would they need another syscon still not clear enough for me.
Can look after those errors by enable sb uart debugging and assembly unit to record with putty or realterm.

 

[kemo98]

Dual transistor replaced.
Still a black screen on hdmi - yes, I have re-tried to reset the resolution. No luck.

I'm thinking that it really might be some one small smd, that would cause it...
...and maybe we are wasting time here

After all did it worked and what things you changed?

 

[kemo98]

Dual transistor replaced.
Still a black screen on hdmi - yes, I have re-tried to reset the resolution. No luck.

I'm thinking that it really might be some one small smd, that would cause it...
...and maybe we are wasting time here

After all did it worked and what things you changed?

 

[Hamzatoun]

Hi everyone,

I have a PS3 that has a MultiAV controller problem (CXM4024R), i swaped the chip then discovered after that another resistance was faulty, so i've also repaced it.
After that, the PS3 powered on successfully. I shut it down and repowred it on but this time it won't power on, it just beeps 3 times (like ylod) without registering any syscon errors.
For verifying, i unplugged the 12v and powered it on again and the syscon registered the 3001 errors witch means that syscon is safe.
I tried the bringup command and it gaves me this :

bringup
00000000
[SSM] Fataldown ok.
(PowerOff State) (Fatal)
NG E00000E0
[SSM] Clearfatal Start.
[SSM] Clearfatal ok.
(PowerOff State)
[SSM] Bringup Start.
[PowSeg] Error:8301
[SSM] PS0 ng.
[SSM] Cond/Fatal received, msg=24D0
[SSM] Fataldown Start.

I don't understand what does this mean and why any error is registered into the syscon.

Thank you for your help .

 

[Hamzatoun]

Hello, got a bit of an odd error I've not seen before. This is from a PS3 slim CECH-2003, the error code it keeps spitting out in the syscon is A0092114.

I have attached the bringup output and the error log. Any help would be appreciated!

Did you resolve the problem ? I'm in the same situation please

 

[Kalulo24]

Hi! This is is my first time here. I have a CECHK01 with the errors A06114FF and A0611701 and all timestamps are FFFFFFFF. Before doing the syscon, the only other time I've opened the console was to replace the Blu-Ray drive (I also transferred the board from the old drive into the new drive).
My PS3 got YLOD in the middle of the night sometime in May 2022 when turning on automatically to upload to online storage.
I know that 14FF is Check stop and 1701 is CELL BE ATTENTION.
The PS3 was manufactured July 2008 if that's important.

 

[armorsnake]

My friend made a mistake and update firmware on FSM mode.
Is their any known command for SYSCON to exit Factory Service Mode?
PS3 CECHA and he only got 239mb backup of NAND.