Ram frequency affects rift tracking.

flexy123

I hope all you guys who overclock (I do as well of course) test your machines for stability before coming to any conclusions. And I am not just talking memtest and the usual, but running a bunch of tests like Aida64, Asus RealBench etc. And even then, 100% stability can never be "guaranteed". On the other hand, if you use built-in XMP "oveclocking" profiles of memory, one would assume these settings should be stable.

guysery2000

Sure, but the problem persists even if i reset Bios to default settings and then just "overclock" (between apexes because they are 3000mhz certified modules) my ram modules to keep them at their certified frequency, with or without XMP. 

guysery2000

UnFknBLievable, I have the exact same problem.
Asus Z170-A and tracking problems if i overclock my ram (i can notice that instantly if i run The Unspoken, with Touch tracking going super messy every couple of seconds). 
I tried 2133mhz (the frequency they are staying at now) for them to be stable, and 2666 or more, at which they started to be unstable. I also came to the conclusion that cpu overclock was not the culprit, so i decided to keep that and keep the Ram at 2133, but lowering the latencies (tightening them). So far so good.
I don't remember Ram modules' brand atm, but if this information can be helpful i will check and come back for sure.
I will definitely try to go up to 2400mhz with my Ram and see what i can accomplish with the Rift.
Let me know if you find a solution to the problem, thank you in advance.

guysery2000

UnFknBLievable, I have the exact same problem.
Asus Z170-A and tracking problems if i overclock my ram (i can notice that instantly if i run The Unspoken, with Touch tracking going super messy every couple of seconds). 
I tried 2133mhz (the frequency they are staying at now) for them to be stable, and 2666 or more, at which they started to be unstable. I also came to the conclusion that cpu overclock was not the culprit, so i decided to keep that and keep the Ram at 2133, but lowering the latencies (tightening them). So far so good.
I don't remember Ram modules' brand atm, but if this information can be helpful i will check and come back for sure.
I will definitely try to go up to 2400mhz with my Ram and see what i can accomplish with the Rift.
Let me know if you find a solution to the problem, thank you in advance.

guysery2000

Sorry for the duplicate posts.

flexy123

and you only get problems with Oculus and in no other app when you overclock the memory?

guysery2000

Nope. Was stable for more than 1 year and never noticed problems before buying the Rift.

g5xr

Bumping this:

ASUS Z170-A
The above chipset and motherboard appears to be very problematic with the Rift as Google results show we are not the only ones.

Touch tracking is fine but the HMD (Rift) disconnects every 10 minutes. The Touch controllers sometimes go wonky. My mouse is jittering a ton. 

I have G.Skill Trident Z sticks, somewhere in the 4xxx range. I'm going to try underclocking them as some have mentioned, and maybe tightening the timings. Admittedly, my system is not 100% stable as it has crashed with sound looping twice in the last year. 

I've also ordered a Inatech USB PCI-E card. 

Will report back after.

https://forums.oculus.com/community/discussion/35589/asus-z170-a-motherboard-incompatibility

Here is another topic with the same problem and conclusion regarding ram.

https://www.reddit.com/r/oculus/comments/3zrtgs/psa_your_usb_30_ports_may_not_be_compatible_with/

More issues with the above board.

mbze430

X99 system here, with no tracking issues with ram.  my set are originally 2400 OC to 3000 64GB

g5xr

mbze430 said:

X99 system here, with no tracking issues with ram.  my set are originally 2400 OC to 3000 64GB

This doesn't seem to affect any other board except for the Z170-A and some variants.

Pic0o

I am on a Z270 motherboard running DDR4-3000 and have not seen this issue.
Thank you for sharing your information on this issue.

g5xr

Fixed it by updating my firmware, OCing the CPU, but leaving the RAM on AUTO. I'll deal with the tiny performance loss for Oculus stability.