Another update on Nvidia's noise filtering software - now called Nvidia Broadcast, I believe officially supported, replacing the experimental Nvidia RTX Voice.
I continue to love it.
But... (you know that a but was coming):
I recently did a warranty replacement of my Surface Book 3. The old SB3 ran Nvidia Broadcast without the fan coming on - but over time its touchscreen, keyboard, and trackpad all failed. I blame the infamous SurfBook hinge. I was able to use it for a few months (!) essentially as something like a Mac Mini with display, but made sure to replace it before the warranty expired. The warranty replacement - exactly the same specs - cannot run Nvidia Broadcast, even on the lowest noise cancellation settings, without the fan going into hyperdrive. Same OS, etc.
Having worked at both Intel and Nvidia, I am aware that there is considerable variation in power efficiency and heat production even between chips with the same specs. Sometimes even in the same wafer.
Nevertheless, the fan overdrive is so annoying that I have stopped using Nvidia Broadcast noise cancellation.
I have some hope that when I return to air conditioning the fan problem may be fixed. (I am currently in non-air-conditioned COVID quarantine quarters - not sick, just travelled to Canada for family reasons.)
Various monitoring tools - Core Temp, Open Hardware Monitor - don't show any overheating. It is probably just fan policy settings. I know how to change Windows' CPU fan settings, but haven't found GPU fan policy by Googling.
BTW: I am 99.44% certain that the problem is GPU, hardware or software. Disconnect the GPU, fan turns off. Reconnect the GPU, fan turns on when I start using Nvidia Broadcast. Fan occasionally turns on even when I am not using Nvidia Broadcast. Annoyingly, the Nvidia GPU video engine is running, and it doesn't need to, non-GPU graphics is fine for my application. All I want is the noise filtering. GPU utilization circa 2% or less. But fan is still on.
--
As frequently happens when I make such a post, I realize a possible cause: I restored the old Surface Book image on the "new" (refurbished) warranty replacement Surface Book. It is possible that there were some tuning parameters on the new SB3.2 image. Fortunately, I made a backup, and might try going back.
-------------------------
DPG15.6 (also DPI 15.3) + KB, Sennheiser MB Pro 1 UC ML, BTD 800 dongle, Windows 10 Pro, MS Surface Book 3, Intel Core i7-1065G7 CPU @ 1.3/1.5GHz (4 cores, 8 logical, GPU=NVIDIA Quadro RTX 3000 with Max-Q Design.