GRRRRR Crashes all over the place

All great suggestions..Thanks Guys! I'll try changing the ram. So it sounds like 2gb would be the best way to go. As for drivers, it's a new system so they were all recently updated. When I first started the project I didn't have any problems and I was on 2.58. As the song gets more involved and more effects are added, and the update to 3.01 is when this all started. I was getting some crashing in 2.58 but it seems to be worse in 3.01. That could also be related to adding more fx. It's most likely plug in related, I just need to locate the culprit and get rid of it. To bad there isn't some kind of utility that can monitor for plug-in issues and alert you to the one causing problems. Easier said than done I'm sure. Is there a list of known problem plug in that I can refer to or is that going to be different for each setup?

seeing reaperwave.dll means he isnt using asio right? And isnt ozone DX only ?

[QUOTE=pipelineaudio;327719]seeing reaperwave.dll means he isnt using asio right?QUOTE] that's wav input, i think. (?)

Is anything 'modern' DX only these days? Isn't DX about dead? Anyway, I was playing with Guru in v.3.01 last nite for the first time, and Reaper was hanging when I'd shut it down. I *think* it was maybe one of my midi controllers causing the hang with Guru, though I can't be sure...

as i understand it, without the /3gb switch, xp limits process address space to 2GB. if you use the /3gb switch, that lets each process address up to 3GB. (the 2GB point is pretty special, that's the largest possible signed 32 bit number - any pointer arithmetic that crosses that boundary can choke in weird ways. software that's built with this in mind will handle more with no problems, but it only takes one bad plugin to break everything) on the other hand, reaper tends to choke in weird ways (typically: just disappears) if you totally run out of RAM/address space. but you should be able to keep an eye on that. there are options to make reaper use less address space in the advanced settings somewhere if this is happening. edit: short verrsion. definitely try turning off /3gb. windows doesn't "take" any RAM for itself, it's more about address space (which includes swap space etc... it gets a bit hairy). edit 2: i really really wish i had an I7...

A little off topic but when I duplicate a track I always get a message that "The following effect plug-in could not be loaded" and the VST's on the new track are Red. I have to delete all the VST's and their settings and then open a new plugin and get everything setup again. Is it possible to duplicate a track and have all the same vst's copied over to the new one?

So I've gone back to version 2.58. Physically removed all the ram in my system so it only have 2GB worth, removed some plug-ins, cleaned up my system and still getting crashes. AppName: reaper.exe AppVer: 2.5.8.0 ModName: reaper_wave.dll ModVer: 0.0.0.0 Offset: 0000a2e8 What is Reaper_wave.dll - What is it's function or what does it relate to? Doing a search for reaper_wave.dll brings up multiple posts from other users also having trouble. One of the guys was only using reaper plug ins and still having trouble. We all have different sound cards, ram, processors, motherboards, video cards yet seen to have this one item in common "REAPER". Just playing the song will get to a point where this error will occur. Also if I zoon in or out I get this error. I really don't thinks it's a hardware based issue, but I'm still interested in if anyone else resolved this issue another way? p.s. The vocalist is coming over tomorrow to record, i relaly hope we can get through our session without trouble. If this is a vst related issue, then if I mute a track will that disable the vst's and fx on those tracks? or I guess putting the fx offline should also work? or does reaper still parse that info in the background.

One more post for the evening.. Does the attached screen help at all...Something about Version is not 0 1 or 2. Invalid magic in file..Output.. Where can I get valid magic for my file?

Time for a complete hardware and software list!! Please include rev #'s and/or service pack revision and such for all. Otherwise, I think your installation is foobar'd too much to try to troubleshoot one issue at a time. When you last installed your new system hardware components, did you do a complete system rebuild of the OS and software, or did you just migrate your new parts into your old OS and then add the new drivers? If you did a clean installation Did you create a clean installation image (ghost, etc.) of the clean install at any point? -mr moon

Same problem here