This problem is not limited to MS surface. It's been happening for years (Since 2010) on some machines. Someone mentioned that Microsoft told them this is the first time they'd heard of it... haha... it's the first time some call centre rep heard of it!
It's amusing that it's happening on actual Microsoft designed computers too.
Anyhow I found a sort of fix for my PC that might also pertain to your MS Surface. I'm still investigating so I'm hoping some genius at Microsoft can write me a patch or create a proper solution.
I have a HP 8 core Xeon Workstation. It has coil whine coming from the CPU, only when it's not doing much. When the cores are being used intensively, no whine and when i'm in bios (where its not intensive) no whine. The problem I think arises from how the
operating system is controlling power states (particularly how the computer/OS handles cores when some cores on the CPU are idling).
The solution i have for my computer creates another problem and being that your devices are portable it may not be viable but lets try.
- Open regedit
- Locate HKEY_LOCAL_MACHINE SYSTEM\ CurrentControlSet\Control\ Power \PowerSettings \54533251-82be-4824-96c1-47b60b740d00\ 5d76a2ca-e8c0-402f-a133-2158492d58ad
- Change Attributes from 1 to 0
- This will add a new entry into the power schema in your power options under control panel=> power options.
- In Windows Power Settings (I have mine set to maximum performance) select change advanced settings of your plan and find Processor power management -> Processor idle disable, and set it to Disable Idle.
This instantly stops my coil whine. I can switch it on and off and make music with the coil whine!
But (onto the fact it causes another problem) what it does when processor idle is disabled, task manager reports 100% utilisation on all cores on CPU. This doesn't mean the cores are all being used per se but it does mean it's pumping power to the cores so
heat and battery life are impacted and therefore probably not a viable solution on a portable device.
The thing is Microsoft know this occurring. They can also identify why it's occurring (i.e how the operating system is controlling idle states of power on the device) It's been happening since 2010. They've created patches and work arounds on some platforms.
On mine they haven't (or I haven't found it and seemingly not on their own product as well. Let's hope they do!