OC'ing Ripjaws 4 2400MHz to.. ??

Ahh ok sweet, nice to know they can go that far.
What'd you do to get it to there? Just manually change frequency to 2933 (gradually) and change latencies? (if so what to, or if you kept stock)
- Mini q here: How do I know when to change the latencies if I go exploring how far I can push my sticks on my own? Is there a set latency to frequency format or is it that you switch it on > does something weird > change latency up one for each > see if that works, rinse/repeat ... ?

This line: "As long as you're not changing voltage you won't kill the RAM" - Wait so you OC'd your RAM by that far without changing your voltages what-so-ever? I feel like that's impressive to me but when that's probably just normal, I thought anything over like 100MHz would need you to crank up the voltage even just slightly.

On the second note ...
I wasn't aware about that ASUS thing. She keeps mainly good temps but hovers 25-30C idling which seems alot to me for doing nothing - especially with a Cryorig Ultimate cooler... I think that for some reason [strike]it's staying at high MHz when idling for no reason (staying in turbo mode) instead of dropping down to like 2GHz[/strike] (disregard this, I must've just had some background shit running, or wasnt paying attention for long enough, will frequently drop to 800MHz, 2.3/2.9GHz.. Still weird that its going full 4.4GHz turbo just with Mozilla, CPUz, fl.ux and background stuff going though..) like before I selected the OC.. I'm in the middle of investigating that, and perhaps manually OC'ing is the answer, I just selected it because I got lazy..

Edit: Yeah, you're right about ASUS being too happy with voltages, 1.328v max @ 4.4GHz during a short stress..
I changed voltage from 'Auto' to 'Offset' (ASUS/Asrock lack 'Adaptive')
It won't run offset AT ALL unless it's like +0.05 (50mV) which is certainly not what we want when aiming for lowering happy voltages lmao.. (Atleast with my very brief and new understanding of 'Offset' which is .. It takes the voltage from Auto and adds or subtracts whatever you put in?..)
Didn't run on ANY negative offset, didn't even want to boot with +5mV. (Thought that was weird, actually)
God knows running fixed voltage is an even worse idea than dealing with slightly happy voltages for a few hours per day - if ASUS were pushing closer to a dangerous 1.4V in Auto, that'd be a different story I reckon..

This probably wouldn't be such a headache if I shelled out more for like MSI instead of CheapRock but meh, it does the job.
I'll just deal with auto voltages being too happy and lowering the life span of my CPU.. It only ever runs 1.328V when maxing out anyway which is only during a few hours (some days more, some days less) of gameplay, otherwise sits ~/<1.00V

Anyway, now that has been sussed out - back to on topic, would really like to know what you did to get your result with the RAM before I go in fiddling

Cheers.

Sweet, cheers! Got it down packed now, it didn't even get to 2600MHz before needing to raise the timings up by one each to 16-16-36, it booted up then - took it straight to 2800MHz, was just gonna go to what I thought would be my limit and worked my way down if it didn't work, booted up fine at the same latencies 16-16-36-2N but got a rounding error in Prime95 between ~2, 5 and 8 mins in.. (fatal error/hardware error ... something 0.4xxxxxxxx expected 0.4) (couldn't be relevant to CPU because didn't touch anything to do with CPU and don't get that error when RAM is back down to 2400MHz and stock latency) - gonna see if loosening timings works better or something, maybe raise voltage to 1.21v but I don't see that being the fix, idk .. trial and error I spose - otherwise no visible errors, does everything fine - just the error in prime95.