Reaper 4.71/64 Reaper Host32.exe crashed

[mtotton]

I have no reliable way to recreate this, but nearly everytime I open or close a project I get this message (from Soluto). Often Reaper continues without problems, sometimes a plugin loses its interface, and sometimes I have to restart Reaper. It has only started in the latest release 4.71. The plugin most affected appears to be BFD 3.

Intel i7 4770k
ASUS Z87-A mobo
16GB memory
SSD system disk
7TB storage
Win 8.1 64b

[mtotton]

I also get the message when I close Reaper. On one accasion I opened Task Manager to see what was going on, and even after I had closed Reaper and Host32.exe had crashed, there were still about 4-6 (i didn't count) instances of Reaper Host32.exe running in background.

[Ollie]

Originally Posted by mtotton

I get this message (from Soluto).

What message? Please read http://forum.cockos.com/showthread.php?t=36653 about crashes and crash logs.

[mtotton]

Reaper 4.71/64 Reaper Host32.exe crashed

It's the title of the thread :-). I did read the link that's why I put the error message up front.
I have additionally found two instances of Reaper Host32.exe running in background over an hour after exiting Reaper

[ovnis]

I have the same problem (with the same message)...

All my x86 plugs doesn't work on my reaper x64 when reaper is launched from task bar (windows 8.1 x64).

To solve the problem, i have given admin's rights to my reaper's link.

[mtotton]

Originally Posted by ovnis

I have the same problem (with the same message)...

All my x86 plugs doesn't work on my reaper x64 when reaper is launched from task bar (windows 8.1 x64).

To solve the problem, i have given admin's rights to my reaper's link.

Thanks for the input! I shall give it a try and let you know.

[mtotton]

OK, setting up a link with admin privileges seems to have fixed the problem. However, it IS still a problem, that shouldn't happen. I did get a different error message on startup, but it only happened once and I didn't copy it, so I will wait and see if it turns up again.

Thanks for the help

[karbomusic]

Originally Posted by mtotton

OK, setting up a link with admin privileges seems to have fixed the problem. However, it IS still a problem, that shouldn't happen.

You are absolutely correct and have just identified a flaw in the VST. You could reinstall the VST so that wherever it accesses its own files/settings is in a 100% writeable and unprotected location. Chances are it is trying to write to a protected location which throws and error which isn't handled and the resulting crash.

Having to run Reaper as admin is almost always a workaround to someone else's coding oversight.