RIP-Felix
Senior Member
This is actually, the first and only time someone has posted SYSCON errors showing 1002's in a console claiming that repeated repeated attempts to power on the console resulted in it working. I had written off the idea that heat could have any effect on the tokins...which I'm still dubious about. However, that doesn't mean the VRM can't be effected by the heat. I'm not sure.Hello,
I have recently inherited a Fat PS3 with YLOD. The console was in good conditions with warranty sticker still applied, so I'm pretty confident nobody has messed with it (except myself)
I believe the console belongs to the Warm-Start category, according to the faq.
This is the behavior I observe:
- from completely cold, the console shows YLOD between 3 and 12 secs approx.
- during a period of about 3 minutes of repeatedly trying to switch the console on, the time elapsed to YLOD becomes progressively longer, until the console becomes stable and stays powered on.
- after this time, all in all the console seems to be working fine. I also tried to play GT5 for 30 mins with no visible issue.
If I switch the console off then on when warm, the console will boot fine first attempt.
Confident of the stability, I went for jailbreak and extracted syscon logs with PS3 Advanced tools.
From the logs, I can see error 1002 (RSX VRAM Power Fail) as only error.
I read on this forum that 1002 is usually a sign of bad Tokins, but I also read that for Warm-Start YLOD consoles, the Tokins are usually not the culprits.
Any suggestion on how I could take the investigation further?
Logs below, and thanks in advance to all the experts in this thread!
Code:Firmware Version: 4.88 (build 50731) Platform ID: CokE10 Product Code: 00 87 Product Sub Code: 00 07 Hardware Config: 4E00FFFF0107BCBF Syscon Fimware Version: 0E69.0001000400040002 (EEPROM: 0001000400040002) Bringup Count: 1726, Shutdown Count: 1639 Runtime: 162 Days, 7 Hours, 24 Minutes, 52 Seconds Error Log 01: A0801002 Wed Feb 16 01:58:24 2022 02: A0801002 Wed Feb 16 01:57:37 2022 03: A0801002 Wed Feb 16 01:57:02 2022 04: A0801002 Wed Feb 16 01:56:42 2022 05: A0801002 Wed Feb 16 01:56:34 2022 06: A0801002 Wed Feb 16 01:56:25 2022 07: A0801002 Wed Feb 16 01:56:06 2022 08: A0801002 Wed Feb 16 01:55:45 2022 09: A0801002 Wed Feb 16 01:55:31 2022 10: A0801002 Mon Feb 14 18:12:41 2022 11: A0801002 Mon Feb 14 18:12:33 2022 12: A0801002 Mon Feb 14 18:11:51 2022 13: A0801002 Mon Feb 14 18:11:43 2022 14: A0801002 Mon Feb 14 18:11:23 2022 15: A0801002 Mon Feb 14 18:11:15 2022 16: A0801002 Mon Feb 14 18:11:07 2022 17: A0801002 Mon Feb 14 18:10:50 2022 18: A0801002 Mon Feb 14 18:10:32 2022 19: A0801002 Mon Feb 14 18:10:15 2022 20: A0801002 Mon Feb 14 18:10:07 2022 21: A0801002 Mon Feb 14 09:12:57 2022 22: A0801002 Mon Feb 14 09:12:39 2022 23: A0801002 Mon Feb 14 09:12:33 2022 24: A0801002 Mon Feb 14 09:12:14 2022 25: A0801002 Mon Feb 14 09:12:06 2022 26: A0801002 Mon Feb 14 09:11:48 2022 27: A0801002 Mon Feb 14 09:11:31 2022 28: A0801002 Mon Feb 14 09:11:13 2022 29: A0801002 Mon Feb 14 09:10:55 2022 30: A0801002 Sun Feb 13 22:48:59 2022 31: A0801002 Sun Feb 13 20:52:27 2022 32: FFFFFFFF Sun Feb 13 20:52:07 2022
You do have the correct errors for a tokin replacment. I just don't have an explanation for that warm start YLOD. I greatly appreciate the errorlog with that observation. I would have bet this was a BGA defect otherwise!
)

