Windows 10 1709 freeze randomly

Hi Nicholas,

When Windows freezes it's usually caused by compatibility issues. We suggest checking if the device is compatible with Windows 10 Fall Creators update. If the device is compatible, you may try to start computer in safe mode. This will start Windows using a limited set of files and drivers. This is performed to check if device drivers aren't causing the issue.

If the issue persists in safe mode, we suggest that you run the Hardware troubleshooter in normal boot.

Feel free to post back should you need further assistance.

Thank you for the crappy Microsoft Canned answer.. I have already done all this Lenovo says M$ is to blame and logic would dictate that.

remember M$ forced this update on us.

how about a solution not a canned answer

my clients are tired of excuses.

There is often no quick fix for computer freezes.

They are multifactorial.

What works in one computer often fails in another.

There are lots of things that can cause freezing.

High or 100% disk, 100%cpu, 100%memory intermittingly or for long periods of time.

Problems with BIOS, CPU, GPU, PSU, MB, etc.

So frustration is typical with no quick fix.

So you must start with a systematic plan to rule in or rule out each component.

Often the best method to start is to place the computer in clean boot:

These are some initial steps:

Open administrative command prompt and type or copy and paste:

1. sfc /scannow
2. dism /online /cleanup-image /restorehealth
3. chkdsk /scan

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4. msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)
5. taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

https://social.technet.microsoft.com/wiki/contents/articles/29876.how-to-perform-a-clean-boot-in-windows-10.aspx

6. shutdown /r (you will reboot the computer so that it is in clean boot)

Evaluate the performance on your computer in clean boot during typical use.

Are the boots faster or slower?

Are the shutdowns faster or slower?

How has the video performance changed? Is it better, worse, or the same?

How has the freezing changed?  Is it better, worse, or the same?

Continue using clean boot indefinitely to monitor performance.

8. type control in the left lower corner search > click on control panel > click on large or small icons > click on troubleshooting > on the left pane click on view all > run the following windows troubleshooters:
9. Hardware and Devices
10. Video Playback
11. Playing Audio > open audio enhancements > play test sounds > advanced > change sample rate > test multiple sample rates
12. Recording Audio

For each troubleshooter make sure that advanced is clicked to apply repairs automatically.

For each troubleshooter click on view detailed information.

Report any problems using images that were fixed or not fixed.

i want to tell you what i have experienced so far

1703 fine

1709 fine for some days than freezes at about 1-3 times a day, mostly only 1

1709 also killed my asus ac wireless-card, something about the broadcom chipset driver or so...

the update to 1709 16299.98 seems to have fixed the freezes so far, a week without any, so maybe it could help others too

edit: of course, now some hours later it froze again, i try the disabled fastboot now

Thank You for a real answer with a real solutionn

I will give this a try on two machines tonight.

also i need to suspend this update on any future 

machines until it gets fixed by MS developers

as these are bandaids the real problem is the

coding.