PS3 PS3 CECHC04 From YLOD to GLOD - Particular Case

Hi all,
I recently came across a very particular case that I think requires more attention than the usual GLOD -> make it Frankie.
The PS3 arrived with the usual YLOD, warranty sticker intact. Inside was relatively clean and the thermal paste was not very dry (at the center it was almost liquid).
Before jumping to the conclusion of bumpgate, I connected UART to get to internal mode and retrieve the error log as usual.
Code:
ofst[ 84]:err_code:0xffffffff, clock:0x30d754dc  2025/12/19 00:12:12
ofst[ 88]:err_code:0xa0801001, clock:0x30d7550c  2025/12/19 00:13:00
ofst[ 92]:err_code:0xa0801001, clock:0x30d75546  2025/12/19 00:13:58
ofst[ 96]:err_code:0xa0801001, clock:0x30d75826  2025/12/19 00:26:14
ofst[100]:err_code:0xa0801001, clock:0x30d75903  2025/12/19 00:29:55
ofst[104]:err_code:0xa0801001, clock:0x30d75c0a  2025/12/19 00:42:50
ofst[108]:err_code:0xa0801001, clock:0x30d75c1e  2025/12/19 00:43:10
ofst[112]:err_code:0xa0801001, clock:0x30d75c4f  2025/12/19 00:43:59
ofst[116]:err_code:0xa0801001, clock:0x30d8890b  2025/12/19 22:07:07
ofst[120]:err_code:0xa0801001, clock:0x30d88921  2025/12/19 22:07:29
ofst[124]:err_code:0xa0081004, clock:0x30ec132a  2026/01/03 17:49:30
ofst[  0]:err_code:0xa0081004, clock:0x30f3f71b  2026/01/09 17:27:55
ofst[  4]:err_code:0xa0081004, clock:0x30f3f721  2026/01/09 17:28:01
ofst[  8]:err_code:0xa0081004, clock:0x30f3f728  2026/01/09 17:28:08
ofst[ 12]:err_code:0xa0081004, clock:0x30f3f72e  2026/01/09 17:28:14
ofst[ 16]:err_code:0xa0081004, clock:0x31093ff8  2026/01/25 20:56:24
ofst[ 20]:err_code:0xa0081004, clock:0x31094004  2026/01/25 20:56:36
ofst[ 24]:err_code:0xa0081004, clock:0x3109400a  2026/01/25 20:56:42
ofst[ 28]:err_code:0xa0081004, clock:0x31094012  2026/01/25 20:56:50
ofst[ 32]:err_code:0xa0081004, clock:0x31094018  2026/01/25 20:56:56
ofst[ 36]:err_code:0xa0091004, clock:0x31094298  2026/01/25 21:07:36
ofst[ 40]:err_code:0xa0101004, clock:0x310942a0  2026/01/25 21:07:44
ofst[ 44]:err_code:0xa0101004, clock:0x310942a6  2026/01/25 21:07:50
ofst[ 48]:err_code:0xa0091004, clock:0x31094338  2026/01/25 21:10:16
ofst[ 52]:err_code:0xa0091004, clock:0x31094340  2026/01/25 21:10:24
ofst[ 56]:err_code:0xa0101004, clock:0x31094343  2026/01/25 21:10:27
ofst[ 60]:err_code:0xa0101004, clock:0x3109434e  2026/01/25 21:10:38
ofst[ 64]:err_code:0xa0101004, clock:0x31094354  2026/01/25 21:10:44
ofst[ 68]:err_code:0xa0101004, clock:0x31094362  2026/01/25 21:10:58
ofst[ 72]:err_code:0xa0101004, clock:0x31094366  2026/01/25 21:11:02
ofst[ 76]:err_code:0xa0091004, clock:0x3109436b  2026/01/25 21:11:07
ofst[ 80]:err_code:0xa0101004, clock:0x31094372  2026/01/25 21:11:14

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0201004
[SSM] *** Power Fail ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000

So we have:
  • a lot of 1001 that happened when the console was powered on (set 80)
  • a lot of 1004 when the console was powering on at stages 08, 09, 10, so the console was failing more in the middle of the booting process
  • bringup shows error 1004 at stage 20
I think the errors were compatible with a non-working power supply because:
  • 1001 indicates improper shutdown caused, for example, by loss of power (or NEC/TOKINs problems but we have to verify this after there are no more 1004)
  • 1004 indicates loss of AC power that, in this case, happens during the initial boot process (08, 09, 10)
The logical conclusion for me was to replace the power supply, and indeed now it powers on and stays on forever.
But what I have now is:
  • no display both with vga and hdmi
  • no blinking HDD light
  • sometimes the controller LEDs blink, but not always
  • it retrieves, spins (not at reading speed), and ejects Blu-ray discs
  • sometimes in recovery mode I get a black screen, and sometimes no signal at all
To shut it off, I have to keep pressing the power button or use the shutoff command in internal mode.
Another strange thing is this:

Code:
becount
Bringup : 726 times
Shutdown: 156 times
Power-on: 2day 23hour 24min 36sec

So, very little power-on time, but a very high bringup count and low shutdown count. Maybe it was shut off improperly a lot of times because it had a defective power supply from the start?
Anyway, I read a lot of posts by Rip-Fenix, so I tried almost all the troubleshooting information, but I'm still undecided if I should make it a Frankie or if there is something I'm missing.
Here is the full bringup log after replacing the power supply:

Code:
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD

Powerstate

Code:
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE

Shutdown:

Code:
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

I also found these two commands (hdmi chstat 0) for checking the HDMI communication.
When connecting to the TV, it seems it is waiting for the resolution from the RSX, but I would like a second opinion on this.

When HDMI is unplugged:
Code:
hdmi chstat 0
[HDMI] ----------------------------
[HDMI] -- HDMI Channel 0 Context --
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[System Management]
[HDMI]     - SSM Task ID : 13
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : EVENT FLAG
[HDMI]     - SSM State : UnPlg
[HDMI]     - SSM Mutex Information : ID[2] LockTID[0] WaitTID[0]
[HDMI]     - SSM Event Flag Info : ID[2] WaitTID[13] FlagPattern[0]
[HDMI]     - SSM Mode : DVI
[HDMI] ------------------------------------------------------------------------------------
[HDMI]     - Authentication Status : NotStart
[HDMI]     - Repeater : Sink
[HDMI]     - KSVs     : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[Interrupt]
[HDMI]     - External Interrupt Number of Mullion : 7
[HDMI]     - Interrupt Mask Pattern in SiI : [0x0000E0]
[HDMI]     - Interrupt Register Size : 3
[HDMI]     - Interrupt Task ID : 12
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : SLEEPING
[HDMI]     - Semapho Information : ID[38] WaitingTID[0] Count[1]
[HDMI]     - Plug Status : UnPlug
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[SiIType]
[HDMI]     - Chip Type : 9132
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[EDID]
[HDMI]     - EDID Mutex ID : 3
[HDMI]     - EDID Mutex Information : ID[3] LockTID[0] WaitTID[0]
[HDMI]     - EDID Block Size : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[I2C Bus]
[HDMI]     - Device Address 0x72(0) 0x7A(1)
[HDMI]     - Semapho Information : ID[36] WaitingTID[0] Count[1]
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[AV Setting]
[HDMI]     - Audio Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]     - Video Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]                  Setting  : 11 80 30 01 88 20 00 33 98 37 00 14
[HDMI]                           : 82 02 0D 46 00 18 00 11 00 00 00 00 00 00 00 00 00 00 00
[HDMI]

After plugging the HDMI cable:

Code:
[mullion]$
Press Ctrl+C to exit
>$ hdmi chstat 0
hdmi chstat 0
[HDMI] ----------------------------
[HDMI] -- HDMI Channel 0 Context --
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[System Management]
[HDMI]     - SSM Task ID : 13
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : EVENT FLAG
[HDMI]     - SSM State : WaitResolution
[HDMI]     - SSM Mutex Information : ID[2] LockTID[0] WaitTID[0]
[HDMI]     - SSM Event Flag Info : ID[2] WaitTID[13] FlagPattern[0]
[HDMI]     - SSM Mode : HDMI
[HDMI] ------------------------------------------------------------------------------------
[HDMI]     - Authentication Status : NotStart
[HDMI]     - Repeater : Sink
[HDMI]     - KSVs     : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[Interrupt]
[HDMI]     - External Interrupt Number of Mullion : 7
[HDMI]     - Interrupt Mask Pattern in SiI : [0x0000E0]
[HDMI]     - Interrupt Register Size : 3
[HDMI]     - Interrupt Task ID : 12
[HDMI]         * Task Status : WAITING
[HDMI]         * Wait Cause  : SLEEPING
[HDMI]     - Semapho Information : ID[38] WaitingTID[0] Count[1]
[HDMI]     - Plug Status : PowerOn
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[SiIType]
[HDMI]     - Chip Type : 9132
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[EDID]
[HDMI]     - EDID Mutex ID : 3
[HDMI]     - EDID Mutex Information : ID[3] LockTID[0] WaitTID[0]
[HDMI]     - EDID Block Size : 2
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[I2C Bus]
[HDMI]     - Device Address 0x72(0) 0x7A(1)
[HDMI]     - Semapho Information : ID[36] WaitingTID[0] Count[1]
[HDMI] ------------------------------------------------------------------------------------
[HDMI]  +-[AV Setting]
[HDMI]     - Audio Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]     - Video Setting State : Unset
[HDMI]                     Mute  ; Mute
[HDMI]                  Setting  : 11 80 30 01 88 20 00 33 98 37 00 14
[HDMI]                           : 82 02 0D 46 00 18 00 11 00 00 00 00 00 00 00 00 00 00 00
[HDMI]

hdmi redid 0
[HDMI] - Ch.0 EDID Block 0 -
[HDMI] Addr :  0  1  2  3| 4  5  6  7| 8  9  A  B| C  D  E  F
[HDMI] -----:------------+-----------+-----------+-----------
[HDMI]  00  : 00 ff ff ff|ff ff ff 00|1e 6d bc 57|01 01 01 01
[HDMI]  10  : 01 14 01 03|80 33 1d 78|0a c6 65 a0|59 58 9d 27
[HDMI]  20  : 0e 50 54 a5|6f 00 81 80|81 8f 71 40|b3 00 81 4f
[HDMI]  30  : 71 4f 01 01|01 01 02 3a|80 18 71 38|2d 40 58 2c
[HDMI]  40  : 45 00 fd 1e|11 00 00 1a|21 39 90 30|62 1a 27 40
[HDMI]  50  : 68 b0 36 00|56 50 21 00|00 1c 00 00|00 fd 00 38
[HDMI]  60  : 4b 1e 53 11|00 0a 20 20|20 20 20 20|00 00 00 fc
[HDMI]  70  : 00 4d 32 33|38 30 44 0a|20 20 20 20|20 20 01 d2

[HDMI] - Ch.0 EDID Block 1 -
[HDMI] Addr :  0  1  2  3| 4  5  6  7| 8  9  A  B| C  D  E  F
[HDMI] -----:------------+-----------+-----------+-----------
[HDMI]  00  : 02 03 21 f1|4e 84 05 03|02 20 22 10|11 13 12 14
[HDMI]  10  : 1f 07 16 26|15 07 50 09|07 07 66 03|0c 00 10 00
[HDMI]  20  : 80 01 1d 00|72 51 d0 1e|20 38 88 15|00 56 50 21
[HDMI]  30  : 00 00 1e 01|1d 80 18 71|1c 16 20 58|2c 25 00 56
[HDMI]  40  : 50 21 00 00|9e 01 1d 80|d0 72 1c 16|20 10 2c 25
[HDMI]  50  : 80 c4 8e 21|00 00 9e 02|3a 80 d0 72|38 2d 40 10
[HDMI]  60  : 2c 45 20 06|44 21 00 00|1e 00 3a 80|18 71 38 2d
[HDMI]  70  : 40 58 2c 45|00 56 50 21|00 00 1e 00|00 00 00 d0

Then I connected to the southbridge and retrieved the logs with the hard drive connected.

Code:
Boot Loader SE Version 3.5.0 (Build ID: 4002,46233, Build Date: 2010-09-13_16:37:51)
SDK Version: 350.000
Copyright(C) 2010 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:PX1.1
Device: PATAC0:Cable Not Connect
Cell OS SDK3.5.0 000 (release build: r46233 2010_09_13_153000)
Copyright 2010 Sony Computer Entertainment Inc.
revision: 45553
date:     Mon Sep 13 16:40:25 JST 2010
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3704KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 3.5.0
lv2(2): Copyright 2010 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 46233
lv2(2): build date: 2010/09/13 16:48:04
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b08 500/650 vpe:ff shd:3f  [AP0005368:1:1:e:12:b:2:f:1][16:3:1:1:1:3:1][0:0:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2): creating the initial system process : OK
lv2(2): entering stand-alone mode.
lv2(2): system software: PS3 console mode (game memsize=200MB)
lv2(2): creating the system software process : OK
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.

I connected the Blu-ray drive and tried to get to safe mode, but no display.

Code:
Boot Loader SE Version 3.5.0 (Build ID: 4002,46233, Build Date: 2010-09-13_16:37:51)
SDK Version: 350.000
Copyright(C) 2010 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:PX1.1
Cell OS SDK3.5.0 000 (release build: r46233 2010_09_13_153000)
Copyright 2010 Sony Computer Entertainment Inc.
revision: 45553
date:     Mon Sep 13 16:40:25 JST 2010
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3704KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 3.5.0
lv2(2): Copyright 2010 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 46233
lv2(2): build date: 2010/09/13 16:48:04
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b08 500/650 vpe:ff shd:3f  [AP0005368:1:1:e:12:b:2:f:1][16:3:1:1:1:3:1][0:0:0]

lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2):
lv2(2): ###
lv2(2): ### Safe mode
lv2(2): ###
lv2(2):
lv2(2): creating the recover process (for safe mode) : OK

I attached the complete log, including PME and SS logs.
I have also uploaded it here: https://pastebin.com/js1jeUZB
At the end there is update_manager::read_eprom(0x48c42), so maybe it's stuck reading that address?
I'm undecided what to do…
Maybe the console is stuck on a broken update due to the power supply failing during an update (at the end of the southbridge log it seems it is loading an update), or there is a problem with the RSX.
Should I dump the NAND and validate it?
 

Attachments

I've had these same glod symptoms on multiple systems, considering the amount of improper shutdowns it's safe to say this system ran way longer than it says it did. It is most likely a bad gpu in the case of a 90nm gpu.
 
It looks like you've done a great job narrowing this down to a software or firmware issue rather than a hardware failure. Based on your logs, here is the assessment and some targeted questions:

Hardware Status: The hardware appears healthy, as LV2 initializes the RSX and the HDMI controller successfully reads the EDID data from your display.

Update Loop: The system seems stuck in a standalone or update-related state, specifically ending at the EPROM flag check 0x48c42.

Integrity Checks: Core OS components like lv0 and lv1 have already passed their integrity checks, so the foundational boot files are likely fine.

Corruption Risk: The becount statistics, showing 726 bringups versus only 156 shutdowns, strongly support your theory that the faulty PSU caused frequent improper power-offs, likely leading to Flash or filesystem corruption.

Questions:
Have you tried a manual video output reset by holding the power button until the second beep?
Have you attempted to force a system update via USB while the console is in Recovery Mode?
Have you tested the console's behavior with the HDD removed or verified the drive's health on a PC?
If the above steps fail, your plan to dump the NAND to validate the ROS0 and ROS1 sections for corruption, seams good.
 
I've had these same glod symptoms on multiple systems, considering the amount of improper shutdowns it's safe to say this system ran way longer than it says it did. It is most likely a bad gpu in the case of a 90nm gpu.
Do you have some logs of the southbridge of them with also PME and SS enabled?
I think what is missing on this forum is some kind of examples of such logs for GLOD ps3.
And also I couldn't find example logs for working one, only syscon

It looks like you've done a great job narrowing this down to a software or firmware issue rather than a hardware failure. Based on your logs, here is the assessment and some targeted questions:

Hardware Status: The hardware appears healthy, as LV2 initializes the RSX and the HDMI controller successfully reads the EDID data from your display.

Update Loop: The system seems stuck in a standalone or update-related state, specifically ending at the EPROM flag check 0x48c42.

Integrity Checks: Core OS components like lv0 and lv1 have already passed their integrity checks, so the foundational boot files are likely fine.

Corruption Risk: The becount statistics, showing 726 bringups versus only 156 shutdowns, strongly support your theory that the faulty PSU caused frequent improper power-offs, likely leading to Flash or filesystem corruption.

Questions:
Have you tried a manual video output reset by holding the power button until the second beep?
Have you attempted to force a system update via USB while the console is in Recovery Mode?
Have you tested the console's behavior with the HDD removed or verified the drive's health on a PC?
If the above steps fail, your plan to dump the NAND to validate the ROS0 and ROS1 sections for corruption, seams good.

I'll report back when the E3 flasher arrives
- I tried the video reset
- the controller doesn't sync, there is another way to force it?
- the behavior seem the same, it doesn't even try to read it (I don't hear it being read and the red light doesn't blink) and the SMART values are ok.

I've had these same glod symptoms on multiple systems, considering the amount of improper shutdowns it's safe to say this system ran way longer than it says it did. It is most likely a bad gpu in the case of a 90nm gpu.
Before trying my luck with the e3 flasher i tried to press around the space between the cpu and the southbridge and now it works until i let go, then some artifacts.
It's clearly a BGA issue but what component of the two?
3.jpeg

2.jpeg
1.jpeg
 
Last edited by a moderator:

Similar threads

Back
Top