Horizon OC 2.0 - Most powerful overclock tool. CPU 2397MHz, GPU 1228MHz, RAM 3200+MHz

  • Thread starter Thread starter Souldbminer
  • Start date Start date
  • Views Views 22,611
  • Replies Replies 89
  • Likes Likes 31
So the only way would be to temporarily lower the max freq I have currently set, to whatever freq I want to test that is outside of the table?

That kinda sucks, but I guess it is what it is, luckily I only need to test 1333 Latency at 2333MHz or lower for GPU stability rather than doing the full set
There was discussion of adding the 33MHz increments at one point but I don't remember where it landed. For your example yes temporarily setting the limit to 2333 should allow you to test what you want.
 
  • Love
Reactions: Esurient
Hi, I have sys-clock and wanted to change it to horizon oc, for the handheld without external power is possible to have more than 614mhz?
Edit: ok, so it works both ways but I can't change more settings for mhz with a max cap of
CPU: 1963mhz (but stays most between 1581 and 1887)
GPU: 1152mhz (can't change more, no options)
RAM: 2133mhz (max option, but I can "change" it on the settings menu)

I tried following the tutorial from the guide but even with Uncapped clocks still doesn't change, do I need to restart the console?

Edit 2: so I had to ALSO download HOC toolkit and in that, started changing some stuff and now finally GPU and RAM go past 1152 and 2133.

Horizon OC Toolkit
 
Last edited by HasRock17,
Hi, I have sys-clock and wanted to change it to horizon oc, for the handheld without external power is possible to have more than 614mhz?
Edit: ok, so it works both ways but I can't change more settings for mhz with a max cap of
CPU: 1963mhz (but stays most between 1581 and 1887)
GPU: 1152mhz (can't change more, no options)
RAM: 2133mhz (max option, but I can "change" it on the settings menu)

I tried following the tutorial from the guide but even with Uncapped clocks still doesn't change, do I need to restart the console?

Edit 2: so I had to ALSO download HOC toolkit and in that, started changing some stuff and now finally GPU and RAM go past 1152 and 2133.

Horizon OC Toolkit
Check your max voltage for CPU and GPU. If the calculated dynamic voltage for the higher frequency is above the limit it won't set. CPU/GPU UV can help with that as well.
 
Last edited by l7777,
  • Like
Reactions: HasRock17
Check your max voltage for CPU and GPU. If the calculated dynamic voltage for the higher frequency is above the limit it won't set. CPU/GPU UV can help with that as well.
These are my settings, but want to undervolt a little bit.

They are "ok" for default?
 

Attachments

  • 2026092310452200_c.jpg
    2026092310452200_c.jpg
    164.5 KB · Views: 2
These are my settings, but want to undervolt a little bit.

They are "ok" for default?
What are your speedo ratings? Most units will do 2601 CPU with a little UV. SOC temp is more critical than the others. I try to keep it under 60.

Are you following the OC Guide? If so after you've found your RAM max you can start tinkering with UV. You can't hurt anything with UV, things will run cooler and battery life will increase on handheld mode. At the higher UV levels you'll likely need to increase the high and low VMin to compensate. I ran into a situation where max RAM & CPU frequency were stable but frequencies between the Tbreak and max were unstable because the high vmin was too low.

I used the Memtester from the Benchmark Toolbox to find my optimum settings. My understanding is that running the memtester won't tell you if things are 100% stable, but any mismatches are confirmation that you've gone too far. If things are stable there, then I think it's recommended to use the Korok forest benchmark with ultracam to confirm that you're good.
 
  • Like
Reactions: HasRock17
What are your speedo ratings? Most units will do 2601 CPU with a little UV. SOC temp is more critical than the others. I try to keep it under 60.

Are you following the OC Guide? If so after you've found your RAM max you can start tinkering with UV. You can't hurt anything with UV, things will run cooler and battery life will increase on handheld mode. At the higher UV levels you'll likely need to increase the high and low VMin to compensate. I ran into a situation where max RAM & CPU frequency were stable but frequencies between the Tbreak and max were unstable because the high vmin was too low.

I used the Memtester from the Benchmark Toolbox to find my optimum settings. My understanding is that running the memtester won't tell you if things are 100% stable, but any mismatches are confirmation that you've gone too far. If things are stable there, then I think it's recommended to use the Korok forest benchmark with ultracam to confirm that you're good.
I tried to follow the guide but couldn't understand much (compared to pc, it's a bit harder).

I did some "updates" to my OC either docked or handheld, this are my new settings.
 

Attachments

  • 2026092807410600_c.jpg
    2026092807410600_c.jpg
    170.5 KB · Views: 1
I tried to follow the guide but couldn't understand much (compared to pc, it's a bit harder).

I did some "updates" to my OC either docked or handheld, this are my new settings.
In general you should:
  1. Find your SOC version (Erista/Mariko) ram type and speedo rating
  2. Go to the RAM section of the Guide and use it to find your max RAM frequency. There guidelines about what is typical for your ram modules. If going for very high RAM clocks you might have to increase CPU high & low Vmins
Finding your max RAM frequency is a loop:
  1. Open HOC & set a tempeorary RAM frequency at the lower end of the range for your modules.
  2. Launch the HB Menu or Sphaira with full RAM (title takeover mode)
  3. Launch the Benchmark Toolbox and select the memtester, see if it makes it through a couple loops without freezing or mismatches
  4. If it makes it through, go back to 1 and select a higher RAM frequency.
  5. Once you find the point of mismatches or freeze/crashes, you know you're close to the limit. You can try increasing CPU high/low VMin but gains will be minimal.
  6. Next step is to keep the RAM at its highest frequency and increase the timing reductions, start with the common timings for your RAM, then try the tight timings repeating 1-3.
  7. Once you find the timing options you can start lowering DVB and repeating 1-3 until you find the lowest stable setting.
  8. A final stability check is to play TOTK for ~60 mintues or run the ultracam korok forest stress test. If you get no crashes you've found the limits of your RAM. If you get crashes increase DVB by 1 or reduce frequency or timing reductions slowly.
Finding CPU/GPU UV limits follows the same testing loop but there are less settings so it shouldn't take as long.

Disclaimer, successfully running the Benchmark Toolbox stress tests does not indicate 100% stability, but failures would positively indicate an instability.
 
Last edited by l7777,

Site & Scene News

New Hot Discussed User Submitted