BSOD "Ntfs.sys+ec93" Kernel Handle

"they dropped support for my 002 control surface" - Sounds like you ignored their warnings of moving on past the tech you invested in and now your seeking solutions to something no longer supported. I would advise that, as a businessman, you reevaluate your business strategy and investment to consider - if it keeps breaking and no support mechinism exists, how many 'outages' will occur and cost you repeated loses as compared to a one time reinvestment into your *CRITICAL* system. How much Return On Investment will you get from repeated 'outages' then from a one time critical expenditure.

Going forward from this point, unless you are heavy BIG name (Sony, Google, etc.) with MILLIONS to spend to ensure 24x7x365, no low end budget can prevent any downtime. You need to think in terms of Risk Analysis, the system WILL break, there WILL be a fire, there WILL be a power outage, the equipment has a limited (3 years) life span of support, etc. HOW do you recover? What are the steps? Then invest in each solution so you can be 24x7. Most small companies would likely have a scheduled replacement time window they would save capital over time to achieve BEFORE put into this position.

Just to comment/discuss, " Not all equipment dies out after three years, in fact I have a 16 year old mic sat in front of me" - Your are right in the sense of hardware itself shouldn't die out if maintained and kept proper (look at all the old 1950s, 1940s etc cars still out there).

But Software (which this is) and it's interoperatibility with other components both software and hardware can't be coorelated to that same idea. Basically, consider we had WAV files before we had MPEG standard which lead to MP3 then Apple helped push MP4 all different software based audio formatting (simplifying it for the discussion I know it is a matter of encoding, decoding, etc.) and never mind AAC and other standards out there as well. To interoperate among these, including hardware specific to support it, software is like water running down a stream, it changes overtime and many times it is changed we don't want but will have to settle for or worse move out of its way (flooding).

Any Business Guide or school that discusses the Lifecycle for technology equipment, across all industries, is 3 years, 5 for consumers. 3 years because by the time you have the equipment in your hand a year or 2 are already lost due to regulatory needs (can't just make a new wireless heartbeat maker and start selling it) or lost due to manufacturing timelines usually not the sametime as business purchase schedules. When you actually use it for 3 years, usually standards have changed, things have been dropped from support schedules, new advances have changed the playing field (as I mentioned devices supporting WAV files didn't make everyone run out and get the MSPod, but when things changed to the MP3/Mp4 standard everyone needed a iPod).

For businesses to be competitive and lucrative, they must be fluid and nimble to change is the mantra of any Business School or Guide, and in todays wifi, instagram, cellphone, there is a app for that instant world business came up with the 3 year rule to be able to stay that way. I wish you good luck in how best to handle it, but please do consider these words.