Confused about CPU-Z "Timings Table" discrepancy (tRC)

[tomhwk]

I recently popped open cpu-z to take a look at my memory. I am using 4 sticks of 4gb 1333 ram. They are all identical. But when I took a look at the "timings table", I noticed one number was off. I assume that "Slot #1" and "Slot #3" are running together in a dual channel, and 2 and 4 are doing the same, because they are identical, but the two dual channels have different "tRC" numbers under "JEDEC #3". I have no idea if this is bad or doesn't matter, but I figured I might as well ask.
Although not entirely related, I feel like even though I have 16gb of ram, when I hit about 10gb usage, I can feel my browser start to slow down, and small slow downs, but I've heard it probably just has something to do with how chrome handles memory, and isn't that great.

Thanks!

 

[chrisso]

First, any numbers in the jedec you are not using are irelivant.
Second, cpu z reports anomolous no's because it is trying to work out your changing cpu/ram timings whilst your motherboard is messing about with your multipliers all the time and
Third,if you are hitting ten gig of use in chrome you got no chance. Chrome corrupts itself and ends up un responsive way before that.
Even half a dozen pages can crash after a nites sleep .
Hope this helps. Yes, I just build a haswell quad rig and cpuz ?????????

 

[tomhwk]

How do I know which jedec I am using? I don't really know what I'm looking at, but I guess it's okay if I'm not using that one? I just heard that having different timings running on your memory can really mess things up, so I figured I would take a look. I really know almost nothing about what I'm looking at. Hahaha..

 

[Pinhedd]

How do I know which jedec I am using? I don't really know what I'm looking at, but I guess it's okay if I'm not using that one? I just heard that having different timings running on your memory can really mess things up, so I figured I would take a look. I really know almost nothing about what I'm looking at. Hahaha..

Only one set of timings can be used at a time.

You have two channels, with two DIMM slots on each channel.

tRC is not a primary timing, it can be specified or calculated automatically by the firmware. It is equal to tRAS + tRP which in both cases is 22 cycles + 8 cycles. You can check and see if a firmware update is available to fix that, but if not just leave it well enough alone.