PS3-HW Hardware Questions/Issues? - Post Syscon Logs/details here

Reviving PS3 from the flea market
.Hey guys, first of all, congratulations and thank you for this incredible community you've built on PS3. It's truly amazing.

Lately I've been very interested in delving into the world of the PS3, especially the Fat version, because I find everything that's been discovered about the yellow light and the many problems it brings very interesting.

Okay, let's begin. A couple of months ago, I got a PS3 Fat at a flea market for a ridiculously low price. I brought it home and tested it. As expected, it had the famous yellow light of death. I proceeded to completely disassemble it, and to my surprise, the console didn't look too bad internally; it was just very, very dirty. It's also important to mention that it looked like it had never been disassembled before, as it had a warranty seal and factory thermal paste.

For all of this, it's a PS3 Fat model CECHG01 with a SEM-001 motherboard, 65nm CELL, and 90nm RSX, manufactured in September 2007.

My journey of pain begins here. After performing the necessary maintenance, I tested it again, and as expected, the error code was still there. I installed SYSCON to see what errors it was throwing and how much lifespan it had, and I found the following.

Error log:
Code:
errlog
ofst[ 56]:err_code:0xffffffff, clock:0x27b8896f  2021/02/12 00:33:51
ofst[ 60]:err_code:0xa0403034, clock:0x27b8896f  2021/02/12 00:33:51
ofst[ 64]:err_code:0xa0404422, clock:0x27b8b96e  2021/02/12 03:58:38
ofst[ 68]:err_code:0xa0403034, clock:0x27b8b96e  2021/02/12 03:58:38
ofst[ 72]:err_code:0xa0404422, clock:0x27b8b97a  2021/02/12 03:58:50
ofst[ 76]:err_code:0xa0403034, clock:0x27b8b97a  2021/02/12 03:58:50
ofst[ 80]:err_code:0xa0404422, clock:0x27b8b987  2021/02/12 03:59:03
ofst[ 84]:err_code:0xa0403034, clock:0x27b8b987  2021/02/12 03:59:03
ofst[ 88]:err_code:0xa0404422, clock:0x27b8b992  2021/02/12 03:59:14
ofst[ 92]:err_code:0xa0403034, clock:0x27b8b992  2021/02/12 03:59:14
ofst[ 96]:err_code:0xa0404422, clock:0x2f345c3f  2025/02/04 05:03:59
ofst[100]:err_code:0xa0403034, clock:0x2f345c3f  2025/02/04 05:03:59
ofst[104]:err_code:0xa0404422, clock:0x2f345c67  2025/02/04 05:04:39
ofst[108]:err_code:0xa0403034, clock:0x2f345c67  2025/02/04 05:04:39
ofst[112]:err_code:0xa0404422, clock:0x2f345c83  2025/02/04 05:05:07
ofst[116]:err_code:0xa0403034, clock:0x2f345c83  2025/02/04 05:05:07
ofst[120]:err_code:0xa0404422, clock:0x2f652909  2025/03/13 05:26:33
ofst[124]:err_code:0xa0403034, clock:0x2f652909  2025/03/13 05:26:33
ofst[  0]:err_code:0xa0404422, clock:0x2f652916  2025/03/13 05:26:46
ofst[  4]:err_code:0xa0403034, clock:0x2f652916  2025/03/13 05:26:46
ofst[  8]:err_code:0xa0404422, clock:0x2f652920  2025/03/13 05:26:56
ofst[ 12]:err_code:0xa0403034, clock:0x2f652920  2025/03/13 05:26:56
ofst[ 16]:err_code:0xa0404422, clock:0x2f652932  2025/03/13 05:27:14
ofst[ 20]:err_code:0xa0403034, clock:0x2f652932  2025/03/13 05:27:14
ofst[ 24]:err_code:0xa0404422, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404422, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0404422, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0404422, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
[mullion]$

Usage time:
Code:
becount
Bringup : 1458 times
Shutdown: 1243 times
Power-on: 75day 04hour 04min 05sec
[mullion]$

Startup sequence:
Code:
bringup
[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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7

As you can see, the error codes are 3034 and 4422. The usage time is just over 75 days, and I can't interpret the startup sequence, but I'm posting it in case anyone sees something that might be helpful.

According to the PS3 wiki, errors 3034 and 4422 are problems related to the processor or graphics chip, specifically problems with the BGA solder. Possible solutions are reballing or reflow. I opted for reflow because I don't have a stencil or the right tool for reballing.

I applied heat to the RSX and CELL chips at approximately 210° Celsius (410° Fahrenheit) for approximately 2.5 minutes, moving constantly to avoid concentrating the heat in one spot. I added a little flux around both chips (the flux I used was MG Chemicals 8341). I also used aluminum foil to try to prevent other components from being exposed to the heat.

After completing this process and reassembling the console for testing, the console behaves slightly differently, turning the fan on and off almost immediately, displaying a yellow light again. I checked the error log again to see if the error I was getting now was different, and yes, the error I was getting now was different.

Error log after reflow on CPU and GPU:
Code:
errlog
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xa0404422, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404422, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404422, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404422, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0801200, clock:0xffffffff
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0902203, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902120, clock:0xffffffff
ofst[112]:err_code:0xa0801200, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0902203, clock:0xffffffff
ofst[  4]:err_code:0xa0902120, clock:0xffffffff
ofst[  8]:err_code:0xa0902203, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0902203, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0902203, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
[mullion]$

After this, I couldn't extract the date, and all the logs were showing no date.

As you can see, the errors are now 2203 and 1200. Error 2203 refers to the south bridge, and error 1200 refers to a thermal problem with the CELL.

To try to fix this, and I don't know if it makes much sense or not, I reflowed the south bridge. Maybe what I should have done before was check the card for a short or something like that, but as I said before, I'm not very familiar with PS3 hardware yet, so the easiest thing for me was to reflow it again.

After this reflow, the yellow light remained, but the console's behavior was identical to the initial one. I mean, the fan no longer started and was sending a yellow light almost immediately.

I used SYSCON again, and now the results were as follows.

Error log after the south bridge reflow:
Code:
errlog
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xa0801200, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0902203, clock:0xffffffff
ofst[  4]:err_code:0xa0902120, clock:0xffffffff
ofst[  8]:err_code:0xa0902203, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0902203, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0902203, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
ofst[ 52]:err_code:0xa0801200, clock:0xffffffff
ofst[ 56]:err_code:0xa0902203, clock:0xffffffff
ofst[ 60]:err_code:0xa0801200, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0093003, clock:0xffffffff
ofst[ 72]:err_code:0xa0022110, clock:0xffffffff
ofst[ 76]:err_code:0xa0022110, clock:0xffffffff
ofst[ 80]:err_code:0xa0093003, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0093003, clock:0xffffffff
ofst[ 96]:err_code:0xa0093003, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0093003, clock:0xffffffff
[mullion]$

Now the error is 3003 and 2110, although 2110 hasn't appeared in the latest logs. 2110 refers to a clock subsystem issue. It's said it could be a 5V line issue or a shorted fuse F6001. I checked the fuse and found it to be good.

Error 3003 indicates a problem with the processor's power supply and suggests a possible problem with the NEC/TOKIN chips. I checked all the NEC/TOKIN chips by removing the plastic cover and found at least two had some kind of oxidation. I'm planning on using Rip Felix's Tantalizer mod to try to revive the console... But based on your experience, and this is why I'm seeking your help, do you think the NEC/TOKIN chips are causing this problem? Or maybe I ruined something by applying heat to the card? I was careful when reflowing the chip and I'm pretty sure there's no delamination.

Something important to mention that I was forgetting to mention is that I checked all the fuses, and fuse F6002 was open. I replaced it, but nothing changed; the problem was still exactly the same.

Any ideas or advice on what I can do? These last errors I've been getting are actually a bit strange, and I haven't found much information about them. By the way, I'm documenting everything and plan to upload a video about it showing everything I've said above in a much more graphic way. As soon as I have the audiovisual material ready, I'll attach it to this post if it's not a problem.

Great forum and community. I've honestly found a lot of information here. Thanks for sharing so much, guys :)

Hola chicos, antes que nada felicitarlos y agradecerles por esta increible comunidad que han construido sobre PS3, en verdad es asombrosa.

Ultimamente eh estado muy interesado por adentrarme en el mundo de la PS3, en especial de la versión Fat porque me parece muy interesante todo lo que se ha descubierto alrededor de la luz amarilla y los múltiples problemas que esto trae.

Bien, comencemos. Hace un par de meses conseguí una PS3 fat en un tianguis a un precio ridículo, la traje a casa y la probe, como era de esperarse tenía la famosa luz amarilla de la muerte. Procedí a desarmarla completamente y para mi sorpresa la consola internamente no se veía tan mal, solo estaba muy muy sucia, también es importante mencionar que parecía nunca antes haber sido desarmada ya que traía sello de garantía y la pasta térmica de fábrica.

Para todo esto se trata de una PS3 fat modelo CECHG01 con placa SEM-001, CELL de 65nm y RSX de 90nm, fabricada en septiembre de 2007.

Mi camino de dolor comienza aquí. Después de darle el mantenimiento pertinente la probe de nuevo y como era de esperarse la ylod seguía ahí. Instale SYSCON para ver cuales errores me arrojaba y cuánto tiempo de vida ya tenía recorrido y me encontré con lo siguiente.

Error log:
Code:
errlog
ofst[ 56]:err_code:0xffffffff, clock:0x27b8896f  2021/02/12 00:33:51
ofst[ 60]:err_code:0xa0403034, clock:0x27b8896f  2021/02/12 00:33:51
ofst[ 64]:err_code:0xa0404422, clock:0x27b8b96e  2021/02/12 03:58:38
ofst[ 68]:err_code:0xa0403034, clock:0x27b8b96e  2021/02/12 03:58:38
ofst[ 72]:err_code:0xa0404422, clock:0x27b8b97a  2021/02/12 03:58:50
ofst[ 76]:err_code:0xa0403034, clock:0x27b8b97a  2021/02/12 03:58:50
ofst[ 80]:err_code:0xa0404422, clock:0x27b8b987  2021/02/12 03:59:03
ofst[ 84]:err_code:0xa0403034, clock:0x27b8b987  2021/02/12 03:59:03
ofst[ 88]:err_code:0xa0404422, clock:0x27b8b992  2021/02/12 03:59:14
ofst[ 92]:err_code:0xa0403034, clock:0x27b8b992  2021/02/12 03:59:14
ofst[ 96]:err_code:0xa0404422, clock:0x2f345c3f  2025/02/04 05:03:59
ofst[100]:err_code:0xa0403034, clock:0x2f345c3f  2025/02/04 05:03:59
ofst[104]:err_code:0xa0404422, clock:0x2f345c67  2025/02/04 05:04:39
ofst[108]:err_code:0xa0403034, clock:0x2f345c67  2025/02/04 05:04:39
ofst[112]:err_code:0xa0404422, clock:0x2f345c83  2025/02/04 05:05:07
ofst[116]:err_code:0xa0403034, clock:0x2f345c83  2025/02/04 05:05:07
ofst[120]:err_code:0xa0404422, clock:0x2f652909  2025/03/13 05:26:33
ofst[124]:err_code:0xa0403034, clock:0x2f652909  2025/03/13 05:26:33
ofst[  0]:err_code:0xa0404422, clock:0x2f652916  2025/03/13 05:26:46
ofst[  4]:err_code:0xa0403034, clock:0x2f652916  2025/03/13 05:26:46
ofst[  8]:err_code:0xa0404422, clock:0x2f652920  2025/03/13 05:26:56
ofst[ 12]:err_code:0xa0403034, clock:0x2f652920  2025/03/13 05:26:56
ofst[ 16]:err_code:0xa0404422, clock:0x2f652932  2025/03/13 05:27:14
ofst[ 20]:err_code:0xa0403034, clock:0x2f652932  2025/03/13 05:27:14
ofst[ 24]:err_code:0xa0404422, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404422, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0404422, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0404422, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
[mullion]$

Tiempo de uso:
Code:
becount
Bringup : 1458 times
Shutdown: 1243 times
Power-on: 75day 04hour 04min 05sec
[mullion]$

Secuencia de inicio:
Code:
bringup
[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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7

Como se puede ver los códigos de error son 3034 y 4422, el tiempo de usos son poco más de 75 días y la secuencia de inicio no la se interpretar, pero la pongo por si alguien ve algo que sea de ayuda.

Los errores 3034 y 4422 según la wiki de PS3 son problemas relacionados con el procesador o el chip gráfico, en específico problemas con la soldadura BGA. Las posibles soluciones son reballing o reflow, yo opte por reflow porque no tengo esténcil ni la herramienta adecuada para hacer reballing.

Aplique calor a los chips RSX y CELL a una temperatura aproximada de 210° Celsius (410° Fahrenheit) por un tiempo aproximado de 2 minutos y medio con movimientos constantes para no concentrar el calor en un solo punto y agregue un poco de flux alrededor de ambos chips (el flux que use fue el 8341 de MG Chemicals), también use papel aluminio para tratar de prevenir que otros componentes estuvieron expuestos al calor.

Al finalizar este proceso y armar de nuevo la consola para probarla la consola se comporta un poco diferente encendiendo el ventilar y apagándolo casi de inmediato y mandando luz amarilla de nuevo. Revise nuevamente el log de errores para ver si el error que ahora me daba seria diferente y si, el error que me daba ahora era otro.

Log de errores después de reflow en CPU yGPU:
Code:
errlog
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xa0404422, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404422, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404422, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404422, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0801200, clock:0xffffffff
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0902203, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902120, clock:0xffffffff
ofst[112]:err_code:0xa0801200, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0902203, clock:0xffffffff
ofst[  4]:err_code:0xa0902120, clock:0xffffffff
ofst[  8]:err_code:0xa0902203, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0902203, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0902203, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
[mullion]$

Después de esto la fecha ya no la pude extraer y todos los logs me los arrojaba sin ella.
Como se puede ver ahora los errores son 2203 y 1200. El error 2203 hace referencia al south bridge y el error 1200 a un problema térmico con el CELL.

Para intentar solucionar esto, y no sé si tenga mucho sentido o no, fue hacer reflow al sothbridge. Tal vez lo que tuve que haber hecho antes fue revisar la tarjeta en busca de algún corto o algo así pero como ya lo dije antes, no estoy muy familiarizado aun con el hadware de PS3 por eso lo más fácil para mí fue hacer reflow nuevamente.

Después de este reflow la luz amarilla continuo pero el comportamiento de la consola fue idéntico a la inicial, me refiero a que ya no iniciaba el ventilador y mandaba luz amarilla casi de inmediato.
Una vez más use el SYSCON y ahora los resultados fueron los siguientes.

Log de errores después del reflow en southbridge:
Code:
errlog
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xa0801200, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0902203, clock:0xffffffff
ofst[  0]:err_code:0xa0902203, clock:0xffffffff
ofst[  4]:err_code:0xa0902120, clock:0xffffffff
ofst[  8]:err_code:0xa0902203, clock:0xffffffff
ofst[ 12]:err_code:0xa0801200, clock:0xffffffff
ofst[ 16]:err_code:0xa0902203, clock:0xffffffff
ofst[ 20]:err_code:0xa0902203, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0902203, clock:0xffffffff
ofst[ 32]:err_code:0xa0902203, clock:0xffffffff
ofst[ 36]:err_code:0xa0801200, clock:0xffffffff
ofst[ 40]:err_code:0xa0902203, clock:0xffffffff
ofst[ 44]:err_code:0xa0902203, clock:0xffffffff
ofst[ 48]:err_code:0xa0902203, clock:0xffffffff
ofst[ 52]:err_code:0xa0801200, clock:0xffffffff
ofst[ 56]:err_code:0xa0902203, clock:0xffffffff
ofst[ 60]:err_code:0xa0801200, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0093003, clock:0xffffffff
ofst[ 72]:err_code:0xa0022110, clock:0xffffffff
ofst[ 76]:err_code:0xa0022110, clock:0xffffffff
ofst[ 80]:err_code:0xa0093003, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0093003, clock:0xffffffff
ofst[ 96]:err_code:0xa0093003, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0093003, clock:0xffffffff
[mullion]$

Ahora el error es 3003 y 2110, aunque 2110 no salto en los últimos registros. 2110 hace referencia a un problema del subsistema de reloj. Se dice que pudiera ser problema de la línea de 5v o el fusible F6001 en corto, verifiqué el fusible y lo encontré en buen estado.

El error 3003 indica un problema en la alimentación del procesador y se insinúa que pudiera ser posible un problema con los NEC/TOKIN. Revise todo los NEC/TOKIN retirando la tapa de plástico y encontré que por lo menos 2 presentaban algún tipo de oxidación. Tengo pensado usar el mod de Rip Felix Tantalizer para intentar revivir la consola... Pero según su experiencia y es por eso que busco ayuda con ustedes, ¿creen que los NEC/TOKIN sean los causantes de este problema? o tal vez al aplicarle calor a la tarjeta arruiné algo? fui cuidadoso al hacer el reflow y estoy muy seguro de que no hay delaminación.

Algo importante a mencionar que se me estaba olvidando es que revise todos los fusibles y el fusible F6002 estaba abierto, lo remplace, pero nada cambio, el problema seguía siendo exactamente el mismo.

¿Alguna idea o consejo de que puedo hacer? Realmente estos últimos errores que obtuve son algo raros y no eh encontrado mucha información sobre ellos. Por cierto, estoy documentando todo y tengo pensado subir un video al respecto mostrando todo lo anterior dicho de una forma mucho más gráfica, en cuanto tenga listo el material audiovisual lo adjuntare a este post si no es algún problema.

Muy buen foro y comunidad, sinceramente he encontrado mucha información aquí, gracias por compartir tanto chicos :) .
 
Last edited by a moderator:
My Ps3's Errlog
.
errlog

ofst[ 4]:err_code:0xffffffff, clock:0x256a9f0b 2019/11/22 13:28:43
ofst[ 8]:err_code:0xa0801004, clock:0x2598fb77 2019/12/27 17:27:19
ofst[ 12]:err_code:0xa0801001, clock:0x259e14e3 2019/12/31 14:17:07
ofst[ 16]:err_code:0xa0801004, clock:0x259e1cff 2019/12/31 14:51:43
ofst[ 20]:err_code:0xa0801004, clock:0x25a0e033 2020/01/02 17:09:07
ofst[ 24]:err_code:0xa0801004, clock:0x25a4c10f 2020/01/05 15:45:19
ofst[ 28]:err_code:0xa0801004, clock:0x25a79e06 2020/01/07 19:52:38
ofst[ 32]:err_code:0xa0801004, clock:0x2629ff05 2020/04/15 17:21:09
ofst[ 36]:err_code:0xa0801004, clock:0x26346b35 2020/04/23 15:05:25
ofst[ 40]:err_code:0xa0801002, clock:0x2635aa0a 2020/04/24 13:45:46
ofst[ 44]:err_code:0xa0801004, clock:0x2677b5e4 2020/06/13 16:05:56
ofst[ 48]:err_code:0xa0801001, clock:0x26db9e68 2020/08/28 10:52:24
ofst[ 52]:err_code:0xa0801004, clock:0x26dba662 2020/08/28 11:26:26
ofst[ 56]:err_code:0xa0801001, clock:0x26dbb11c 2020/08/28 12:12:12
ofst[ 60]:err_code:0xa0902120, clock:0x26dbb11c 2020/08/28 12:12:12
ofst[ 64]:err_code:0xa0801004, clock:0x26de925d 2020/08/30 16:37:49
ofst[ 68]:err_code:0xa0801002, clock:0x2f55d041 2025/03/01 14:03:45
ofst[ 72]:err_code:0xa0801002, clock:0x2f55d092 2025/03/01 14:05:06
ofst[ 76]:err_code:0xa0801002, clock:0x2f55d09f 2025/03/01 14:05:19
ofst[ 80]:err_code:0xa0801002, clock:0x2f55d0d1 2025/03/01 14:06:09
ofst[ 84]:err_code:0xa0801002, clock:0x2f670613 2025/03/14 15:21:55
ofst[ 88]:err_code:0xa0801002, clock:0x0b4886ac 2005/12/31 00:00:44
ofst[ 92]:err_code:0xa0801002, clock:0x0b4887ad 2005/12/31 00:05:01
ofst[ 96]:err_code:0xa0801002, clock:0x0b488849 2005/12/31 00:07:37
ofst[100]:err_code:0xa0902120, clock:0x0b488849 2005/12/31 00:07:37
ofst[104]:err_code:0xa0801002, clock:0x0b488880 2005/12/31 00:08:32
ofst[108]:err_code:0xa0801002, clock:0x0b4888a4 2005/12/31 00:09:08
ofst[112]:err_code:0xa0801002, clock:0x0b488ad1 2005/12/31 00:18:25
ofst[116]:err_code:0xa0801002, clock:0x0b488b03 2005/12/31 00:19:15
ofst[120]:err_code:0xa0801002, clock:0x0b488b1a 2005/12/31 00:19:38
ofst[124]:err_code:0xa0801002, clock:0x0b488bf1 2005/12/31 00:23:13
ofst[ 0]:err_code:0xa0801002, clock:0x0b488c03 2005/12/31 00:23:31
[mullion]$
becount
Bringup : 1263 times
Shutdown: 940 times
Power-on: 57day 10hour 32min 19sec
[mullion]$

How can i find faulty Nec tokin ?

Is there a definitive way to detect it?
 
Last edited by a moderator:
need advice please, for frankenstein mod
.
hi there,

i have several playstation consoles and handhelds (round about 20, and a ton of other consoles and handhelds), my location is germany.

Ever since i found out about the frankenstein mod, my greatest wish has been to own such a console.

There are three candidates in my collection who could be considered. LV1 RSX info and syscon log see spoilers

CECHB00, like new, I removed the warranty seal, only replaced the heat-conducting paste and cleaned the console. No obvious failures or abnormalities, fan profile syscon. rsx and cell temperatures @ 68 to 76 degree celsius (vertical stand, room temperature 21 degree celsius), after 1 hour of last of us. ironically, the cell processor is hotter than on the consoles that are still sealed.

LV1 dump RSX Info - b03 500/650 vpe:ff shd:77 [AP0003781:1:1:18:6:e:2:f:1][16:3:1:1:1:3:1][0:0:0]
RSX: CXD2971DGB

Firmware Version: 4.91 (build 50754)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 02
Hardware Config: 000000000003FFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)
Bringup Count: 456, Shutdown Count: 399
Runtime: 38 Days, 23 Hours, 12 Minutes, 22 Seconds
Error Log
01: A0801001 Sat Dec 31 01:04:58 2005
02: A0801001 Sat Dec 31 01:03:17 2005
03: A0801601 Sat Dec 31 01:01:10 2005
04: A0801701 Sat Dec 31 01:01:10 2005
05: A0801601 Mon May 13 12:19:38 2024
06: A0801701 Mon May 13 12:19:38 2024
07: A0801001 Sat Nov 3 06:57:32 2018
08: A0801001 Sat Aug 10 14:51:20 2013
09: A0801001 Sun Jul 29 08:49:18 2012
10: A0801001 Mon Jul 23 10:21:13 2012
11: A0901001 Mon Jun 18 04:36:24 2012
12: A0801001 Thu May 3 06:33:10 2012
13: A0801001 Mon Sep 12 02:49:27 2011
14: A0801001 Sun Sep 11 12:22:13 2011
15: A0901001 Mon Jul 18 12:13:41 2011
16: A0801001 Mon Jul 18 06:45:57 2011
17: A0801001 Mon Jun 13 06:52:37 2011
18: A0801001 Mon May 30 11:04:20 2011
19: A0801001 Mon Apr 25 09:00:55 2011
20: A0801001 Mon Apr 25 08:59:55 2011
21: A0801001 Wed Mar 23 10:26:14 2011
22: A0801001 Mon Feb 28 11:15:45 2011
23: A0801001 Mon Feb 28 08:15:25 2011
24: A0801001 Sun Feb 13 10:08:26 2011
25: A0801001 Mon Dec 13 09:48:53 2010
26: A0801001 Mon Dec 13 07:31:15 2010
27: A0801001 Mon Dec 13 06:51:17 2010
28: A0801001 Mon Dec 13 03:51:07 2010
29: A0801001 Mon Nov 1 09:01:13 2010
30: A0801001 Mon Oct 18 09:34:21 2010
31: A0801001 Tue Oct 5 02:05:48 2010
32: FFFFFFFF Mon Sep 27 06:18:48 2010


CECHA00 (1), like new, dust free, still factory sealed. No obvious failures or abnormalities, fan profile syscon, rsx and cell temperatures @ 64 to 76 degree celsius (vertical stand, room temperature 22 degree celsius), after 1 hour of last of us.

LV1 dump RSX Info - b08 500/650 vpe:ff shd:6f [AP0004502:1:1:4:14:b:2:f:2][16:3:1:1:1:3:1][0:0:0]

Firmware Version: 4.91 (build 50754)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)
Bringup Count: 1620, Shutdown Count: 1615
Runtime: 58 Days, 3 Hours, 41 Minutes, 34 Seconds
Error Log
01: A0801601 Sat Dec 31 03:46:33 2005
02: A0801701 Sat Dec 31 03:46:33 2005
03: A0801001 Sat Dec 31 01:44:19 2005
04: A0802022 Wed Mar 20 15:17:18 2013
05: A0802022 Wed Mar 20 15:07:18 2013
06: A0801001 Fri May 20 01:14:53 2011
07: A0802203 Tue Sep 22 06:49:46 2009
08: A0802022 Mon Oct 13 12:50:18 2008
09: A0802022 Mon Oct 13 12:16:05 2008
10: A0802022 Mon Oct 13 12:16:05 2008
11: A0802022 Mon Oct 13 12:16:05 2008
12: A0802022 Mon Oct 13 10:50:31 2008
13: A0802022 Mon Oct 13 10:33:36 2008
14: A0802022 Mon Oct 13 10:33:36 2008
15: A0802022 Mon Oct 13 10:33:36 2008
16: A0802022 Mon Oct 13 09:19:25 2008
17: A0802022 Mon Oct 13 09:19:25 2008
18: A0802022 Mon Oct 13 09:19:25 2008
19: A0802022 Mon Oct 13 09:18:05 2008
20: A0802022 Mon Oct 13 09:18:05 2008
21: A0802022 Mon Oct 13 09:18:05 2008
22: A0802022 Mon Oct 13 07:37:28 2008
23: A0802022 Mon Oct 13 07:37:28 2008
24: A0802022 Mon Oct 13 07:37:27 2008
25: A0802022 Sun Oct 12 15:07:52 2008
26: A0802022 Sun Oct 12 15:07:32 2008
27: A0802022 Sun Oct 12 15:07:32 2008
28: A0802022 Sun Oct 12 15:07:32 2008
29: A0802022 Sun Oct 12 15:07:01 2008
30: A0802022 Sun Oct 12 13:30:12 2008
31: A0802022 Sun Oct 12 13:30:12 2008
32: FFFFFFFF Sun Oct 12 13:30:12 2008


CECHA00 (2), like new, dust free, still factory sealed. No obvious failures or abnormalities, fan profile syscon. rsx and cell temperatures @ 67 to 74 degree celsius (vertical stand, room temperature 21 degree celsius), after 1 hour of last of us. i have no clou if the error A0801002

LV1 dump RSX Info - b08 500/650 vpe:ff shd:3f [AP0004829:1:1:19:14:a:2:f:2][16:3:1:1:1:3:1][0:0:0]

Firmware Version: 4.91 (build 50754)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)
Bringup Count: 326, Shutdown Count: 316
Runtime: 15 Days, 19 Hours, 50 Minutes, 39 Seconds
Error Log
01: A0801001 Mon Jan 13 13:52:02 2025
02: A0801002 Sat Jan 11 09:28:25 2025
03: A0801001 Tue Jun 22 14:20:54 2010
04: A0801001 Tue Apr 20 09:02:27 2010
05: A0801001 Wed Jan 10 05:36:18 2007
06: A0801001 Wed Jan 10 05:31:42 2007
07: A0801001 Wed Jan 10 05:26:36 2007
08: A0801001 Wed Jan 10 05:20:11 2007
09: FFFFFFFF Sat Jan 1 00:59:59 2000
10: FFFFFFFF Sat Jan 1 00:59:59 2000
11: FFFFFFFF Sat Jan 1 00:59:59 2000
12: FFFFFFFF Sat Jan 1 00:59:59 2000
13: FFFFFFFF Sat Jan 1 00:59:59 2000
14: FFFFFFFF Sat Jan 1 00:59:59 2000
15: FFFFFFFF Sat Jan 1 00:59:59 2000
16: FFFFFFFF Sat Jan 1 00:59:59 2000
17: FFFFFFFF Sat Jan 1 00:59:59 2000
18: FFFFFFFF Sat Jan 1 00:59:59 2000
19: FFFFFFFF Sat Jan 1 00:59:59 2000
20: FFFFFFFF Sat Jan 1 00:59:59 2000
21: FFFFFFFF Sat Jan 1 00:59:59 2000
22: FFFFFFFF Sat Jan 1 00:59:59 2000
23: FFFFFFFF Sat Jan 1 00:59:59 2000
24: FFFFFFFF Sat Jan 1 00:59:59 2000
25: FFFFFFFF Sat Jan 1 00:59:59 2000
26: FFFFFFFF Sat Jan 1 00:59:59 2000
27: FFFFFFFF Sat Jan 1 00:59:59 2000
28: FFFFFFFF Sat Jan 1 00:59:59 2000
29: FFFFFFFF Sat Jan 1 00:59:59 2000
30: FFFFFFFF Sat Jan 1 00:59:59 2000
31: FFFFFFFF Sat Jan 1 00:59:59 2000
32: FFFFFFFF Sat Jan 1 00:59:59 2000

Which console would you choose for a mod? It is usually said that you never change a running system, but as I said, there is a great desire for a modified console.

Do you also know a trustworthy frankenstein service in germany or the neighbouring EU countries (if you are from the region)? I have already been in dialogue with proconsoles.nl, but their conditions didn't suit me. The contact however was very nice and responsive, it has to be said.

Any advice is helpful. Thanks in advance.
 
Last edited by a moderator:
need advice please, for frankenstein mod
.
As an owner of an unofficial Frankenstein A00 system, here's my advice...
  1. Consider doing the Frankie mod to an already YLOD system. This is because the board is not guaranteed to survive the Frankenstein process. Some boards also have a delamination defect (although it's still possible to do the mod, just means higher risk) and if this happens, the board is basically toast.
  2. (optional) Use a system that hasn't been opened or had the board modified if you are using a YLOD one. Over the years people have done crazy things like blast the board/chips with hair dryers, heat guns, even putting it in the oven.... I would say these are the worst boards as who knows what the previous owners did....
  3. If you're still wanting to do it to a system that isn't YLOD, try and pick a system with a cooler running Cell. This is basically silicon lottery. Some Cells run cooler than others. The lower the temperatures, the better the longevity of the console.
  4. And similarly to the cooler Cell idea, see if the person providing the service will let you handpick a good RSX. I haven't looked into it too deeply, but apparently the 2500 slim 40nm RSX is very good for overclocking. Some modders also offer a new old stock RSX as opposed to harvesting one off a slim or super slim that may already have seen a lot of use, and may be prone to failing quicker than a new old stock one.
Here's what I did: I found a completely trashed A00. It was well used, YLOD (with 3034 errors) and basically junk. I paid for the service in the UK (I know this is outside of EU so not ideal for you) as I live in UK myself, and got a great running A00 with 40nm RSX. I paid extra for the NEC Tokins replaced for futureproofing.

Though I didn't do points 3 and 4 above myself because 1) it was a dead system so I had no idea how cool the Cell was 2) I did it before overclocking became well known in the modding community.

A year and a half later though, still runs great. I love it.

Hope this helps.
 
Last edited by a moderator:
CECHC04 shuts down only when playing non-bluray games
.
I am on CFW 4.91 and it shuts down in games installed through pkgi (triple red light beep) but not those on blurays. Assassin's Creed 1, Ridge Racer 7 and GTA IV all run without issues.

I got grid 2 to load in and immediately after finishing the first race it shut down. Midnight Club and Gran Turismo 6 just shut it down when loading.

I thought it was a hard drive issue then (after opening it up and thoroughly cleaning it up and repasting) but it runs GTA IV which is on a hard drive so now I am just confused. Any ideas?

I didn't try PS2 games as I don't have a ps3 controller and my dualsense won't work in ps2 mode.

The syscon error is 1002 which is confusing me because apparently it is power delivery to the rsx?
 
Last edited by a moderator:
CECH 2501A Standby light turns on for a moment after standby voltage added, then turns off.

Was doing RSX voltage modding. w 51 56, not enough, w 51 46, too much (it runs too hot), w 51 48, I lose a screw and decide to button it up without testing it. The next morning, I find the screw, and put it where it's supposed to go, and I test the PS3, but the standby light turns off a little after it turns on. I figure it's a SYSCON issue, since that's the only thing I touched, so I figure I should check the checksum.
Code:
>$ eepcsum
00000000
# csum = 0xFFFF

Press Ctrl+C to exit
>$
Obviously not right. Am I cooked? Here's what a bringup looks like.
Code:
>$ bringup
FFFFA605
No clue. Help!
 
Hello, I have a PS3 CECHH01 which started having the YLOD a couple years ago. It would still boot and work fine at first if I pressed the power button a few times but would die completely after not long. It no longer powers on, only shows the YLOD after 2-10 seconds from powering on. I used RIP Felix's PS3 SYSCON Tutorial to try and diagnose the problem and the error log constantly shows a 1002 error. Also looked at the Syscon Error Codes list and learned that a 1002 error is associated with faulty NEC/TOKIN capacitors.

Here's what my errlog looks like:

>$ errlog
errlog
ofst[ 20]:err_code:0xffffffff, clock:0x0ce3b43f 2006/11/07 21:16:47
ofst[ 24]:err_code:0xa0801002, clock:0x0ce3b44b 2006/11/07 21:16:59
ofst[ 28]:err_code:0xa0801002, clock:0x0ce3b452 2006/11/07 21:17:06
ofst[ 32]:err_code:0xa0801002, clock:0x0ce3b458 2006/11/07 21:17:12
ofst[ 36]:err_code:0xa0801002, clock:0x0ce3b45e 2006/11/07 21:17:18
ofst[ 40]:err_code:0xa0801002, clock:0x0ce3b492 2006/11/07 21:18:10
ofst[ 44]:err_code:0xa0801002, clock:0x0ce3b49d 2006/11/07 21:18:21
ofst[ 48]:err_code:0xa0801002, clock:0x0ce3b4a8 2006/11/07 21:18:32
ofst[ 52]:err_code:0xa0801002, clock:0x0ce3b4b9 2006/11/07 21:18:49
ofst[ 56]:err_code:0xa0801002, clock:0x0ce3b4c0 2006/11/07 21:18:56
ofst[ 60]:err_code:0xa0801002, clock:0x0ce3b4c7 2006/11/07 21:19:03
ofst[ 64]:err_code:0xa0801002, clock:0x0ce3b4d2 2006/11/07 21:19:14
ofst[ 68]:err_code:0xa0801002, clock:0x0ce3b4d9 2006/11/07 21:19:21
ofst[ 72]:err_code:0xa0801002, clock:0x0ce3b4df 2006/11/07 21:19:27
ofst[ 76]:err_code:0xa0801002, clock:0x0ce3b4e6 2006/11/07 21:19:34
ofst[ 80]:err_code:0xa0801002, clock:0x0ce3b4ec 2006/11/07 21:19:40
ofst[ 84]:err_code:0xa0801002, clock:0x0ce3b4f3 2006/11/07 21:19:47
ofst[ 88]:err_code:0xa0801002, clock:0x0ce3b4fa 2006/11/07 21:19:54
ofst[ 92]:err_code:0xa0801002, clock:0x0ce3b501 2006/11/07 21:20:01
ofst[ 96]:err_code:0xa0801002, clock:0x0ce3b508 2006/11/07 21:20:08
ofst[100]:err_code:0xa0801002, clock:0x0da41f5e 2007/04/02 20:09:02
ofst[104]:err_code:0xa0801002, clock:0x0da41f6d 2007/04/02 20:09:17
ofst[108]:err_code:0xa0801002, clock:0x0da41f78 2007/04/02 20:09:28
ofst[112]:err_code:0xa0801002, clock:0x0da41f80 2007/04/02 20:09:36
ofst[116]:err_code:0xa0801002, clock:0x0da41fa8 2007/04/02 20:10:16
ofst[120]:err_code:0xa0801002, clock:0x0da42021 2007/04/02 20:12:17
ofst[124]:err_code:0xa0801002, clock:0x0da42044 2007/04/02 20:12:52
ofst[ 0]:err_code:0xa0801002, clock:0x0da420a2 2007/04/02 20:14:26
ofst[ 4]:err_code:0xa0801002, clock:0x0da420ae 2007/04/02 20:14:38
ofst[ 8]:err_code:0xa0801002, clock:0x0da42837 2007/04/02 20:46:47
ofst[ 12]:err_code:0xa0801002, clock:0x0da4284d 2007/04/02 20:47:09
ofst[ 16]:err_code:0xa0801002, clock:0x0da42919 2007/04/02 20:50:33

Here's what my bringup looks like:

>$ bringup
bringup
[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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$ bringup
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 2.0.0 (Build ID: 2655,27256, Build Data: 2007-10-26_12:10:58)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bringup
Do nothing. (FatalOff State)
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit

Help! What to do next? If it means replacing the NEC/TOKIN capacitors I'd be willing to give it a try, it's a $5 PS3 so not much to lose.
Thanks all.
 
Hello, I have a PS3 CECHH01 which started having the YLOD a couple years ago. It would still boot and work fine at first if I pressed the power button a few times but would die completely after not long. It no longer powers on, only shows the YLOD after 2-10 seconds from powering on. I used RIP Felix's PS3 SYSCON Tutorial to try and diagnose the problem and the error log constantly shows a 1002 error. Also looked at the Syscon Error Codes list and learned that a 1002 error is associated with faulty NEC/TOKIN capacitors.

Here's what my errlog looks like:

>$ errlog
errlog
ofst[ 20]:err_code:0xffffffff, clock:0x0ce3b43f 2006/11/07 21:16:47
ofst[ 24]:err_code:0xa0801002, clock:0x0ce3b44b 2006/11/07 21:16:59
ofst[ 28]:err_code:0xa0801002, clock:0x0ce3b452 2006/11/07 21:17:06
ofst[ 32]:err_code:0xa0801002, clock:0x0ce3b458 2006/11/07 21:17:12
ofst[ 36]:err_code:0xa0801002, clock:0x0ce3b45e 2006/11/07 21:17:18
ofst[ 40]:err_code:0xa0801002, clock:0x0ce3b492 2006/11/07 21:18:10
ofst[ 44]:err_code:0xa0801002, clock:0x0ce3b49d 2006/11/07 21:18:21
ofst[ 48]:err_code:0xa0801002, clock:0x0ce3b4a8 2006/11/07 21:18:32
ofst[ 52]:err_code:0xa0801002, clock:0x0ce3b4b9 2006/11/07 21:18:49
ofst[ 56]:err_code:0xa0801002, clock:0x0ce3b4c0 2006/11/07 21:18:56
ofst[ 60]:err_code:0xa0801002, clock:0x0ce3b4c7 2006/11/07 21:19:03
ofst[ 64]:err_code:0xa0801002, clock:0x0ce3b4d2 2006/11/07 21:19:14
ofst[ 68]:err_code:0xa0801002, clock:0x0ce3b4d9 2006/11/07 21:19:21
ofst[ 72]:err_code:0xa0801002, clock:0x0ce3b4df 2006/11/07 21:19:27
ofst[ 76]:err_code:0xa0801002, clock:0x0ce3b4e6 2006/11/07 21:19:34
ofst[ 80]:err_code:0xa0801002, clock:0x0ce3b4ec 2006/11/07 21:19:40
ofst[ 84]:err_code:0xa0801002, clock:0x0ce3b4f3 2006/11/07 21:19:47
ofst[ 88]:err_code:0xa0801002, clock:0x0ce3b4fa 2006/11/07 21:19:54
ofst[ 92]:err_code:0xa0801002, clock:0x0ce3b501 2006/11/07 21:20:01
ofst[ 96]:err_code:0xa0801002, clock:0x0ce3b508 2006/11/07 21:20:08
ofst[100]:err_code:0xa0801002, clock:0x0da41f5e 2007/04/02 20:09:02
ofst[104]:err_code:0xa0801002, clock:0x0da41f6d 2007/04/02 20:09:17
ofst[108]:err_code:0xa0801002, clock:0x0da41f78 2007/04/02 20:09:28
ofst[112]:err_code:0xa0801002, clock:0x0da41f80 2007/04/02 20:09:36
ofst[116]:err_code:0xa0801002, clock:0x0da41fa8 2007/04/02 20:10:16
ofst[120]:err_code:0xa0801002, clock:0x0da42021 2007/04/02 20:12:17
ofst[124]:err_code:0xa0801002, clock:0x0da42044 2007/04/02 20:12:52
ofst[ 0]:err_code:0xa0801002, clock:0x0da420a2 2007/04/02 20:14:26
ofst[ 4]:err_code:0xa0801002, clock:0x0da420ae 2007/04/02 20:14:38
ofst[ 8]:err_code:0xa0801002, clock:0x0da42837 2007/04/02 20:46:47
ofst[ 12]:err_code:0xa0801002, clock:0x0da4284d 2007/04/02 20:47:09
ofst[ 16]:err_code:0xa0801002, clock:0x0da42919 2007/04/02 20:50:33

Here's what my bringup looks like:

>$ bringup
bringup
[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 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
Press Ctrl+C to exit
>$ bringup
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 2.0.0 (Build ID: 2655,27256, Build Data: 2007-10-26_12:10:58)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bringup
Do nothing. (FatalOff State)
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit

Help! What to do next? If it means replacing the NEC/TOKIN capacitors I'd be willing to give it a try, it's a $5 PS3 so not much to lose.
Thanks all.
Well, your situation is more defined than mine (error code 0801001), and since you haven't removed the IHS from the processor, if I were in your shoes, I'd start by replacing the NEC/Tokin capacitors under the RSX processor and then see how it goes.
 
Ps3 cok-002 ylod 3034 with good ohm readings
.Hello everyone. Maybe someone can help me find the cause. I have a PS3 cechc04, board cok-002 with an ylod that I wanted to use for a Frankie. I usually always check the ohm resistors on the board first before reading the Syscon values such as vddio, pll, vddr etc., purely out of interest. And I usually see straight away that some values are completely off, which also confirms an error 3034. But this board has very good values for all known test points. For example, vddc is very healthy at 3.2 ohms in my opinion, as are all the other points. Cell also has healthy values. I know that 3034 doesn't always mean that the BGA under the rsx or cell is defective, but that the southbridge could also have a fault. My question is, should I just carry on as usual and replace the rsx with a 40 nm one, or should I first check whether the problem really comes from the rsx. Not that I replaced the RSX and the problem lies elsewhere. Thanks.
 
Last edited by a moderator:
Code:
errlog
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xa0003001, clock:0xffffffff
ofst[ 44]:err_code:0xa0003001, clock:0xffffffff
ofst[ 48]:err_code:0xa0003001, clock:0xffffffff
ofst[ 52]:err_code:0xa0003001, clock:0xffffffff
ofst[ 56]:err_code:0xa0003001, clock:0xffffffff
ofst[ 60]:err_code:0xa0003001, clock:0xffffffff
ofst[ 64]:err_code:0xa0003001, clock:0xffffffff
ofst[ 68]:err_code:0xa0003001, clock:0xffffffff
ofst[ 72]:err_code:0xa0003001, clock:0xffffffff
ofst[ 76]:err_code:0xa0101004, clock:0xffffffff
ofst[ 80]:err_code:0xa0101004, clock:0xffffffff
ofst[ 84]:err_code:0xa0101004, clock:0xffffffff
ofst[ 88]:err_code:0xa0101004, clock:0xffffffff
ofst[ 92]:err_code:0xa0101004, clock:0xffffffff
ofst[ 96]:err_code:0xa0801200, clock:0xffffffff
ofst[100]:err_code:0xa0801200, clock:0xffffffff
ofst[104]:err_code:0xa0801200, clock:0xffffffff
ofst[108]:err_code:0xa0801200, clock:0xffffffff
ofst[112]:err_code:0xa0902203, clock:0xffffffff
ofst[116]:err_code:0xa0902203, clock:0xffffffff
ofst[120]:err_code:0xa0801200, clock:0xffffffff
ofst[124]:err_code:0xa0801200, clock:0xffffffff
ofst[  0]:err_code:0xa0801200, clock:0xffffffff
ofst[  4]:err_code:0xa0801200, clock:0xffffffff
ofst[  8]:err_code:0xa0902203, clock:0xffffffff
ofst[ 12]:err_code:0xa0902203, clock:0xffffffff
ofst[ 16]:err_code:0xa0801200, clock:0xffffffff
ofst[ 20]:err_code:0xa0801200, clock:0xffffffff
ofst[ 24]:err_code:0xa0801200, clock:0xffffffff
ofst[ 28]:err_code:0xa0801200, clock:0xffffffff
ofst[ 32]:err_code:0xa0801200, clock:0xffffffff
[mullion]$
 
Hello Guys!

I have a CECHG PS3 and got it from Marketplace cheap. :)

Its on YLOD and trying to fix it as my 1st PS3 Project.

Already extracted the Errlogs and bringups, Would like to ask for you help regarding the logs.

Hoping for your Help Guys! :)

Thanks.

Code:
[CODE]Microsoft Windows [Version 10.0.26100.3624]
(c) Microsoft Corporation. All rights reserved.

D:\BACKUP\DOWNLOADS\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM5 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x1596
Addr:0x000034fe should be 0x86d6
sum:0x0100
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
Press Ctrl+C to exit
>$ w 39fe 60 73
w 39fe 60 73
w complete!
[mullion]$
Press Ctrl+C to exit
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x1596
Addr:0x000034fe should be 0x86d6
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 36]:err_code:0xffffffff, clock:0x2f6bc6b2  2025/03/18 05:52:50
ofst[ 40]:err_code:0xa0101002, clock:0x2f6bc6c7  2025/03/18 05:53:11
ofst[ 44]:err_code:0xa0101002, clock:0x2f72d365  2025/03/23 14:12:53
ofst[ 48]:err_code:0xa0101002, clock:0x2f72d375  2025/03/23 14:13:09
ofst[ 52]:err_code:0xa0101002, clock:0x2f72d381  2025/03/23 14:13:21
ofst[ 56]:err_code:0xa0101002, clock:0x2f72d38c  2025/03/23 14:13:32
ofst[ 60]:err_code:0xa0101002, clock:0xffffffff
ofst[ 64]:err_code:0xa0093004, clock:0xffffffff
ofst[ 68]:err_code:0xa0101002, clock:0xffffffff
ofst[ 72]:err_code:0xa0101002, clock:0xffffffff
ofst[ 76]:err_code:0xa0101002, clock:0xffffffff
ofst[ 80]:err_code:0xa0101002, clock:0xffffffff
ofst[ 84]:err_code:0xa0101002, clock:0xffffffff
ofst[ 88]:err_code:0xa0101002, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0101002, clock:0xffffffff
ofst[100]:err_code:0xa0101002, clock:0xffffffff
ofst[104]:err_code:0xa0101002, clock:0xffffffff
ofst[108]:err_code:0xa0101002, clock:0xffffffff
ofst[112]:err_code:0xa0101002, clock:0xffffffff
ofst[116]:err_code:0xa0101002, clock:0xffffffff
ofst[120]:err_code:0xa0101002, clock:0xffffffff
ofst[124]:err_code:0xa0101002, clock:0xffffffff
ofst[  0]:err_code:0xa0101002, clock:0xffffffff
ofst[  4]:err_code:0xa0093004, clock:0xffffffff
ofst[  8]:err_code:0xa0101002, clock:0xffffffff
ofst[ 12]:err_code:0xa0101002, clock:0xffffffff
ofst[ 16]:err_code:0xa0101002, clock:0xffffffff
ofst[ 20]:err_code:0xa0101002, clock:0xffffffff
ofst[ 24]:err_code:0xa0101002, clock:0xffffffff
ofst[ 28]:err_code:0xa0101002, clock:0xffffffff
ofst[ 32]:err_code:0xa0093004, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ becount
becount
Bringup : 340 times
Shutdown: 273 times
Power-on: 197day 05hour 03min 58sec
[mullion]$
Press Ctrl+C to exit
>$ bringup
bringup
[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] fatalreq delayed.
[ERROR]: 0xa0101002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0101002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0101002
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] *** Power Fail RS ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$
[/CODE]
 
NEC/Tokin question: I have a CECHH01 FAT model. I have removed one NEC/Tokin (the right-hand side) from the back side of the RSX. After remove I have checked the positive and negative pads with a multimeter. I have measured short circuit between the positive and negative pads. Is this normal?
 
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] fatalreq delayed.
[ERROR]: 0xa0901001
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[SSM] *** Power Fail BE ***
[SSM] state: 0000 -> 0800
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.

Is there something wrong with my CELL/BE power rail?
 
NEC/Tokin question: I have a CECHH01 FAT model. I have removed one NEC/Tokin (the right-hand side) from the back side of the RSX. After remove I have checked the positive and negative pads with a multimeter. I have measured short circuit between the positive and negative pads. Is this normal?

Yes, that's normal, it will vary slightly based on the lithography of the RSX, but 3Ω is about the average from my experience. Lower is fine (the lowest I have tested is a slim with a 60nm RSX at 2.8Ω) as long as it's not a dead short. Make sure you're checking with the resistance setting on your multi-meter as diode/continuity will identify such low resistances as shorts even though they're not.

Is there something wrong with my CELL/BE power rail?

Error 1001 could be a number of things, but the first thing I'd suspect is the Cell B.E. Tokins, does the PS3 stay on or immediately YLOD?

Hello Guys!

I have a CECHG PS3 and got it from Marketplace cheap. :)

Error 1002 would imply RSX Tokins, but I notice that there are a few 3004's in there as well, they could also be related to RSX filtering (i.e. Tokins) but it could also indicate an issue with the RSX itself (bumps?), as 1002 is the most recent error and what occurred during bringup I'd tackle that first.

Ps3 cok-002 ylod 3034 with good ohm readings
.

It's hard to say, your best bet would likely be desolder the RSX and see if the resistance values change, I can't say what they should be as I don't think motherboard sans RSX values have ever been recorded, but a change would likely indicate that the RSX is the problem. Have you checked the log during bringup to see if it fails during bit-training?

Also, I've had a few dead RSX's that appeared fine except for one value (usually one point like PLL fluctuating so that my DMM can't auto range on it), sometimes they're all bad, the way these things fail is totally random.

Good luck with your Frankie! I hope to make my own 40nm RSX COK-002 one day..

Code:
errlog

3001 errors can occur if you tried to power the system on with only the 5V cable from the PSU connected, though 1004 could also indicate a bad PSU, also the Cell B.E. reached critical tempreture (error 1200) and caused a forced shutdown.

Try a known good PSU first, if it works replace the TIM under the heatsinks, if it still overheats delid the Cell B.E.
 
Last edited:
Error 1002 would imply RSX Tokins, but I notice that there are a few 3004's in there as well, they could also be related to RSX filtering (i.e. Tokins) but it could also indicate an issue with the RSX itself (bumps?), as 1002 is the most recent error and what occurred during bringup I'd tackle that first.

Thanks For the reply. Already replaced the NECTOKIN on RSX Side. Now it is alive again. Thanks for the Suggestion.
 
So, I found a PS3 COK-002 on a dump today. TLDR, errlog was full of 0xa0404422 and 0xa0403034. Only these 2, nothing else.
When I tried bringup to see what happens, this is what I got:
Code:
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] fatalreq delayed.
[ERROR]: 0xa0061004
[SSM] fatalreq delayed.
[ERROR]: 0xa0081001
[SSM] state: 0101 -> 0301
[SSM] *** Power Fail BE ***
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093003

From what I understand, it seems like the RSX is busted. Your opinion, guys?
 
Greetings PSX place. I come to the wizards of this place looking for a second opinion from much more informed people on what the next course of action would be in repairing my friends PS3 that we are working on. I have an idea of what the problem is but I don't want to commit our limited funds to the next action without increasing our confidence. He has a CECHL01.

>$ auth
Auth successful
Press Ctrl+C to exit
>$ version
00000000
# Sherwood Version = 0.17.0
>$ errlog
00000000
# CODE CLOCK
# A0802124 FFFFFFFF
# A0801200 FFFFFFFF
# A0802024 FFFFFFFF
# A0802024 FFFFFFFF
# A0802124 FFFFFFFF
# A0802024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
 
Firmware Version: 4.92 (build 50763)
Platform ID: CokC12
Product Code: 00 84
Product Sub Code: 00 05
Hardware Config: 000000000007FCFF
Syscon Firmware Version: 0DBF.0000000000030002 (EEPROM: 0000000000030002)
Bringup Count: 1512, Shutdown Count: 749
Runtime: 47 Days, 13 Hours, 24 Minutes, 36 Seconds
Error Log
01: A0801200 Fri Dec 30 19:00:16 2005
02: A0003001 Fri Dec 31 18:59:59 1999
03: A0A02030 Fri Dec 31 18:59:59 1999
04: A0003001 Fri Dec 31 18:59:59 1999
05: A0003001 Fri Dec 31 18:59:59 1999
06: A0003001 Fri Dec 31 18:59:59 1999
07: A0A02030 Fri Dec 31 18:59:59 1999
08: A0003001 Fri Dec 31 18:59:59 1999
09: A0A02030 Fri Dec 31 18:59:59 1999
10: A0003001 Fri Dec 31 18:59:59 1999
11: A0003001 Fri Dec 31 18:59:59 1999
12: A0003001 Fri Dec 31 18:59:59 1999
13: A0003001 Fri Dec 31 18:59:59 1999
14: A0003001 Fri Dec 31 18:59:59 1999
15: A0003001 Fri Dec 31 18:59:59 1999
16: A0003001 Fri Dec 31 18:59:59 1999
17: A0003001 Fri Dec 31 18:59:59 1999
18: A0003001 Fri Dec 31 18:59:59 1999
19: A0003001 Fri Dec 31 18:59:59 1999
20: A0003001 Fri Dec 31 18:59:59 1999
21: A0003001 Fri Dec 31 18:59:59 1999
22: A0003001 Fri Dec 31 18:59:59 1999
23: A0003001 Fri Dec 31 18:59:59 1999
24: A0003001 Fri Dec 31 18:59:59 1999
25: A0003001 Fri Dec 31 18:59:59 1999
26: A0003001 Fri Dec 31 18:59:59 1999
27: A0003001 Fri Dec 31 18:59:59 1999
28: A0003001 Fri Dec 31 18:59:59 1999
29: A0003001 Fri Dec 31 18:59:59 1999
30: A0003001 Fri Dec 31 18:59:59 1999
31: A0003001 Fri Dec 31 18:59:59 1999
32: FFFFFFFF Fri Dec 31 18:59:59 1999


Additional information/context: This PS3 usually - upon powering on - instant shutdowns. No blinking light; nothing. However, and on the contrary, there are times in between where the PS3 boots up perfectly fine and loads the XMB (which is how I extracted this error log) peppered in between the instant shutdowns. Moreover, these instant shutdowns can happen when the PS3 is in the XMB or doing anything, so it doesn't happen always at start up (naturally). The temps are perfectly normal and are in fact in the desirable category.

Things I've done: Changed the power supply.
 
PS3 Slim CECH3001A was running fine.
After installing HFW and Hen, it froze during the installation of a PKG game.
I turned it of by holding the power button for some seconds.

Now it doesn't boot up anymore.
The system turns on for about 30 seconds and then shuts down; the power indicator also turns off.
Sometimes, after a dozen tries, it does boot up, but it always freezes randomly while navigating the XMB or anything. Even trying to boot up in Safe Mode is a hit-and-miss; sometimes it works, sometimes it doesn't.

HDD is fine. Tested it on PC.

upload_2025-7-3_22-21-37-jpeg.46179

upload_2025-7-3_22-21-48-jpeg.46180
 
Back
Top