Debugging windows standby issue


I have a following issue: one of processes in the system, is running a thread, which sets SetThreadExecutionState to ES_SYSTEM_REQUIRED. This prevents system from entering standby. I've disabled all custom software, and most of unneeded services/drivers, and it still happens. It happens only if there is network connection active.

I need a way to debug and find out which thread does this. If I could use SoftIce, i could set breakpoint on SetThreadExecutonState, but SoftIce does not work on XP SP3. I tried to use Syser, but couldn't get it to work.

I'm open for all suggestions.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

There is this place to look for a posible solution:

For example, something to check:

OpenGL Screen Saver Prevents Power Management Standby Mode

When you configure your computer to use an OpenGL screen saver and the System Standby feature in Advanced Power Management (APM), your computer may not start the Standby mode.  This issue can occur if the OpenGL screen saver starts before the time you configured for the Standby mode to start has elapsed.

The Computer Cannot Enter Standby or Hibernate If a Direct3D-Based Screen Saver Is Running

Microsoft has released a new update for Windows XP, which addresses a rather small flaw that may prevent the computer from entering standby or hibernation mode if a Direct3D-based screen saver is running. Despite replacing two DirectX libraries and all the 3D screen savers that have been shipped with Windows XP, this update does also replace the winlogon.exe with an updated build.  Download here:

QQAuthor Commented:
Hi guys,

thanks for all the links.

I have no screensaver enabled.

And the problem is caused exactly by ES_SYSTEM_REQUIRED flag being set.

I have read the first link, but I didn't see anything that could help me..
QQAuthor Commented:
I found the issue - it was caused by someone connecting to the computer through netbios file sharing.

Admins: You can close the question. I would like points refunded.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.