Two more E41's, both coming out of sleep mode :(. I think I am done with these Trident 4x16's for now. I'm going back to my rock solid RipJaws 3200 C14 kit and will research some 2x32 kits while waiting on a 59x0 to come my way...
Well after swapping back to the RipJaws 4x8 3200 C14's, running DCOP and a 13% OC, system has been rock solid. Running the 2502 Release Bios from Asus' Bios Download page. Not sure if it the change from Neo to RipJaws, or the change from 3600 to 3200 solved the issue. Would like to get back to 64GB, but unsure of which way to go now. 4x16 or 2x32...Ripjaws or try the Neo's again... or something else altogether.
I have random reboots at 2502 and 2402! 😞
Now i am using 2311.
My system is 5900x, cviii hero (non wifi), g.skill 2x8 3200 cl14, gtx970 (w8ing for 6800xt).
In 2402 i had single core 5.125ghz! but these reboots are too annoying...
Tested good with MemTest86 and MemTest64. I see several references to Karhu memory test but have not used it. I've also used Aida64 cache and mem benchmark although I'm not sure how valid is is as a testing tool.
IS this strictly a 4 dimm issue? My next test case will be to pull 2 dimms - I don't recall having any of these issues before going to 4 dimms, but was on older bios version as well... 2103 I believe. Worst case I can change to 2x32's, but I don't want to do that/spend the $$ if I'll face the same issues I am facing now with 4x16's. I also want to stay 59xx compatible as I plan on upgrading cpu.
EDIT - i went ahead and bought Karhu, seems to be recommended over the MemTest86. Will run it and report back.
And now that I think about it, before the Trident Neo I ran 4x8 of Ripjaws 3200 CL14 with no issues. I only upgraded to the Neo to get 3600/1800 FCLK, but I never had any issues with the RipJaws either... :rolleyes:
When we can expect Bios versions with FCLK improvements?
2402 was already pushing but without real performance gain. Now we see already 2033Mhz on e.g. ASUS B450-F Gaming (v8501) Boards.
It's a real disappointment!
I think it is not Asus issue, but AGESA (AMD) issue. AMD will relase new AGESA code soon what I know 🙂
its propably memory issue or corupted BIOS (reflash it with BIOS flashback function)
For better tweak your memory set all mnaully includind secondary timings and driving (Ryzen DRAM calculator help you)