[Joe Ross]

Rather the doing a full re-image of the cRIO, try going to the imaging tool and turning on the no-app switch and then reboot the cRIO, reload your code, and then go back the imaging tool and turn off the no-app switch. Unless the cRIO image is actually getting corrupted (not likely), this is a faster way to get no code running on the cRIO. The most common reason for deployment errors like this is the code already running on the cRIO.

To get to the root cause of the problem, what is the cRIO CPU usage and RAM usage when running. These are shown in the Driver Station charts tab. Swamping the CPU or using too much ram may interfere with the deploy process.