Incorrect DRAM speed showing in Windows

[Homewrecker]

So I finally got my build done and have finished installing all of my apps. I haven't started OCing yet but when I went to look at CPU-Z and AIDA64 my RAM speed showed up as 1066. The memory tab for CPU-Z is not even populated aside from the amount of RAM which is showing correctly at 16gb. At system boot up the memory amount and speed shows correctly. I tried XMP and manual settings in the bios but no change. I manually entered the voltage to 1.6 and manually entered the frequency as well. I haven't messed with any of the other settings as of yet. Any suggestions?

[HiVizMan]

Out of interest which CPUz are you using? I assume that you are using the latest version?

Could you confirm which of the ram slots you have populated?

And finally take another look at your BIOS screen and check that your ram overclock has been set.

[GetMax]

1066x2 = 2132

[HiVizMan]

So we have one of the problems sorted out. Yes the frequency of your ram is twice the value shown in CPU-z. Thank you GetMax



But still waiting to see why none of your ram slots appear populated in CPU-z, I take it you have cycled through the drop down menu which shows each of the slots?

[Homewrecker]

HiVizMan wrote:
So we have one of the problems sorted out. Yes the frequency of your ram is twice the value shown in CPU-z. Thank you GetMax



But still waiting to see why none of your ram slots appear populated in CPU-z, I take it you have cycled through the drop down menu which shows each of the slots?

I could have sworn in the past that my actual memory frequency showed up in CPU-Z or in some other app. That is why I was surprised to see it at 1066.

[xeromist]

Homewrecker wrote:
I could have sworn in the past that my actual memory frequency showed up in CPU-Z or in some other app. That is why I was surprised to see it at 1066.

That *IS* the actual memory frequency. DDR just means that it performs operations twice per cycle so 2133 is not the actual frequency. If you saw an app display the data rate as the frequency then it was probably a bug that got fixed because that would be wrong.

[Homewrecker]

The forum layout seems to be screwed up again as everything is difficult to read and text showing up as black.

Anyway, only the Red Slots are populated on the board - 2 sticks on each side. I'm using the latest version of the ROG CPU-Z. I belive its 1.57.1 (I'm currently at work but I'm fairly certain that's the version). I've tried all the drop down menus and there's nothing there. MEMTweakIt shows all of the possible JEDEC values under the SPD tab (Inclduing XMP Profile #2 @ 2133).

When I run the AIDA 64 Cache & Memory benchmark the speed there shows up as 1066 as well.

There was an error in my sig. The RAM speed is supposed to read 2133 and not 2100. I've corrected that.

When you stated to check the RAM Overclock did you mean Memory Frequency or are you referring to a specific item under the DRAM Timing Control Screen?

[Terminal_Meltdo]

I'm confused... You're saying it's 1066 x2 = 2133? As if this formula was like it use to be with the old dual channel systems 533 x2 =1066mhz. Then, shouldn't it be something like 533.25 x 4 = 2133 going by the quad channel definition, then? Kind of like how the old FSB used to be called "QUAD PUMPED" before QPI took over.


I hope I wasn't sold a "QUAD channel" gimmick -- that won't be good -- because the memory bandwidth is why I purchased this system.











3930k Ordered - Waiting for stock *shrug*
Asus Rampage 4 Extreme - In route to my house now
G.Skill 32 gig 2133mhz - Sitting on desk
Corsair Force GT 120gig SSD - Sitting on desk


Soon... :cool:

[HiVizMan]

LOL - nah quad channel is the number of slots and how they work together. Double data rate is what you see in CPU-z.

The x 2 part is nothing to do with channels mate. So relax and enjoy your system. What to see bandwidth run some benchmarks and you will see just how much bandwidth you are getting scary it is.

[Homewrecker]

I reinstalled CPU-Z and all the fields were populated. Seemed to have been a bug with the installation. Everything seems good now.