GRRRRR Crashes all over the place

V3.01 I can't get any work done.. SUPER frustrating. I've got two months into a project and now all I get is crashes. I get a crash if I try to render in realtime, before it crashes I get all kinds of audio crackling during the realtime render. When I render in fast mode (non realtime) I get vocal parts that drop out in the mix. This was stuff that was working fine before. When I try to play the song reaper will crash. So I'm at a point where I cannot do much of anything. Was able to do most things using 2.58 with some crashes here and there. Thought I would update "Thinking" it would fix some fo the crashes.. I was wrong. I'm partly venting and also asking for help. What can I do to figure out what is causing the crashes? I cannot get any work done if this keeps happening but I have too much time invested in the project to give up now. Is there a list of common vst plug-ins known to cause issues? Can I go back to a previous version of reaper and which previous version was most stable? It's not the most recent. Would it help to get the crash appcompat.txt file and post that? Thanks in advance for any help

You can certainly downgrade to a version that you find to be more stable, however if you could post specific problems that would be a great help -- particularly any crash addresses/module/versions you see. -Justin

Looking in the Event Viewer I was able to locate some info..Maybe this helps? 1. Faulting application reaper.exe, version 3.0.0.1, faulting module reaper.exe, version 3.0.0.1, fault address 0x002d02f9. 2. Faulting application reaper.exe, version 3.0.0.1, faulting module reaper.exe, version 3.0.0.1, fault address 0x003069af. 3. Hanging application reaper.exe, version 3.0.0.1, hang module hungapp, version 0.0.0.0, hang address 0x00000000. 4. One of the times I tried to render the song in realtime I got this crash which was Dr. Watson: Faulting application drwtsn32.exe, version 5.1.2600.0, faulting module dbghelp.dll, version 5.1.2600.5512, fault address 0x0001295d. These were crashes from V3.0 5. Faulting application reaper.exe, version 3.0.0.0, faulting module reaper_wave.dll, version 0.0.0.0, fault address 0x0000db45. 6. Faulting application reaper.exe, version 3.0.0.0, faulting module reaper.exe, version 3.0.0.0, fault address 0x0016bb35. Looks like I had a couple of crashes related to Waves 5.0 and Nexus.dll but there are only a couple of those. Waves 5.0 I'm not using much of in the song but I have noticed that anytime I try to load a waves FX I have problems. P.s. Using Windows XP SP3 with all the latest updates.

And these are all just randomly occurring? Anything you can do to get them to repeat?

I would certainly go back to the version that you've been using successfully - you can reinstall it over your v3.01 installation (or alongside it). But backup your projects and data first. Your projects should be OK unless you've used the new features in v3 and saved in v3. In v2.xx on opening a v3 project you might get a pop-up window reporting that some items could not be understood.

Most of them appear to be random, which is even more frustrating. Appears to be reaper is not very stable as I didn't have this many issues before. The latest one below I can repro everytime. All I have to do is play the song for a couple of measures, then stop it. Then click on the Izotope Ozone 4 plug in to try and view it and i get the following crash: Runtime Error! Program: C:Program Files\Reaper\reaper.exe Abnormal program termination In the event viewer the following error: Faulting application reaper.exe, version 3.0.0.1, faulting module reaper.exe, version 3.0.0.1, fault address 0x00307926.

One more thought. Are there some settings in preferences that are common to cause issues. With so many selections it's possible I have some checked that are causing the issues? For example, If I check to use anticipative fx processing, I have more problems with crashing even thought this option is touted as "superior multiprocessing and lower latencies" and seems like a good thing to check. Another one is if I turn off Synchronous Fx multiprocessing I get garbled audio and really slow playing audio.

how come you have 6gb of ram on a 32bit xp system? shouldn't you move to a 64bit OS so you can actually use most of that? maybe that'll sort out your problem?

This is by far the most frustrating kind of crash, for users and for developers. Because it only happens for a few users, we infer that it must be specific to user settings, hardware, plugins, or habits. The crash log offsets are very useful, thank you for reporting those, and please anyone having a crash, if you can record the faulting module and offset, please post it. Any sort of recipe for repeating the crash is really what we need, or ideally posting a project. It may be that the problem is with a specific plugin or plugins (either the plugin is buggy, or Reaper is calling the plugin in a buggy way). If there is any way to narrow the problem down to projects with specific plugins, that would also be helpful.

I had a similar issue on a large project I was working on last week, constant random crashes, especially when changing parameters in ReaDelay as well as zooming in/out in TCP and other GUI type changes. It was very frustrating at the time. I have since removed all 3rd party plugs and made a few other preferences changes and the issue "may" be gone now. However, during the issue I was able to capture a complete memory dump using ADPlus -crash -pn reaper.exe. I looked at these in the debugger but was unable to narrow it down to the specific issue. I am happy to provide the dump files if I still have them but the full set is going to be 4+ GB or if you tell me what you need I'll pull it back up in windbg and extract the info. Regards- Karbo