Solved NT Kernel & System Spiking?

Today, I turned on my laptop to do an assignment and realized the computer wasn't keeping up with my typing speed, instead I get ~2 second delays from what I type or the keys just don't count at all. So I check my task manager and notice System (NT Kernel & System) jumps from 0 to ~12 CPU every second. I tried so many options and none seem to work for me: System Restore, updating drivers, scanning for viruses with Malwarebytes, disabling my wireless adapter to see if CPU drops, and other failed methods. Should I just reinstall windows/do a system refresh? I've tried so much all day long, so please toss me suggestions. It hurts to type. Also yesterday, I didn't download/update a single thing, so I don't get how this tragedy occurred.

Edit: Also, ETD Control Center seems to randomly spike up from about 2 to 12 CPUish, when I remove my mouse from the USB, the track pad refuses to work although the mouse is unplugged. Maybe that has something to do with the issue?

You may be able to restore the track pad by booting into safe mode, deleting the track pad in Device Manager, then booting normally. On normal boot Windows should "find new hardware" and reinstall the track pad driver. Sometimes this restores normal operation. In any case it's the first thing to try since it is free and I never heard of it failing to reinstall the deleted device.

MilesAhead said:

You may be able to restore the track pad by booting into safe mode, deleting the track pad in Device Manager, then booting normally. On normal boot Windows should "find new hardware" and reinstall the track pad driver. Sometimes this restores normal operation. In any case it's the first thing to try since it is free and I never heard of it failing to reinstall the deleted device.

Click to expand...

I managed to fix it myself by just unplugging my USB mouse and power adapter, then shutting off my laptop and letting it rest overnight. But hey, thanks for the effort anyways! I was going to try what you suggested until I discovered the problem fixed itself.

Glad you resolved it.