Unsolved
This post is more than 5 years old
2 Intern
•
152 Posts
0
2755
July 17th, 2018 07:00
CPU pump failing message, reinstall required
Periodically, the thermal controls mechanism fails. "CPU Pump Failing" is displayed on my desktop which alerts me a non-existent problem. Everything is actually working but the sensors report all failing. A repair does not work but uninstall and re-install with "run as administrator" works.
This seems to occur after an update, I assume win10x64 from Microsoft but possibly it could be any upgrade that thinks it needs Visual C redistributable. This is just a guess, as I have not been able to identify the offender. Looking in "add / remove apps" for "c++ Redistributables" I see in ascending install date:
2008, 2012, 2017, 2010, 2013
I installed "Alienware-Command-Center-for-Desktops_J7XK6_WIN64_4.8.23.0_A00" at the exact time that the 2013 runtime was installed so it appears that Dell's thermal command center requires 2013 and ignores the 2017 runtime. The 2010 runtime was installed a full month earlier but I am positive I did not see the "pump failing" error message until this week.
Before the re-install, I tried using the "manual" option to see if I could raise / lower the fan speeds. I got an error message. The error message showed up inside the dialog box for the thermal manual control, and overprinted the existing text which made it difficult to read. I did make out the sentence 'cannot run in elevated mode" which I thought was suspicious as usually elevated mode can run anything.
If any DELL SW developers read this, I hope they will fix the install to use a C++ runtime that is newer and already on the system. The error message should have its own box and not use the manual display screen. The error analysis is not robust enough. If all the sensors report "0" then "cannot run in elevated mode" is not adequate.
This was the second time this has happened in last 3 months so I decide to write the problem up in detail. Hope this helps someone.
[EDIT] I just discovered a version 5.1.27.0, which was in a sticky post here and NOT in the list associated with my Dell system ID. Maybe that will help with this problem.
Also, after thinking about this, I recall having to update itunes and icloud just a few days ago and I am guessing that caused the problem If apple installed 2013 as part of icloud or itunes it may not have installed the runtime in elevated mode and the re-installed of AWCC in elevated mode fixed the problem This is just a guess.
Tesla1856
10 Wizard
•
17.7K Posts
•
70.7K Points
0
July 17th, 2018 16:00
It is NOT required to install anything in Elevated-Mode (and, in fact, might cause problems).
You simply install normally. Installing cleanly (uninstalling and rebooting first) does seem to help. Of course, you should be logged in as first User ... which should be you and you are part of Administrators group.
The question I have is ... What exact Alienware model do you have ?
Joseph Stateson
2 Intern
•
152 Posts
0
July 18th, 2018 15:00
Yesterday I installed that older version using "run as administrator" and after rebooting my Area51 R4 worked fine. OK, today, I installed that new version I saw in the sticky. I did not use "run as administrator" as you suggested.. However, the UAC popped up and asked for my blessing.
I looked up the UAC and according to how it works UAC is asking for for an administrator token so effectively it appears that is equivalent to "run as administrator"
I think the problem is that apple update as that is the only recent update I can think of about when I noticed all the NULL reading on the sensors. I was guessing about the C++ runtimes, maybe there was some other problem. This has happened twice in last 3 months, hopefully it will not happen again but at least I know how to fix it.
Anyway, thermal sensors are still working and I rebooted just to be sure and they are still working.
Tesla1856
10 Wizard
•
17.7K Posts
•
70.7K Points
0
July 18th, 2018 19:00
Hmm, well I'm just speaking from my experience with my old Aurora-R1 and Aurora-R6 (with AW-CC v4.6.20).
If you are logged-in with Admin account, sounds to me like your permissions are screwy. If you found a work-around, I guess run with that if you want.
AFAIK, AW-CC uses Dot-Net as a frame-work, but maybe that changed on later versions (ones reserved for your machine).
Tesla1856
10 Wizard
•
17.7K Posts
•
70.7K Points
0
July 30th, 2018 11:00
I ran Alienware Command Center v4.6.20 through DotPeek (DotNet Analyzer) and it does appear to still be a DotNet program.
That means that once it's running on a machine (and with its required DotNet Framework) it's very hard to de-rail that. Any new versions of DotNet or programs are simply loaded and run along-side this working set (does not replace them).
I suggest you find the proper working version of AW-CC for your machine and always use it. Don't Upgrade it or Repair it. If it has a problem, just uninstall, reboot, and clean-install it.
For now, I would also not install any kind of Over-Clocking plugins and should probably skip the Over-Clocking for a while in general (for stability and your CPU is plenty fast anyway).