- Thread Author
- #1
I've been trying to install Windows 7 RC (Build 7100) on a brand new Dell box (model: Optiplex 760) for the past week or so. I've tried both 32-bit and 64-bit. The issue I'd been having was a very interesting one. What would happen is that any processes on the computer (logging in, the clock, installing applications, etc) would run extremely slow, if not motionless unless I was moving the mouse. For example, when logging in the circle that moves around showing you it is processing information, it would stall and only move forward if the mouse was moving.
I tried all of the latest drivers from Dell to no prevail. I then noticed that login scripts on the network were not working and this was found out to be because the clock was too far off. I then noticed that the clock would only count seconds if the mouse was moving, hence why the time was way off as I am not constantly moving the mouse.
Finally after a lot of head scratching and no luck on Google...I decided to look at all of the options in the BIOS. After booting to the BIOS I noticed two (2) different options that I thought could be causing issues:
Under Performance >
Intel SpeedStep & C States Control
Both were checked by default so first I unchecked both of them. When I booted into Windows it booted extremely fast and I watched the clock run for two (2) solid minutes without moving the mouse. I then booted back to the BIOS and turned on C States Control but left Intel SpeedStep off. This time when I booted in I got the same issue of a hault in processing unless the mouse was moved.
To be sure I had pinpointed the issue, I rebooted again and turned on Intel SpeedStep and off C States Control. When Windows 7 booted up, everything worked flawlessly. I came to the conclusion that Intel's C States Control causes issues with Windows 7 perfoming properly...at least on my Intel board from Dell.
In the BIOS this is what the details say under "C States Control":
"This option enables or disables additional processor sleep states. The operating system may optionally use these for additional power savings when idle."
So it seems that Windows 7 must be idling the processor when the computer does not have mouse movement...almost like a sleep mode.
Interesting issue, with interesting solution...just thought I'd share the information for anyone else out there experiencing something similar!
- Jason
I tried all of the latest drivers from Dell to no prevail. I then noticed that login scripts on the network were not working and this was found out to be because the clock was too far off. I then noticed that the clock would only count seconds if the mouse was moving, hence why the time was way off as I am not constantly moving the mouse.
Finally after a lot of head scratching and no luck on Google...I decided to look at all of the options in the BIOS. After booting to the BIOS I noticed two (2) different options that I thought could be causing issues:
Under Performance >
Intel SpeedStep & C States Control
Both were checked by default so first I unchecked both of them. When I booted into Windows it booted extremely fast and I watched the clock run for two (2) solid minutes without moving the mouse. I then booted back to the BIOS and turned on C States Control but left Intel SpeedStep off. This time when I booted in I got the same issue of a hault in processing unless the mouse was moved.
To be sure I had pinpointed the issue, I rebooted again and turned on Intel SpeedStep and off C States Control. When Windows 7 booted up, everything worked flawlessly. I came to the conclusion that Intel's C States Control causes issues with Windows 7 perfoming properly...at least on my Intel board from Dell.
In the BIOS this is what the details say under "C States Control":
"This option enables or disables additional processor sleep states. The operating system may optionally use these for additional power savings when idle."
So it seems that Windows 7 must be idling the processor when the computer does not have mouse movement...almost like a sleep mode.
Interesting issue, with interesting solution...just thought I'd share the information for anyone else out there experiencing something similar!

- Jason