Prev: disk driver implementation
Next: Seven API to force local driver check first
From: René on 7 Feb 2010 17:30
Hello,


I've got problems regarding the system idle time on my Windows 7 x86 system. After longer system usage sometimes whether my monitor doesn't go in standby mode nor my screensaver appears.

For testing purposes I've killed all unnecessary processes via the task manager. But even my monitor doesn't went into standby mode.

So I'd like to determine all processes sending a SetThreadExecutionState() message to the operating system. BOINC, a software for distributed computing (e.g. "SETI(a)home"), is running all the time and is logging system activity. I guess it's using the Windows idle timer (via GetLastInputInfo()). In case the system doesn't shut down the monitor, even BOINC does not continue it's calculations. This is an evidence for a process resetting the system idle timer (probably via SetThreadExecutionState()). The system behaves like there is user activity for an infinite time.

Therefore I'd would like to ask if there is a possibility to list all processes which are sending SetThreadExecutionState() messages to the OS to consider the problem from all sides.

Thank you in advance.


Sincerely yours,
Ren? Schwarz


Submitted via EggHeadCafe - Software Developer Portal of Choice
Windows Forms .NET Creating an Owner-Drawn Menu
http://www.eggheadcafe.com/tutorials/aspnet/fc9938c7-4b78-46c3-863d-bce78c6d5c95/windows-forms-net-creati.aspx
From: Doron Holan [MSFT] on 8 Feb 2010 13:03
no such list exists, this api is problematic for the reasons you list and
there is nothing the OS can do under the covers to make it go away

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Ren� Schwarz" wrote in message
news:201027173026eggheadcafe.20.reneschwarz(a)spamgourmet.com...
> Hello,
>
>
> I've got problems regarding the system idle time on my Windows 7 x86
> system. After longer system usage sometimes whether my monitor doesn't go
> in standby mode nor my screensaver appears.
>
> For testing purposes I've killed all unnecessary processes via the task
> manager. But even my monitor doesn't went into standby mode.
>
> So I'd like to determine all processes sending a SetThreadExecutionState()
> message to the operating system. BOINC, a software for distributed
> computing (e.g. "SETI(a)home"), is running all the time and is logging
> system activity. I guess it's using the Windows idle timer (via
> GetLastInputInfo()). In case the system doesn't shut down the monitor,
> even BOINC does not continue it's calculations. This is an evidence for a
> process resetting the system idle timer (probably via
> SetThreadExecutionState()). The system behaves like there is user activity
> for an infinite time.
>
> Therefore I'd would like to ask if there is a possibility to list all
> processes which are sending SetThreadExecutionState() messages to the OS
> to consider the problem from all sides.
>
> Thank you in advance.
>
>
> Sincerely yours,
> Ren? Schwarz
>
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Windows Forms .NET Creating an Owner-Drawn Menu
> http://www.eggheadcafe.com/tutorials/aspnet/fc9938c7-4b78-46c3-863d-bce78c6d5c95/windows-forms-net-creati.aspx

From: Pavel A. on 8 Feb 2010 19:45
Seen same behaviour on WinXP x86 with Intel GMA 3100 video. I wonder if
this is caused by malware :-(

Regards,
--pa

"Ren� Schwarz" wrote in message
news:201027173026eggheadcafe.20.reneschwarz(a)spamgourmet.com...
> Hello,
>
>
> I've got problems regarding the system idle time on my Windows 7 x86
> system. After longer system usage sometimes whether my monitor doesn't go
> in standby mode nor my screensaver appears.
>
> For testing purposes I've killed all unnecessary processes via the task
> manager. But even my monitor doesn't went into standby mode.
>
> So I'd like to determine all processes sending a SetThreadExecutionState()
> message to the operating system. BOINC, a software for distributed
> computing (e.g. "SETI(a)home"), is running all the time and is logging
> system activity. I guess it's using the Windows idle timer (via
> GetLastInputInfo()). In case the system doesn't shut down the monitor,
> even BOINC does not continue it's calculations. This is an evidence for a
> process resetting the system idle timer (probably via
> SetThreadExecutionState()). The system behaves like there is user activity
> for an infinite time.
>
> Therefore I'd would like to ask if there is a possibility to list all
> processes which are sending SetThreadExecutionState() messages to the OS
> to consider the problem from all sides.
>
> Thank you in advance.
>
>
> Sincerely yours,
> Ren? Schwarz
>
>


From: Pavel Lebedinsky [MSFT] on 9 Feb 2010 03:24
> I've got problems regarding the system idle time on my Windows 7
> x86 system. After longer system usage sometimes whether my
> monitor doesn't go in standby mode nor my screensaver appears.

Does powercfg -requests or powercfg -energy (run it from an elevated
cmd window) show anything intertesting?

--
Pavel Lebedinsky/Windows Fundamentals Test
This posting is provided "AS IS" with no warranties, and confers no rights.


 | 
Pages: 1
Prev: disk driver implementation
Next: Seven API to force local driver check first