Well, Well, Well...
I'm a bit ashamed...
After several additional trials, I guess (fingers crossed) I got it.
Instability in WoT seems to be linked to low latency subtimings (others than 14-14-14-14-34)....I was so convinced that memtest64 was enough to test RAM OC stability...in fact not really.
Simply I ran with R7 1700X OC 3.9Ghz @1,4875v, GTX 1080ti OC and RAM with DOCP/XMP profile (3200Mhz, 14-14-14-14-34)...and it went smoothly on WoT.
I just realized yesterday evening, that all my previous test have been done with RAM with lower latency sub timings (validated with memtest64)...and I wonder.."what if memtest64 trial was not 100% crash proof?"..
I must admit that it's quite easy to validate overclocking for CPU (intel burn test, high mode) and GPU (3D mark time spy)...but for RAM overclocking, it's another level..
I'm a bit ashamed...
After several additional trials, I guess (fingers crossed) I got it.
Instability in WoT seems to be linked to low latency subtimings (others than 14-14-14-14-34)....I was so convinced that memtest64 was enough to test RAM OC stability...in fact not really.
Simply I ran with R7 1700X OC 3.9Ghz @1,4875v, GTX 1080ti OC and RAM with DOCP/XMP profile (3200Mhz, 14-14-14-14-34)...and it went smoothly on WoT.
I just realized yesterday evening, that all my previous test have been done with RAM with lower latency sub timings (validated with memtest64)...and I wonder.."what if memtest64 trial was not 100% crash proof?"..
I must admit that it's quite easy to validate overclocking for CPU (intel burn test, high mode) and GPU (3D mark time spy)...but for RAM overclocking, it's another level..