thank you Ganesh Gandhi for relying, i tried what you suggested both with cmd and through another way but since i don't like wifi i had no wireless interface to show on them only the wired one. i tried disabling the wired connection driver and it did temporarily stop using so much cpu % but turning it on went right back. in my reply to Irisdiel i said i fixed it (for the time being at least) i will add it here.
"thank you Irisdiel for responding i tried the safety scanner but it didn't show any problems, i however moved the wlanext from its folder and placed it into another one (so it just wouldn't be called) that seemed to fix it. now i'm running at 1% cpu usage idling."