PS3 Project RSX Boost: Overclock your Retail PS3 RSX Speeds (ps3 cfw only)

I was blown away by the performance increase from 600 to 700 core already. And then when we got the option to OC memory, every step was another 3-4% increase in FPS in games like GT6, Bioshock Infinite etc., truly amazing what these machines are capable of considering they're 15 years old :D
That's because the chip matured so much from 90nm to 40nm and Sony had them underclocked to a measly 500/650 speeds to keep spec, that massive performance was left on the table. 40nm yields were pretty big. 200 extra on the core and 350 extra on memory is good stuff. Then using an SSD to speed up the loading times and responsiveness of the OS and fixing texture pop in and stutter in games is a recipe for greatness. PS3 still has more potential. If we can overclock the CPU one day, my god, the days of terrible framerates on PS3 are over.
 
That's because the chip matured so much from 90nm to 40nm and Sony had them underclocked to a measly 500/650 speeds to keep spec, that massive performance was left on the table. 40nm yields were pretty big. 200 extra on the core and 350 extra on memory is good stuff. Then using an SSD to speed up the loading times and responsiveness of the OS and fixing texture pop in and stutter in games is a recipe for greatness. PS3 still has more potential. If we can overclock the CPU one day, my god, the days of terrible framerates on PS3 are over.

Best decision ever was upgrading to an SSD! Shame that the PS3 has only SATA speeds, but nevertheless, the difference in some games is truly night and day. GTA V loading times are cut in half and almost all the texture pop-ins are gone!
I'm just sad I didn't pay 20€ more for 1TB... I have only 500 GB and I cant' fit many games on it :')
 
Best decision ever was upgrading to an SSD! Shame that the PS3 has only SATA speeds, but nevertheless, the difference in some games is truly night and day. GTA V loading times are cut in half and almost all the texture pop-ins are gone!
I'm just sad I didn't pay 20€ more for 1TB... I have only 500 GB and I cant' fit many games on it :')
A 1tb would have been better. I already have me PS3 1tb Samsung SsD filled up. Christ I wish PS3s supported 2tb minimum instead of only 1tb. There's so many games I want to load up on it. I want to make it an ultimate PS3. And even with Sata 1 the speeds are still big. And xmb and overall system is snappy and dont have hang ups like when you use HDDs. It's proof that by the time 7th gen came along, hard drives were already annoying and bad. Sadly back then ssds were high end enthusiast grade parts. Now they are common and affordable. And also has big storage.
 
Hello fellas. Want to share my results (thanks to Mitsu for СFW) : CECH-2508B (0D). Stable work at Core750/VRAM950. Glitches and artifacts at 800 GPU core clock. Maybe my console can more at VRAM, but i dont wanna risk to brick my console and I doubt that this will give more performance.
P.S Need for Speed Carbon and Battlefield Bad Company (need to download config file from Nexus mods) also have unlocked framerate and good to test the overclock.
P.P.S after update to overclocked CFW i noticed some sounds and voices in some game are disapper. How ca i fix it?
If 950MHz VRAM is perfectly stable, you're right to not push it further. There won't be a huge FPS difference.
A brick can occur so easily/abruptly nearing 1000MHz...

About the sound issue, this is the first time I've heard of these kinds of problems.
Are you sure it's not the fault of these config files ?
Please 750/900 Beta 9 pex

To anyone reading this :
For testing purposes, use the previous Beta 8 .PUP.
https://app.mediafire.com/0uxvp5ismnjwm
If the file you're searching isn't already made, then ask me.
Once you've found your limits, feel free to ask an updated version.

750/900 EVILNAT 4.91 BETA 9 PEX
https://www.mediafire.com/file/qsxlvsf286vur6c/750_900_BETA9_PEX.PUP_4.91.CEX-PS3UPDAT.zip/file

I also remind you that this tutorial exists ;)
(If you really can't make it work, then it's ok. There are many compatibility issues it seems, so ask me.)

Another reminder for our new testers :
Please dump your LV1 (in Evilnat options, search for the "Extract" category), search this kind of string and share it here.
Code:
rsx65 a06 650/900 vpe:ff shd:3f [K4A049400:1:2:16:c:c:3:8:2] [1c:0:2:0:1:2:0] [2:1:0]
It's easy, just search for your RSX speeds with any Hex editor and you will find it. In some HEX programs, you'll need to do a "back search" for it.
Screenshot_2024-05-20-15-28-53-235_com.myprog.hexedit.jpg
 
Last edited:
A 1tb would have been better. I already have me PS3 1tb Samsung SsD filled up. Christ I wish PS3s supported 2tb minimum instead of only 1tb. There's so many games I want to load up on it. I want to make it an ultimate PS3. And even with Sata 1 the speeds are still big. And xmb and overall system is snappy and dont have hang ups like when you use HDDs. It's proof that by the time 7th gen came along, hard drives were already annoying and bad. Sadly back then ssds were high end enthusiast grade parts. Now they are common and affordable. And also has big storage.
You can still use a big external HDD. I have a total of 296 games on my PS3
 
Damn a 2511A for the first time on here not hitting 850 or more? Though I don't know how the manufacture month works cause that's what matters. Is that PS3 manufactured January of 2011?

I think mine is from July 2010, 3.40 minimum firmware.
 
Last edited:
I have already tested my 2501a on 750-950 for over 2 weeks and it is stable

Is it safe to test 750-975?
You were lucky to have got a stable 750 core, my PS3 that was newer than yours choked with 750, I don't know why, as it was supposed to handle at least 800.
about 975 I don't think you should, because it's a risk of killing your PS3, but if you like riches, go ahead.
 
Respect Bro and we all appreciate the work! @Mitsu™
If 950MHz VRAM is perfectly stable, you're right to not push it further. There won't be a huge FPS difference.
A brick can occur so easily/abruptly nearing 1000MHz...

About the sound issue, this is the first time I've heard of these kinds of problems.
Are you sure it's not the fault of these config files ?


To anyone reading this :
For testing purposes, use the previous Beta 8 .PUP.
https://app.mediafire.com/0uxvp5ismnjwm
If the file you're searching isn't already made, then ask me.
Once you've found your limits, feel free to ask an updated version.

750/900 EVILNAT 4.91 BETA 9 PEX
https://www.mediafire.com/file/qsxlvsf286vur6c/750_900_BETA9_PEX.PUP_4.91.CEX-PS3UPDAT.zip/file

I also remind you that this tutorial exists ;)
(If you really can't make it work, then it's ok. There are many compatibility issues it seems, so ask me.)

Another reminder for our new testers :
Please dump your LV1 (in Evilnat options, search for the "Extract" category), search this kind of string and share it here.
Code:
rsx65 a06 650/900 vpe:ff shd:3f [K4A049400:1:2:16:c:c:3:8:2] [1c:0:2:0:1:2:0] [2:1:0]
It's easy, just search for your RSX speeds with any Hex editor and you will find it. In some HEX programs, you'll need to do a "back search" for it.
View attachment 43128

I've decided to do one more experiment to confirm one thing about OC, I played for 6 hours, GTA V with 750/1000Mhz temps play a very huge role on our current project, I think I'm going to keep this and 975MHz for 2504B I want to also order the best thermal paste for my chips and I see pads were also mentioned somewhere. I think I can go higher core with cool temps I was at 800/950 only Shift 2 and Crysis artifacts I also accidentally renamed the wrong OC with the wrong name. i accidentally did 850/900 but then immediately reverted to my usual OC but I was able to load everything without a slight sign of instability or freeze at xmb. I noticed when i was installing 4k that I flashed wrong pup thankfully lol after I sort those out then I'm back to experimenting with higher clocks! :) :D
Screenshot_20240521_190846_Gallery.jpg
 

Attachments

  • Screenshot_20240521_190852_Gallery.jpg
    Screenshot_20240521_190852_Gallery.jpg
    329.2 KB · Views: 39
Last edited:
What's the
If 950MHz VRAM is perfectly stable, you're right to not push it further. There won't be a huge FPS difference.
A brick can occur so easily/abruptly nearing 1000MHz...

About the sound issue, this is the first time I've heard of these kinds of problems.
Are you sure it's not the fault of these config files ?


To anyone reading this :
For testing purposes, use the previous Beta 8 .PUP.
https://app.mediafire.com/0uxvp5ismnjwm
If the file you're searching isn't already made, then ask me.
Once you've found your limits, feel free to ask an updated version.

750/900 EVILNAT 4.91 BETA 9 PEX
https://www.mediafire.com/file/qsxlvsf286vur6c/750_900_BETA9_PEX.PUP_4.91.CEX-PS3UPDAT.zip/file

I also remind you that this tutorial exists ;)
(If you really can't make it work, then it's ok. There are many compatibility issues it seems, so ask me.)

Another reminder for our new testers :
Please dump your LV1 (in Evilnat options, search for the "Extract" category), search this kind of string and share it here.
Code:
rsx65 a06 650/900 vpe:ff shd:3f [K4A049400:1:2:16:c:c:3:8:2] [1c:0:2:0:1:2:0] [2:1:0]
It's easy, just search for your RSX speeds with any Hex editor and you will find it. In some HEX programs, you'll need to do a "back search" for it.
View attachment 43128
what's the point of people dumping their lvl 1 dumps anymore?
 
What's the

what's the point of people dumping their lvl 1 dumps anymore?
As far as I'm concerned, I don't need it, but the more data we gather the better it will be to draw conclusions and know a little better the limits of the different models I guess.
RIP-Felix also asked for the SYSCON logs btw.
This is still an experiment thread after all.
 
As far as I'm concerned, I don't need it, but the more data we gather the better it will be to draw conclusions and know a little better the limits of the different models I guess.
RIP-Felix also asked for the SYSCON logs btw.
This is still an experiment thread after all.
We already know the limits. For weeks now. 65nm chips can't exceed 650 on core. 90nm 600 core. 40nm 700-900 core. 40nm is the one that has the most variance depending on the month. The latest 2501A and 2501B models do the highest OC. 65nm on memory can do 800 or 850 on memory, will depend. 90nm just 750. 40nm 900 at the lowest guaranteed. All my PS3 slims, all 8 of them, do 950 100% stable easily. And I have recently pushed them to 975 and are solid stable as well. Pushing the 1000 mark is where all the issues arise. 1000 is just not good. 25xx models are just the only models you want for OC. 700/950 guaranteed is a huge OC from stock. There's nothing new to learn about the models and OC. So far we know, 950 core fully stable is just not possible. 900 fully stable is a miracle on one of my 3 850 core PS3s. My best is 900/975 right now. That's a 2011 model. Those will be the peak of cfw capable OC. What I want to learn is how and why, some of these chips do such high OC.
 
We already know the limits. For weeks now. 65nm chips can't exceed 650 on core. 90nm 600 core. 40nm 700-900 core. 40nm is the one that has the most variance depending on the month. The latest 2501A and 2501B models do the highest OC. 65nm on memory can do 800 or 850 on memory, will depend. 90nm just 750. 40nm 900 at the lowest guaranteed. All my PS3 slims, all 8 of them, do 950 100% stable easily. And I have recently pushed them to 975 and are solid stable as well. Pushing the 1000 mark is where all the issues arise. 1000 is just not good. 25xx models are just the only models you want for OC. 700/950 guaranteed is a huge OC from stock. There's nothing new to learn about the models and OC. So far we know, 950 core fully stable is just not possible. 900 fully stable is a miracle on one of my 3 850 core PS3s. My best is 900/975 right now. That's a 2011 model. Those will be the peak of cfw capable OC. What I want to learn is how and why, some of these chips do such high OC.
*900MHz memory on 65nm is possible and completely stable on mine.
650 on core is accurate, even if some 20XX can do more (700) depending on the NEC Tokins health.

25XX models have 3 different RSX revisions. What would be interesting is to know exactly which revision we have in each model, associate them with dates and see how they respond to OC.
IMG_20240521_173634.jpg


Also, if we put a EADP-220BB or APS-250 power supply in a 25XX model, I wonder if they would be able to handle a bit more (since they should bring more stability overall).
EADP 200DB / APS-270 (21XX and 25XX) : 12V 16A (192W)
EADP-220BB / APS-250 (20XX) : 12V 18A (216W)

I'm currently trying to find a 25XX slim btw.
 
Last edited:
*900MHz memory on 65nm is possible and completely stable on mine.
650 on core is accurate, even if some 20XX can do more (700) depending on the NEC Tokins health.

25XX models have 3 different RSX revisions. What would be interesting is to know exactly which revision we have in each model, associate them with dates and see how they respond to OC.View attachment 43140

Also, if we put a EADP-220BB or APS-250 power supply in a 25XX model, I wonder if they would be able to handle a bit more (since they should bring more stability overall).
Base values (25XX) : 12V 16A (192W)
EADP-220BB / APS-250 (20XX & 21XX) : 12V 18A (216W)

I'm currently trying to find a 25XX slim btw.
One of my JSD boards say 1-882-770-21. I took pics. Also my PS3s only ever have APS-270 or EADP 200DB psus. Are you in the states? Or outside the US? Also my gpu says CXD5300GGB
 
Last edited:
One of my JSD boards say 1-882-770-21. I took pics. Also my PS3s only ever have APS-270 or EADP 200DB psus. Are you in the states? Or outside the US? Also my gpu says CXD5300GGB
I've updated the picture, "1-882-770-21" is there indeed.
"APS-270" or "EADP 200DB" PSUs are what you will find in every 21XX and 25XX slims across the world.
Those I speak of are only present in the 20XX models (the region doesn't matter) and can deliver more(/handle more) since they were designed to work with the demanding 65nm RSX.

See :
Sans titre 388_20240521181300.jpg
(I'm from France btw)
 
I've updated the picture, "1-882-770-21" is there indeed.
"APS-270" or "EADP 200DB" PSUs are what you will find in every 21XX and 25XX slims across the world.
Those I speak of are only present in the 20XX models (the region doesn't matter) and can deliver more(/handle more) since they were designed to work with the demanding 65nm RSX.

See :
View attachment 43142 (I'm from France btw)
that could be a nice experiment, just a small fyi my 2504b has a EADP-185AB since my aps270 fried (wasen't oc related) and despite what the wiki says you can fit but it will be tight and it works wihout issue even with 700/925 oc so i also wonder if a beefier psu could lead to better oc
And im also from france if someone finds a ebay listing for a psu hit me up :)
 
that could be a nice experiment, just a small fyi my 2504b has a EADP-185AB since my aps270 fried (wasen't oc related) and despite what the wiki says you can fit but it will be tight and it works wihout issue even with 700/925 oc so i also wonder if a beefier psu could lead to better oc
And im also from france if someone finds a ebay listing for a psu hit me up :)
Hey salut ! :D

At worst try to find a cheap 20XX, they are super easy to find.
It'll make you spare parts on top of that !

Can someone please point me to the right post, dev wiki link...or whatever so I can learn to make the LV1 needed to add specific clocks to the MFW builder?

I want a 450/800 and so on.
You have to modify the "01_patch_rsx_oc.tcl" file in the "tasks" folder.

This is basic hexadecimal editing, it should be easy.

Code:
# RSX OC 500/650
  if {$::01_patch_rsx_oc::options(--patch-lv1-rsx-oc) == "Default - 500MHz / 650MHz"} {
            log "Patching LV1 hypervisor to overclock RSX to Default 500MHz / 650MHz"
   set search "\x0a\x02\x00\x00\x00\xa1\x00\x00\x00\x00\x00\x00\x1a\x04"
   set replace "\x0a\x02\x00\x00\x00\xa1\x00\x00\x00\x00\x00\x00\x1a\x04"
   set offset 0
   set mask 0 
   # PATCH THE ELF BINARY
   catch_die {::patch_elf $elf $search $offset $replace $mask} "Unable to patch self [file tail $elf]"
        }
Code:
# RSX OC 450/800
  if {$::01_patch_rsx_oc::options(--patch-lv1-rsx-oc) == "450MHz / 800MHz"} {
            log "Patching LV1 hypervisor to overclock RSX to Default 450MHz / 800MHz"
   set search "\x0a\x02\x00\x00\x00\xa1\x00\x00\x00\x00\x00\x00\x1a\x04"
   set replace "\x09\x02\x00\x00\x00\xa1\x00\x00\x00\x00\x00\x00\x20\x04"
   set offset 0
   set mask 0 
   # PATCH THE ELF BINARY
   catch_die {::patch_elf $elf $search $offset $replace $mask} "Unable to patch self [file tail $elf]"
        }
Don't forget to add these new values at the beginning of the file too.
 
Last edited:
Back
Top