See screenshots:   one track selected, controller 11 shows at bottom, correctly.   Then screenshot 2, the controller 11 for the selected track has disappeared.   The ONLY difference is that i clicked one time on the scroll bar arrow at the bottom to shift the view forward a few measures.   
 
 

Can you provide steps to reproduce? Controller value persists here when scrolling.
 
Also, does the controller value go to zero, or just the graphic representation? 
 
What happens if you close and re-open the project, and does this happen with all projects? You need to identify whether this is a reproducible bug or a random glitch; two screen shots doesn't provide enough data to troubleshoot.
 
 

I feel sure that it is because of the mis-mangle between track and channel; I'll try to reduce it to a reproducible setup.    The main point is, it happens, all the damn time, in my work.     I imagine that there is a controller 11 in a different track, somewhere in the bars shown on the second screen.    Again, a) it happens constantly and b) the ONLY thing I did, and it was reproducible in that set up, over and over, was click the little arrow key once. 
 

It still would be helpful to know if it's solely a graphic issue and the controller value itself persists, or whether the graphic representation accurately reflects the controller value. Those would be different problems and would require that Cakewalk look in different places to fix it.
 
So are you saying this happens all the time in multiple projects, or all the time in the same project? The reason I'm being persistent about this is you're always complaining about controller issues, and it could be that one simple bug is cascading into multiple manifestations...so being able to identify a bug and reproduce it could be the key to fixing all the issues you experience.
 
The other possibility is a graphics card interaction issue, which is especially a possibility in multiple monitor setups (I assume they're both set to the same resolution). As you know, many issues can happen when there are graphics card driver issues. I went through all kinds of hell with my ATI Radeon (which I really wanted to use because it doesn't have a fan) until AMD came up with a new driver. To add insult to injury, the driver could not be found through AMD's "automated" driver selection process. It took a google search to uncover that there was a new driver. I think nVidia is better in that respect.
 
The bug may not be with SONAR per se, but with an interaction between the system and SONAR. That would explain why so far, I can't reproduce it.
 
The 780 is a screaming graphics card for games, might be worth checking for new drivers just in case. Probably won't hurt, could help.

I rebooted, downloaded Foxboro, loaded same project, went back to the same screens, and the same thing happens.   Tracking down now what other controllers might be in other tracks in the viewable range. ...
 
And the answer is, NONE.  The track where the controller disappears is the only one set at channel 13 in the entire project.  There is a controller 11 event at bar 3, and one at bar 125, and nothing in between.  If I zoom out, the controller continues to show correctly until the entire length of the project is in the window, but when I zoom back in, the problem reappears.       Could this be something to do with 'controller look-back', and might there be a secret limit to how long look-back is set for?
 
As part of this research, just noticed another thing:  there are two places to set "Select Controllers Along With Notes", and they are not independent, one changes the other.    Looks like a bad idea.   Track view, under "MIDI" and PR view, under "Controllers". 

Update: it appears that the controller value itself is changing!   Originally I thought it was a graphics thing only, but I just did some experimenting, and it appears that the controller value, last set a minute-plus earlier in the project, is lost, not found by controller-look back and not found for display purposes. 
 

Just added a midi PAN control, hard right, value 127 at bar 1, no other pan (cc10) used at all.    Shifted ahead 100 bars, started playback, and the pan was forgotten.    Grrrrrrrrrrrrr.     Basic basic stuff.   Then moved here and there in the file, sometimes the pan was hard right, sometimes reset to 0.   This medium sized project has around 15000 events total, not sure if that's a factor. 
 
Preferences, Project, Midi:  Patch/controller searchback before play starts set yes, zero controllers when play stops set no.
 

Could some hardware device be broadcasting cc data and being recorded into the track, producing unexpected results? (wild thought but maybe...)

I don't do hardware!    Nothing connected at all.   No effects, three instances of Kontakt 64bit, and a bunch of midi, that's it.
 
edit, correction: there are two kinds of reverb:  VirtualSoundStage 2 and SIR2.  

williamcopper
Preferences, Project, Midi:  Patch/controller searchback before play starts set yes, zero controllers when play stops set no.

I wonder if that's the problem. I always set "zero controllers when play stops" to yes (checked) when searchback is enabled. Then it will start from a known, default setting when searching back.
 
Also under "MIDI Playback and Recording," you might not want "Always Echo Current MIDI Track" checked. You could be depositing data where you don't want it without knowing it.