Editing Syscon Error Codes

==== 1001 (Power Cell) ====

Occured while overvolting a 40nm CXD5300 RSX to achieve a higher overclock on a CECH-2501A. An A0801002/A0801301 occured when the voltage regulation module exceeded it's design specifications. SB UART reported there was a Busy loop detected, suggesting that poor filtering under these extreme conditions can cause a PLL unlock. It did not occur on every YLOD. Note, the 25xx models do not have NEC/Tokins.

CPU is deadlocked and cannot proceed. Some kind of error occurred, preventing a process from completing. It is the software equivalent of trying to pass someone in a hallway and you both keep choosing the same direction to swerve. Now imagine you had exactly 30s to make it to the other end of the hallway to catch an elevator, and it takes 29s to get there. Neither of you can pass and miss your elevators because of it. Now imagine you were supposed to pass an envelope to a person on the 3d floor, who had 30s to read it and enter it in a spreadsheet. Now he misses his deadline too. And imagine the entire organization was micromanaged like this. One disruption can cause the whole operation to grind to a halt! That's kinda how this works.

A0801802 occurring after the console has booted (step# 80) and causes BE Attention (1701) alarm raised when a "checkstop" error (14FF) occurs. Likely the 1802 was the hardware failure that caused the checkstop error. That causes BE ATTENTION to be driven High and the SYSCON shuts the console down with A0801802, A08014FF, and A0801701. That makes sense because the CPU couldn't continue with it's process when the RSX interrupt occurred. These errors have been seen in consoles that were repaired by an RSX reball/replacement.

1802 is confirmation that the RSX was involved, if there's any doubt about what's causing a 3034.

CPU Thermal Sense Error. Thermal Monitor (IC1101) external sense line. Check C1103, R1106/7 & replace IC1101 (COK-00x) before reballing the CPU. If all else fails, the CPU's thermal diode is dead.

Suspected that removing R1106/7 or the CPU itself will cause A0201b01/A0A02030 errors. Hasn't been confirmed through sabotage testing.

RSX Thermal Sense Error. Thermal Monitor (IC2101) external sense line. Check C2103, R2101/2 & replace IC2101 (COK-00x) before reballing/replacing RSX. If all else fails, the GPU's thermal diode is dead.  

This error tends to occur at step number 20, during core initialization.

Confirmed that removing R2101/2 or the GPU itself causes A0201b02/A0A02031 errors.

Bad GPU NEC/TOKINs if associated with 1002. Was reported in a DIA-002 with other errors. A0091002/A0102014, A0101002/A0102113, and also had A0101002 + 10x A0202120s. Presumably caused by failed RSX NEC/TOKINs.

Rare code. Occurred in a CECHBxx model with 10x A0202121 occuring throughout the power on sequencing before starting the bootloader. It did not prevent the boot before the console overheated. Errorlog shows two 10x 2121 + 1200 error combos. One of which also had A0802021 coinside. Log shows the console originally had a NEC/TOKIN issue (A0801002) before this started. While this is an Unknown error combo, it may be similar to 2120. On another console, timestamps showed A0101002 occurred 1st and then 10x 2120's occurred over the next 10 seconds. Replacing TOKINs fixed that console. It's possible this is a similar situation, but with a new code.

This error may be normal in an otherwise working console. They have been observed in the errorlogs of perfectly operational units and can occur naturally from AV issues.  

Often coincides with A0403034 indicating the GPU needs replaced (usually). Delidding can cause this, look for trace damage. In one case, errors A0402101 / A0403034 occured because RSX TX1 was shorted to ground by a nicked RSX trace during the delid. TX is the transmit line, so the CPU didn't receive data from it, and noted the error (BitTraining BE:RRAC:BX0:BX:FLEXIO_ID).

In several reports IC6301 replacement fixed it. RSX_FBVDDQ (VRAM voltage) implicated. In most cases, it's an RSX Failure. Sometimes coinciding with A0403034 or other codes indicating GPU fail. Often after reflow attempt.

 

In another case the combo was caused by Q6012 (COK-001), which was shorted on pins 1,2,4,5,6, leaving the impedance of the 1.5V_RSX_VDDIO voltage in relation to GND with only 2.7 ohms. There were also shorted capacitors on the 1.5V_RSX_VDDIO line. After replacing the components the impedance rose to 43.6 ohms and the CECHB turned on again. Repair and identification of components with the help of a thermal camera, as the defective components did not heat up too much.

One particularly noteworthy component is IC6020, which supplies +3.3v_MK_Vdd to the clock generator (IC5001). When F6001 blows, a 02 2110 is generated. A step number of 02 is very early in the power on sequence (POS), which explains why 2110 is triggered instead of another error code. Since the clock generator is critical for timing, it is one of the first things the SYSCON checks during the POS.

Reportedly fixed by replacing IC5001. One person tried replacing X5301, but short C5142 (2.5v to GND). This killed power to IC5004 (RSX/CELL/SB Clock Generator for FlexIO) and caused error A0092113. IC5004 relies on +1.2V_YC_RC_VDDIO reference voltage to carry the signals. That can be affected by RSX/CPU faults. Another possibility is F6302 or nearby SMDs, which supplys 1.7V_MISC to IC6303 to generate +1.2V_YC_RC_VDDIO, among other voltages required to start CPU/SB/GPU.​

Bad GPU NEC/TOKINs if associated with 1002 and/or 3004. Has been reported in VER-001 and DYN-001 motherboard revisions. Related codes have been reported in a DIA-002, with A0091002/A0102014, A0101002/A0102113. That was presumably caused by failed RSX tokins. ​

A lone 2114 or one assiciated with 2124, 3020, 1301, and/or 3034 may be GPU/BGA related. Possibly HDMI encoder (MN864709), or Texas instrument 88J9LKK C5714 G4 Clock generator, but evidence for both of those cases is weak. However, given it's similarity to error code A0092113, which is related to the clock generators, a connection is suspected.​

Sometime seen with a "SB Counter Error -  Explicit Bug" in bringup log. Often accompanies CPU (1200) or GPU (1201) Overheats. Once occurred in GLOD, after holding power "SB (FATAL) XDR Link not initialized."

Another user (Razmann4k) got this error on their CECHL04 by attempting the eraser mod on an already delidded Cell and noticed a crack running down the middle of the Cell die. It caused 20 3010. A 20 3010 error was also observed on a CELL that was physically damaged during a delidding attempt by the console owner. Another 20 3010 was reported when MC2_VDDIO was shorted internally on the CELL of a COK-002.

Another user had one on a CPU he damaged while delidding.

'''Remember, ITS NOT ALWAYS a bad connection between the CPU, and GPU.''' Bit training calibrates the connection between the GPU, CPU AND South bridge. For example, A0403034 occurred on a VER-001 with a probably BGA defect. By putting pressure on the southbridge the console would boot. Look at the data error and other information of the console before assuming a bad GPU.

This is the most common error seen in early Phat model PS3's with the 90nm [[RSX]]. It is the hallmark of solder fatigue (such as a cracked solder ball or bump defect) which affects the Flex IO interface that allows the CPU, GPU, and SB to communicate. It is by no means limited to the early models, however. These errors have been seen in every model of PS3 with varying frequency. However, it's most common in the earliest models, likely due to a manufacturing defect in the 90nm RSX material set. Namely a CTE mismatch between the underfill and bump material that leads to premature solder fatigue and GPU failure. Dubbed "BumpGate," this is a well known failure modality among GPUs manufactured from 2005-2008. Although it has not been proven unequivocally that the 90nm RSX is affected by Bumpgate, members of the community have shown the 90nm RSX has an increased failure rate, similar material set, and exhibits similar symptoms to known bumpgate affected chipsets - such as black screens (GLOD), graphical artifacts like lines, double images, color splotches and pixelation.