PS3 Syscon fault codes

J

Jarod A

Member
Hey All,

I have connected to the syscon chip (SW3) on my super slim to retrieve the error codes... Many thanks to NSC and Paco btw!!!... but I can't find any list to understand the errors I have retrieved from the log.... Anyone know where I can find that info? Thanks.
 
Does nobody know this info? ... or am I asking the wrong question, or posting in the wrong place?.... As you can see, I am a noob...

The fault codes are 3034 and 4322

Looking at another post with the same problem, it seems like it might be a faulty voltage regulator may have fried the wifi/bluetooth chip. as I have ruled out a faulty power supply...

But the whole idea of pulling the codes from the syscon chip is to actually gather info on the fault right, rather than guess...

I could use some help here...
 
5 days, 90 views and no-one knows this info?

I was given to understand (by whom I thought was a very well informed PS3 source) that you guys here were the best on the net in regards to info on console fixes...

That's literally why I signed up to this forum... because my favorite hobby is tinkering with this kind of stuff, and feeling the satisfaction of getting a dead console running again... But I'm not an expert, and I was hoping to get the occasional help from people who were...

I see a lot of piracy stuff... Is there no-one here who know console repair????? or is this Psx place just a hacking site...
 
pinky said:
you might have better luck in the syscon error codes thread. I think it's stickied. one of those error codes looks familiar, the 3034 one.

edit: https://www.psx-place.com/threads/f...and-error-reporting.30100/page-70#post-298097
Click to expand...
THANK YOU for replying... That info doesn't help with the fault codes I've listed above (and I'm not dealing with a ylod failure on this occasion), but I really appreciate you taking the time to try to help... I do have a couple of cech-c ylod consoles I'll be getting to, so that info may well be valuable in the future. Thanks again...
 
I'm afraid I can't help much, personally. I haven't had a ylod system except for when I bought a phat bc system. this was in the early days of 3.55 where you still had to use swap magic 3.6 or 3.8 on the system. I still own those discs. anyway, it ylod on me within 8 minutes of being turned on. I spent like $200 or a little more on the system, so I returned it. I shouldn't be made to fix something when I paid a premium price for it. anyway, I do read the syscon errors thread even though I have no experience with it. one of those errors sounds familiar, so I'd recommend you post there or I could report your thread and ask it be moved to that thread (merged) or you could do that yourself. it's your choice. :)
 
pinky said:
I'm afraid I can't help much, personally. I haven't had a ylod system except for when I bought a phat bc system. this was in the early days of 3.55 where you still had to use swap magic 3.6 or 3.8 on the system. I still own those discs. anyway, it ylod on me within 8 minutes of being turned on. I spent like $200 or a little more on the system, so I returned it. I shouldn't be made to fix something when I paid a premium price for it. anyway, I do read the syscon errors thread even though I have no experience with it. one of those errors sounds familiar, so I'd recommend you post there or I could report your thread and ask it be moved to that thread (merged) or you could do that yourself. it's your choice. :)
Click to expand...

I'm actually super inexperienced in forums, so I don't know how to do most of that. I did notice after I replied that the link you sent me was on page 70, so I went back to page one and started reading... It seem that the 3034 error might be a dry solder ball on the RSX, so that is awesome info, perfect. I will definitely post there with any queries in the future... Thank you so much for directing me to that resource, it looks to be exactly what I need to try to start understanding this stuff....
 
Coro said:
where? use the report link found on every post to let me know and it will be removed.

goto the first post in the thread that @pinky linked to and goto the github link. there is pdf there with some codes.
Click to expand...
In that comment I'm referring to hacking the firmware of current gen consoles like the PS4 to allow pirated games... I don't personally use aftermarket firmware, and I have no problems with it once a manufacturer stops selling their hardware... But it's obvious that's what some of these applications are for... enabling the ability to play copied disks and isos right?

pinky said:
oh, yeah, sorry about that. I just found the thread, entered it, then copied and pasted.
Click to expand...
Hey, don't worry about it... I'm just super grateful you took the time to reply and help... Thanks again...
 
Last edited by a moderator:
Jarod A said:
enabling the ability to play copied disks and isos right?
Click to expand...
who says the discs need to be pirated? i do not have a ps4, but all my ps3 discs are safely hidden from kids with sticky fingers. one of ps3's will not read discs at all and another has the broken drive completely removed. these consoles would be useless without hacking.

fan control is the only thing keeping my superslim ps3 from dying. i test some HEN stuff on it but otherwise only watch TV shows and movies...using Movian and dvd rips because, again, kids that destroy discs.

it is all in how you use it. that is why we have site rules, to dictate how the site is used. :)
 
Coro said:
who says the discs need to be pirated? i do not have a ps4, but all my ps3 discs are safely hidden from kids with sticky fingers. one of ps3's will not read discs at all and another has the broken drive completely removed. these consoles would be useless without hacking.

fan control is the only thing keeping my superslim ps3 from dying. i test some HEN stuff on it but otherwise only watch TV shows and movies...using Movian and dvd rips because, again, kids that destroy discs.

it is all in how you use it. that is why we have site rules, to dictate how the site is used. :)
Click to expand...

Hey, totally agree... there's a genuine use case for honest people... I'm thinking of installing hen on my ps3's just for the temps and fan control myself... But it's also obviously used by heaps of people to pirate games etc, in fact that's why they have it installed is my point... The software facilitates piracy, that's just a plain fact. It actually sucks that sony doesn't do a better job allowing things like temp monitoring and fan control, and they make it a nightmare to do a simple thing like buy and install a new drive... if you can buy one that is, in the case of the PS3...
 
Jarod A said:
Hey All,

I have connected to the syscon chip (SW3) on my super slim to retrieve the error codes... Many thanks to NSC and Paco btw!!!... but I can't find any list to understand the errors I have retrieved from the log.... Anyone know where I can find that info? Thanks.
Click to expand...

Simple answer is we dont know what the latest syscon codes are! Only sony can tell you or get a leaked copy of their factory debug manual

If you figure out what they are then contribute to the syscon error code thread i started.

All i can say judging from your errors, the RSX is having data errors, so possible bga solder problems or faulty RSX chip
 
Hey, thank you for the reply...

This is literally the first console I've read the syscon chip on, so I'm an utter noob...

I noted on the first page of your thread, that a 3034 could be a dried solder ball on the rsx...

But the pdf I found says a 3034 error is a cell be error... Is that right?

I do note that the 4322 IS an rsx error... my syscon error list is just these two errors over and over... so is it a case of the dried solder ball causing the 4322 error, and the 3034 error just comes naturally after the rsx error?

I've got to tell you that this is absolutely overwhelming in it's confusion for a beginner trying to understand these codes...

Thanks again for taking the time to reply
 
db260179 said:
Simple answer is we dont know what the latest syscon codes are! Only sony can tell you or get a leaked copy of their factory debug manual

If you figure out what they are then contribute to the syscon error code thread i started.

All i can say judging from your errors, the RSX is having data errors, so possible bga solder problems or faulty RSX chip
Click to expand...

I wonder if these repeating 4322/3034 errors are being recorded on the syscon chip when the console gets powered up... and then just goes dead.
Pretty sure (haven't tested yet) there's a short on the board with the regulator to the wifi, causing the power off... and it would explain the same repeating errors in the syscon log... I'm attempting a repair, so if it runs, it might be the cell/rsx are ok after all...

and those errors are just from the weird shutdown...
 
You must log in or register to reply here.

Similar threads

Back
Top