[Talik]

as I understand it(somone correct me if I'm wrong), windows sends a pause command to the processor to not do anything for a cycle when there's nothing to do. This command is what keeps your cpu from being underload all the time. Anyone who used to write old dos programs back in the day before all this object oriented stuff will know that the computer is always doing something. In oldschool code, the simplest way to make the computer not do anything was to let a big loop count down from some big number. Well, on our end, the computer is not doing anything, but the processor is still doing the same number of processes as ever. I believe this all changed when windows introduced multitasking and that pause command to preserve cycles.

The point I was trying to make is that my guess is that some bios' does not use that pause command, and instead is constantly in the midst of some loop or another. Thus running a full load.

I guess I kind of answered my own question. It came to me a little after I asked.