[BUG]: DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by USBMidi2.sys

[dazjjackson]

Windows Version

26200.8328 ge_release

Service Installation Method

In-box In Insider Build

SDK version, if appropriate

No response

Location

Other or Unsure (please indicate in additional notes section below)

Type of bug

Windows Crash (please include device id from Windows Settings About page)

Steps to reproduce

Device ID : 81274EB9-B13A-447A-A893-8159F75C1AD4

Had an NTS-1 digital kit plugged in via USB MIDI, but not really being used.
Machine was running fine for a while, but then green screened with an DRIVER_IRQL_NOT_LESS_OR_EQUAL bugcheck.

WinDBG Output.txt

Expected behavior

Should not be crashing Windows

Additional notes

Second time this has happened. Seems to be when the device has been connected for a few hours and not actively in use.

[Psychlist1972]

We've been investigating this due to #1001 . We think it may be caused when a device starts sending messages immediately on connection (like the Korg nanoKNONTROL sending clock messages as soon as connected.

Do you know if the NTS-1 is set up to send messages right upon connection?

Note that you can change it to use our older MIDI 1 driver (usbaudio.sys) to avoid this crash.

Pete
Microsoft

[dazjjackson]

Ah ok, I did see that one, but wasn't sure if this is the same behavior or not as that was related to a crash having devices conneted during boot.

The two times I've had this crash happen I've connected the NTS-1 after the machine has booted and have been using it just fine, then I left the device connected while I was doing other things. The crash seems to happen after an extended period of time with the device connected but not being used, so could be something going on with power saving I guess.

I'm afraid I can't answer the question about the device sending messages on connection, but thanks for the tip about using the MIDI 1 driver.