Ah! My Mettel friend with the sweet cherry car, always with good advice!
Yes I am writing to an internal drive. And come to think of it, I had been playing with the buffers in an attempt to placate a Melodyne persistent prompt. Maybe a short time prior to the constant crashes. Buffers always confuse me a bit, sometimes high buffers are good (Melodyne wanted them increased) , sometimes low buffers are good ( for Latency issues I think). I dunno. should I turn em up or down?

Also, in the sync and cach, should the 'enable read' and 'enable write' be checked or no?

Buffers can be bad if set to extreme values on either end. Too short and the CPU has to run like a race horse to keep up, and too slow and the system can be left "waiting for data." Since you are already recording "happy go lucky" and your system choked, it seems like either a streaming issue or some service came online that kicked SONAR to the curb (unlikely). Some of those messages above hint at fails to call storage requests, but not researched them specifically.
 
For buffers, the sort of "happy mediums" to start with are:
   Preferences->Audio->Driver Settings: Buffer size of 256 (set via the ASIO panel). These are the ones that are best lower when tracking, and higher when mixing. Unless you actually see Melodyne do freaky things, blow off that warning message. I tend to track at 96 samples and mix at 128 or 256.
   Preferences->Audio->Sync and Caching (requires advanced mode at the bottom): File System section. Playback and Record I/O buffer size of 512KB (default is 256). Enabling the read/write caching may or may not help, most likely not since your system is resource heavy. I bumped mine up to 512KB on a massive project a couple years ago, and left them there since.
 
   Just in case on the latency/process side of things; have you tried running LatencyMon on your machine (download is in "Free Downloads on the left-hand side)?
 
   For drivers, Iobit has a utility to check them versus current called Iobit's Driver Booster. You can use this just to check and choose to download manually if it identifies things (since it is slower than dirt to try to get you to buy their paid version). If you choose that, be sure to create a manual system restore point prior to use, so you can back out if it completely (including its installation) if something goes weird with it. I couple of forum users reported the drivers it chose were not correct a couple years back; but I just rebuilt my Win7 with it and was fine.
 
  

Thanks again!
I did the buffers to 512 and will go back and uncheck the enable boxes that I had just checked and see, cuz it just locked again. I did have the LatencyMon before my last reinstall, I'll get it back and see. asus keeps telling me their drivers that I'm using are current and Roland hasn't rolled out an update of Win7 drivers for the Octacapture in a few years. They did an update for Win10 but I'm still on 7. But ill check out what the driver Booster has to say. Thanks again so much for the help! 

It has been a while since a permissions crash has been posted - I pulled an all night edit on a business plan so I have to grab a couple hours sleep - if nobody else jumps in, I will try to help after I recover a little brain.  :)
 
I am dimly recalling where installs were not getting the elevated permissions that explicitly using Run As Administrator gives, and that performing a clean removal of Sonar and launching the installer again but this time right-clicking on the installer icon and telling it to use Run As Administrator.
 
There are other brain farts telling me that some folks had had issues where their anti-virus/anti-malware software had been running during install or post-install where that software was causing Sonar to hiccup, and they too had done a clean removal of Sonar and another install - also with Run As Administrator, and also with anti-virus and anti malware software either temporarily suspended during the Sonar install or possibly adding things to the 'exclusion list' kind of thing - but I think the temporary suspension during Sonar install was a bit cleaner of a way to go.
 
Anyways - hopefully the above will either help you or will jog someone else's memory to jump in and help get you going, while I grab some much needed shuteye.
 
I WILL check on this after my nap :)
 
Bob Bone
 

Thanks Bob, I will try another install, and check.
Mettelus, I did the latencymon with no probs noted, and the drive boost found a few drivers that I had disables like the high def audio and such that I don't use, but I updated anyway just to be sure. Still failing to respond , checking for solutions, and closing....., maybe the reinstall will help. thanks so much guys!!

Check out this post about that error.
 
To boil this down, Win7 has had drivers installed for a peripheral storage device (USB connection), and is prompting a connection call to it (when it is not even connected). One post makes reference to a "Sony Powershot DSC-H9" (camera) drivers, but this could be drivers for any external hardware it seems (camera, phone, etc.).
 
Do you have any external hardware you connect via USB that has 1) internal storage and 2) specific drivers to run?
 
Quick edit: another possibility may be your keyboard is running at permission levels above SONAR. Try running SONAR as administrator and see if that helps (right click SONAR->Run as Administrator).

I see that you mentioned that you're running your CPU at 4.5GHz. If you're running it over-clocked, I suggest seeing if the issue still occurs at the stock clock speed.
 
-e

I would turn off the HDMI Audio Adapter by right clicking the "Speaker" on the taskbar and selecting "playback" and "Recording Devices" and disable it in both, this interface can sometimes override the internal soundcard and cause sonar to crash...
 

Thanks again guys! I do so appreciate the time and effort of all! You and this forum is one of the big things that keep me trying to work Sonar out!
I tried a uninstall and a reinstall, no glory.
Mettelus, I'm looking but I have no connected devices that  have internal storage other than two flash drives, one that keeps an emergency Linux OS on it the other is for the BIOS and they have been in place since I built the machine in '11 or '12. I have had cameras connected in the past to do videos (that worked out rather nicely I might add) but have not been connected for some time, and the external hard drives that I keep for backups are disconnected/unplugged. My Keyboard is a Roland Fanthom X8, and like the OctaCapture no updated drivers from Roland in a few years, I do use it for analog as well as MIDI control, could that be a problem, I am currently, as I have many times in the past without problems, recording both an analog voice through one track and a controlling a softsynth MIDI voice through anther. I'll try and doo those separately and see if that's makes a difference, (that'd be a real bummer as I kinda need the MIDI notes in perfect sync with the analog voice, and I never play anything the same way twice.:/)
-e, I may have over spoke in my frustration, the stock speed on the CPU is 4K and that's where she's at, no overclocking done, thanks for the observation though. I'll try to keep the facts factual.
Shawn,  yessir, all other audio adapters have been disabled for a few years now, except the OctaCapture, I just updated the drivers on those to make sure I am complying with all suggestions to make this work. Thanks though.
 
FWIW, I have noticed for a while that I get a white screen flash whenever Sonar loads the default template on startup, and the past four or five lockups/crashes/freezes or whatever they're called, what ever I'm recording, I still get that audio and I get the metronome hits but the other tracks, drums etc. drop out. Maybe normal but I thought  strange.