Got mine to 4.020 1.41v stable
That is a unicorn there lol
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
*** Official Ryzen Owners Thread ***
- Thread starter Frozennova
- Start date
That is a unicorn there lol
3466mhz C16-16-16 on Asrock no problem. Key timings are TRFC and TWCL like on Intel play with these and the frequency is easy.
Kitfit sorry will have to check your stuff tomorrow or Wednesday today just too much to test.
At lunch today I set my machine off on HCI, after an hour or so got a blue screen and on second attempt a hard lock at 1.45v running 1.1875v SOC. This was at 3333 14-14-14-36 1T
Question, is it better to loosen to 16-16-16-36 and try to retain 1T, or drop to 2T at c14 (which is 3 hours stable so far), or drop to 3200 and try and keep the timings tight?
I am pleased it crashed as much rather know where the instability is than have these infrequent system lock ups!
Question, is it better to loosen to 16-16-16-36 and try to retain 1T, or drop to 2T at c14 (which is 3 hours stable so far), or drop to 3200 and try and keep the timings tight?
I am pleased it crashed as much rather know where the instability is than have these infrequent system lock ups!
3466mhz C16-16-16 on Asrock no problem. Key timings are TRFC and TWCL like on Intel play with these and the frequency is easy.
Kitfit sorry will have to check your stuff tomorrow or Wednesday today just too much to test.
Not to be a dick, but my ram is far from stable at those speeds, often crashes games etc. Just ask many of the members here that i play with...
But I am able to run such a small amount of HCI without errors to the point I don't consider anything less than an all night run a success.
I really wish that was enough to be considered stable.
3466mhz C16-16-16 on Asrock no problem. Key timings are TRFC and TWCL like on Intel play with these and the frequency is easy.
Kitfit sorry will have to check your stuff tomorrow or Wednesday today just too much to test.
Isn't HCI supposed to be run with 1 instance per thread?
Other people may chime in here but 600% is not enough. We have seen fails at 1000%
Don't see this as a personal insult. Did you manage to get any HCI testing of 3600CL16?
Unfortunately, this is why I only use HCI to test as much as it can overnight (up to around 12 hours) on 64gb - and that's the thread that got highest. With that, I can probably hit 500% on one or two threads. others can be under 300%
To properly test to 1000% on all will take literally days. Not a day and a bit - several days.
I have to rely on overnighters of that and tpu memtest
You are an exception
I was meant to ask you, do you still have your prime board? Would be handy for you to test on before buying another board.
Ran 6 benches with 3200c14 vs 3333C16.
3200 won by 6 points in CPUZ
3333 won by 10 points in Cinebench
3333 won by 1064 points in Realbench
3333 won by 21 points in Timespy 1080p
3333 won by 178 points in Firestrike 1080p
3200 won by 497 points in Superposition 1080p medium.
You are an exception
I was meant to ask you, do you still have your prime board? Would be handy for you to test on before buying another board.
I'm not going to rush into a new board.
I was just getting antsy with that mouse skipping showing up.
Have made a couple of tweeks, so will see how it goes.
But the darn usb connecting/disconnecting has gotten more frequent again - and I am pretty sure that is down to BIOS.
Am sure it was on 1401 that it didn't do it much. But on 1403 it's doing it a bunch again.
using 960 evo for primary - won't let me enable rapid. I am not sure if it's not something generally used on nvme drives or samsung not liking amd controllers.
Apart from that, 1tb ssd for games, 1tb ssd for VM's, 500gb ssd for Lightroom catalog, and several 2tb/4tb hdd.
Oh, and a blu-ray drive. Basically maxed out every storage connector and external 4tb...
Apart from that, 1tb ssd for games, 1tb ssd for VM's, 500gb ssd for Lightroom catalog, and several 2tb/4tb hdd.
Oh, and a blu-ray drive. Basically maxed out every storage connector and external 4tb...
Thanks that's great. I got between 1000 and 1300% on HCI today at 3333c14-14-14-36 but this was with 2T and geardown on auto. Had to power down but was still going strong after 8 hours.
My memory is 3600c17 so it may actually be the RAM struggling rather than the IMC. Not sure.
I looked at rapid mode but reading through the doc it only works on one drive, I have a 960 nvme for OS and two 850 for games and other stuff, to be honest I havent noticed any frame glitches, how would you describe it?
Also, are people using he default Windows 10 driver for the SSD or actually loading a Samsung driver, I am on what ever came with the Windows 10 install.
You would know if you had it. Very noticeable hiccups that occur when something new happens on screen. But if it does happen, rapid mode fixed mine.
Indeed, one instance per thread. So R7 chips should be running 16 threads using at least 850MB of RAM each (for 16GB).
As for % coverage, It depends where you want to draw the line. If at least 1000% what happens if it errors at 1100%? is that not stable? If at least 2000%, what happens if it fails at 2100% etc etc, where do you draw the line? Sure the longer the better, but at least 500% will give you perfect stability for every day use that I'm sure of. IIRC from some forums that HCI recommend at least 500% coverage and 1000% is considered "Golden".
So unless you're using your PC for time consuming number crunching/rendering/compiling/folding etc (which you really wouldn't be pushing the RAM for anyway), I would just stick to 200-250% for quick testing to see if you're on your way with 500% to be the goal for hitting stability and/or 1000% to REALLY REALLY be sure.
Last edited: