Cactus Music

poetnprophet

Cactus Music
What do you mean it has no drivers? It must. And is not Thunderbolt a known issue with PC? 

I'm using it via USB2/3, I'm not quite sure exactly how it works but I didn't have to download or install any drivers.

 
It's funny no one mentioned this as I guess we just assumed you had already done so.
You ALWAYS download and install the latest ASIO driver for all audio interfaces,, this is super critical otherwise you must be using a generic sub par driver. 
http://motu.com/download
 
 

The interface is maybe 2 weeks old, yes the first thing I did was download the app and update the firmware on the device.  Doesn't seem like there is a specific "driver" per se, seems like just an app for "discovery" and that's it....but what do I know?  My point is, there is nothing to update on that device at this point.

Have you read this?
 
https://cdn-data.motu.com...dio+Driver+Read+Me.pdf

Sure did, i almost have it memorized.

Audioicon

Given the OP/User is experiencing issues with Sonar my comment is not about "Any DAW."
Why should I or would I comment on Any DAW when the issue here as reported by the OP is regards to using Sonar?
Please go back and read my post and if possible put down the cool-aid first. 

I never said the issue is with Sonar, again, I even talked about using Windows Server.

I wont get sucked into a Cool-Aid driven battle.

 
No Cool-Aid driven battle intended (I own four different DAWs, so wouldn't be qualified to dispense any one flavor of Kool-aid).
 
I apologize for believing you were "picking on" Sonar.  When I read it, that's how it came across.  I was told I'm getting grouchier in my old age.  I've stopped yelling at kids to get off my lawn, but then the pent-up stress only finds its way here.
 
In the future I promise to direct my grumpiness where it belongs -- at the neighborhood kids.

Update:. I thought I had it figured out. I disabled all plugins on a very small project. Still crashed. I noticed that it seems to happen exclusively when I stop transport. Also seems to happen more with waveform edits: splits, fades, trims etc.
I forgot I had pro channel modules so I disabled those. There is another thread mentioned the console emulator. Then, I was able to work for about 3 hrs without a crash. But it did finally crash, again when I stopped transport. Had another crash shortly after that, but did finish the 4 hr session.
Someone mentioned bad memory. I ran a memory test and all checked out.
I also disabled onboard video in the bios.
Any other ideas, anything I can test?

poetnprophet
Update:. I thought I had it figured out. I disabled all plugins on a very small project. Still crashed. I noticed that it seems to happen exclusively when I stop transport. Also seems to happen more with waveform edits: splits, fades, trims etc.
I forgot I had pro channel modules so I disabled those. There is another thread mentioned the console emulator. Then, I was able to work for about 3 hrs without a crash. But it did finally crash, again when I stopped transport. Had another crash shortly after that, but did finish the 4 hr session.
Someone mentioned bad memory. I ran a memory test and all checked out.
I also disabled onboard video in the bios.
Any other ideas, anything I can test?

What type of crashes are you getting? - i.e...
 
is it a blue screen? - if so, what type of error code does it give?
 
Does cakewalk just freeze or quit?
 
Is the computer still usable immediately after the crash or do you have to reboot?
 
[Edit] - Just thought of another possible issue. I had crashes really early on with OneDrive trying to access my audio files whilst I was in Cakewalk/Sonar. I ended up disabling OneDrive in the end, but you should at least check that things like OneDrive or any virus checker is not trying to access ANY of the folders that your projects and/or audio files are in.

poetnprophet
Update:. I thought I had it figured out. I disabled all plugins on a very small project. Still crashed. I noticed that it seems to happen exclusively when I stop transport. Also seems to happen more with waveform edits: splits, fades, trims etc.

I've been noticing something similar: In a track with intensive edits (splits, amplitude changes, rendered Melodyne, normalization) if I bounce the clips together, everything seems normal - I can save, move tracks, enable buttons, pull down menus, whatever. But as soon as I hit play, CbB freezes. I then have to call up Task Manager, shut down, and open but at least I know to save before hitting play. 
 
I suspect this may be project-dependent, because I did a quick check on a newer project doing a bunch of splits and bounces, and there weren't problems. My next step will be saving and then re-opening as a bundle. Everything might be fragmented as hell.

I would run latency monitor while running the project that crashes.

Thanks for the posts but if you go to the OP you will see I have been running latency monitor during crash, happens on big and small projects, with interenet or not, and the specific crash behavior.

poetnprophet

I am now using a Motu 828es.  It has no drivers.  

This is incorrect.  

https://cdn-data.motu.com...dio+Driver+Read+Me.pdf

The MOTU Pro Audio driver is now available for download
at motu.com/download or motu.com/avb. Rewritten from
the ground up, this new driver provides high-performance
support for Thunderbolt and USB on both Mac and
Windows for MOTU’s latest-generation audio interface
models

poetnprophet

Cactus Music

What do you mean it has no drivers? It must.

I'm using it via USB2/3, I'm not quite sure exactly how it works but I didn't have to download or install any drivers.

I think that this is probably a key step that may have been overlooked...
 
Without the MOTU driver installed in the PC, and Cakewalk configured to use it, the system is likely running with a default Windows driver.