PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

5.8 Ohms between GND and the cell side of the tantalums is a dead Cell right?

PS3 Symptoms:
  1. Has the red standby LED
  2. Turns on with a green LED and no display
  3. After 41 seconds green LED goes out
  4. 5 seconds later PS3 fully shuts down.
  5. Pressing the on button the red LED re-appears.
  6. Repeats from here.
Syscon error reports:

===================================
ERR 00: 00000000 A0805FFF FFFFFFFF
ERR 01: 00000000 A0805FFF FFFFFFFF
ERR 02: 00000000 A0805FFF FFFFFFFF
ERR 03: 00000000 A0805FFF FFFFFFFF
ERR 04: 00000000 A0805FFF FFFFFFFF
ERR 05: 00000000 A0805FFF FFFFFFFF
ERR 06: 00000000 A0805FFF FFFFFFFF
ERR 07: 00000000 A0805FFF FFFFFFFF
ERR 08: 00000000 A0805FFF FFFFFFFF
ERR 09: 00000000 A0805FFF FFFFFFFF
ERR 10: 00000000 A0805FFF 1FFD0776
ERR 11: 00000000 A0805FFF 1FFD05D2
ERR 12: 00000000 A0805FFF 1FF755A8
ERR 13: 00000000 A0805FFF 1FF75499
ERR 14: 00000000 FFFFFFFF FFFFFFFF
ERR 15: 00000000 FFFFFFFF FFFFFFFF
ERR 16: 00000000 FFFFFFFF FFFFFFFF
ERR 17: 00000000 FFFFFFFF FFFFFFFF
ERR 18: 00000000 FFFFFFFF FFFFFFFF
ERR 19: 00000000 FFFFFFFF FFFFFFFF
===================================
 
Last edited:
finalman said:
5.8 Ohms between GND and the cell side of the tantalums is a dead Cell right?

PS3 Symptoms:
  1. Has the red standby LED
  2. Turns on with a green LED and no display
  3. After 41 seconds green LED goes out
  4. 5 seconds later PS3 fully shuts down.
  5. Pressing the on button the red LED re-appears.
  6. Repeats from here.
Syscon error reports:

===================================
ERR 00: 00000000 A0805FFF FFFFFFFF
ERR 01: 00000000 A0805FFF FFFFFFFF
ERR 02: 00000000 A0805FFF FFFFFFFF
ERR 03: 00000000 A0805FFF FFFFFFFF
ERR 04: 00000000 A0805FFF FFFFFFFF
ERR 05: 00000000 A0805FFF FFFFFFFF
ERR 06: 00000000 A0805FFF FFFFFFFF
ERR 07: 00000000 A0805FFF FFFFFFFF
ERR 08: 00000000 A0805FFF FFFFFFFF
ERR 09: 00000000 A0805FFF FFFFFFFF
ERR 10: 00000000 A0805FFF 1FFD0776
ERR 11: 00000000 A0805FFF 1FFD05D2
ERR 12: 00000000 A0805FFF 1FF755A8
ERR 13: 00000000 A0805FFF 1FF75499
ERR 14: 00000000 FFFFFFFF FFFFFFFF
ERR 15: 00000000 FFFFFFFF FFFFFFFF
ERR 16: 00000000 FFFFFFFF FFFFFFFF
ERR 17: 00000000 FFFFFFFF FFFFFFFF
ERR 18: 00000000 FFFFFFFF FFFFFFFF
ERR 19: 00000000 FFFFFFFF FFFFFFFF
===================================
Click to expand...
Kte001? Is a dead cpu. I got it in many slims.
Compared with many working units around 2~4 maximum resistance for cpu. If you reball will get same results, I didn't fixed any of 5fff situations
 
vyktormvmpay25 said:
eepcsum?
Click to expand...

Thanks for the response, eepcsum is as it should be far as I am aware

eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff

and if I run bringup this is what it usually outputs sometimes takes a little longer for it to error out and sometimes it's instant.

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[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
>$ shutdown
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[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 THERM] NOTIFY_MODE CMD
[SERV THERM] Thermal Error Detected!
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SERV NVS] *** sending error ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
 
Ormas said:
I finally did the syscon thing and these are the error codes I got.
folderview

@RIP-Felix you think those 3034 error codes are showing up because of the gamecube wires I'm using for the capacitors?
Click to expand...
Currently you have a 00 3001. 00 means the error is happening at the first step of the power sequence. 3001 means a PSU failure. Try a working power supply.

Before that there were 3034 errors in the log. That's the one requiring a reball. It doesn't guarantee a fix, but it's the only way forward. The question is, was that an old error from when the console was previously reflowed/reballed? Or is it still there, being hidden by the dead PSU? IDK because there are no timestamps.
 
Rozus said:
Hello, hopefully someone might be able to help me with this. I have a C03 COK-002 PS3 with an overheating issue, so I assumed it was going to be a delid and that will fix it but it hasn't. The system will power up and go to the menu for around 10 seconds then the overheat message comes up and shortly after it powers off.

I have ensured the heatsinks/IHS are in the correct place and are making good contact with the chips so I am a bit of a loss what it might be. I hooked the syscon up to get the error logs and this is what I got from it.

Auth successful
> ERRLOG GET 00
00000000 A0801200 0B49D816
> ERRLOG GET 01
00000000 A0902120 FFFFFFFF
> ERRLOG GET 02
00000000 A0801200 FFFFFFFF
> ERRLOG GET 03
00000000 A0902203 0B49D95F
> ERRLOG GET 04
00000000 A0801200 0B49D95F
> ERRLOG GET 05
00000000 A0902120 0B49D95A
> ERRLOG GET 06
00000000 A0902203 0B49D95A
> ERRLOG GET 07
00000000 A0902203 0B49D95A
> ERRLOG GET 08
00000000 A0902203 0B49D95A
> ERRLOG GET 09
00000000 A0801200 0B49D95A
> ERRLOG GET 10
00000000 A0902203 0B49D82A
Click to expand...

08 1200 is a CPU overheat. It's occurring in the on state. The 09 2203 is a south bridge error occurring in the shutdown state, which could be nothing more than an error generated in panic. Panic is a forced shutdown to prevent damage, associated with 3-beeps. Since it was starting to shutdown gracefully and then panicked, it might generate a SB error...IDK.

You said you delided, but didn't specifically say you delided both the RSX and CELL BE. It sounds to me like the CPU's TIC is old and needs replaced. It is unheard of (AFAIK) for a CPU that has been delided to so quickly overheat. If it is there's definitely something bigger going worng here. I would start by checking voltage (VDDC).
 
RIP-Felix said:
08 1200 is a CPU overheat. It's occurring in the on state. The 09 2203 is a south bridge error occurring in the shutdown state, which could be nothing more than an error generated in panic. Panic is a forced shutdown to prevent damage, associated with 3-beeps. Since it was starting to shutdown gracefully and then panicked, it might generate a SB error...IDK.

You said you delided, but didn't specifically say you delided both the RSX and CELL BE. It sounds to me like the CPU's TIC is old and needs replaced. It is unheard of (AFAIK) for a CPU that has been delided to so quickly overheat. If it is there's definitely something bigger going worng here. I would start by checking voltage (VDDC).
Click to expand...

Sorry for not being 100% clear, both the CELL and RSX are delidded I do it fairly regularly so I cannot see that being the cause as it was doing the exact same thing before I did the delid. This morning I did strip it down again and had a look at the IHS plates to make sure they are within the markings I marked on the heatsink and they are in alignment so I am suspecting something much bigger is at play as you said.

I am quite new to this in that using the syscon for error codes and deeper fault finding on the PS3, you said to check the voltage for the CELL I assume, where would the best place to start for this.
 
Rozus said:
Thanks for the response, eepcsum is as it should be far as I am aware

eepcsum
Addr:0x000032fe should be 0x528c
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0038
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff

and if I run bringup this is what it usually outputs sometimes takes a little longer for it to error out and sometimes it's instant.

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[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
>$ shutdown
[SERV THERM] Thermal Error Cleared!
[SERV THERM] *** NO COMMTAG SPECIFIED! ***
[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 THERM] NOTIFY_MODE CMD
[SERV THERM] Thermal Error Detected!
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SERV NVS] *** sending error ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Click to expand...
From bringup it looks like thermal errors. Is something wrong from cpu temperature error or that ic that suppose to read temperature is failing. If you have any spares boards to replace that ic will be easier. Not sure about your delid and new thermal paste making contact back with ihs. That SB debugging is more helpful.
So first he said chips and I've assumed both.
 
vyktormvmpay25 said:
From bringup it looks like thermal errors. Is something wrong from cpu temperature error or that ic that suppose to read temperature is failing. If you have any spares boards to replace that ic will be easier. Not sure about your delid and new thermal paste making contact back with ihs. That SB debugging is more helpful.
So first he said chips and I've assumed both.
Click to expand...

Thank you again for the response, just had a quick look through the service manual and the IC I am assume you are referring to is IC 1101 which according to the PS dev wiki is to do with the CELL thermal monitoring system. I have a few GLOD boards laying about so I will swap this and report back with the results.
 
He said, " I assumed it was going to be a delid and that will fix it but it hasn't." Which delid? Both? Most people are deterred by the silicone gluing the CPU IHS down, so I didn't want to assume he did this too, until he specifically confirms it. I mean, the SYSCON is saying BE overheat. So that's the first place to start.
 
Success! replaced IC1101 from another board and it now works correctly, I have not done any extensive testing yet but if I do run into any further issues I will be sure to drop a message on here. Thank you again for the help it is greatly appreciated!
 
How many seconds did unit booted before? I'm interested because SB debugging had enough time to get some stages there.
He is new user and we have to wait approval for his post (seems he fixed by ic sensor) .
 
vyktormvmpay25 said:
How many seconds did unit booted before? I'm interested because SB debugging had enough time to get some stages there.
He is new user and we have to wait approval for his post (seems he fixed by ic sensor) .
Click to expand...

So I've let it run GT6 for a couple of hours just to make sure it's working as intended and good news no wild temperature spikes and power offs after I replaced the IC.

To answer your question about timing it varied quite a bit. Most of the time would be around 5-10 seconds and if I tried to boot it straight after it reported itself as overheating it would be about 2 seconds with a very sudden fan ramp up before the double beep power off. Then there were times it would allow me to get to the XMB for about a minute then it would ramp up the fan and power off but this seemed to happen less and less often the more I tried it.
 

Attachments

  • _20210608_205031.JPG
    _20210608_205031.JPG
    2.1 MB · Views: 1,008
The way I've understood you did all good is that SB won't get debugging if CPU and Rsx aren't working properly so it was about to fail earlier. Sb won't boot if flash is corrupted flash as glod (just working now on dyn001 with a corruption and tested, before me seller told me he killed about 4 boards dyn001 with E3) .They are at my place.
So low temperatures, it must be a less used unit.
What thermal paste have you used under ihs on top of die ic's and on top of ihs?
I'm really surprised for this unit temperatures.
SB debugging is kind of situation with analog multimeter testing but really more advanced tool.
 
Last edited:
Another test if I recover board I will try halt to see what putty is getting, or for fun I will brik it and halt sb to gnd to understand where bootloader is starting.
 
vyktormvmpay25 said:
The way I've understood you did all good is that SB won't get debugging if CPU and Rsx aren't working properly so it was about to fail earlier. Sb won't boot if flash is corrupted flash as glod (just working now on dyn001 with a corruption and tested, before me seller told me he killed about 4 boards dyn001 with E3) .They are at my place.
So low temperatures, it must be a less used unit.
What thermal paste have you used under ihs on top of die ic's and on top of ihs?
I'm really surprised for this unit temperatures.
SB debugging is kind of situation with analog multimeter testing but really more advanced tool.
Click to expand...

The thermal paste is really nothing special, it's called GD900 ( for both IHS and die ) from my own testing it is a fairly solid performer, maybe a little inconsistent with quality as some tubes will perform better than others but inline with most branded thermal pastes like MX-4 ( or better ) I would say on average. It's 30 grams for basically pennies so I cannot really fault it considering I am doing delids almost daily and continuously buying the more well known stuff gets expensive fast for maybe only a couple degrees better performance.

Total system uptime is about 45 days from what webman said and roughly 600 power ons and offs. Not the lowest I have seen but most certainly not the highest. I would say on average with these COK-002 or 001 boards regardless of total uptime I can get it to sit about 55-60C after a couple hours of GT6 (Fan at 35%) when the console is fully assembled.
 
So if this TIC is possible to keep those temps at 60 with 6w/mk then mx2/mx4 is it a little lie with 8w/mk.
Brand with his industry... Anyway thanks for this I will test it.
 
RIP-Felix said:
That's a GLOD. According to @botakompong they are usually due to RAM PWR failure. My guess is that a BGA defect struck one of the RSX VDDR solder balls. Possibly a CPU, but more likely the RSX. I had a very similar artifacting GLOD...
O1mI87K.jpg

...I was unfortunately unable to fix it. I attempted a reflow that was poorly done and resulted in a Black screen GLOD. Then I attempted my first reball which killed it.

What's interesting, though, mine did have a 40 3034 indicating it needed a reball. Your's doesn't! Yours does have a 1004 = AC/DC Power Fail and 2022 = DVE Error (IC2406). IC2406 controls the AV multiout and the fact that it's associated with a 1004 makes me suspicious of those electrolytic caps right next to it. If you have an ESR meter you can check them. I had a console that was banged around in shipping and one of them popped off. So it's possible that it was dropped and one of those electrolytic caps is not well attached or has gone bad.

Inspect the pins on the HDMI and Multi-Out ports for physical damage first. That'd be a stupid thing to overlook (I did it and chased gremlins for awhile before noticing).

EDIT: Questions:
  1. Does the fan run fast before glitching out?
  2. DId you delid the CPU? Seems pretty hot for just the XMB.
Click to expand...
i dont have a ESR meter, i did maintenance and fan runs ok, (not like jet engine), and only delid the rsx, (i dont have tool for delid CELL), before read your post, i did some testing, machine start only play sound and black screen then i did a little presure with my finger above RSX area and bring YLOD, then i check the lasterrlog now i have the 403034 error registered, i not have tested machine again but i will check againg some days if still have same error. thanks.
 
Rozus said:
...It's 30 grams for basically pennies so I cannot really fault it considering I am doing delids almost daily and continuously buying the more well known stuff gets expensive fast for maybe only a couple degrees better performance...
Click to expand...
Starting to make cost saving decisions like SONY huh?

A slippery slope, the path to the dark side is!
 
felixthecat1970 said:
i dont have a ESR meter, i did maintenance and fan runs ok, (not like jet engine), and only delid the rsx, (i dont have tool for delid CELL), before read your post, i did some testing, machine start only play sound and black screen then i did a little presure with my finger above RSX area and bring YLOD, then i check the lasterrlog now i have the 403034 error registered, i not have tested machine again but i will check againg some days if still have same error. thanks.
Click to expand...
Yeah it definitely responded to the pressure test. 3034 and pressure test + = reball. Sorry :(
 
You must log in or register to reply here.

Similar threads

Back
Top