Subject:Frequent Acid Pro Crashes

Posted by: rumun

Date:4/20/2015 1:21:02 PM

Hi, I was hoping someone here may have some advice as to how to maybe troubleshoot my frequent Acid Pro crashes. When nearing completion of a project (e.g. around 40 tracks, lots of FX chains, 5 VSTis, 4 bus tracks) I get numerous crashes and am unable to play for more than at most 20 seconds before Acid crashes.

This does not happen anywhere near as frequently at the start of a project, only as the load increases. CPU usage is usually around 25%, ram usage in the 1-2 GB range as reported by windows task manager. The crash message appears to differ each time and with each different project, sometimes referencing specific VST plugins, sometimes not. I believe this is down to load of VST FX i.e. the more I have, the more likely the crash.

Is there anything I could try? I am currently using ASIO, and have tried the other device options with no success. I am running Acid with admin rights on an admin account, and have disabled just about everything in Acid I don't use to try and alleviate the problem. I can paste an error message if it would help.

Thank you.

Subject:RE: Frequent Acid Pro Crashes

Reply by: mike_in_ky

Date:4/20/2015 4:05:55 PM

Are you running Windows 8.1?

Subject:RE: Frequent Acid Pro Crashes

Reply by: rumun

Date:4/21/2015 11:56:12 AM

Hi, yes I am. My system:

Windows 8.1 Pro 64 bit
i5 3570k 3.4 GHz quad core
8 GB DDR3 1600 MHz RAM
RME HDSP9632 PCI Soundcard (latest driver 4.06)

Running various vst, vsti and dx plugins but mostly using NI Komplete 7 and the izotope fx bundled with Soundforge Pro 10 and Acid Pro 7.

Would one of the compatibility mode options help with stability?

Subject:RE: Frequent Acid Pro Crashes

Reply by: mike_in_ky

Date:4/21/2015 3:27:44 PM

My wife's laptop has 8.1 on it, too, and Movie Studio 12 crashes unpredictally.

Subject:RE: Frequent Acid Pro Crashes

Reply by: rumun

Date:4/21/2015 3:34:41 PM

Thanks for letting me know. I may have to dual boot xp just for acid if I can't find a solution/determine the offending combination of fx (qualitatively appears random).

I will let you know if I do find a solution, it may be of use.

Subject:RE: Frequent Acid Pro Crashes

Reply by: rumun

Date:4/22/2015 11:49:16 AM

In case this may help someone shed some light here is an example of an error message:

ACID Pro 7.0
Version 7.0e (Build 713)
Exception 0xC0000005 (access violation) READ:0x62ADF000 IP:0x3133C599
In Module 'acid70k.dll' at Address 0x31060000 + 0x002DC599
Thread: TrackRender ID=0xFDC Stack=0x09FAF000-0x09FB0000
Registers:
EAX=000000b8 CS=0023 EIP=3133c599 EFLGS=00010297
EBX=00000fd5 SS=002b ESP=09faf454 EBP=000000b9
ECX=000000b8 DS=002b ESI=0000002a FS=0053
EDX=62adb0a8 ES=002b EDI=00000000 GS=002b
Bytes at CS:EIP:
3133C599: 8B 7C 9A 04 83 C3 01 8B .|......
3133C5A1: C7 2B C5 99 33 C2 2B C2 .+..3.+.
Stack Dump:
09FAF454: 5F69BAC0 5E8F0000 + DABAC0
09FAF458: 5F607710 5E8F0000 + D17710
09FAF45C: 00000800
09FAF460: 5F6954C0 5E8F0000 + DA54C0
09FAF464: 00000026
09FAF468: 5F68EEA0 5E8F0000 + D9EEA0
09FAF46C: 62ADB0A8 62720000 + 3BB0A8
09FAF470: 000000BA
09FAF474: 5CACD1B8 5C810000 + 2BD1B8
09FAF478: 0000002B
09FAF47C: 0000002B
09FAF480: 000000BA
09FAF484: 62AD7098 62720000 + 3B7098
09FAF488: 000000B6
09FAF48C: FCBC4E38 7FFF0000 + 7CBD4E38
09FAF490: 3FA2F983 3EB60000 + ECF983
> 09FAF498: 31343576 31060000 + 2E3576 (acid70k.dll)
> 09FAF52C: 3133853D 31060000 + 2D853D (acid70k.dll)
> 09FAF564: 313865E0 31060000 + 3265E0 (acid70k.dll)
> 09FAF574: 31349116 31060000 + 2E9116 (acid70k.dll)
> 09FAF590: 6F987476 6F970000 + 17476 (MSVCR80.dll)
> 09FAF5BC: 3133F234 31060000 + 2DF234 (acid70k.dll)
> 09FAF5E4: 31341C32 31060000 + 2E1C32 (acid70k.dll)
> 09FAF644: 3133D580 31060000 + 2DD580 (acid70k.dll)
> 09FAF65C: 31338239 31060000 + 2D8239 (acid70k.dll)
> 09FAF668: 31338F4D 31060000 + 2D8F4D (acid70k.dll)
> 09FAF670: 31339D60 31060000 + 2D9D60 (acid70k.dll)
> 09FAF6C4: 3133027F 31060000 + 2D027F (acid70k.dll)
> 09FAF6D0: 31339E4A 31060000 + 2D9E4A (acid70k.dll)
> 09FAF6DC: 31335043 31060000 + 2D5043 (acid70k.dll)
> 09FAF714: 38E8BBB7 38E80000 + BBB7 (sfvstwrap.dll)
> 09FAF728: 38E8E29C 38E80000 + E29C (sfvstwrap.dll)
> 09FAF764: 005648B7 00400000 + 1648B7 (acid70.exe)
09FAF768: 00018000 00010000 + 8000
09FAF76C: 00000000
09FAF770: 00000090
09FAF774: 00000000
> 09FAF794: 38E8E9B7 38E80000 + E9B7 (sfvstwrap.dll)
> 09FAF79C: 38E8BBB7 38E80000 + BBB7 (sfvstwrap.dll)
> 09FAF7B0: 38E8E29C 38E80000 + E29C (sfvstwrap.dll)
> 09FAF7D8: 4B58A8AB 4AD00000 + 88A8AB (icudt46.dll)
> 09FAF7E8: 38000000 37F50000 + B0000 (sfrewiresynth.dll)
> 09FAF7EC: 38000000 37F50000 + B0000 (sfrewiresynth.dll)
> 09FAF7F0: 38000000 37F50000 + B0000 (sfrewiresynth.dll)
> 09FAF7F4: 38000000 37F50000 + B0000 (sfrewiresynth.dll)
> 09FAF804: 311AFF07 31060000 + 14FF07 (acid70k.dll)
> 09FAF820: 31338B4D 31060000 + 2D8B4D (acid70k.dll)
> 09FAF840: 31339010 31060000 + 2D9010 (acid70k.dll)
> 09FAF850: 3133A70A 31060000 + 2DA70A (acid70k.dll)
> 09FAF868: 313353AC 31060000 + 2D53AC (acid70k.dll)
> 09FAF87C: 31330E94 31060000 + 2D0E94 (acid70k.dll)
> 09FAF8DC: 31330BCA 31060000 + 2D0BCA (acid70k.dll)
> 09FAF8EC: 00529657 00400000 + 129657 (acid70.exe)
09FAF8F0: 00216CC8 00210000 + 6CC8
09FAF8F4: 000062A6
09FAF8F8: 00000000
09FAF8FC: 00000000
> 09FAF920: 0051A4D1 00400000 + 11A4D1 (acid70.exe)
09FAF924: 00000000
09FAF928: 02BD24F8 02B90000 + 424F8
09FAF92C: 00000000
09FAF930: 000062A6
> 09FAF94C: 00879800 00400000 + 479800 (acid70.exe)
09FAF950: 09FAFDCC 09EB0000 + FFDCC
09FAF954: 00000000
09FAF958: 00000000
09FAF95C: 00000000
> 09FAF974: 379A794A 37990000 + 1794A (sfppack1.dll)
> 09FAF9A4: 31114E90 31060000 + B4E90 (acid70k.dll)
> 09FAF9B8: 310DA6F6 31060000 + 7A6F6 (acid70k.dll)
> 09FAF9C0: 00879800 00400000 + 479800 (acid70.exe)
> 09FAF9C8: 31114F36 31060000 + B4F36 (acid70k.dll)
> 09FAF9D0: 31114E90 31060000 + B4E90 (acid70k.dll)
> 09FAF9D8: 00879800 00400000 + 479800 (acid70.exe)
- - -
09FAFFF0: 00000000
09FAFFF4: 00521700 00400000 + 121700 (acid70.exe)
09FAFFF8: 05541030 054E0000 + 61030
09FAFFFC: 00000000

Subject:RE: Frequent Acid Pro Crashes

Reply by: Silamanagic

Date:5/13/2015 1:01:59 PM

I found that the NI plugins that came stock with acid pro 7 cause acid to crash. I can actually force it to happen anytime by trying to remove those plugins from an effects chain.

Subject:RE: Frequent Acid Pro Crashes

Reply by: Geoff_Wood

Date:5/13/2015 5:44:28 PM

They are instruments (no ?). Why are they in an effects chain ?!!!

geoff

Subject:RE: Frequent Acid Pro Crashes

Reply by: Silamanagic

Date:5/17/2015 9:57:38 PM

Should they not be? If I record a guitar track them want to apply one of the NI guitar modulators to it how else would I do it?

Subject:RE: Frequent Acid Pro Crashes

Reply by: AudioVizionz

Date:5/18/2015 2:57:12 PM

So this is a combination of midi/wav? Try rendering stems from various simplified versions of your project.

Subject:RE: Frequent Acid Pro Crashes

Reply by: Silamanagic

Date:5/18/2015 9:05:42 PM

I hear ya. But rendering segments is a workaround that doesn't give me much confidence. Perhaps there's something going on with my install. Now I'm getting frequent errors with subsequent crashes related to ReWireDLL error, and error processing the undo buffer. Frustration levels rising.

Subject:RE: Frequent Acid Pro Crashes

Reply by: rumun

Date:5/23/2015 3:52:15 AM

Personally I don't use the included NI plugins that came with Acid; they have always seemed quite buggy to me on multiple systems.

With regards to my original post about stability, I have found that projects which were crashing frequently (even during render) seem absolutely fine on Windows XP 32 bit. This definitely seems to be a Windows 8.1 64 bit / Acid Pro 7.0e 32 bit compatibility issue.

I would recommend trying a Windows XP install for Acid.

Subject:RE: Frequent Acid Pro Crashes

Reply by: Silamanagic

Date:7/21/2015 11:27:35 PM

I'm using a CLEAN install of Windows 7. My system specs are awesome as this is a new PC I built. Only programs installed are what came with the OS, Sony ACID 7.0e, and a few 3rd party VST plugins. ACID crashes every time I use it. I thought it might be related to my audio interface but the same instability issue is present with either Focusrite Scarlet 2i4, AND Presonus Firepod FP 10.

Projects seem to become corrupted after 4 or 5 crashes/Auto Saves. Things such as the chopper do not perform correctly. Scratchy pics and noises occur when moving the mouse around the timeline where one clip ends and another begins. Playback becomes delayed and sluggish.

Given this is basically a virgin PC what could possibly be causing this?

Subject:RE: Frequent Acid Pro Crashes

Reply by: mnickolas

Date:7/23/2015 10:28:31 AM

Video card or video driver? Maybe run some tests with the Microsoft provided driver instead of the manufacturer's driver. Or test with the standard VGA driver or even with a totally different video card.

Subject:RE: Frequent Acid Pro Crashes

Reply by: Silamanagic

Date:7/24/2015 11:17:17 PM

Good suggestion to explore the graphics side of things. Currently I'm not using a peripheral video card but rather the embedded graphics of my new motherboard. Somehow I doubt that's the issue but worth a look.

I may end up doing a full clean uninstall/reinstall of Acid.

I really hope I can get it running stable because I do like the capabilities of the software. I would hate to buy another DAW simply because Acid is unstable on modern systems.

I'm curious how stable Acid is on other peoples systems.

Subject:RE: Frequent Acid Pro Crashes

Reply by: Geoff_Wood

Date:7/25/2015 2:36:22 AM

Graphics driver is the most likely cause ! Especially your other noise problem.

geoff

Subject:RE: Frequent Acid Pro Crashes

Reply by: AnimalNation

Date:2/3/2016 9:15:47 PM

Any luck with this?

I'm having similiar crashes. My temporary solution is to transfer my project to my desktop i7 processor, then render from there. Alternatively, you can just open the project file (through a wifi network), on a more powerful computer, and as long as you have all the same software (Acid Pro + external FX and VSTs) you can render the files like that as well, without having to transfer over the entire project.

I'd love if there was another way though. In case I'm not around the studio, and need to render something on my laptop.
I don't know if it's an improper install on my laptop, or if it's the difference in computing power....