Low AIDA64 memory score

[TheKelz]

Hey everyone.

Basically the title. For some reason, my system is getting pretty low memory scores:

 

This is one of the screenshots I found on these forums, this guy is getting much better scores:

What could be wrong with my setup, any help? XMP is enabled and all power limits are unlocked in BIOS.

[agent_x007]

1) Your NB Frequency is really low, also try using latest version of AIDA64.
2) He is using Quad Channel, and his score is also pretty low for Quad 3200MHz...
3) Can you provide a screen shot from ASRock's Timing Configuration (v4.0.4) program ?
4) Are you sure CPU isn't throttling from too high temperature ?

[TheKelz]

40 minutes ago, agent_x007 said:

1) Your NB Frequency is really low, also try using latest version of AIDA64.
2) He is using Quad Channel, and his score is also pretty low for Quad 3200MHz...
3) Can you provide a screen shot from ASRock's Timing Configuration (v4.0.4) program ?
4) Are you sure CPU isn't throttling from too high temperature ?

Thanks for the answer. My NB frequency is actually fluctuating. When I first boot my PC, it stays on 4200 (memory scores are even lower though). I will try the latest AIDA64, also thought about that. I want to add that I've bumped my scores to 45k because my secondary timings were manually tweaked before that, so I set them to defaults and now it's 45k, but I can't still get it higher, which I think it should be? My stock trfc was at 880 which is high imo (correct me if I'm wrong), so I set it at 460 now. My CPU is not throttling at all mate, 64 celcius on average during gaming and AIDA64 stability testing.

As for Asrock Timing configurator, here it is: 

[agent_x007]

Drop tFAW to 20 and tRC to value = tRP + tRAS.
After this, check bandwidth again.

[TheKelz]

14 minutes ago, agent_x007 said:

Drop tFAW to 20, and check bandwidth again.

Very subtle change, unfortunately... 

Want to mention once again that I ran this test twice, once 30 seconds after boot and then 2 minutes after boot. At first, NB frequency was at 4299 but the score was basically the same. This is weird. 

[TheKelz]

18 minutes ago, agent_x007 said:

Drop tFAW to 20 and tRC to value = tRP + tRAS.
After this, check bandwidth again.

Saw your edit and not quite sure I understand what you mean. Can you please explain in details what do you mean with those values? Sorry if I sound stupid.

[agent_x007]

tRC is timing that should be visible in BIOS (or AIDA64), set it's value to what those two timings (tRP and tRAS) combined to. With your current settings, that would be 18 + 38 = 56. It probably won't make much difference though... as Intel CPUs don't use it much. No worries if it's not in BIOS, just move on to next thing.

Also, if you want more information about your memory (like what chips were used), you can try running "thaiphoon burner" program, it provides more information about what they are (it's not 100% right all the time but it's good enough).

The last weird thing that strikes me is IO-Ls at 14...
Try setting 25 and see what happens.
Fair warning : Tweaking this can result in failed boot, and clearing CMOS may be required to make PC boot again.

[TheKelz]

6 minutes ago, agent_x007 said:

tRC is timing that should be visible in BIOS (or AIDA64), set it's value to what those two timings (tRP and tRAS) combined to. With your current settings, that would be 18 + 38 = 56. It probably won't make much difference though... as Intel CPUs don't use it much. No worries if it's not in BIOS, just move on to next thing.

Also, if you want more information about your memory (like what chips were used), you can try running "thaiphoon burner" program, it provides more information about what they are (it's not 100% right all the time but it's good enough).

The last weird thing that strikes me is IO-Ls at 14...
Try setting 25 and see what happens.
Fair warning : Tweaking this can result in failed boot, and clearing CMOS may be required to make PC boot again.

It's already set at 56 mate... 

I will try and see what happens. I'm starting to thing that it's just this memory itself, because no matter what I do, it doesn't go above 46k, even though the score drops to 35k if I use higher (loose) timings. It's like it hits the wall at 46k.

[agent_x007]

Did you picked "high performance power plan" before testing ?
(^may be the cause of dropping NB Frequency)