New
#11
An update ...
Graphic driver: Windows update offered me a new Intel G41 Express driver. I couldn't see which level it was but decided not to take it.
PSU: I swapped out the PSU and replaced it with the spare PSU, which seems to power the PC OK. However, the problem persists with the swapped PSU. I removed the CD/DVD drive, the Soundblaster card and the Wireless card to minimise the PSU current load.
PassMark Sleeper: This seems to be very good. Help says:
Power State ... Description
Working ... The system is fully on. Some devices may independently conserve power if there usage falls below a certain threshold.
Sleeping ... The system seems as though it’s shut down. Power consumption is reduced to one of the three sleep levels (see below). The lower the level, the more power that is conserved, but the longer it takes for the system to wake. Mouse movement or key presses will usually wake the system.
Soft Off or Hibernate ... The system appears to be off. Power consumption is very low. The operating system context is saved out to disk and no longer exists in RAM. Wake up usually results in hardware boot, but not software boot.
Mechanical Off ... No power consumption. A full reboot will be required to start up the system.
ACPI (Advanced Configuration and Power Interface) is an industry wide standard that defines a power management and configuration mechanism for hardware and operating systems. ACPI defines six discrete power states. Lower states consume more power, but have a smaller latency on wake up.
S0 – Working
S1 – Sleeping
S2 – Sleeping
S3 – Sleeping
S4 – Hibernate
S5 – Off
Sleeper allows the user to put the system into sleep state S1, S2, S3 or S4. To turn off or reboot the computer, see the Rebooter application also available from PassMark.
Note that not all computer systems will support all power states. It is not unusual for just S1 and S4 to be supported or S1, S3 and S4. Attempting to put a system into an unsupported state results in the next lowest supported state being chosen.
It tells me that my PC supports S1, S3 and S4, so I set up a cycle of: sleep S1 for 30 sec > wake for 60 sec > sleep S3 for 30 sec > wake for 60 sec > sleep for S1 for 30 sec > ... etc. Sometimes it runs several times, but it always seems to fail while sleeping in the S3 (deepest) sleep state - see output below where it failed on the first S3 state.
I read elsewhere that the deepest sleep state leaves only the memory powered (lighter sleeps leave other stuff powered). I have 2 x 2GB memory cards = 4GB total.
EDIT. I now think that statement is wrong. My desktop supports Hybrid sleep as the default sleep mode, so I think these states are: (see http://www.tekrevue.com/tip/comparin...ep-on-windows/)This is the output I got from Sleeper for the last failure with the swapped PSU:
S1 Sleep as in the old days. The memory is powered up (possibly at low voltage because it is not being changed, it just needs to retain the data), but everything else is powered down. The problem is that a power cut will lose what is in memory
S3 Hybrid sleep. User data in memory is first written to disk, and the PC is then put to sleep as in S1. If there is no power cut while sleeping, then it comes out of sleep exactly like S1.
But if there was a power cut, then user data and system in memory are lost, but user data is still available on disk and can be recovered.
2014-Jun-25 12:11:11 **********************************************************************
2014-Jun-25 12:11:11 Sleeper V2.3 (Build: 1009), built on Oct 15 2012 10:38:25
2014-Jun-25 12:11:11 Attempting to load powrprof.dll
2014-Jun-25 12:11:11 **********************************************************************
2014-Jun-25 12:11:11 GlobalPowerPolicy.user.GlobalFlags = 0x12
2014-Jun-25 12:11:12 WAKE UP FROM S1, CYCLE 1, Sleeper restart, possible power cycle
2014-Jun-25 12:11:12 SLEEP TIME TOO LONG WARNING, Sleep time 1403694672sec
2014-Jun-25 12:11:26 Going to sleep, S1, Unforced, Duration 30sec
2014-Jun-25 12:11:26 Setting wake time at Wed Jun 25 12:11:56 2014
2014-Jun-25 12:12:14 Waitable timer triggered.
2014-Jun-25 12:12:14 Wake up from S1, Cycle 1
2014-Jun-25 12:12:14 Sleep time too long warning, Sleep time 48sec
2014-Jun-25 12:12:14 Successfully left sleep state S1...
2014-Jun-25 12:12:14 About to enter sleep state S3...
2014-Jun-25 12:13:16 Going to sleep, S3, Unforced, Duration 30sec
2014-Jun-25 12:13:16 Setting wake time at Wed Jun 25 12:13:46 2014
... and it powered itself off. I will continue checking to see if it powers off immediately, or when it gets the wake up signal - I expect the latter.
I have attached a new set of debug files - they are debug-Lounge-PC-0002.zip and I would greatly appreciate any hints they suggest. I left all the original dmp files in so it includes those I posted before. Hopefully the drivers bits might reveal something new.
Last edited by JohnHa; 27 Jun 2014 at 07:43. Reason: typos, correction