Syscon Error Codes: Difference between revisions

Revision as of 20:19, 13 November 2021

Description

Syscon memory contains a table of size 0x100 bytes intended to store error codes, every error code is composed by 4 bytes + another 4 bytes for its timestamp, in total the table can store 32 errors. When the table is full of errors and a new error needs to be stored syscon deletes the oldest
The timestamps are in UTC format (number of elapsed seconds since 2000)

How to get the syscon error log

If the PS3 still boots up to the XMB and is able to install and run apps you can use programs like the ones mentioned at top of Platform ID page
If the PS3 doesnt boots is still posible to retrieve the syscon error log by connecting a PC to syscon UART port using a "USB to TTL UART adapter" and running the command errlog. There is also the command clearerrlog to empty the error table (handy to prevent confusions with old error codes that could be cummulated along the months/years and not related with the actual problem)

Error code format

The error codes follows the format: ARSSCEEE, where:

A (Fixed)
- A = unknown
R (Reserved)
- 0-E = Unknown
- F = Frequent error
SS (Step)
- 00-7F = Step of the power on sequence where the error happened
- 80 = The error happened when the PS3 was powered on
- 90 = The error happened when the PS3 was powered off
- A0 = The error happened after a syscon reset
C (Category)
- 1 = System
- 2 = Fatal
- 3 = Boot
- 4 = Data
EEE (Error)
- Any number in hex

The list below only includes the last 4 numbers (category + error)

Error codes

System

1001

Cell Vram Power

Speculation:
1001 errors happen when the system encounters an unexpected shutdown. They often occur in testing, when the console is turned on/off a lot, instead of graceful shutdown. They have been associated with other errors, but there doesn't appear to be any single cause.

The hypothesis that this error is associated with insufficient Filtering on CPU's core voltage (VDDC) has not been confirmed. There is a range of voltage ripple/noise that "should" cause errors before it gets so bad it causes a CELL BE VDDC Power Failure (3003). There are numerous SMD components involved in filtering, but the main concern are the NEC/TOKIN Proadlizers (capacitors). 1002 errors are the fingerprint of bad tokins on the GPU, but 1001 has not been shown to have the same association with the CPU's filter. However, a connection is strongly suspected.

1002

RSX Vram Power

This error has been associated with insufficient Filtering on RSX_VDDC. There is a range of voltage ripple/noise that will cause this error before it gets so bad it causes an RSX_VDDC Power Failure (3004). YLOD's causing 1002's range in duration from 2 seconds to only occurring during intense games.

There are numerous SMD components involved in filtering, but the main concern are the NEC/TOKIN Proadlizers (capacitors). 1002 errors are the fingerprint of bad tokins.

1004

PSU Power

1103

Thermal

1200

CELL BE Thermal Error

CPU Overheat. This is a common error. The usual culprit is failed Thermal Interface Material (TIM). As the material ages it "dries" allowing air inside. Air is a heat insulator, reducing the TIM's ability to transfer enough heat away from the processor. The system fan will steadily get louder over time until it cannot keep up. Once the processor approaches it's Thermal Shutdown Temperature a Yellow LED begins flashing on the console (Early Phat Models). Once it reaches the Thermal Shutdown Temperature the console will beep three times and hard shutdown, flashing red until the console is unplugged and the error state reset. Error 1200 is generated in the SYSCON errorlog.

First be sure the system fan is working. If so, apply new TIM Between the Internal Heat Spreader (IHS) and Heatsink (HS). If that does not resolve the problem, carefully remove the IHS (Delid) and replace the TIM between the IHS and processor DIE.

If that still doesn't work, it could be an issue with the temperature monitor chip (IC1101). Beyond that, some users have noted that dead CPU's can throw error 1200. However, that's the limit of our current understanding. It could be dead, or have another unexplained issue, but usually reflowing or reballing is the last ditch effort to revive such a console.

1201

RSX Thermal Error

GPU Overheat. This is the same as error 1200 above, except it's for the GPU. The same repair steps apply, except it's Temperature Monitor Chip is IC2101.

1203

Cell voltage regulators thermal

1204

Southbridge thermal

1205

EE/GS thermal

1301

Cell PLL

14FF

Check stop

1601

BE Livelock Detection

Speculation: If a YLOD turns into a GLOD after reball/reflow then 1601 (with or without 1701) could mean the RSX RAM was damaged. This is a loose association based on a few user reports.

1701

Cell attention

1802

RSX init

1900

RTC voltage

1901

RTC oscilator

1902

RTC access

Fatal

2001

Cell

2002

RSX

2003

Southbridge

2010

Clock 1

2011

Clock 3

2012

Clock 2

2013

Clock 4

2020

HDMI

2022

DVE Error (CXM4024R MultiAV controller for analog out)

2024

This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD).

2124 and 2024 errors have been fixed by replacing both the AV and HDMI encoders. One user reported 2024/2124 errors resolved by replacing the HDMI encoder. Another removed the HDMI encoder and tested the console without it. That console primarily filled the errorlog with 2124 errors, but a few 2024's as well. So it is unclear if 2124 is specific to the HDMI Encoder or AV Encoder. It seems it could be either.

2030

Thermal Sensor Error (IC1101) CELL BE Temp. Monitor

Speculation: 2030-33 errors reported in case of dodgy PWR/EJT daughter board.

2031

Thermal sensor Error (IC2101) RSX Temp. Monitor

2033

Thermal sensor 3

2101

Cell

2102

RSX

2103

Southbridge

2110

Clock 1

2111

Clock 3

2112

Clock 2

2113

Clock 4

2120

HDMI

2122

DVE

2124

This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD).

2124 and 2024 errors have been fixed by replacing both the AV and HDMI encoders. One user reported 2024/2124 errors resolved by replacing the HDMI encoder. Another removed the HDMI encoder and tested the console without it. That console primarily filled the errorlog with 2124 errors, but a few 2024's as well. So it is unclear if 2124 is specific to the HDMI Encoder or AV Encoder. It seems it could be either.

2130

Thermal sensor 1

2131

Thermal sensor 2

2133

Thermal sensor 3

2203

Southbridge

Boot

3000

Power

3001

12v Power Failure

Usually this caused by a bad Power Supply Unit (PSU).

Alternatively, a failure on the 12v_main line can cause it. Check fuses, capacitors, resistors, and IC's on the 12v line. Measure resistance of the large 2 prong 12v connector on the motherboard. It should read in the Kilo ohms range if there is sufficient separation. Otherwise you may have a short on the line that need to be found and repaired.

3002

Power

3003

VDDC CELL BE Power Failure

This error will occur in the case of a PWR failure on the main core voltage of the CPU. For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well.

3004

VDDC RSX Power Failure

This error will occur in the case of a PWR failure on the main core voltage of the GPU. For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well.

3010

Cell BE Error

Cell and RSX

3040

Flash

Cell or RSX

@@ Line 235: / Line 235: @@
 ==== 3013 ====
-Observation: 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?
+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 dead CPU?
 Another user had one on a CPU he damaged while deliding.
 ==== 3020 ====
 Cell