Windows 10 1709 freeze randomly

Anonymous
2017-11-10T16:29:39+00:00

Windows 10 1709 its been out almost a month now and still no fix for the freezing bug issue, lots of people are having the same issue as me and none of your suggestion work  unlike the 1703 which didn't freeze for me but sadly 1709 does but seems like Microsoft hasn't acknowledge the problem yet..   #Microsoft fix it

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

203 answers

Sort by: Newest
  1. Anonymous
    2018-04-04T10:33:22+00:00

    Same here. Three devices, three HP laptops (one intel, two AMD). Also a Lynx tablet which seems now not to freeze following a BIOS fix released specifically to stop the tablet turning itself on and draining battery. All suggested fixes for Laptops tried with no success. I have noticed however, that both AMD devices do not freeze after rebooting (hard reset via power button that is).

    Would be nice to see a fix for this, been an MS OS user since Win 3.11, and currently only use MS OS and Office 365 (even have a Win phone), otherwise I will have no choice but to switch to Mac OS.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-03-30T04:16:39+00:00

    Yes, right, I already lost a hard drive. Mine freeze at 54% installing, and I need to shut it down . lucky it rolls back to 1706 every time

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-03-29T18:28:13+00:00

    Very true... Freeze means Freeze...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-03-29T17:06:33+00:00

    UT, CAPS AGAIN:---IF STUFF FREEZES UP, hit CTRL+ALT+DEL & IT SHOULD BRING UP THE blue security screen. Then click on Task Mgr & every thing will unfreeze. Even if you have Task Manager open, it does not matter. That is the easiest quick solution. THAT IS THE EASIEST QUICK SOLUTION.

    Unfortunately the problem (for some of us at least) is when it freezes, it freezes. Nothing usually works besides a hard reset, mouse doesn't move and keys don't work. And on top of that nothing appears regarding the error when you check the event manager after the hard reset.  I think some have had this issue to the point of having to hard reset so much that it's damaged their hard drives.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-03-29T15:27:09+00:00

    After reading all 17 pages of this thread, it is time for me to chime in on this. I too have experienced, and continue to experience, lockups described here.

    I have three machines each of which has 1709 Build 16299.301 on them.

    • HP Laptop
    • HP Desktop
    • Dell Laptop

    My husband's HP desktop also has 1709 Build 16299.301 on it. (Hubby also happens to be an IT professional.)

    NONE of our machines have AMD processors - we only buy machines with Intel processors. So the issue does not appear to be processor-specific.

    My husband's machine experienced these lockups a few weeks ago. He booted into Safe Mode, ran virus scans (i.e., MalwareBytes followed by a full Norton scan,)  and after doing this a couple times, his machine finally booted normally and has been working ok since (knock on wood.) FYI, he just turned off fast startup on it.

    My machines were working well until last Thursday (March 22) when I booted my HP Desktop for a video call I had - everything looked normal, but after launching Chrome everything hung as described by everyone here. I let it sit for several hours, no change. Finally did a hard shutdown, and left it until the weekend.

    Next, Saturday morning (March 24) I booted my Dell laptop, launched Chrome, and it locked up... Again, I let it sit for several hours - no change. Did a hard shutdown, booted in safe mode, ran virus scans (again MalwareBytes and full Norton,) shut down, rebooted, and it booted normally.

    In parallel, we did the same Safe Mode/scan process on my HP Desktop, only it did not boot up normally - it still hung. The following morning (Sunday, March 25,) I tried again and booted it up to see if it would be ok (with the plan to try the Safe Mode/scan process again,) and this time it booted ok. Never hung for the rest of day after I let it sit idle for the entire day.

    Saturday I also checked my HP Laptop, and it booted ok, and has done so a couple times since. I hope it continues to work.

    Then this morning, I booted my Dell Laptop before leaving for work (as I normally do to check a few things,) and after launching Chrome, it again hung. I let it sit for about a half hour while I did other things before doing yet another hard shutdown. We will try turning off Fast Startup if we can get it to boot normally.

    One other issue I noticed a couple weeks ago (i.e., well before learning about this hanging/freezing issue,) that I had forgotten about until just now – and I did not see this issue mentioned anywhere in this very long thread. It may or may not be related but it may offer a clue to what is happening. On my Dell Laptop, about a week ago, I tried to enable the built-in Photo Gallery Screensaver that I had been using several months ago (I had switched to SETI at Home for a while, but decided to stop using it.) When I previewed the the screen saver to make sure it was pointing at the correct directory, my machine WOULD NOT WAKE UP when I moved my mouse or hit the keyboard. I think I finally got it to wake up using Ctrl-Alt-Delete or the Windows key or something - can't remember specifically what worked… But after that, I disabled all screen savers because I didn't want to have to resort to hard shutdowns if it would not wake up. The symptoms I experienced are the same as what we are seeing with the freezes - it is as if the mouse and keyboard are are not connected/inputs are not being recognized...

    As an electrical engineer, this makes me wonder if Microsoft programmers did something unintentionally that screwed up the Interrupt Service Routine (ISR) for peripheral interrupts (not sure if these should be NMIs, or non-maskable interrupts, or normal interrupts,) with this update... Wouldn't be the first time an update intended to push out bug fixes and improvements seriously broke other parts of an otherwise working system. And what is most frustrating, it seems to be an intermittent problem that is difficult to reliably reproduce/track down.  Just a thought.

    Was this answer helpful?

    0 comments No comments