This post is more than 5 years old
5 Posts
0
14247
January 2nd, 2013 13:00
Command Center, AuroraR1, Clean Install
I thought this Command Center garbage was fixed. .. Completed clean install of Win7 on new HDD. Driver deployment suggested by Dell / Tesla. Prior to that, I ran Diagnostics (thru dvd) and Physical tests to see if MIO-board was working, getting power, bricked etc.. However I did not disconnect during install as was suggested safeguard (believed CC v2.8.9.0 would be enough) This isn't my first go around with this. Earlier this year, had issues that I believe eventually led to systemic failure of HDD. I now plan to completely remove CC and reinstall in hopes of a miracle.. Any suggestions are greatly appreciated.
Can someone please post link on how to completely remove CC so I can reinstall (feeling of returning for rancid well water)
This is what greeted me on my first log-in after CC install - it's like the calling card of bad things to come-blue and black screens, oh my!. I hope I am overreacting, but this CC crap is like a bad rash... Help me Obi-wan, you're our only hope.
THERMAL CONTROLLER
System.Threading.ThreadStateException: Thread is running or terminated; it cannot restart.
Server stack trace:
at System.Threading.Thread.StartInternal(IPrincipal principal, StackCrawlMark& stackMark)
at System.Threading.Thread.Start()
at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchedQueueProcessor.initiateApplicationLaunchedThread()
at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchWatcherClass.Start()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at AlienLabs.CommandCenter.RemotingService.Domain.ApplicationLaunchWatcher.Start()
at AlienLabs.ThermalControls.Controller.Classes.ProfileManagerClass.Init()
at AlienLabs.ThermalControls.Controller.Main.processWindowsLoaded()
at AlienLabs.ThermalControls.Controller.Main.Window_Loaded(Object sender, RoutedEventArgs e)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at MS.Internal.FrameworkObject.OnLoaded(RoutedEventArgs args)
at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
0 events found
morblore
2 Intern
•
2.4K Posts
1
January 2nd, 2013 13:00
Try the 2.8.11 version and see if it will write over the old one and fix the issue. If it does don't ever update it again. If you install the OS open the case and unplug the thing and make sure you install the same version of ACC again. Better safe then sorry I believe.
Also, don't put that CD in your drive again. You don't want to take that chance ether. It could brick it. Only use drivers from the Dell support site from here on out. You can run the PSA test through the BIOS, hit F12 and scroll down to the pre-boot system test thingy and run that. There is no need for that CD anymore.
Tesla's write up on it is the best around. If you used that then just do what he said again.
ACC 2.8.11: en.community.dell.com/.../20231391.aspx
Tesla1856
8 Wizard
•
17.5K Posts
0
January 2nd, 2013 14:00
Yes, a Jedi Mind Trick might help
I am running AW-CC v2.7.25.0
Dell never wrote a proper AW-CC MIO-Board driver erase utility. It installs it's drivers in a strange PnP hidden way and then MIO-Board itself is not categorized in Device Manager in a conventional way.
After a clean install, if the MIO-Board is not responding:
- Try Power Dissipation Fix
- Try testing MIO-Board with Dell Diags (sometimes this will reset it)
- Try clean installing a know good working AW-CC version (for your machine model ... there are several different MIO-Board versions)
If all that fails, and the MIO-Board still tests good in Dell Diags, try a fresh clean install of Windows and it should work this second time. We have seen users have problems with this. Either the drivers don't get installed properly that first initial time or Windows MIO-Board drivers get corrupt somehow. Definitely a "Windows problem" because a second clean install fixes it.
We have also seen clean Windows installs kill MIO-Boards (maybe it's the hardware detection phase or something). Anyway, that's what the "dis-connection step" is all about. You can identify this problem because the MIO-Board will stop responding in Dell Diags (outside of Windows).
Bobs_Big_Boy
5 Posts
0
January 2nd, 2013 23:00
....Smells like.. victory.. I dialed it back to v2.7.25.0, device mgr and diagnostics clean... went in and tooled with it, seems stable.. for now...perhaps the gremlins lay in wait.
Sincere thanks to both. Accessible user help that is prompt, concise and objective isn't a typcial get these days.
Bobs_Big_Boy
5 Posts
0
February 8th, 2013 16:00
Tesla1856
8 Wizard
•
17.5K Posts
0
February 8th, 2013 16:00
morblore
2 Intern
•
2.4K Posts
0
February 8th, 2013 19:00
Plus if it's only on shutdowns it's more then likely just a driver/OS issue.