I saw this knowledgebase article and wondered why this problem still persists
in windows xp sp2
http://support.microsoft.com/kb/328915/en-us
My scenario: Windows XP Professional, SP2. Fast User Switching enabled.
Two users logged into acpi laptop. One user currently using it, on battery
power, when battery level falls to the "critical battery alarm" level.
As soon as that happens, I get the following
1: popup (as expected) saying "Low Battery : You should change your battery
or switch to outlet power immediately to keep from losing your work."
2: CSRSS.EXE USES 100% CPU (wow, way to handle low battery level..!)
3: System log in Event Viewer filling with messages like "Timeout (30000
milliseconds) waiting for a transaction response from the SENS service." and
"Timeout (30000 milliseconds) waiting for a transaction response from the
Spooler service." etc
But according to the knowledgebase article, the problem of csrss.exe using
100% cpu in low battery conditions was fixed in 2002.
Any ideas? This is freely reproducible for me. Workarounds are not
acceptable (such as "turn off fast user switching" or "use your laptop from
AC power").
Similar Threads
