Cannot log on after sleeping machine for a few hours - Build 14393
-
Cannot log on after sleeping machine for a few hours - Build 14393
Just wondering of anyone has seen this issue. I reinstalled my machine with fresh copy of Anniversary build. One issue that cropped up is when I suspend my machine, usually for extended periods, I can't log back on anymore. I would get the password screen, I enter my password, it spins for a while and then returns me to the locked screen.
After a bit of digging in the Event Viewer, I noticed a bunch of crashes on the LogonUI.exe, but the timestamp of the log was from when I first put the machine to sleep.
Something like this:
|
|
|
|
|
[ Name] |
Application Error |
|
|
|
|
Keywords |
0x80000000000000 |
|
|
|
|
|
|
[ SystemTime] |
2016-09-11T01:29:12.200385200Z |
|
|
|
|
C:\Windows\system32\LogonUI.exe |
|
|
|
C:\Windows\system32\Windows.UI.Logon.dll |
|
|
|
0c07b31c-aa3b-4b33-8afe-696bed0739c6 |
This has happened twice so far.
-
-
Unplug your computer, open up the chassis. If you know how to remove and reinstall the RAM, you may want to swap your memory sticks and retry. Could be a small memory leak.
Also make sure the motherboard BIOS is fully up to date, and your drivers are fully up to date.
What are your system specifications? "MOBO, CPU, RAM, Video Card, etc"
-
Unplug your computer, open up the chassis. If you know how to remove and reinstall the RAM, you may want to swap your memory sticks and retry. Could be a small memory leak.
Also make sure the motherboard BIOS is fully up to date, and your drivers are fully up to date.
What are your system specifications? "MOBO, CPU, RAM, Video Card, etc"
Specs updated, kinda annoying that the forums (I have an account on SevenForums already) aren't all synced to use one account DB.
I'm not convinced it's hardware or drivers, actually. Hardware has been untouched for 5 years, it was running Windows 7, a poorly upgraded Windows 10 previously and it was rock solid. Only hardware change was adding the MX300, and that drive has been running for weeks on the previous Windows 10 installation.
-
-
As horrible as it seems, untouched hardware can also go bad over years.
Although, if you are not convinced, one thing I have done in the past is go back to a previous operating system and retested an issue.
If the issue is there, but wasn't before, chances it's hardware, but if not, then it could be a bug in the Anniversary update..
My pc has no issues with the Anniversary Update . Seems like a few PCs are still having issues.
-
As horrible as it seems, untouched hardware can also go bad over years.
Although, if you are not convinced, one thing I have done in the past is go back to a previous operating system and retested an issue.
If the issue is there, but wasn't before, chances it's hardware, but if not, then it could be a bug in the Anniversary update..
My pc has no issues with the Anniversary Update . Seems like a few PCs are still having issues.
Well when I meant it was working fine I meant a few days ago when I was still on 10586... I literally just installed this copy fresh.
I mean I could restore my backup and try it again on 10586, but I'm fairly sure it isn't the case.
Quote