![]() ![]() I did not OC, simply loaded the XMP profile for my RAM, and reduced ram Voltage from 1.66 to 1.64 because BIOS warned me about going over 1.65V. In XP, CPU-Z showed my clock speed at ~3.4Ghz, while in W7, my clock speed was at ~1.6GHz. One of the reasons I was meddling in BIOS was because I noticed different results in Windows XP Pro 圆4 SP2 and Windows 7 Enterprise 圆4. So I guess that is my next question: Does the OS communicate via SpeedStep, or interact with SpeedStep in any way, or is it all in the hands of SpeedStep when it comes to turning the clocks up or down? As I understood it, it was the OS that was responsible for NOT clocking up when necessary, and after your explanations, my guess is either I misread, or OS controls SpeedStep. What I read was that the OS sometimes screwed up when it needed to put the clock speed back up, not SpeedStep. I wish I had the links on hand so I can post them here or at least re-read them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |