Suddenly Reaper is crashing constantly

monstaar · 09-12-2017, 12:53 AM

Been using Reaper for about 2 months now. NO crashes until today.
Was trying to record audio on a project with about 7 tracks of audio (my system is very capable of this. I have projects with 100+ tracks running fine).
Suddenly, Reaper just started crashing.
Some of the errors said Addictive Drums problem and some said the ntdll.dll was the problem. I've posted only three of the event logs but there are more.
To resolve this, I have reinstalled (not a clean install) Windows and reinstalled Reaper with no effect. It is still crashing.

I'll post my system specs then a few error reports below:
Intel i7-4790 @ 3.60Ghz - 16 GB RAM - 64 bit processor - Win 8.1

9/11/2017 9:07:20 PM
Faulting application name: reaper.exe, version: 5.4.0.0, time stamp: 0x58d45081
Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x530895af
Exception code: 0xc0000008
Fault offset: 0x00000000000f4030
Faulting process id: 0xa0
Faulting application start time: 0x01d32b6adf7f554c
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 1b74f989-975f-11e7-8251-1c872ccb7619
Faulting package full name:
Faulting package-relative application ID:

9/11/2017 9:17:52 PM
Faulting application name: REAPER.exe, version: 5.4.0.0, time stamp: 0x58d45081
Faulting module name: Addictive Drums 2.dll, version: 2.1.6.0, time stamp: 0x584ab890
Exception code: 0x80000004
Fault offset: 0x00000000002dd432
Faulting process id: 0x13ec
Faulting application start time: 0x01d32b6ce96ed449
Faulting application path: C:\Program Files\REAPER (x64)\REAPER.exe
Faulting module path: C:\Program Files\Cakewalk\VstPlugins\Addictive Drums 2.dll
Report Id: 94308c94-9760-11e7-8278-1c872ccb7619
Faulting package full name:
Faulting package-relative application ID:

9/11/2017 9:47:42 PM
REAPER.exe
5.4.0.0
58d45081
ntdll.dll
6.3.9600.17031
530895af
c0000008
00000000000f4030
86c
01d32b6f90bda45b
C:\Program Files\REAPER (x64)\REAPER.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
beb5f679-9764-11e7-8278-1c872ccb7619

Any thoughts?

ivansc · 09-13-2017, 01:53 PM

Why post the same thing in 2 separate threads a day apart?

Frankly it would be best if you continue this in the other thread & also give us a little more to go on.
I agree it does seem like a naught plug crashing the bridge though. Try taking all thee plugins in the offending project offline and then assuming Reapr no longer crashes put them back one by one till Reapr DOES crash.

Oh and since THIS crash report points at Addictive Drums as the culprit, you might want to try re-running the Installer/udater supplied by XLN for their VSTis.

srdmusic · 09-17-2017, 10:25 AM

A while ago I had a problem with permissions on a VST folder.

Try to install all your VST 2's in the parent folder of your system drive. For example: C://VST 2/Cakewalk/Addictive Drums.vst

VST3's should always be installed in the common files folder located in program files.

Then make sure that the folder VST2 and all the subfolders get full control permissions.

If you install into the program folder/cakewalk or steinberg/vst then sometimes the program files folder does not get full permissions or at least it has more potential to get screwed up.

I know you already know this but, if you got a crash with addictive drums then install the latest version. If the latest version is crashing, go back a version. If the manufacturer will not fix the bug.... stop using that plugin. There are plenty of alternatives out there for every plugin and it's not worth losing recording time over someones buggy plugin coding.

If you absolutely must use that plugin and can not get around it, Reaper has a 'buggy plugin' safety mode that can be activated on a plugin by plugin basis.