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

I have a Cech-2504B 0C 320GB Slim. Dual boot with E3 Flasher. Minimal firmware 3.40.
Motherboard is JSD-001 or JTP-001. Temp 33% maximum 64 °C. My test:
700 900 was good
850 950 graphics errors already at power-on
750 1000 uncharted 3 freezes
700 1000 freezes at the logo, black image, a few green spots, sound was the first time
700 950 is still good
750 975 so far so good
I can't make my own mfw because the program gives me an error. (virtual win7 and retail win11)
I would like to try the following:
750 950
800 950
800 975
 
I have a Cech-2504B 0C 320GB Slim. Dual boot with E3 Flasher. Minimal firmware 3.40.
Motherboard is JSD-001 or JTP-001. Temp 33% maximum 64 °C. My test:
700 900 was good
850 950 graphics errors already at power-on
750 1000 uncharted 3 freezes
700 1000 freezes at the logo, black image, a few green spots, sound was the first time
700 950 is still good
750 975 so far so good
I can't make my own mfw because the program gives me an error. (virtual win7 and retail win11)
I would like to try the following:
750 950
800 950
800 975
You can't do more than 750 on the core bro. Test crysis HD. 750/950 if you don't see artifacts or crashes in 30 minutes to an hour of testing, then your OC is stable. If you see any artifacts at all or crashes, then you aren't stable. 800 core and 975 memory, you're just asking for a bricked PS3.
 
Would you have time to export the SYSCON log before it freezes ?

Firmware Version: 4.91 (build 50754)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)
Bringup Count: 1568, Shutdown Count: 1539
Runtime: 155 Days, 10 Hours, 8 Minutes, 51 Seconds
Error Log
01: A0801004 Sat Apr 1 22:40:09 2006
02: A0801004 Sun Mar 26 19:34:01 2006
03: A0802022 Fri Mar 24 11:38:19 2006
04: A0802022 Fri Mar 24 11:30:44 2006
05: A0801004 Mon Mar 20 17:42:03 2006
06: A0802022 Sun Mar 19 00:20:16 2006
07: A0802022 Sat Mar 18 22:36:04 2006
08: A0802022 Sat Mar 18 22:36:00 2006
09: A0802022 Sat Mar 18 22:08:57 2006
10: A0802022 Sat Mar 18 21:33:00 2006
11: A0802022 Sat Mar 18 21:23:39 2006
12: A0802022 Sat Mar 18 21:23:35 2006
13: A0802022 Sat Mar 18 19:55:33 2006
14: A0802022 Sat Mar 18 19:42:49 2006
15: A0802022 Sat Mar 18 19:35:44 2006
16: A0801004 Sat Mar 18 19:27:47 2006
17: A0802022 Sat Mar 18 19:26:20 2006
18: A0802022 Sat Mar 18 19:26:19 2006
19: A0802022 Sat Mar 18 18:41:04 2006
20: A0802022 Sat Mar 18 01:07:09 2006
21: A0802022 Sat Mar 18 01:06:04 2006
22: A0802022 Sat Mar 18 00:31:36 2006
23: A0802022 Fri Mar 17 23:27:00 2006
24: A0802022 Fri Mar 17 23:26:05 2006
25: A0802022 Fri Mar 17 23:21:57 2006
26: A0802022 Fri Mar 17 23:21:09 2006
27: A0802022 Fri Mar 17 23:20:20 2006
28: A0802022 Fri Mar 17 23:19:47 2006
29: A0802022 Fri Mar 17 23:18:59 2006
30: A0802022 Fri Mar 17 23:18:01 2006
31: A0802022 Fri Mar 17 23:17:02 2006
32: FFFFFFFF Fri Mar 17 23:13:05 2006
 
Firmware Version: 4.91 (build 50754)
Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Firmware Version: 0B8E.0000000000000006 (EEPROM: 0000000000000006)
Bringup Count: 1568, Shutdown Count: 1539
Runtime: 155 Days, 10 Hours, 8 Minutes, 51 Seconds
Error Log
01: A0801004 Sat Apr 1 22:40:09 2006
02: A0801004 Sun Mar 26 19:34:01 2006
03: A0802022 Fri Mar 24 11:38:19 2006
04: A0802022 Fri Mar 24 11:30:44 2006
05: A0801004 Mon Mar 20 17:42:03 2006
06: A0802022 Sun Mar 19 00:20:16 2006
07: A0802022 Sat Mar 18 22:36:04 2006
08: A0802022 Sat Mar 18 22:36:00 2006
09: A0802022 Sat Mar 18 22:08:57 2006
10: A0802022 Sat Mar 18 21:33:00 2006
11: A0802022 Sat Mar 18 21:23:39 2006
12: A0802022 Sat Mar 18 21:23:35 2006
13: A0802022 Sat Mar 18 19:55:33 2006
14: A0802022 Sat Mar 18 19:42:49 2006
15: A0802022 Sat Mar 18 19:35:44 2006
16: A0801004 Sat Mar 18 19:27:47 2006
17: A0802022 Sat Mar 18 19:26:20 2006
18: A0802022 Sat Mar 18 19:26:19 2006
19: A0802022 Sat Mar 18 18:41:04 2006
20: A0802022 Sat Mar 18 01:07:09 2006
21: A0802022 Sat Mar 18 01:06:04 2006
22: A0802022 Sat Mar 18 00:31:36 2006
23: A0802022 Fri Mar 17 23:27:00 2006
24: A0802022 Fri Mar 17 23:26:05 2006
25: A0802022 Fri Mar 17 23:21:57 2006
26: A0802022 Fri Mar 17 23:21:09 2006
27: A0802022 Fri Mar 17 23:20:20 2006
28: A0802022 Fri Mar 17 23:19:47 2006
29: A0802022 Fri Mar 17 23:18:59 2006
30: A0802022 Fri Mar 17 23:18:01 2006
31: A0802022 Fri Mar 17 23:17:02 2006
32: FFFFFFFF Fri Mar 17 23:13:05 2006
According to PSDevWiki :

PSDevWiki said:
1004 (Power AC/DC)
Components Involved:
Power Supply
When a console loses AC power, it may generate error A0801004. During the shutdown sequence, voltage regulators are turned off sequentially in reverse order to the Power On Sequence (POS). This allows components enough time to enter a power off state. It helps to prevents data corruption and voltage spikes or discharges that can damage sensitive components. 1004 errors commonly occur in machines that can power on but have graphical artifacts or no video, also known as GLOD. In such cases, the user has no choice but to improperly power off. Forcing a shutdown using the power rocker at the back of the console (for Phat models), or by pulling the power cord (for slim and super slim models) will cause an unexpected loss of AC power and prevent the SYSCON from completing the shutdown sequence.


This error may be disregarded if it occurred due to abnormal circumstances, such as a power outage or accidental unplugging. Since it did not result from a hardware malfunction, it is not a significant concern. If a console displays artifacts or the GLOD, the main issue should be addressed first, typically involving a GPU problem requiring a reball or replacement. Afterward, if 1004 errors reoccur, the AC/DC line, PSU, and its connection to the DC-DC converters should be diagnosed.

2022 (DVE)
DVE Error (IC2406, CXM4024R MultiAV controller for analog out)

This error occurs when you see no video out using HDMI on any Samsung Smart TV.

You can intentionally produce this error code by making the TV detect another console first (a PS4), turn off the TV, swap the HDMI cable from the PS4 to the PS3, and turning back on the TV. You can fix this error code by replugging it in while the TV is on.

This error is also present when the console produces graphical artifacts on the screen. The console freezes and cannot be used, forcing the user to turn off the console. This produces the 2022 error code and is an early sign of GLOD.
 
With your help I slowly went up, and I tested 700/900 on my ps3 version 2511A and it's stable, now what are the next steps you recommend for me safely?
 
Hey guys!

Small update:
My perfectly stable 700/1000 Slim is unable to do 700/1025. 1st time booting up the VSH froze immediatelly, all next boot attempts I got only sound.
Thankfully, I was able to revert to 700/1000 via recovery menu, I can consider myself lucky and "smart" for going 1025 first and not 1050 on the 1st try, I'm sure even recovery menu wouldn't work in 1050 memory.
This just goes to show that even having a perfectly working system, the next step might be a killer :bitsbubba:

Attached is an image of what the recovery menu looked like when I managed to install the 700/1000 PUP, for the 3rd time (2 times it failed at different percentages), attached also proof that I got it to work again, phew!
IMG_20240519_165244.jpg
IMG_20240519_165723.jpg
 
Hey guys!

Small update:
My perfectly stable 700/1000 Slim is unable to do 700/1025. 1st time booting up the VSH froze immediatelly, all next boot attempts I got only sound.
Thankfully, I was able to revert to 700/1000 via recovery menu, I can consider myself lucky and "smart" for going 1025 first and not 1050 on the 1st try, I'm sure even recovery menu wouldn't work in 1050 memory.
This just goes to show that even having a perfectly working system, the next step might be a killer :bitsbubba:

Attached is an image of what the recovery menu looked like when I managed to install the 700/1000 PUP, for the 3rd time (2 times it failed at different percentages), attached also proof that I got it to work again, phew!
View attachment 43105
View attachment 43106

i continue to say = we have 2 slot for fw, i read is possible switch it... why not code a possibility for switch slot in case of freeze/brick state?
probably my idea is wrong?
 
This model takes overclocking like a champ, my thermals barely changed introducing the overclocked firmware and it's basically been like free performance. I've been impressed with the performance increase of 600/750 and am thinking 650/800 should get me close to a consistent 30fps for capped titles and better performance overall.
The voltage is fixed.

Reporting in with my -CG RSX from October 2010. 850/850 froze within a minute, 800/850 is "stable enough". I can get 42 FPS exactly in TLOU menu compared to my 950/1000 getting 48.

rsx40 a01 850/850 vpe:ff shd:7d [AP0022738:0:1:8:17:f:2:0:2][28:0:a:0:1:0:1][1:1:0]

Platform ID: CokJ20
Product Code: 00 84
Product Sub Code: 00 0B
Hardware Config: 000000000A03BC3C
Syscon Firmware Version: 08C2.0000000000000000 (EEPROM: 0000000000000000)
either way it's nowhere as good (and hotter!) then my golden Sep2010 950/1000. @RIP-Felix , what stands out to you from the above worse PS3 versus the "golden" one below?

CXD5300GGB.
950/1000 vpe:ff shd:3f [L4B576500:0:2:18:14:9:3:0:2][26:0:a:0:1:0:1][1:1:0]
800/850 is weird. Run 750/900 or even 950.
With your help I slowly went up, and I tested 700/900 on my ps3 version 2511A and it's stable, now what are the next steps you recommend for me safely?
750/750
if not stable then 700/925.
 
Last edited:
I have a Cech-2504B 0C 320GB Slim. Dual boot with E3 Flasher. Minimal firmware 3.40.
Motherboard is JSD-001 or JTP-001. Temp 33% maximum 64 °C. My test:
700 900 was good
850 950 graphics errors already at power-on
750 1000 uncharted 3 freezes
700 1000 freezes at the logo, black image, a few green spots, sound was the first time
700 950 is still good
750 975 so far so good
I can't make my own mfw because the program gives me an error. (virtual win7 and retail win11)
I would like to try the following:
750 950
800 950
800 975
I will build a 750/950 firmware ASAP.
If by chance it stay perfectly stable after prolonged testing, we will see for higher speeds (if you like risks).

EDIT :

750/950
https://www.mediafire.com/file/8i49m754lj3uuw5/750_950_Beta8_PEX.pup_4.91.CEX-PS3UPDAT.zip/file

Hey guys!

Small update:
My perfectly stable 700/1000 Slim is unable to do 700/1025. 1st time booting up the VSH froze immediatelly, all next boot attempts I got only sound.
Thankfully, I was able to revert to 700/1000 via recovery menu, I can consider myself lucky and "smart" for going 1025 first and not 1050 on the 1st try, I'm sure even recovery menu wouldn't work in 1050 memory.
This just goes to show that even having a perfectly working system, the next step might be a killer :bitsbubba:

Attached is an image of what the recovery menu looked like when I managed to install the 700/1000 PUP, for the 3rd time (2 times it failed at different percentages), attached also proof that I got it to work again, phew!
View attachment 43105
View attachment 43106
Glad you managed to save it ! 1000MHz on memory is a terrifying barrier :chargrined:

i continue to say = we have 2 slot for fw, i read is possible switch it... why not code a possibility for switch slot in case of freeze/brick state?
probably my idea is wrong?
If possible, that would be great.
I've seen several users reporting that on Rebug firmwares (in fact, it should be any firmware), in order to activate the OC a LVL 1 poke was needed at each start.
A bit inconvenient solution but probably safer for testing. I assume that in case of brick (and shutdown), the base values would be restored ?
I don't know much about it though, I may have misunderstood.
 
Last edited:
I will build a 750/950 firmware ASAP.
If by chance it stay perfectly stable after prolonged testing, we will see for higher speeds (if you like risks).

Glad you managed to save it ! 1000MHz on memory is a terrific barrier :chargrined:


If possible, that would be great.
I've seen several users reporting that on Rebug firmwares, in order to activate the OC a LVL 1 poke was needed at each start.
A bit inconvenient solution but probably safer for testing. I assume that in case of brick (and shutdown), the base values would be restored ?
I don't know much about it though, I may have misunderstood.
a poke and restart is better no? update every time isnt good..
 
Hey guys!

Small update:
My perfectly stable 700/1000 Slim is unable to do 700/1025. 1st time booting up the VSH froze immediatelly, all next boot attempts I got only sound.
Thankfully, I was able to revert to 700/1000 via recovery menu, I can consider myself lucky and "smart" for going 1025 first and not 1050 on the 1st try, I'm sure even recovery menu wouldn't work in 1050 memory.
This just goes to show that even having a perfectly working system, the next step might be a killer :bitsbubba:

Attached is an image of what the recovery menu looked like when I managed to install the 700/1000 PUP, for the 3rd time (2 times it failed at different percentages), attached also proof that I got it to work again, phew!
View attachment 43105
View attachment 43106
I'd back it up to 975mhz for full true stability. 25 extra MHz from 1000 causing a near brick is bad, you gotta stay 50 MHz away from that instability. 1000 is just barely stable. All my 7 PS3s have nearly bricked or crazy artifacted at 1000. Memory is the thing that causes the bricks the most. We at least get warnings with the core every 50 MHz.
 
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?
 
Last edited:
Update: ps3 model 2511A.

700/900 - stable.
700/950 - stable.
750/875 - icons blinking, not stable.
750/900 - icons flashing again.

It's interesting to note that the Vram is holding up longer than the GPU, which was only increased by 50 MHz and started to show instability, I don't know why, as a 2511A model was supposed to last longer, I'm sad and happy at the same time, I don't know what what to do from now on, currently stuck at 700/950, I would like to thank Mitsu for the files.
 
Update: ps3 model 2511A.

700/900 - stable.
700/950 - stable.
750/875 - icons blinking, not stable.
750/900 - icons flashing again.

It's interesting to note that the Vram is holding up longer than the GPU, which was only increased by 50 MHz and started to show instability, I don't know why, as a 2511A model was supposed to last longer, I'm sad and happy at the same time, I don't know what what to do from now on, currently stuck at 700/950, I would like to thank Mitsu for the files.
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'd back it up to 975mhz for full true stability. 25 extra MHz from 1000 causing a near brick is bad, you gotta stay 50 MHz away from that instability. 1000 is just barely stable. All my 7 PS3s have nearly bricked or crazy artifacted at 1000. Memory is the thing that causes the bricks the most. We at least get warnings with the core every 50 MHz.

I don't know if you've noticed my older posts, it's been quite some time since we got the chance to go up to 1000 memory. I have done extensive testing, went through my whole game library(almost 100 games), even left Crysis HD running for over 24 hours once, never had any crashes or artifacting on 700/1000.

750/1000 started giving me artifacts, I even tested 800/1000 and it was about the same as 750/1000.

700/1000 is perfectly stable tho and I'm gonna f*kin keep it for that GHz overclock :'D

So imagine going from 100% stability to "no image" in 25 MHz... Insane.
 
I don't know if you've noticed my older posts, it's been quite some time since we got the chance to go up to 1000 memory. I have done extensive testing, went through my whole game library(almost 100 games), even left Crysis HD running for over 24 hours once, never had any crashes or artifacting on 700/1000.

750/1000 started giving me artifacts, I even tested 800/1000 and it was about the same as 750/1000.

700/1000 is perfectly stable tho and I'm gonna f*kin keep it for that GHz overclock :'D

So imagine going from 100% stability to "no image" in 25 MHz... Insane.
I've had it go from 975 stable. To causing full blown console crashing 10 seconds into booting. But that's lucky cause when I enter safe mode, being a more cut back screen and menu, stability stays till I can Install a lower firmware. Which has saved me twice. But I say be 50 away, cause if the silicon degrades enough, it will eventually cause the same symptoms as 1025. But! If 1000 is Rock solid stable, rock it out for a long time. The chances of it degrading and causing instability is still there, but it's not a huge thing to worry about. 1ghz is an amazing OC. Just know if something ever goes wrong down the line. You'll know it's the memory.
 
I've had it go from 975 stable. To causing full blown console crashing 10 seconds into booting. But that's lucky cause when I enter safe mode, being a more cut back screen and menu, stability stays till I can Install a lower firmware. Which has saved me twice. But I say be 50 away, cause if the silicon degrades enough, it will eventually cause the same symptoms as 1025. But! If 1000 is Rock solid stable, rock it out for a long time. The chances of it degrading and causing instability is still there, but it's not a huge thing to worry about. 1ghz is an amazing OC. Just know if something ever goes wrong down the line. You'll know it's the memory.

Agreed! That's why I have a 975 file on hand at all times already :'D

And yes, I was expecting maybe to have a warning of some sort after going up only 25 MHz but no... Just instant crash in VSH and next boot no image at all. It was a bit scary.
Then the recovery menu update failed 2 times and worked on the 3rd... I was already "dead" :D
 
Agreed! That's why I have a 975 file on hand at all times already :'D

And yes, I was expecting maybe to have a warning of some sort after going up only 25 MHz but no... Just instant crash in VSH and next boot no image at all. It was a bit scary.
Then the recovery menu update failed 2 times and worked on the 3rd... I was already "dead" :D
Yup. Memory OC is what kills the PS3s. That's why it's not worth trying anything after 975. 975 seems to be the safe stable OC I've gained in multiple of my 25xx slims. Only the later 25xx slims can do that OC on memory. Mostly October, November December and January models can do those OC. If you're unlucky, 975 will cause artifscts and instability and you'll be fully fine at 950. 700/950 is already a huge overclock and the benefits are night and day. So no one should feel bad they can't go higher. I have 3 PS3 slims I've binned so far that do 900 and 850 core. I learned how to find them easier.
 
Yup. Memory OC is what kills the PS3s. That's why it's not worth trying anything after 975. 975 seems to be the safe stable OC I've gained in multiple of my 25xx slims. Only the later 25xx slims can do that OC on memory. Mostly October, November December and January models can do those OC. If you're unlucky, 975 will cause artifscts and instability and you'll be fully fine at 950. 700/950 is already a huge overclock and the benefits are night and day. So no one should feel bad they can't go higher. I have 3 PS3 slims I've binned so far that do 900 and 850 core. I learned how to find them easier.

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
 
Back
Top