Reaper is done...?

Is there a life expectancy to Reaper? I have a new project. I have about 10 tracks and two FX tracks set up that some of the others are routed to. Everything is working fine for several hours. I render a stem track on track #1 to stereo. Reaper locks up. I figure, okay, its thinking. I'll just wait. 3 mins...10mins...I go watch TV, come back 30 mins later, its still locked up. I shut down my presonus preamp. Reaper comes to life long enough for me to click twice (FILE-SAVE). Locks up again. I shut the PC down holding the power button. Reboot. The PC won't boot completely. I shut it down. Wait 10 mins. Reboot. Fires up fine. Fire up Reaper. Locks up, can't load the default project i was just working on. I see its hung up on a WAV file. I browse, remove that WAV file to the desktop. It opens up. The WAV file is a different track than the one I rendered recently. I click on a track. Reaper locks up...again. What the heck is going on? Anyone have this happen? Any tips on what might be causing this?

I had a similar thing happen, but with a much more basic project. Two recorded MIDI files and VSTis for each (on separate tracks). I forget the exact point that it locked up, but I'm about 95% sure it was when I tried to do something with one of the two VSTis. After opening the project again twice, and it locking up both times, I could see that it was locking up when it was loading a particular VSTi. What I did was open the .RPP file in Windows notepad, and took out the code for whichever track the VSTi was on, and voila, it worked again. I managed to salvage the MIDI by copying it to another track (in editinf the .RPP file), but that shouldn't be a problem for you if you're using audio. I would say it's probably a plugin problem. Cheers, Pembo.

One of the first things I would do is run 'chkdsk', hard disk errors may cause this behavior. Info on chkdsk here: . You might also want to check your hard drive manufacturer's website, they usually supply *free* diagnostic tools. And as Sheppola suggested you may want to run a diagnostic on your RAM, see here: .

Well, I finally got it working on a different project. I'm going to avoid that project for the night. I'll check these tips in the am. Going to grab a beer. Thanks.

After re-seating the ram as Sheppola suggested and you still have the problem, go to download their iso image and run that bad boy. Even one error means faulty ram and time to buy some new sticks.