Hello everyone,
I’m looking for board-level diagnostic advice for a PS5 Pro CFI-7000 that shuts down approximately 1–2 seconds after power-on.
I’m from Ukraine, where obtaining official PlayStation repair is currently extremely difficult. The main official service facility available to us was destroyed during a missile strike, and the remaining out-of-warranty option was an expensive exchange for a refurbished console rather than component-level repair of my own unit.
The console is approximately 18 months old and has only about 250 hours of use. Because of the war, electricity outages and other circumstances, I had very few opportunities to play it before the warranty expired. Replacing the console is unfortunately not financially realistic for me, so I am trying to help the technician find a repairable board-level fault.
Failure history
The console was running a relatively undemanding PS4 game when I stepped away for approximately 30 seconds. When I returned, it had completely shut down.
Its current behaviour is consistent:
Troubleshooting already performed
PSU and motherboard inspection
The PSU has been thoroughly tested by the technician and confirmed to be working correctly, including its 12 V output. The PSU itself has therefore been ruled out.
The technician has also reported:
UART/error log
The fresh log contains the following relevant errors:
80810001 — Severe
Power Sequence Error / General Power Failure
Reported possibilities include peripheral, GDDR6, APU or data-line fault.
Raw example:
OK 00000000 80810001 0000000B FFFF0042 10000000 217C 0020 FFFF FFFF:8C
80000009 — Low
AC In Detect / Unexpected Power Loss or Shutdown Failure.
This may simply be a consequence of the immediate shutdown.
80801002 — High / not found in the database
This is the important code because it appears after almost every fresh startup attempt.
Raw examples from different attempts:
OK 00000000 80801002 00000001 FF100005 10000100 2013 0036 1EB1 1D1D:E4
OK 00000000 80801002 00000106 FF100005 10000100 2013 0036 22B0 22C6:CA
OK 00000000 80801002 000000FC FF100005 10000100 2013 0036 2270 22D0
C
OK 00000000 80801002 000000D5 FF100005 10000100 2013 0036 21D5 2280
1
The changing values appear to include timing or state information, but the fields FF100005 10000100 2013 0036 remain consistent.
80800022 — Severe
No/bad communication between APU and RAM after APU initialization.
Raw example:
OK 00000000 80800022 000000F1 FF110005 10000100 2013 0036 2269 2292:CB
Unlike 80801002, this APU-to-RAM error appears only intermittently and is not recorded after every startup attempt.
Theories received so far
One person reported seeing 80801002 associated with SSD-controller faults on regular PS5 consoles. However, he had not encountered it on a PS5 Pro and could not suggest a confirming measurement; in those cases, the SSD controller was replaced experimentally and the console was tested afterwards.
Other suggestions have included:
Questions
Thank you very much for reading and for any technical guidance you may be able to provide.
I’m looking for board-level diagnostic advice for a PS5 Pro CFI-7000 that shuts down approximately 1–2 seconds after power-on.
I’m from Ukraine, where obtaining official PlayStation repair is currently extremely difficult. The main official service facility available to us was destroyed during a missile strike, and the remaining out-of-warranty option was an expensive exchange for a refurbished console rather than component-level repair of my own unit.
The console is approximately 18 months old and has only about 250 hours of use. Because of the war, electricity outages and other circumstances, I had very few opportunities to play it before the warranty expired. Replacing the console is unfortunately not financially realistic for me, so I am trying to help the technician find a repairable board-level fault.
Failure history
The console was running a relatively undemanding PS4 game when I stepped away for approximately 30 seconds. When I returned, it had completely shut down.
Its current behaviour is consistent:
- The first press of the power button sometimes produces no response.
- On the next press, it beeps and the blue light appears.
- The fan begins spinning normally.
- After approximately 1–2 seconds, all power is cut immediately.
- The blue light and fan stop at exactly the same moment.
- It never reaches a solid white light.
- It shuts down long before the second beep, so Safe Mode is impossible.
Troubleshooting already performed
- Disconnected every USB device and external cable.
- Removed the additional M.2 SSD.
- Removed the detachable Blu-ray drive.
- Tested the console in minimum configuration.
- Left it completely disconnected from power for more than 24 hours.
- Discharged it by holding the power button while unplugged.
- Tested it after fully cooling down.
- Confirmed that the behaviour is unchanged without HDMI or any other peripheral attached.
PSU and motherboard inspection
The PSU has been thoroughly tested by the technician and confirmed to be working correctly, including its 12 V output. The PSU itself has therefore been ruled out.
The technician has also reported:
- no visible motherboard damage;
- no short circuits found;
- no obviously abnormal resistance measurements;
- static voltages and resistances appear consistent with a working board.
UART/error log
The fresh log contains the following relevant errors:
80810001 — Severe
Power Sequence Error / General Power Failure
Reported possibilities include peripheral, GDDR6, APU or data-line fault.
Raw example:
OK 00000000 80810001 0000000B FFFF0042 10000000 217C 0020 FFFF FFFF:8C
80000009 — Low
AC In Detect / Unexpected Power Loss or Shutdown Failure.
This may simply be a consequence of the immediate shutdown.
80801002 — High / not found in the database
This is the important code because it appears after almost every fresh startup attempt.
Raw examples from different attempts:
OK 00000000 80801002 00000001 FF100005 10000100 2013 0036 1EB1 1D1D:E4
OK 00000000 80801002 00000106 FF100005 10000100 2013 0036 22B0 22C6:CA
OK 00000000 80801002 000000FC FF100005 10000100 2013 0036 2270 22D0
OK 00000000 80801002 000000D5 FF100005 10000100 2013 0036 21D5 2280
The changing values appear to include timing or state information, but the fields FF100005 10000100 2013 0036 remain consistent.
80800022 — Severe
No/bad communication between APU and RAM after APU initialization.
Raw example:
OK 00000000 80800022 000000F1 FF110005 10000100 2013 0036 2269 2292:CB
Unlike 80801002, this APU-to-RAM error appears only intermittently and is not recorded after every startup attempt.
Theories received so far
One person reported seeing 80801002 associated with SSD-controller faults on regular PS5 consoles. However, he had not encountered it on a PS5 Pro and could not suggest a confirming measurement; in those cases, the SSD controller was replaced experimentally and the console was tested afterwards.
Other suggestions have included:
- PS5 Pro SSD controller CXD90070GG;
- onboard SSD NAND or its BGA connections;
- SSD cache/memory associated with the controller;
- Southbridge or SSD communication;
- RAM/APU BGA fault;
- a fault on the bus between the APU and memory;
- an enable, reset, clock or power-good signal failing dynamically during startup.
Questions
- Does anyone have a reliable interpretation of PS5 Pro error 80801002?
- Has anyone personally repaired a CFI-7000 with this exact code and 1–2 second shutdown behaviour?
- Is 80801002 known to indicate the CXD90070GG SSD controller, its associated memory/NAND, Southbridge communication, or another subsystem?
- Could the intermittent 80800022 be a secondary consequence of the power sequence being aborted, or does its presence strongly indicate a physical APU/RAM/BGA fault?
- Which dynamic measurements would be most useful during the 1–2 second startup window? For example, particular SSD, RAM or APU rails, enable/power-good signals, reset lines or clock activity.
- Is there a non-destructive way to distinguish an SSD-controller fault from an APU/RAM communication failure before attempting BGA replacement?
Thank you very much for reading and for any technical guidance you may be able to provide.






