Anyway... shortly after all of that I had issue, reverted controller drivers back, ect. Well I kept thinking this poor performance I had was related to really **** controller drivers, so I switched my OS over to another SATA port and things were still just as bad.
So the already long story short... I ran Process Explorer and found SVCHost and WmiPrvSE.exe both jumping up and down in CPU usage, anywhere from 10-20%. I watched as my i5-2500k (Stock) hit 50-80% CPU use while the RAM stuck at 11-13% (16GB). Opening up SVCHost showed an odd thread listed as
Code: Select all
ntdll.dll!rtlValidateHeap+0x170
This line repeats 5-10 times and only one of them (the newest) has the majority of the SVCHost's CPU use under the threads. Oddly enough, I did a LOT of reading over the course of the last 4-5 hours and found someone mentioning having a lot of Logitech stuff running. I do have a Logitech Keyboard (original G15) and a G5 mouse. Other posters noticed the OP's SVCHost mentioned PNP, which was apparently odd. Well so does mine...
Now here is where it gets funny and odd. I decided to move use the volume button on my keyboard to see what reaction it would have and....... The SVCHost CPU Use went out the roof. The system idle went from 4% total CPU use to 50 and 60%. The thread that shot out of the roof was the
Code: Select all
ntdll.dll!rtlValidateHeap+0x170
So I'm going to remove the drivers that run this stupid keyboard and see what happens. But I figured I'd share this for any poor SoB Google searching a fix for this issue.
Here is an example thread stack when I use the volume adjustment button and spike the heck out of the Plug and Play service/threads.
Code: Select all
ntoskrnl.exe+0x81e7a
ntoskrnl.exe+0x74a32
ntoskrnl.exe+0x865d3
ntoskrnl.exe+0x363197
ntoskrnl.exe+0x6a236
ntoskrnl.exe+0x7e253
ntdll.dll!ZwWaitForWorkViaWorkerFactory+0xa
ntdll.dll!RtlValidateHeap+0x3bb
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21