Area 51 alx command center issues

No change in device manager when pulling the plug & reinserting the plug 'live' does not sound ok.

Any motherboard replacement posts on this forum may not apply to you & probably apply to an aftermarket swap. The Alientube teardown vid is about all you'd need to see what happens to get old out & new in. We're jumping the gun of course ..

This was my very 1st forum post, pics at https://community.dell.com/thread/4259" rel="nofollow noopener noreferrer nofollow ugc">Need original Win7 recovery media

You'd 've been given either the logo'd DVD or the basic Dell branded DVD. The Alien logo'd 7 DVD installs activated, Dell's basic 7 DVD reqwires you input/activate your product key.

7DVD's are no longer purchasable from Dell > $35+ for a reinstall USB. Sometimes available on eBay.

Dell reinstall DVD's available, always buy a SP1. We might pretend you install 7 from a Dell DVD, only to discover it didn't help. In that event, you might keep your original install alive so long as you did the clean install on a different drive. i.e. > boot into 'new replacement motherboard' using old install.

there may be places to download a copy of 7 still, I don't know where from though.

One wonders if as a test, Windows 10 might be tried for free (???). Tesla is up & running 2.8.9 on 10.

The drivers should all come from Dell.com

If I have to go for the night, good luck

Ok, given all of the diagnostic tests have come back basically thumbs up (lights cycle, vents cycle, fans cycle), and all of my USB headers work for everything else, the issue seems to be almost certainly software related no? Either getting the correct firmware installed on the board (could already be too late for this from the sounds of it) or getting command center to just play nice with my machine.  In multiple posts I've seen several different .Net frameworks mentioned:

"AWCC v2.8.9.0 will not install unless proper version of Dot-Net is installed. IIRC, it's v3.0.x or 3.5.x"

"reinstall .net 4 / 4.6; if it fixes the issue, apply the fix to your daily-use drive"

"2.8.9 should have zero issues, CC 2.8.11 is another version, reqwires .net3.5, but do not expect that simply changing versions will 'cure' the issue"

If my problem truly is NOT hardware related (it very well might be) could not having the correct framework prevent CC from installing correctly, updating the board firmware, and thus communicating with my tower?  I have already unistalled 4.6 and clean installed 4.0, followed by a clean CC install and still no board found.  Which .Net should I be using? Dumb question but I'm assuming they're sequential? As in .Net4 is an updated version of 3.0 and 3.5?  Is there one that should DEFINITELY work or should I just try them all?  Is there anything to do after running the executable file for the install of the .Net frameworks?

Also, I saw your repeated warnings about messing with the BIOS, and how easy it is to brick something.  As I mentioned I'm on BIOS A11, even though A10 is listed under the dell drivers.  Could A11 be something preventing CC from working properly or should I just avoid messing with that basket of snakes all together?

Again, this is all just speculation on the fact that the hardware, for the moment, seems to be passing the tests.  As of now I am backing up my HDD and will be upgrading to Win10 by tonight to see if that does anything.  That failing, I'll shell out for the Win7 installation flash drive and try the clean install.

Thank you so much for sticking with me and for lending me your experience and expertise.  No one else has been remotely close to as helpful as you have all been.  Thank you for your patience and your time.  I sincerely appreciate it.

1. Ok, given all of the diagnostic tests have come back basically thumbs up (lights cycle, vents cycle, fans cycle), and all of my USB headers work for everything else, the issue seems to be almost certainly software related no?   2. "AWCC v2.8.9.0 will not install unless proper version of Dot-Net is installed. IIRC, it's v3.0.x or 3.5.x"   3. 2.8.9 should have zero issues, CC 2.8.11 is another version, reqwires .net3.5, but do not expect that simply changing versions will 'cure' the issue"   4. If my problem truly is NOT hardware related (it very well might be) could not having the correct framework prevent CC from installing correctly,

1. Right, that is my guess. Windows problem ... seen it before in other users posts. MIO-Board in an un-conventional device and driver load strangely.

2. It won't even begin to install. It will prompt you to install the proper version first, or might even lead you to proper version.

3. In Win7-64, I use AWCC v2.8.9.0 . In Win10-64, I use v2.8.11.0 ... installed in Win8-Compatibility-Mode (only that one checkmark in Compatibility TroubleShooter). Works fine for me ... for a whole week or so now, on my stock Aurora-R1 (very similar to your Area51-R1)

4. No, because the installer won't even start. If it can't start, it can't install incorrectly [:)]

Addict archived his Alien-Version 7Home 64sp1 ISO (T8R68) for download on Mega:

• Alienware Windows 7 Home Edition 64 bit Re installation disk
• https://mega.nz/#!6R5XUaqA!mKLuzmTPSvD1y-u1DgWMiVw470vA7iQZqZjUIM6jp0M

Another 7HP:

• windows 7 disk?
• https://mega.nz/#!6R5XUaqA!mKLuzmTPSvD1y-u1DgWMiVw470vA7iQZqZjUIM6jp0M

Download Windows 7 Disc Images (ISO Files) >< Legal Download from DigitalRiver: Windows 7 SP1

Link Link2 Link3 Win7 Forum > search ISO

.net4 2.8.9 > .net3.5 for 2.8.11

yes, try software fix before replacing mthrbrd > mthrbrd suspect due to usb high-current fail

I told you to call or chat in about an X504R front panel / bezel ... they have 10 left, last of them, probably discontinued after this, who knows. Get one while you can. Also, you can haggle with them, try for $150/shipped then work your way up til the both of you agree on a price:

How to tell standard vs ALX

Standard W558R Lunar R841R ALX X504R

obligatory edits

I have a reply in queue, waiting on approval to publish re: 7 ISO links, see this link

https://www.microsoft.com/en-us/software-download/windows7

Our 1st line of defense is 32BIT DIAG: if 32bit can't detect mio, you get nowhere in this life. Next, it has to pass all tests in 32bit (more or less, for instance yours is good save for odd motor fail). From there, I like to think ALL info related to testing MIO has been posted in your thread - or - a link to another thread has the info. Unraveling it all on your end is the task at hand. There is a fix somewhere in all that's been said, be it a clean 7 install, replace mio, replace mthrbrd etc.

For a 10upgrade (just to get some fresh software going), unplug mio usb_3 during upgrade as we would a clean7 install. Since 10upgrade will 'overlay' your driver suite, on 1st desktop I would power down > plug in usb_3 > power up > see if 10 installs driver (detects mio as a new usb device), then proceed from there. Launch CmndCntr, see if tower is displayed finally. If not, you have the 'detect mio scenario', & you can launch CC.exe & try a 'repair'. You have the 'yank usb-3 when pc is live' while watching device manager & 'plug usb_3 back in while sysem live' also, looking for a change in device manager. Again, all of these tips/tricks exist in your post, you have to unravel it all. 10 should install with .net4.6 onboard, so 2.8.9 should 'work' (note I said 'should), 2.8.11 may reqwire .net3.5 be turned on as a windows feature.

- additional -

.netframework: I can posit a loss of AlienFx features due to .net corruption; however, your situation includes the following:

• loss of Tower in AlienFx UI
• 'board not detected' in AlienFxTester.exe
• device manager doesn't respond when yanking / reinserting usb_3 when pwr on
• device manager / 7 do not respond when placing usb_3 into new / other usb header
• 32bit says 'ok' > I assume your exterior lights light up (a good sign mio 'wants to work')
• all the while your top usb2.0 ports 'work' with other devices
• the plot thickens over *** the problem is

what we know is that if clean 7 install (with driver suite + .et applied) or 10upgrade, if mio inside case does not produce harmony (tower won't show in AlienFx / AlienFxTester.exe 'does not detect board') you have a new 604GC test unit. If new test unit doesn't cure issue, there is almost nothing left to blame.

• RedPlanetTrading got that 604GC direct from Dell, it should be a winner
• do not revert back to bios A10

We're waiting on a clean OS install to tell us what we need to know: is it software-based ...

yes, try software fix before replacing mthrbrd > mthrbrd suspect due to usb high-current fail

I didn't catch that it was still giving that error in Dell Diags. I agree that it does point to a core hardware problem.

I would disconnect all USB headers from motherboard and test with Dell-Diags. If it passes finally, MB might be ok. Proceed to connect each USB cable one-at-a-time (including front panel, MIO-Board, etc.) to see which "USB device" it causing problem (over-amping the header).

I would then replace offending part and re-test from beginning.

I think this problem needs to go away before final MIO-Board/AW-CC troubleshooting.

Thanks for the replies regarding .Net framework.  That cleared a few things up for me.  Thank you cass for researching that part for me, but I had already contacted dell and was elated when they told me they had it =D

Some updates:

With all usb headers (MIO USB3 USB2 USB1) unplugged, I tested board in dell diag.  No over current indicated, all usb tests pass.  Plugged back in one at a time (removing the previous one at the start of each test) and found that I get the over current indicator with USB3 plugged in and nothing else.  What does USB3 correspond to part wise? What kind of problem does this indicate?

Another possibly relevant problem I've had ever since that one tech came out to do the swap way back when is I have sound coming from only one speaker.  I initially thought this was just a sound card or driver problem until I realized I don't really have a sound card.  When I run the speaker test, I get pings from all speakers, but during game play or music streaming, I get sound from only front right speaker and subwoofer.  I have the basic logitech 5.1 surround speaker set up.  Could be relevant, might not be.  Thought I'd mention it.

Have NOT gotten around to win10 or even win7 yet as I've been fumbling with my backup drive.  apparently it takes a while to transfer 700 gigs with a usb cord XD

on page 1 I posted a photo of usb headers left-to-re marked 3 2 1; by happenstance, MIO wears a tag that reads USB_3 so we tend to push it into USB3 header. For troubleshooting, we're free to push it into any of those USB headers - for instance - push it into USB2 in order that device manager 'see' it on bootup & 'reinstall driver'.

 USB3 header & USB_3 cable have been call-outs which reference the MIO board; minor testing involved USB2 & USB1 - headers & cables - both of which support the top external USB2.0 ports, where simple test might be: insert thumbdrive, keyboard or mouse into top external port in order to verify headers are 'working'.

If you've pushed USB_3 into USB3 header, performed 32bit & it says there is an over-current situation (this is the only relevant scenario), I might disconnect the Media Card Reader & Bluetooth Radio & retest; if over-current, you may at your discretion unplug everything, save for, again:

• 24p black + VGA sense + MIO 10pin power & MB_1 (aka the other end of USB_3)

if over-current with minimal amount of connexions, we probably await clean 7 install & test old MIO - if it fails - introduction of new 604GC into system: new 604GC tested against 32bit & clean 7 install. This would be my approach when asked to talk outloud. No clue about speakers.

Any unresolved doubts should be cleared up b4 you install 7 or 10 ... so this doesn't go awry as we inch along in 10 more back & forths.

I would disconnect all USB headers from motherboard and test with Dell-Diags. If it passes finally, MB might be ok. Proceed to connect each USB cable one-at-a-time (including front panel, MIO-Board, etc.) to see which "USB device" it causing problem (over-amping the header).

After doing this, I have found that it was this device causing the problem:

I switched which header it was plugged into and got the same overcurrent error but on a different controller in dell diags, meaning this is the offending part.  What does it mean then that this USB3 is causing the overcurrent? What is USB3 connected to?

If you've pushed USB_3 into USB3 header, performed 32bit & it says there is an over-current situation (this is the only relevant scenario), I might disconnect the Media Card Reader & Bluetooth Radio & retest; if over-current, you may at your discretion unplug everything, save for, again: 24p black + VGA sense + MIO 10pin power & MB_1 (aka the other end of USB_3)

Apologies, I was a tad confused by this, because isn't the media card reader plugged into the MIO board?  I got that the gist of it was clean install and report back, however I'm awaiting the flash drive atm, and making sure I'm all backed up correctly.

In the back of computer (directly from motherboard), the green 1/8inch jack for analog speakers, connect a pair of common analog stereo headphones or ear-buds.   Not from a phone. Not with a integrated mic. Should only have 3 metal contact-bands on plug.

done.  I only get sound out of one earphone while plugged into the green jack on the back of the machine.  Thoughts?

I have sound coming from only one speaker.

First, check the Balance control if you have one.

Second, unplug and disconnect all speaker systems.

In the back of computer (directly from motherboard), the green 1/8inch jack for analog speakers, connect a pair of common analog stereo headphones or ear-buds.

Not from a phone. Not with a integrated mic. Should only have 3 metal contact-bands on plug.

... what happens?

Agh. Again, the master i/o is basically a usb device so it needs a usb cable to work; each end of that cable has a 'tag' on it; the end that plugs into mio is tagged MB_1 & the end that plugs into mthrbrd is tagged USB_3:

• the top external USB2.0 ports are named USB_2 & USB_1
• shipped from the factory, USB_3 cable is pushed into USB3 header
• in the end, what matters is that USB_3 cable is plugged in, not 'where'
• for clarity & ID we want it plugged into USB3 header

Our design was to unplug USB_2 & USB_1 cables, & test USB_3 cable (test mio) in all three headers (USB3 USB2 USB1):

• if mio causes over-current status in 32bit test across USB3, USB2 &/or USB1, we've pinned down 'the offending part'

Over-current or over-amps, 'amperage' refers to electrical current or the amount of 'draw' or 'pull'. Low amps is a low 'draw' of electricity, high-amps is a high 'draw' of electricity. Over-current will be 'over-draw'. If the test says the mio (& we know it is the mio now) is drawing too much current (too much power) from the or a USB header, my suggestion was to start unplugging those items from mio, in hopes to 'reduce the amount of current' it is trying to 'draw':

• unplug media card reader & bluetooth
• they want power, want to draw current, unplug them
• also unplug the 1.5 amp pci fan & .5amp hard drive fans

to 'remove' a full 2amps of current draw through mio. right?

Why? If there is a 'short to ground' or 'short to 12v' anywhere in your wiring or related devices (which are plugged into mio) then simply unplugging items may alleviate this so-called over-current status.
Since mio runs the fans, vents, case lights, media card, bluetooth et al, unplugging as many things as you can might allow mio to pass the 32bit test ... in fact it might restore normal behavior (Tower appears in AlieFx, the final issue to solve). Either unplugging 'everything' will or won't help a pass in 32bit, will or won't 'restore normality'. The idea is to unplug it all & also boot into the system to see what happens, even reinstall/repair CmndCntr & restart to see if it helped.

The reason we leave the 24pin black & VGA Sense connected is due to the liquid cooler & radiator fan which depend on mio to 'relay' power to them; & we can't test our systems without the cpu cooler (not for long anyway, only about 2minutes or less before overheating cpu occurs).

Does that answer it?

Nobody I know of wants to blame the motherboard, yet. The fact the over-current followed the mio to a different header (from usb3 to I assume USB2 or USB1) seems a good sign; now the qwestion is 'what' item plugged into mio is causing an over-current: is it the pci fan / hard drive fan, media card, Bluetooth, lights ... all of the above? Would new 604GC produce a different result? Is old mio toast? We'll wait & see. In this post (not that you need to read it), but it took forever for the guy to do what I said from the start: make sure all connexions are verified against the Landmark pic; in the end he had his MB_1 plugged into wrong media card port on mio. *shrug* I advised him to unplug everything, start with the bear neccesities & one by one test system to isolate over-current situation. Live & learn.

Alienware Area 51 ALX - USB Overcharge when connecting MIO board to new ASUS motherboard

'New Asus Motherboard' may grab your attention so I hear:

- Blanche Neige -

Area-51 Groom Lake Edition

- the Moon Child -

Part1Part2

SUCCESS!!!  I finally did what you told me to do in your third or fourth post.  Unplugged everything from the MIO save for the 4 cords, tested in dell diags and it passed.  No over current.  Reconnected one or two cords at a time and retested.  I still do not have blue tooth or media card reader connected but I booted up, logged onto my desktop and the fins started moving and the color scheme changed!!  Opened CC and all of my thermals are present and I have control over case lighting again!! Thank you thank you thank you thank you!  The reason I was so hesitant to perform this step was because I was intimidated.  Even with that beautiful graphic you provided, there's a lot of tiny cords, and a lot of tiny connections.  I'm getting better with computers but I was very nervous to go yanking stuff out.

However, it is close to perfect but not quite.  In CC, when I click on active venting, I get a huge error message and CC closes/crashes.  Here's a screen shot.

The vents are up which is what I wanted, but I'm not sure how to proceed with this....

SUCCESS!!! ...  No over current. logged onto my desktop and the fins started moving and the color scheme changed!!  Opened CC and all of my thermals are present and I have control over case lighting again!!   Thank you thank you thank you thank you!

Good work. You are making progress. Sounds like you are about 85% finished.

What version of Windows and what version of AW-CC are you running?

I suggest you do a "clean-install" of proper AWCC version (based on your OS) ... with Reboots and some Power-Dissipations when machine is Off/Shut-Down.

Live & Learn. *poke*

There's the 'no instance of an object' error I've seen before; my systems work, therefore I've seen the error but can only reproduce that when the mio usb cable is unplugged, which happened about 3months ago. I can't promise you a fix on this error, other than it exists inside this post already somewhere (you have to unravel the mystery), since we've thrown the kitchen sink on top of (your) la cabeza; everything that can be done to solve error is already posted.

#1) the driver: is it in device manager or not

#2) AlienFxTester.exe has to detect board; if it does, we'd want a clean reinstall of CC as Tesla says:

• "Uninstall the Alienware Command Center from your system
• Uninstall the .NET Framework 3.5, 4.0 and 4.5
• Restart the computer. Install the .NET Framework 3.5 and 4.5
• Download the latest Alienware Command Center from our website and install it

If issue persists please go to "Control Panel", "Programs and Features" and choose uninstall Command Center, when setup loads, run the "Repair" option. This will solve any software corruption in the AlienFX firmware while installing"

* If this doesn't work, please uninstall and reinstall Command Center again. This might take several times to uninstall and reinstall before it starts working correctly

* Hossmcd wrote - It reported that a firmware update had not gone to completion when a previous tech had uninstalled the old Command Center and installed the latest one. After uninstalling and reinstalling the Command Center again my situation appears to be back to normal. The Command Center now communicates with the MAIN I/O board. The fans, lights, and venting work as designed.

I posted the language in the guidelines above to highlight mio firmware & .net software concerns.

#3) Tesla is not a fan of running 2.8.11 on W7; I have no issue with it. What I do know is the MIO Filter Driver materializes in device manager using 2.8.11 (you saw my snips) but can not 'member if it does so on 2.8.9. I feel it'd be ok to apply 2.8.11, sniff around some & revert back to 2.8.9 & vice versa, using whichever version produces the fix you need. Also note 2.8.9 can be tried 1st on your clean 7. Hopefully any changes you're making now were done on a clone. Since a clean 7 install is on your plate soon, I suggest sticking with that old mio & save new 604GC for last; for mio wiring & rewiring you need a powerful small led flashlight (removal of pci shroud battery shroud & pci fan can help open up things down there).

To correctly reinstall Command Center on your Area-51 or Aurora systems, please follow these steps:

1. Uninstall Command Center from the Control Panel > Programs and Features.

2. Open My Computer, click Folder and Search Options, choose the View Tab and enable Show hidden files and folders. Click OK.

3. Go to C:/Program Data/Alienware/Command Center/Thermal Controls and delete the Profile.xml file.

4. Go to C:/Users/ /AppData/Local/Alienware/Alienware AlienFX/Themes and delete all *.ath files.

5. Verify that the device manager doesn't have any unknown devices under Universial Serial Bus Controllers. If there are unknown devices see the note below.

6. Restart the computer.

• Download & Run CCleaner registry cleaner to remove left over keys from the old Command Center uninstall

7. Download the latest version of Command Center available and run it.

8. Complete the Alien Command Center installation by answer Yes to all dialogue pop-ups. During the installation process, the Master I/O board firmware will be updated. Do not shut down the computer at this time. If the firmware update process fails, please contact Alienware for support.

9. Restart the computer.

10. Verify that there are no Unknown devices under Universal serial Bus Controllers. If there are unknown devices see the note below.

11. Launch AlienCommand Center.

Note: If there are unknown devices on the device manager, or no device is detected please do the following:

a. Verify the Master I/O board USB cable is properly connected to the motherboard and to the Master I/O board.

b. Drain the MB power for 1 minute.

edit @KJ

there's no time in my life for mthrbrd swap hand-holding (I'm s'posed to be retired); search the forum for past swap success stories, the answers are there waiting to be uncovered / unraveled.

I see you're up & running after a long long drought: good job, tread lightly, & you're welcome

To rule out all software corruption concerns, a clean 7 install would be performed in order to test MIO & CmndCntr. Testing would ensue, then Win-updating that new 7 install is a secondary concern performed later. At least here it is. Copy/pasted tip below.

"When we clean install 7 SP1 & do the 1st update check, these days there are 200+ that await (see note). It has always been the advice to only install Security Updates 1st in one fell swoop & leave all other update choices behind for the next go 'round.

*note: it is advised to download & apply these two stand-alone updates 1st before doing your 1st online update check; these two updates may dramatically improve the time it takes for checking/downloading your 1st batch of updates:

• 3102810 & 3083710
• Sticking with Windows 7? The forecast calls for pain "