Skip to main content ↑ ↓
Topic: BSOD (Read 3754 times) previous topic - next topic

BSOD

I use NWC so much I can't remember with which update it started, but if I hit the stop button (F6) while no song is playing, it bluescreens me and noteworthy crashes. You might ask why I'd try to stop it while no song is playing - well, sometimes I hit stop just as it's reaching the end of playback. Anyone else have this problem? It seems like it would be an issue of what MIDI playback devices I have activated, but I still get the problem with only one activated, and none in use by other programs, as far as I can tell... Ideas? Suggestions?

Re: BSOD

Reply #1 –
This sounds like one of two things:

1 - You have a MIDI setup/driver problem; the driver crashes under the heavy load of receiving many note off events in fast succession.

Resolution: Check your manufacturer for the latest MIDI drivers. Also, if you caused this by updating your drivers, then go back to the driver version that was working.

2 - I have also seen this when a MIDI feedback loop is created, usually when one or more external MIDI boxes (such as a MIDI keyboard) are interconnected to the computer. Sometimes, in the setup process, a MIDI feedback loop is created where MIDI events sent by the computer out get echoed on its input port. If you also have the NWC MIDI echo feature enabled, this creates a feedback loop that can be haxardous to your computer's health.

Resolution: Avoid MIDI infinite loops.

Re: BSOD

Reply #2 –
Bob,
I had a similar problem when I upgraded my motherboard and went to an AMD K6-500. In my case, Noteworthy would play
for about 1 min. and then freeze on all notes. I did absolutely nothing to change the program before or after the upgrade. The solution was to reinstall Noteworthy. It sounds to me like a corrupted file somewhere. Anyway, by reinstalling you will assure yourself that there is nothing wrong with the Noteworthy. You'll also solve your problem of not knowing which upgrade you have. :)

Mark

Re: BSOD

Reply #3 –
This probably won't cure Bob's problem, but to address one of the issues pointed out by Noteworthy Support: you can easily avoid midi infinite loops and their attendant hazard to your computer's health by using Hubi's Midi Cable to patch your devices together. In addition to making dealing with multiple devices easy as pie, it also contains a "fuse" feature which prevents such feedback loops.

One place to get it is Hitsquad

Re: BSOD

Reply #4 –
When I accidentally hit F6 (stop playback) when I haven't first started a playback, I get an hourglass for about a second or two. I figure the program is just searching memory to try to find out what it's supposed to be stopping because the F6 works instantaneously if there is a playback going when you hit it. You probably have a similar problem, but are bluescreening for some reason instead of getting an hourglass.

I'm running Windows ME with a fairly large memory but a slower chip. The problem, such as it is, did not occur before I upgraded to 1.70 version 9.

Re: BSOD

Reply #5 –
David,
Hitting F6 when NWC is not playing performs a MIDI reset.
The hourglass displays to indicate the process is running. While this you may notice on the status bar (bottom line of NWC main window) that this action is reported : "Performing full reset on each port and channel..." :)
NWC doesn't look into its memory if it should stop something it's doing: I believe it "knows" it perfectly well because it was well enough designed, Thx to Eric.

BTW, the F6 key ("Stop command") is documented in the inline help as :
"This command is used to stop or cancel a currently playing score. It can be quickly activated from the keyboard using the F6 key.

If a score is not currently playing, all the open MIDI device ports will be reset. This is a good way to quiet or shut off stuck notes, should this ever happen."

NWCly yours,
Dominique
 

Re: BSOD

Reply #6 –
If you press F6 when not playing, NWC sends note off messages for every possible note on every possible MIDI channel. This can be the cause of a short delay.

If you have your port usage set to While Playing, an additional delay can occur while NWC opens the MIDI ports. The quick opening, using, and closing of the MIDI ports could also be the cause of some problems for poorly behaved MIDI drivers.