Actually the crash sequence doesn't produce an entry in the MB error log, unfortunately. Instead, you get a Windows "Program Not Responding" message:
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: MusicBee.exe
Application Version: 3.3.7011.33478
Application Timestamp: 5c894de6
Hang Signature: bb13
Hang Type: 4
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: bb1339ed19f0961c98e0ff516ad1cc8a
Additional Hang Signature 2: f9f7
Additional Hang Signature 3: f9f725122ec4d4f052ead1320d7ca78f
Additional Hang Signature 4: f095
Additional Hang Signature 5: f095ea1431772cece13db4b56e132bf5
Additional Hang Signature 6: 06cb
Additional Hang Signature 7: 06cba739a016d32254006ebbc35e5469
The sequence of events is thus:
1. Open MB with the CSA loaded and its window displayed.
2. Right-click in the CSA window; instead of then displaying a Properties/Profiles/Close/About context menu from the plugin, part of the spectrum (if playing) will freeze and nothing appears. Your song (if playing) will continue to play--if you didn't have anything playing, nothing appears either.
3. Then trying to perform any kind of activity in MB (navigate to another tab, start a song, etc.) will totally freeze it. Attempting to continue will result in the Windows error and offer to close the program.
If you don't try to pull up that right-click menu, the plugin functions (shows a spectrum) problem free, crash free every time throughout any MB navigation. Users must therefore make their changes manually to the plugin's actual ini files (yes there are TWO of 'em--"vis_classic.ini" in the Plugins folder and "Current_Settings.ini" in the vis_classic subfolder within Plugins).
I hope I haven't scared you off