I am fairly sure I may have some registry issues with my PC and I can not get my restore disc to work.
 
I have been using Sonar on the PC error free for a while but now everytime I load a project that has Addictive drums in it or add addictive drums to an existing or new project I get a SONARPDR.EXE has stopped working and has to close message, does anyone know how to find a solution to this problem?
 
Also does anyone know if an AMD Quad-Core A4 5000 processor would work for X3 Producer? I am looking at a new pc with it in it?
 
 

I dont bump my own posts but I am hoping for some helpful information.

Open the project in Safe Mode (I think this means holding down shift while you open it, but do a search to verify this) and then it will prompt you for each plugin to ask whether you want to enable it or not. Say 'no' when asked about Addictive Drums, obviously. Then, if the project loaded correctly, you should be able to delete that synth from your project. Save it, and hopefully it'll reopen perfectly next time.
 
I don't see why an AMD Quad-Core A4 5000 processor wouldn't work with X3, but AMD are generally not very good for CPU performance these days. (Review here: http://www.techradar.com/reviews/pc-mac/pc-components/processors/amd-a4-5000-apu-1153738/review) I'd recommend an Intel i7 if you're using a lot of synths and effects, or an i5 if not.
 

You were right about opening in safe mode. I did it and loaded the project, its addictive drums that's causing the problem. I was able to open a new instance of AD2 but when I saved and opened again...same problem.

Uninstall AD2, reinstall it. If that's not an option, I'd suggest contacting XLN Audio technical support who can probably advise on what needs to be done to get a clean installation.
 
But if you have wider issues with your PC and this is just one instance, then you're really going to have to fix the whole thing, maybe buy a new one. Run a check for errors on the hard disk, as a minimum.

If you can run AD2 in standalone mode, it's probably not AD2.
 
I don't know if this applies to you, but I throw this out  - 90% of the time on a failed or stuck project load, it's because the midi ports have changed and Sonar is expecting one where it is not. You should see the fun when Sonar starts defaulting midi to my Faderport --- yeesh.