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

Okay after loosing the screws which tightens the heatsink to the processors I am still having an YLOD. I discovered, that error codes responsible for YLOD is this 1701 followed by 1601 (or the other way around). the ps3dev documentation says that it's probably related to the BGA ball cracks. I wrote probably, because tbh I doubt it - my ps3 has got small uptime and I've never exceeded temps above 65 degrees on CELL/RSX.
This YLOD always occurs whenever I am in XMB or close the app/game or start app/game. When app/game starts, no matter how long I play or how demanding game it is, everything is very stable. But whenever I start console, it goes to the XMB and I am in an XMB for longer than 30 seconds, 1 minute, it freezes the screen and console shuts down with YLOD. This is very, very, very odd behavior. I suspect it might be somehow related to OS issues, I was playing around with the system, gameboot/coldboot files, I installed also some homebrew apps and maybe something deadlocks the OS. I must check if this YLOD also occurs on different (empty) HDD. If so, then I will try to reinstall whole system via recovery.
 
CrazyRati0n said:
error codes responsible for YLOD is this 1701 followed by 1601 (or the other way around). the ps3dev documentation says that it's probably related to the BGA ball cracks. I wrote probably, because tbh I doubt it - my ps3 has got small uptime and I've never exceeded temps above 65 degrees on CELL/RSX.
Click to expand...
Probably is the operative word here.

It's a livelock condition that can be caused by software incompatibility as well. BGA or Bump failure is the most common way manner we see this error pop up, because they are in the errorlogs of an absurdly large number of consoles preceding a 3034 (closest thing we have to a smoking gun indicating a bad GPU). So that's where our minds immediately go.

But it was pointed out that 1701 can be cause by a bad HDD, or misbehaving homebrew app as well.
 
RIP-Felix said:
But it was pointed out that 1701 can be cause by a bad HDD, or misbehaving homebrew app as well.
Click to expand...
Alright, I managed to get rid of this YLOD. As I supposed, these 1601 and 1701 errors were caused by faulty homebrew/mod. After updating CFW to 4.90, removing all homebrew and installing them again, everything started working flawlessly :)
 
sandungas said:
What you did with the CELL ?, i guess is the same one, right ?, keep in mind whatever that damaged the thermal monitor chip (that seems it was damaged and now is working fine) happened at the same time the error 2130 you are having now
Actually, at some point you said you noticed some marks in the thermal monitor chip... so the previous person that was trying to fix it maybe damaged the thermal monitor chip... and the thermal sensor inside CELL too

Dunno, but to me it looks the CELL sensor is damaged, so the "gheto fix" i mentioned the other day by adding a custom sensor to the thermal monitor chip comes in mind again
And btw... i remember months ago there was someone in the forum reporting temperature value 255ºC in webman with a screenshot as a proof (but obviouslly it was not realistic). The point is... the thermal monitor chip was damaged, but the PS3 was booting fine into XMB and working normally (probably syscon was throwing internal errors but it seems it was booting anyway)
So... try to mimick that behaviour... boot without the thermal monitor chip... or take the damaged thermal monitor chip and solder it to the motherboard without pins #2 and #3 (this way is not connected to CELL at all)
Click to expand...
you have a good candidate for thermal sensor replacement model no company name
 
Fallen777 said:
you have a good candidate for thermal sensor replacement model no company name
Click to expand...
No, the monitors has a rom inside with ID's and a config, so i guess the PS3 is not going to accept other monitor models

If you are asking about the sensor inside CELL, RSX, etc... i dont know how are made or how are rated
Someone mentioned an alternative part for them a couple of days ago
 
sandungas said:
No, the monitors has a rom inside with ID's and a config, so i guess the PS3 is not going to accept other monitor models

If you are asking about the sensor inside CELL, RSX, etc... i dont know how are made or how are rated
Someone mentioned an alternative part for them a couple of days ago
Click to expand...
i know about thermal monitor part i am asking about replacement diode
 
Fallen777 said:
i know about thermal monitor part i am asking about replacement diode
Click to expand...
Then this is the post i was talking about, the other day i did read it but i was not following the conversation, i thought some of you was discussing it and that was the solution
https://www.psx-place.com/threads/f...nd-error-reporting.30100/page-167#post-357708
Den4515 said:
I solve A0A02031 error by soldering transistor 2N3906 to T1L chip (see datasheet to ADT7461A there displayed about the way to make external 'thermal' transistor) It will help, if the problem only in dead RSX thermal diod. But as usual the problem is bigger than that
Click to expand...
 
Hi, just got access to my CECHA01's error log. Are these indicative of NEC/TOKIN failure? I haven't used the console heavily yet, so no random shutdowns happened with me as of now. Also, is the console uptime "good"?

Bringup Count: 1248, Shutdown Count: 1042
Runtime: 56 Days, 13 Hours, 53 Minutes, 57 Seconds
Error Log
01: A0801002 Fri Dec 30 21:19:27 2005
02: A0801001 Sun Jan 16 21:40:05 2022
03: A0801001 Sun Jan 16 21:33:37 2022
04: A0801001 Sun Jan 16 21:32:19 2022
05: A0801001 Tue Dec 12 14:58:14 2017
06: A0801001 Tue Dec 12 14:44:44 2017
07: A0801002 Tue Jul 11 20:53:13 2017
08: A0801001 Sun Jun 4 21:55:58 2017
09: A0801001 Sat May 27 00:13:38 2017
10: A0801002 Mon May 15 23:23:59 2017
11: A0801001 Mon May 15 22:38:56 2017
12: A0801001 Fri Sep 2 15:26:44 2016
13: A0801001 Fri Sep 2 15:26:33 2016
14: A0801002 Mon Aug 29 14:16:42 2016
15: A0801001 Mon Aug 22 14:33:30 2016
16: A0801001 Mon Aug 22 13:28:16 2016
17: A0801001 Mon Aug 22 11:32:57 2016
18: A0801001 Fri Aug 19 14:05:09 2016
19: A0801001 Thu Aug 18 23:33:44 2016
20: A0801002 Thu Aug 18 15:00:43 2016
21: A0801001 Thu Aug 18 14:57:11 2016
22: A0801001 Tue Aug 9 10:32:05 2016
23: A0801001 Thu Aug 4 19:26:50 2016
24: A0801001 Wed Aug 3 23:34:38 2016
25: A0801001 Fri Jul 29 23:12:48 2016
26: A0801002 Thu Jul 28 23:11:57 2016
27: A0801002 Sun Jul 24 15:25:46 2016
28: A0801001 Wed Jul 20 23:01:15 2016
29: A0801002 Mon Jul 18 00:02:58 2016
30: A0801001 Mon Jul 18 00:02:04 2016
31: A0801001 Fri Jul 15 13:44:35 2016
32: FFFFFFFF Thu Jul 14 12:21:27 2016
 
redcyclone said:
Hi, just got access to my CECHA01's error log. Are these indicative of NEC/TOKIN failure? I haven't used the console heavily yet, so no random shutdowns happened with me as of now. Also, is the console uptime "good"?

Bringup Count: 1248, Shutdown Count: 1042
Runtime: 56 Days, 13 Hours, 53 Minutes, 57 Seconds
Error Log
01: A0801002 Fri Dec 30 21:19:27 2005
02: A0801001 Sun Jan 16 21:40:05 2022
03: A0801001 Sun Jan 16 21:33:37 2022
04: A0801001 Sun Jan 16 21:32:19 2022
05: A0801001 Tue Dec 12 14:58:14 2017
06: A0801001 Tue Dec 12 14:44:44 2017
07: A0801002 Tue Jul 11 20:53:13 2017
08: A0801001 Sun Jun 4 21:55:58 2017
09: A0801001 Sat May 27 00:13:38 2017
10: A0801002 Mon May 15 23:23:59 2017
11: A0801001 Mon May 15 22:38:56 2017
12: A0801001 Fri Sep 2 15:26:44 2016
13: A0801001 Fri Sep 2 15:26:33 2016
14: A0801002 Mon Aug 29 14:16:42 2016
15: A0801001 Mon Aug 22 14:33:30 2016
16: A0801001 Mon Aug 22 13:28:16 2016
17: A0801001 Mon Aug 22 11:32:57 2016
18: A0801001 Fri Aug 19 14:05:09 2016
19: A0801001 Thu Aug 18 23:33:44 2016
20: A0801002 Thu Aug 18 15:00:43 2016
21: A0801001 Thu Aug 18 14:57:11 2016
22: A0801001 Tue Aug 9 10:32:05 2016
23: A0801001 Thu Aug 4 19:26:50 2016
24: A0801001 Wed Aug 3 23:34:38 2016
25: A0801001 Fri Jul 29 23:12:48 2016
26: A0801002 Thu Jul 28 23:11:57 2016
27: A0801002 Sun Jul 24 15:25:46 2016
28: A0801001 Wed Jul 20 23:01:15 2016
29: A0801002 Mon Jul 18 00:02:58 2016
30: A0801001 Mon Jul 18 00:02:04 2016
31: A0801001 Fri Jul 15 13:44:35 2016
32: FFFFFFFF Thu Jul 14 12:21:27 2016
Click to expand...
1001 and 1002 error codes indicate dead NEC/TOKIN cell capacitors. In what manner do you experience or experienced YLOD? Random shutdowns during gameplay?
 
CrazyRati0n said:
1001 and 1002 error codes indicate dead NEC/TOKIN cell capacitors. In what manner do you experience or experienced YLOD? Random shutdowns during gameplay?
Click to expand...

I acquired this console last week, I haven't experienced YLODs with it yet. Seller says it's never been reballed or reflowed. Just checked the error log out of curiosity and these 1001s and 1002s concerned me.
 
redcyclone said:
I acquired this console last week, I haven't experienced YLODs with it yet. Seller says it's never been reballed or reflowed. Just checked the error log out of curiosity and these 1001s and 1002s concerned me.
Click to expand...
These errors are not recorded in SYSCON for no reason. I suspect previous owner must have experienced YLOD in the past, but he merely didn't tell you that.
 
Hi, I am getting the following errlog after delidding a CECHE01 this month:

ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0x0de3f771 2007/05/21 06:23:45
ofst[ 4]:err_code:0xa0801004, clock:0x0de3f8e3 2007/05/21 06:29:55
ofst[ 8]:err_code:0xa0801004, clock:0x0de3f961 2007/05/21 06:32:01
ofst[ 12]:err_code:0xa0801004, clock:0x0de3f9e7 2007/05/21 06:34:15
ofst[ 16]:err_code:0xa0801004, clock:0x0de3fabd 2007/05/21 06:37:49
ofst[ 20]:err_code:0xa0801004, clock:0x0de3fd74 2007/05/21 06:49:24
ofst[ 24]:err_code:0xa0801004, clock:0x0de3fe34 2007/05/21 06:52:36
ofst[ 28]:err_code:0xa0801004, clock:0x10e609db 2008/12/25 09:07:39
ofst[ 32]:err_code:0xa0801001, clock:0x11f15b0e 2009/07/16 03:29:18
ofst[ 36]:err_code:0xa0801004, clock:0x11f15c7c 2009/07/16 03:35:24
ofst[ 40]:err_code:0xa0801004, clock:0x11f15cb2 2009/07/16 03:36:18
ofst[ 44]:err_code:0xa0801004, clock:0x129916b2 2009/11/20 08:58:26
ofst[ 48]:err_code:0xa0801004, clock:0x2b57e0a5 2023/01/16 10:17:09 <---PS3 was working until here
ofst[ 52]:err_code:0xa0404411, clock:0xffffffff <---after delid

I thought I was really careful :( The only info I could find about 4411 was from the quote below. But this error is seen here by itself, without 3034 etc. Any ideas?

RIP-Felix said:
Well there are no timestamps, so the battery was removed. Someone opened it and "did something" requiring them to unplug the CMOS battery. Whatever they did didn't work, since they had 10x YLOD with 3034 and 4411. These are consistent with an RSX issue usually requiring areball to fix. That means that the 10x YLODs recorded in the errorlog were form subsequent testing after work was done on the console. I'm guessing this was you @TimeWalker75a?

I generally suggest the first thing anyone do is get the errorlog off the console before they start filling it with new errors, which overwrite the error history of the console. You might erase important errors that tell the console's story.

Spilled milk. Moving on...It looks like there are a string of 80 1001's that singal a GLOD to me. @squeept had a console he reballed that exhibited the same behavior. Namely, GLOD & SYSCON full of 80 1001's. He replaced the tokins and it had no effect. He concluded it was a dead RSX due to bump failure, but I still wonder if it might mean the CPU needs a reball. I would expect to see an unhealthy resistance on the RSX (less than 1 Ohm) if it were dead. @TimeWalker75a could you measure the resistance of the tokins on the CPU/RSX +/GND? If the RSX is less than 1 ohm it could mean it's dead or you screwed up the tantalum mod. I just released the Tantalizer beta, so you could go that route now, if you want. It makes it easy.

Your latest error related to the SB is concerning. So is the behavior. Sounds like a blown fuse that's taken out that circuit. You need to pull out a multimeter and go to town! Find the blow fuse, shorting cap, resistor, or lightning struck IC. The bigger question is what happened to cause that since the GLOD??? Did you test a good PSU? Is it possable the old one was bad, and that all that flipping the PWR switch caused a surge that blew a fuse on the motherboard? Almost sound like you left something in there and it shorted out and blew a fuse. Liquid damage maybe? A stray piece of wire? IDK, you'll have to troubleshoot your MB to figure out the source of that.

Edit:
Lastly, the bootloader failing to initialize is interesting. Have you tried rebuilding the database in the recovery menu? I wonder if a corrupt DB was causing your GLOD.
Click to expand...
 
solaralex said:
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0x0de3f771 2007/05/21 06:23:45
ofst[ 4]:err_code:0xa0801004, clock:0x0de3f8e3 2007/05/21 06:29:55
ofst[ 8]:err_code:0xa0801004, clock:0x0de3f961 2007/05/21 06:32:01
ofst[ 12]:err_code:0xa0801004, clock:0x0de3f9e7 2007/05/21 06:34:15
ofst[ 16]:err_code:0xa0801004, clock:0x0de3fabd 2007/05/21 06:37:49
ofst[ 20]:err_code:0xa0801004, clock:0x0de3fd74 2007/05/21 06:49:24
ofst[ 24]:err_code:0xa0801004, clock:0x0de3fe34 2007/05/21 06:52:36
ofst[ 28]:err_code:0xa0801004, clock:0x10e609db 2008/12/25 09:07:39
ofst[ 32]:err_code:0xa0801001, clock:0x11f15b0e 2009/07/16 03:29:18
ofst[ 36]:err_code:0xa0801004, clock:0x11f15c7c 2009/07/16 03:35:24
ofst[ 40]:err_code:0xa0801004, clock:0x11f15cb2 2009/07/16 03:36:18
ofst[ 44]:err_code:0xa0801004, clock:0x129916b2 2009/11/20 08:58:26
ofst[ 48]:err_code:0xa0801004, clock:0x2b57e0a5 2023/01/16 10:17:09 <---PS3 was working until here
ofst[ 52]:err_code:0xa0404411, clock:0xffffffff <---after delid

I thought I was really careful :( The only info I could find about 4411 was from the quote below. But this error is seen here by itself, without 3034 etc. Any ideas?
Click to expand...
Its gone jim it ain't among us anymore.
 
Getting that weird 2022 error on my working ps3 slim 2001a, mentioned a few post back by other ppl. I bought this console recently off ebay, just needed a new laser which has been replaced. Upon further testing it cant do 480p anymore via the multiAV cord, 480i does work tho. Other than that the console works fine, Thoughts?

Bringup Count: 2470, Shutdown Count: 2102
Runtime: 237 Days, 5 Hours, 17 Minutes, 55 Seconds
Error Log
01: A0802022 Sat Mar 18 02:03:07 2023
02: A0802022 Sat Mar 18 01:46:53 2023
03: A0802022 Wed Mar 15 17:59:53 2023
04: A0802022 Wed Mar 15 17:59:50 2023
05: A0802022 Wed Mar 15 05:17:38 2023
06: A0802022 Wed Mar 15 04:54:43 2023
07: A0802022 Thu Mar 9 04:46:40 2023
08: A0802022 Thu Mar 9 04:13:31 2023
09: A0802022 Sat Sep 3 12:08:44 2011
10: A0802022 Sat Sep 3 12:08:44 2011
11: A0802022 Sat Sep 3 12:08:43 2011
12: FFFFFFFF Fri Dec 31 16:59:59 1999
13: FFFFFFFF Fri Dec 31 16:59:59 1999
14: FFFFFFFF Fri Dec 31 16:59:59 1999
15: FFFFFFFF Fri Dec 31 16:59:59 1999
16: FFFFFFFF Fri Dec 31 16:59:59 1999
17: FFFFFFFF Fri Dec 31 16:59:59 1999
18: FFFFFFFF Fri Dec 31 16:59:59 1999
19: FFFFFFFF Fri Dec 31 16:59:59 1999
20: FFFFFFFF Fri Dec 31 16:59:59 1999
21: FFFFFFFF Fri Dec 31 16:59:59 1999
22: FFFFFFFF Fri Dec 31 16:59:59 1999
23: FFFFFFFF Fri Dec 31 16:59:59 1999
24: FFFFFFFF Fri Dec 31 16:59:59 1999
25: FFFFFFFF Fri Dec 31 16:59:59 1999
26: FFFFFFFF Fri Dec 31 16:59:59 1999
27: FFFFFFFF Fri Dec 31 16:59:59 1999
28: FFFFFFFF Fri Dec 31 16:59:59 1999
29: FFFFFFFF Fri Dec 31 16:59:59 1999
30: FFFFFFFF Fri Dec 31 16:59:59 1999
31: FFFFFFFF Fri Dec 31 16:59:59 1999
32: FFFFFFFF Fri Dec 31 16:59:59 1999
 
You must log in or register to reply here.

Similar threads

Back
Top