This is still pretty "anecdotal" evidence but my production laptop doesn't like my friend's Audient ID22 at all. I get frequent pops and even a few crashes with the latest drivers, and couldn't find a solution in a different buffer size or sample rate. My laptop is otherwise rock solid using my RME Fireface UCX or my Behringer X18, or even my other friend's A&H Qu24 or the Behringer X32 at the music school I work at.
 
I don't trust Audient interfaces anymore. It works great on his Mac though. Do you get the same crashes if you try using WASAPI or even MME with the internal sound chip?
 
Btw my laptop runs a 980 and it helped when I installed just the bare NVidia driver set, not that whole GeForce experience BS. With "helped" I mean I got significantly lower latency on LatencyMon and far fewer hard page faults. Also worth checking out.

Sanderxpander
 
..... it helped when I installed just the bare NVidia driver set, not that whole GeForce experience BS. With "helped" I mean I got significantly lower latency on LatencyMon and far fewer hard page faults. Also worth checking out.

Yes this has been my experience with NVidia as well. At least for DAW use. Good call.

Thanks guys,
 
Power setting all set to off to avoid sleep states and I had to disable xmp when I first configuresd the machine and set it to full auto in the bios as I just couldn't get the system to boot with it in anything other than auto.
 
Thanks for the words of warning about the Audient - although to be fair when I first put this machine together I was still using my Zoom R16 and was having similar problems - The Zoom worked fine with my old laptop rig.
 
So far tonight the system has been stable but i've not been pushing it hard really as I have been n and out of here and other stuff I've been dealing with. 
 
I do wonder about all the extra crap installed by the GeForce experience but again in the (admittedly little) bit of latency testing I did last night I didn't get any page faults even when running a full mix featuring my normal loading of plugins and VST etc. How would I go about keeping just what I need from it and losing the rest?

To revisit the comments about DPC Latency Checker, since you asked about that, it was never rewritten for Windows 8 or 10.  It works fine, but the readings are about 1000 too high.  Thus a system that is fine shows as borderline.  If you don't get any red spikes, you are not having a problem with some offending driver.  In my experience, such drivers are things like wireless devices and network interfaces.
 
LatencyMon is optimized for Windows 10, and if that shows you are fine, that's even better.  In other words, your problem lies elsewhere.
 
I used to have Windows crash routinely and I got a free utility that could show me the cause of the crash after I rebooted.  It had 'Blue" in the name, I think, but there are others.  Also, there is a setting in Windows that, when a crash occurs, you can let the machine hang rather than fully reboot.  That may prove helpful to view what happened.

I just set lat mon running and spent some time driving the system really hard - loading up full projects and playing, stopping, looping on the fly and jumping all around the timeline while it was playing - that kind of thing.
 
All was looking good until i finally bombed out Sonar by doing this in a project which has a video synced up in the video view.
 
These are the monitor reports for this period:

 

 
 EDIT: - Hmm cant seem to get the images to show?

OK almost all your recent crashes are Sampletank 3.  Some are the VST2 version, some the VST3 version.  (a few of the crashes are just SONAR itself, one crash from Melodyne, and one Kontakt crash).  But of the July 2017 crashes it's really just Sampletank 3.  In some of the older crashes your using a ZOOM ASIO driver but all the recent ones are the Audient.  There isn't really anything that sticks out though.  So if I were trying to fix this I'd do simple things:
 
I'd uninstall Sampletank 3.  Then completely delete it from c:\Program Files\IK Multimedia\SampleTank 3 and C:\program files\Cakewalk\vstplugins and c:\Program Files\Common Files\VST3.  Don't delete/uninstall your sound library, just the software itself. 
 
Then I'd start SONAR, not open a project, open the plugin manager (from inside SONAR) and then I'd go into the VST options, make sure the paths are correct (and include the VST3 paths) and do a full reset and then rescan everything (without Sampletank installed).  Then when it was done, I'd exit the plugin manager, then exit SONAR and reboot.
 
I'd make sure if I'm running Windows 10 I've turned off Game Mode (see this blog post http://blog.cakewalk.com/windows-10-creators-update-your-daw-is-not-a-game/ )
 
I'd download and install the latest 2015 C+ Runtime and the 2017 C++ Runtime from Microsoft
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
and (direct link to the 2015 runtime)
https://www.microsoft.com/en-us/download/details.aspx?id=52685
(the version of VCRUNTIME140.dll you are running is earlier than the one I have)
 
I'd make sure I apply all Windows Updates.
 
I'd get the newest Sampletank 3 from IK (they just shipped an update last week).  And I'd install that.  Then start it stand alone and make sure everything works right there (configure its ASIO standalone settings).  Then start SONAR and let it find it.  It should find both the VST2 and VST3 versions. 
 
While I believe the VST3 version is buggy with SONAR, if you have a project that uses the VST3 version there is no way to "convert it" short of opening it, saving the multi, then removing it and adding the VST2 version and reloading the settings.  That's super painful and I don't recommend it.
 
Sampletank 3 does have issues when the latency on the audio device is too low,  I know it has pushed me to increase my ASIO buffer more than once to get it to stop crashing (I've got a Sampletank 3 test project that won't play without stuttering/stopping unless I have my ASIO buffer set to 20msec, lower than that and it will hiccup, much lower and it crashes.  But my older Focusrite Saffire isn't exactly a low latency device).  I'd consider doubling whatever you are using now, if you can try something 4 times what you have been using.  Even if it's not usable at that level, it might help you narrow the problem.
 
You might also want to try changing SONARs options for Plug-In Load Balancing.  I'm running with it and the multiprocessing engine on, but there are forum posts of problems that the load balancing seems to be causing.
 
I doubt though any of this will fix your problem, though it might push it out or delay it.  If it still happens, then start trying to produce a reproduction case.  While the problem really is Sampletank 3's code, I don't think IK support will be of much use.  If you can get it to happen on command you might at least get them to look at it.  You might want to contact them and see if they can offer any advice, just because I've not had any luck with them doesn't mean you won't.  Good luck.