This problem is usually caused when the application itself or the Master I/O board doesn't read the correct temperatures. I recommend you completely uninstall and re-install the Command Center by following the troubleshooting steps on this article.
When I shutdown the PC overnight, and cold boot in the morning, sometimes, almost always, Alien FX Lights aren't lighting and the Alien Head eyes a pulsing yellow and white and Thermal control sensors are all non-existent, then without powering down, I restart the machine and walla, everything is ok.
My machine used to do this once or twice a year. Lately, it has been doing it once a month.
Not much has changed hardware-wise, but I did install a SSD about a year ago.
One thing that will cause this is if the Aurora gets un-plugged while shut-down. I have a APC-UPS, so that is not really possible. It sometimes happens after servicing or cleaning but that's to be expected. I'll ignore those events.
My theroy is that it is misinterpreting the Power-State of the machine. It thinks the Aurora is asleep, so the MIO-Board itself goes into a Sleep-Mode. This also fits with "warm rebooting fixes it" because it gets a chance to re-check the machine status on reboot.
So, why does this happen intermittently? IMO, possible causes: 1. Bad, cold, or lose connection somewhere in MIO-Board wiring 2. MIO-Board is failing 3. With SSDs, the boot and Windows initialization is much faster now. Maybe the PowerState-Check fails or times-out sometimes and the default is Sleep. Something along these lines.
There also has been however an intermittent problem with CC mainly the Alien FX not communicating with the Master I/O on a cold boot. Even on a clean install of window 7 professional, and new SSD for the booting. Here is the issue. When I shutdown the PC overnight, and cold boot in the morning, sometimes, almost always, Alien FX Lights aren't lighting and the Alien Head eyes a pulsing yellow and white and Thermal control sensors are all non-existent, then without powering down, I restart the machine and walla, everything is ok. I installed an SSD to speed up things. Restarting in the morning to get the I/O board to properly communicated with CC is getting annoying.
Thank you I didn't see that thread at first. I followed the instructions on that topic and uninstalled and re-installed CC. This fixed my ambient sensors.
Thanks Tesla, come to think of it, this started happening after the SSD was put in for the boot up boost. This morning the PC didn't do it, but I starred at it very hard while it was booting.....LOL!
Alienware-Naomi
1.8K Posts
0
March 17th, 2014 10:00
Hi!
This problem is usually caused when the application itself or the Master I/O board doesn't read the correct temperatures. I recommend you completely uninstall and re-install the Command Center by following the troubleshooting steps on this article.
Tesla1856
8 Wizard
•
17.3K Posts
0
March 18th, 2014 13:00
My machine used to do this once or twice a year. Lately, it has been doing it once a month.
Not much has changed hardware-wise, but I did install a SSD about a year ago.
One thing that will cause this is if the Aurora gets un-plugged while shut-down. I have a APC-UPS, so that is not really possible. It sometimes happens after servicing or cleaning but that's to be expected. I'll ignore those events.
My theroy is that it is misinterpreting the Power-State of the machine. It thinks the Aurora is asleep, so the MIO-Board itself goes into a Sleep-Mode. This also fits with "warm rebooting fixes it" because it gets a chance to re-check the machine status on reboot.
So, why does this happen intermittently? IMO, possible causes:
1. Bad, cold, or lose connection somewhere in MIO-Board wiring
2. MIO-Board is failing
3. With SSDs, the boot and Windows initialization is much faster now. Maybe the PowerState-Check fails or times-out sometimes and the default is Sleep. Something along these lines.
SOF Phantom
15 Posts
0
March 18th, 2014 07:00
SOF Phantom
15 Posts
0
March 18th, 2014 07:00
SOF Phantom
15 Posts
0
March 19th, 2014 06:00