Help get this topic noticed by sharing it on Twitter, Facebook, or email.

M-Track 2x2 Kernel Mode Trap

Hello there.
I bought an M-Track 2x2 a couple of days ago. I keep getting random blue screen system crashing reporting "kernel mode trap".
I use Windows 10 and the latest m-track 2x2 drivers (1.0.12)
This happened three times over 2 days I've been using it.
I've seen other people reporting the very same issue but could find any solution.
Is there any possible fix to this problem?

Thank you in advance.
1 person has
this problem
+1
Reply
  • Eliza (Official Rep) August 05, 2019 15:36
    Hey n0l4n666,

    Thanks for posting!

    Sorry to hear that! Blue Screen crash reports do often reference drivers. The BSOD may even mention the M-Track driver specifically but the M-Track interface cannot directly cause a BSOD. While it may be the catalyst for a low-level software malfunction, the M-Audio hardware is not the direct cause of the BSOD.

    Blue Screen crashes are generally caused by a hardware or a hardware configuration problem on a PC (like an IRQ conflict, or BIOS setting). This generally is not caused by a particular driver. In this case, the USB ports, or card on the PC may have an issue, or other I/O hardware on the PC may be misconfigured preventing the addition of a new device.

    The following knowledge base article courtesy of AVID addresses IRQ Conflicts.

    AVID Knowledge Base - Pops, clicks, crackles, dropouts, or distortion

    Very rarely, this could be caused by defective M-Track hardware. To confirm whether the fault is the M-Track, or with the computer, try the device on another computer. If it functions, you can confirm the problem lies with the computer. You may also benefit from removing any old driver for M-Track hardware that may be on your computer.

    If all of the above can be ruled out, the M-Track may require service. If that is the case, warranty and non-warranty claims cannot be handled here on the forum but I can point you in the right direction! Here are a couple of options that you could choose from:

    • Submit a Warranty or Service Inquiry with our Technical Support team by logging onto the M-Audio Support Page. Select Warranty or Service Inquiry from the drop down menu. This will not require a support code.

    or

    • For faster support, call or email your nearest Support Office or International Distributor. Select your country to find the nearest office.

    Make sure to reference or link to this thread to help out the support team.
  • (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

  • Here's an update: I uninstalled the drivers and I had not a single BSOD since, it's been two days. The product works nonetheless both as an input and as an audio device, so I'm good enough for now.
    I'd say it's not a case of defective hardware, rather the driver itself causing some kind of conflict, possibly with other ASIO drivers I'm using.
  • (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 2019-08-14.
    see the change log