Hmm... maybe it'll be one of those things that magically disappears next time I boot up. Thanks for checking it out.
However the fact you get a click on ALL your PC modules is a little worrisome. I've NEVER had that unless I was totally maxing out my resources... and that would usually lead to a drop out or some other nastiness. I'm assuming you've reported this. Noise when a/b'ing is REALLY bad for objective listening which is why I find this CL problem perplexing. It is a distraction to the ears and can lead to misguided mixing decisions... IMO anyway.
The following is a long story but you may find it interesting, Alex. The tl;dr version is after updating Windows but BEFORE installing the X3e patch I started getting dropouts and it turned out something reset my hard drives read/write buffers to the default 256.
Long version....
Here's another weird thing that happened that day. This project has gotten rather large and at a couple points I had to up my read/write buffers to avoid persistent dropouts. As I said that day I updated Windows (it had been about a year) as well as X3.
I had made a restore point before starting all this and wanted to test the effects of these updates as I did them. After I did the Windows updates and started trying to play back my project BOOM... dropout after a few seconds. Uh oh. I started playback again and it kept playing normally so I started doing stuff I know can lead to dropouts like jumping the Now Time during playback to another position, riding PC module controls hard and fast, dragging things around really erratically, etc... I was definitely getting a lot of dropouts, especially when jumping the Now Time around (which doesn't happen if I have my buffers high enough).
Naturally I figured it had something to do with the Windows updates and that maybe there was a conflict with X3c and the new Windows patches and perhaps updated to X3e would fix it so I installed the patch. After testing it the same way I did before I was still getting the dropouts (but admittedly it was a little harder to force the dropouts so the patch did seem to make things a little better).
So I tossed the Performance Module into the Control Bar and started my little tests again and sure enough the disk icon flashed red before one of the dropouts (took a couple tries because sometimes the dropouts occur before the Perf Mod actually can register a disk overload so anyone trying to find out whether your hard drive buffers are too low keep that in mind... do the tests for a while even if the first few times it stays yellow).
I opened Preferences and checked my buffers and they had been reset to 256 (IIRC they had been double that and at one point before I cleaned up the project and archived a ton of things I actually had them over 1000).
Weird... at first I figured the X3e patch had reset them but that doesn't make any sense because the dropouts started occurring BEFORE I had implemented the patch but AFTER I had done the Windows updates. I don't understand how that is possible and I wish I had checked my buffers before installing X3e to see if they had indeed been reset by the Win updates but there you have it.
I turned the read/write settings up to 512 and everything worked like they did before. Freaky stuff.