Sustain Pedal Midi CC 64 at low value not 0 -- crashes?

I rarely have an actual sonar crash, and I rarely use midi CC 64 (sustain pedal).    Generally even in a heavily loaded project the Performance module shows low values for CPU activitiy.  
 
But recently in a very small project I've been having some lock-ups in a project that uses CC 64.    Is it possible that 'drawing' the off value (in PRV controller pain) to a low number, but not 0, can cause crashes or 100% cpu lockup?    

It might be something else.    The lockups have happened during long work sessions with a large number of starts, stops, changes of Now times.    But only in (I believe --- like any unexpected problem I didn't keep track until it happened) small projects (chorus and piano, all midi) with sustain pedal for three piano tracks.  
 
Always on 'play', not during entering the values.   And not at the beginning of play necessarily.    Also, painfully, caused audio noise, my least favorite thing for my tired ears.   Also I very rarely change anything while a project is playing .. exception might be some tempo drawing, but this particular project had a stable tempo that I did not change. 

I use CC64 extensively, usually with all events being non-zero.
 
Can't recall a single problem with this

I accidentally left in a CC64= 3 recently; got the freeze again.     I'm getting more and more sure it's something to do with the audio engine trying to sustain notes according to a CC64 value. 
 
This happens after an hour or so of work, with many starts and stops, so it is not the kind of thing that happens immediately.   The CPU at 100% can not be stopped -- you have to exit Sonar.  
 
Possible additional factors:  3 midi tracks going to 3 different Kontakt channels, CC64 values different in the three tracks, but the 3 Kontakt channels all going to the same single output track.    Midi lookback preference enabled; zero controllers on stop disabled.
 
The latest freeze happened not during playback, but when I dragged a note (in the track with a CC64 = 3) to a new pitch in the PRV.  (edit)  Opening the same project, dragging the same pitch -- I can hear that the sustain pedal effect is ON, though it should not be.    Is there any kind of lookback during the sounding of a note during note entry or modification?   
 

I actually had something similar last night: 2 lock ups / crashes when recording piano as MIDI track while working the sustain pedal heavily.
 
Have not seen that before, but it happend twice on the same project within a short time. So I take back what I said earlier - the crashes were definitely while recording MIDI @ low ASIO buffer settings and high audio track count / relatively high load (but that's what I have always done before).

As a test I eliminated all CC64 control messages except one -- left that one at value 10.    Unchecked "reset controllers to Zero".    With a few stops and starts, I could see the CPU begin to rise in the Performance Module.   Changed it to value 0, CPU went back to effectively 0.    

Maybe it is the Kontakt instrument.   I had thought it was a standard that CC64 less than 63 is equivalent to 0.
 
From another forum: 
"Cubase has a MIDI CC mapper/filter built in.

Are you using a pedal or a switch? CC64 should only have 2 values - ≤63 off, ≥64 on, which is a switch's job."