[BUG]Sending messages from MME MIDI app to midi monitor causes Green Screen on the USB MIDI 2.0 driver and loopback device

[Sho-KDM]

Describe the bug
Sending messages from MME MIDI app to midi monitor causes Green Screen on the USB MIDI 2.0 driver and loopback device
This issue only occurs if the device is running with the USB MIDI 2.0 driver (UsbMidi2.sys) and loopback device (e.g. ProtoZOA)

To Reproduce

1. Load the attached firmware to the ProtoZOA.
2. Make sure the USB MIDI 2.0 driver (UsbMidi2.sys) is loaded.
3. Open midi.exe and monitor the ProtoZOA.
4. Open the Pocket MIDI 64bit(MME MIDI app) and choose MidiSrv enumerated ports for Output.
   Output: ZOA-104 (iIF AC) O-1
   
5. From the "Views" menu, open "System Exclusive" window.
6. In the System Exclusive window, open the attached test data set, then, System Exclusive window shows sending data.
   
   
   
7. Click "Transmit" to send messages.
   
8. In the few seconds after starting data transmission, then Green Screen occurs.

Green screen shows "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".

Expected behavior
No Green Screen.

Installer Name or Version
Windows.MIDI.Services.In-Box.Service.-.1.0.1-preview.7.24305.1438-x64.exe

Desktop (please complete the following information):

• OS: Windows 11 24H2 build 26120.2222 (Insider Dev channel)

Device information, if this is with an external MIDI device:

• ProtoZOA running with the attached firmware.
  UUT_ZOA_104.zip

• USB MIDI 2.0 class driver (USBMIDI2_10.0.1.7.x64.zip)

Application Information
MORSON Pocket MIDI (64bit MME MIDI app)
https://www.morson.jp/pocketmidi-webpage/

[MusicMaker]

Tested this with a UMP USB device that loops the USB packet internally (not via MIDI DIN). Seems to work. Saw once PocketMIDI to crash (closed itself). 10.0.1.7 driver
https://github.com/user-attachments/assets/6d48ed0d-5cff-4599-934d-6d61a96ce94d

[MusicMaker]

I used Pocket MIDI and just was sending some pitchbend message , then the app crashed the service too it seems
https://github.com/user-attachments/assets/287d04c3-aaf2-4ef7-ab6c-8ed8577161f2

[Psychlist1972]

This issue also appears to be a problem in USB MIDI 2 driver