X

Microsoft driver flaw saps battery strength

Company acknowledges, promises patch to flaw causing notebooks to drain batteries when using USB 2.0 devices.

Tom Krazit Former Staff writer, CNET News
Tom Krazit writes about the ever-expanding world of Google, as the most prominent company on the Internet defends its search juggernaut while expanding into nearly anything it thinks possible. He has previously written about Apple, the traditional PC industry, and chip companies. E-mail Tom.
Tom Krazit
2 min read
Microsoft has confirmed the existence of a flaw in its USB 2.0 drivers for Windows XP Service Pack 2 that can cause a notebook to consume power at a faster-than-expected rate when using a peripheral device.

The issue, first uncovered by Tom's Hardware two weeks ago, appears to affect certain Intel-based notebooks running Windows XP Service Pack 2.

When a peripheral device was connected to a USB 2.0 port, the notebook's battery life plunged at a greater rate than would normally be expected from the use of a peripheral such as a mouse or storage key. When details of the flaw were first published, Intel denied that its processors or chipsets were the responsible for the issue. And Microsoft refused to confirm to CNET News.com until yesterday that the software company was responsible for the battery performance problem.

Microsoft published a Knowledge Base article on the subject in July 2005 but made that information available only to PC vendors and partners, a company representative said in a statement. The software maker is not releasing the article to the public, but industry sources confirmed that a posting on Slashdot is a copy of the original article.

In that article, Microsoft outlined a problem with its USB 2.0 drivers that prevents a mobile processor from entering advanced sleep states designed to minimize power consumption. According to Tom's Hardware's testing, the effect was even more pronounced on Intel's new Core Duo processors, which are capable of entering a deeper sleep state than older Pentium M chips.

Other tests by reviewers such as Anandtech found that the problem affected notebooks with a variety of Intel processors. It was not clear whether the issue also affected notebooks with Advanced Micro Devices' Turion or Athlon 64 processors.

In the private Knowledge Base article, Microsoft outlined a fix that involved modifying the registry key for USB 2.0. However, since then, the company has realized that this is an impractical fix for most users and is working on a new fix that could involve a BIOS update patch, a company representative said in a statement.

The severity of the problem depends on how USB 2.0 has been implemented in a notebook--which encompasses a wide variety of factors, such as the operating system, processor, chipset, USB 2.0 device, and the software and drivers attached to all those components, an Intel representative said. Intel is also working on a fix for the problem that would not be dependent on a software download, such as a tweak to future processors, the representative said.

Notebook users who experience the problem should contact the manufacturer of the notebook for further assistance. Some notebook manufacters have modified the registry keys as outlined in the Knowledge Base article, but this solution does not always work as intended outside of lab testing, the Microsoft representative said.