title: Visual Studio CPU High Usage
body: <p>It's a week that I have any Visual Studio (2010 professional, 2012 professional and 2015 community edition) that, after few minutes I started a project even empty, without touching anything, start a thread that consumes entirely one core, 100% usage.
  From task manager I've seen that <strong>devenv.exe</strong> is consuming 25% of CPU, I have 4 cores so 100/4=25.</p>
  
  <p>By using Process Explorer I've seen that is <strong>clr.dll</strong> (<strong>clr.dll!GetCLRFunction+10793</strong>) that is running continuosly.</p>
  
  <p>here is the stack trace of the thread:</p>
  
  <pre><code>ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a 
  ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
  ntoskrnl.exe!KeWaitForSingleObject+0x19f
  ntoskrnl.exe!PoStartNextPowerIrp+0xba0
  ntoskrnl.exe!PoStartNextPowerIrp+0x183d
  ntoskrnl.exe!IoFreeErrorLogEntry+0x297
  System.ni.dll+0x19ab70
  System.ni.dll+0x1de979
  System.ni.dll+0x19ab70
  System.ni.dll+0x199d42
  System.ni.dll+0x1ded86
  System.ni.dll+0x1de5fa
  System.ni.dll+0x1de397
  System.ni.dll+0x1da636
  System.ni.dll+0x1c755e
  System.ni.dll+0x19ebfb
  System.ni.dll+0x19eccf
  clr.dll+0x1396
  clr.dll+0x291f
  clr.dll!PreBindAssemblyEx+0x1822c
  clr.dll!PreBindAssemblyEx+0x183af
  mscorlib.ni.dll+0x2f1213
  mscorlib.ni.dll+0x2f103e
  mscorlib.ni.dll+0x2ffb72
  mscorlib.ni.dll+0x30a366
  mscorlib.ni.dll+0x2ffd30
  mscorlib.ni.dll+0x3aebef
  mscorlib.ni.dll+0x3aeaba
  clr.dll+0x291f
  clr.dll+0x9aff
  clr.dll!PreBindAssembly+0xb165
  clr.dll!PreBindAssembly+0x9653
  clr.dll!PreBindAssembly+0x96bd
  clr.dll!PreBindAssembly+0x978a
  clr.dll!PreBindAssembly+0x9805
  clr.dll!PreBindAssembly+0xb0f9
  clr.dll!PreBindAssembly+0xa166
  clr.dll!GetCLRFunction+0x107dc
  ntdll.dll!RtlInitializeExceptionChain+0x63
  ntdll.dll!RtlInitializeExceptionChain+0x36
  </code></pre>
  
  <p>Does anyone understand something from the above lines??</p>
  
  <p>On Internet I've found several suggestion to disable one or another plugin/extension of visual studio, by none of them solved the problem, and moreover I have the problem on all the VS version (with different extension and happened at the same time)</p>
  
  <p>I think it's something related to the .net framework 4.5 ~4.6 that I have updated recently.
  How can I understand where is the problem and how to solve it?</p>