[notebook] system restarts after sleep if power cable is plugged in

drkh · 07 Jan 2020

Hi,

On my notebook (Acer Travelmate 4730), if the power cable is plugged in, the system always restarts automatically after it is woken up from sleep. whether the battery is removed or not. No such a problem if un-plugged.

That happened after a certain Win10 update which I don't remember. (Automatic updating is disabled and the Win10 version stops at 1709 build 16299.492.)

Can it be fixed?

Thank you.

dalchina · 07 Jan 2020

Hi, latest manufacturer support is to Win 7,
Product Support | Acer United States

so running Win 10 like millions of others you're in non-specified territory. I.e. if it works, great, but you may have problems (unspecified). Is that why you're staying with 1709?

That happened after a certain Win10 update which I don't remember.

Options:
a. Assuming you mean this started to happen with build 1709 installed, you can of course uninstall updates that have been applied.

b. You can do an in-place upgrade repair of 1709 which keeps all progs and data.
Search for Heidoc iso downloader and use that to get a suitable iso file.

Note: if the problem started to occur with an earlier build of Windows you would have to clean install an earlier build to get back to where you were.

Of course, if you used disk imaging routinely (Macrium reflect free-paid + large enough external storage) as is so frequently recommended here, you might have another way to resolve this yourself by restoring an image you had created.

drkh · 08 Jan 2020

dalchina,

Thank you for helping.

I bought that NB as a second hand sale. The old owner had upgraded the OS from the original Win7 to Win10 1607 before he sold it to me.

I have only allowed updating to 1709 because I'm not sure if more updatings won't do anything bad to that NB whose original OS was Win7. So far I havn't experienced anything bad. So I decided to disable updating before it might be too late. However, I still download malware difinitions manually.

As I recall now, the problem we are discussing must happen after the update to the current 1709 version bcause a few months ago the same problem occurred for the first time and by that time the update to the current version had been done. For that problem at that time I successfully fixed it with a system restore.

A few days ago the problem occurred again. Naturally I tried fixing it with a system restore, using the same restore point as I did last time. But this time it did not work. After the system restore, the problem still exists.

Before I made the post here, I had thought about rolling back to the previous Win10 version as you suggested. But I would like to try my luck first. Of course I will follow your advice and do the un-installment if I have to, as the last recourse.

dalchina · 08 Jan 2020

A few days ago the problem occurred again.

You can look at your Update History to see which update that was, assuming a Windows update is responsible. (Driver Updates also listed at the bottom).

Uninstalling individual updates should be quite painless. Of course, if you wish to stay with a particular build, you wil need to disable Windows Updates. A 3rd party tool can easily help there.

An in-place upgrade repair install is not uninstalling. It's the same procedure as upgrading, but going backwards within the same build.

Note- you cannot go back to 1609 except by:
- restoring a disk image created when 1609 was running - if you have one
- clean installing 1609.

Before any major change make sure you have a current disk image (Macrium Reflect e.g. ).

drkh · 09 Jan 2020

Before the problem occurred a few days ago, Win10 had gotten updated to 1709 and, because automatic updating is disabled, there hadn't been any updating of any sort. So the question might be:"Why does a system restore back to the same restore point not work?" This morning I started to doubt BIOS. So I flashed it again. But no good.

It seems quite a few people have the same problem. Anyway, usually I don't use the NB with the power cable plugged in. I think I can live with it.

dalchina · 10 Jan 2020

You could try disabling fast startup- this causes users problems quite often. Some comments suggest there's a relationship between this and sleep, although that is non-intuitive.

However, what you're seeing could be low-level driver incompatibility related to upgrading to a non-supported O/S.

drkh · 11 Jan 2020

Fast startup had been disabled before that problem occurred the first time.

Try3 · 11 Jan 2020

Perhaps your display driver has become corrupted. Go to your computer maker's website and download then re-install the display driver.

More generally & only after current issues have been resolved -
Since ver 1709 is no longer supported, perhaps you could make a system image then experiment with updating to ver 1909 safe in the knowledge that you can revert easily by restoring that system image.

Denis

dalchina · 11 Jan 2020

I'd have suggested 1609 as an experiment, rather than 1909, or as above an in-place upgrade repair install of 1709 - if the problem starts following a Windows update already experienced, using 1909 is not likely to resolve it, if it is a driver issue with an older PC.

joeandmarg0 · 11 Jan 2020

In the cmd window, type in powercfg /lastwake,then enter and see if that gives any clues.Also check your Reliability History for any entries.
Run sfc /scannow at least twice,followed by dism /online /cleanup-image /restorehealth and see if there are any results.It is a sensible action to use these two methods once a week,which helps prevent problems from starting.
Naturally ,use Macrium.