Motu Ultralite mk3 Hybrib USB. Causing all sorts of issues and BSOD

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Home Premium 64bit
       #1

    Motu Ultralite mk3 Hybrib USB. Causing all sorts of issues and BSOD


    Hi there people.

    I plumped for the Ultralite a couple of months ago, mainly because of it's i/o options/price point. When it works it's just what I need. I was aware of Windows driver issues before buying but as my studio/live laptop is kept reletivly stripped back I thought it was worth a stab.

    However, it's just not playing nicely. Here's a quick run down of my system:
    PC Specialist/Clevo W150HRM
    Intel i7 2670QM @ 2.2GHz
    8GB RAM
    Windows 7 Home Premium 64bit (6.1, Build 7601)
    Motu driver version: 4.0.5.5333
    Running at 96/24

    And a run down of the porblem/s

    The laptop has 2x USB3 and 2x USB2, I always (or used to) have NI's Maschine plugged into one of the USB2 slots as it will not work on USB3, the Motu goes in the other USB2 because that won't work in USB3 either. The USB3 slots are used for a Roland A-300 MIDI keyboard, and a hub that has a mouse and a bus power lead for an eSATA drive that is always plugged into the eSATA port.

    Problem #1
    The Motu and Maschine don't dig each other's company. If I power up, with everything connected, there is no output, no audio runs. I worked thorugh different power up procedures until I came to the working solution of only plugging in the Maschine hardware once the software is running, or a VST instance of it. If i then close the software, with Maschine hardware plgged in, audio stops. This is of course not ideal.

    Problem #2
    Often, when powering up, without Maschine connected, I will have lots of audio glitching. Opening up Motu's Audio Console, and changing buffer rates a couple of times sorts this. However, playback often starts glitching/DC spiking while running windows audio/Sonar X1 without anything seemingly being changed.

    Problem #3
    I use Sound Forge pro 10 as my main audo editor, however it now does not work. It crashes if I open it while Sonar or any other audio application is running. I gather this is because it is still set to 44.1 in audio prefrences. When I open the program it changes the Motu's sample rate. If i try to change the sample rate in Soundforge it pretty much flips me off and stays the same. While doin this the other day, Sound Forge hung then I got my first BSOD (mini dump link at bottom).

    Basically, the Motu is rather hit or miss. I hate having to dick about unplugging/replugging hardware all the time, and I know how good it would be if it just got along. I'm very close to doing a clean install of the OS and starting again. I've updated (or think I have) the drivers for my Laptop, but it's quite hard to work out from the Clevo site just what I need.

    I'm in all day and it would be great if someone could have a look over the mini dump and help me identify what is causing all the grief. Let me know if you need any other info.

    Many thanks.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Welcome aboard.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {3, fffff80002e6caa0, fffaf80002e1caa0, fff9f80002e1caa0}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
    
    Followup: Pool_corruption
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    In such a situation, it is better to enable Driver Verifier to monitor the drivers.

    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  3. Posts : 10
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

    Ok, will do. Cheers for the reply.
      My Computer


  4. Posts : 10
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Ok, just had a BSOD. Audio had been a bit hit and miss after enabling Driver Verifier, and the compuer was failing to shut down fully. The BSOD occured when powering up the Motu, once the computer was up and running and signed in.

    Here's the new dump.

    Cheers.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    Yes, it is caused on Motu :)
    Code:
    fffff880`03368c08  fffff880`0637b323Unable to load image \SystemRoot\system32\drivers\Motufwa64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Motufwa64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Motufwa64.sys
     Motufwa64+0x38323
    Uninstall the FireWire, and see if it is crashing anymore or not.
      My Computer


  6. Posts : 10
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Do you mean uninstall just the FW componant and leave the USB driver? Uninstall Program only gives me the single 'Motu Hardware' option.

    I've located the file in System 32, tho the file contains more uppercase letters eg. MotuFWA64.sys.

    Just to clarify, my system doesn't have FW.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    bartak101, Motufwa64 means Motu firewire. Please have a check ...
    Driver Reference Table - Motufwa64.sys

    You uninstall whatever is there under Motu.

    If USB devices cause any problem, it will not be a big toruble later. OK?
      My Computer


  8. Posts : 10
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Ok, think I'm with you. I'll uninstall the entire soundcard run the system with Driver Verifier running and see if there's any more crashes.
      My Computer


  9. Posts : 10
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    Ok, just bluescreened while uninstalling Motu Hardware though Control Panel/Uninstall a program.

    'Motu Hardware' is no longer on the list.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    the last one happened during uninstallation only?

    It is not showing any cause though.

    Noe wait and see the situation. If it crashes again, we may need to enable verifier once again.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:10.
Find Us