help to find root cause of ps3 shutdown

I

i5han

Member
Hi Everyone

I have a ps3 cecha01. firmware is evilnat 4.89. webman mod installed. I keep the system on standby power always. a crucial mx500 1Tb SSD is installed.

When I turn it on for the first time in a given day it turns on goes to the xmb and shuts down within a minute with a couple of beeps. The red indicator keeps flashing. when I press the power button again it shuts down and the red light indicator is lit constantly. When I turn it back on the system does the standard unsafe shutdown warning, does a scan, and then boots normally. I can then use the system for a couple of hours without an issue. If I turn it off and on again it works normally as well.

The temperatures seem to be normal, around 70 for CPU and GPU. There is nothing on the syscon error logs.

Is there a way I could troubleshoot to find out the cause for this shutdowns?
 
Yes, they will show up on syscon.
Did you read the codes? if not search for a pkg called "PS3 advanced tools" and dump your flash syscon log to your usb flash. it only takes 2 seconds...and will return to smb when finished.
 
Last edited:
i5han said:
Hi Everyone

I have a ps3 cecha01. firmware is evilnat 4.89. webman mod installed. I keep the system on standby power always. a crucial mx500 1Tb SSD is installed.

When I turn it on for the first time in a given day it turns on goes to the xmb and shuts down within a minute with a couple of beeps. The red indicator keeps flashing. when I press the power button again it shuts down and the red light indicator is lit constantly. When I turn it back on the system does the standard unsafe shutdown warning, does a scan, and then boots normally. I can then use the system for a couple of hours without an issue. If I turn it off and on again it works normally as well.

The temperatures seem to be normal, around 70 for CPU and GPU. There is nothing on the syscon error logs.

Is there a way I could troubleshoot to find out the cause for this shutdowns?
Click to expand...
Taking advantage of the fact that the console is still able to turn on, I recommend that you extract the error codes from the syscom, so you can better understand what is causing this defect. I recorded a video about it, but in Portuguese, maybe you understand something, or look for a topic or video with the theme "syscom error log"

 
If the console stops working, you will only be able to obtain this information using the "USB UART" method, and for that you will need to open the console and perform some soldering points on the motherboard.
I recently acquired 2 PS3 FAT CECHE consoles, and none of the 2 came back working after replacing the capacitors.
 
I did a dump of the syscon log with the dump tools on the evilnat firmware. I see some error codes but they are from 2006. bought this from ebay. This the contents of the file


Code: 
Firmware Version: 4.89 (build 50740)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)

Bringup Count: 1420, Shutdown Count: 1277
Runtime: 210 Days, 17 Hours, 16 Minutes, 31 Seconds

Error Log
01: A0801002  Thu Jul 20 20:56:49 2006
02: A0801002  Thu Jul 20 20:53:47 2006
03: A0801002  Thu Jul 20 20:08:29 2006
04: A0801002  Tue Jul 18 17:31:01 2006
05: A0901001  Fri Jul 14 14:42:08 2006
06: A0801002  Fri Jul 14 14:39:46 2006
07: A0801002  Thu Jul 13 17:49:33 2006
08: A0801002  Thu Jul 13 17:36:52 2006
09: A0801002  Tue Jul 11 13:31:46 2006
10: A0801002  Tue Jul 11 13:17:58 2006
11: A0901001  Thu Jun 29 10:08:49 2006
12: A0801002  Wed Jun 28 19:24:00 2006
13: A0901001  Fri Jun 23 17:27:34 2006
14: A0901001  Sun Jun 18 18:42:25 2006
15: A0801002  Sun Jun 18 18:30:40 2006
16: A0801002  Sat Jun 17 13:29:58 2006
17: A0801002  Sat Jun 17 13:27:05 2006
18: A0801002  Fri Apr 21 21:51:40 2006
19: A0901001  Fri Apr 21 11:09:50 2006
20: A0801002  Thu Apr 20 16:51:10 2006
21: A0901001  Wed Apr 12 06:07:29 2006
22: A0801002  Tue Apr 11 20:31:04 2006
23: A0801002  Mon Apr 10 20:58:16 2006
24: A0801002  Mon Apr 10 20:12:40 2006
25: A0801002  Mon Apr 10 19:07:36 2006
26: A0801002  Mon Apr 10 18:46:26 2006
27: A0801002  Mon Apr 10 18:41:24 2006
28: A0801002  Mon Apr 10 18:12:12 2006
29: A0801002  Thu Apr  6 20:23:01 2006
30: A0801002  Thu Apr  6 20:19:48 2006
31: A0801002  Wed Mar 15 20:58:08 2006
32: FFFFFFFF  Wed Mar 15 20:56:00 2006
 
i5han said:
I did a dump of the syscon log with the dump tools on the evilnat firmware. I see some error codes but they are from 2006. bought this from ebay. This the contents of the file


Code: 
Firmware Version: 4.89 (build 50740)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)

Bringup Count: 1420, Shutdown Count: 1277
Runtime: 210 Days, 17 Hours, 16 Minutes, 31 Seconds

Error Log
01: A0801002  Thu Jul 20 20:56:49 2006
02: A0801002  Thu Jul 20 20:53:47 2006
03: A0801002  Thu Jul 20 20:08:29 2006
04: A0801002  Tue Jul 18 17:31:01 2006
05: A0901001  Fri Jul 14 14:42:08 2006
06: A0801002  Fri Jul 14 14:39:46 2006
07: A0801002  Thu Jul 13 17:49:33 2006
08: A0801002  Thu Jul 13 17:36:52 2006
09: A0801002  Tue Jul 11 13:31:46 2006
10: A0801002  Tue Jul 11 13:17:58 2006
11: A0901001  Thu Jun 29 10:08:49 2006
12: A0801002  Wed Jun 28 19:24:00 2006
13: A0901001  Fri Jun 23 17:27:34 2006
14: A0901001  Sun Jun 18 18:42:25 2006
15: A0801002  Sun Jun 18 18:30:40 2006
16: A0801002  Sat Jun 17 13:29:58 2006
17: A0801002  Sat Jun 17 13:27:05 2006
18: A0801002  Fri Apr 21 21:51:40 2006
19: A0901001  Fri Apr 21 11:09:50 2006
20: A0801002  Thu Apr 20 16:51:10 2006
21: A0901001  Wed Apr 12 06:07:29 2006
22: A0801002  Tue Apr 11 20:31:04 2006
23: A0801002  Mon Apr 10 20:58:16 2006
24: A0801002  Mon Apr 10 20:12:40 2006
25: A0801002  Mon Apr 10 19:07:36 2006
26: A0801002  Mon Apr 10 18:46:26 2006
27: A0801002  Mon Apr 10 18:41:24 2006
28: A0801002  Mon Apr 10 18:12:12 2006
29: A0801002  Thu Apr  6 20:23:01 2006
30: A0801002  Thu Apr  6 20:19:48 2006
31: A0801002  Wed Mar 15 20:58:08 2006
32: FFFFFFFF  Wed Mar 15 20:56:00 2006
Click to expand...

Forget the date.
Yes confirmed bad tokins!
Error A0801002 RSX bad tokins

Error A0801001 CELL bad tokins, or could simply mean the console wasn't shut off properly.

Buy 16 tatalum capacitors 470uf
Change them! and problem solved
 
Last edited:
i5han said:
I did a dump of the syscon log with the dump tools on the evilnat firmware. I see some error codes but they are from 2006. bought this from ebay. This the contents of the file


Code: 
Firmware Version: 4.89 (build 50740)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)

Bringup Count: 1420, Shutdown Count: 1277
Runtime: 210 Days, 17 Hours, 16 Minutes, 31 Seconds

Error Log
01: A0801002  Thu Jul 20 20:56:49 2006
02: A0801002  Thu Jul 20 20:53:47 2006
03: A0801002  Thu Jul 20 20:08:29 2006
04: A0801002  Tue Jul 18 17:31:01 2006
05: A0901001  Fri Jul 14 14:42:08 2006
06: A0801002  Fri Jul 14 14:39:46 2006
07: A0801002  Thu Jul 13 17:49:33 2006
08: A0801002  Thu Jul 13 17:36:52 2006
09: A0801002  Tue Jul 11 13:31:46 2006
10: A0801002  Tue Jul 11 13:17:58 2006
11: A0901001  Thu Jun 29 10:08:49 2006
12: A0801002  Wed Jun 28 19:24:00 2006
13: A0901001  Fri Jun 23 17:27:34 2006
14: A0901001  Sun Jun 18 18:42:25 2006
15: A0801002  Sun Jun 18 18:30:40 2006
16: A0801002  Sat Jun 17 13:29:58 2006
17: A0801002  Sat Jun 17 13:27:05 2006
18: A0801002  Fri Apr 21 21:51:40 2006
19: A0901001  Fri Apr 21 11:09:50 2006
20: A0801002  Thu Apr 20 16:51:10 2006
21: A0901001  Wed Apr 12 06:07:29 2006
22: A0801002  Tue Apr 11 20:31:04 2006
23: A0801002  Mon Apr 10 20:58:16 2006
24: A0801002  Mon Apr 10 20:12:40 2006
25: A0801002  Mon Apr 10 19:07:36 2006
26: A0801002  Mon Apr 10 18:46:26 2006
27: A0801002  Mon Apr 10 18:41:24 2006
28: A0801002  Mon Apr 10 18:12:12 2006
29: A0801002  Thu Apr  6 20:23:01 2006
30: A0801002  Thu Apr  6 20:19:48 2006
31: A0801002  Wed Mar 15 20:58:08 2006
32: FFFFFFFF  Wed Mar 15 20:56:00 2006
Click to expand...
At least no serious errors were detected. Apparently the defect must be only in the NEC/TOKIN. Errors like 3034 yes can represent reballing.
 
I prefer not to mess around with nec/tokins unless I'm 100% sure about it. Is there anything i can do to rule out a software issue?
 
I have for example enabled dev_blind to write a different ps1_rom.bin.

question 1 could this cause an issue?
Question 2 would this be reset if i reinstall the firmware
 
1 - No
2 . No, Its not a software issue, that capacitors are out of spec.

You or someone has to do that job. I had same error, and same sympthoms, after I replaced them the problem never returned.
 
So after careful consideration im not going to solder anything. I did the advanced tools thing and only got FFFFFF error codes. After much googing I found out that activision did an update for pcs in March of 2023 and I'm assuming it's a server side thing blocking me as i also tried using the disc version with all applicable updates. Unless it some rare instance of me having a new account as i forgot my other accounts password or some strange evilnat bug as i couldnt install his cfw over ofw 3.55 but had to update to an old ferro cfw and then his. Thank you for all the replies
 
You must log in or register to reply here.

Similar threads

Back
Top