https://bugs.winehq.org/show_bug.cgi?id=52131
--- Comment #29 from Eric eric.wheez@gmail.com --- Thank you so much for reading all of this. You've already done so much work, I really appreciate it. Apologies for the deluge of info - I kept thinking I had gotten as far as I could get on my own but then kept thinking up different angles to look at the crash from. I think my first and last posts here are a decent summary of the info.
I do believe that the SEH exception in .NET / RMS Express on Windows is normal behavior caused by whenever dvoa.dll is given a small-value frequency to calculate and tries to tell users that it can't calculate anything.
Thanks for the insight into this too - that makes more sense. The good news is the crash is able to be worked around now that we know where it's coming from. The typo in the RMS Express database was also fixed (though another database typo in the future is always possible).