How do you know what Cas Latency your ram have?(66 posts)
Gives info for all critical components.
(Download and try).
(NO) installation required.
Old up to date utility changed every few months with new version.
Been around for years.
Rick P.♦ :)
Hmm, maybe. I myself am actually not very interested in the CAS latency numbers for my systems. It does not buy me anything knowing that. It is what it is. I know it is usually between 4 and 6. But that is not very telling. You need a lot more info to usefully apply the number. Would be different if I were out shopping for Dimms.
You are both right! It is best to get your CL and other timings and voltages from the manufacturer, if you can. Also, it's not that useful to have the numbers for your installed memory, because there is not much you can do to change it.
However, CPU-Z does have a very cool feature on the "SPD" tab that reads the JEDEC timing tables from the DIMMs. This information is useful when first setting up a new build-your-own system because the default timings may not be the best for your build. The "Memory" tab in CPU-Z shows the current timing settings.
EDIT: and, BTW, CPU-Z can also show you the manufacturer's name and model number of the DIMMs (SPD tab) which will save you from opening your system to read the tiny print on the DIMMs themselves.
Rick, You were right. It does show the latencies. Now I know that my CAS is 5 (as I suspected between 4 and 6 - right in the middle). But I don't think that this new knowledge will disturb my sleep. lol
Thank you anyhow for the link. I'll keep it around.
Chris, This will be a Zip folder. You unzip it and double click on "cpuz.exe". That will give you the data - after a couple of minutes. Then click on the "memory tab" where you'll find your CAS Latency. I don't know though what you are going to do with the data - other than look at it.
It gives and (confirms) to us Builders a lot info when configuring a Custom Machine.
Remember on Builder Boards, the Bios has settings for changing about everything.
Rick P.♦ :)
This topic has been closed to new replies.