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

@Pacorretaco, thanks, i keep in mind, look in reported lasterror before conclude the "nec reemplacement" also my friend buy other of this "second hand ps3" from gamestop with this "kind" of labels, i will check for maintenance next weeks and keep informed here, and beware if someone buy some machine in gamestop they almost no checked, have this "corrup hardrive" or similar labels and require maintenance (example this machine never was cleaned, paste was dry, one of main screw atached to plastic base was broken, i think strong pressure break the plastic atachment to base it have to broke the top screw for dissasemble the machine.
 
@Pacorretaco had this test, did not forget. So slims really have 0.95 v. Got another strange situation with one sur001 that after reball both I have kind of glod. Board came with 3034 4402. In this glod I can hear recovery beeps, claiming errors, nothing found in UART. Took rsx reball to another sur001 well known working, same results, glod no av/Hdmi signals, can go in recovery.
Rsx resistance 1.8 ohms, ram resistance 435 ohms out of board.
So yes it can happen at one point we should create test boards with socket for rsx at least. Not a permanent socket that will run games and everything but just to place ic and get image on screen, from there reball to its board should work for sure.
c8a99647801df931499b393baf7833f2.jpg
 
db260179 said:
The power on states stages give an indication on how bad a component has gone bad.

Ironically i have recieved a DIA-002 board with the following:

ofst[ 84]:err_code:0xa0801002, clock:0x26d6f228 2020/08/24 21:48:24
ofst[ 88]:err_code:0xa0801001, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0002120, clock:0xffffffff

$ lasterrlog
lasterrlog
Last Error Code:0xa0002120, Time:0xffffffff
[mullion]$

This is indicating i have two issues (possibly) - Faulty hdmi decoder or power components related? (power ic's, nec tokins...)

I believe you correct in saying that 1001 is a symptom and not a cause (related to the CELL power on process) 1002 is the RSX code.

I'm going to reorganise my error info and just label as possible issue for these codes.

I'll update on my findings and how i diagnosed the fault.
Click to expand...
I suspect that you only have one error (1002). 1001 can happen by just flipping the PWR switch off. It's common when testing the syscon codes, as most people don't like to wait for the console to startup and shutdown gracefully, they just flip the rocker off. That generates a 1001 fairly regularly.

2120 will happen when you have the HDMI cord inserted into a console that experiences a YLOD. It probably happened when you hooked the console up for a test, expecting to get a picture. Unplug the HDMI cord and it will not happen on the next 1002, unless there actually is something wrong with the HDMI encoder.

You don't have a 3034, so it worth adding some low ESR TaPol. I'd start by removing that 1002, since we know what's causing it. Afterwards, see if any of the other errors persist.
 
Can I ask a student question? If I clear errorlog and I don't have rtc battery attached will syscon save errors to his log events?
Tried something with putty while powered send from keyboard ctrl+B and unit stopped suddenly in off state without any led blinking just red standby. Didn't record any errlog. Done with cok002, will do more with my sur001 tomorrow. I don't have battery on socket, probably won't store any errors for this type of glod. Now I also have to make a simulation of ylod by removing one wire of modchip on cok002, it should store 3034 and second I cannot remember now.
 
felixthecat1970 said:
for document here: a friend bring me a ps3 cok-002 from gamestop with label. "corrupt harddisk" but.........
- 1 slow loading menu, no load
- 2 hd reemplaced, almost load but slow, controllers slow sync by blueetooh, after some minutes freeze, restart garbled pixelated image
- 3 dissamble (internal plastic part broken have to break screw) syscon mod and read errlog:
View attachment 33553
-a0901001=BE VRAM power Fail (possible nec reemplacement adviced 1post), so reemplaced:
>1 4x470uf BE Side test *random aftermentioned problems
>14x470uf RSX Side test *random aftermentioned problems
> change PSU for APS 226 (it have powerhungry ZSRXXXXX) test
> last upgrade firmware to 4.87 test
stable boot now but only after some seconds or 1minute:
View attachment 33552
Becount show 302days (pretty used); someone with experience in this error? rsx almost dead? reballing required?
also did maintenance, RSX delid, thermal paste, clean motherboard, check BE = 63-73 - RSX = 50 temps in syscon and syscon dont show any other error. thanks.
Click to expand...
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.
 
Last edited:
Putty seems to get debugging in real time automatically. Once auth successfully has been done with python script in cmd can close cmd, open putty, boot units (if you're unit is kind glod or normal functionality).
Can see power state on and further updates with temp in real time. Can not send commands on putty or at least I don't know.
Only tested to send ctrl+b keep pushing while boot and unit will instantly shut down at red standby (not as ylod red blinking) and got bunch of addresses didn't copy (I will on next test and see if someone can explain).
This method is used on boot in routers via UART debugging send ctrl +b will skip boot and let you read info of that router (was being tested with old like 2016 models and got bunch of informations there).
In our case is not easy as it won't accept commands in putty.
Did ps4 blod test as well only got this
secure loader build: Nov 30 2020 05:19:57 (r10323:release_branches/release_08.03
0) [711MHz]
AGESA: ThebePBDK W5C21
ERROR: DCT[6] is disabled
ERROR: DCT[7] is disabled
 
Last edited:
Has anyone successfully repaired A0403034 by reballing? I keep hearing people say reball, but nobody actually says that they've fixed a PS3 by reballing. I really don't want to reball if I don't have to, but I have like 3 BC models that have this error.

I'm so worried right now because I have gone through 10 PS3's and zero have NEC errors.
 
lovetohax said:
Has anyone successfully repaired A0403034 by reballing? I keep hearing people say reball, but nobody actually says that they've fixed a PS3 by reballing. I really don't want to reball if I don't have to, but I have like 3 BC models that have this error.

I'm so worried right now because I have gone through 10 PS3's and zero have NEC errors.
Click to expand...
Well I done all by reball, I have Cok002 with 40nm rsx and is the real example for 3034 and second error 4xxx is really rsx not responding well with syscon if modchip is not soldering correctly. I do reball on both cpu and rsx to skip all errors, apart from that from now where I have nec's caps I will exchange them with tantal. Just look at my previous photos posted.
 
now how do i access sb wart? on SW -sur001 board?i can see on putty but can not send commands.
Code: 
Boot Loader SE Version 4.7.0 (Build ID: 5271,50509, Build Date: 2015-02-04_21:00                                                                                                 :09)
SDK Version: 470.000
Copyright(C) 2015 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:12S DD2.0, SB:ZX1.1
Cell OS SDK4.7.0 000 (release build: r50509 2015_02_04_203000)
Copyright 2015 Sony Computer Entertainment Inc.
revision: 50304
date:     Wed Feb  4 21:02:03 JST 2015
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3492KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.7.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50509
lv2(2): build date: 2015/02/04 21:08:16
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x2100
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      rsx40 a01 500/650 vpe:ff shd:3f  [NM9677-18:0:4:12:d:f:6:0:1][28:0:a:0:1:0:1][1:1:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : ........... Failed (error code:0x8001002b)
lv2(2):
lv2(2): ###
lv2(2): ### Vflash recovery mode
lv2(2): ###
lv2(2):
lv2(2): creating the vflash recover process (emergency program) : OK

More details how should I send commands on SB uart to dump /read info ,what software do you use ?
 
vyktormvmpay25 said:
now how do i access sb wart? on SW -sur001 board?i can see on putty but can not send commands.
Code: 
Boot Loader SE Version 4.7.0 (Build ID: 5271,50509, Build Date: 2015-02-04_21:00                                                                                                 :09)
SDK Version: 470.000
Copyright(C) 2015 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:12S DD2.0, SB:ZX1.1
Cell OS SDK4.7.0 000 (release build: r50509 2015_02_04_203000)
Copyright 2015 Sony Computer Entertainment Inc.
revision: 50304
date:     Wed Feb  4 21:02:03 JST 2015
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3492KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.7.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50509
lv2(2): build date: 2015/02/04 21:08:16
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x2100
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      rsx40 a01 500/650 vpe:ff shd:3f  [NM9677-18:0:4:12:d:f:6:0:1][28:0:a:0:1:0:1][1:1:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : ........... Failed (error code:0x8001002b)
lv2(2):
lv2(2): ###
lv2(2): ### Vflash recovery mode
lv2(2): ###
lv2(2):
lv2(2): creating the vflash recover process (emergency program) : OK

More details how should I send commands on SB uart to dump /read info ,what software do you use ?
Click to expand...

Sending commands isn't supported by external PS3 firmwares.
 
lovetohax said:
Has anyone successfully repaired A0403034 by reballing? I keep hearing people say reball, but nobody actually says that they've fixed a PS3 by reballing. I really don't want to reball if I don't have to, but I have like 3 BC models that have this error.

I'm so worried right now because I have gone through 10 PS3's and zero have NEC errors.
Click to expand...
A 3034 doesn't mean the error is due to a BGA failure that a reball will fix. It can also be the die bumps, memory balls, electromigration in the die itself, etc. Those problems are so serious that they are not possible or worth diagnosing and fixing separately. So basically, hoping it's the BGA and reballing is the only way forward. Reball and hope for the best!

That doesn't necessarily mean it "Will" fix it. According to @squeept's repair spreadsheet 4/12 consoles with 40 3034 were successfully repaired by reballing (33% success rate). However, he did mention that his successes since starting that spreadsheet have been unusually low. Normally he repairs more by reballing. So a 33% success rate is probably a low estimate.

@vyktormvmpay25, what would you estimate your success rate with reballs are?
 
M4j0r said:
Here you go ;)
As you can see scversion doesn't return the full Patch ID, but in combination with the Soft ID it's enough to identify it.
Click to expand...
Cool, the tool fulfills 2 purposes, displays the error codes but also for hardware/software identification purposes
I like that you swapped the positions when printing the patch_id_rom and patch_id_ram
Is something i didnt realized when i suggested to change the way how are printed, but i know why you did it, some weeks ago you mentioned that the patch_id displayed in the "more system information" screen is readed from syscon RAM (not from syscon EEPROM)... and the way how this tools is printing them is mimicking a bit that screen... so yeah, this way is better

The other improvements i think can be made are mostly suggestions to @bucanero incase he wants to grow it
-The syscall to get the current time, to add timestamps as the name suffix of the log.txt files. This way are not overwritten and we can create a new "log-timestamp.txt" file everytime we run the app
-I think the timestamps printed in the log.txt at the right of each error code would be more straightformward in the format YYYY/MM/DD HH:MM:SS (and will be better aligned with each others)
-The original idea from @RIP-Felix was to make the error codes the most user friendly posible by showing some info about what means every error code, and the only way to achieve it is by adding all this descriptions to the code
 
lovetohax said:
Has anyone successfully repaired A0403034 by reballing? I keep hearing people say reball, but nobody actually says that they've fixed a PS3 by reballing. I really don't want to reball if I don't have to, but I have like 3 BC models that have this error.

I'm so worried right now because I have gone through 10 PS3's and zero have NEC errors.
Click to expand...

Most of the time for certain models they will be a bad connection for the RSX - CECHG models are most common for this. Its to do with the manufacturing quality of the PCB sony used.

They warp and break alot under heat conditions.

I usually reflow first with a IR heater - bottom plate 160C and top plate 190C for 30 secs.

If that doesn't fix it, i remove the RSX chip and check the pins on the RSX and motherboard.

What i find mostly is the bga solder balls have shrunk or the pins on the RSX have disintegrated - then means game over for that RSX.
Occasionally the motherboard points have not aged well.

Worst part of this in the early days is not having an IR heater, as getting the RSX off will destroy it without a proper temp control.
 
Got working PS3 CECHG08 (SEM-01)
Before: A0403034, A0404402 - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
Applied 5min 350°С to RSX with RSA flux
After: booted up
 
RIP-Felix said:
I suspect that you only have one error (1002). 1001 can happen by just flipping the PWR switch off. It's common when testing the syscon codes, as most people don't like to wait for the console to startup and shutdown gracefully, they just flip the rocker off. That generates a 1001 fairly regularly.

2120 will happen when you have the HDMI cord inserted into a console that experiences a YLOD. It probably happened when you hooked the console up for a test, expecting to get a picture. Unplug the HDMI cord and it will not happen on the next 1002, unless there actually is something wrong with the HDMI encoder.

You don't have a 3034, so it worth adding some low ESR TaPol. I'd start by removing that 1002, since we know what's causing it. Afterwards, see if any of the other errors persist.
Click to expand...

I have one of these hdmi test ports, 1002 is a power fail error code which is generic, 2120 code was pointing the finger on the hdmi encoder chip. When measuring the PTC thermistor fuses near by they are showing a 1.5 ohm resistance, meaning there is a fault somewhere on the hdmi encoder line.

PTC fuses should only read 0.2 ohms and increase in resistance if there is too much current to protect the circuit. This fuse is on the +5v line to the encoder - so more digging to find the offending fault.
 
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?
 
Last edited:
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
 
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...
eepcsum?
 
You must log in or register to reply here.

Similar threads

Back
Top