I've tried everything I know, plus a million new things I've read about here on the forums to stop my Quad Capture from crashing X3d 64-bit, Win 7, but it still remains an issue.  I've gone so far as to reinstall/update all software, drivers, and synths from the ground up and still have intermittent problems.
 
When?  Sometimes randomly, but usually when I'm trying to bounce to track, or freeze soft synths...almost ALWAYS happens with Kontakt 5 (which I use on every project and have read also having issues with...), or as I'm closing/saving the project.  Happens on multiple projects.  It rarely crashes while I'm mixing, recording, etc., just when I try to do a bounce, freeze, or export.
 
A have a dumb theory that I may have the old Quad driver still on my system somewhere...but that remains an ignorant hunch.  Looking at my crash report below, it shows version 1.0.0.0, though I'm running 1.5.2 control panel and driver, 1.04 (012E) MAIN, and 1.01 (012E) BIOS (whatever that means). Should they match the event summary??  Anyway...I'm way over my head.  Any help would be greatly appreciated. 
 
BTW, thanks already to those on this forum who have helped me directly or via another poster's thread...pretty amazing knowledge base out there.  Here are the guts:
 
Faulting application name: SONARPDR.exe, version: 20.0.4.278, time stamp: 0x52abb061
Faulting module name: Rdas1117.dll, version: 1.0.0.0, time stamp: 0x523a6373
Exception code: 0xc0000005
Fault offset: 0x000000000000a350
Faulting process id: 0x640
Faulting application start time: 0x01cf36926bd040e9
Faulting application path: C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe
Faulting module path: C:\Windows\system32\Rdas1117.dll
Report Id: 6cdb22e5-a287-11e3-bbed-870af191d6f6

Your assumption may be true. Have you searched your C drive for "Rdas1117.dll" specifically? The only way you would see a version mismatch is if you do have two copies installed. I would start there. if you find multiple copies, you can right click on them, select "Properties" and then look at the "Details" tab for the file version.
 
Also, if you do find multiple copies, before doing anything with them, can you please post the locations that they are in?
 
Another quick thing to try is re-download, and re-install the X3d patch. That has the SONARPDR.exe file embedded into it (be sure to right click it and install as administrator explicitly).

caminitic
When?  Sometimes randomly, but usually when I'm trying to bounce to track, or freeze soft synths

You can stop focusing on your interface drivers. Freezing and bouncing are offline process that don't make any use of you interface driver. The only setting that's relevant to both offline and realtime processes is the ASIO buffer size which is used as the default "chunk" size for processing audio offline. If it's under 128 samples, you might try raising it. If it solves the bouncing problem, there's a setting in AUD.INI called BounceBuffSizeMsec that you can set to some non-zero value (zero is what tells SONAR to use the ASIO buffer size).
 
There may be something entirely different causing this. I just wanted to tell you it's not the interface hardware or drivers.

mettelus
Your assumption may be true. Have you searched your C drive for "Rdas1117.dll" specifically? The only way you would see a version mismatch is if you do have two copies installed. I would start there. if you find multiple copies, you can right click on them, select "Properties" and then look at the "Details" tab for the file version.
 
Also, if you do find multiple copies, before doing anything with them, can you please post the locations that they are in?
 
Another quick thing to try is re-download, and re-install the X3d patch. That has the SONARPDR.exe file embedded into it (be sure to right click it and install as administrator explicitly).

I have 8 copies of it on my computer...trying to figure out the best way to "post the locations" for you...wish I could just take a screen shot, but I'm not that smart...
 
 

brundlefly You can stop focusing on your interface drivers.

Wow...really?  I guess that's good.  BTW, the buffer size on Quad Capture and X3d are both set to 128...they're supposed to match, right?  And, if I raise the buffer on Quad Capture, would my latency suffer?  Thanks brundlefly.

Brundlefly has a good point that the interface is not a likely candidate for the operation you are doing (as the interface is not involved), but the 8 copies is rather odd.
 
I guess the quickest way for the dlls is to:
1) uninstall the drivers
2) search for "Rdas1117.dll" again, and rename them all (right click->rename->Rdas1117.bak) - changing the extension from dll to bak will make it a non-executable and easy to find later
3) re-install the latest drivers for the Quad-Capture
 
That will at least make the older ones incapable of being used. The fact that that driver is being declared as the "faulting module" is concerning.

Yes your latency will increase. But it's just temporary to test for an improvement in bounce/freeze stability. If it works, you can set it back to 128 and increase the BounceBuffSizeMsec parameter to the equivalent or higher in milliseconds. 4ms solved the issue I ran into with freezing Rapture when my buffer was 96 samples, but I went ahead and set it at 20 for good measure, and it's been there ever since.

Thank you both.  About the 8 locations...5 of them were in my downloaded install folder still on my desktop...lol
 
The other 3 are located in:
C:\Windows\System32\DriverStore\FileRepository\rdif1117.inf_amd64_neutral_abb12a575daf6aa6\RDAS1117.DLL
C:\Windows\System32\RDAS1117.DLL
C:\Program Files\RdDrv001\RDID0117\Files\RDAS1117.DLL
 
All versions are the same re: details, times, accessed-- actually identical -- though the permissions are different for all of them.  Weird.
 
The middle one, BTW, was the culprit for the latest crash due to its location.  Where did the other 2 come from?  Normal?

mettelus
The fact that that driver is being declared as the "faulting module" is concerning.

Yep.  Mysterious considering what brundlefly wrote...
 
I'll tackle the uninstall, rename, and reinstall tomorrow.  Thanks mett!

It helps us to troubleshoot when you provide your system specs (Look at my sig for what I'm talking about.  Also, do you have latest OS updates, software and interface drivers installed?  The fact that you have 5 copies of the interface driver file in your download folder is suggestive of a need to check all of the above:  updates, etc). 
 
Did this problem just start happening?  If not, did you make any change at about the same time it did?
 
One obvious tip - not mentioned so far - is to remove Kontakt from the project and see what happens.  If that doesn't work, then remove the other plugins systematically to make sure none are crashing the system.