It usually happens only after working for a while.

Sir William & davec69
Do you guys have the taskbar in Bottom or in sides?

sonarman1
It usually happens only after working for a while.

Sir William & davec69
Do you guys have the taskbar in Bottom or in sides?

Hi sonarman
 
Mine is at the bottom on my large monitor, not my laptop screen. I spread Sonar across the two screens.

I see. So It should be happening irrespective to the position of taskbar. Just wondering why not everyone has this issue. 
Some specific setting is the cause or something else? 

I have my win10 updated so thats not the prob. 

I have had this problem for some time and only with Sonar. As a matter of interest, what display adapter do you use? I use Intel HD Graphics 4600 (i.e on-CPU for an i7) and I have wondered whether it's connected to that.
 

Intel HD 4400. But I dont suppose its connected to that. Tested and reproduced the same problem in my old pc which has Intel G33/G31 chipsets. 

Casting back to my days as a programmer, given that:
1) this only happens after working for a while,
2) restarting Explorer sorts it out, and
3) it's only happening with Sonar Platinum,
this sounds like one of Sonar's buffers is running off the end of its assigned memory space and overwriting in-RAM settings for Explorer. What's really odd is that an error should be coming up during the compile phase when Sonar is being built. If it isn't, then it's a problem with Microsoft's development tools.

 If that's the case hope Bakers report this to Microsoft and sort it. This really is a hindrance to pleasant workflow.