Maybe too obvious, but as it's not been mentioned:
You are using RMEs own ASIO drivers, not ASIO4ALL?
 
Quotes:"I've been experimenting with using 64bits with 44.1KHz and for this project and  it was working fine until a few days ago "
"...because everything I recorded at 64bit sounded amazing. Any help greatly appreciated."
 
I'm not sure I understand this correctly. You mean you have installed both 64 bit SONAR and 32 bit SONAR?
Using 32 bit or 64 bit OS and/or SONAR version does not affect the recording quality in any way, AFAIK.
There are no soundcards that can go above 24 bits anyway. The higher bit rates have an effect
in the internal processing of VSTs or SONAR.

I've installed the RME Drivers and have them on my system. I think the card/program are running off the RME one rather than ASIO4ALL. I'm not really sure how I would check though as I have both installed (my other soundcard I occasionally use for editing with headphones uses ASIO4ALL).
 
 

Kalle Rantaaho
Quotes:"I've been experimenting with using 64bits with 44.1KHz and for this project and  it was working fine until a few days ago "
"...because everything I recorded at 64bit sounded amazing. Any help greatly appreciated."
 
I'm not sure I understand this correctly. You mean you have installed both 64 bit SONAR and 32 bit SONAR?
Using 32 bit or 64 bit OS and/or SONAR version does not affect the recording quality in any way, AFAIK.
There are no soundcards that can go above 24 bits anyway. The higher bit rates have an effect
in the internal processing of VSTs or SONAR.

I do have both 32 and 64 installed. If you're correct in what you've written (and I'm not saying you aren't, merely that I am confused), then maybe it's to do with how the software renders or otherwise presents and saves audio. I have files that I have recorded from Sonar which are 64 bit files and others which are 24 bit. If it doesn't make any difference on the way in then I won't bother. Would be good to know.
 
 

FWIW I have encountered situations where merely having ASIO4ALL installed has interfered with other drivers to the point where you had to increase latency with the "real" drivers to unreasonable amounts so as not to have dropouts.
 
Standard disclaimer: ASIO4ALL works very well for some people with some systems, and horribly for other people with other systems. Like all kludges, performance is subject to change without notice depending on what else is happening with your system.

intel i7-4710HQ CPU @ 2.50Ghz - there is your bottleneck.  You seem to mention more the bitrate instead of the buffer size.  You may have trouble having the ASIO set a 64.  Record dry add effects later.  You will not get desktop performance using a laptop.   

Anderton
FWIW I have encountered situations where merely having ASIO4ALL installed has interfered with other drivers to the point where you had to increase latency with the "real" drivers to unreasonable amounts so as not to have dropouts.
 
Standard disclaimer: ASIO4ALL works very well for some people with some systems, and horribly for other people with other systems. Like all kludges, performance is subject to change without notice depending on what else is happening with your system.

The system and setup have been working fairly painlessly for almost two years with ASIO4ALL also installed, so I don't think that is the primary cause of my issues.
 

kitekrazy1
intel i7-4710HQ CPU @ 2.50Ghz - there is your bottleneck.  You seem to mention more the bitrate instead of the buffer size.  You may have trouble having the ASIO set a 64.  Record dry add effects later.  You will not get desktop performance using a laptop.  

I do record dry. I mentioned this earlier. I'm not expecting desktop performance, but is it unreasonable to want a relatively stable recording system from a laptop?

I see no mention of adjusting the file system buffers. Pretty sure it is mentioned in the help linked to the Dropout TOAST. The adjustments are made in Preferences > Audio > Sync and Caching. To see "Sync and Caching" make sure to select the Advanced button at the bottom of the Preference screen.

In addition to scook's suggestion to look at the file system buffer sizes (not the same thing as the ASIO Buffer Size), I would suggest you try temporarily turning off or disabling your laptop's WiFi adapter, as that is often a problem for folks - where a WiFi adapter spikes the DPC Latency and causes audio streaming performance issues.
 
When I used to gig or record with a laptop, I would always go into Windows Device Manager and open the Properties for the WiFi, and then I would click Disable - just prior to launching Sonar, and that cleared up a bunch of audio problems - when finished with that Sonar session I would simply go back into Device Manager and click Enable on the WiFi, and all was back to normal for general use.
 
Bob Bone