SCCM Retro Overclocking Setup Guide

Every Switch chip is a little different. Two consoles of the same model can hold different RAM speeds, CPU clocks, and voltages depending on the silicon inside. SCCM Retro ships tuners that measure what your exact console can do, and they only save a setting after it passes real stability testing. This guide is the whole flow in order: prepare a save state, tune RAM, prove it in a game, tune CPU voltage, then pick your CPU clock.

Crashes and restarts during a tuning run are normal and expected. The tools are built to crash safely, record what failed, and keep going.

Before you start

Create a GC/WII save state
This is required, not optional. The RAM tuner does not use a synthetic benchmark. It tests each candidate setting by actually playing one of your GameCube or Wii games, because that is the workload that finds bad memory settings.

Add a demanding GameCube or Wii game to your SD card. Mario Kart Wii, Super Smash Bros. Melee, Metroid Prime and Super Mario Galaxy are all good choices.
Launch it and play until you reach a genuinely busy moment: the middle of a Mario Kart race with a full grid, a 45 minute Melee match, a heavy fight or a dense area. A menu or a title screen is not good enough.
Save a state there from the in-game menu. See the save states guide if you have not made one before. One save state in one game is enough.

If you start a run with no save state on the console, SCCM Retro warns you and lets you continue anyway. The run is still valid, it is just more likely to pass a speed that turns out to be unstable later. It is worth the five minutes.

Plugged in, undocked
You also need to remove the console from the dock and plug it into the official charger.

Where the tools live

Open Settings from the game grid and go to the Overclocking tab. Every tool in this guide is here, and each button shows what is in force right now.

The Overclocking tab in SCCM Retro Settings, showing View Console Info, RAM Overclock, CPU UV, CPU Settings and GPU Settings

The one rule: only force a reboot if the screen has been fully black for 2 or more minutes, the moving dots have stopped moving, the display is jumbled, or the web page has been down for more than 5min straight. Then hold POWER for 15 seconds, power back on, and pick Continue Tuning in the boot menu to resume, NOT “Scratch“. Picking Cancel Tuning instead stops the session and returns the console to stock settings. That entry is the way out of any run, RAM or CPU. If you get yellow text from a panic error, just press the power button once to dismiss.

Step 1: run the RAM tuner

Go to RAM Overclock and choose Run a Tuning Session.

The RAM Overclock menu with Previous Results, Run a Tuning Session and Set a Custom RAM Setting

Leave the defaults alone. The page opens on the recommended speed range for your console and the community voltages for your exact memory chip, both marked on screen. Those are the values you want. The address to watch the run from another device is printed here too.

The Run a Tuning Session page showing the Before you start notes, the recommended speed range and the community memory voltage

Scroll down and check the test toggles. All of them should be On, which is how they ship. If any of these is Off, turn it back on:

Test HP Mode
Test read and write latencies
Test timing presets
Test core timings (B)
Test refresh stretch (C)
AC Mode

The RAM tuning toggles: Test HP Mode, Test read and write latencies, Test timing presets, Test core timings and Test refresh stretch, all On

Then press Start tuning (restarts the console).

AC Mode toggle, the what to expect summary and the Start tuning button at the bottom of the RAM tuning page

What the next few hours look like

About 4 hours for a full range, and it is mostly hands off. The tuner climbs to the fastest speed that passes, tests the extras, then proves the result with a final stability soak before anything is saved.
Expect to hard reset it roughly 3 to 5 times across the session, following the one rule above. That is the tuner finding a setting your chip cannot hold, which is exactly what it is for. Power back on and pick Continue Tuning.
Watch it from your phone. On the same home WiFi, open http://<console-ip>:8098 in a browser. The exact address is printed on the start screen. You get the live progress, the current test, and the elapsed time without touching the console.
If nothing faster than your current speed turns out to be stable, your current setting is kept. You cannot end up worse off.

If you do not have 4 hours

Run a shorter session instead of skipping it. Turn off: Test HP Mode, Test timing presets, Test core timings (B) and Test refresh stretch (C), and leave Test read and write latencies and AC Mode on. You still get your chip’s stable speed plus the tighter latencies, which is most of the benefit, in a much shorter run. You can always come back and run the full session later.

Step 2: prove it in a real game

A passed tuning run is a strong result, not a guarantee. Before you move on, play a demanding Wii or GameCube game for 10 to 20 minutes. Real gameplay, not menus, and ideally the same kind of busy scene you saved your state in.

Watch for a crash back to the launcher, a freeze, a sudden reboot, garbled or flickering textures, stretched geometry, or scratchy audio. Any of those means the settings are too aggressive.

Most runs will be stable right after the test with no modification needed.

If it is unstable, back off in this order

Go to RAM Overclock and then Set a Custom RAM Setting. Change one thing, apply it, then play for another 10 to 20 minutes before deciding whether to go further. Changing several at once tells you nothing about which one was the problem.

The custom RAM timing controls: Timing A, Timing B, Timing C refresh and Write latency

Timing C (refresh) down to 0. Start here. Refresh stretch is the setting gated on temperature, so it is the usual cause of a console that tested fine but falls over 15 minutes into a game once everything is hot.
Timing B down one step, and again if it is still unstable. Core timings are the next most aggressive thing the tuner commits.
Timing A down one step
Write latency (wrl) to Off
HP Mode off. This also cuts power draw and heat, so it is worth trying if the trouble only shows up after a long session.
Memory speed down one bracket. Last, because the speed is worth more than everything above it put together. Give up the timings first.

Leave the memory voltages on the community values while you do this. Test it (restarts the console) makes the console check the setting before it commits to it. Save and restart (no test) writes it straight to your boot settings, which is the quicker choice when you are simply loosening something back off.

Step 3: run the CPU UV tuner

Once RAM is stable, go to CPU UV, choose Run Tuner, and press Start tuning (restarts the console). Leave the starting steps on Automatic.

The CPU UV tuner start page, Tune CPU voltage to your silicon, with its Before you start notes and monitoring address

This one finds your exact chip’s lowest stable CPU voltage across its whole clock range, in fine steps. Lower voltage means less heat and better battery, and it helps an overclock hold its top clock instead of throttling.

About 2 to 3 hours, and it runs unattended. It restarts itself many times; that is normal.
Watch it from your phone at http://<console-ip>:8098, the same as the RAM run. You can also stop the run from there.
It enables the Extreme overclock setting for you, and applies the result automatically as your normal-clock and boost-clock undervolt steps.

If it is unstable afterwards

Go to CPU UV and then Set Manually, and drop both Normal-clock undervolt and Boost-clock undervolt by one step, then Save and restart now. Lower step numbers mean less undervolt and more stability. Repeat one step at a time if it is still not right.

The Set CPU undervolt manually page with Normal-clock undervolt and Boost-clock undervolt steppers

Step 4: pick your CPU settings

Go to CPU Settings. Two controls matter here, Max clock and Max voltage. Max voltage is the ceiling the chip is allowed to reach, and it moves in 5 mV steps.

The CPU Settings page with Max clock and Max voltage steppers and the measured voltage table for this console

V2 and OLED (Mariko)

1120 mV is the default and the safe everyday figure. Up to 1180 mV is widely run and generally considered safe. For the best performance, set Max voltage to 1180 mV and Max clock to 2703 MHz. Past 1180 mV the risk of shortening the chip’s life goes up.

Original V1 (Erista)

1225 mV is the default and the safe everyday figure. 1235 mV is likely safe. For the best performance, set Max voltage to 1235 mV and Max clock to 2295 MHz.

If it is unstable, drop your Max clock one step at a time. Do not answer instability by raising the voltage ceiling; the ceiling is there to protect the chip.
2703 MHz on Mariko and 2295 MHz on Erista only appear in the list with Extreme overclock on, further down the Overclocking tab. The CPU UV tuner turns it on for you; if you skipped that step, flip it yourself and restart.
The clock applies instantly. A changed voltage ceiling only takes effect on the next restart, so use Apply and restart now when you change it.
Measured on this console lists what each clock actually drew on your chip, with averages, peaks and sample counts. It is advice for choosing a clock, not a limit, and it fills in as you play.

If a run looks stuck

A crash or a black screen between tests is part of the search. The tuner notes the failed setting on the next start and moves on by itself. While a test runs, the on-screen page shows a progress bar, an elapsed timer, and a working notice; the page on port 8098 shows the same from another device. Trust the one rule: 2 or more minutes of a truly dead screen before you force anything, then Continue Tuning to resume or Cancel Tuning to stop at stock. Nothing is damaged either way. If you get a yellow panic error, that is normal, just press the power button once.

After tuning

View Console Info shows everything in force at once, along with your chip type, silicon rating and memory model. Each tool’s Previous Results or Tuner result page keeps the history of past sessions.

The Console info page showing chip type, speedo bin, RAM model and the current RAM, CPU UV and CPU clock settings

Once you are happy, save the whole setup as a named profile with Save current settings, and bring it back any time with Load Profile. For choosing performance profiles per game now that tuning is done, see the Performance and Overclock Settings guide.

SCCM Retro Guides

Was this guide helpful? Consider donating to support development of new content, software, and guides.

Support This Guide

Need a modchip installed? Place an order or learn how to ship your console.