Command Center Crashing!

Question

Hello,
Just yesterday I brought a Z97 Gaming 5 to replace an older Z77 board.  Went to install Command Center and other utilities, and from the get go not working. Let me be specific, the main thing I need is command center, however Super Charger says "Super-Charger only supports MSI mainboard" when launched and the MSI gaming app says "The platform does not support this application".  Now on to the more annoying matter. Command Center refuses to even open, crashes on startup.  It did startup ONCE but was stuck on the loading screen.  Used the debug mode and got this:
[Loding]
create=on
service=ok
startTime=ok
My Event Viewer Logs are as such:
Log Name:      Application
Source:        Application Error
Date:          17/07/2014 10:55:43 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Benji-PC
Description:
Faulting application name: CC_LoadingPage.exe, version: 1.0.0.68, time stamp: 0x5399654f
Faulting module name: Smbios.dll, version: 0.0.0.0, time stamp: 0x52a0ce71
Exception code: 0xc0000005
Fault offset: 0x000013d0
Faulting process id: 0x19fc
Faulting application start time: 0x01cfa1be6b1cd0c4
Faulting application path: C:\Program Files (x86)\MSI\Command Center\CC_LoadingPage.exe
Faulting module path: C:\Program Files (x86)\MSI\Command Center\Smbios.dll
Report Id: a93abff1-0db1-11e4-bfb8-448a5b9c6c7e
Faulting package full name:
Faulting package-relative application ID:
And:
Log Name:      Application
Source:        .NET Runtime
Date:          17/07/2014 10:55:43 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Benji-PC
Description:
Application: CC_LoadingPage.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at CC_LoadingPage.MainWindow.Type2_Product Name(System.String ByRef)
   at CC_LoadingPage.MainWindow.Type2_Product Name()
   at CC_LoadingPage.MainWindow..ctor()
   at CC_LoadingPage.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at CC_LoadingPage.App.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1(System.Object)
   at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOper ation.InvokeImpl()
   at System.Windows.Threading.DispatcherOper ation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.RunIn ternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOper ation.Invoke()
   at System.Windows.Threading.Dispatcher.Pro cessQueue()
   at System.Windows.Threading.Dispatcher.Wnd ProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbac kOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapp er.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHe lper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.Leg acyInvokeImpl(System.Windows.Threading.DispatcherPrio rity, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMe ssage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.Pus hFrameImpl(System.Windows.Threading.DispatcherFram e)
   at System.Windows.Threading.Dispatcher.Pus hFrame(System.Windows.Threading.DispatcherFram e)
   at System.Windows.Application.RunDispatche r(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at CC_LoadingPage.App.Main()
NOT SURE WHAT OTHER LOGS ARE NEEDED.
PLEASE HELP! I have tried all the latest beta's (I think) and flashed the latest BIOS.
Thanks.

Answer 1

Quote from: benjiconnor478 on 18-July-14, 10:33:14
Thanks, I tried that one and still no cigar.  It also appears there is something wrong in general as when installing SpeedFan and other programs alike to check whether its an isolated issues, SpeedFan could not pick up any of my Fans connected to the board...except for the GPU! What is this! As for the Command Center, nope, I re installed NET again and engine drivers etc... Any Ideas?
Still getting same Error Events for the NET framework and CC itself. I need a fix ASAP as I have no real way to control fans or small clock increases, minus BIOS of course. And controlling fans as i said previous seems...interesting right now.
SpeedFan won't detect the fan sensors, it's not just you. On the command center issue, try this, install MSI Intel Extreme Tuning utility http://download.msi.com/uti_exe/extreme_tuning_9.zip, and give the Command Center 1.0.0.70 beta 1 another try.
It refuses to run for me unless Intel Extreme Tuning is also installed..... also, make sure you're running the latest version of the chipset driver, and the Intel Management Engine driver.