Расшифровка кодов ошибок ps3

Всегда неприятно, когда любимая игровая приставка Playstation 3 вместо запуска игры либо выполнения других функций выдает какой-то непонятный код или набор цифр. Эти коды ошибок имеют свою расшифровку, которая адресована мастеру в сервисном центре. Но не всегда все так печально, что нужно обращаться в ремонт. Со многими проблемами можно справиться самостоятельно. Главное знать, как говорится, от куда ноги растут. 

Буквенно-номерные коды ошибок появляются на экране, когда ваша PS3 сталкивается с той или иной проблемой. Чаще всего можно видеть следующие ошибки:

80010514 — ошибка, возникшая при чтении диска

Попробуйте:

Проверить диск на серьезные царапины и почистить его мягкой тряпочкой. Если проблема не решена вставьте другой диск и если ошибка все равно не устранена, то возможно проблема в дисководе.

80710B23 — означает, что нет возможности войти в PlayStation Network.  Это либо ведутся профилактические работы или очень много пользователей в сети. Лучше попробовать войти позже

80710102 — установить интернет-соединение невозможно

Проверьте подключена ли ps3 к интернету и правильно ли произведено подключение. Перезагрузите приставку, перенастройте на ней соединение, попробуйте сменить iP консоли. 

Еще существуют следующие ошибки:

80010001 — очень серьезная ошибка — не возможно запустить игры, так как эта возможность отключена. Одна из причин это конфликт Bluetooth устройств, перезагрузите их. Иногда возникает на прошитых приставках. Необходимо включить BD эмуляцию в настройках мультимана.

80010006 — такая же ошибка, что и выше

80010007 — такая же ошибка, что и выше

80010009 — необходимо правильно настроить гарнитуру

80010014 — перекачайте купленную Вами игру в ps store

80010017 — не получается запустить игру с диска, возможно диск поврежден, попробуйте другой, если не помогает, возможно причина в дисководе

80010029 — файл, который вы пытаетесь открыть — поврежден

80010036 — не возможно удалить файл. Переименуйте его и попробуйте удалить снова

8001050B — не возможно запустить демо с жесткого диска при вставленном диске в Blu-Ray дисковод. Попробуйте достать диск и провести операцию снова

8001050D — ошибка во время операции запуска. Извлеките диск и вставьте обратно.

8001050F — ошибка, которая имеет отношение к дате 1.03.10, и многие сервисы не работают, бывает только на толстушках

80010510 — игра с жесткого диска не может быть запущена. Возможно повреждены файлы 

80022A07 — проблема связанная с трофеями, их синхронизацией. перезагрузите ps3 или попробуйте позже

80022D68 — проблема связанная с трофеями, их загрузкой. перезагрузите ps3 или попробуйте позже

80023017 — PSN лежит, лучше подключитесь позже

80023102 — ошибка, возникающая, когда Вы пытаетесь пополнить баланс, причина не ясна. Лучше попробовать позже или попытаться пополнить баланс другим способом

8002311A — ошибка при погашении кодов. Возможно, кто-то сделал это за Вас и на другой ps3

8002880C — возникает при запуске DivX видео файлов — не поддерживаемый формат

80028818 — ошибка при воспроизведении видео, возможно не поддерживаемый формат или видео файл поврежден

80028EA5 — PSN лежит, лучше подключитесь позже. Либо проверьте подключение к интернету

80028EA6 — ошибка подключения к сети

80028EA8 — ваше интернет-соединение фильтруется. Повод обратиться к Вашему провайдеру за выяснением причины

80028F08 — данные на жестком диске повреждены. Если часто возникает, то проблемный жесткий диск. Форматируйте его либо замените.

80028F10 — ошибка вывода изображения на обычный телевизор, лучше всего купить нормальный современный телек

80028F17 
80028F18 
80028F19 
80028F1A — все эти ошибки связаны с запуском ps2 дисков, скорее всего провести операцию не возможно.

80029023 — время ожидания вышло.

80029564 — не удается установить скачанную игру. Перекачайте ее заново

80029906 — не верная кодировка файла

80029945 — запуск сторонних дисков не возможен

80029946 — ошибка при запуске двухслойного DVD. Скопируйте файлы с диска на приставку и запустите заново с жесткого диска

80029С55 — ошибка обновления с флешки. Либо прошивка повреждена, либо ее нужно переименовать в PS3UPDAT.PUP

80029C68 — файлы на флешке испорчены, причина либо в файлах либо в флешке

8002A10D — стоит блокировка на добавление человека в чат

8002A220 — PSN лежит, лучше подключитесь позже.

8002A4A6 — нет возможности игры онлайн, бывает на некоторых играх, причина в игре

8002A515 — PSN лежит, лучше подключитесь позже. Либо проблемы с интернетом

8002AA08 — проблема на сервере у Sony

8002AE1D — ошибка с сетью. Попробуйте в настройках ps3 поставить DNS: основной — 208.67.222.222, дополнительный — 208.67.220.220.

8002B241 невозможно передать через DVI аудио сигнал

8002F029 — ошибка обновления. Либо прошивка повреждена, либо ее нужно переименовать в PS3UPDAT.PUP.

8002F147 — Не получается обновить прошивку с помощью Интернета. Попробуйте отключить прокси, не использовать брэндмауэр (firewall), отключите поддержку UnuP

8002F14E — теперь у вас не приставка, а кирпич. Обратитесь к мастеру

8002F994 — очень много людей в настоящий момент качают обновление прошивки. Сделайте это позже

8002F997 — ошибка обновления с флешки. Либо прошивка повреждена, либо ее нужно переименовать в PS3UPDAT.PUP

8003051E — не получается сохранить игру. Проблема в игре

80030920 — копирование файла не возможно. Либо не хватает места, либо нет доступа к источнику

80031150 — системные настройки не удалось сохранить. Вернитесь к стандартным настройкам, нажав кнопку Х

80031601 — ошибка при создании аккаунта. Попробуйте еще раз, либо удалите лишние аккаунты

80110116 — ошибка при подключении пульта от PS3, попробуйте выключить все джойстики.

80130182 — данный код ошибки можно увидеть, при подключении к сети. Попробуйте поменять настройки соединения, либо дело вообще в провайдере

80130203 — ps3 корректно подключена к интернету, но не со всеми параметрами соединения порядок и не возможно выйти в PSN

80130301 — ps3 не может выйти в psn. Просто запустите любую игру с онлайн и запустите мультиплеер

8013030F — точка доступа к интернету не найдена, проблема либо с модулем, либо с роутером

80410A0B — проблема с psp возможно придется отнести ее к мастеру

80431068 — проблема с доступом к серверу, проверьте настройки подключения к серверу

80710016 — PSN перегружен и не доступен, лучше повторить попытку потом

80710092 — тайм-аут при ожидании psn

80710104 — роутер не отвечает. Перезагрузите его

80710541 — время ожидания ответа от сервера истекло. Возможно ошибочно введены настройки подключения к серверу

80710B24 — PSN не отвечает при попытке создать аккаунт. Попробуйте позже или введите другие данные.

80710D23 — возможно приставка перегрета. Дайте ей отдохнуть

80711008 — не верные настройки роутера, поменяйте их на стандартные или обратитесь к провайдеру

81019002 — сохранялки не Ваши или повреждены 

Огромное спасибо за внимание к статье. К сожалению, блок для коментариев пока не готов. Поэтому если остались вопросы, то оставляй их под схожим по тематике видео на моем YouTube канале. Буду рад ответить на все твои вопросы.

Код ошибки отображается на экране, когда система PS3 сталкивается с известной проблемой. Наиболее часто приходится иметь дело с тремя обозначениями:

80010514 — ошибка чтения диска
Система не может прочитать вставленный диск. Для решения проблемы можно:

• Проверить и при необходимости почистить используемый диск;
• Заменить диск, если на нем видны царапины;
• Вставить другой диск; если ошибка повторяется, необходимо связаться со службой поддержки.

80710B23 — невозможно подключиться к PlayStation Network. Возможно ведутся профилактические работы или слишком много пользователей. Попробуйте позже.

80710102 — невозможно установить интернет-соединение.

• Это может случиться в результате ошибки в процессе подключения к сети или разрыва интернет-соединения. Например, при использовании беспроводного соединения ошибка может быть вызвана слишком слабым сигналом, а с проводным соединением — перегруженным каналом связи.
• Или может быть конфликт IP адресов: в вашей локальной сети находится устройство с таким же IP адресом как у вашей PS3. Попробуйте поменять адрес приставки или найдите это устройство и поменяйте IP-шник там.
• Так же возможно, что приставка не может соединиться с маршрутизатором (router). Попробуйте перезагрузить маршрутизатор: выключите и через несколько секунд включите питание. Так же возможно ошибка сервера DNS. Может возникать при включенном DHCP на приставке, если DHCP- и DNS-сервера — точки доступа (ADSL-, VPN-, WiFi-модемы и маршрутизаторы) типа D-link DSL G-604T. Если раздать адреса ручками — то проблема пропадает. Если же это по каким-то причинам невозможно — помогает прогон теста соединения с интернетом (иногда работает только со второго раза).

Также, могут возникнуть следующие ошибки:

Description[edit | edit source]

Syscon memory includes a 0x100-byte table for storing error codes. Each error code consists of 4 bytes and an additional 4 bytes for its timestamp. The table can hold up to 32 errors. When the table reaches its maximum capacity and a new error needs to be stored, Syscon will delete the oldest error.

How to get the syscon error log[edit | edit source]

If the PS3 still boots to the XMB and is able to install and run applications, you can use programs such as those listed at the top of the Platform ID page.
If the PS3 fails to boot, you can still get the error log by connecting a PC to the PS3’s UART port using a «USB to TTLUART Adapter» and running the errlog command. There is also the clearerrlog command to clear the error table (handy to avoid confusion with old error codes that might have accumulated along the months/years and not related to the actual problem).

Error log format[edit | edit source]

There are 2 error log formats that depends of the syscon type: for Mullion, or for Sherwood.
The error codes and the timestamps are stored in little endian (right to left)
The timestamps are in J2000 format (number of elapsed seconds since 2000/1/1 12:00:00). They can be converted to the standard Unix epoch and then summed 30 years minus 12 hours (or 946684800 seconds). Check the link to the right for information: 1
If the battery was empty or removed when the error was triggered, the timestamp will be recorded as FFFFFFFF.
If the battery is replaced but the time is not configured in GameOS either manually or by network, the error log will seem to store timestamps starting with a date around 2005/12/31 00:00:00 (0x0B488680).
More info about error log timestamp formats and loops in the Talk page

• Unix epoch starts counting at 1970/1/1 00:00:00
• J2000 epoch starts counting at 2000/1/1 12:00:00

Offset(h) 00 01 02 03  04 05 06 07  08 09 0A 0B  0C 0D 0E 0F
                                                 
00003700  01 10 80 A0  01 10 80 A0  01 10 80 A0  01 10 80 A0
00003710  01 10 80 A0  01 10 80 A0  04 10 80 A0  01 10 80 A0
00003720  01 10 80 A0  01 10 80 A0  01 10 80 A0  01 10 80 A0
00003730  01 10 80 A0  04 10 80 A0  01 10 80 A0  01 10 80 A0
00003740  01 10 80 A0  01 10 80 A0  01 10 80 A0  01 10 80 A0
00003750  01 10 80 A0  01 10 80 A0  04 30 09 A0  04 30 09 A0
00003760  04 30 09 A0  04 30 09 A0  FF FF FF FF  01 10 80 A0
00003770  01 10 80 A0  01 10 80 A0  01 10 80 A0  01 10 80 A0
                                                 
00003780  20 CF 6D 16  13 23 A7 16  3E D6 D9 16  87 13 2A 17
00003790  17 3C 7C 17  E4 A2 A3 17  A2 15 D4 17  13 FB EB 17
000037A0  CD 7D EF 17  33 85 EF 17  12 8C EF 17  A7 D9 FB 17
000037B0  58 5E 0E 18  BB C9 66 18  CD 25 B5 18  49 C4 29 19
000037C0  75 D5 F9 19  04 8B 61 1B  17 67 D0 22  2D 67 D0 22
000037D0  03 07 6C 27  12 09 6C 27  FF FF FF FF  FF FF FF FF
000037E0  FF FF FF FF  FF FF FF FF  F0 E7 27 16  06 BD 33 16
000037F0  E5 DE 38 16  DD D4 5C 16  C4 AC 6C 16  EA C7 6D 16

Offset(h) 00 01 02 03  04 05 06 07  08 09 0A 0B  0C 0D 0E 0F
                                                 
00003700  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003710  22 43 40 A0  34 30 40 A0  FF FF FF FF  34 30 40 A0
00003720  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003730  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003740  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003750  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003760  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
00003770  22 43 40 A0  34 30 40 A0  22 43 40 A0  34 30 40 A0
                                                 
00003780  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
00003790  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037A0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037B0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037C0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037D0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037E0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000037F0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF

Offset(h) 00 01 02 03  04 05 06 07  08 09 0A 0B  0C 0D 0E 0F
                                                 
00000900  31 21 80 A0  73 D4 50 0B  30 20 40 A0  89 D4 50 0B
00000910  31 21 80 A0  8C D4 50 0B  30 20 80 A0  8E D4 50 0B
00000920  30 21 80 A0  8E D4 50 0B  31 21 80 A0  8F D4 50 0B
00000930  01 30 00 A0  FF FF FF FF  FF FF FF FF  FF FF FF FF
00000940  30 20 80 A0  75 D1 50 0B  30 20 80 A0  78 D1 50 0B
00000950  30 20 80 A0  B2 D1 50 0B  31 20 80 A0  B3 D1 50 0B
00000960  30 21 80 A0  BD D1 50 0B  30 21 80 A0  D5 D1 50 0B
00000970  30 21 80 A0  DF D1 50 0B  30 20 80 A0  E0 D1 50 0B
00000980  31 21 80 A0  84 D2 50 0B  30 21 80 A0  DC D2 50 0B
00000990  31 21 32 A0  4F D3 50 0B  31 20 40 A0  50 D3 50 0B
000009A0  31 21 80 A0  51 D3 50 0B  30 21 80 A0  57 D3 50 0B
000009B0  31 21 80 A0  59 D3 50 0B  31 21 80 A0  FF D3 50 0B
000009C0  31 21 80 A0  05 D4 50 0B  30 20 80 A0  06 D4 50 0B
000009D0  30 20 80 A0  07 D4 50 0B  31 21 80 A0  2D D4 50 0B
000009E0  31 20 80 A0  3A D4 50 0B  30 21 80 A0  42 D4 50 0B
000009F0  30 21 80 A0  72 D4 50 0B  31 21 80 A0  72 D4 50 0B

Offset(h) 00 01 02 03  04 05 06 07  08 09 0A 0B  0C 0D 0E 0F
                                                 
00000900  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000910  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000920  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000930  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000940  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000950  02 18 61 A0  FF FF FF FF  02 18 61 A0  FF FF FF FF
00000960  02 18 61 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
00000970  34 30 40 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
00000980  34 30 40 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
00000990  34 30 40 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
000009A0  34 30 40 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
000009B0  34 30 40 A0  FF FF FF FF  02 40 40 A0  FF FF FF FF
000009C0  34 30 40 A0  FF FF FF FF  FF FF FF FF  FF FF FF FF
000009D0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000009E0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF
000009F0  FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF

Error code format[edit | edit source]

The error codes follows the format:  A  R  ST  C  ERR , where:

 A  (Fixed)
A = This is always «A»

 R  (Reserved)
0-E = Unknown

• F = Frequent error (For example, Motherboard Damage/Breakdown, etc.)

 ST  (Step Number)
00-7F = Step Number of the Power On Sequence (POS). This is the Power On Self Test (POST) process. If successful, the BOOT process begins, which loads the OS.

80 = Static State (Power ON). The console completed the POST and was in a static state. An error occurred during the PS3 boot-up process. If you encounter an error during gameplay, it may happen with Step No. 80. For instance, if your NEC/TOKINs are failing, you may experience 80 1002 errors.

90 = Static State (Power OFF). The error happened when the PS3 was powering off. For example, if a problem causes the system to hang while shutting down the console will beep before powering off. An error with step no. 90 will be recorded in the errorlog.

A0 = Immediately after SYSCON reset. When power is supplied to the PS3, it should enter Standby mode. Early «Phat» models will have a solid red LED illuminated to indicate Standby mode. The PS3 contains a Standby circuit that requires constant power so that it can wait for the user to turn on the console. Many other electronics also utilize this feature. This is also referred to as a Vampire circuit, as it uses constant power even when a user is not using the console. It enables the ability to turn it on remotely, thus mitigating the need to physically flip a switch.

The PS3 reset circuit comprises the SYSCON and its clock generating crystal, Bluetooth/WIFI card, front power/eject and LED panel, and thermal monitor ICs. The SYSCON must detect whether the console is being manually started with the power button or over Bluetooth using the controller, hence these modules must be powered. It is important to ensure proper functioning of the thermal monitors before releasing power to the Southbridge, CPU, or GPU. Neglecting this step could pose a fire hazard. The thermal monitors ICs serve as the PS3’s fire alarms, and are critical safety equipment.

If there is a hardware issue in the circuit, an error will occur after the SYSCON reset, preventing the console from powering on. Instead of a solid red LED, the front LED will flash red indefinitely upon plugging in the console, indicating an error with the standby circuit. There will also be associated error log in the syscon which can help identify the specific component causing the issue.

5v_MISC powers the reset circuit, consisting of SMD/SMT components and ICs that power the modules above. Please refer to the Service manual (if available) for details. In particular, in the COK-001 service manual, the circuit diagram is provided on page 23/45. From the diagram, it’s evident that DC/DC converter IC6005 generates +3.3v_EVER, while IC6006 produces +1.8V_EVER, and IC6009 is responsible for generating +3.3V_THERMAL. These are the primary voltages utilized by the component in the reset circuit, such as the Wi-Fi/Bluetooth card necessary for initiating console startup remotely by pressing the PS button on the controller.

 C  (Category)

• 1 = System Error
• 2 = Fatal Error
• 3 = Booting Error
• 4 = Data Error

 ERR  (Error)

• This is a 3-Digit error code that gives specific information about the issue. For example, System error 002 (1002) means «RSX VRM Failure.»

Discussion

The three-digit error code may repeat in other categories, but that does not necessarily indicate the same issue. System error 001 and Fatal error 001 don’t mean the same thing. 1001 is «BE VRM Power Failure» and 2001 is «BE Error.» We wouldn’t be able to distinguish the error just by referencing it. This alone lacks sufficient information to comprehend the problem. The category gives the error context. To provide context, we use the 4-digit code CERR to differentiate them from one another.

Likewise, the Step Nump (ST) provides context to the 4-digit code. For example, you can have a CELL VRM Power Failure occur while playing an intense game (Static State, Power on). That would generate an 801001 (Step number 80). However, this error can also occur when the console is turned on, during the Power On Sequence Testing (POST), before it has a chance to start the boot loader, which loads the operating system, which in turn allows you to load the game. This time, it might generate error 101001. Step number 10 is lower than Step number 80, telling you this 1001 occurred earlier. The Category + Error tells you «What» happened. The Step Number tells you «when» it happened. It’s building context that can help you figure out what is causing the error.

It’s crucial to examine the entire error log, not just the 4-digit CERR, to understand «why» the error occurred. In the previous example, the A0801001 may indicate an issue with the NEC/TOKIN Proadlizers, a type of capacitor in the CELL CPU’s VRM (voltage regulation module). Conversely, A0101001 may result from various other factors, simply because there is a larger number of things that can go wrong. Therefore, it’s possible that the NEC/TOKINs are not the source of the error.

All of this means you must be knowledgeable about the hardware to comprehend the errors stored in the SYSCON. Unfortunately, there is not a unique error code for every potential issue. For example, there is no error that can indicate if Capacitor C6900 is short. Nonetheless, there are a few exceptions, where a specific code typically conveys the same meaning. For example, a fuse that has blown «usually» causes said code. But we cannot dismiss the possibility that a cap blowing on the same line could also be the cause, however unlikely that may be.

Examples:

A0801002

• System Error 002 (RSX VRAM Power Fail) which occurred while the System was successfully powered On.
• 1002 errors are known to be caused by faulty NEC/TOKINs, but other factors could also be involved. For additional information, refer to the Error Code section below.

A0403034

• Fatal Booting Error 034 (RSX/CELL Communication Error) which occurred at step no. 40 (BitTraining), before the Power On Sequence has completed.
• 3034 errors are often caused by defects on the BGA or Bump (among other issues). Experienced PS3 repair technicians have noted that it is almost exclusive to the RSX. Although we cannot completely exclude the possibility of a CELL BE BGA/Bump defect being the cause, it has been the exception to the rule. Time and experience have demonstrated that 3034 errors are primarily an RSX problem. A repair technician needs to decide which processor to reball/replace based upon the more likely candidate and proceed accordingly, using their judgement.
• See Error Code section below for more details.

A0213013

• 3013 errors are caused by Dead CELL BE CPU.

The following error code section will only list the last 4 numbers (category + error). However, remember the Reserved Area and Step Number can be useful to figure out «when» the error occurred and how frequent it is. The last four numbers are the most important for figuring out what specific error means, but you still need to figure out what it means in context of your issue. So you can diagnose the error and then fix it.

Error codes[edit | edit source]

System Errors[edit | edit source]

1001 (Power CELL)[edit | edit source]

• Components Involved:
  • CELL (IC1001 on COK-001)
  • NEC/TOKIN Proadlizers (C6140/C6141/C6142/C6143 on COK-001)
  • Other nearby components of the power block

This error may result from inadequate filtering on the CPU’s core voltage (VDDC) or an unexpected system shutdown. Voltage ripple or noise within a certain range could cause errors before they worsen into a CELL VDDC Power Failure (3003). There are several SMD filters, but the most critical ones are the NEC/TOKIN Proadlizers (capacitors). Bad NEC/TOKINs are responsible for 1002 errors on the GPU, but diagnosing 1001 errors is not as straightforward. You must observe the console experiencing YLOD while under load and confirm the generation of a new 1001 error. Otherwise, the 1001 code may indicate the console was not turned off correctly.

1001 errors can be recorded automatically when the system experiences an unexpected shutdown or loss of AC power. These errors frequently arise during testing when the console is frequently turned on or off instead of being gracefully shut down. A0801001 errors alone cannot prove that NEC/TOKINs are failing. Such errors are regularly found in the log of properly functioning machines and are not cause for concern unless the system is unexpectedly shutting down on its own.

A machine that can power on but displays graphical artifacts or no video may lead to misinterpretation of 1001 errors. In such cases, the console must be turned off forcibly using the power switch at the back of Phat/Fat models or by pulling the power cord in Slim and Super Slim models. This may cause 1001 or 1004 errors, which can be ignored if they were not generated under normal circumstances. If a console is showing artifacts/GLOD, fix the larger problem first (usually a GPU problem requiring a reball/replacement). Only after that, if stress testing results in 1001 errors, should you troubleshoot the CPU NEC/TOKINs.

Anecdote: One console, with faulty CPU NEC/TOKINs, displayed an A0901001 error only during shutdown. The Last of Us, a strenuous game, showed no signs of typical bad NEC/TOKIN behavior, and the system remained stable. However, it remained in shutdown for a prolonged period, resulting in the YLOD (3 beeps and flashing red light). It required a reset to power back on. Replacing the NEC/TOKINs resolved the problem.

1002 (Power RSX)[edit | edit source]

• Components Involved:
  • RSX (IC2001 on COK-001)
  • NEC/TOKIN Proadlizers (C6229/C6230/C6231/C6232 on COK-001)
  • Other nearby components of the power block

1004 (Power AC/DC)[edit | edit source]

• Components Involved:
  • Power Supply

When a console loses AC power, it may generate error A0801004. The 1004 error commonly occurs in machines that can power on but have graphical artifacts or no video, also known as GLOD. In such cases, the system should be powered off by using the power rocker at the back of the console (for Phat models), or by pulling the power cord (for slim and super slim models). This will cause a loss of AC power, which can lead to the error.

This error may be disregarded if it occurred due to abnormal circumstances, such as a power outage or accidental unplugging. Since it did not result from a hardware malfunction, it is not a significant concern. If a console displays artifacts or the GLOD, the main issue should be addressed first, typically involving a GPU problem requiring a reball or replacement. Afterward, if 1004 errors reoccur, the AC/DC line, PSU, and its connection to the DC-DC converters should be diagnosed.

1103 (Thermal Alert SYSTEM)[edit | edit source]

• Components Involved:
  • CELL
  • CELL temperature monitor (only in mullion syscons, the CELL temperature monitor for PS3 slims and super slims are unable to send this error code)

Syscons have a pad/pin specifically for this signal. It was given an official generic name (not indicating anything that triggers it) because several components can send it. In the first PS3 models (with mullion syscon?), the signal can be sent by CELL or the CELL temperature monitor using the official function names SYS_THR_ALRT or THERMAL_OVERLOAD.

But this electrical design is not specific for the PS3, there could be other devices based on the IBM CELL, and developed by SONY, where this error code is sent by other components, which could have more than one CELL so in general we could say this error code indicates one (or more) of the CELL processors (and maybe other components not present in retail PS3 models or his temperature monitor chips) is overheating.

At least 3 consoles that had CPU trace damage resulting from failed IHS delid attempts exhibited A0801103 and A0902203 errors.

1200 (Thermal CELL)[edit | edit source]

• Components Involved:
  • CELL

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 (Thermal RSX)[edit | edit source]

• Components Involved:
  • RSX

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. This error is rare. Out of hundreds of consoles and years of user reports this error has only occurred when the user forgot to replace the RSX heatsink when testing the console. It has not been reported under normal circumstances. The RSX tends to fail long before the TIM degrades to the point thermal shutdown is reached.

1203 (Thermal CELL VR)[edit | edit source]

• Components Involved:
  • CELL voltage regulators
  • Temperature Monitors

Some PS3 motherboards (TMU-520, COK-001, COK-002), have a temperature monitor located somewhere in the CELL power block. The other retail PS3 motherboard models doesnt meassures the temperature of the CELL VR

All the PS3 temperature monitor chips have a internal thermal sensor integrated + 2 pins for an optional external sensor. The temperature monitors for CELL and RSX are configured to use the external sensor, but this one for CELL VR probably uses the internal

1204 (Thermal South Bridge)[edit | edit source]

• Components Involved:
  • South Bridge

1205 (Thermal EE/GS)[edit | edit source]

• Components Involved:
  • CXD2953AGB or CXD2972GB
  • See also: Emotion Engine / Graphics Synthesizer

This error is specific for COK-001/CXD2953AGB (with full PS2 hardware compatibility, EE+GS) or COK-002/CXD2972GB (with partial PS2 hardware compatibility, GS only)

1301 (CELL PLL Unlock)[edit | edit source]

Has been reported in a console where the CPU die was chipped during a delid attempt gone wrong. The console exhibited a Green Light of Death (GLOD) and shutting down periodically with A0801301.

On another console 1301 occurred after both the CPU and RSX were reballed. The reball of cell likely failed, or damaged it.

On a third console it was reported after nearly every chip on the Motherboard was heat gunned. They probably didn’t achieve the necessary temperatures to reflow the CPU, and if they did they probably damaged it by using too much heat.

In all 3 cases the CPU was damaged or heated in some way.

14FF (Check Stop)[edit | edit source]

This error can occur when the console was on at the time the YLOD occurred. On consoles exhibiting this error, subsequent attempts to start the console resulted in a GLOD with 1601/1701 errors, or a YLOD within 2 seconds. SYSCON errors usually show one A0801601/A0801701 occurring at the same timestamp, followed thereafter by 3034/4xxx errors for all subsequent attempts to PWR it on. Or it’ll GLOD and throw more 1701/1601’s. The working theory is that there is a precarious solder joint (BGA or bump defect) teetering on the edge of breaking. It’ll soon switch to 3034 with or without 4xxx errors.

Complicating the issue is the fact that sometimes people will get a 1301 or 1802 also. It likely has to do with where the joints are failing and it’s involving those sub systems briefly before fully breaking.

Unlike Livelocks, which can be caused by both hardware and software conditions, Checkstops are a hardware issue. A checkstop occurs when the CPU or GPU, cache, memory, or I/O bus controller, finds something in an impossible state (impossible unless the Hardware is broken). The error isn’t identified as a particular bus transfer in progress, or the CPU/GPU detects the console is stuck (frozen, no progress being made with that operation). When nothing can be done for a long enough period of time, the checkstop errors is logged and BE ATTENTION is driven High. SYSCON immediately shuts the console down with error A08014FF and A0801701.

The most likely cause of the error is a failing GPU (RSX) solder joint (BGA or Bumps). A distant second is a failing CPU (CELL) solder joint (BGA).

1601 (CELL Livelock Detection)[edit | edit source]

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 spreadhseet. 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.

Basically this means the console froze and had to reboot. In the PS3 this is often preceded by graphical artifacting. The cause is often a solder joint on the RSX (BGA or Bumps). Generally these errors are seen in the early stages of a GPU failure. However CPU failures cannot be ruled out. They are just less likely.

Speculation:

As the impedance of propagating solder cracks increases, the digital logic core has a harder time calibrating the FlexIO during BitTraining. Once impedance reaches the limits of the compensation network, interference causes random issues during software execution. LiveLock conditions cause BE Attention signal to be driven High and the SYSCON shuts the console down (YLOD) with errors A0801601 and A0801701.

As the console cools the microscopic gaps in the solder can be physically reconnected by thermal warping. Warping is due to differences in the Coefficients of Thermal Expansion (CTE) between materials in the motherboard and processor. This expansion and contraction can reconnect the solder joints just enough to allow the console to boot. Or it may disconnect them.

• If they reconnected, the console will boot until it experiances another 1601/1701 event.
• It they do not reconnect, the console cannot complete BitTraining and will fail in POST with error A0403034. Often with an associated Data error, such as A0404401 (if the broken solder joint affected a Data line on one of the SPI lines). If there is no Data error, the broken joint only affected the voltage for the SPI line. Either RSX_VDDR or YC_RC_VDDIO.

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 BE ATTENTION)[edit | edit source]

BE ATTENTION is an active-high output flag sent by the CPU to the SYSCON. During initialization & configuration it is used to request an operation by the SYSCON. When ATTN goes High the syscon reads the SPI Status Register to determine the cause of the Attention signal. It remains high until software resets the condition that caused it.

After Power On Reset the BE attention signal is driven low and is supposed to stay there! If there is a Checkstop error (14FF), Livelock Detection (1601), or PLL Unlock (1301) the CPU enters a fault condition and raises the Attention signal (1701) during operation. The SYSCON sees this and immediately shuts the console down with error code A0801701 and usually another error indicating the cause. One common way this happens is when a solder connection breaks while the system is on. This could be the BGA (Ball Grid Array) or the Solder Bumps under the die.

Going into more detail, BE Attention is used during Power On Reset (POR)…

• To load CPU VID voltage from the VRM internal registers.
• To Write configuration-ring data (Important CPU Config settings that should only be modified at boot, otherwise errors can occur).
• To calibrate the FlexIO interface (BitTraining).

If Attention occurs during the Power ON State (Step# 80) it indicates an error condition. Basically, something is flagged by the Processor as abnormal. It’s forced to attempt to resolve the problem before it can continue with whatever it was trying to do. If the error condition cannot be resolved, the CPU sends the ATTENTION signal to the SYSCON. The SYSCON immediately shuts off the console, then reads the SPI Status Register to determin the cause. Then it records the A0801701 in it’s errorlog along with the specific cause (if it determined one). Errors that can cause the Attention include:

• Unresolved Checkstop errors (14FF)
• Livelock Detection (1601)
• PLL Unlock Condition (1301)
• BGA/Bump Defect that occurs while the Console was On (Step# 80). Subsequent attempts to power on the console would result in 3034/4xxx errors.

A user get this error code with a damaged hard drive. He was transfering some games via FTP, and his console turned off with Ylod. When he tried to turn on again, he get a Glod. Problem was fixed just by changing the HDD.

1701 has been reported from using homebrew apps that caused a software conflict. Uninstalling the software can resolve the issue. It that’s not possible because the system is locked up, it may be necessary to restore the operating system (OS).

1802 (RSX Initialization)[edit | edit source]

A0201802 is the error the SYSCON will return when there is no RSX installed at all! Step# 20 is when the RSX is first Initialized. So if it’s not responding that early in the Power On Sequence, then it’s Dead-Dead or completely missing!

A0801802 is occuring 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.

1900 (RTC Voltage)[edit | edit source]

RTC voltage

1901 (RTC Oscilator)[edit | edit source]

RTC oscilator

1902 (RTC Access)[edit | edit source]

RTC access

Fatal Errors[edit | edit source]

• This fatal error codes seems to be repeated up to 3 times for 3 special cases, as example, errors 2003, 2103, and 2203 are related with southbridge, the only thing that changes in the error code is the second digit (located inmediatly after the category 2). If at some point we find what means that second digit we can join the wiki page sections together (with titles: «2001 & 2101», «2002 & 2102», «2003 & 2103», etc…)

In other words, there are 3 groups: 20xx (composed by 13 errors), 21xx (composed by 13 errors), and 22xx (composed by 1 error). See Discussion

2001 (CELL)[edit | edit source]

CELL (IC1001)

2002 (RSX)[edit | edit source]

RSX (IC2001)

2003 (South Bridge)[edit | edit source]

South Bridge Error (IC3001)

2010 (Clock Subsystems)[edit | edit source]

Clock Generator Error (IC5001)

2011 (Clock CELL)[edit | edit source]

Clock Generator Error (IC5003)

2012 (Clock CELL)[edit | edit source]

Clock Generator Error (IC5002)

2013 (Clock CELL, RSX, South Bridge)[edit | edit source]

Clock Generator Error (IC5004)

2020 (HDMI)[edit | edit source]

HDMI Error (IC2502)

2022 (DVE)[edit | edit source]

DVE Error (IC2406, CXM4024R MultiAV controller for analog out)

This error occurs when you see no video out using HDMI on any Samsung Smart TV.

You can intentionally produce this error code by making the TV detect another console first (a PS4), turn off the TV, swap the HDMI cable from the PS4 to the PS3, and turning back on the TV. You can fix this error code by replugging it in while the TV is on.

This error is also present when the console produces graphical artifacts on the screen. The console freezes and cannot be used, forcing the user to turn off the console. This produces the 2022 error code and is an early sign of GLOD.

2024 (AV)[edit | edit source]

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, CELL)[edit | edit source]

• Components Involved:
  • CELL
  • CELL Temperature Monitor (IC1101 on COK-001)

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

2031 (Thermal Sensor, RSX)[edit | edit source]

• Components Involved:
  • RSX
  • RSX Temperature Monitor (IC2101 on COK-001)

2033 (Thermal Sensor, South Bridge)[edit | edit source]

• Components Involved:
  • South Bridge
  • South Bridge Temperature Monitor (IC3101 on COK-001)

2040 (Super Slim CELL BE)[edit | edit source]

2044 (Super Slim short circuit — BT/Wi-Fi and 5Volt)[edit | edit source]

2101 (CELL)[edit | edit source]

CELL (IC1001)

2102 (RSX)[edit | edit source]

RSX (IC2001)
I had detected a short in the CELL, after removing one of the NEC/TOKINS, the error had changed.

After applying slight pressure to the CELL, I used some thermal pads to create the pressure. 5 small, 1 mm pads, and two larger 2mm pads, the same size and depth as the ones used on the southbridge chip) The console now boots and runs without any issues.

2103 (South Bridge)[edit | edit source]

Southbridge Error (IC3001)

2110 (Clock Subsystems)[edit | edit source]

Clock Generator Error (IC5001)

This error can be caused by a 5V_MISC short to ground. One user had an A0022110 after replacing IC6105 (Buck Converter) and accidentally bridging the 5V voltage input. So check the 5V line for shorts.

This error has been resolved by a number of users who had a short on F6001. It is important to note that something usually causes that fuse to blow, like a short. So it’s important to troubleshoot the board to find and repair the shorting component before replacing the fuse. Otherwise the new one will blow too.

One user, who resolved this error on his C model PS3, noted «very short YLOD. Error code shows 2110[…]Some earlier code shows 1001 and 1002.» The 1001 & 1002 errors he noted in the log before the 2110 appeared may have been a clue that C6019 or C6020 (as they are in parallel) was deteriorating. Further investigation is needed to confirm this hypothesis, however. In his case, C6019 was shorting and caused F6001 to blow. This short overloaded F6001 and cut power to many Subsystems, such as the HDD, USB ports, South bridge, CPU, GPU, etc.
Another user confirmed this. The error log was showing code 2110 and one entry earlier was showing code 1001. Checking both capacitors after removing them from the board, confirmed that one capacitor was reading 140 ohms and not reading as a capacitor, so it was working as a resistor causing extra load in the fuse.

One particularly noteworthy component is IC6020, which supplys +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.

2111 (Clock CELL)[edit | edit source]

Clock Generator Error (IC5003)

2112 (Clock CELL)[edit | edit source]

Clock Generator Error (IC5002)

2113 (Clock CELL, RSX, South Bridge)[edit | edit source]

Clock Generator Error (IC5004)

Analog Voltage for the core PLL of IC5004, which is an ICS9214 Clock Generator used to support the Rambus XDR memory subsystem and Redwood logic interface.

SW_1_B enables control Pin 5 on IC6013, which generates +2.5V_LREG_XCG_500_MEM. If that fails it generates A0092113.​

2120 (HDMI)[edit | edit source]

HDMI Error (IC2502)

A0202120/A0213013 error combinations are common. They appear to be related to VDDIO. IC6301 is involved in the formation of +1.7V_MISC, which amonge other things provides input power to the DC-DC converters that output +1.2V_YC_RC_VDDIO, +1.5V_YC_RC_VDDA, +1.2V_SB_VDDC and +1.2V_SB_VDDR. Lack of voltage to these DC/DC converters downstream of IC6301 suggests F6302 has blown. A number of people have fixed these 2120/3013 errors by finding shorts at or near C6320 and replacing Fuse F6302. But there are many other SMD nearby that might cause these fuses to blow. So you will need to track the source of the short and fix it, or the fuse will just blow again.

A bad thermistor (TH2501) has been reported to cause A0002120.

A0802120 and A0902120 errors may be related to the actual HDMI transmitter (IC2502). Or they can be caused by BGA/Bump defects affecting VDDIO, on the RSX or CELL. BGA defects on the RSX VDDIO pads have been confirmed with a pressure test to have caused 2120 errors.

2122 (DVE)[edit | edit source]

DVE Error (IC2406, CXM4024R MultiAV controller for analog out)

2124 (AV)[edit | edit source]

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, CELL)[edit | edit source]

• Components Involved:
  • CELL
  • CELL Temperature Monitor (IC1101 on COK-001)

2131 (Thermal Sensor, RSX)[edit | edit source]

• Components Involved:
  • RSX
  • RSX Temperature Monitor (IC2101 on COK-001)

2133 (Thermal Sensor, South Bridge)[edit | edit source]

• Components Involved:
  • South Bridge
  • South Bridge Temperature Monitor (IC3101 on COK-001)

2203 (South Bridge)[edit | edit source]

From sabotage tests it was found that disabling +2.5V_SB_PLL_VDDC
produced four A0802203 errors.​ Also, disabling +1.2V_SB_VDDR produced A0302203 & A0403034.

2310[edit | edit source]

Fatal Boot Errors[edit | edit source]

3000[edit | edit source]

Power Failure

3001[edit | edit source]

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 somewhere on the line.

3002[edit | edit source]

Power Failure

3003 (CELL Core Power Failure)[edit | edit source]

This error will occur in the case of a PWR failure on the main core voltage of the CPU (VDDC). 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.

A shorted Blu-Ray drive can cause this error as well. Be sure that your drive is going well before doing anything on your console.

3004 (RSX Core Power Failure)[edit | edit source]

This error will occur in the case of a PWR failure on the main core voltage of the GPU (VDDC). 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[edit | edit source]

CELL Error

Observations:
A user triggered this error by injecting 3.3V into PWRGD (power good) of IC6103 (NCP5318 CPU Buck Controller). It generated error 20 1001 and 20 3010.
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.

This problem may be related to the PLL signal generator circuit, open resistors, crystal oscillator or even the integrated itself (CDC735/CDC736/4227ANLG)

3011[edit | edit source]

CELL

3012[edit | edit source]

CELL

3013[edit | edit source]

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.

A0212120/A0213013 error combinations are common. They appear to be related to VDDIO. IC6301 is involved in the formation of +1.7V_MISC, which among other things provides input power to the DC-DC converters that output +1.2V_YC_RC_VDDIO, +1.5V_YC_RC_VDDA, +1.2V_SB_VDDC and +1.2V_SB_VDDR. Lack of voltage to these DC/DC converters downstream of IC6301 suggests F6302 has blown. A number of people have fixed these 2120/3013 errors by finding shorts at or near C6320 and replacing Fuse F6302. But there are many other SMD nearby that might cause these fuses to blow. So you will need to track the source of the short and fix it, or the fuse will just blow again.

One person reported A0202120/A0213013 when his CPU substrate (interposer) was cracked in half by a failed delid attempt.

Through sabotage testing is was found that disabling +1.2V_YC_RC_VDDIO caused A0213013​.

Also through sabotage testing, it was found that when L6305 is removed it cut’s off +1.8V_RSX_FBVDDQ (VRAM voltage). It caused a 10x A0202120 & 1x A0213013 error combo.

3020[edit | edit source]

CELL

3030[edit | edit source]

CELL

3031[edit | edit source]

CELL

3032[edit | edit source]

CELL Error

It was discovered throgh sabotage testing that disabling +1.5V_YC_RC_VDDA caused error A0313032

3033[edit | edit source]

CELL

3034[edit | edit source]

CELL / RSX Communication Error

This is the most common error seen in early Phat model PS3’s with the hottest 90nm RSX and CELL processors. It is the hallmark of a BGA defect (such as a cracked solder ball). It is by no means limited to the early models, however. These errors have been seen in every model of PS3 with varying frequency. The most reliable consoles appear to be those with a CPU/GPU of smaller manufacturing process, such as the Super Slim (SS) models (42xx and later) which have a 45nm CELL and 28nm RSX. The least reliable are the PS2 Backwards Compatable A-E Models, which have 90nm RSX/CELL.

The root cause is mechanical fatigue due to thermal cycling. The materials used to contruct the motherboard and processors have different properties. For example, the cooefficient of thermal expansion for FR4 Fiberglass used in the Motherboard and Processor Substrate is different than that of the copper BGA pads, which is different than that of the Lead-Free solder used to join them. This means they will expand and contract at different rates as the chip heats up and cools down, which applies shearing force to the BGA. Over many thermal cycle this deforms the solder balls and cause a defect (Such as a solder crack, torn trace, or the ball may pull away from the pad).

3034 is triggered when the voltage or data lines connecting the CPU/GPU are broken. There is often a data error (4XXX) that also appears, but not always. The most common cause is a BGA defect on the RSX, which usually requires a reball/reflow to repair. Something about the RSX construction or workload causes it to fail more frequently, but the CPU can fail too. However, it’s not always a BGA defect. The bumps on either chip can fail, Flex IO traces (the data lines that connect the CPU/GPU) can be broken/scratched, or accumulated damage from wear and tear (electromigration) can also cause this error. The true percentage of consoles with BGA defects that can be fixed with a reball/reflow is unknown. However, there is evidence to suggest that the underfill used to reinforce the CPU/GPU die and RSX Ram bumps was not as effective when the PS3 was manufactured. This could explain many of the consoles who’s reball fails prematurely afterwards.

If a reflow/reball of both the CPU/GPU fails, then the chip is beyond repair and needs replaced. The RSX can be replaced with the same model without modification. It can be replaced with a different model using a modchip (or new syscon modification) that injects the correct RSX ID during boot. This has been nicknamed a «Frankenstein Mod.» Since they are married to each other, the CPU can only be replaced if also replacing the chipset (NAND/NOR and SYSCON Chips). Since the CPU can’t as easily be replaced, a dead CPU is usually considered unrepairable.

3035[edit | edit source]

CELL and RSX

3036[edit | edit source]

CELL and RSX

3037[edit | edit source]

CELL and RSX

3038[edit | edit source]

CELL and RSX

3039[edit | edit source]

CELL and RSX

3040[edit | edit source]

Flash

A0603040 is know to be caused by not soldering the flash (NAND/NOR) back on properly. It happens when the flash is not powered. Step #60 is when the StarShip 2 flash controller and NAND/NOR are initialized, kicking off the firmware sequence that loads the Operating System. Check their voltages and be sure the FW is not corrupt. If you have a backup, you could try replacing the Flash to see if a module failed.

3041[edit | edit source]

Flash (eMMC)

Data Errors[edit | edit source]

• This error codes seems to be repeated up to 5 times for 5 special cases, as example, errors 4001, 4101, 4201, 4301, 4401 are related to CELL, the only thing that changes in the error code is the second digit (located inmediatly after the category). If at some point we find what means that digit we can join the wiki page sections together (with titles: «4001, 4101, 4201, 4301, 4401», etc…)

4001[edit | edit source]

CELL

4002[edit | edit source]

RSX

4003[edit | edit source]

Southbridge

4011[edit | edit source]

CELL

4101[edit | edit source]

CELL

4102[edit | edit source]

RSX

4103[edit | edit source]

Southbridge

4111[edit | edit source]

CELL

4201[edit | edit source]

CELL

4202[edit | edit source]

RSX

4203[edit | edit source]

Southbridge

4211[edit | edit source]

CELL

4212[edit | edit source]

RSX

4221[edit | edit source]

CELL

4222[edit | edit source]

RSX

4231[edit | edit source]

CELL

4261[edit | edit source]

CELL

4301[edit | edit source]

CELL

4302[edit | edit source]

RSX

4303[edit | edit source]

Southbridge

4311[edit | edit source]

CELL

4312[edit | edit source]

RSX

4321[edit | edit source]

CELL

4322[edit | edit source]

RSX

4332[edit | edit source]

RSX

4341[edit | edit source]

CELL

4401[edit | edit source]

CELL or RSX

4402[edit | edit source]

CELL or RSX

4403[edit | edit source]

CELL or RSX

4411[edit | edit source]

CELL or RSX

4412[edit | edit source]

CELL or RSX

4421[edit | edit source]

CELL or RSX

4422[edit | edit source]

CELL or RSX

4432[edit | edit source]

CELL or RSX

4441[edit | edit source]

CELL or RSX