Win8 x64 Fastlane USB MIDI Out lags and BSODs

[jayhitcher]

Hello forum,

After using a Fastlane USB's MIDI In capabilities for sequencing in Renoise (only pressing one note at a time, no complex input), I tried to use its MIDI Out with a RadioShack Custom Tone Synthesizer and a Roland MC-505 Groovebox, but whenever MIDI data was transferred out of the Fastlane, it'd start lagging and eventually hit a IRQL_NOT_LESS_OR_EQUAL BSOD.

The Fastlane does not cause a BSOD with simple MIDI In; with any MIDI Out and with testing through programs like SoundDiver it lags and subsequently crashes.

All of the drivers are updated. As soon as the issue made itself apparent I manually uninstalled/reinstalled the drivers (once through Device Manager, second time through the MOTU hardware setup). It still lags and results in a BSOD after continued use (around two minutes of continuous output).

I tested the Fastlane with a Win7 x64 laptop I have, and it runs perfectly fine with no lag, so there's definitely nothing wrong with the Fastlane hardware.

I'm using a Lenovo IdeaPad Y500, with the latest BIOS and the latest Intel chipset updates provided by the manufacturer.

I put minidumps from the crashes in a .zip here.

[torrentg]

I'd be very inclined to remove Daemon Tools then reboot. Check that this driver is then gone:

Code: Select all

   Image path: \SystemRoot\System32\drivers\dtsoftbus01.sys
    Image name: dtsoftbus01.sys
    Timestamp:        Fri Jan 13 08:45:46 2012 (4F10358A)
    CheckSum:         00046D1E
    ImageSize:        00049000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4 

Replace with PowerIso if successful.

DT is quite notorious.

Regardless, see if you can get an updated driver for this from Lenovo. If there is no update, then don't worry about it:

Code: Select all

0: kd> lmvm LhdX64
start             end                 module name
fffff880`01fed000 fffff880`01ffb000   LhdX64     (deferred)             
    Image path: \SystemRoot\System32\DRIVERS\LhdX64.sys
    Image name: LhdX64.sys
    Timestamp:        Mon Jan 11 10:06:58 2010 (4B4B3E92)
    CheckSum:         0001784C
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[jayhitcher]

Thanks for the response!

I uninstalled DT and made sure the driver for it was gone. Checked around to find an update for Lhdx64 (as far as I can tell there aren't any), and ended up finding a thread on Lenovo's support forums about it. None of my issues are as extreme as what the OP mentions--my boot time is as fast as always, no BSODs outside of using the Fastlane--so I'm unsure if it has much to do with this specific problem.

After the DT uninstall, I checked output through Renoise, and it still catches and lags as usual. I didn't press it far enough to get a BSOD because the lags were very apparent from the start.

I tested output in FL Studio to make sure it wasn't a Renoise issue, and I was able to send notes for roughly two minutes before lags started.

[torrentg]

You're welcome.

Funny, it doesn't make any bit of difference as far as the BSODs go, as the methodology is all the same, but I just realized you are talking about Win8 and not Win7.

Credit to you for even being able to post the crash dumps. Win8 doesn't make it easy out of the box to do that. Obviously, you were smart enough to take the proper permissions or use a tool to do it instead. And good job on the updates too.

Anyway....

It's probably a good idea to do all you can to TRY to make a new stop error (bsod). If you can't do that at all, then we already know we made some sort of progress in the right direction. If you can make one, then posting the new crash can not hurt the efforts but only possibly help.

I'm usually good and thorough, but perhaps I will see something I previously overlooked.

And if no bsod happens, then 100% concentration can then be applied to moving on the effort elsewhere.

[jayhitcher]

Sorry it's been so long since I've been able to respond. Been mad busy with getting ready for college stuff.

Today I plugged it in to test it, and I realized that the last times I was using the Fastlane, I had it plugged into the USB 3.0 ports of my laptop, rather than the one USB 2.0 port.

I plugged it into the 2.0 port, and it's functioning just as well as my Win7 laptop was. No lags, no crashes. I tested it with a sequence I wrote on the Win7 laptop using all eight channels of the 505, no problems after running it for half an hour straight.

I'm glad the issue was rooted out of something that simple.