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

With syscon code 0xa0801001 (BE VRAM Power Fail) is the VRAM the video ram? I've replaced my nec/tokins with tantalum caps and I'm getting the same error as before replacing them. The console will boot for just shy of a minute and then act exactly like I've issues the shutdown command returning to a solid red standby light.
 
I believe its CPU related. I was testing a console and I got a shutdown after a few hours of playing TLOU. I piggybacked on 2 tantalum Panasonic capacitors on the CPU tokins topside of the MB. Today I did a syscon read and it should the error 1001. The console no longer shuts down so it seems to be related in part at least to the CPU tokins

Sent from my SM-G988B using Tapatalk
 
I believe its CPU related. I was testing a console and I got a shutdown after a few hours of playing TLOU. I piggybacked on 2 tantalum Panasonic capacitors on the CPU tokins topside of the MB. Today I did a syscon read and it should the error 1001. The console no longer shuts down so it seems to be related in part at least to the CPU tokins

Sent from my SM-G988B using Tapatalk
I've got 12 470uf tantalums feeding the Cell (both sides of the MB with bridge wires), it is giving me this code and shuts down with no extra error in the log. It's exactly as if it's issued a shutdown command via syscon. The only time I can get an error to appear in the log is if I flip the switch in the back right after powering it on.

I'm at a loss on this and I have no idea where to look next

Sent from my SM-G965U using Tapatalk
 
Sorry let me be clear, what is the exact specification of the capacitors. So I understand they are 470uf. So are they 6.3v? What's the resistance, they need to be under 9 ohm each.

Sent from my SM-G988B using Tapatalk
 
Last edited:
With syscon code 0xa0801001 (BE VRAM Power Fail) is the VRAM the video ram? I've replaced my nec/tokins with tantalum caps and I'm getting the same error as before replacing them. The console will boot for just shy of a minute and then act exactly like I've issues the shutdown command returning to a solid red standby light.
The PDF of error codes has a typo. VRAM is supposed to be VRM (Voltage Regulation Module).
I've got 12 470uf tantalums feeding the Cell (both sides of the MB with bridge wires), it is giving me this code and shuts down with no extra error in the log. It's exactly as if it's issued a shutdown command via syscon. The only time I can get an error to appear in the log is if I flip the switch in the back right after powering it on.

I'm at a loss on this and I have no idea where to look next

Sent from my SM-G965U using Tapatalk
Try replacing the PWR/EJT daughterboard. I've seen somthing like that when with one that was dodgy. Alternatively, double check the BD ribbon cable is properly inserted and cliped in. The console can turn on/off when messing with BD ribbon.

1001 can and will happen if you cut power when the console is on (without graceful shutdown). Sounds like the pwr button is being held down (forced shutdown), which is not graceful.
 
Sorry let me be clear, what is the exact specification of the capacitors. So I understand they are 470uf. So are they 6.3v? What's the resistance, they need to be under 9 ohm each.

Sent from my SM-G988B using Tapatalk
The capacitors I'm using are 2R5TPE470M7 the listing says they're 7 mohm

Sent from my SM-G965U using Tapatalk
 
The PDF of error codes has a typo. VRAM is supposed to be VRM (Voltage Regulation Module).

Try replacing the PWR/EJT daughterboard. I've seen somthing like that when with one that was dodgy. Alternatively, double check the BD ribbon cable is properly inserted and cliped in. The console can turn on/off when messing with BD ribbon.

1001 can and will happen if you cut power when the console is on (without graceful shutdown). Sounds like the pwr button is being held down (forced shutdown), which is not graceful.
That's good to know! Thanks for letting me know.

And as for the power and eject button daughterboard, I've already swapped that from a working system and no change whatsoever.

I'll try swapping a different bluray ribbon cable onto it though and see if that helps any.

Outside of that where should I look next though?

Sent from my SM-G965U using Tapatalk
 
Data sheet indicates 15 ohms.
0a8bc36a4f3323ff7567e023dc1f98cd.jpg


Sent from my SM-G988B using Tapatalk
 
Data sheet indicates 15 ohms.
0a8bc36a4f3323ff7567e023dc1f98cd.jpg


Sent from my SM-G988B using Tapatalk
Welp, I guess I'll be ordering some different ones and swapping them out.

Would 12 tantalums be sufficient? And do you have a brand you recommend?

Sent from my SM-G965U using Tapatalk
 
Welp, I guess I'll be ordering some different ones and swapping them out.

Would 12 tantalums be sufficient? And do you have a brand you recommend?

Sent from my SM-G965U using Tapatalk
Looking at Mouser the caps I'm using are spec'd at 7 mohm

Tantalum Capacitors - Polymer 2.5volts 470uF ESR 7mohm

Sent from my SM-G965U using Tapatalk
 
The capacitors I'm using are 2R5TPE470M7 the listing says they're 7 mohm

Sent from my SM-G965U using Tapatalk
"M7" stands for 7mOhms ESR.

Those are the best caps IMO and should be perfectly adequate, if they're installed correctly. Are you sure that they are?
...The console will boot for just shy of a minute and then act exactly like I've issues the shutdown command returning to a solid red standby light.
I've got 12 470uf tantalums feeding the Cell (both sides of the MB with bridge wires), it is giving me this code and shuts down with no extra error in the log. It's exactly as if it's issued a shutdown command via syscon. The only time I can get an error to appear in the log is if I flip the switch in the back right after powering it on.

Let me see if I understand you.

  1. You flip the power rocker. Standby LED goes solid red witohut beeps.
    • Means standby circuit is fine and there are no checksum issues.
  2. You press the PWR touchpad and the console boots.
    • Means the power on sequencing completed sucessfully. No shorts, blown fuses, or serious HW failures.
  3. XMB loads.
    • Means the bootloader finished sucessfully. No NAND corruption. No GLOD because of it.
  4. You can see and hear the menu? Can navigate around?
    • Means the controller paired, HDMI/AV are working, no slowdown, artifacting, or freezing to indicate a BGA/Bump defect.
  5. And then for no reason whatsoever it immediately shuts off, witout any warning. And the standby LED is still solid red.
    • Means the PSU didn't die or the LED wouldn't be illuminated.
    • Means there was no YLOD or SYSCON error or the LED would be flashing.
    • Acts like the SYSCON was issued a shutdown comand, immediately shutting down (not gracefully), except it wasn't. At least not by you, not intentionally.
Did I get all that right?

Regardless, it would be helpful to see the bringup command. I would especially like to see what it records while the shutdown occurs. So hookup the UART, HDMI, a controller, and auth into internal mode. Use the bringup command to start the console. Then switch to HDMI. Navigate around XMB until it shuts off. Then hit enter on the UART to see the string of events that took place. The bootloader and shutdown sequence should be recorded. Post that entire log here.
 
Yes you can! Patch the Syscon and run the DIAG-GND wire, that way you will be able to issue the commands "tmp 0", "tmp 1" and so on. One of those is for the CELL temperature sensor. You can also run "powerstate" to get the availability of the RSX/CELL sensors. They're unavailable on my shorted-out COK-002 which brings us to...

I'm in internal mode (I feel like Neo in The Matrix!!)

I get this:
upload_2022-5-26_21-57-40.png


This is with the PS3 in standby.
Does that mean BOTH my temp control chips are faulty or is that normal for an idle PS3?

Edit:
No, if I issue the powerstate WHILE it's trying to boot up I get AVAILABLE.
upload_2022-5-26_22-3-22.png


Ok so the temp sensor is only working when the PS3 is powered up!
I managed to get 81 degrees reported from the Cell. It's not 127 - the maximum reported? - that is telling me that maybe the CPU is actually getting to that temp for lack of dissipation.

upload_2022-5-26_22-5-39.png


Any inputs?
 
Last edited:
Thanks Felix!

I now managed to read a 63 degrees so it seems the sensor is working ok (if it wasn't I'd expect a stuck high value). So I guess the next step is to delid :)
 

Similar threads

Back
Top