CPU temps, USB usage

[Brett_Henderson]

make more sense?

Kind of... lol

I was under the impression that I could take a mother-board standing all by itself...

..Connect a USB hub to one of the mother-board USB sockets

..Then get a couple of USB cables with bared wires on the device ends

...Plug one of them into a mother-board USB socket

....Plug the other cable into one of the hub sockets

.....Select a data wire (not power) from one of cable's bared end

......Select the same data wire on the other cable's bared end

THEN   ..  Using a continuity tester, I'd see that electronically, they might as well be the same wire.

If that's true.. then the CPU (or even the O/S) would have no idea whether the the device was on the hub, or plugged right into the mother-board. It (they) just know that the device is somewhere on the shared data bus. Then... the operating system will have assigned one of the 127 possible USB "nodes" to that device and would use that as an address of sorts, when swapping input/output stuff. Like a yoke will electronically "get" data from FSX that was intended for the pedals, it just won't "accept" it, because it's "addressed" to the pedals (and vice-versa).

Or am I bonkers ? (my brain's a little scrambled since hearing that Favre retired)  :(

[7X7-800]

Well, at the risk of beating this thing to death let me weigh in again.

First off, Nick I really do appreciate your taking the time on this, and at the risk of aggravating you, I have removed the powered hub (for now)and gone back to XP SP2 and that registry tweak. All temps have returned to normal.

For the sake of others in the thread, let me summarize my beliefs at this time. I am presently operating on the assumption that my issues with some USB devices causing a rise in CPU temperatures are due to constant USB polling not allowing the processor to throttle down to a lower C-state.

This is apparently what was happening a few years ago with USB devices connected to a laptop running XP SP2 causing unusually rapid battery drain.

The registry tweak I use is supposed to work by relaxing the polling rate and letting the CPU throttle down. It works on my setup but evidently

[NickN]

[quote]Well, at the risk of beating this thing to death let me weigh in again.

First off, Nick I really do appreciate your taking the time on this, and at the risk of aggravating you, I have removed the powered hub (for now)and gone back to XP SP2 and that registry tweak. All temps have returned to normal.

For the sake of others in the thread, let me summarize my beliefs at this time. I am presently operating on the assumption that my issues with some USB devices causing a rise in CPU temperatures are due to constant USB polling not allowing the processor to throttle down to a lower C-state.

This is apparently what was happening a few years ago with USB devices connected to a laptop running XP SP2 causing unusually rapid battery drain.

The registry tweak I use is supposed to work by relaxing the polling rate and letting the CPU throttle down. It works on my setup but evidently

[NickN]

make more sense?

Kind of... lol

I was under the impression that I could take a mother-board standing all by itself...

..Connect a USB hub to one of the mother-board USB sockets

..Then get a couple of USB cables with bared wires on the device ends

...Plug one of them into a mother-board USB socket

....Plug the other cable into one of the hub sockets

.....Select a data wire (not power) from one of cable's bared end

......Select the same data wire on the other cable's bared end

THEN

[7X7-800]

[quote][quote]Well, at the risk of beating this thing to death let me weigh in again.

First off, Nick I really do appreciate your taking the time on this, and at the risk of aggravating you, I have removed the powered hub (for now)and gone back to XP SP2 and that registry tweak. All temps have returned to normal.

For the sake of others in the thread, let me summarize my beliefs at this time. I am presently operating on the assumption that my issues with some USB devices causing a rise in CPU temperatures are due to constant USB polling not allowing the processor to throttle down to a lower C-state.

This is apparently what was happening a few years ago with USB devices connected to a laptop running XP SP2 causing unusually rapid battery drain.

The registry tweak I use is supposed to work by relaxing the polling rate and letting the CPU throttle down. It works on my setup but evidently

[NickN]

OK, I saw SP RC2 and assumed it was SP2 RC2, my mistake

OK, so you have 2 boxes, same motherboard different OS

Just because you have the same motherboard does not mean they are the same unless you open the towers and confirm they are both on the same revision number of motherboard, and then confirm the same BIOS revision, and then confirm the same BIOS settings.


If all of the above is true, then we can say the towers are identical and the OS or something in the drivers for one or the other is the difference

At that point I would say it is possible there may be something about the OS that is the problem, or, a patch or update that may not be applied.

My point was the information you posted had been removed by MS. The KB does not exist

Now... here is more around that KB which states AMD is not affected

"Tom's Hardware recently discovered a bug in Microsoft's ACPI driver
implementation under Windows XP SP2 that causes a loss of more than one
hour of battery time when connecting any USB 2.0 device to an Intel Core
Duo based system. Apparently Microsoft, Intel and ODMs have known of
this problem under a confidentiality agreement since July 12, 2005 via
(a still private) Knowledge Base article KB899179. The bug lies in the
asynchronous scheduler component inadvertently being left running
causing Windows' internal task scheduler (ITS) to treat it as a running
process involving the attached device. This in turn prevents the ITS
from powering down the processor into one of the ACPI sleep states
causing the system to use more battery power. At this time there seems
to be no fix. Strangely, single-core systems and AMD systems are not
affected. This leads one to wonder if it is truely a software problem or
if there a much larger hardware problem that may affect Core Duo
equipped Apple systems."

OK, so my next question would be how is power management set on each of these systems,, the same?

Are both systems set exactly the same in the BIOS for power management AND in Windows under the POWER properties?

If so, do both towers have the same AMD processor driver and/or (if applicable) the dual core optimizer running?

If so then I would have to say at that point you have an issue you shouldn