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

That's all normal, as expected. So the console is booting and everything that's supposed to be powered on is. The console should be in XMB and displaying. What do you get when you plug in AV cable?
I get absolutely nothing either through hdmi or a standard AV cable. I do notice that the HDD light turns solid just before shutting down though

*edit: I notice when I use the bringup command that it beeps once like normal and then a couple seconds after it beeps once more. Is that normal when everything is hooked up like this?

Sent from my SM-G965U using Tapatalk
 
I get absolutely nothing either through hdmi or a standard AV cable. I do notice that the HDD light turns solid just before shutting down though

*edit: I notice when I use the bringup command that it beeps once like normal and then a couple seconds after it beeps once more. Is that normal when everything is hooked up like this?

Sent from my SM-G965U using Tapatalk
Let me recap what version of software have you installed last time?
 
I get absolutely nothing either through hdmi or a standard AV cable. I do notice that the HDD light turns solid just before shutting down though

*edit: I notice when I use the bringup command that it beeps once like normal and then a couple seconds after it beeps once more. Is that normal when everything is hooked up like this?

Sent from my SM-G965U using Tapatalk
Yes, the extra beep is normal doing it this way. Questions:
  1. Did you remember to plug the battery back in? If so measure the voltage to verify it's bad. Do you have access to another one on hand to test?
  2. Did you clear the errorlog and wait for it to shut down on it's own again?
  3. What did the error log capture after the console shut down?
  4. Do you have another HDD you can test?
 
I had quite similar issues back with years. I have tried from recovery many fw. Take out hdd and formatting on pc and try going on recovery mode.
Waiting to see what happens.
It did not work straight to high fw there are some patch levels with those fw not sure why probably the otheos issus.
 
Yes, the extra beep is normal doing it this way. Questions:
  1. Did you remember to plug the battery back in? If so measure the voltage to verify it's bad. Do you have access to another one on hand to test?
  2. Did you clear the errorlog and wait for it to shut down on it's own again?
  3. What did the error log capture after the console shut down?
  4. Do you have another HDD you can test?
1: yes its plugged in but I can swap it out.

2: yes I cleared it and let the console do its thing a few times.

3: no new errors show up after 3 cycles.

4: yes I have a spare I can swap in. Do I need to do anything to it before hand?

Sent from my SM-G965U using Tapatalk
 
Can't remember which one fixed units, had more from Greece. All around 2.30. Now looking over last otheros ofw should start unit back. It's kind of rsod. So unit was delided on both cpu/gpu?
If so is fw related.
 
Can't remember which one fixed units, had more from Greece. All around 2.30. Now looking over last otheros ofw should start unit back. It's kind of rsod. So unit was delided on both cpu/gpu?
Are you talking about my console? No it hasn't been delidded yet. Only regular thermal paste

Sent from my SM-G965U using Tapatalk
 
I don't want to be rude but I know what I'm speaking.
616d2778b8602bdcda4c01622bee3f4e.jpg
 
I don't want to be rude but I know what I'm speaking.
616d2778b8602bdcda4c01622bee3f4e.jpg
Hey I dont doubt it, thats why I'm here lol getting help from the people that know what they're talking about and deal with it on the daily. I usually delid my ps3s anyways because I know how bad old thermal paste can get and it will eventually become an insulator instead of a conductor of heat.

Sent from my SM-G965U using Tapatalk
 
Just looked at your errlog. The timestamps go back to 2008 and the errors and dates jump in discrete steps. The last 3 1001s have no timestamp, consistent with the dead batt. Replace that.

You said you did clear the log, but were there no errors generated?Cuz you didn't post the log?

Anyway, replace the batt. Try to boot and press the x/start buttons to try and get past the set date screen. You may not be able to see it.
 
Yes is like a thermal thert kind.
And if controller is paired with unit you have your fixing solution now after battery exchange and pushing buttons.
 
Just looked at your errlog. The timestamps go back to 2008 and the errors and dates jump in discrete steps. The last 3 1001s have no timestamp, consistent with the dead batt. Replace that.

You said you did clear the log, but were there no errors generated?Cuz you didn't post the log?

Anyway, replace the batt. Try to boot and press the x/start buttons to try and get past the set date screen. You may not be able to see it.
Currently replacing that as I type this and yes I didn't post the error log after clearing it because there's no errors showing.

And I'll try it again with a good battery in there. Last time I tried it wouldn't connect a controller but it may have been a bad cable I had

Sent from my SM-G965U using Tapatalk
 
Well I don't think is really cmos issues. It was if discharged completely, you can try one with 3v at least. But never seen battery issue on software side. This is hardware issue if sync controller does not work.
 

Similar threads

Back
Top