I really need help, its been a month trying to fix this. KThreadd problems, stuck processes.

If you have a UEFI BIOS a small partition formatted as FAT32 is required.
Have you tried running

lsusb

Don't worry about the kernel or the disks unless you have confirmed that USB is OK (or not).
Change one thing at a time.

You say it i'm on it bud. I provided this. Not sure at all if this means anything.

Bus 002 Device 002: ID 8087:8001 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 046d:c537 Logitech, Inc. 
Bus 003 Device 002: ID 0461:4d8a Primax Electronics, Ltd 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

That lsusb looks OK
Guessing that you have a Primax keyboard & a logitech mouse - and nothing else.
You can look up most devices in https://wiki.debian.org/HowToIdentifyADevice/USB or http://www.linux-usb.org/usb.ids, using those hex digits.

Your devices aren't listed though, which doesn't necessarily mean anything.

Are you still having problems?

One suggestion would be to boot a live distro from USB or DVD and see if it still has problems.
This would rule out your HD.

Bro they are, they just sit there even when i got to a usb or cd live version, they just sit there, i reformat, there still there, i turn off the computer, hey there still there, this amazingly sucks. Does that link i posted in the first page of this post mean anything somebody told me that was the answer at a time.

If a live version doesn't work it comes down to hardware.
(I trust you've tried a non-KDE live version?)

If something like Debian fails, then you need to test things like RAM.

Bro, i appreciate your response i will say this one more time though. they are stuck in uninterpretable processes from a virtual box instance and within that virtual box instance a program kept closing and i kept reopening it. Which in turn spit out all these processes.

From what i have read. i need to send a signal to them to end them, that is how i do it but i have no idea how to go about that.

get the PID of that process/es then inspect with lsof and see which files that processes is working on.

lsof -p <PID>

hey cowboy, i truly appreciate your wisdom into this situation. here is the terminal lines.

/home/xd# lsof -p 2
COMMAND  PID USER   FD      TYPE DEVICE SIZE/OFF NODE NAME
kthreadd   2 root  cwd       DIR    8,1     4096    2 /
kthreadd   2 root  rtd       DIR    8,1     4096    2 /
kthreadd   2 root  txt   unknown                      /proc/2/exe

here is another one also, there is about 40+

migration  32 root  cwd       DIR    8,1     4096    2 /
migration  32 root  rtd       DIR    8,1     4096    2 /
migration  32 root  txt   unknown                      /proc/32/exe

is this helpful at all?

I did a bit of googling for you and realized that this is a kernel process similar with PID 1. So you cannot kill or remove it and should not even attempt to. It gets started by the kernel itself denoted by its brackets. I am not a kernel hacker but I think we are barking a a wrong tree here. If something is bothering you, maybe find I/O, network or hardware issues instead or maybe a rogue user-space processes. I don't think it is the cause of perceived high CPU usage.

My 2cents.

I appreciate you a ton man, like i said your wisdom is welcome. I see what your saying and i agree. It was a program that was sending stuff on line, the program that was crashing and i was using in virtual box to run it. So that makes perfect sense, i did read about something i/o in the past. i can signals to these process to get to get them leave but i don't know how. There is programs but i have no idea how to use them.

i look at your post and your join date. i do appreciate you man you don't insert yourself to often so thank you again.

Glad to help.