There have been clear pointers in this thread that should allow the OP to resolve this issue.
I suggest the OP reads through the thread again and follow advice given. Sonar does not come with this generic driver.
 
1) Update the existing drivers and firmware. Rule that out first.
2) Assuming problem still exists afterwards identify what the generic driver is, and identify which app it lives with.
3) Remove the driver by uninstalling or via manual method. Maybe you could even just disable it. Further info on what to do here within this thread...
 
It's not like issues like this have not been experienced before.

Ta.

CakeAlexS
It's not like issues like this have not been experienced before.

i agree with what you said but this is a misleading link

There are similar situations and scenarios here if you scan through the results. The link closely associates itself to points (2) and (3) of my post which wasn't quoted. Many of the results are extremely relevant. Again it's not a Sonar specific issue.

lawp

CakeAlexS
It's not like issues like this have not been experienced before.

i agree with what you said but this is a misleading link

Actually, it seems clear (from the posts in the link) that "Generic ASIO driver" is installed with Steinberg hardware/software.
 

The first hit is asio4all

If I was going to be that specific I would have linked directly to it. Point (2). Plenty of posts to read through (incidently I have). I do not have the OPs machine in front of me. Ta

mazing

not exactly trying to be a smart azz but it sounds to me that you're more involved with tweaking software than making music.  I usually run Sonar using the ASIO drivers with very high latency (like 1024)- and I have a very powerful PC (i7 with 16 gigs of RAM).  I've found no need to monitor with plugins but I guess everyone's mileage varies.  However, I DO make a living with this software so results beat logic.