As I had indicated to you in response to your private message, even if no other applications than Sonar are running, WINDOWS could still grab exclusive control of your Edirol audio interface, IF Windows is set to use the Edirol audio interface as the Default Audio Device.
In simple terms, generally speaking, the ASIO design specs are that only a single application can have control/access to an audio device, using ASIO drivers. SOOOO, this means that if both Sonar and Windows are set to use ASIO drivers of the audio interface, there is an inherent conflict potential that way.
I believe it probable that you have both Windows and Sonar set to use ASIO of your interface.
You can click on the little speaker icon in your system tray (bottom right corner of your screen), and Windows will display whatever is the currently set default audio device for Windows to use. IF you have this set to your Edirol audio interface, then I recommend you change the Windows Default Audio Device to use your Realtek drivers for Windows, and then leave Sonar to continue to use the Edirol audio interface with a driver mode of ASIO.
Please try going into Control Panel and changing the Windows Default Audio Device to be the Realtek on-board sound chip in your system, and then see if that fixes Sonar. Let's start with this and then we can figure out how to also deal with hearing your Windows sounds outside of Sonar AFTER fixing Sonar first.
Bob Bone