MSILoading contains a list of parameters (?), like:
mb_DelayLoading_csDDrSize=0 MBytes
...
DRAMFreq_DelayLoading=ok
This and the fact that X.M.P. works without the Command Center installed lets me think that the BIOS and the overclocking tools from the command Center are somehow interfere.
i have no Idea what happened there TBH. i'm sure you deleted the Command Center Profiles after uninstalling it. it should not affect your BIOS Settings after you installed it again.
the MSI Folder is located in C:\Dell\MSI? it could be the Driver Folder for your BD/DVD Drive Eject Button.
i fired up my Area 51 to see what the Files are. the Command Center File was edited today when i started my PC and looks like a Log File. the other one was created on 02.06.2017, the Day when i installed Command Center and it looks like another Log File. you have to start over. uninstall the CC, delete all related Files, shut down, Clear CMOS + Power Drain, then go into BIOS and Edit all the Settings. then install the CC App and hope it works.
Hey CarbonBasedLifeform, thank you very, very much for the effort to help me!
But I went to the whole process today already. Tried to really get rid of every snip of the Command Center this time.
I found a hidden Folder in C:\ that is named "MSIServiceCfg_CC". There are a lot of .cfg files in it, I think this is the place where the OC variables are saved. Deleted it and all software associated with Alien... (spared my XCOM2 files, there are a lot of them with Alien... names ). Even deleted the AlienFX plugins for my Roccat Keyboard and Mouse.
Result is the same: XMP works fine without Command Center, but when I install it, XMP enabled will prevent Windows from starting up.
One thing I noticed is that the computer ran fine the first time I activated XMP after Command Center reinstallation. But once I turned it off and on again, it switched off at the moment the Windows desktop appeared (the moment the Command Center started, I think). It started again, but got stuck in the Windows loading screen. This makes me even more sure that the Command Center is interfering with the BIOS configuration.
I will search around until weekend for a solution, maybe someone of the Dell crew steps in with a hint. After all, it could be worse, 2.133 vs 2.666 is no big deal, but it's still pretty annoying.
I will try a clean Windows install when all else fails.
If that is still no solution, I will have to think about reflashing my BIOS. But this makes me VERRY nervous every time, and I'm not sure if I just would better leave it the way it is now.
really weird. i have no Ideas left. well, i have one but i would not recommend it. do you know how to use CCleaner? i'm talking about Registry Cleaning Feature. you can uninstall the Command Center with the CCleaner and remove all Reg Keys related to the App. BUT be careful with CCleaner.
Strange because I thought XMP profiles were burned into DIMMs. Run CPUz and see for yourself.
On the Aurora-R6, OCing is not supported by base AW-CC. We just do it from the BIOS. If your AW-CC supports OC and setting XMP, I suppose it's possible to have a corrupt config file (hidden) somewhere.
as far as i know 3200 MHz never worked with Area 51. 2666 MHz is the highest you can go. everything above will not work. i am not 100% sure about it because i never tried it myself but i saw an old Thread somewhere here. some Guys tried but could not Boot either.
I stumbled over the same problem as jk4dell while I installed the latest Command Center: my AlienFX Board has the firmware 9.00.00 an the Command Center wants to install 7.00.00.
And I also have now the problem that AlienFX of the Command Center will not work when starting up windows, but if I restart the Command Center manually, it will work without problems.
I’m still in hope that a fresh Windows installation will clean all this mess up, but I have no time at hand at the moment ... always wörk, wörk, wörk!
Roladin
1 Rookie
•
53 Posts
0
July 10th, 2017 02:00
No, it's C:\MSI ...
Ther are two files in it (both text files):
CommandCenter
MSILoading
MSILoading contains a list of parameters (?), like:
mb_DelayLoading_csDDrSize=0 MBytes
...
DRAMFreq_DelayLoading=ok
This and the fact that X.M.P. works without the Command Center installed lets me think that the BIOS and the overclocking tools from the command Center are somehow interfere.
Carbon Based Lifeform
2 Intern
•
872 Posts
0
July 10th, 2017 02:00
i have no Idea what happened there TBH. i'm sure you deleted the Command Center Profiles after uninstalling it. it should not affect your BIOS Settings after you installed it again.
the MSI Folder is located in C:\Dell\MSI? it could be the Driver Folder for your BD/DVD Drive Eject Button.
Carbon Based Lifeform
2 Intern
•
872 Posts
0
July 10th, 2017 03:00
i can check what my A51 has later. i'm working ATM.
Carbon Based Lifeform
2 Intern
•
872 Posts
2
July 10th, 2017 08:00
i fired up my Area 51 to see what the Files are. the Command Center File was edited today when i started my PC and looks like a Log File. the other one was created on 02.06.2017, the Day when i installed Command Center and it looks like another Log File. you have to start over. uninstall the CC, delete all related Files, shut down, Clear CMOS + Power Drain, then go into BIOS and Edit all the Settings. then install the CC App and hope it works.
Roladin
1 Rookie
•
53 Posts
0
July 10th, 2017 09:00
Hey CarbonBasedLifeform, thank you very, very much for the effort to help me!
But I went to the whole process today already. Tried to really get rid of every snip of the Command Center this time.
I found a hidden Folder in C:\ that is named "MSIServiceCfg_CC". There are a lot of .cfg files in it, I think this is the place where the OC variables are saved. Deleted it and all software associated with Alien... (spared my XCOM2 files, there are a lot of them with Alien... names
). Even deleted the AlienFX plugins for my Roccat Keyboard and Mouse.
Result is the same: XMP works fine without Command Center, but when I install it, XMP enabled will prevent Windows from starting up.
One thing I noticed is that the computer ran fine the first time I activated XMP after Command Center reinstallation. But once I turned it off and on again, it switched off at the moment the Windows desktop appeared (the moment the Command Center started, I think). It started again, but got stuck in the Windows loading screen. This makes me even more sure that the Command Center is interfering with the BIOS configuration.
I will search around until weekend for a solution, maybe someone of the Dell crew steps in with a hint. After all, it could be worse, 2.133 vs 2.666 is no big deal, but it's still pretty annoying.
I will try a clean Windows install when all else fails.
If that is still no solution, I will have to think about reflashing my BIOS. But this makes me VERRY nervous every time, and I'm not sure if I just would better leave it the way it is now.
Carbon Based Lifeform
2 Intern
•
872 Posts
0
July 10th, 2017 12:00
really weird. i have no Ideas left. well, i have one but i would not recommend it. do you know how to use CCleaner? i'm talking about Registry Cleaning Feature. you can uninstall the Command Center with the CCleaner and remove all Reg Keys related to the App. BUT be careful with CCleaner.
Tesla1856
8 Wizard
•
17.4K Posts
0
July 10th, 2017 12:00
Strange because I thought XMP profiles were burned into DIMMs. Run CPUz and see for yourself.
On the Aurora-R6, OCing is not supported by base AW-CC. We just do it from the BIOS. If your AW-CC supports OC and setting XMP, I suppose it's possible to have a corrupt config file (hidden) somewhere.
Anonymous User
6 Posts
0
July 22nd, 2017 06:00
Hi there Roladin,
Same problem here.
I hope to use 3200mhz Corsair LPX ram 32gb (8x4)
it works well when XMP disabled at BIOS. (But 2133mhz)
change to XMP Enable, windows log in screen frozen.
So I really wanna solve this problem. and wonder your status.
I think Dell should update or edit with Alien Command Center.exe...
Carbon Based Lifeform
2 Intern
•
872 Posts
1
July 22nd, 2017 07:00
as far as i know 3200 MHz never worked with Area 51. 2666 MHz is the highest you can go. everything above will not work. i am not 100% sure about it because i never tried it myself but i saw an old Thread somewhere here. some Guys tried but could not Boot either.
Roladin
1 Rookie
•
53 Posts
1
July 25th, 2017 03:00
I think that CarbonBasedLifeform is right about the 2.666 Mhz cap.
I stumbled over the same problem as jk4dell while I installed the latest Command Center: my AlienFX Board has the firmware 9.00.00 an the Command Center wants to install 7.00.00.
And I also have now the problem that AlienFX of the Command Center will not work when starting up windows, but if I restart the Command Center manually, it will work without problems.
I’m still in hope that a fresh Windows installation will clean all this mess up, but I have no time at hand at the moment ... always wörk, wörk, wörk!