Is anyone, who uses a Midisport 4x4 USB-to-MIDI box (either manufactured by Midiman or M-Audio, i.e. the "Anniversary Edition", henceforth to be referred to as "AE"), having problems with BSOD's or Windows 10 startup failures due to problems with the drivers?
 
I use two MIDI interfaces in my setup: one Midiman 2x2 and one Midiman 4x4.  If the 4x4 is disconnected, then I experience no problems.  So the issue lies in the 4x4 hardware.
 
M-Audio aquired Midiman a long time ago.  They re-issued the Midisport series of boxes as the AE versions.  Between the old Midimans and the new AE's, I suspect that absolutely nothing has changed in terms of the circuitry.  Therefore, replacing mine with an AE version would probably NOT solve the problem.
 
Just wondering if I should retire this piece of hardware to put it all behind me and go with something else like a MOTU Midi Express 128 or something comparable, or do something to solve the constant crashes with my existing gear.  Thanks!

I've had nothing but trouble with a 2x2AE since Windows 7. M-Audio taking ages to release drivers - like years - when new versions of Windows were released didn't help either. In the end I gave up on it when it's poor sysex and NRPN handling scrambled my Mopho patches. Again.

It behaves better connected to a Mac, but sysex is still an issue.

I'd say go with Motu. Works fine for me (Win 8.1 and Mac).

tlw
I've had nothing but trouble with a 2x2AE since Windows 7. M-Audio taking ages to release drivers - like years - when new versions of Windows were released didn't help either. In the end I gave up on it when it's poor sysex and NRPN handling scrambled my Mopho patches. Again.

It behaves better connected to a Mac, but sysex is still an issue.

I'd say go with Motu. Works fine for me (Win 8.1 and Mac).

Thanks, tlw.  This seems like the best solution to my problem.  What interface do you have?

Yes, Green screen of death as well in recent Preview. GDOS are gone now,in  Preview 16926.
Microsoft acknowledgedthe duplicate device name issues on Win 10. Has been there for > 1 year without a fix !
MIDI seems to have a VERY LOW priority for Microsoft.  Perhaps MAUDIO has no power to push either.
M-AUDO even stated somewhere on theor forum two M-Audio devices on Windows is not supported !
Two  or more M-AUDIO interfaces work PERFECTLY under Ubuntu  ! (Bitwig for example) with very large SYSEX et all
ONE MIDISPort MIDI interface on Windows works fine. Both the 4x4 AE and 2z2 AE.
 
Discussed with Microsoft. Conclusion is don't rely on much support for the MIDISports on Windowx 10. Two MIDISport devices won't work, Just try another device like the Mio https://www.iconnectivity.com/product.... Don't make the same mistake like me to believe things will get better and fixed by Microsoft and M-AUDIO. Microsoft considers the MIDISport line OLD produict. Don't buy TWO same M-AUDIO interfaces on windows 10. Sorry for negative recommendation, but this is reality.
 
It hilarious Windows MIDI  problems gets ingnored.
I am going t try an Mio, Forget about the M-AUDIO nightmare.
Do you remember NAMM 2016, M-Audio announced  new MIDI USB interfaces. They NEVER came to market !
 
Here are some link , don't forget to scroll down and read the comments.
 
Duplicate port naming and wrapper issues
https://docs.microsoft.co...udio-video-camera/midi
http://forum.cakewalk.com...UWP-midi-m3605788.aspx
https://answers.microsoft...85-75a25f5b7c67?auth=1
https://github.com/Micros...sal-samples/issues/639
https://social.msdn.micro...esizer?forum=wpdevelop
https://github.com/Psychl...10-MIDI-Library/issues
https://www.tenforums.com...i-port-limitation.html
http://forum.cakewalk.com...-Edition-m2931327.aspx

M-AUDIO MIDI-Sport issues.
http://community.m-audio....ws-10-preview-editions
http://forum.cakewalk.com...-Edition-m2931327.aspx