Crash/Lockup on clicking FX button 4.72

This is intermittent, works the vast majority of the time. Windows 7 64, Reaper 32 (4.7.2.0), Intel I7 Sometimes if I click the FX button on a track, the FX window will open up, and instead of automatically displaying the FX Browser (as I have set), it freezes the GUI, goes completely unresponsive (it keeps playing audio fine, and I've only had it happen while playing audio). I have to force close Reaper. When I open Reaper again (to the default empty project), strangely the FX Browser window pops up automatically. Only had this happen over the last week, so may be related to the 4.72 release. Had about 5 instances of it over the last few days. Unfortunately, since it doesn't crash, I don't get a crash log, I just get this : he program reaper.exe version 4.7.2.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: 89e0 Start Time: 01cfbc3dcd9c8f8d Termination Time: 19 Application Path: C:\Program Files (x86)\REAPER\reaper.exe Report Id: f1167e38-2832-11e4-9ff3-94de80a63b24 Which I assume is of no benefit at all :( These are all on fairly FX intensive projects (with around 100ish tracks), but nowhere near CPU or memory limits.

Not sure, will try doing that. It just happened again, and I'm going to leave it for a bit and see if it actually crashes instead of just the lockup, then I might have some useful crash information. (this one happened while stopped)

Haven't had a lockup since changing that setting. Looks like it might have done the trick (got another full day of tracking and mixing tomorrow, so will know for sure then). Hate having the audio glitch when I do it though, so I'll have to track down the offending plugin (I'm assuming that, given the name of the setting) and find a replacement. Thanks Jeffos!

I've had this problem as well. Click the fxlist in the mcp...poof! Thru trial & error, I've found that I MUST keep the FX Browser UNdocked to avoid this problem, however my config keeps reverting back to docked unexpectedly. Not sure why? Might be saved screenset settings, but I believe that I resaved em all with the FX browser UNdocked. The FX Browser has been docked in my config/setup for a long time now, but since 7.2 or so I've had these crashes. I'm going to now try the bypass audio setting and leave it set. Didn't help when I tried it before.

Not fixed 

The bypass audio setting did not fix this for me. I can re-create the problem at will now. Bypass audio while opening is ON. Start a new project, make sure FX browser is UNdocked. Add a track. Add an FX via an mcp fxlist click. FX browser pops up, all OK. Select etc... Dock the FX browser, hide dock. Click mcp fxlist...poof! This xml error file was generated. Does anyone check this type of thing out? Any place I can find a core dump to send?

Thanx Ollie, I guess its in the right place then.

Please read the bit about Event Viewer and crash logs in that thread.