karl Posted June 16, 2011 Share Posted June 16, 2011 Quote Link to comment Share on other sites More sharing options...
Fiery Posted June 16, 2011 Share Posted June 16, 2011 For both readings we follow Intel's specifications. We're pretty sure both values are right. Did you set the Command Rate to a manual value in the BIOS Setup? Do you have another Windows software that could read the Command Rate and that shows a different value than AIDA64? Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
karl Posted June 17, 2011 Author Share Posted June 17, 2011 For both readings we follow Intel's specifications. We're pretty sure both values are right. Did you set the Command Rate to a manual value in the BIOS Setup? Do you have another Windows software that could read the Command Rate and that shows a different value than AIDA64? Thanks, Fiery Bios <> XTU Quote Link to comment Share on other sites More sharing options...
Fiery Posted June 17, 2011 Share Posted June 17, 2011 Thank you. It seems either we got an incorrect information on how to detect Command Rate on Sandy Bridge processors, or Intel XTU has a bug about Command Rate configuration. We'll do more test runs, contact Intel, and I'll get back to you in this topic once we have a development about this. Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
Fiery Posted June 17, 2011 Share Posted June 17, 2011 We've done a few test runs on our DP67BG motherboard, and it seems no matter if we configure 1T or 2T setting for Command Rate, the system provides virtually identical memory performance in AIDA64 benchmarks. It must mean there's a BIOS bug, and the motherboard is stuck at 1T Command Rate all the time. We'll contact Intel and send them our findings. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.