Unsolved

This post is more than 5 years old

1 Rookie

 • 

49 Posts

176659

August 21st, 2015 22:00

Alienware Area 51 R1 - Windows 10 Command Center PCI Fan Fix

Update #1 8/27/15

Wanted to give an update to everyone that I'm still smooth sailing with no issues :) It's possible it may have been related to a windows 10 update but if anyone is still experiencing issues please post to this thread.

I don't recommend anyone to do the following steps because it can result in a bricked MIO board but here's what I did to fix it temporarily.

1). I booted to windows 10 and installed the latest CC version 2.8.11.0 (Cass has posted the link below)

2). During installation it asked me to restart the computer. I did and fans were still loud. Then I booted to Windows 7 image and did a repair (On the Win 7 image, I had CC 2.8.9.0 installed), It did a MIO flash -  most likely to the 2.8.9.0 bios)

3). Booted back to Windows 10 and everything has been fine (I may have done a power dissipation at the end)

So apparently I now have CC 2.8.11.0 installed in windows 10 but have the MIO board flashed to the 2.8.9.0 version. I hope this makes sense. I expected the board to be flashed to the new version when I did the latest install in windows 10 but it must have somehow skipped the MIO flash.

The only other thing I noticed is I use to have a blue blinking light at all times on the MIO board. Now I just see the orange light.

Original Post:

I'm creating this post because I recently ran into an issue when I upgraded my computer to Windows 10. My fans were on full blast and after changing CC profiles, they wouldn't budge from 55% or 100%. Power dissipation, repair, uninstall/reinstall and no luck.

Fortunately I was able to fix it and would like to share that information here in case anyone experiences the same issue.

First, I recommend anyone whose considering upgrading to windows 10 to first go view this informative post by our wonder friend Cass.

 

So here are your options for windows 10 install:

1). Upgrade from an existing windows 7 or 8 installation (recommended)

2). Clean Install Windows 10 (either by formatting and using an image or using the reset feature after upgrade)

Reason I recommend the first option is because you have a WORKING CC in place. After upgrading it's very unlikely to run into any issues (registry, files, and settings are already in their proper places).

Also I had success using Alien FX 2.8.09.0 but Cass has mentioned success with 2.8.11.0 as well.

Unfortunately for me I decided to do #2 install. After windows 10 installed, I installed AlienFx 2.8.09.0. Everything was working fine for a few weeks until one day I woke up my computer from sleep and the PCI and HD fans were on full blast at 100%.

I tried CC repair tool through uninstalling CC through Programs and Features and although in hindsight it looked like it work, it was a temporary fix until I restarted and woke my computer from sleep again (also noticed it tried to flash the board again).

Cass recommended that I go back to an old Win 7&8 image and try running repair from there and it ended up fixing the issue until a few days later it showed up again. (repair did not perform a MIO flash).

I was finally able to figure out what the issue was and I think it had to do with the flashing of the MIO board during the CC installation in windows 10. It DOES NOT WORK PROPERLY. It will look like it's flashing the board but it must not be flashing correctly (at least for me it didn't).

Then I thought it might just be the fact that 2.8.09.0 is not compatible so I tried installing 2.8.11.0. It told me to restart and the issue didn't go away. I also noticed it didn't flash the board (it was still running 2.2.0.0)

To get it to work again I went back to a Win 7 image and repaired CC and this time it flashed the MIO board.


After flashing the board properly in a win 7 environment, I rebooted to my win 10 drive and all was well. Sleep, changing profiles, and auto mode worked again.


I advise against using CC install wizard on Windows 10. Go back to an older version of windows and run it there to avoid issues. If you don't have an old OS image, you can try running the wizard in compatibility mode but I don't know how that will fare out.


So again to reiterate, use #1 to install windows 10. It will work better in most cases.

If fans go crazy and restarting or power dissipation doesn't fix it, try reflashing the board in a win 7/8 environment and it should do the trick. I'm using 2.8.09.0 currently and its working fine. Also remember that this is the last version of CC that will work with aftermarket motherboards (in case like me your considering upgrading your board in the future). Cass has also mentioned that if you have already installed 2.8.11.0, you will have to just use an installed image that has the latest version already when you swap the board (or down flash to 2.8.09.0 and pray :)

I'll keep you guys informed with any updates. Feel free to ask any questions and I'll try my best to answer them.

kiax0001

8 Posts

August 22nd, 2015 05:00

Hi. Thanks for the advice. I did run into the same problem with my Area 51.

This is how I did it (before knowing the fix from you). I went back to restore and did a clean reformat of my computer. Then did all the windows update (over 240). Then installed Windows 10..After a day, I got the loud noise from my fans. So after researching, I did download the latest version of Command Center and did a profile changing the fan speeds.  After going to thermal control on the start bar, I updated the profile.

This did work, but I do run into some problems. When first starting up, at times, the fans will run full blast, Then when it goes into the Windows 10, the profile loads and the fans are back quiet again.

Is there any way to do a regedit to fix it where it will always install before hitting Windows 10. I would hate to go back through the whole install again.  So you are saying when you do a restore to the factory, update the Command software. then install Windows 10 and it will keep it?

Thank you so much for your advice. I wish I had read it before installing..I do have to say through this work around is working for me and Windows 10 is running smoothly on mine..I do have one issue with the Venting fans, they do not close.

Judi Haley

1 Rookie

 • 

49 Posts

August 22nd, 2015 10:00

Couple of quick questions:

1). Did you upgrade after you reformatted or clean install windows 10?

2). What version of CC are you using?

3). When you said you download the latest version of CC, did you install it in windows 10?


To answer your question yes. Restore to factory, update the command center, then upgrade to windows 10 and it should work fine because you don't need to install it again in windows 10.

If it's acting strange in windows 10, you must be able to go back to the factory image drive (or any win 7/8 drive) that CC was installed and either reinstall it or uninstall/reinstall. Be sure the MIO board gets flashed during the install/repair process.

I've experienced the same issue where setting up a manual profile works after windows 10 loads but as soon as you change it to auto or a different thermal profile it goes crazy and requires a restart to properly reload the profile. Apparently this happens if you install CC in Windows 10 (or repair it for that matter).

I suggest you find a separate HD/SSD with windows 7 loaded on it as well as the CC version your currently using and perform a repair using the un-installation wizard. Make sure the MIO board gets flashed in win7/8 environment. Then restart and load the win 10 drive and all is well.

6 Professor

 • 

1.8K Posts

August 22nd, 2015 11:00

I installed W10 on my Area-51 August 1st & I haven't used it since, but it was working properly on day one. In the interim I've neither received updates for it nor taken it out for a test-drive. There have been multiple reports from Aurora owners who's fans are also going helter-skelter. I don't know of any reg-edit or tweak or fix at the moment, & the next time I'm online with my Alien will be in October for Threshold Wave2 & whatever updates it entails. I won't be trouble-shooting fan issues anytime soon. Since we have 6 hard drive bays, the advice is to have W10 on one hard drive, and W7/8 on another. When problems arise like this, boot into 7/8, test & possibly fix CmndCntr issues like this, then boot into 10 and see if normal behavior is restored.

1st line of defense, unplug machine, press top power button down for 1 minute to dissipate energy, plug in and restart. Next, a fast method is to launch CmndCntr.exe in W7/8 & click the 'repair option', or do an uninstall / reinstall there. Possible vents fixes are here:

  • "I tried changing the 'Hybrid Shutdown' setting in the 'Change what the Power Button Does' menu. That setting fixed the issue with the vents not closing at all during shut-down"
  • Area-51 R1 Windows 10 Success Command Center & AlienFx 2.8.11.0 / 2.8.09.0 & Top Vents Issue / Fix {mid-way is a troubleshooting Cmnd Cntr section with Jumper Reset procedure)
  • http://en.community.dell.com/owners-club/alienware/f/3746/t/19625158

the last version of CmndCntr is here, 2.8.11, & requires .net framework 3.5:


Area-51 R1 Latest Last Final Bios Version A11 Link to R311673.exe on Dell.com

Aurora R4 fans at 100%

If this is a Dell approved & Dell tested upgrade, why are the fans wigging out??? Where's the fix? Where are the Dell techs to weigh in on this issue with a fix? Where ???

6 Professor

 • 

1.8K Posts

September 16th, 2015 15:00

@i4laine --> did u find the tricks to try to get your vents to close? It's in your power plan & most likely turning off fast startup in 10:

For fans at 100%, open CmndCntr > Thermals > if PCI Fan & HardDrive Fan1 are set to auto, set to manual fixed' (& set a speed in %) or manual 'curve' & set a curve, & report back if you found a fix or didn't.

edit: note the latest suggestion > "enable the thermal controller in the windows start up:

  • go to run, msconfig & startup
  • thermal controller starts running as soon as the desktop screen's loaded
  • vents open & the lights come on".

No Events found!

Top