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

RIP-Felix said:
I have since confirmed that all 65nm revision have fixed underfill. While that doesn't mean they are free from bumpgate materials (namely a lack of the polyamide stress layer, which I cant confirm exists or not), I can say there is not sufficient evidence of an increased RSX failure rate among 65nm models. Which I interpret to mean the decreased TDP of the 65nm RSX, but same load (ps3 games), and addition of more durable underfill is adequate to not exploit the defect even it it exists.

IMO, the 65nm is in the clear.
Click to expand...
Ahh thats good information to know. This means the fats are now more reliable
RIP-Felix said:
1601/1701 can occure from solder, but also from normal software crashes. Even Bluray drive and several non RSX/CELL related ICs. They do not always mean a 3034 is coming. They just often preceed one.

The 1001/1002 in game behavior you describe and correctly diagnosed is the classic NEC/Tokin behavior. So that is likely one issue solved. Now I would have done the caps differently, but to each their own.

Just keep an eye on it. Keep saves and stuff backed up and hope for the best. 1st diagnostic and repair step was done correctly. So we wait now to see if it is going to last. GL and good work!
Click to expand...
That does make sense, if 1601 is caused by a livelock condition it does not have to be the RSX.
I would imagine that components such as the hard drive and the flash could be potential vectors for the issue as well
 
Last edited:
Tomatarto said:
Right.
Does the console GLOD or YLOD when you turn it on now?
Click to expand...

It gives me YLOD whenever I try to turn it on. I got it stay on once last week but it showed no video and the fan speed was at max. That lasted for around 15 seconds. It gave me another error code: A0902120
 
Last edited:
Kalulo24 said:
It gives me YLOD whenever I try to turn it on. I got it stay on once last week but it showed no video and the fan speed was at max. That lasted for around 15 seconds. It gave me another error code: A0902120
Click to expand...
Hmm, If we have established that the 65nm chips do not have a statistically higher failure rate then the other cause for the 2120 error code is a fault in the HDMI subsystem.

That being said with the 1701/14FF error a 2120 in tandem could indicate a BGA/Bump failure.

I honestly don't know myself. If you didn't get any 3034/4xxx error codes than it might not indicate a failed RSX.
One other thing. if you got 3013 error with the with the 2120 error then that is good evidence to support a fault in the HDMI subsystem.
Specifically a blown fuse (F6302)
Do you have the 2120 SYSCON log?
 
Last edited:
Tomatarto said:
Hmm, If we have established that the 65nm chips do not have a statistically higher failure rate then the other cause for the 2120 error code is a fault in the HDMI subsystem.

That being said with the 1701/14FF error a 2120 in tandem could indicate a BGA/Bump failure.

I honestly don't know myself. If you didn't get any 3034/4xxx error codes than it might not indicate a failed RSX.
One other thing. if you got 3013 error with the with the 2120 error then that is good evidence to support a fault in the HDMI subsystem.
Specifically a blown fuse (F6302)
Do you have the 2120 SYSCON log?
Click to expand...

The A0902120 is near the end of the log.
I used the GUI syscon reader so I only got 20 errors instead of the traditional 32. If you need me to, I can use the regular syscon reader to get all 32.

ERR 00: 00000000 A06114FF FFFFFFFF
ERR 01: 00000000 A0611701 FFFFFFFF
ERR 02: 00000000 A06114FF FFFFFFFF
ERR 03: 00000000 A0611701 FFFFFFFF
ERR 04: 00000000 A06114FF FFFFFFFF
ERR 05: 00000000 A0611701 FFFFFFFF
ERR 06: 00000000 A06114FF FFFFFFFF
ERR 07: 00000000 A0611701 FFFFFFFF
ERR 08: 00000000 A06114FF FFFFFFFF
ERR 09: 00000000 A0611701 FFFFFFFF
ERR 10: 00000000 A06114FF FFFFFFFF
ERR 11: 00000000 A0611701 FFFFFFFF
ERR 12: 00000000 A06114FF FFFFFFFF
ERR 13: 00000000 A0611701 FFFFFFFF
ERR 14: 00000000 A0902120 FFFFFFFF
ERR 15: 00000000 A06114FF FFFFFFFF
ERR 16: 00000000 A0611701 FFFFFFFF
ERR 17: 00000000 A06114FF FFFFFFFF
ERR 18: 00000000 A0611701 FFFFFFFF
ERR 19: 00000000 A0902120 FFFFFFFF
 
Kalulo24 said:
The A0902120 is near the end of the log.
I used the GUI syscon reader so I only got 20 errors instead of the traditional 32. If you need me to, I can use the regular syscon reader to get all 32.

ERR 00: 00000000 A06114FF FFFFFFFF
ERR 01: 00000000 A0611701 FFFFFFFF
ERR 02: 00000000 A06114FF FFFFFFFF
ERR 03: 00000000 A0611701 FFFFFFFF
ERR 04: 00000000 A06114FF FFFFFFFF
ERR 05: 00000000 A0611701 FFFFFFFF
ERR 06: 00000000 A06114FF FFFFFFFF
ERR 07: 00000000 A0611701 FFFFFFFF
ERR 08: 00000000 A06114FF FFFFFFFF
ERR 09: 00000000 A0611701 FFFFFFFF
ERR 10: 00000000 A06114FF FFFFFFFF
ERR 11: 00000000 A0611701 FFFFFFFF
ERR 12: 00000000 A06114FF FFFFFFFF
ERR 13: 00000000 A0611701 FFFFFFFF
ERR 14: 00000000 A0902120 FFFFFFFF
ERR 15: 00000000 A06114FF FFFFFFFF
ERR 16: 00000000 A0611701 FFFFFFFF
ERR 17: 00000000 A06114FF FFFFFFFF
ERR 18: 00000000 A0611701 FFFFFFFF
ERR 19: 00000000 A0902120 FFFFFFFF
Click to expand...
Seeing the full 32 error codes would be useful

With the data here my hypothesis is
The 1701 and the 14FF codes combined with the 2120 indicate a failed RSX BGA/Bump joint, this joint is one of the joints that is responsible for the VDDIO output.
The failed joints would trigger a 14FF, a 14FF is a checkstop error which is when the console sees that a piece of hardware is in a state that would be impossible to achieve unless it is broken. Thus it keeps trying to check the state of the hardware and gives up after enough time.
The CPU sees this and it flags the 1701 error (more detail on how this is done on the dev wiki) which causes the SYSCON to terminate the boot up process.
Then the SYSCON logs the 2120 code as it sees there is a fault in the HDMI subsystem somewhere. This fault would be one of the joints that outputs data to that system and thus it cannot run.

It is also possible that a similar failure to this is in the CELL, although this would be less likely
 
Last edited:
It's important to note that step number 61 is the FW sequence, where the Flash is read and booloader started. This could be a software brick, SS2 failure, solder connection to the flash itself or any supporting SMDs.

You can useually ignore 2120s. The often occure in coincidence with more telling (diagnostic) codes. The 14FF is a checkstop, and is an inherantly HW related issue. With that step number my mind would be thinking hard about the flash.
 
RIP-Felix said:
It's important to note that step number 61 is the FW sequence, where the Flash is read and booloader started. This could be a software brick, SS2 failure, solder connection to the flash itself or any supporting SMDs.

You can useually ignore 2120s. The often occure in coincidence with more telling (diagnostic) codes. The 14FF is a checkstop, and is an inherantly HW related issue. With that step number my mind would be thinking hard about the flash.
Click to expand...
Interesting. I am not very fluent with the times of the SYSCON codes and the consequences that they might have. That is something that i do have to learn more about

That being said it is strange that the flash or the flash subsystem would fail as they are not a "traditional" point of failure. But i do see how you could come to that conclusion.
I think you might be correct in that assumption
 
Last edited:
The southbridge is also involved in that step number for accessing and loading the OS. So conceivably a solder joint on it could cause those error.
 
hi felix I'm back, here are some test points I did on the Ver-001 board, with no Nec / Tokin on the RSX. Is this value reasonable? some values are unstable and even jump far from 20 - 120.
with error #A0093004 is there a problem with the rsx too?
gUIxP4T.jpg
 
Hi, i have recently taken apart my ylod slim ps3, it did this 4-5 years ago and the warranty seal was still intact until yesterday when i read the syscon.
# CODE CLOCK
# A0203010 2C91FF73
# A0203010 2C91FDBE
# A0203010 2C91FB0E
# A0203010 2C91FAFB
# A0203010 2C91F992
# A0203010 2C8FB0FE
# A0203010 2C8FB0F7
# A0203010 2C8BA4BE
# A0203010 2C8BA4B8
# A0203010 2C8BA4B5
# A0203010 2C8BA4AE
# A0203010 2C8B9F7F
# A0203010 2C8B9F7D
# A0203010 2C8B9F7A
# A0203010 2C8B9F77
# A0203010 2C8B9F74
# A0203010 2C8B9F70
# A0203010 2C8B9F6A
# A0203010 2C8B9D1B
# A0203010 2C8B9D16
# A0203010 2C8B9D0D
# A0203010 29A04097
# A0203010 29A03F7D
# A0203010 267983F1
# A0203010 267983A3
# A0203010 257EC7EC
# A0203010 247EE13F
# A0203010 247EE0FF
# A0203010 247EE0E0
# A0203010 2419129F
# A0203010 23DA3103

All the errors are 3010 and when i do the bringup command i get this response
FFFFA605
# [PowSeq] Error:A104
# [SSM] PS1 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0

From my research i can see this fault does not have a obvious fix. What should my next step be in fixing it.
 
Nascar1243 said:
Can you enter in r 800 8 so you can get the becount as well, was there any drop damage to the console itself, anything noteworthy about this console


Sent from my iPad using Tapatalk
Click to expand...
How do I get becount to work as i have tried authing in with lower case to use internal commands and it still doesn't work. There is nothing of note in the history, used as primary console till ps4 came out then used occasionally untill failing.
 
T4crew said:
How do I get becount to work as i have tried authing in with lower case to use internal commands and it still doesn't work. There is nothing of note in the history, used as primary console till ps4 came out then used occasionally untill failing.
Click to expand...

When you auth in, type r 800 8, that will give it to you in bytes, just post what it reports back here.


Sent from my iPad using Tapatalk
 
You must log in or register to reply here.

Similar threads

Back
Top