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

[bizarrewitness]

W

Here you gan go for it but be careful mine was dead bricked at 950mhz

650/800
https://1fichier.com/?hzv8bybgiug9kxvpp9xw
650/850
https://1fichier.com/?449b7i5f97mz11oaq3nn
650/900
https://1fichier.com/?cm83n2e2nigk3l04dxhj
650/950
https://1fichier.com/?70ec1volz1zngdqaoeh6
650/1000
https://1fichier.com/?jzqiwk76tqkuc714jnve

Heres also a OneDrive Folder with other https://onedrive.live.com/?authkey=!AN83IKuHqhsAdsI&id=6C17BE77EAA9E82E!24688&cid=6C17BE77EAA9E82E

Thank you, I will start testing slowly. My model might fair a little better since it's a 25xx but I will be very cautious as I reach 900...

 

[Mitsu™]

just as always, no offense! I am just the direct guy, sorry

nonsense, don't spread misinformation by speculation. it is all about RSX, which is incredibly sensitive

I admit not to know much about hardware flashers.
It's just that I thought "resurrecting" a PS3 with it was simpler than that.
Sorry ^^'

Edit : I erased it. I don't want to spread misinformation at all

 

[haxxxen]

@Mitsu™
sorry, wasn't meant that harsh. removing your post, will lead into my nonsense, lol.

press repeat...
as long as you can access the flash correctly with hardware flasher, you are fine. dunno what goes on with RSX and how it comes to this behaviour, but I can tell you for sure, I was one of the early lucky ones who has used E3Flasher and never had any problems (using the clip without soldering the 48 orso cables). as soon as you solder, it is another story...hate electrics

 

[ryeno]

Damn... Another bricked PS3
I hope you'll find a solution.


Unfortunately, this trick won't work in this situation, as the firmware is stored in the console itself :\

On my side, my CECH-2004B (RSX code : CXD2991EGB / Date code : 9C) seems able to do 700MHz core/900MHz VRAM.
I will test some games.
I won't push it any further, 950MHz would not be stable and I don't need a second door wedge ^^ /QUOTE]

How do we find the RSX code?
I'm also running 700_900 on my consoles to be safe.

 

[Mitsu™]

@Mitsu™
sorry, wasn't meant that harsh. removing your post, will lead into my nonsense, lol.

I didn't take it badly, don't worry ^^'
You're probably right. At worst, we can still see what you were referring to in the quote.

press repeat...
as long as you can access the flash correctly with hardware flasher, you are fine. dunno what goes on with RSX and how it comes to this behaviour, but I can tell you for sure, I was one of the early lucky ones who has used E3Flasher and never had any problems (using the clip without soldering the 48 orso cables). as soon as you solder, it is another story...hate electrics

Understood. This is reassuring !

Otherwise, you know, I'm learning as I go.
I had my first ps3 less than a year ago, so this modding scene is pretty new to me. That said, I love learning.

 

[ryeno]

W


Thank you, I will start testing slowly. My model might fair a little better since it's a 25xx but I will be very cautious as I reach 900...

Like I said. I would start by testing core: 650_800 > 700_800 > 750_750. then once you found the max safe core go on to overclocking memory.

 

[Mitsu™]

How do we find the RSX code?
I'm also running 700_900 on my consoles to be safe.

You can find this information directly on the IHS, but you will need to reapply thermal paste if you want to check this.

Maybe there is a simplest method to get it ? I don't know.

 

[bizarrewitness]

am i supposed to revert to ofw before changing cfw? I was already on cex 4.91 and i went through the steps of installing the pex pup file but it shows i'm still on 4.91 cex.

 

[ryeno]

am i supposed to revert to ofw before changing cfw? I was already on cex 4.91 and i went through the steps of installing the pex pup file but it shows i'm still on 4.91 cex.

install
Download: CFW Evilnat 4.91.2 Cobra 8.5 BETA6 [PEX] [CEX] [OC]

 

[bizarrewitness]

install
Download: CFW Evilnat 4.91.2 Cobra 8.5 BETA6 [PEX] [CEX] [OC]

yeah, that's what I downloaded and installed but on the webman mod overlay it still says 4.91 CEX Cobra 8.5 and 600MHz/750MHz. I might just revert to ofw and do it all over again.

 

[ashura]

hi guys its really interesting to see all of these tests that you are doing i want to see if there is a chance that you guys have a cfw cex only not PEX from evilnat 4.91 under frequencies 750/750 mhz i would like to test it on my current ps3 slim, ussually im on standard OC 600/750mhz it goes really good and my temps are basically the same but also i was wondering if the frequencies are alsog taking too much watts from the power source, do you have by any chance as well any tests regarding power consumption on these frequencies? i will really appreciate it

 

[ryeno]

yeah, that's what I downloaded and installed but on the webman mod overlay it still says 4.91 CEX Cobra 8.5 and 600MHz/750MHz. I might just revert to ofw and do it all over again.

that's normal
now install a custom OC update, start with 650_800 and test in demanding games. I like Black Flag.

 

[bizarrewitness]

that's normal
now install a custom OC update, start with 650_800 and test in demanding games. I like Black Flag.

welp, i already started the process of reverting to ofw lol. i get it now though. i forgot it's pex cex and not just pex... time to reinstall cfw.

i don't have black flag but i do have bioshock infinite. i'll see what other games have been tested from other people but it seems like some of the main ones to test are Crysis (3), God of War Ascension, Bioshock Infinite, and The Last of Us.

 

[LuanTeles]

So Guys i actually got new Info's about my CECH2004A Date Code 9C for you, today the console died permanently

I was trying to get the maximum she can do with the Overclock, my GPU does not go over 650 Clock when i go to 700 it gives me a XMB Freeze, the Maximum is 650 Clock on GPU

The VRAM Clock can go to 900 so i tried to put it on 950 after the install i got a Black Screen but Sound in background XMB, i turned off the console and i wanted to go into the Recovery Menu but i also got a Freeze in there but first i saw a picture from the Message that say turn on the controller and press home button, after i tried it i realized i got a Frozen picture in recovery after that i tried to go back in Recovery but there was also a Black Screen. So i opened the Console and tried to Flash my Backup on the Nor Chip with my E3 Hardware Flasher i tried it several times about 6-8 Times but nothing happens i didnt get a Picture on my Monitor but the console stays always active. I have no USB and no Picture so i think the VRAM overclock from 950 was to much and it killed my VRAM totally also guys for the Future, if you have a CECH2004A Model with Date Code 9C, dont go over 900 VRAM Clock it will kill you VRAM i think the Console is dead i hope i can help with my Info's keep going guys <3

If you have sound on XMB, you can try to blindly update your FW.

I don't think your VRAM died. In our tests and with the logs provided by Haxxxen, it seems like there isn't enough power supply for it. Try to provide us with a syscon log.

Personally, i think your console can be recovered as you can still hear that the XMB is working.

Thats how i handle it so far. Unless @LuanTeles made the github by now

I'll make one today.

Update

@JoeSapecudo's system runs 900/1000 better than mine, but on Crysis, it randomly crashes after some minutes (It's rare, but it is happening). Therefore, we should assume that the latest stable clocks for 2511X are 850/1000. Although it works fine for most of the game, Crysis and GOW are experiencing these issues, so it's better to keep everything 100% stable.

I don't think it's worth pushing to 950 core, at least on our consoles. It may become stable in the future on Super Slim models, but I do believe we can still push the memory further. We haven't observed any artifacts in our systems, and overclocking the memory is providing a greater FPS boost than overclocking the core.

I'll create an updated table soon.

Important notes:

Keep in mind to observe the following:

If your console is reaching the memory clock limit, it will start artifacting. If you notice this happening, DO NOT push it further, as it will 100% brick your PS3.

If your console is reaching the core clock limit, it will crash in RSX-extensive games such as Crysis and GOWs. We haven't had any consoles bricked due to the core.

And, of course, test only incrementing by 50MHz each time.


One question:

If you've tested, let's say, 700/1000 and it worked, could we assume that the 1000MHz memory will work in all core speeds, right? As I could see, if a memory clock is supported, it will work just fine at every core speed, so there is no need to start from scratch in the next core increment.

 

[Mitsu™]

hi guys its really interesting to see all of these tests that you are doing i want to see if there is a chance that you guys have a cfw cex only not PEX from evilnat 4.91 under frequencies 750/750 mhz i would like to test it on my current ps3 slim, ussually im on standard OC 600/750mhz it goes really good and my temps are basically the same but also i was wondering if the frequencies are alsog taking too much watts from the power source, do you have by any chance as well any tests regarding power consumption on these frequencies? i will really appreciate it

Regarding power consumption, the only test I've seen is this one, made by Quake. Just for 600/750 OC, though.

My tests with 600/750 RSX CFW 4.90 on a slim using a killawatt showed no power consumption increase, and a 10-20% increase in performance.

20% increase in yamagi quake 2 alpha v0_02
20% increase in bioshock infinite

cech2501, 40nm? 500gb ssd, cfw,
2+ hours RDR1 idle, 36% fan cpu 61 gpu 65
1hr+ last of us 36% fan cpu 60 gpu 67, killawatt: 76W
stock is 3.2/500/650
xmb idle @ Users
55C cpu 59C gpu fan speed 36%, killawatt: 68W
Bioshock infinite complete edition, easy difficulty, unlocked framerate, after intro boat idle:
cpu 57.5 gpu 65C fan 36%
33 FPS, killawatt: 73W




CFW Evilnat 4.90 Cobra 8.4 [PEX] [CEX] [OC].PUP:
3.2/600/750
rdr1 start,singple player, without saving, 60cpu 66 gpu
LoU 36% fan cpu58C gpu66C, killawatt: 75W
Bioshock infinite complete edition, easy difficulty, unlocked framerate, after intro boat idle:
39.x FPS, killawatt: 74W
xmb idle @ Users
55C 59GPU fanspeed 36%, killawatt: 66W

One question:

If you've tested, let's say, 700/1000 and it worked, could we assume that the 1000MHz memory will work in all core speeds, right? As I could see, if a memory clock is supported, it will work just fine at every core speed, so there is no need to start from scratch in the next core increment.

Well, I guess not.
Quoting iTzSweetTooth :

WHELP, I think I just bricked my PS3 2000 model, at first I tried the 700/900 and it did worked fine without any issue so I just wanted to go higher and tried 800/900 and after the update my ps3 goes black screen every time I start, but I can still hear the startup PS3 sound, is there any hope I can revive my PS3 or go lower firmware.

when you bricked your 2004B does it act the same as mine ?

 

[LuanTeles]

Well, I guess not.
Quoting iTzSweetTooth :

Well, i'm sure his case is caused by the core, 200X max core is 700 he jumped straight to 800 and the console is not bricked, as he can hear that the system is running, so it's a RSX problem.

As we could see.

Memory - Bricks
Core - Crashes, and in extreme cases - no image at all with a working system.

 

[ryeno]

Update

@JoeSapecudo's system runs 900/1000 better than mine, but on Crysis, it randomly crashes after some minutes (It's rare, but it is happening). Therefore, we should assume that the latest stable clocks for 2511X are 850/1000. Although it works fine for most of the game, Crysis and GOW are experiencing these issues, so it's better to keep everything 100% stable.

I don't think it's worth pushing to 950 core, at least on our consoles. It may become stable in the future on Super Slim models, but I do believe we can still push the memory further. We haven't observed any artifacts in our systems, and overclocking the memory is providing a greater FPS boost than overclocking the core.

I'll create an updated table soon.

Important notes:

Keep in mind to observe the following:

If your console is reaching the memory clock limit, it will start artifacting. If you notice this happening, DO NOT push it further, as it will 100% brick your PS3.

If your console is reaching the core clock limit, it will crash in RSX-extensive games such as Crysis and GOWs. We haven't had any consoles bricked due to the core.

And, of course, test only incrementing by 50MHz each time.


One question:

If you've tested, let's say, 700/1000 and it worked, could we assume that the 1000MHz memory will work in all core speeds, right? As I could see, if a memory clock is supported, it will work just fine at every core speed, so there is no need to start from scratch in the next core increment.

I have the opposite experience. In Black Flag, unstable core results in glitchy geometry but unstable memory results in a hard crash and likewise unstable memory results in the PS3 freezing when opening a game.

1000 memory is not stable on all systems. so far 650_900 has been the min stable for all systems.

 

[LuanTeles]

I have the opposite experience. In Black Flag, unstable core results in glitchy geometry but unstable memory results in a hard crash and likewise unstable memory results in the PS3 freezing when opening a game.

That's interesting, totally the opposite of what we are experiencing since the past few weeks

 

[bizarrewitness]

Update

Important notes:

Keep in mind to observe the following:

If your console is reaching the memory clock limit, it will start artifacting. If you notice this happening, DO NOT push it further, as it will 100% brick your PS3.

If your console is reaching the core clock limit, it will crash in RSX-extensive games such as Crysis and GOWs. We haven't had any consoles bricked due to the core.

And, of course, test only incrementing by 50MHz each time.

Hey Luan, so you suggest figuring out memory clock limit first and then core? or other way around?

 

[LuanTeles]

Hey Luan, so you suggest figuring out memory clock limit first and then core? or other way around?

Well, I'm not sure anymore, as @ryeno reported the opposite of what we are experiencing in the past few weeks.

But yes, start with 650 core and increment the memory by 50 MHz, then test it on RSX-extensive games. When you start seeing artifacts or wrong geometry, do not push the memory further at ANY core speed, and then start pushing the CORE.
Begin again with the memory, just because it's better to be safe than sorry, but never go beyond the memory clock that gave you artifacts.

Also, since we can overclock the memory higher than the RSX, it is boosting the FPS significantly more than the RSX. Do not worry if you can't push the core as much, as the memory is playing the major role here.