Hi
Not 100% sure what is happening for you, but SyncBackFree (like SE & Pro) contains no low-level code, and does not address hardware (or drivers) directly, only via Windows API calls. We thus have no direct involvement with 'interrupts', so it would seem the internal/low-level result of some legitimate API call is upsetting something on your system, which then stays that way ('upset') until rebooted. As there are (apparently) no errors returned to our software, it's not something we could debug, sorry. You probably need to try alternative software.
Not 100% sure what is happening for you, but SyncBackFree (like SE & Pro) contains no low-level code, and does not address hardware (or drivers) directly, only via Windows API calls. We thus have no direct involvement with 'interrupts', so it would seem the internal/low-level result of some legitimate API call is upsetting something on your system, which then stays that way ('upset') until rebooted. As there are (apparently) no errors returned to our software, it's not something we could debug, sorry. You probably need to try alternative software.