I got a workaround here. It seems like closing all the windows resets something in MS' code and fix the z-order problem until the next resolution change. It hasn't been tested thoroughly but worked for me everytime I tried. It's not an ideal solution but it's still better that rebooting. [edit] well...actualy not everytime [/edit]
After some other testing, i came to the conclution that 'always on top' state acts exactly the other way it should on alpha frames. Normal frames are drawn on top of always on top frames. This is quite inefficient using CursorXP because cursor are drawn below the frame.
This problem also happens with nvidia drivers, so it mustn't driver-related. I have a GeForce 6800 and this problem come after playing games, even if I play at the same resolution of my desktop. I suppose the games might just call a resolution change anyway. Also, the problem is more significant when the window is set to 'always on top'. In this case, the frames are always below normal windows' frame. Hope that helps...
Stardock Forums