Anderton
If someone's committed to using ASIO4ALL, then use it for a laptop (if you have a desktop, you should have a proper ASIO interface), and make sure no other audio drivers are installed. That's the only way I've gotten it to work.

Sorry but "you should have a proper ASIO interface" sounds quite offensive...
 
I am using ASIO4ALL on several different computers (2 desktops, 1 nettop, 1 notebook and recently tablet), with different interfaces (build-in and generic USB audio devices) and I have not noticed big problems with it. Every time I have tried to use WDM, either that was not working at all (tablet) or that increased usable latency.
 
The first device with which I have problems is V-Studio 20. Something which has "proper ASIO". Well, had... "discontinued" for Win10 without any technical reason (works fine under Linux, using generic Edirol drivers, so there should be not big difference between other, "supported", devices and this one). And from my general Internet observation, most "proper ASIO" devices are discontinued faster then I change my mobile phone, leaving me thinking either they are "a proper" way to go at first place...
 
What is really A MUST after installing ASIO4ALL is to configure it. It is almost never properly configured once installed, even when it till some degree "works" without changing anything. By default, it attaches itself to (all/arbitrary selection) devices and till there is only one (build-in) interface, that is wrong. It should be (manually) configured to use with one device only.
 
I can imagine that such driver can somehow influence other drivers. But it is surround by too many rumors, f.e.: http://mtippach.proboards.com/thread/1379/uninstalling-asio4all