FireRx1

Perhaps this should be addressed to the team, but as Computing is pushing forward to the x64 bit realm, there are issues that needs to be addressed before launch, or Windows 7 will be behind the curve. One issue I've noted is Windows still refers to the FSB to determine the BCLK speeds on most processors. This was fine, a year ago when processors speed calculations were dependant on the FSB. However, with the advent of the new Intel Core i7 processors, especailly the Extreme additions, the BCLK is determined by the Multi settings, rather than the the QPI/FSB setting alone. For example:

My BCLK on my Core i7 965 EE is 24x, with a QPI of 133mhz. That's is seen in bios , and windows at 3.2 ghz. However, Many users, including myself, overclock our processors. So when I set my multi to 34x with the same QPI I'm at 4.5ghz in bios. But in Windows it remains 3.184Ghz. This is because Windows is using the new processors QPI settings to determine the BCLK only, when in reality it should be using the multi's setting also to determine the clock speed of the processor.  I bring this up because I sent feedback on this issue, and have yet to see an update to addrees it.  As you know, most new computer will have the intel Core i7 processors in them. It would be nice to have windows read them correctly,  versus having to use third party software to get correct processor speed ratings.
Thanks!

 [img]http://img.photobucket.com/albums/v209/firerx/whatswronghere-1.jpg [/img]



I hope they fix this!  Todays Core i7 965/975's don't use just the FSB/QPI to identify the BCLk of a processor. It also uses the mutli settings. It appears a kernel issue , and I've sent this to the team.