Reaper Crashes when closing VST GUI

[Glubber]

If I load Peavey Revalver MkIII onto a track, and then close the GUI for Revalver by clicking the 'x', Reaper consistently crashes.

Faulting application reaper.exe, version 3.2.0.0, faulting module ntdll.dll, version 5.1.2600.3180, fault address 0x00028bed.
The previous 3 crashes show the same data.

WinXP sp3, 32bit
4gbRam,
Emu1212m

[Ollie]

Sorry to hear that but do you have some info what exactly crashes there (crashing module + fault offset)? Create a fresh crash and note the informations when you click the "..details.." button on the crash message or check Event Viewer:

Originally Posted by That other thread

[XP]
Go 'Start Menu->Run' and type EVENTVWR <Enter>. In Event Viewer, open the 'Applications' branch and look for the latest "Error" entries.

Jotting down the time of the crash or creating a fresh crash may help you finding the right error entry. The most important informations there are the faulting module and the fault offset. Post them.

[Glubber]

Currently when I initiate this crash, it drops immediately to the desktop with no error window, and no log. Here's one from yesterday.

Faulting application reaper.exe, version 3.2.0.0, faulting module ntdll.dll, version 5.1.2600.3180, fault address 0x00028bed.
The previous 3 crashes show the same data.

Hopefully this is more helpful

I also discovered that if no preset is loaded into Revalver, it closes properly.

[Ollie]

Hmm, alas this doesn't point clearly to something. My suspicion is that another plugin is involved in that.

- Does that happen in an empty project with Revalver as the only plugin?

If it does,
- Have you set the marked two checkboxes in the VST preferences in Reaper like this?



- If yes, what happens if you uncheck them?

[Glubber]

I tried the check boxes, no change.
And I tried a completely empty project with just one track and Revalver, same crash.
Good ideas, but Reaper dies ungracefully.

[Mercado_Negro]

What Revalver version are you using? This only happens with older versions afaik (I do not own it but it used to happen when I demoed it about 2 years ago). This was fixed... it was a 'copy protection' issue, Peavey said. Try to update to latest version if you haven't done so