v 3 MIDI output stops, then crash

Reaper v.3 has crashed on me 3 times tonight. All three times when I was fiddling with MIDI. I never saw this with 2.5x. Several times tonight Reaper has stopped outputting MIDI, either in the middle of playing or with the MIDI editor open and me manually generating MIDI events. The remedy was to open the Options > MIDI Devices and right click one to open, then close the Options dialog, and MIDI worked again. Most of the times... But three times, and I think all of them with the MIDI editor open, when trying to remedy the MIDI out silence, Reaper crashes. It freezes and XP (DuX' audio optimized) puts up its "stopped responding" dialog. What I could find in the Event Viewer that could possibly relate to this is the following: Code:

The warning is related to the MIDIsport driver indeed. But the actual crash log(s) is(are) missing. Deleting C:\Documents and Settings\<username>\Application Data\REAPER\reaper-midihw.ini sometimes fixed issues with MIDI drivers in the past.

Steindork, Thanks for responding. I deleted the old reaper-midihw.ini, but the crash happened again. Same project. MIDI output stops, clicking in the upper right corner to get the Preferences dialog, Reaper freezes. Task Manager says "Not responding". Trying to close Reaper I get XP's "The program is not responding" message. This time, there are no warnings from the MIDIsport in the event viewer. And nothing but good-looking entries there. No crash dumps generated, even though I've set (and then restarted) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\CrashControl] to enable crash dumps and to write a small memory dump. Also, the MiniDumpDir key is set to %SYSTEMROOT%\MiniDump, but this dir does not exist (it would have been created, right? And yes I know %SYSTEMROOT% is C:\Windows). Something is rotten... I never saw this with 2.5x... Speaking of 2.5x, it may be relevant that this project was originally created in 2.57.

This thread is the same thing I think. This continues over there.