I’m frustrated

When will this be fixed M-Audio driver crashes Windows BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL

I know there is another thread on this but it has been closed for comments with no resolution of a serious problem that still exists.

Despite all the finger pointing by M-Audio at any other possible cause of a BSOD, it is absolutely apparent that many people have exactly the same problem as I do on multiple computers. That is, with no M-Audio driver present the computer runs audio applications glitch free for weeks with no restarts; then install the M-Audio driver and it crashes during audio operations, maybe once in three days, sometimes three or more times in a day.Or it doesn't totally crash but just refuses to record or replay audio.

I bought this gear for a local broadcast radio station as supposedly top quality equipment from a reputable maker, and it is distressing to have the station silenced or disrupted repeatedly in a way that never happened when we used 'cheapo' Behringer interfaces that require no drivers.

If the drivers cannot be installed and work reliably on a majority of real systems 'in the wild', then they are not fit for purpose. It is not acceptable for them to be reliable only under laboratory conditions with a pristine installation of nothing else.

It's long overdue for M-Audio to get some capable software driver engineers and on the case and find out why their drivers are trying to reference paged out code or other invalid addresses under common circumstances across a wide range of different systems.

If this can't be achieved, then the gear is simply not ready for the professional market, and M-Audio should bow out with a full recall and refund to disatisfied purchasers.

Alex
49 people have
this problem
+1
This topic is no longer open for comments or replies.
next » « previous
  • I’m sad
    I have this problem on my M-Audio 2x2 as well. Originally on my old Firewire 410 I had the exact same problem. I'll try to describe some of the symptoms I've faced with both audio interfaces.

    1) After a period of time being connected, the audio drivers will crap out. This means youtube videos will be continuously spinning, and other programs be playing without sound. Unplugging and replugging both devices in forces the drivers to reinit and they go back to work.

    2) After a few instances of 1) I will get the BSOD. It happens randomly but usually when audio is playing (I think). Same IRQL problem.

    3) This has happened from Windows7 to 8 to 10.

    4) The reason why I gave up on my Firewire 410 is because of 2 reasons: A) M-Audio never decided to rebuild their drivers for newer OSX compatibility. Usually just involves opening the project with latest xcode and republishing for the new OS. B) I started getting audio crackles on the output bus. Even when muting other channels/bus it would still crackle. I didn't bother cracking open the machine to debug it.
    • I have had this issue as well with both maudio usb and the mtrack 2x2 c series where i have to unplug and plug back in to restore audio on cubase, youtube, whatnot all the way from win7 to win10 doesn't matter i've accepted it as reality. BSOD is definitely common, I'm seeing every 2 days or so and while it might not be something that m audio is doing wrong, it is definitely an issue for me. Many lost ideas over the years due to not saving before a BSOD. Either windows or maudio needs to patch something because im always getting the same error message something like "m-track 2x2 driver irql blah blah invalid" Next time it happens today ill post the actual message...came here for help and instead found an employee trying to dismiss what looks to be a common problem. Common enough for 2 separate units ive gotten years apart which were different models and 3 different computers to replicate it. Honestly might be windows though idk
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly

  • We have an M-Track Eight USB connected to a Dell Power Edge R310 running Windows 7-64 SP1 Professional w/ 4 GB RAM and the (only) version 1.0.11 of the driver.. We are experiencing the BSOD restart every few days. The most recent 4 instances happened this morning Nov 10th, Nov 1st, Oct 27th, Oct 22nd. Please see the attached image for greater detail.

    David
    cfoxdrop@gmail.com

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • 1
    Welcome to our world, David - one in which M-Audio couldn't care less!

    They claim it affects 'very few' users, and that it is usually the fault of the user's system, not their dud driver. It seems that "few users"="who cares" in the M-Audio book of software design.
    • view 1 more comment
    • Well, Nick D claims to take this seriously, and if he looks at the crash report screenshot I posted he'll see that our server class Dell PowerEdge crashes with BSOD every 4 to 10 days. Each crash report points directly to the M-Audio Track Eight driver and clearly states, "This appears to be a typical software driver bug and is not likely to be caused by a hardware problem". I will give Nick and his team an opportunity to respond before I jump to conclusions. My boss however has directed me to swap out the M-Audio Track Eight for an old Motu sitting on the shelf, which I will do early this coming week.
    • This shit issue stays in the field for very long time and ton of people have to experience, but Sir Nick D still blames us for buying and setting up wrong PC. How TF did we know that when we bought it!!! They should print warning on the product: "Not compatible with some PC, some Software, some Users ...".
      p/s: sorry. I am so tired of unpluging and pluging and getting BSOD
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I also keep having those BSODs in Win 10, m-Audio m-track ii. Usually this happens when I have Ableton Live open (not playing) and I'm listening to sth on youtube.
    I didn't get them when I was on Win 7. But now, on Win 10 (x64) they do occur once in a month. The culprit is always MAudioMTrack.sys and the error DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • To shed some more light on the issue. In my scenario with my M-Track 2x2, after every so often, audio drivers would poop out with no BSOD. Unplugging and replugging the type C cable solves this. When it's bugged out, video stream videos would not play until I have reinitialized the audio drivers.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Same thing here. Why everything works after replugging, basically? This is just a joke.

    Regards,
    Tim - research papers writing expert
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • From my past experience using the Firewire 410 as well, it seems like something to do with the ASIO buffer size. If the buffer gets over overloaded (or something malfunctions with the driver), it treats it as a device disconnect. Replugging reestablishes the connection but I'm guessing the BSOD is due to buffer overflow. It happened with the Firewire 410 as well. However I can't even use the 410 anymore because they refused to reexport the drivers to the latest version of Windows and OSX. I ended up moving to the M-Track 2x2. I'm also getting crackling noises on my 410 now with nothing plugged in. Tried cracking it open but could not pinpoint any loose hardware that could be the culprit.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I have the same problem too, starts hissing and crackling, have unplug and plug but still keeps happening!!!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I am now sitting here with no decent audio because my quad just hisses and crackles, M-Audio trash.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

    • view 1 more comment
    • hi everyone, i used to have this same problem with my m audio mkii. i even listed it for sale but just after i listed it for sale, i decided to remove Asio4All and use the mkii bundled asio driver instead and that solved the problem

      the m audio mkii asio driver will work fine with buffer of 96 - 256 samples and you would get low latency depending on your cpu power

      i always wanted to use asio4all drivers because i thought that it is always better to have more samples buffer with low latency rather than less sample buffer with low latency. i thought less sample buffer will overload the cpu

      but that is not always the case. i believe the mkii asio driver is the best suited to the hardware

      also, all the problems related to how many audio sources can be simultaneaously played on your pc went away.

      i could play youtube, spotify and cubase at the same time

      so, yea, if you have asio4all installed, remove it and your good
    • I have never installed asio4all on the machine - it was a clean Windows 10 build with as little as possible added, but still presence the M-Audio drivers caused BSOD crashes regularly. Mine is an M-Track 8.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • Just to save anyone else some pain as a fellow long time sufferer of the infamous bsod, I did the win10 creators update I had been "selected " for in a moment of rare optimism, that maybe issue would be resolved.
    Don't!
    Caused havoc on my system. M-audio control panel bit rate settings were greyed out. Couldnt be recognised by Samplitude proX2 or proX3. Samplitude wouldn't run. Uninstalled reinstalled driver. Would no longer work at 24bit 4100hz studio quality.

    In the end gave up, Fortunately, I was able to roll back to previous Win10 64bit version.
    At least I can run again with the risk of intermittent bsods.
    Btw, I too have noticed a connection with chrome usage and bsods pointing at mAudio driver (little "m" intentional until they fix this crap) when no daw running.

    On a separate point, does anyone know about the windows setting for the Audio card under Speaker properties/advanced setting? Here there is an option for exclusive mode or not. When should this be enabled or not? Thanks for any tips.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Thanks for those warnings. I uninstalled my M-Audio card some time ago as it was just making the system too unreliable.

    I believe the exclusive mode should in theory give slightly better latency, and also makes sure no other devices you have forgotten to mute can generate unexpected sounds (beeps etc). I'm not sure you would see any difference on a modern PC with decent performance.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I’m frustrated
    Nick D,

    so essentially your response to our troubles is "thousands of customers don't have these problems". Did you read the post by Yuno above? Three out of three freshly installed systems that worked flawlessly with their onboard sound experienced BSODs repeatedly when running the M-Audio drivers. I don't know about you, but for me there's very little room for doubts about who's the culprit here. Do you really expect us to believe that your engineers aren't able to reproduce these crashes?

    Here is how I reproduced them four times within 20 minutes: I simply enabled the "Driver Verifier" that comes with Win 10 (Win + R > verifier.exe). ATTENTION all, don't do this unless you know what you're doing, or read for instance the following:
    WhoCrashed help
    Then I played around. Even using the mouse crashed the computer instantly in one case. The result in WhoCrashed shows the following lines (4 times):

    "Deadlock: A lock hierarchy violation has been found. A bug check with this parameter occurs only when the Deadlock Detection option of Driver Verifier is active. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: maudiomtrack2x2.sys (M-Track 2X2 WDM Audio Streaming Driver, M-Audio)."

    I use my PC to make a living and simply cannot afford to lose progress repeatedly. Can you PLEASE fix this.
    • Good work Teuto, sadly though confirming what so many of us have found. Responses here range from from studio users who simply want to get on with their real work through to experienced PC experts called in to try to figure where the crashes are coming from.

      All these lines of inquiry always point back at the M-Audio driver, while M-Audio staffers always point anywhere they can think of, except their own defective driver.
    • Well, I believe the line I set in bold above is new (maybe I'm mistaken and overlooked it in older posts?). Either way, this "lock hierarchy violation" is proof that this is a bug in their driver and that there's no sense in pointing in any other direction.

      Nick D did a good job in explaining how these crashes occur; however, he omitted the part where the programmers prevent that from happening. After reading his post one would have to think that BSODs are unavoidable whenever more than one audio source access the same hardware concurrently. But this isn't the case, of course, and the (software) mechanism to prevent them are those locks.

      These are notoriously hard to code but part of the job for a programmer of kernel mode drivers. I would also think it's far more costly for the company to lose customers and their reputation day in, day out than paying an experienced programmer to fix this, even if he is not done in half a day, so I really don't understand the rationale behind letting this slide for so many months.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly

  • Well done Nick.
    If anyone has twitter account make this sure this issue is put out there. I have tried . Seems to be the only way companies will take notice these days.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I doubt Nick D works there anymore, because despite his claim "we do take this matter seriously and want to work directly with users that are experiencing this behavior consistently", I have yet to receive any response whatsoever to my post from well over a month ago in which I included screen shots of crash reports that directly identified the M-Audio Track Eight driver as the cause.

    I can only conclude that if you have a problem driver, consider your M-Audio device an orphaned product and make future purchase decisions accordingly.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I’m happy
    Well would you credit it. My M-TRACK does NOT work on any of the REAR USB ports, but DOES work on either of the FRONT USB Ports. This is strange, because I tried two other makes on the rear ports and they work fine. Also I used the M-Audio ASIO driver which locks it to 256 samples. I'm guessing so there is no buffer overload. Hope this helps.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I found another solution: dont install M-Audio ASIO driver comes along with them, install ASIO4ALL instead (you have to tweak configurations a bit but it works great). I havent got any problem yet but still have to test more.
    • view 5 more comments
    • I do know this, I had to set the buffer size to ~1.024. Everything below caused a lot of crackle.

      Anyway, it's too late now, I just sent the thing back. I also left a 1-star review on amazon.de and plan do the same on thomann.de (where I bought it). On amazon.de the percentage of reviews with 1 star is now 29%, plus an additional 24% with 2 stars. So much for "virtually nobody has trouble with our products".
    • crackle (white noise) can be caused by many aspects. I have to say M-Track 2x2 is quite good device despite its shit driver. But you did right. They have to realize the power of community. It's unacceptable that the problem stays in the field for years without solution.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • You diehard M-Audio persevering users impress me to no end. Utterly dedicated to contributing to holding M-Audio accountable for her egregious need for self-assessment and quality management of their product development and maintenance programs.

    Here's praying M-Audio will finally rise to the occasion, and even gift us with pertinent, working driver and firmware updates for our still-otherwise-not-broken hardware interfaces and other music and audio production tools, sadly crippled by subpar drivers.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    ok guys. i had this problem for nearly a year. random cut out of sounds, blue screen, crackling audio. i suspected the soundcard must have clashed with another piece of hardware, sharing irq settings etc. Anyway i think i finally figured what it was. I downloaded a Driver Inspector type of program (not sure if i can name the one i downloaded here) and it found so many out of date windows/intel drivers (some it reckoned were for 2006, i have a new PC so unless it was windows loading standard stuff). Well fingers crossed, i havent had a problem since. I played loads of youtube videos while having my DAW running (this would cause cut out of sounds or bluescreen) for past 2 days and still to see an issue. Only thing i can suggest guys is a) update you BIOS to latest firmware b) download a driver inspector that downloads all the drivers for you, theres a trial one out there that lets you do it. Hope this helps guy
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Hey,
    I also open a dedicated thread and answer on another thread about this problem.

    Someone can help please ?

    Problem was present on my previous PC windows10.
    Now i've got a brand new nuc7i5bnh and BSOD still occurs ...

    I activated the driver verifier and igot this at boot in logs :

    MAudioMTrackEight.sys MAudioMTrackEight.sys+1270 fffff80f`b4e90000 fffff80f`b4f13000 0x00083000 0x54af345e 09/01/2015 02:52:30 M-Track Eight WDM Audio Streaming Driver M-Track Eight WDM Audio Streaming Driver 5.10.0.6032 built by: WinDDK M-Audio C:\Windows\system32\drivers\MAudioMTrackEight.sys

    ntoskrnl.exe ntoskrnl.exe+7aa2d3 fffff802`cee94000 fffff802`cf769000 0x008d5000 0x5a4a1659 01/01/2018 12:07:05 Microsoft® Windows® Operating System NT Kernel & System 10.0.16299.192 (WinBuild.160101.0800) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

    K. Rgds,
    J
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • I have the same problem with profire 2626 and windows 8.1. Equal blue screen of
    Felipe Raffaini. The card is unusable.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Windows 10 and getting this BSOD basically every day multiple times a day, been getting them since win 8.1. I hope someone will eventually come up with something
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • this error is by far a major problem and saying that affects a small amount of people is in fact a bigger failure. Windows is the biggest OS in the world, and I bought this poor excuse of audio card (no stereo monitoring) because I trusted this company. Many people has this problem, in USA, Argentina and (like me) Uruguay. So if a 3rd world country like Uruguay has user that are experiencing this problem , let me tell you that you are not fixing the problem because you cant nor want to.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • I’m frustrated
    Bought the M-Track 2x2 in December 2016. Everything was working spectacularly until Windows 10 had a major update in April 2017. Since that update I've been experiencing a couple issues.
    One issue is the M-Track will "freeze", videos(youtube) and audio(TIDAL, files from hard drive, Ozone 7, etc) freeze and completely stop working. Windows reports the M-Track is functioning properly (lol).


    Sometimes disabling the device and re-enabling it will fix this issue but after it happens 1-3 times the computer requires a restart to regain functionality through the M-Track. This happens multiple times a day and will even happen while I'm not touching the computer. (ex. I can't get through a playlist on youtube without this occuring). This issue is quite a nuisance but not as bad as the other issue... the same BSODs everyone is describing here that have cost me hours of irreplaceable studio time.
    I expect Microsoft to update their products regularly and expect the same of M-Audio, being that they are claiming compatibility with Windows. The M-Audio driver dates back to 12/28/2016 which is 4 days after I bought the M-Track. Great! But the version of Windows I had then doesn't exist anymore, making the M-Audio driver compatible with something that doesn't exist for a large percentage of Windows users.
    The official response from M-Audio saying "I am sorry if you are experiencing difficulty but the vast majority of M-Track users do not experience this behavior" is an oversight and is counting out all the people using other operating systems (Mac is common in studios).. and all the people that went and replaced it with a product they can rely on and moved forward with their lives.
    It's not only the people with functioning M-Audio products that aren't participating in the forums, it's MOST people. If I put this interface in a clients studio and they were mid-session and told me they were experiencing this issue.. well first I would be ashamed of myself for using an unreliable product but next I WOULD IMMEDIATELY REPLACE IT WITH SOMETHING THAT WORKS. There's no time to report my issues on the forums in that situation and definitely no time to wait for an update from a company that is going to pass the blame and stand confidently behind their faulty product. Luckily none of my clients have M-Audio products in their studios.
    With all that being said, I'm done waiting for an update. So long M-Audio!
    • view 2 more comments
    • Unfortunately not Mark. Think it is called being stonewalled?
    • Sad when a manufacture doesn't back their product. Ill sure pay more but I'm going back to audio sciences. Solid products and the best support I've ever experienced. No passing the buck, they get everyone involved to troubleshoot an issue right down to the coders
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • 1
    It almost seems like we have enough people on this forum alone to start a class action. If anyone wants to, we can take a list of all the members with the problems and submit it to legals to get them to at least look at this forum thread seriously.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • This reply was removed on 2018-03-05.
    see the change log
  • 2 more of same old blue screens within 15mins just whilst on chrome browser. Hope I can get this posted before it goes again.
    Like-wise, in the UK so cant sadly. I have referred two well known music equipment publications to this issue and threads for what its worth.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • Well I think I'm going to replace mine with another manufacturer as suggested by others here. You win M-audio I give up, but you also lose . You lose any good will or recommendations from me and people I know. Butterfly effect.

    I have made some initial searches for alternative well supported products. What do you guys know of Roland Rubix22 as a viable like for like replacement of my M-track plus mk2?
    It seems they at least take account of drivers for different windows 10 and older, (take note M-audio!!)

    - If you're using Windows 10, version 1703
    -->Driver Compatible with Windows 10 -- Version 1703 and After (Creators Update and After)
    If you're using Windows 10, version 1607
    -->Driver Compatible with Windows 10 -- Version 1607 or Earlier
    If you're using Windows 8.1 / Windows 8 / Windows 7
    -->Driver Compatible with Windows 8.1 / Windows 8 / Windows 7
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • I’m Mad as hell!
    I'm not seeing any real support to solve this issue. It doesn't seem like Avid nor M-Audio even care about this situation so, I'm done with any and all avid and m-audio products. it sucks when companies doesn't even care about their customer's issues they are having while using their products!.
    • FYI Avid is a completely separate company - They sold M-Audio well before the M-Track products were released.

      Joel
    • @ Joel... FYI When I purchased a bundle in which my M-Audio | Fast Track C-600 audio interface... it came with a version of Protools MP9. At that time updates for the M-Audio | Fast Track C-600 audio interface was via M-Audio until they sold out to Avid for that line! So, I don't trust M-Audio any longer for that reason. M-Audio was always on top of their game. Until that! Avid doesn't care because they just wanted the patent for the ideas for the technology. They can careless about what product M-Audio released before they got the patent. That's why they don't support what was a "Top Notch" audio interface created by M-Audio. Now everyone who bought one gets no love anymore (support). Just more $$$ down the drain. Thanks for chiming in with your perspective anyway, Joel.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Maudio 2x2 worked on old pc with win8.1 flawlessly. On a new one with win10 it is a disaster. Sound cutoffs every few hours (as card just dropped from the system as driver falling and than restarts) with need to restart all audio applications. And sometimes BSOD, not very frequent but they are really shows maudio as a failed company. I liked 2x2 but need to switch to another manufacter. The problem is clearly in driver as a BSOD show “maudio2x2.sys stop working”, but what a hell guys? EVERY user of an maudio on win10 suffers from bsods and cutoffs by faulty drivers, and M-AUDIO doesn’t even show to care.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly happy, confident, thankful, excited

  • I’m Angry
    My Mtrack plus mk2 is now being used as a door stop. The roland Rubix24 I bought to replace it works fine so far. Drivers that work with Windows 10, and support.
    Goodbye M-audio.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

  • @ Rajiv Lutchman - All good so far in Samplitude Pro X3
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Hello everyone,

    The latest driver update for the M-Track 2X2 series improves driver stability on most computers. This also includes changes that will prevent some rare causes of BSOD crashes like those reported with some store-bought computers.

    However, please keep in mind that if you have a custom built computer that is not configured correctly (i.e. with IRQ conflicts or that have install issues with the motherboard drivers), BSODs will still be possible with this, or other USB peripheral audio devices.

    The latest drivers for the M-Track 2X2 and M-Track 2X2M can be downloaded from the following links:

    M-Audio M-Track 2X2 Driver (v1.0.10) - Windows

    M-Audio M-Track 2X2M Driver (v1.0.13) - Windows
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned happy, confident, thankful, excited

next » « previous