PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
Jose Denilson Nog F
Forum Noob
Yeah, what gave it away? haha. Im also returning here to update you guys that I managed to read the syscon after all, but I had to boot up into my Linux partition and install some dependencies. My 2 consoles(CECH20 and CECH21) have A0203010 and A0093003. I will try to look up what may be the reasons. The A0203010 didnt help much, as I found little information about it online. But its something to work on.
Nascar1243
Member
Can you please include the full error logs of those consoles along with a description of the condition of the console along with if the warranty stick was intact, just anything you think would be important to note
Sent from my iPad using Tapatalk
Tomatarto
Member
Step 00 is when the SYSCON switches on the power converters and the clocks
The 3001 error code with that POST number is most likely a fault with the 12V line
@Fallen777 is correct. Chances are the PSU is at fault, or some sort of fuse/SMT on the 12V line.
Well 3003 is cell core power fault since 2000x-2100x still use NEC caps on side b you can do tantulum fix but 3010
That's pretty much a rabbit hole its in prefix 30 so that means it might be pos state error possible areas are clock generation circuit power supply chip south bridge circuitry depends on how well you use multimeter also you should refer to some YouTube channels like idreestech that will help you in approaching suspected fault areas.
Last edited:
Bazookaben
Forum Noob
Is SYSCON useful when your console just shuts down after 2-10 seconds with no yellow or red light?
I would think that immediate power down means no error logs are able to be written? Hopefully there is still something useful.
But I just want to see what you guys think before I go through the trouble of building the cable and setting everything up
I would think that immediate power down means no error logs are able to be written? Hopefully there is still something useful.
But I just want to see what you guys think before I go through the trouble of building the cable and setting everything up
RIP-Felix
Senior Member
Guys, that's the errorlog. Just before this he recorded a bringup that shows the bootloader starting and web man mod issuing read temp commands (that's why there are so may temp commands being issued). That means his console works. So the 3001 errors are from before. Likely from attepting to power on the console without the 12v connector attached.
RIP-Felix
Senior Member
I suspect bad CPU. Try pressure test. Remote possability of a bad CPU VRM buck converter or filtering cap. But 3010 is usually an important voltage line to the CPU and has been seen in cases where the CPU has been destroyed by a heatgun. It may only need reballed. Or it could have worn out. Or have trace damage. Or an important SMD in the voltage line it bad. 3010 is less understood, which is why I haven't written up what I do know about it on the dev wiki yet. But I probably should.
Jose Denilson Nog F
Forum Noob
Im on Windows now, but I believe I didnt save it, just screenshotd it, but later I will switch OS and post it. Both of them I got already not working for "cheap"(not as cheap as it is for some of you in other countries, but still cheap compared to a working one haha) to challenge myself and maybe learn something, my experience was with some other simpler electronics and RGH on Xbox and some other things. So both of them had been open already by someone else, the first one I got dont even have a switch board(with the power and eject buttons) but still worked for some minutes when I managed to turn it on with a cd on the drive(just inserted it enough to power it on and pulled it back), this one is the one with 3003, I will try to solder the tantalum caps to the CELL, as I already have those(I dont have a lot of stuff or equipment, as I dont work with it and things usually are a little expensive here). The other one I got this sunday and didnt mess around with it much, on the outside its in better conditions(and has the switchboard) but inside I noticed that the CELL(I believe its CELL, but maybe its the RSX, I need to check that again) has a delid for some reason, no idea why, maybe it was indeed heated up. But I will try to inspect the board more closely as I didnt have too much time with this one yet. The first one I tested more and couldnt find anything like a short or something like that, but Im no professional and those models dont have the service manual avaible online(SUR001 with 3003 and DYN001 with 3010). Thanks for the interest and help guys, didnt expect I would get any attention
I'm unable to get the codes from a YLOD VER-001 board. Every code is just 00000000 FFFFFFFF FFFFFFFF, which shouldn't happen because it get YLOD every time i try to boot.
Running the errlog command after bringup gives this, but not sure what to make of it.
Running the errlog command after bringup gives this, but not sure what to make of it.
> errlog get 00
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!Boot Loader SE Version 4.8.2 (Build ID: 5336,50677, Build Date: 2017-08-24_13:10:12)
#!SDK Version: 482.000
#!Copyright(C) 2017 Sony Computer Entertainment Inc.All Rights Reserved.
#![INFO]: === eXtreme Data Rate Memory Subsystem ===
#![INFO]: (Configured Memory
#!S
#!ize 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:11S DD1.0, SB:SX1.1
#![ERROR]: 0xb0000
#!0
#!04 Boot CELL OS : stopcode [19]
#!load lv1 fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!
#!Boot Loader SE Version 4.8.2 (Build ID: 5336,50677, Build Date: 2017-08-24_13:10:12)
#!SDK Version: 482.000
#!Copyright(C) 2017 Sony Computer Entertainment Inc.All Rights Reserved.
#![INFO]: === eXtreme Data Rate Memory Subsystem ===
#![INFO]: (Configured Memory
#!S
#!ize 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:11S DD1.0, SB:SX1.1
#![ERROR]: 0xb0000
#!0
#!04 Boot CELL OS : stopcode [19]
#!load lv1 fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
Tomatarto
Member
Why is he here then?
Tomatarto
Member
The "#!load lv1 fail" is certainly concerning.
Its probably an obvious solution but i've got no idea
Nascar1243
Member
Yes, if you have a 25xx model or higher, then it is very likely you have the YLOD, it just has a different way of showing it, if it is a 21xx or earlier then likely not but its always best to check syscon either way, but in this case I suspect it is a late slim or super slim in which case, yes syscon is very useful in determining the cause of the system shutting down after a few seconds.
Sent from my iPad using Tapatalk
"#![ERROR]: 0xb0000" doesn't seem great either, why is everything just 0's? Maybe some ROM chip somewhere is just totally corrupted or something, just guessing.
Just hoping someone who actually knows something sees this.
Emil Tuzla
Forum Noob
Anyone had A0801200 errors after fixing tokins?
I got console with a lot 1001 and 1002 errors and after replacing tokins now its glod and getting only A0801200 errors.
CECHH04
DIA-001 MB
===================================
ERR 00: 00000000 A0801200 FFFFFFFF
ERR 01: 00000000 A0801200 FFFFFFFF
ERR 02: 00000000 A0801200 FFFFFFFF
ERR 03: 00000000 A0801200 FFFFFFFF
ERR 04: 00000000 A0801200 FFFFFFFF
ERR 05: 00000000 A0801200 FFFFFFFF
ERR 06: 00000000 A0801200 FFFFFFFF
ERR 07: 00000000 A0801200 FFFFFFFF
ERR 08: 00000000 A0801004 1D201CC5
ERR 09: 00000000 A0801004 FFFFFFFF
ERR 10: 00000000 A0801004 0B741FBC
ERR 11: 00000000 A0801004 0B740998
ERR 12: 00000000 A0801004 1D172E22
ERR 13: 00000000 A0801004 1D16F734
ERR 14: 00000000 A0801004 0B6D0BE8
ERR 15: 00000000 A0801004 1C0F8D06
ERR 16: 00000000 A0801004 0B682B33
ERR 17: 00000000 A0801002 FFFFFFFF
ERR 18: 00000000 A0801004 1D0F4905
ERR 19: 00000000 A0801001 1D0F382B
===================================
I got console with a lot 1001 and 1002 errors and after replacing tokins now its glod and getting only A0801200 errors.
CECHH04
DIA-001 MB
===================================
ERR 00: 00000000 A0801200 FFFFFFFF
ERR 01: 00000000 A0801200 FFFFFFFF
ERR 02: 00000000 A0801200 FFFFFFFF
ERR 03: 00000000 A0801200 FFFFFFFF
ERR 04: 00000000 A0801200 FFFFFFFF
ERR 05: 00000000 A0801200 FFFFFFFF
ERR 06: 00000000 A0801200 FFFFFFFF
ERR 07: 00000000 A0801200 FFFFFFFF
ERR 08: 00000000 A0801004 1D201CC5
ERR 09: 00000000 A0801004 FFFFFFFF
ERR 10: 00000000 A0801004 0B741FBC
ERR 11: 00000000 A0801004 0B740998
ERR 12: 00000000 A0801004 1D172E22
ERR 13: 00000000 A0801004 1D16F734
ERR 14: 00000000 A0801004 0B6D0BE8
ERR 15: 00000000 A0801004 1C0F8D06
ERR 16: 00000000 A0801004 0B682B33
ERR 17: 00000000 A0801002 FFFFFFFF
ERR 18: 00000000 A0801004 1D0F4905
ERR 19: 00000000 A0801001 1D0F382B
===================================
Emil Tuzla
Forum Noob
I know its thermal paste error but if thermal paste is not making contact it will overheat and turn off, console is turned on for 1 hour with green light,vent is running with normal speed.I connected to syscon with console turned on and its just giving me A0801200 one after another.
Also I get only black screen, no display
Bazookaben
Forum Noob
Getting two error codes on a 3001B system from every shutdown, in this order:
A0801701
A08014FF
Dev wiki says 14FF is likely RSX bumps (on a 40nm? damn)... but is it possible it could be hard drive I/O related? Let me explain.
Background:
Shutdown usually happens soon after power on, but I found I can get to the XMB if I start with a safe mode and reformat.
And after that reformat, I've been able to allow Shadow of the Colossus to run for hours with no errors.
But when I try to play Vanquish, PS3 crashes early in the tutorial stage, before you get out of first person mode. Same two errors.
The difference between Vanquish and SotC? Vanquish installs a lot of files onto the hard drive.
Another strange event: I had a very old 30GB SSD that I've used for various things in a variety of PCs, including as portable storage. But it immediately fried when I tried to use it in the PS3. Couldn't use it again in a PC
After that I got a modern SSD that is holding up so far. Before all this I removed HDD that the system came with because googling had told me that could be the problem, I've never actually tried to put it back in. I noticed I can read SMART data off it. I don't if that's normal or not.
So, between the frying of the old SSD, and the difference in behavior between Vanquish and SotC, is it possible this could be a faulty circuit going to the SATA port?
I guess the difference between the two games could just also be down to how they tax the RSX?
A0801701
A08014FF
Dev wiki says 14FF is likely RSX bumps (on a 40nm? damn)... but is it possible it could be hard drive I/O related? Let me explain.
Background:
Shutdown usually happens soon after power on, but I found I can get to the XMB if I start with a safe mode and reformat.
And after that reformat, I've been able to allow Shadow of the Colossus to run for hours with no errors.
But when I try to play Vanquish, PS3 crashes early in the tutorial stage, before you get out of first person mode. Same two errors.
The difference between Vanquish and SotC? Vanquish installs a lot of files onto the hard drive.
Another strange event: I had a very old 30GB SSD that I've used for various things in a variety of PCs, including as portable storage. But it immediately fried when I tried to use it in the PS3. Couldn't use it again in a PC
After that I got a modern SSD that is holding up so far. Before all this I removed HDD that the system came with because googling had told me that could be the problem, I've never actually tried to put it back in. I noticed I can read SMART data off it. I don't if that's normal or not.
So, between the frying of the old SSD, and the difference in behavior between Vanquish and SotC, is it possible this could be a faulty circuit going to the SATA port?
I guess the difference between the two games could just also be down to how they tax the RSX?
Bazookaben
Forum Noob
I meant to say "can't read" SMART data on the original HDD.
Kalulo24
Member
Similar threads
-
-
PS3 CECHA00 with several SYSCON errors (3004, 1001,1002, 2120,3011)
- Started by LSL
- Replies: 7
-
PS3 Interesting PS3 Errors (1802, 1701, 1601) and Capacitor Replacement- Started by Cheshire UK
- Replies: 2
-