If the stress test doesn't find an error in 2 hours, even though it will find an error after 2 days, you're at a clock speed that is technically not stable, but in practice it will be very unlikely to crash at that speed. If you give your cpu a bit of rest (e.g. don't run the stress test, but "only" something like ps1 emulation, where you probably pause the game every hour or so, and even in the intense moments it'll stress the cpu less than the stress test), it'll be less likely to mess up. Also, not every cpu mess up will cause a crash - if you're lucky, the only harm done is a few pixels having the wrong color in one frame.
If you wait long enough, some error will be found at some point at any clock speed, even if only caused by some rather unlikely but not impossible bitflip caused by cosmic background radiation.
I recommend letting the stress test run overnight, check in the morning what speed it's at, and then round that down by subtracting 2% or so. E.g. on my unit, the stress test doesn't find errors at 999MHz in 8 hours or so (haven't tried for longer yet), so I set the max clock speed to 980MHz to be sure.
One factor that probably has some influence is the temperature: the higher, the worse it will perform. So it's a good idea to run the stress test while you're charging your unit - the charging will increase the temperature of your unit, so the results will be more reliable.