I'm putting a MIA midi card into a brand new Asus A8V mobo with AMD 64 3400 with 512 mb pc3200 ram. System works fine. Win2k sp4
I'm getting instant lock up as soon as I try to use the audio card.
-No messages in event viewer
-On-board audio is disabled
-Latest drivers downloaded and installed
-Works fine with onboard audio before and after
-Card put into different computer with no problem
-Echo says these are compatible
-device manager says it's working properly - no conflicts
WHAT AM I MISSING?????
Want to enjoy fewer advertisements and more features? Click here to become a Hardware Analysis registered user.
I'm having a problem with the A8V-Deluxe Rev 2 and MIA as well. In my case I'm using WinXP Pro SP1a. As soon as the MIA driver is loaded and accessed, I get a BSOD: MACHINE_CHECK_EXCEPTION. The address is 0x0000009C, which looks like the PCI-IDE Bridge.
I've tried everything, pretty much. This is a clean install with no apps loaded, and all on-board peripherals turned off. I've tried three different video cards (ATI Radeon 9200 SE, ATI Radeon 9000, nVidia 400). I've tried BIOS versions 1007, 1008 and 1009 beta. I've tried MIA drivers 6.08 and 6.11 beta. I've tried it with the on-board audio off and on. The furthest I get is with on-boad audio enabled, MIA driver disabled. I then do a fresh boot, and enable the MIA driver. I can play audio through the on-board. If I open the MIA console or try to route audio through the MIA, BSOD: MACHINE_CHECK_EXCEPTION, 0x0000009C.
I'm hoping that this is just a bum board. I have also had the ocassional boot problem. Sometimes the BIOS fails to post, saying that there is an overclocking error - even though I set the overclocking screen to "standard". It also fails to recognize my keyboard sometimes. These errors occur randomly on boot - even with the MIA unplugged from the PCI bus.
So, how did you learn that this motherboard is supported by Echo? Did they claim to have tested with the A8V? My processor is the 90um version. It's a 3000+. Maybe they tested with the older chips.
I've got a call in to Asus. I'll see about getting a replacement board. The MIA ran perfectly in my A7V8X Deluxe.
Let me know if you find anything. I'll do the same...
Wow! I got that overclocking failed error too! I just hit F10 in bios without changing anything and it booted up. That doesn't sound like it's connected to the mia board, though. Let me know what Asus says. I put my mia board back into the old system, and it worked fine, so this seems like a compatibility issue with asus.
Well, just to make sure, I tried another hard drive. It's a fairly new SATA, and has been flawless. It has XP on it already, but it wouldn't boot. Probably because it lacked the SATA driver for this MB. I went through all the steps, everything went perfectly. I installed the Echo MIA, loaded the driver, tried to play music through it, and boom, crash, BSOD. Same MACHINE_CHECK_EXCEPTION. Same address (0x0000009C).
Either this board is bad or I bought the one motherboard on the planet that is incompatible with the Echo MIA.
Unfortunately, Asus support in the US has been pathetic. I've used their website and their phone number. They promised to call me back, but never did. That was two days ago. The only e-mails I've received have been auto-gens. I've always liked Asus, but this experience is souring things quickly.
I got a reply from Asus. Here's the technical part:
This problem only apper when you install MIA driver? And Machine check exceptions are frequently caused by one of the following conditions:
#1.Noisy power, overstressed power strips, outmatched power supplies and failing power supplies can destabilize your computer. Make sure that you have a stable, reliable power supply to your computer.
[I've got a brand new Seasonic 400W supply. According to AsusProbe, it's in spec. -JF]
#2,Extreme thermal conditions caused by the failure of cooling devices such as fans may damage your computer. Make sure that your cooling devices are all working.
[Thermalright XP-120 w/ Vantec Stealth fan. CPU around 100F/38C]
#3 ,You have damaged memory or memory that is not the correct type for your computer. If you recently changed the memory configuration, revert to the previous configuration to determine what is wrong. Make sure that yo! u are using the correct memory for your computer
[I have OCZ PC3200 Rev2 Platinum 2-2-2-5 RAM. I tried many conservative settings, as well as AUTO and some very low-latency setting. I always get the same failure.]
If still not , please contact your dealer whom you bought motherboard from for RMA service. If it is impossible, please contact :
> "Your right, because 0x0000 errors are memory errors"
Not necessarily. It could be an I/O address.
I had been testing with OCZ PC3200 RAM. I tried the system with my Samsung PC3200 RAM (which had been working perfectly in my A7V8X system), and I got the same exact error.
Opening the device manager and setting the View to "Resources by Type", I can see that 0x00000090 - 0x0000009F is "Motherboard Resources". Opening the properties of this it is shown to be a system device on the PCI-ISA Bridge. This bridge is critical for audio devices, since WDM drivers must behave in the newer 32-bit (PCI) realm as well as the legacy 16-bit (ISA) realm.
Furthermore, if I expand the memory branch of the "Resources by Type" view, it shows addresses 0x00000000 to 0x0009FFFF to be owned by the System Board.
I am viewing these values with the Echo MIA board removed from the system.
In the end I've tried multiple video cards, RAM and hard drives. In each case the error is 100% repeatable. Either it's a bad board, or the MIA and A8V are incompatible. I sure hope it's the former. I'll know the answer in a week or so...
I replaced the motherboard. It's been rock solid. But the Echo MIA still doesn't work on it.
I then bought an M-Audio Audiophile 192. It works, but not with the legacy drivers - only the ASIO and GSIF stuff works. That means that my pro apps like Sonar and Vegas are fine, but I can't run Media Player, WinAmp or other consumer stuff.
It seems that VIA has found a way to screw up the audio side again. I thought that they were long over that.
Last week I got my lean mean 3500+ Amd machine with the asus Av8 deluxe mainboard , and was hoping to set up my layla24 audio card and see what kind of monster I`d created and .....Geuss what ?!?
Same problem here !!!
Macine_check_exeption with the 0x000009 being the cause( strange thing is that it only happens when I turn on the power to the break-out box)
Ok...stay calm.....this will be fixed soon....flash everything....update every thing....but.......
Nothing works !!
Thankfully I found this post so I know that more people have encountered this problem and I don`t have to worry about the state of my Layla24 card.
I have mailed my grieves to Echo and hope to hear from them soon(????)
Has anybody found a solution for this problem yet.....?
I gave up. We need the mia board working for shows, so I moved it to another AMD with an xfx board and it's working fine. I feel sure this is a compatibitlity issue between echo and asus. Echo said they had tested the same setup with an A8V, but I don't believe them.
I spoke with Echo back in early December. The technician was very nice and knowledgable.
He told me that they had tested with all of the *chipsets*, and that they had tested with the K8T800-Pro, but he didn't say that they had tested with all of the mobos. Also, Asus applied some tricks to speed up Rev 2 that may have broken something.
It sounds like Echo needs to get an A8V-Deluxe ASAP.
The technician also said that they had a great relationship with AMD, and that AMD has all of their hardware and drivers. Maybe AMD can become the honest broker between Asus and Echo. It's hard to say which company is at fault.
My money says that Asus screwed up. I bought an M-Audio Audiophile 192. The GSIF and ASIO drivers installed fine, but my MIDI and legacy audio drivers did not. I'm familiar with a Windows Registry problem that probably caused the MIDI install problem, but the legacy problem seems too close to what I'm seeing with Echo. Fortunately, the GSIF and ASIO solves 95% of my problems.
Hopefully we'll get a new driver of BIOS soon that will fix this.