Interesting. Someone from Cakewalk who used a US-366 (same basics as a 322) was going to do a SONAR demo to the press, and I had been invited. So he brought the interface and his laptop to San Francisco.
When he booted up his demo the evening before for a run-through, he found to his horror that no TASCAM latency setting was long enough. There were crackles, soft synths crashed, and there were other issues. I checked his drivers for the 322 and they were the most current. He said "Oh well, I have ASIO4ALL on my laptop, I guess I'll use that."
Aha! I asked him to uninstall ASIO4ALL completely - not just disable it, remove all traces from his computer. He was reluctant but did so. After that, the interface worked perfectly, the latency was low, nothing crashed, and the demo went off without a hitch.
I've done a ton of interface reviews over the years, and the TASCAM ones weren't the only interfaces compromised by ASIO4ALL. I need to add my usual disclaimer: This is not a diss, and I applaud ASIO4ALL for a very clever kludge that manages to fool Windows into doing something it wasn't intended to do. But it's a last resort. If you have native drivers for an interface, use those and completely uninstall ASIO4ALL. Driver conflicts are a little like a game of chance; they affect some programs and interfaces but not others. Why take a chance?