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

doomslayer2099 · Jan 9, 2025

Hi everyone, could anyone help me identify which part of the PS3 needs replacement?

Before pressing the power button, the power indicator shows a solid red light.

After pressing the power button, the light changes from red to green with one beep, followed by a yellow light.

It then switches to a blinking red light with three beeps.

Below is the error code I collected from the SYSCON.

Thank you!

Code:

>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0003001 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 2376E312
# A0801002 234DF223
# A0801002 234DF21C
# A0801002 234DF213
# A0093004 234B4AF5
# A0801002 1FC0602B
# A0801002 1FC0601F
# A0801002 1EADE6D4
# A0801002 1EADE6C5

Press Ctrl+C to exit
>$ help
00000000
# B_AUTH "AUTH1"
# B_AUTH "AUTH2"
# ANY    "AUTHVER"
# A_AUTH "BOOT"
# A_AUTH "BOOTENABLE"
# A_AUTH "CID"
# A_AUTH "CSAREA"
# A_AUTH "DISABLEALLERASE"
# A_AUTH "ECID"
# A_AUTH "EEP"
# ANY    "ERRLOG"
# A_AUTH "HALT"
# A_AUTH "KSV"
# INT    "LS"
# A_AUTH "PDAREA"
# A_AUTH "R16"
# A_AUTH "R32"
# A_AUTH "R8"
# A_AUTH "REV"
# ANY    "SETCMDLONG"
# A_AUTH "SPU"
# ANY    "VER"
# A_AUTH "VID"
# A_AUTH "W16"
# A_AUTH "W32"
# A_AUTH "W8"
# A_AUTH "bestat"
# A_AUTH "bringup"
# INT    "buzz"
# INT    "buzzduty"
# INT    "cleareep"
# INT    "commt"
# A_AUTH "csum"
# A_AUTH "devpm"
# A_AUTH "duty"
# A_AUTH "eepcsum"
# A_AUTH "ejectsw"
# ANY    "errlog"
# A_AUTH "extend"
# A_AUTH "fanconmode"
# A_AUTH "fanconpolicy"
# A_AUTH "fanservo"
# A_AUTH "fanservostat"
# A_AUTH "fantbl"
# INT    "getrtc"
# A_AUTH "hdmi"
# A_AUTH "help"
# INT    "hversion"
# A_AUTH "hyst"
# INT    "meminfo"
# A_AUTH "nonfatalerror"
# A_AUTH "patchinfo"
# INT    "poll"
# A_AUTH "portscan"
# INT    "portset"
# A_AUTH "powerstate"
# A_AUTH "powersw"
# A_AUTH "powupcause"
# A_AUTH "r"
# A_AUTH "r16"
# A_AUTH "r32"
# A_AUTH "r64"
# A_AUTH "r64d"
# INT    "rbe"
# INT    "recv"
# ANY    "revision"
# INT    "send"
# ANY    "setcmdlong"
# A_AUTH "shutdown"
# A_AUTH "syspowdown"
# INT    "task"
# A_AUTH "thrm"
# A_AUTH "tmp"
# A_AUTH "trp"
# A_AUTH "tsensor"
# A_AUTH "tshutdown"
# A_AUTH "tzone"
# ANY    "version"
# A_AUTH "w"
# A_AUTH "w16"
# A_AUTH "w32"
# A_AUTH "w64"
# A_AUTH "wbe"

Press Ctrl+C to exit
>$ bringup
FFFFA605

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [PowSeq] Error:A101
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

LSL · Jan 9, 2025

doomslayer2099 said:
Hi everyone, could anyone help me identify which part of the PS3 needs replacement?

>$ errlog
00000000
# CODE CLOCK
# A0003001 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 FFFFFFFF
# A0093004 2376E312
# A0801002 234DF223
# A0801002 234DF21C
# A0801002 234DF213
# A0093004 234B4AF5
# A0801002 1FC0602B
# A0801002 1FC0601F
# A0801002 1EADE6D4
# A0801002 1EADE6C5

https://www.psdevwiki.com/ps3/Syscon_Error_Codes

Lichi · Jan 9, 2025

Hi people! I was able to get the codes. Could you help me with this?

PS3 super slim cech 4xxx turns on for about 30 seconds, then something like an ambulance/siren/alarm sound appears, then shuts off.

For what I have seen through the ps3 dev wiki, seems to be either a power supply problem or a problem with the line through which the power supplies current goes.

I tested the same psu with which I'm getting this error with another motherboard (that is same model, PQX-001), and I can use ps3 completely fine. Is it safe to assume then that the problem is in the motherboard?

If it its, then is it some kindo of beautiful tutorial on yt explaining how to measure the componentes of the said line?

Thanks!

Code:

D:\PS3\Syscon\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM7 SW
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Lichi · Jan 9, 2025

I did the test after changing power cable (the one that goes to the wall) and now I get A0801200, a problem related with cpu overheating... I'm guessing that this happened because... I don't know. I of course don't have the fan connected, so could be because of that. That problem should be solved when I change thermal paste and connect the fan. But why didn't I get the error in the first try?

When I changed the power cable (the one that goes into the wall), I kind of pressed the psu against the motherboard (just to ensure) and I think I heard some kind of click...

Could it be, maybe, that the problem was that psu was incorrectly connected? Seems madness to me, but it could be that that was the problem, and now it gives me the heat error because the system is trying to start normally but there is no fun connected. Could it be that?

NightLess · Jan 9, 2025

Lichi said:
I did the test after changing power cable (the one that goes to the wall) and now I get A0801200, a problem related with cpu overheating... I'm guessing that this happened because... I don't know. I of course don't have the fan connected, so could be because of that. That problem should be solved when I change thermal paste and connect the fan. But why didn't I get the error in the first try?

When I changed the power cable (the one that goes into the wall), I kind of pressed the psu against the motherboard (just to ensure) and I think I heard some kind of click...

Could it be, maybe, that the problem was that psu was incorrectly connected? Seems madness to me, but it could be that that was the problem, and now it gives me the heat error because the system is trying to start normally but there is no fun connected. Could it be that?

Plug the fan back in, make sure your cells don't overheat, they heat up very quickly, if you see an overheat message this means the system has 12v power and booted successfully.

Lichi · Jan 9, 2025

Latest errors:

Code:

>$ errlog
00000000
# CODE     CLOCK
# A0805FFF 0B51B85B
# A0805FFF 0B51B7B5
# A0805FFF 0B51B317
# A0801200 0B51B058
# A0801200 0B51AF88
# A0801200 0B51AA4B
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

NightLess · Jan 9, 2025

Lichi said:

Latest errors:

Code:

>$ errlog
00000000
# CODE     CLOCK
# A0805FFF 0B51B85B
# A0805FFF 0B51B7B5
# A0805FFF 0B51B317
# A0801200 0B51B058
# A0801200 0B51AF88
# A0801200 0B51AA4B
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

This looks like a firmware issue.

Lichi · Jan 9, 2025

NightLess said:
This looks like a firmware issue.

That is so weird. A problem of the firmware of the motherboard? Do you know of any method to sort that out?

NightLess · Jan 9, 2025

Lichi said:
That is so weird. A problem of the firmware of the motherboard? Do you know of any method to sort that out?

Experienced people have answered this question. The cause 5FFF may be dead cell or rsx, but you should first check the firmware. They may be damaged or when you appling patch. You need a hardware flasher to restore it.

RIP-Felix · Jan 9, 2025

5FFF is often caused by a BGA defect or dead CELL in sherwood models. The CPU overheat errors (1200) leading up to the 5FFF implicates the cell. It may have needed delided and if someone tried and failed they might have scratched traces causing that. Or the added pressure under the cell with a thermal pad causing the die to crack or BGA to break.

I'm not certain why people thing firmware issues with this code. I did read a few reports of it on ps3devwiki where they said that error was displayed in diag mode after a brick, but most reports I've heard with that has been the CPU.

Zx6r · Jan 9, 2025

Ps3 backward compatible CECH-C03

544day total runtime

Could error 2102 be rsx or voltage? It was glod then became ylod when I applied heat for 20 mintues

errlog
ofst[ 28]:err_code:0xffffffff, clock:0x18041a27 2012/10/07 10:47:03
ofst[ 32]:err_code:0xa0801001, clock:0x18041ff0 2012/10/07 11:11:44
ofst[ 36]:err_code:0xa0801001, clock:0x180420e5 2012/10/07 11:15:49
ofst[ 40]:err_code:0xa0801001, clock:0x18042706 2012/10/07 11:41:58
ofst[ 44]:err_code:0xa0801004, clock:0x183f7317 2012/11/21 11:10:15
ofst[ 48]:err_code:0xa0801004, clock:0x18941230 2013/01/24 15:39:28
ofst[ 52]:err_code:0xa0801004, clock:0x19bf3c1a 2013/09/08 13:46:02
ofst[ 56]:err_code:0xa0801004, clock:0x2084037a 2017/04/14 22:02:34
ofst[ 60]:err_code:0xa0801001, clock:0x0b4886b7 2005/12/31 00:00:55
ofst[ 64]:err_code:0xa0801001, clock:0x0b4897ad 2005/12/31 01:13:17
ofst[ 68]:err_code:0xa0801001, clock:0xffffffff
ofst[ 72]:err_code:0xa0801001, clock:0x0b488697 2005/12/31 00:00:23
ofst[ 76]:err_code:0xa0801001, clock:0x0b48877d 2005/12/31 00:04:13
ofst[ 80]:err_code:0xa0801001, clock:0x0b4887cc 2005/12/31 00:05:32
ofst[ 84]:err_code:0xa0801001, clock:0x0b488808 2005/12/31 00:06:32
ofst[ 88]:err_code:0xa0801001, clock:0x0b48887c 2005/12/31 00:08:28
ofst[ 92]:err_code:0xa0232102, clock:0x0b650b5b 2006/01/21 15:10:19
ofst[ 96]:err_code:0xa0232102, clock:0x0b650b68 2006/01/21 15:10:32
ofst[100]:err_code:0xa0232102, clock:0x0b667a66 2006/01/22 17:16:22
ofst[104]:err_code:0xa0232102, clock:0x0b667a6e 2006/01/22 17:16:30
ofst[108]:err_code:0xa0232102, clock:0x0b667a76 2006/01/22 17:16:38
ofst[112]:err_code:0xa0232102, clock:0x0b667aab 2006/01/22 17:17:31
ofst[116]:err_code:0xa0232102, clock:0x0b667abc 2006/01/22 17:17:48
ofst[120]:err_code:0xa0232102, clock:0x0b667ac0 2006/01/22 17:17:52
ofst[124]:err_code:0xa0232102, clock:0x0b667aca 2006/01/22 17:18:02
ofst[ 0]:err_code:0xa0232102, clock:0x0b667ace 2006/01/22 17:18:06
ofst[ 4]:err_code:0xa0232102, clock:0x0b667ad3 2006/01/22 17:18:11
ofst[ 8]:err_code:0xa0232102, clock:0x0b66d634 2006/01/22 23:48:04
ofst[ 12]:err_code:0xa0232102, clock:0x0b66d639 2006/01/22 23:48:09
ofst[ 16]:err_code:0xa0232102, clock:0x0b96a0f0 2006/02/28 05:49:36
ofst[ 20]:err_code:0xa0232102, clock:0x0b96a0fa 2006/02/28 05:49:46
o

NightLess · Jan 9, 2025

RIP-Felix said:
5FFF is often caused by a BGA defect or dead CELL in sherwood models. The CPU overheat errors (1200) leading up to the 5FFF implicates the cell. It may have needed delided and if someone tried and failed they might have scratched traces causing that. Or the added pressure under the cell with a thermal pad causing the die to crack or BGA to break.

I'm not certain why people thing firmware issues with this code. I did read a few reports of it on ps3devwiki where they said that error was displayed in diag mode after a brick, but most reports I've heard with that has been the CPU.

victor has answered this question before. He said that soft bricks can be checked by tristate test, but actually I don't know because I also told Lichi that it might be cell death.Glad you answered Felix

Lichi · Jan 9, 2025

NightLess said:
Experienced people have answered this question. The cause 5FFF may be dead cell or rsx, but you should first check the firmware. They may be damaged or when you appling patch. You need a hardware flasher to restore it.

RIP-Felix said:
5FFF is often caused by a BGA defect or dead CELL in sherwood models. The CPU overheat errors (1200) leading up to the 5FFF implicates the cell. It may have needed delided and if someone tried and failed they might have scratched traces causing that. Or the added pressure under the cell with a thermal pad causing the die to crack or BGA to break.

I'm not certain why people thing firmware issues with this code. I did read a few reports of it on ps3devwiki where they said that error was displayed in diag mode after a brick, but most reports I've heard with that has been the CPU.

I see. A BGA defect would happen when the little balls under the chips are not correctly soldered to the motherboard, right? Maybe the heat error code was an intermediate state between them little balls kind of making ok contact and finally not making contact at all.

But anyways, I'll have to give up on this. Even if I could do a reballing (assuming that that would fix the problem, which could not be the case), there would be still an error in the motherboard 12v power line. There are hundreds of components on that line. I'm not even sure what that trace looks like or how far it goes, and I'm pretty sure there isn't a tutorial out there detailing every component of that line and the correct voltage and ohms it should be giving/receiving. It's sad because this was my ps3. But it is what it is.

Thanks a lot for the help!

Tuner357 · Jan 10, 2025

Hey!

I have this 4001c super slim that was given to me broken. When i first powered it on, i got video output, but it was all garbled up. Any time after that, the console beeps, green light comes on for like 5-10 seconds, and then turns off. Ive never had it output any sort of video since.

I poked around the board to see if any fuses were blown, but they were all fine from what i could tell. Also visually went over the board, and didn't see anything out of the ordinary besides it being fairly dirty.

PS3 dev wiki says the 3034 is "rsx core power failure". Im wondering what steps i should take next, should i poke around the rsx and see if i can find any shorted caps? Or is this most likely a cooked rsx?

Code:

>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF
# A0404421 FFFFFFFF
# A0403034 FFFFFFFF

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9003
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

nickxab · Jan 12, 2025

Sometimes 3034 is a cracked rsx pin (bga solder ball)

Tuner357 · Jan 12, 2025

nickxab said:
Sometimes 3034 is a cracked rsx pin (bga solder ball)

That was kinda my guess since it was artificing real bad when it turned on the first time. but maybe ill poke around the board a bit more and test some stuff blindly before i write it off as needing a reball. Another reason for me to get a bga machine lol

nickxab · Jan 13, 2025

I don't know if nec tokins can cause this error as well

Tuner357 · Jan 13, 2025

nickxab said:
I don't know if nec tokins can cause this error as well

so i read that it could, but this is a super slim model, with no tokens, they have tantalum caps

LSL · Jan 13, 2025

nickxab said:
I don't know if nec tokins can cause this error as well

NECs = 1001, 1002, 3003, 3004

RGBeter · Jan 15, 2025

Hey everyone, ran into a GLOD system earlier today, Syscon codes are pretty much useless but they're here anyway, I also checked diagnostic output from the SB, and from what I see the system just, boots, no complaints, but I have no video output from either AV or HDMI. I inserted both logs, if anybody with advanced knowledge on the PS3 can help me out that would be great. If it is just a bad RSX, I recently got the equipment together, and learned how to swap GPUs on xbox 360, getting a JTAGable falcon running again, so an RSX swap is no issue to me, I just need to know it needs to be done.

Code:

Boot Loader SE Version 4.4.0 (Build ID: 5012,49722, Build Date: 2013-03-14_23:53:31)
SDK Version: 440.000
Copyright(C) 2013 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.2, SB:PX1.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.4.0 000 (release build: r49722 2013_03_14_223000)
Copyright 2013 Sony Computer Entertainment Inc.
revision: 49423
date:     Thu Mar 14 23:56:50 JST 2013
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3524KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.4.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 49722
lv2(2): build date: 2013/03/15 00:04:17
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0202
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:5f  [4K0349001:1:3:10:7:7:4:f:1][39:2: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): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : OK
lv2(2): creating the initial system process : OK

Code:

ofst[  0]:err_code:0xa0801701, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  4]:err_code:0xa0801601, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  8]:err_code:0xa0802203, clock:0x1548e3d3  2011/04/26 02:00:51
ofst[ 12]:err_code:0xa0801004, clock:0x1779e4c1  2012/06/24 14:46:25

Bringup : 2773 times
Shutdown: 2329 times
Power-on: 216day 21hour 13min 35sec

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

Member

Member

Member

Member

Member

Member

Member

Member

Member

Senior Member

Member

Member

Member

Forum Noob

Glitta

Forum Noob

Glitta

Forum Noob

Member

Member

Similar threads