Serious Problems with Focusrite Scarlett (1st Gen)

What do you mean by "audio crapping out"?  Dropouts?  In any case, something may have changed with a recent O.S. update.
 
Run LatencyMon as explained here:
 
https://www.sweetwater.com/sweetcare/articles/solving-dpc-latency-issues/
 
Also, try the 2i4 with a different USB port (USB2 first).

 
Did you try a different USB port?  That might reinstall the driver for you.
 
When uninstalling, unplug the unit first.  From the error message, it does seem like you have some driver corruption. 
 
You can do a dirty uninstall (Delete the software folders, then delete the registry entries - the latter either manually or with a utility like JVPowertools or CCleaner).  Depending on the utility, some will handle all of these tasks so you don't have to hunt and delete anything yourself.

Yes it looks like your computer is thinking there are more than one and this must be there is 2 or more drivers installed. Moving USB ports can cause this to happen but it might be W10 updates too.   You install the correct driver from the Web site and if you move ports or during the next update Windows will re install a generic driver. This is a well documented flaw of Windows 10 now taking over proper driver management. It did this to my Video card. It took me a few hours to straighten it all out after reading on forums etc. I have since unplugged my DAW from the internet and will be very careful what updates when I plug it in again. 
Of course I don't have any issues with my W7 DAW :) It's always on line. 

No, Uninstall everything that is Focusrite first, Then install the correct driver. 

Exactly

petemus
 That's what I did, and it went well, without registry hackery or such.
 

It's not hackery, but rather cleaning up bits of leftover code.  You don't even have to go into the registry editor if you have a utility like JVPowertools or CCleaner, which searches for and cleans up all unused registry entries.   After a reboot, all the old driver bits are gone! 
 
This ensures a thorough fix as opposed to installing on top of the corrupted code and hoping it all works out.  Also, by leaving the old drivers in there, you never know if they'll cause a problem again down the road.
 
I get that some folks are leery of anything to do with the registry, but a registry cleaner is just another tool.  You don't have to know a thing about how it works - only how to run it.  The only thing I suggest users learn to do is backup the registry beforehand.  (In 20+ years of cleaning the registry I've never had to restore one because of a botched cleanup job.  Just pointing out that there's an easy fix if something bad were to happen).

JonD

petemus
 That's what I did, and it went well, without registry hackery or such.
 

It's not hackery, but rather cleaning up bits of leftover code.  You don't even have to go into the registry editor if you have a utility like JVPowertools or CCleaner, which searches for and cleans up all unused registry entries.   After a reboot, all the old driver bits are gone! 
 

Whatever works is ok! The idea with reinstalling the package is to use the manufacturer's installer to set those missing or faulty bits back in order and then remove them with the manufacturer's uninstall sequence, which most probably knows best what to remove (IF the (un)installer was done right in the first place).
 
All those 3rd party cleaners might do an ok job, but still. If you don't have the original installer available, then these utilities might come in handy.
 
     -Pete