I don't think so, because a debug output trace record has no owner.

If the rogue traces exhibit some patterns, you can filter them out using an open source tool similar to DebugView I wrote for this kind of problem: TraceSpy, but in this case, you'll need to visualize the traces outside of Visual Studio. It won't change the OutputWindow behavior.