Unable to get Command Center to work, Main I/O USB issues

I also get this message when the Thermal Controller tries to start

System.NullReferenceException: Object reference not set to an instance of an object.

   at AlienLabs.ThermalControls.Domain.Classes.CommunicationServiceClass.get_IsChassisSupportingVenting()

   at AlienLabs.ThermalControls.Domain.Profiles.Classes.ProfileProcessorClass.ExecuteVenting(Profile profile)

   at AlienLabs.ThermalControls.Domain.Profiles.Classes.ProfileRepositoryClass.VentingExecute()

   at AlienLabs.ThermalControls.Controller.Classes.ProfileManagerClass.Init()

   at AlienLabs.ThermalControls.Controller.Main.processWindowsLoaded()

   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)

Does the device manger show any " yellow warning " icons. There may be a driver missing.

I would also do an uninstall of Command Center, run CCleaner, restart and re- install Command Center.

I had the same problem, then I tried this.

Shutdown the PC

Hold the power button for ~30 seconds

Unplug the power cable from the PSU for ~ 30 seconds. Pug cable back in.

Power the PC back on

When I booted back into windows I actually had additional (some nonfunctional) temp sensors that didnt show before. Graphics pump and liquid temp certainly were not there before. There is a total of 7 now. Ambient 1 and 2. Sys Fan, HD fan 2 and cpu pump.  I also think leaving the computer unplugged (not just shut off) over night might have the same effect.

Ghost in the machine

I had the same problem, then I tried this.       Shutdown the PC   Hold the power button for ~30 seconds   Unplug the power cable from the PSU for ~ 30 seconds. Pug cable back in.   Power the PC back on           When I booted back into windows I actually had additional (some nonfunctional) temp sensors that didnt show before. Graphics pump and liquid temp certainly were not there before. There is a total of 7 now. Ambient 1 and 2. Sys Fan, HD fan 2 and cpu pump.  I also think leaving the computer unplugged (not just shut off) over night might have the same effect.

I took this procedure one step further and reset the cmos using the jumper on the motherboard. I no longer have the additional sensors showing but the original sensors are reading properly and my system is running like a dream.

Thanks everyone. I tried each one of those items. And still no dice... Chris is sending me another Main i/o board to see if that works. I'll let you know.

Wil

Got the Main I/O board in yesterday and swapped it out. Everything is back to normal after I updated Command Center... Thank you everyone for your suggestions, and thank you Chris for helping out.... 

Wil

Good to hear you are back in business.

Seems it was all caused by yet another failed MIO-Board firmware flashing attempt (with the 2.x firmware). I sure hope someone at Dell is paying attention and looking into this problem.

I am getting the same error message below when I try to run diags from the f12 menu.  The trigger event was updating Command Center through command center.  It said there was an update available, so I said update it.  When it came back up I had that "unknown USB device" and my forum search began.  I have read just about every post and tried just about every fix.  I am likely going to need a new MIO board from what I can tell.  Please advise.

*attempting to run a diagnostic which resulted in this error: 5D00:0009 - UUTUSBTM- DEVICE_INITIALIZATION_FAILURE user must reattach unit on ROOT HUB port 1 and re-start test.  The Main I/O was not in the available items to test.

I did the following just like Wil but I am still not working.

On my own, I tried moving the Main I/O USB cable to the other MB ports (USB2 and USB3) with the same results. I know all the ports are working because the HUB on top of the system is working fine for each of the inputs.

restting the jumper on the Main I/O

*reseating all cables

I am getting the same error message below when I try to run diags from the f12 menu.  The trigger event was updating Command Center through command center.  It said there was an update available, so I said update it.  When it came back up I had that "unknown USB device" and my forum search began.  I have read just about every post and tried just about every fix.  I am likely going to need a new MIO board from what I can tell.  Please advise. System Type: Alienware Desktop Aurora/Aurora ALX Ship Date: 11/27/2009 Country: United States *attempting to run a diagnostic which resulted in this error: 5D00:0009 - UUTUSBTM- DEVICE_INITIALIZATION_FAILURE user must reattach unit on ROOT HUB port 1 and re-start test.  The Main I/O was not in the available items to test.   I did the following just like Wil but I am still not working.   On my own, I tried moving the Main I/O USB cable to the other MB ports (USB2 and USB3) with the same results. I know all the ports are working because the HUB on top of the system is working fine for each of the inputs.   resetting the jumper on the Main I/O   *reseating all cables

Yes, sounds like the MIO-Board is locked up.

Try variations of this:

Shutdown the PC
If ALX model with Interior Lighting, remove AA batteries from behind black ODD cover 
Unplug the A/C power cable from the PSU for ~ 30 seconds
Hold the power button for ~30 seconds (while A/C un-plugged)

What the above does is dissipate all power from MIO-Board. It helps to do this at various points but especially before testing and the install of a new Command Center version.

Also, with the default reset Jumper ... try it all ways in relation to powered-up status ... ie. boot up with Jumper in non-default position, etc. Non-technical users can skip this step or get a freind to help.

Is the MIO-Board orange light on?

I'm sure you know now, but never use that Upgrade button. Always un-install, reboot, re-install, reboot ... when changing versions. Because there is often a MIO-Board firmware update inside the installers, it's better to only go forward on versions. Get CC from support.dell.com .

If the FlexBay Card Reader is working, you at least know your USB-1 cable is probably ok. Inside that one cable is 2 USB channels ... 1 for the FlexBay, 1 for the MIO-Board.

Yes, using the other USB-2 cable (that goes directly to the top USB ports), is a good simple way to check all your MB USB ports (1-3).

Dell-Alienware Diags is at ... BIOS boot, F12, Utility Partition, System Diagnostics.

If Dell Diags can't detect (and therefore test) your MIO-Board, there is really no chance it will work in Windows. However, I think it might only look for it on USB-1 (it's default connection location). In Dell Diags, make sure the MIO Board is actually tested and the user should further test by changing the light colors.

I have been at this for a couple of days, and I will be at it again tonight to try variations on the techniques.  My MIO board  power light is on, and I did the jumper reset.  I did it like this: power down and discharge.  Move it to the other two pins power up for 30 seconds.  Power down and discharge.  Remove jumper all together and power up for 30 seconds.  Power down and discharge.  Return jumper to original location and power up for 30 seconds.  Power down and discharge.  Power on hit f12 and try to run diags.  Which got the 5d00:0009 message again.

(to prevent windows from loading during the jumper resets I was hitting f12 to finish my 30 seconds, tonight I am going to just let it load windows and then shutdown windows/discharge) Do you think not loading windows would effect the jumper reset?

I will be sure to only use latest version of CC, and my BIOS is A11.

Is the "Flex-bay" card reader the area on top with the usb and 1394 connections?  Otherwise I am not sure what "Flex-bay" is.  I can say all my usb ports are working.  I was using those top ones to move downloads over from a thumb drive.

On my downloads for Command Center I have a "Command Center Desktop" version that has a 4/25/2011 release date but a 2.6.11.0 Command Center for Desktops, A03 version.  Compared to another in the list called "Command Center" and version is 2.5.52.0, A08.  Should I get the desktop version with the new release date?  The thing throwing me is the A03 vs. A08.  I am leaning towards the desktop version...  Please advise.

Do you think not loading windows would effect the jumper reset?

Try letting load . Try every possible variation. 

Is the "Flex-bay" card reader the area on top with the usb and 1394 connections?  Otherwise I am not sure what "Flex-bay" is.  I can say all my usb ports are working.  I was using those top ones to move downloads over from a thumb drive.   On my downloads for Command Center I have a "Command Center Desktop" version that has a 4/25/2011 release date but a 2.6.11.0 Command Center for Desktops, A03 version.  Compared to another in the list called "Command Center" and version is 2.5.52.0, A08.  Should I get the desktop version with the new release date?  The thing throwing me is the A03 vs. A08.  I am leaning towards the desktop version...  Please advise.

The FlexBay Card Reader is installed in one of the Optical Drive Bays. Sounds like you didn't buy that option. No, the top ports are different ... they all connect directly to the MB with various cables.

They are both Desktop Versions.

The latest v2.5.x version is A08 Release. It uses the original MIO-Board firmware 1.x
The latest v2.6.x version is A03 Release. It uses the new MIO-Board firmware 2.x . Also requires the new Dot-Net 4.0 Framework for the CC apps.

That's why the Axx notation started over ... there are 2 different architectures. It's fine to stick with v2.5.x , but once you go to v2.6.x ... you should really only go forward. Since you used the internal updater, it's hard to say what got applied (attempted any way).

That's also why it's better to un-install first (usually a v2.5.x version) before installing v2.6.x . That way no CC apps are using the MIO-Board when the v2.x firmware updater runs ... it has a better chance of success.

If your MIO-Board is just locked up or in-a-loop, you should be able to reset it. If the firmware is corrupt ... well, are you still under warranty?

I am not under warranty. 

I am not under warranty.

That's cool ... then keep at it.

I just wanted to make sure you were not under warranty . If you were, the answer to your problem right about now would be "Call Dell and get it replaced".

Yes, I think a failed firmware update might brick-it (sorta like how a MB gets bricked). However, there might also be an  Emergency BootLoader BIOS (like a dualBios) that will load (if you can find the correct procedure).

So, (while it's broken) are the fans turning? Are they all just running at 100% ?

Still no go. Diags keep giving that same message.  The fans are running all out till windows loads, then they slow down but are louder than normal. So, next step is Emergency BootLoader BIOS.  Any tips on how to find this procedure?  Do you how much a new card runs if that fails?  I saw a mention of a trade in option on another thread.