Atmosphere crashes when overclocking CPU

[Crusatyr]

Bug Report

What's the issue you encountered?

Edit: In Atmosphere, if I had an overclock that was too high (what is determined as too high is variable, but usually above 1122MHz) a game launch (or RetroArch) would cause the Switch to immediately turn off.
Entering any game without an OC, and re-enabling it afterwards would usually allow the game to play fine. However very likely would the Switch would immediately power off (crash) soon afterwards at random, in particular during loading screens. This issue is exacerbated the higher the CPU OC. GPU and RAM clock speed changes did not seem to affect stability or the chance of system crashes.

How can the issue be reproduced?

By using Freebird,or sys-clk, increase the CPU overclock to max for near immediate results. Some reports claim Atmosphere is unstable at any CPU speeds higher than 1.2Ghz, however

Crash Report

Don't have one

System Firmware Version

6.2.0

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
• Official release or unofficial build:
  • Official Release 0.8.3 and 0.8.4
• Do you have additional kips or sysmodules you're loading: n/a
• Homebrew software installed: N/A

Additional context?

EDIT: It was determined in RS discord that Exo is not at fault here and fatal does not generate a report since it is not called

[TheCoder3156]

I think this is because atmosphere runs more custom sysmodules than something like ReiNX and therefore requires more stability. Overclocking any cpu will cause stability issues at some level especially when doing more cpu intensive things (like more sysmodules in this case). I’m not sure if everything I said is 100% true and these are just my thoughts.

[SciresM]

It's probably just that AMS runs more on the syscore --> race conditions hit more often at higher clicks.

[SciresM]

Ignoring the rest of the content in that comment...it is my understanding that changing the speed at which a processor operates will change the relative timings of events, which can cause whether race conditions occur to change.

It's an honest best guess, not like there's any other plausible reason I can see.

[SciresM]

@Crusatyr "EDIT: It was determined in RS discord that Exo is not at fault here and fatal does not generate a report since it is not called"

This is false, pretty sure it's an exosphere problem (it's not a coincidence that reinx began experiencing this issue on 7.0.0, where it uses exosphere).

Anyway pretty sure I found the problem, testing it atm.