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
9 people have
this problem
+1
Reply
  • Hi Alex,

    Thanks for posting.

    You'll want to start by making sure that you in fact have the correct driver for the M-Track 2x2, not the 2x2M, or vice versa. Please uninstall all of your M-Track drivers and use the guide below to ensure that you download/install the correct driver:

    Finding the Right Driver for Your M-Track

    A BSOD is almost always caused by an internal hardware malfunction or other issues within the PC or OS, not the M-Track or drivers. This is very often prevalent with custom built PC's and less often in store-bought computers, though it does happen from time to time. In order to properly troubleshoot or identify the problem, please use the article below and/or contact your computer's manufacturer:

    https://support.microsoft.com/en-us/k...

    http://www.howtogeek.com/163452/every...

    I hope this helps! Let me know if you have any additional questions.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m frustrated by M-Audio's handling of this
    I have of course checked those things and unloaded and reloaded the correct drivers several times Alex. (NB Mine is an M-Track Eight, not a 2x2, but I understand 2x2 users see the same problem).

    Perhaps if you would like to avoid any doubt you could send a link to the specific driver for an M-Audio M-Track Eight running on Windows 10 Pro 64-bit, just in case there is something wrong with the drivers being selected on the "Finding the right drivers" page.

    I am aware that many BSODs are caused faulty hardware, but in my decades of experience with PCs I would say that misbehaving drivers do in fact account for a high proportion of them, and for the particular error being thrown up in these cases it is almost always down to a driver bug, either a straightforward coding error, or the driver writer failing to account for all circumstances that can commonly arise.

    See https://msdn.microsoft.com/en-us/libr... for more information.

    The MS support link you sent does not appear relevant at all to the current problem - it's for an entirely different class of BSOD. The howtogeek article is only about BSODs in general, not the specific one being thrown up in the M-Audio driver, but even that generalist article states: "Blue screens are generally caused by problems with your computer’s hardware or issues with its hardware driver software." Note the latter point.

    I am using modern standard 'shop-bought' hardware, Intel i5-4430 based, that has not been modified in any way, and gives absolutely no trouble with a wide range of other audio software and hardware. Without the M-Audio drivers installed it can typically run for weeks without a reboot or crash, but as soon as the M-Audio drivers are installed it becomes unreliable.

    The system crashes are not the only problem. When the M-Audio drivers are in use, audio applications are prone to simply stopping producing audio output - they will run for a few seconds visually looking fine, but with no sound being produced, and then stop altogether after maybe 3 secs (perhaps once a buffer is full?).

    What again points to the drivers more than anything is that this stop after a few seconds with failure to produce output happens identically in a range of reputable audio apps such as Adobe Audition, WinAmp and VLC Player, none of which gives the slightest trouble when used with the system's integrated sound or plugged in Behringer USB hardware.

    You'll understand I hope why I feel everything points to inherent problems in the M-Audio drivers, and I am frustrated by M-Audio's persistent attempts to pass the buck to computer manufacturers in the face of dozens of reports of similar problems.

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

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

  • Hi Alex,

    While I still recommend connecting with our support team (as well as a Windows support team) and I'd like to direct your topic back to this thread, considering the other thread is an entirely different problem.

    The drivers in the article above are totally accurate and simply link to the drivers & updates page. For some users, it's difficult to decipher their M-Track model and grab the correct driver, and this article helps. Alex description was inaccurate. Sorry if that threw you off.

    Thank you for sharing this thread. I certainly understand that there are likely other users pointing this out elsewhere, or even not at all, but the numbers are still very low in comparison to the number of units being sold. I'd even go so far as to say ANY inquiries about the M-Track Eight are rare in comparison to other products. Granted the smaller M-Tracks are far more popular due to their accessibility, but the numbers are still very low.

    Now, the thread you shared is only one user and the other two user's both point to memory as a likely culprit throughout the entire thread. I don't believe that you have posted your system specs yet, but that's important to consider. If you have recently replaced or upgraded RAM in your system, transferred it from one computer to the next, that's important to consider as well.

    The M-Track driver is likely a part of the problem in that it's triggering something else in the system or requesting resources that other applications or devices may not request, though in my experience we have not seen anything that points directly to the driver as the culprit. These drivers are tested and stress-tested in the field, not just "in a laboratory." I myself use an M-Track Eight everyday in the office, Windows 7, and often take it home to use with a Windows 10 system and a Mac Yosemite system with no problems.

    But that being said, especially with Windows, it is impossible to consider every possible combination of hardware components or other software and drivers that may be running in a user's system and there may be some cases where the driver highlights some discrepancies between components. Thus, there are some situation where we cannot guarantee the driver will run properly. Most users that are building their own systems or replacing components typically understand this and know what to look for in these circumstances, though there are of course a few that will inquire about assistance here.

    Finally, I'd like to point out that older drivers, like those for older M-Audio products no longer in use and especially older AVID interfaces, can sometimes cause conflicts. I noticed that you also have an M-Track Quad tagged in this thread. If you have any M-Track Quad drivers installed, try uninstalling them and any unused product drivers and reinstalling the M-Track Eight drivers. This may help.

    I hope this helps clarify a bit and I hope you can get in touch with a support representative to discuss the situation more closely.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m frustrated
    My M-Track 2x2 crashes with BSOD all the time as long as M-Track is connected - even if no DAW is running. I have a generic laptop. It is clearly a driver problem - I am not sure how manufacturer cannot admit it - it cannot be anything else... Simply frustrating.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m frustrated
    I too am having BSOD problems since connecting an M-Track Quad to my Windows 7 PC. I can go back to my old 2 channel Line6 box and use it for days without a problem. When the M-Track is connected, BSODs pop-up whenever they feel like it. There is no rhyme or reason to them whatsoever - I can be using a DAW at the time, or not using one.

    I have drivers 2.9.55 installed.

    Not sure what else to do at this point except take it back and exchange it for something else.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Where is the damn fix??? Having BSODs too, because of your card! m-track MKII. Yes, i have proper drivers. WTF???
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • same her every day a crash on windows 10 BSOD just a Thought update your driver M-AUDIO
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Where is the fix god damn it? just now, bsod is ruined my rendering process, which is going about 4 hours, and was about to end!! Hey, M-Audio, where s the answers? it was a wery expensive to me to buy this card, why cant it work properly???
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Reinstalling helps untill a new upgrade from MS BTW but not an realy good solution !
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • They will not address the issue. They keep saying it is a problem with the customer's hardware, then tell you to submit a warranty/service inquiry. Used multiple computers, USB ports, clean Windows installs, all moot. They need to talk to whoever poorly writes their drivers to completely redo everything.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • This reply was removed on 2017-03-07.
    see the change log
  • I’m extremely frustrated
    I have tried e-mailing about this issue for weeks now and I feel like I am just being ignored after it was forwarded to a technical department.

    This is really terrible support. JUST FIX THE DRIVERS PROPERLY!!!

    Look at all these people having problems! Black screens of death are just not acceptable, they are clearly being caused by the M-Audio driver. I am terribly disappointed in this company.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hmm, I am not sure if the solution to this problem is really in maudio's hands. This kind of blue screen occurs with other controllers too. I had the same issues with novation's launchpad on Win10 64-bit. I tried several setups with/out usb-hub, usb 2.0/3.0. They were all prone to this bug. While it does seem to occur a bit random, there seem to be actions which make it more likely to happen, like unplugging the controller or causing the usb-controller to reinit stuff.

    Just out of curiosity: do you guys have multiple m-audio usb devices attached?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

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

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

  • [Just out of curiosity: do you guys have multiple m-audio usb devices attached?]

    No - it was a pretty clean Windows 10 installation with no other audio hardware when I installed the M-Track 8. A clean installation of the M-Audio drivers caused the crashes and removal of it stopped the crashes.

    The crashes were with the machine in normal everyday use, not when plugging or unplugging anything. I did notice that more than once they occurred when a player switched from playing a wav file to playing an MP3 file, but at other times the machine crashed with no apparent immediate cause, but the BSOD identified the crash as coming from an 'out of bounds' memory reference in the M-Audio drivers.

    Removing the M-Audio drivers restored complete stability - for example with 16-channel in 16-channel out drivers for another manufacturer's interface now on board, plus another simple 2x2 USB audio interface, the machine has been running 24x7 for several weeks with no crash - in fact I can't remember the last time it crashed since removing the M-Audio drivers somemonths ago.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hi Corey

    "I certainly understand that there are likely other users pointing this out elsewhere, or even not at all, but the numbers are still very low in comparison to the number of units being sold. I'd even go so far as to say ANY inquiries about the M-Track Eight are rare in comparison to other products"

    I started having this issue after upgrading from windows 8.1 to windows 10.
    Do a google search : "M-audio DRIVER_IRQL_NOT_LESS_OR_EQUAL " then
    " m-audio blue screen of death"
    and see for yourself how many people have this problem. Many of your customers are not technically inclined and don't know how to solve or inquire about a issue like this. Some will even throw your equipment and not bother using it. Some will have the BSOD crashes once in a while(like me) and live with it.
    By looking at the date of my driver 1/15/2015 and considering that this was the first and only driver ever made it is not that difficult to evaluate the funds m-audio is spending on support. You can't tell us that your driver/software engineering team is so advanced that they can make drivers that are future proof. No other company can achieve this! For example my canon camera get's a new firmware every 5-6 months and it's continuing to get updates for 4 years now. My 5 years old wireless router gets firmware updates every ~3 months. Every other pc component gets updates for fixes i'm not even aware exist and for a user it is important and pleasant to have this kind of service, a practice m-audio surely doesn't see as valuable.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • After doing some research, there are a few things that could cause this issue.
    motherboard audio driver conflict
    gpu audio conflict
    USB port , (using usb 3.0 for device instead of usb 2.0)
    other motherboard controller/drivers?

    Seems that m-audio competitors (focusrite, maybe others too...) are getting the driver irql bsod as well.
    someone said that disabling the USB selective suspend option control helped solve the issue:
    control panel /system&security/ power options/ change plan settings/ change advanced power settings/ usb settings/ USB selective suspend setting - disable

    http://www.tomshardware.com/answers/i...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Just because other OEMs may have similar issues does not give M-Audio a free pass. I've switched to a Tascam unit of the same price bracket and there's been no problems, because they actually provide both firmware and driver updates for their products.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m pissed
    Disabling the USB selective suspend option control did not work, still got a BSOD afterwards. Still no reply from M-audio support either, after a whole month of waiting. It's freaking ridiculous. How hard is it to update these drivers.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • My Windows corrupted because of these crashes and you say that there is nothing to do with the interface driver? I do not want any more support, I'm going to sell this card and I never buy M-Audio anymore, besides they do not give me a direct answer, they transfer me to a random post thinking everything will be fine, I lost all my work files and what I get is A redirect on your forum, but that's it, thanks for nothing. =)
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m peeved
    Disappointed to come here in hope of an answer only to find an unresponsive support team and a bunch of angry customers.

    If the problem is the drive, then yet M-audio should be tracking the bug and coding a fix.

    So either A its the driver and they are incapable of fixing it and need to hire new coders, or B the problem is with the OS and should be addressed by windows directly. Just an update would be good.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

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

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

  • Same problem after win 10 64bit clean install
    Works Fine on win 7 64 bit
    DRIVER_IRQL_NOT_LESS_OR_EQUAL MAudioMTrack.sys
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m amused
    I love how everyone comments that they have the same issue, but in the original post only 6 people gave a +1 saying they had the same issue. It makes the post more visible if you click that button.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I'm still having the exact same issue as OP with my M-Track Plus II and have raised it before.

    The BSOD's that everyone is reporting CLEARLY links back to the MAudioMTrack.sys driver. This is NOT an isolated problem to individuals unique hardware or software configuration, it is widespread.

    Pull your finger out and fix your drivers M-Audio! I will never again be buying an M-Audio product after the absolutely shameful and woefully dismissive tech support on offer.

    Secondly, I will also be actively telling others on numerous popular audio forums to stay away from M-Audio products and will be archiving and pointing them to these threads as proof of your ineptitude. Congratulations.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hello,

    I have the same kind of issue on my Win 7 (card 2x2M), but without the BSOD, sometime, the computer is completely freezing, when it is, i unplug the card, and the PC is instantly back to normal.
    Unfortuntaley, when it's freeing in the DAW, i have to restart it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Same here on the creators update windows 10 freezes of the computer for 20-60 sec !
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • 1
    No need to be nice. I've owned the CrashTrack Pro for years, and it's been a piece of shit through 3 different computers, and 3 different operating systems. It worked best on Windows XP, but still sucked back then. It's a total nightmare in Windows 10. I'll be sure to share this far and wide on music forums.


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

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

  • Ps if an Freeze happens if I pull out any usb device out the freeze stops !
  • (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