Computer won't resume from standby

[mikeymikec]

I've just built a PC of the following spec:

AMD Athlon II X2 250
Crucial 2GB (single channel) DDR3-1333
ASUS M4A89GTD PRO/USB3 (latest BIOS tried after experiencing problem for the first time)
WD Black 500GB
on-board graphics (HD 4290)
Corsair CX430 PSU
Win7 64 HP

I've reinstalled it a few times out of desperation, trying different routines, drivers, disabling all optional on-board devices, etc. It's the same board as I have in my own PC which resumes from S3 fine, but about 50% of the time this computer doesn't, even if I use the power button to wake it. The power LED just carries on flashing. Holding down the power switch for >5 seconds does nothing, and I have to switch off the PSU directly. When I switch the computer back on, if hybrid sleep is enabled, the computer thinks it has resumed successfully and says as much in the log, when really it has used the hibernation data to resume.

I've also tried getting all the latest Windows and driver updates, disabling USB selective suspend, hybrid sleep, forcing S3 in the BIOS, and quite a few other bits. I've reset the BIOS several times, including removing the battery, and tried not touching any BIOS settings, etc. I also tried IDE and AHCI setups of Windows.

Based on something I read, I downloaded the Windows 7 SDK and used the performance analysis software in it to monitor the S3 standby/resume process, but even the summary XML is a long read and I have no experience with this software previously. The only things I've noticed that are out of the ordinary are the same bits of info that are in the event log entries for when the computer has 'resumed', being the 'BIOS init duration' and the 'hibernation read duration', but I think those are just indicators that the problem has happened, particularly the latter.

The 'BIOS init duration' is about 350 during a successful resume and zero when it doesn't succeed.

 

[panais]

I've just built a PC of the following spec:

AMD Athlon II X2 250
Crucial 2GB (single channel) DDR3-1333
ASUS M4A89GTD PRO/USB3 (latest BIOS tried after experiencing problem for the first time)
WD Black 500GB
on-board graphics (HD 4290)
Corsair CX430 PSU
Win7 64 HP

I've reinstalled it a few times out of desperation, trying different routines, drivers, disabling all optional on-board devices, etc. It's the same board as I have in my own PC which resumes from S3 fine, but about 50% of the time this computer doesn't, even if I use the power button to wake it. The power LED just carries on flashing. Holding down the power switch for >5 seconds does nothing, and I have to switch off the PSU directly. When I switch the computer back on, if hybrid sleep is enabled, the computer thinks it has resumed successfully and says as much in the log, when really it has used the hibernation data to resume.

I've also tried getting all the latest Windows and driver updates, disabling USB selective suspend, hybrid sleep, forcing S3 in the BIOS, and quite a few other bits. I've reset the BIOS several times, including removing the battery, and tried not touching any BIOS settings, etc. I also tried IDE and AHCI setups of Windows.

Based on something I read, I downloaded the Windows 7 SDK and used the performance analysis software in it to monitor the S3 standby/resume process, but even the summary XML is a long read and I have no experience with this software previously. The only things I've noticed that are out of the ordinary are the same bits of info that are in the event log entries for when the computer has 'resumed', being the 'BIOS init duration' and the 'hibernation read duration', but I think those are just indicators that the problem has happened, particularly the latter.

The 'BIOS init duration' is about 350 during a successful resume and zero when it doesn't succeed.

Hi

In two other oldest similar cases like urs in the first computer the reason was a damaged motherboard and in the second case problematic memory.
So for the moment try to install and use any other compatible memory.
-------------------
And please post back with any results!

 

[mikeymikec]

Thanks for responding so quickly

Re: possibly damaged board - was that the only symptom you saw, not being able to resume?

 

[panais]

Thanks for responding so quickly

Re: possibly damaged board - was that the only symptom you saw, not being able to resume?

The reason i have mention in my first reply the possibility of damaged motherboard or problematic memory (or both) is...<<In two other oldest similar cases like urs in the first computer the reason was a damaged motherboard and in the second case problematic memory>>
So the first and easiest step is to try with other memory ram,just give it a try.
As for the damaged motherboard (if is that the case) is very difficult to repair a damaged motherboard and in most of the cases not possible.