PS3 PS3 slim 3001a turns on without problem, but shut off after a minute

[Reisver]

I have a PS3 slim 3001a (KTE-001 board) the device turns on and displays the video signal without problem. The wireless connection works well, whatever, everything works perfectly.

The problem is after 40 or 60 seconds, the device turns off without any "beep" and there is no "stand-by" light (red light). I have checked fuses, capacitors, some resistors and everything looks good. I have tried other PSUs and the same failure continues. I really don't know where to go next.

 

[Nascar1243]

So I made a video on this topic recently, I have deemed this on and off issue the No Light of Death. It is the same as the Yellow Light of Death, there is just no yellow light shown.

You will need to pull the syscon codes to figure out what is going on with your console. It shouldn't be a PSU issue but you can also use LED Diag mode which I will also link a video to but it is also described in my video, It would be better to have the full error log but for this purpose if you are not comfortable with soldering this is an alternative.

 

[Reisver]

So I made a video on this topic recently, I have deemed this on and off issue the No Light of Death. It is the same as the Yellow Light of Death, there is just no yellow light shown.

You will need to pull the syscon codes to figure out what is going on with your console. It shouldn't be a PSU issue but you can also use LED Diag mode which I will also link a video to but it is also described in my video, It would be better to have the full error log but for this purpose if you are not comfortable with soldering this is an alternative.

thanks for your reply.

I have performed the LED diagnosis. throwing me the code "14FF" (0001 - 0100 - 1111 - 1111)

I read on the ps3devwiki page about the code it tells me the following:
" This error can occur when the console was on at the time the YLOD occurred. On consoles exhibiting this error, subsequent attempts to start the console resulted in a GLOD with 1601/1701 errors, or a YLOD within 2 seconds. SYSCON errors usually show one A0801601/A0801701 occurring at the same timestamp, followed thereafter by 3034/4xxx errors for all subsequent attempts to PWR it on. Or it'll GLOD and throw more 1701/1601's. The working theory is that there is a precarious solder joint (BGA or bump defect) teetering on the edge of breaking. It'll soon switch to 3034 with or without 4xxx errors.

Complicating the issue is the fact that sometimes people will get a 1301 or 1802 also. It likely has to do with where the joints are failing and it's involving those sub systems briefly before fully breaking.

Unlike Livelocks, which can be caused by both hardware and software conditions, Checkstops are a hardware issue. A checkstop occurs when the CPU or GPU, cache, memory, or I/O bus controller, finds something in an impossible state (impossible unless the Hardware is broken). The error isn't identified as a particular bus transfer in progress, or the CPU/GPU detects the console is stuck (frozen, no progress being made with that operation). When nothing can be done for a long enough period of time, the checkstop errors is logged and BE ATTENTION is driven High. SYSCON immediately shuts the console down with error A08014FF and A0801701.

The most likely cause of the error is a failing GPU (RSX) solder joint (BGA or Bumps). A distant second is a failing CPU (CELL) solder joint (BGA) " .

Now my question is, in case it is a failure due to possible BGA soldering. Why do the values of some components show me without fail?

 

[Nascar1243]

thanks for your reply.

I have performed the LED diagnosis. throwing me the code "14FF" (0001 - 0100 - 1111 - 1111)

I read on the ps3devwiki page about the code it tells me the following:
" This error can occur when the console was on at the time the YLOD occurred. On consoles exhibiting this error, subsequent attempts to start the console resulted in a GLOD with 1601/1701 errors, or a YLOD within 2 seconds. SYSCON errors usually show one A0801601/A0801701 occurring at the same timestamp, followed thereafter by 3034/4xxx errors for all subsequent attempts to PWR it on. Or it'll GLOD and throw more 1701/1601's. The working theory is that there is a precarious solder joint (BGA or bump defect) teetering on the edge of breaking. It'll soon switch to 3034 with or without 4xxx errors.

Complicating the issue is the fact that sometimes people will get a 1301 or 1802 also. It likely has to do with where the joints are failing and it's involving those sub systems briefly before fully breaking.

Unlike Livelocks, which can be caused by both hardware and software conditions, Checkstops are a hardware issue. A checkstop occurs when the CPU or GPU, cache, memory, or I/O bus controller, finds something in an impossible state (impossible unless the Hardware is broken). The error isn't identified as a particular bus transfer in progress, or the CPU/GPU detects the console is stuck (frozen, no progress being made with that operation). When nothing can be done for a long enough period of time, the checkstop errors is logged and BE ATTENTION is driven High. SYSCON immediately shuts the console down with error A08014FF and A0801701.

The most likely cause of the error is a failing GPU (RSX) solder joint (BGA or Bumps). A distant second is a failing CPU (CELL) solder joint (BGA) " .

Now my question is, in case it is a failure due to possible BGA soldering. Why do the values of some components show me without fail?

To me it does sound like it could be a bga defect but then again it can be something else. More than likely if it was then you won't be able to repair it without a proper rework station.