Windows 10 1709 freeze randomly

can you confirm if you issue was resolved after disabling fast start up?

In my case, this was allready disabled.

The update is the problem.

Fix it!

disabling fast startup made no difference

using powercfg.exe /h off and turning off virtual memory management has seamed to work

as well as a full system reset keeping documents

thats it.

doing an in place install only worked on 1/4 pcs

the other thing was the full reset so far had 100 success just time consuming.

First, let me say I have the same random freezing problem after installing Windows 10 version 1709, and have tried all the suggested fixes in this and other posts to no avail.

But, I did find one recommendation on a third party web site that got my attention. It was talking about having too little Virtual Memory specified and how that might cause Windows 10 to hang randomly. So, I checked to see how much Virtual Memory I had specified on my system with 16GB of memory and a Samsung 850 EVO 500GB SSD. To my surprise, my Virtual Memory settings were set to Initial = 200 and Maximum = 1000. I have no idea how they were set to that level.

I decided to change my Virtual Memory settings to Initial = 1024 and Maximum = 8192. So far, I have gone 24 hours without any random freezes, and am waiting to see if that change helps resolve my random freezing problem for a longer period. I thought I would pass this along to others as a possible resolution and will report back in about a week to let you know my results.

After writing the information above on 12/22/17 about changing virtual memory, I also noticed that my NVIDIA GPU driver had been updated to version 388.71 earlier that day. My OS Build is currently at 16299.125. I kept my fast startup turned on after trying it on and off. My system has been running very well for 24 hours per day for the last 7 days. But, I don’t know exactly why, so I can’t pass along anything definitive except that something had a positive impact and helped my particular case.

After reading all these posts, it is easy to see that many systems are freezing and others aren’t, and there are no common instances as to why. Some workaround fixes help some people and those same fixes don’t help others. That makes it very hard to pin down exactly what the problem is and how to fix it because there are so many variables.

What would be nice is for some expert at Microsoft to post a message on this thread and let us know if Microsoft knows what the problem is and when it might be fixed. That way all of us wouldn’t be wasting a lot of our time, energy and money trying to diagnose and fix something that is out of our control.

Update 01/01/18: My PC just froze up again so nothing I did really helped.

can you confirm if you issue was resolved after disabling fast start up?

Fast startup is a combination of hibernation & shut down. You're system shuts down normally, but the system provides a little power to your on memory to store data. Now, you will notice if you use fast startup & you take out ram & put in new or the same. It'll take a but longer to load up & sometimes crash during the load up as it was looking for files no longer accessible. 

Disabling fast startup only does one thing. It doesn't use hibernation. It re loads data from your HDD or SSD to load up. Now fast startup is useless if you use a SSD because the access times are no different from ram to SSD, in many cases its better from the SSD. I don't have fast startup enabled because it can cause corruption & crashing during windows load up. It has no effect on the system once it's loaded up. So only disable if you have problems loading windows. Once windows has fully loaded & you've been using software or whatever. Fast startup has no bearing at that point on your system. 

I will also like to add. Fast startup is the worst thing you can have enabled if you have a laptop. Because if a battery goes dead after or taken out. It will try & load data that's not available anymore & most likely crash during boot.

I have also had this problem since the 1709 update in December 2017. I rolled back to 1703 and disabled the updates. Microsoft - can you please acknowledge that there is a problem with 1709? Are you looking into this and when will it be fixed?