Zargg
You could try disconnecting it and see if it makes a difference.
Are you on Win 10, by the way?
I had to tweak some stuff after the latest update, incl HD Audio, and Nvidia Audio device.

Zargg
Do explain, please!  I do not have issues with my Console 1 (one of the best things I ever bought!!!), but I am constantly getting audio dropouts since the Win 10 update.  

space_cowboy

Zargg
You could try disconnecting it and see if it makes a difference.
Are you on Win 10, by the way?
I had to tweak some stuff after the latest update, incl HD Audio, and Nvidia Audio device.

Zargg
Do explain, please!  I do not have issues with my Console 1 (one of the best things I ever bought!!!), but I am constantly getting audio dropouts since the Win 10 update.  

I just disabled and uninstalled HD Audio, and Nvidia Audio device in Device Manager.
I did some other minor tweaks I can't remember right now (not in my studio now). Perhaps screensaver and some power management.
All the best.

It strikes again!!! I lost my whole night's work tonight. Right after it screwed up and zeroed out all my work, I closed SONAR and reopened. Upon reopening the Presonus FaderPort went crazy with the fader moving up and down rapidly and freezing the startup process. I had to unplug the USB from the FaderPort, then SONAR opened but all my work was still lost.
 
I am most certain that this is happening because of the FaderPort now. I don't know if there is a solution. I love the FaderPort and it is such a part of my workflow, but I have to leave it unplugged if I am mixing with Console 1 apparently because I will lose work if I don't. Bummer... 
 
Does this happen with the Behringer X-Touch or the FaderPort 8? I am afraid to use anything Presonus now so I would probably not look at the FaderPort 8. I will try to adapt a new workflow without a control surface for now.

Are you using Faderport with the original (Presonus) plug-in or with AZ Controller?
Any plug-in, including Control Surface one, can technically corrupt Sonar memory.
You can try the plug-in you do not use at the moment as a check.
 
 
The only other possibility for the effect you observer which comes in my mind is something horribly wrong inside USB host/device/driver/Sonar MIDI ports chain and what should be sent to / received from Console mixed with Faderport communications.
a) Recent Sonar versions definitively have some bug in MIDI<->surfaces routing. In/Out ports are periodically messed. That can explain "chaotic fader movement". You can try to remove MIDI related .INI files and re-insert MIDI settings. Also re-build surfaces list. Check for periodic Connect/Disconnect for (any!) MIDI devices in Windows, that normally trigger the bug.
b) try to use another USB port for Console or Faderport, I mean try to use them on different physical USB chains inside computer.

I was just about to ask you to try Alexey's AzController, when the man himself chimes in 

I don't know if this is helpful but maybe worth to check:

It's not necessary to use Console 1 as a MIDI device in SONAR.

Mine is unchecked (in Preferences > MIDI > Devices) and Console 1 works without the problems you described along with other MIDI control surfaces including X-Touch Compact (using AZ Controller).

Only a shot in the dark...

Best,
Klaus
 

Klaus
I don't know if this is helpful but maybe worth to check:

It's not necessary to use Console 1 as a MIDI device in SONAR.

Mine is unchecked (in Preferences > MIDI > Devices) and Console 1 works without the problems you described along with other MIDI control surfaces including X-Touch Compact (using AZ Controller).

Only a shot in the dark...

Best,
Klaus
 

This I didn't know. Thanks!
I'll remove it from MIDI devices, if it doesn't need to be there.
All the best.