Error Code 0 in Passmark Sleeper

[Yan2008]

An "Error Code 0" message pop up when I tried running Passmark Sleeper for 240 cycles [suporting S1, S3 and S4 state]. Anyone can help in providing the details of this error code?

Thanks in advance.

[David (PassMark)]

Exact when does it occur, and is this the full error message. A screen shot might be helpful.

[Yan2008]

I do have a screen shot but unfortunately I do not think I have the privileged to attached picture/file

Following are the details information in the log file:

2008-Nov-12 15:36:33 Going to sleep, S4, Unforced, Duration 60sec
2008-Nov-12 15:36:33 Setting wake time at Wed Nov 12 15:37:33 2008
2008-Nov-12 15:36:37 System Event, 01 - Information, Event: 0x4000001A, Source: Application Popup (Generated time: 2008-11-12 15:36:37)
2008-Nov-12 15:36:38 SetSuspendState failed. Error code: 0
2008-Nov-12 15:36:38 Sleep error, Error code 0
2008-Nov-12 15:36:38 Error entering sleep state S3...
2008-Nov-12 15:36:46 System Event, 02 - Information, Event: 0x40001069, Source: Tcpip (Generated time: 2008-11-12 15:36:46)
2008-Nov-12 15:37:01 System Event, 03 - Information, Event: 0x4000106A, Source: Tcpip (Generated time: 2008-11-12 15:37:01)
2008-Nov-12 15:37:36 System Event, 04 - Information, Event: 0x40001B7B, Source: Service Control Manager (Generated time: 2008-11-12 15:37:36)
2008-Nov-12 15:37:36 System Event, 04 - Description: The Windows Image Acquisition (WIA) service was successfully sent a start control.
2008-Nov-12 15:37:41 System Event, 05 - Information, Event: 0x40001B7C, Source: Service Control Manager (Generated time: 2008-11-12 15:37:36)
2008-Nov-12 15:37:41 System Event, 05 - Description: The Windows Image Acquisition (WIA) service entered the running state.
2008-Nov-12 15:38:01 System events activity logging stopped.
2008-Nov-12 15:38:01 Application events activity logging stopped.

[David (PassMark)]

The Windows function SetSuspendState fails. When this function fails, according to the Microsoft documentation, it returns a system error code.

The list of possible system errors can be found here.

But error code 0 is not in fact an error. Which doesn't make much sense. My guess it that is really did fail, but for this particaular failure condition, no error code was set.

The fault is likely to be in a device driver, but tracking down sleep and hibernate problems is very hard work.

[Yan2008]

Thanks a bunch for the information.

I'm really interested in looking into the root cause as you said it is likely to be a device driver issue, and it still would be best I take off this incompatible driver to make sure my computer works stable, right?

So if I face this error again, any advise on how to track down which driver is giving me this issue?

[David (PassMark)]

We are only aware of 2 methods
1) Trial and error, by removing & replacing hardware / software. Looking in the Windows event log can sometimes help.
2) Kernel level using the Windows debugger. However you need to be a pretty hard code programmer to do this. I only know of one or two people in the world who have the knowledge to do this.

[Yan2008]

If that's the only choices, I'll try method 1 to give a go and see can I get any positive results.

Thanks a bunch.