Power Drain Bug
"Two weeks ago, TG Daily reported that external USB 2.0 devices may cause certain notebook computers to consume power excessively. In the interest of tracking down the source of the problem, Tom's Hardware Guide worked with engineers from both Intel and Microsoft. Through our extensive collaborative research, we can report that an Advanced Configuration and Power Interface (ACPI) driver in Windows XP Service Pack 2 is the sole cause of the unusually high power drainage observed by all three teams. Today, Microsoft confirmed to TG Daily that it is developing a new patch to fix this particular driver bug, whose nature is somewhat different of those those addressed by earlier Microsoft Knowledgebase postings."
"Our collaborative tests revealed that the new problem's root cause is not - as we already had indicated in our initial article - Intel's Core Duo platform itself, even though the problem crops up on Core Duo notebook systems. Instead, the root cause is a Microsoft ACPI driver that leaves the asynchronous task scheduler component continuously running."
As expected, it is M$'s sh1ttiness.
"Two weeks ago, TG Daily reported that external USB 2.0 devices may cause certain notebook computers to consume power excessively. In the interest of tracking down the source of the problem, Tom's Hardware Guide worked with engineers from both Intel and Microsoft. Through our extensive collaborative research, we can report that an Advanced Configuration and Power Interface (ACPI) driver in Windows XP Service Pack 2 is the sole cause of the unusually high power drainage observed by all three teams. Today, Microsoft confirmed to TG Daily that it is developing a new patch to fix this particular driver bug, whose nature is somewhat different of those those addressed by earlier Microsoft Knowledgebase postings."
"Our collaborative tests revealed that the new problem's root cause is not - as we already had indicated in our initial article - Intel's Core Duo platform itself, even though the problem crops up on Core Duo notebook systems. Instead, the root cause is a Microsoft ACPI driver that leaves the asynchronous task scheduler component continuously running."
As expected, it is M$'s sh1ttiness.
