Found it really handy when you start loading up Kontakt or other sample based instruments

 

Sorry mate, 1.5tb of ram and 60k$ for a MacPro, now that is ridiculous, 64gb is just fine and won't break the bank either. If you noticed the OP's system is a quad channel mobo, he can populate half the mobo slots with 16gb sticks and still have space for more. I have 64gb on my secondary machine lol. At the moment even serious gamers go with 32gbs. NVME ssds which is the norm for anyone wanting at least a speedy system drive, require 16gb minimum to perform full speed. For anyone using a lot of sample libraries more ram is never enough. Seriously now, ram has nothing to do with what bullcrap MS issues as "DCH drivers". I wonder what do they test that sht with before they release it.
Cheers

 

Sorry to hear about the issues your having, but there are so many variables this thread is quite useless without providing a full spec sheet and showing us lots of tests.

I have built an intel machine that was a total pig to get smooth, then shortly after an AMD based one that just worked. you can either go with a recommended set of hardware or go through a bunch of troubleshooting/hardware replacement but I would have thought the more advanced technology gets the easier stuff like this is.

How old is this computer?

 

Man,I thought you were joking untill I ended up on the Apple website!

 

That board with the AIC Card seems to have issues no matter how it is being used. A board at this lelvel should never have been released without thorough field testing.

Two choices I would use if building an Intel based system are:
Gigabyte Z390 Designare & ASUS Prime X299 Edition 30

These have the TB3 ports on the rear i/o eliminating the possible translation/communication errors of an AIC Card connected by means of a TB3 header.

A few have mentioned BIOS settings. There is a possibility that the correct BIOS settings could eliminate your issue.
Some 'Auto' settings in the BIOS can set memory timings incorrectly for 'stock' settings.

NVidia drivers could be another issue.


Hope you find a workable solution...

 

True the (Gigabyte) boards which come with straight out of the box TB3 connectivity in the rear i/o have been reported less troublesome. But bro, it's the same thing and TB3 itself is not some otherwordly exotic science either. It is pci-e over usb-c. The hardware does most of the job itself. I'm pretty sure the OP's problem is the driver, although his system is somewhat ~3 years old and by now he should have found a solution imho. Right now, TB3 Windows10 users, if they want a working system, they have to download a driver from Intel which is oddly named "Thunderbolt 3 legacy driver for Windows 10 for Intel NUC". Performing a clean install with no traces of the "new" DCH driver left in the system is mandatory too.
They also have to disable any C-States from the bios and Windows and any other tech that makes ports,pci-e slots and cpu cores park, sleep, hibernate or use less power than nominal etc etc.
Cheers

 

Last edited: Dec 30, 2019

I built this one last year. Setup now works but often have to sign out and log back in for audio in WASPI. Sonarworks adds a layer of complication taking output from interface but it is working. Thank you for your help everyone!

 

Using the Nvidia studio version of the driver works better than the game ready driver. Thanks