![]() ![]() Additionally, every safe mode boot added a few dozens of error entries because some services were The message also stated how to change the interval but I never found the option. Also, some error messages simply stated "This error was already logged less than 24 hours ago, not logging it again." (whatĪ dumb behaviour that is btw.), but there was no similar error within 24 hours. I have tried to find out the cause but got frustrated by the suffocatingĪmount of entries in the event log, sometimes happening before the hang, sometimes at the next startup, sometimes not at all. I am not sure whether these are two unrelated problems, two problems both caused by the same update failure, or the same crash that can be recovered from at start up but not at runtime. So they are not related to the creator update. And for once to be clear, the problems first occurred in November 2015, Note that the occurence of the black screen during startup phase is also unrelated to whether the system hung and was forced shutdown or Windows was shutdown normally from the start menu. Since it only happens in idle mode as far as I can tell, I suppose it's related to energy settings/standby/hibernate, but I have no idea how to debug this one. Including the cursor freezes and it does not respond to any input by mouse or keyboard. This happens independently of the program I am running so far I had it with Skype, Android Studio, Visual Studio and Notepad++. Usually, my PC hangs when I am distracted and leave it unattended for a few minutes (watching TV, talking toĪ friend, getting food in the kitchen). The next few startups after that hung update went normal, but after two or three days, there was a long delay of black screen before the login screen (today's test: 5s Acer logo and BIOS > 3s startup (Windows logo, rotating dot circle) > 79s black screenįurthermore my PC started to hang after running Windows for an extended amount of time (range anywhere between 3 and 24 hours system uptime so far). I guess this must have left something corrupted, although symptomes where not immediately visible. I used hard power-off (holding power button) to shutdown. ![]() When it still was updating in the evening, which means updating for about 22 hours, After scheduling the next preview update to be applied upon shutdown over night, I found my PC still running and updating in the next morning. Usually Windows would start withinĨ-10 seconds and updated took 10-20 minutes. I upgraded from an OEM-pre-installed Windows 7 and proceeded to upgrade to every new Insider Preview Build available without any problems several times. I have been using the Windows Insider Preview since April 9th, 2015. Samsung SSD 850 EVO (backfitted) Preliminary events/history: Windows 10 Pro, Version 1703, Build 15063.250 (Creator Update Beta) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |