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

RIP-Felix said:
I love that you're including a screenshot of this in your eBay listing. I saw you are finally back at it. I see a reball and a 65nm frankie up for sale. High price, but I'm curious to see if it sells. 2 year warranty is pretty epic. You do lean pretty heavily on your credentials, so maybe you can convince someone yours is worth a premium. I'm not saying it isn't worth that...IDK really.

AFAIK @DeadEnd's is the only one that's been sold, for around $800. But who knows what they're worth. The market will decide and I guess it makes sense to start high and lower the price if it doesn't sell.

When I really start thinking about the amount of time and money I've put in before having any sort of sucess with reballing, let alone a frankie, $800 seems fair. And I would need to sell many before breaking even.

OTH I would like to see the prices fall to a more affordable point where more people can enjoy these consoles. We know how to do it now. It's just a matter of cranking them out and competing with each other.
Click to expand...

In North America people have much more disposable income compared to other countries, due to the price of food, gas, energy, vehicles, property, retail, rent, etc in the US being many times cheaper than in Europe. And the average wage salary in the US being higher. For example here in the UK, 500 litres of heating oil = $918, electricity bill for 1 month = $262, and food prices are sky high. Yet the average yearly income in Europe is alot less when compared to the US. Because of this, imo, there is no way a person would pay $800 for a BC 40nm / 65nm Frankie PS3 in Europe. Maybe $400 to $500 max.
 
Mostly offtopic?

The weather turned shitty so I'm making some money before I go back to hiding from customers. Next week I start getting my gigantic garden in, and probably expanding with a small orchard. I'm not a doomsday prepper or anything, but the writing on the wall from climate change is there - food quality, security, and prices will never be the same. Anyway....

My A01 prices have been going up about $100 a year for the last few years, even before the pandemic. I've been getting the $680 ask for at least a year now.

About 5 years ago, I really leaned in to the "artisan" angle of quality over quantity with my reputation, experience, and established business. I used to churn out a handful of consoles a day, now for most things it takes me a day or two per console. A 2 year warranty from someone with a 15+ year old powerseller account with 15k feedback means a lot more than some random dude. My info gets passed around by word of mouth to some serious collectors - I've had people swap out their entire collections through me. Not bragging, that's all just to say that my sale prices are absolutely NOT indicative of the "real" market value on any console.

I already sold the first 40nm I did for $1180. They'll probably get outrageous prices for awhile until the hype dies down, but my guess is that they'll stabilize somewhere around "your own established base A01 price" + $250.
 
I also think the supply of virgin A01 is really starting to dry up. The great TOKIN massacre of 2020 really put a dent in the supply. And now all the previously repaired then given up on consoles have heatgunned chips and butchered delids PLUS ripped off then burned on caps. So the base input cost is rising. Average number of "bought at an estate sale, no cords to test it" liar consoles needed before you find a good quality repair candidate is always rising.

And I think there's a growing sentiment from people that have been ripped off repeatedly by the heatgun and TOKIN fixes that paying more is actually worth it to avoid yet another return / dispute.
 
Well you can get a working A01 for $250, so +$250 would put it in the $500 range, which I think is around the fair to aggressively (competitive) priced range. There's still meat left on the bone at that price, but you'd have to churn them out quick, which may lead to cutting corners that comprimizes reliability.

On a separate note, am I remembering correctly that you clean the flux off the MB using an ultrasonic bath filled with IPA? Have you tried branson water based cleaners? Or do they not take the kingbo off very well?
 
RIP-Felix said:
Well you can get a working A01 for $250, so +$250 would put it in the $500 range, which I think is around the fair to aggressively (competitive) priced range. There's still meat left on the bone at that price, but you'd have to churn them out quick, which may lead to cutting corners that comprimizes reliability.

On a separate note, am I remembering correctly that you clean the flux off the MB using an ultrasonic bath filled with IPA? Have you tried branson water based cleaners? Or do they not take the kingbo off very well?
Click to expand...

Since I'm pretty much doing the same amount of work whether the console is working or not, I've found paying the premium on sealed but not working consoles is the spot that I like to jump in. I've found that taking working consoles as the base still had warranty returns since BGA/RSX issues were already present or crept up anyway, and I hate the idea that I'm responsible for killing an already working console if something goes wrong.

Ultrasonic bath in distilled water + Syberkleen or SRA TruPower. Then hose it down in the sink, then it goes in the IPA bath to displace the rinse water. Then a quick blowgun and in to the drying oven for a bit. Never tried the Branson (suck it, Rossmann!), the other two have always been perfect.
 
Last edited:
Hi everyone, can I get some help on my CECHA unit? It was turning off before on heavy games so I had the capacitors fully replaced. All NEC Tokins are gone now and have been replaced with SMD Tantalums (3 for each NEC Tokin). I was stress testing it for a week and everything seemed fine, could play TLOU, Tekken Tag 2 seemingly endlessly. Just now though, I was playing NBA 2k18 and it shut off during the 3rd quarter :( Dumping the Syscon Logs via Advanced Tools had this to say:

Error Log
01: A0801002 Sun Jan 1 14:44:57 2006
02: A0802022 Sat Dec 31 13:59:09 2005
03: A0802022 Sat Dec 31 13:47:49 2005
04: A0802022 Sat Dec 31 02:11:35 2005
05: A0802022 Sat Dec 31 02:07:22 2005
06: A0802022 Sat Dec 31 01:42:05 2005
07: A0802022 Sat Dec 31 01:41:18 2005
08: A0802022 Sat Dec 31 13:48:38 2005
09: A0802022 Sat Dec 31 13:47:25 2005
10: A0802022 Sat Dec 31 13:46:41 2005
11: A0802022 Sat Dec 31 13:46:14 2005
12: A0802022 Sat Dec 31 13:08:01 2005
13: A0802022 Sat Dec 31 13:06:58 2005
14: A0802022 Sat Dec 31 01:43:12 2005
15: A0802022 Sat Dec 31 01:39:32 2005
16: A0801001 Sat Dec 31 00:00:19 2005
17: A0801001 Sat Dec 31 00:02:13 2005
18: A0801001 Sat Dec 31 00:00:29 2005
19: A0801001 Sat Dec 31 00:00:19 2005
20: A0801001 Sat Dec 31 00:00:07 2005
21: A0801002 Sat Dec 31 00:00:00 2005
22: A0801002 Sat Dec 31 00:00:00 2005
23: A0801002 Sat Dec 31 00:00:00 2005
24: A0801002 Fri Dec 31 23:59:59 1999
25: A0801002 Sat Dec 31 00:00:00 2005
26: A0801002 Fri Dec 31 23:59:59 1999
27: A0221002 Fri Dec 31 23:59:59 1999
28: A0231002 Fri Dec 31 23:59:59 1999
29: A0801004 Sat Dec 31 00:31:04 2005
30: A0801001 Sat Dec 31 00:00:03 2005
31: A0801001 Sat Dec 31 00:01:45 2005
32: FFFFFFFF Sat Dec 31 01:57:06 2005

Upon checking it seems it's still a caps issue and the AV Encoder chip? I've been using HDMI cables ever since so I don't know if that AV error will still affect it. As for the caps, by chance am I using faulty ones? Or is it normal for caps error appear even after replacing them since the values don't necessarily match? Hope someone can help me understand it more, I'm very new to this.

Thanks in advance!
 
omnicloud7 said:
Hi everyone, can I get some help on my CECHA unit? It was turning off before on heavy games so I had the capacitors fully replaced. All NEC Tokins are gone now and have been replaced with SMD Tantalums (3 for each NEC Tokin). I was stress testing it for a week and everything seemed fine, could play TLOU, Tekken Tag 2 seemingly endlessly. Just now though, I was playing NBA 2k18 and it shut off during the 3rd quarter :( Dumping the Syscon Logs via Advanced Tools had this to say:

Error Log
01: A0801002 Sun Jan 1 14:44:57 2006
02: A0802022 Sat Dec 31 13:59:09 2005
03: A0802022 Sat Dec 31 13:47:49 2005
04: A0802022 Sat Dec 31 02:11:35 2005
05: A0802022 Sat Dec 31 02:07:22 2005
06: A0802022 Sat Dec 31 01:42:05 2005
07: A0802022 Sat Dec 31 01:41:18 2005
08: A0802022 Sat Dec 31 13:48:38 2005
09: A0802022 Sat Dec 31 13:47:25 2005
10: A0802022 Sat Dec 31 13:46:41 2005
11: A0802022 Sat Dec 31 13:46:14 2005
12: A0802022 Sat Dec 31 13:08:01 2005
13: A0802022 Sat Dec 31 13:06:58 2005
14: A0802022 Sat Dec 31 01:43:12 2005
15: A0802022 Sat Dec 31 01:39:32 2005
16: A0801001 Sat Dec 31 00:00:19 2005
17: A0801001 Sat Dec 31 00:02:13 2005
18: A0801001 Sat Dec 31 00:00:29 2005
19: A0801001 Sat Dec 31 00:00:19 2005
20: A0801001 Sat Dec 31 00:00:07 2005
21: A0801002 Sat Dec 31 00:00:00 2005
22: A0801002 Sat Dec 31 00:00:00 2005
23: A0801002 Sat Dec 31 00:00:00 2005
24: A0801002 Fri Dec 31 23:59:59 1999
25: A0801002 Sat Dec 31 00:00:00 2005
26: A0801002 Fri Dec 31 23:59:59 1999
27: A0221002 Fri Dec 31 23:59:59 1999
28: A0231002 Fri Dec 31 23:59:59 1999
29: A0801004 Sat Dec 31 00:31:04 2005
30: A0801001 Sat Dec 31 00:00:03 2005
31: A0801001 Sat Dec 31 00:01:45 2005
32: FFFFFFFF Sat Dec 31 01:57:06 2005

Upon checking it seems it's still a caps issue and the AV Encoder chip? I've been using HDMI cables ever since so I don't know if that AV error will still affect it. As for the caps, by chance am I using faulty ones? Or is it normal for caps error appear even after replacing them since the values don't necessarily match? Hope someone can help me understand it more, I'm very new to this.

Thanks in advance!
Click to expand...
Yes it is very normal to get capacitor issues "after" replacing the NEC Tokins.

Because the original NEC Tokin capacitors were very high performance in the first place. If you remove them, it is hard to match their electrical parameters with something different even today.

You need something that is high quality and very low ESR in order to be comparable to the original.

Thats why is not always advisable to remove them.
Adding more in parallel can decrease the combined ESR but without oscilloscope is hard to see when things are actually improving or getting worse, or barely working.

You should be able to get it working in the end though, even if you dont get something as good as the original, there is some margin for it to be good enough.
 
Pacorretaco said:
Yes it is very normal to get capacitor issues "after" replacing the NEC Tokins.

Because the original NEC Tokin capacitors were very high performance in the first place. If you remove them, it is hard to match their electrical parameters with something different even today.

You need something that is high quality and very low ESR in order to be comparable to the original.

Thats why is not always advisable to remove them.
Adding more in parallel can decrease the combined ESR but without oscilloscope is hard to see when things are actually improving or getting worse, or barely working.

You should be able to get it working in the end though, even if you dont get something as good as the original, there is some margin for it to be good enough.
Click to expand...

Thanks for the info, really appreciate it. So the PS3 shutting down while playing NBA is still a Capacitor issue? And to resolve I would need to upgrade to higher quality capacitors? Any recommended place to get them then?

Also, if I replace them to higher quality capacitors, should the Capacitor codes be gone from Syscon?
 
RIP-Felix said:
It could be something simpler tho. So you want to check all the easier stuff first. Voltages, fuses, software resets, rebuilding the database, etc.
Click to expand...

It's been a bit since I've looked at the console. Been kinda busy, not enough time to dedicate to it.

What do you mean by software resets? Every time I try to lookup your suggestions in google I don't seem to get quite the right thing. My GoogleFu is lacking it seems. I remember trying to rebuild the DB, didn't seem to actually do that. One thing I thought was weird is that the console shut itself off after 30 seconds or so with no error light and no syscon error messages. I don't think that's normal behavior?

Which voltages are you referring to? I've been looking through your READ THIS link in your signature but I haven't been able to find what I'm looking for. Also tried looking around the PSDev Wiki for anything that might be helpful to no avail.

Also I didn't do much with the Southbridge UART. Sounded like Vyktor never ended up using it. I certainly don't have the brain space for that right now.
 
#3

sqRv9Ow.jpg
 
Hello, I have a CECHA01 that has the YLOD, the only service done to the system was an RMA to Sony back in 2008. I got a few readouts from the syscon, all of the errors in the log were 1601 and 1701.

I skimmed over a decent number of pages in this thread, but didn't come to a good conclusion, is this a code that could be resolved by a NEC token swap? or is the 1601 more a sign of a cpu/rsx failure where the solution would be a reball?

I'd be willing to give the token change a chance on my own, but wouldn't want to reflow/reball on my own and I would love to try my best to not ruin a savable system.

errlog
ofst[ 0]:err_code:0xa0801601, clock:0xffffffff
ofst[ 4]:err_code:0xa0801701, clock:0x19e7cdbb 2013/10/09 08:18:03
ofst[ 8]:err_code:0xa0801601, clock:0x19e7cdbb 2013/10/09 08:18:03
ofst[ 12]:err_code:0xa0801701, clock:0x19e89868 2013/10/09 22:42:48
ofst[ 16]:err_code:0xa0801601, clock:0x19e89868 2013/10/09 22:42:48
ofst[ 20]:err_code:0xa0801701, clock:0x19e898a0 2013/10/09 22:43:44
ofst[ 24]:err_code:0xa0801701, clock:0x19e89d83 2013/10/09 23:04:35
ofst[ 28]:err_code:0xa0801701, clock:0x19e89d98 2013/10/09 23:04:56
ofst[ 32]:err_code:0xa0801701, clock:0x19e89db1 2013/10/09 23:05:21
ofst[ 36]:err_code:0xa0801701, clock:0x19e8c6b9 2013/10/10 02:00:25
ofst[ 40]:err_code:0xa0801701, clock:0x19e8c6e4 2013/10/10 02:01:08
ofst[ 44]:err_code:0xa0801701, clock:0x19e8c743 2013/10/10 02:02:43
ofst[ 48]:err_code:0xa0801701, clock:0x19e8c772 2013/10/10 02:03:30
ofst[ 52]:err_code:0xa0801701, clock:0x19e8c77f 2013/10/10 02:03:43
ofst[ 56]:err_code:0xa0801004, clock:0x19e8c8c9 2013/10/10 02:09:13
ofst[ 60]:err_code:0xa0801001, clock:0x19e8c8d2 2013/10/10 02:09:22
ofst[ 64]:err_code:0xa0801701, clock:0x19e8c8d8 2013/10/10 02:09:28
ofst[ 68]:err_code:0xa0801701, clock:0x19e8c8df 2013/10/10 02:09:35
ofst[ 72]:err_code:0xa0801701, clock:0x19e8c9dd 2013/10/10 02:13:49
ofst[ 76]:err_code:0xa0801701, clock:0x19e8c9e5 2013/10/10 02:13:57
ofst[ 80]:err_code:0xa0801701, clock:0x19e8cb9b 2013/10/10 02:21:15
ofst[ 84]:err_code:0xa0801701, clock:0x19f3a353 2013/10/18 07:44:19
ofst[ 88]:err_code:0xa0801601, clock:0x19f3a353 2013/10/18 07:44:19
ofst[ 92]:err_code:0xa0801001, clock:0x19f63d9a 2013/10/20 07:07:06
ofst[ 96]:err_code:0xa0801701, clock:0x19f63e5c 2013/10/20 07:10:20
ofst[100]:err_code:0xa0801601, clock:0x19f63e5c 2013/10/20 07:10:20
ofst[104]:err_code:0xa0801701, clock:0x19f7a8f4 2013/10/21 08:57:24
ofst[108]:err_code:0xa0801701, clock:0x26806edb 2020/06/20 06:53:15
ofst[112]:err_code:0xa0801701, clock:0x26806ef7 2020/06/20 06:53:43
ofst[116]:err_code:0xa0801701, clock:0x26806fbd 2020/06/20 06:57:01
ofst[120]:err_code:0xa0801701, clock:0x29dfb17c 2022/04/06 02:03:40
ofst[124]:err_code:0xa0801701, clock:0x29dfb1ca 2022/04/06 02:04:58
bringup - I ran this with the power supply only plugged in to the mobo via the cable, so the rails on the board were disconnected, I read that can be the cause of a 3001.
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0003001
[ERROR]: 0xa0003001
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
becount
Bringup : 2443 times
Shutdown: 2379 times
Power-on: 147day 08hour 11min 39sec
 
Hi there :)

Today I've got a FAT CokC12. Case looks very good, still sealed. Seems the BR drive is faulty, it recognizes disks but the TV shows a spinning drive symbol at the top/right. I used the bgtoolset to patch and did an update from OFW 4.83 to Rebug 4.86 lite.

Bringup Count: 2075, Shutdown Count: 1900
Runtime: 136 Days, 18 Hours, 3 Minutes, 51 Seconds
01: A0801001 Wed Mar 23 11:32:47 2022
02: A08014FF Wed Mar 23 11:32:47 2022
03: A0801001 Thu Nov 1 00:00:38 2018
04: A0801001 Fri Nov 17 16:36:29 2017
05: A0801004 Mon Nov 21 22:10:02 2016
06: A0801004 Wed Jun 29 14:01:19 2016
07: A0801001 Mon Feb 8 19:33:19 2016
08: A0801001 Wed Sep 23 16:22:21 2015
09: A08014FF Wed Sep 23 16:22:21 2015
10: A0801701 Wed Sep 23 16:22:21 2015
11: A0801001 Sat May 16 16:16:02 2015
12: A0801001 Thu Jan 22 16:45:09 2015
13: A0801001 Tue Jan 13 20:52:46 2015
14: A0801001 Tue Jan 13 20:46:48 2015
15: A0801001 Mon Jan 12 17:38:26 2015
16: A0801004 Wed Dec 31 01:44:01 2014
17: A0801001 Mon Dec 29 11:14:44 2014
18: A0801001 Sat Dec 27 14:36:23 2014
19: A0801004 Tue Dec 9 21:33:24 2014
20: A0801004 Sat Dec 6 15:22:57 2014
21: A0801004 Fri Dec 5 21:20:04 2014
22: A0801001 Thu Dec 4 17:44:28 2014
23: A0801004 Wed Dec 3 20:09:28 2014
24: A0801004 Sun Nov 30 20:52:12 2014
25: A0801004 Mon Oct 27 16:33:46 2014
26: A0801004 Mon Oct 27 16:12:17 2014
27: A0801001 Wed Jun 18 11:59:31 2014
28: A08014FF Wed Jun 18 11:59:31 2014
29: A0801004 Mon Apr 28 13:35:03 2014
30: A0801001 Fri Oct 25 14:48:23 2013
31: A0801001 Sun Oct 6 14:39:24 2013
32: FFFFFFFF Sun Dec 30 15:50:43 2012

01: A0801001 Wed Mar 23 11:32:47 2022
02: A08014FF Wed Mar 23 11:32:47 2022
03: A0801001 Thu Nov 1 00:00:38 2018
04: A0801001 Fri Nov 17 16:36:29 2017
05: A0801004 Mon Nov 21 22:10:02 2016
06: A0801004 Wed Jun 29 14:01:19 2016
07: A0801001 Mon Feb 8 19:33:19 2016
08: A0801001 Wed Sep 23 16:22:21 2015
09: A08014FF Wed Sep 23 16:22:21 2015
10: A0801701 Wed Sep 23 16:22:21 2015
11: A0801001 Sat May 16 16:16:02 2015
12: A0801001 Thu Jan 22 16:45:09 2015
13: A0801001 Tue Jan 13 20:52:46 2015
14: A0801001 Tue Jan 13 20:46:48 2015
15: A0801001 Mon Jan 12 17:38:26 2015
16: A0801004 Wed Dec 31 01:44:01 2014
17: A0801001 Mon Dec 29 11:14:44 2014
18: A0801001 Sat Dec 27 14:36:23 2014
19: A0801004 Tue Dec 9 21:33:24 2014
20: A0801004 Sat Dec 6 15:22:57 2014
21: A0801004 Fri Dec 5 21:20:04 2014
22: A0801001 Thu Dec 4 17:44:28 2014
23: A0801004 Wed Dec 3 20:09:28 2014
24: A0801004 Sun Nov 30 20:52:12 2014
25: A0801004 Mon Oct 27 16:33:46 2014
26: A0801004 Mon Oct 27 16:12:17 2014
27: A0801001 Wed Jun 18 11:59:31 2014
28: A08014FF Wed Jun 18 11:59:31 2014
29: A0801004 Mon Apr 28 13:35:03 2014
30: A0801001 Fri Oct 25 14:48:23 2013
31: A0801001 Sun Oct 6 14:39:24 2013
32: FFFFFFFF Sun Dec 30 15:50:43 2012

I wonder if those errors tell me something about the console, without to know or to see symptoms?

I've searched this thread and it seems that 1001 and 1004 doesn't tell much, could be nothing, isn't it?
What is about the 1701 14FF 1001 combination? Something to worry about? Any insight, hint or opinion, please?:)

Best regards :)
 
St3v3b82 said:
Hi there :)

Today I've got a FAT CokC12. Case looks very good, still sealed. Seems the BR drive is faulty, it recognizes disks but the TV shows a spinning drive symbol at the top/right. I used the bgtoolset to patch and did an update from OFW 4.83 to Rebug 4.86 lite.

Bringup Count: 2075, Shutdown Count: 1900
Runtime: 136 Days, 18 Hours, 3 Minutes, 51 Seconds
01: A0801001 Wed Mar 23 11:32:47 2022
02: A08014FF Wed Mar 23 11:32:47 2022
03: A0801001 Thu Nov 1 00:00:38 2018
04: A0801001 Fri Nov 17 16:36:29 2017
05: A0801004 Mon Nov 21 22:10:02 2016
06: A0801004 Wed Jun 29 14:01:19 2016
07: A0801001 Mon Feb 8 19:33:19 2016
08: A0801001 Wed Sep 23 16:22:21 2015
09: A08014FF Wed Sep 23 16:22:21 2015
10: A0801701 Wed Sep 23 16:22:21 2015
11: A0801001 Sat May 16 16:16:02 2015
12: A0801001 Thu Jan 22 16:45:09 2015
13: A0801001 Tue Jan 13 20:52:46 2015
14: A0801001 Tue Jan 13 20:46:48 2015
15: A0801001 Mon Jan 12 17:38:26 2015
16: A0801004 Wed Dec 31 01:44:01 2014
17: A0801001 Mon Dec 29 11:14:44 2014
18: A0801001 Sat Dec 27 14:36:23 2014
19: A0801004 Tue Dec 9 21:33:24 2014
20: A0801004 Sat Dec 6 15:22:57 2014
21: A0801004 Fri Dec 5 21:20:04 2014
22: A0801001 Thu Dec 4 17:44:28 2014
23: A0801004 Wed Dec 3 20:09:28 2014
24: A0801004 Sun Nov 30 20:52:12 2014
25: A0801004 Mon Oct 27 16:33:46 2014
26: A0801004 Mon Oct 27 16:12:17 2014
27: A0801001 Wed Jun 18 11:59:31 2014
28: A08014FF Wed Jun 18 11:59:31 2014
29: A0801004 Mon Apr 28 13:35:03 2014
30: A0801001 Fri Oct 25 14:48:23 2013
31: A0801001 Sun Oct 6 14:39:24 2013
32: FFFFFFFF Sun Dec 30 15:50:43 2012

01: A0801001 Wed Mar 23 11:32:47 2022
02: A08014FF Wed Mar 23 11:32:47 2022
03: A0801001 Thu Nov 1 00:00:38 2018
04: A0801001 Fri Nov 17 16:36:29 2017
05: A0801004 Mon Nov 21 22:10:02 2016
06: A0801004 Wed Jun 29 14:01:19 2016
07: A0801001 Mon Feb 8 19:33:19 2016
08: A0801001 Wed Sep 23 16:22:21 2015
09: A08014FF Wed Sep 23 16:22:21 2015
10: A0801701 Wed Sep 23 16:22:21 2015
11: A0801001 Sat May 16 16:16:02 2015
12: A0801001 Thu Jan 22 16:45:09 2015
13: A0801001 Tue Jan 13 20:52:46 2015
14: A0801001 Tue Jan 13 20:46:48 2015
15: A0801001 Mon Jan 12 17:38:26 2015
16: A0801004 Wed Dec 31 01:44:01 2014
17: A0801001 Mon Dec 29 11:14:44 2014
18: A0801001 Sat Dec 27 14:36:23 2014
19: A0801004 Tue Dec 9 21:33:24 2014
20: A0801004 Sat Dec 6 15:22:57 2014
21: A0801004 Fri Dec 5 21:20:04 2014
22: A0801001 Thu Dec 4 17:44:28 2014
23: A0801004 Wed Dec 3 20:09:28 2014
24: A0801004 Sun Nov 30 20:52:12 2014
25: A0801004 Mon Oct 27 16:33:46 2014
26: A0801004 Mon Oct 27 16:12:17 2014
27: A0801001 Wed Jun 18 11:59:31 2014
28: A08014FF Wed Jun 18 11:59:31 2014
29: A0801004 Mon Apr 28 13:35:03 2014
30: A0801001 Fri Oct 25 14:48:23 2013
31: A0801001 Sun Oct 6 14:39:24 2013
32: FFFFFFFF Sun Dec 30 15:50:43 2012

I wonder if those errors tell me something about the console, without to know or to see symptoms?

I've searched this thread and it seems that 1001 and 1004 doesn't tell much, could be nothing, isn't it?
What is about the 1701 14FF 1001 combination? Something to worry about? Any insight, hint or opinion, please?:)

Best regards :)
Click to expand...

Here bro, is the link where you can define the Syscon error codes:-
https://www.psdevwiki.com/ps3/Syscon_Error_Codes

Error code 1001: says it's usually the NEC / Tokins on the CELL

Error code 1004: says "Power Supply"

Error code 1701: says "CELL attention"

Error code 14FF: says "Check stop"
 
You must log in or register to reply here.

Similar threads

Back
Top