I recently made the upgrade to Windows 10 1704 (after rolling back because of too many bugs).
Besides another bug, Chrome was crashing/freezing quite often. So I looked into Windows' ressource monitor and saw a red entry of chrome.exe saying "chrome.exe is waiting for another process: svchost.exe (NetworkService)" in the queue. Killing Chrome or the svchost-subprocess on any way resulted in an access denied. So I thought Windows was the cause and that they screwed up an upgrade yet again. Adding to this, it didn't matter if I used Chrome dev or stable and even Edge crashed on me even "lying" about it by not giving a "not answering" and not exactly freezing but not really reacting on much and not being able to load any site.
About three days I had enough and made a fresh installation of Windows...without any success. So I took a look into the event viewer (or whatever they call it in english) and found following error:
Das Schließen einer UDP-Socket mit der lokalen Portnummer "59217" im Prozess "3024" dauert länger als erwartet. Die lokale Portnummer ist möglicherweise erst nach Abschluss dieses Vorgangs wieder verfügbar. Der Grund hierfür liegt in der Regel im fehlerhaften Verhalten von Netzwerktreibern. Stellen Sie sicher, dass die neuesten Updates für Windows und für die Netzwerksoftware von Drittanbietern einschließlich NIC-Treibern, Firewalls oder anderer Sicherheitsprodukte installiert sind.
For those not speaking german in short: it's some problem about closing a UDP-Socket and that the reason is mostly a bad network driver.
Well, I'm using the SetPRO version from Lenovos website since this is a lenovo laptop, but I also tried to uninstall the driver and Proset and install it from Intels download section but nothing changed. Chrome keeps freezing, especially after waking up my laptop from sleep or hibernation (which happens very often since I pretty much never shut down my laptop because a I still have an HDD running b because I am too lazy to open up all programs again after the system is finally ready to work at an appropiate speed and c I deactivated hybrid shutdown since it often either causes problems or at least stops solving them since that often needs a real restart).
I also experienced that a simple restart is often helping only for a very short time, a restart via shutdown -g -t 0 gives me a bit more time to the next freeze. And Chrome doesn't exactly crashes, it freezes for a few minutes and then returns to normal. But then it's pretty much guaranteed that it will freeze again in the next minute and if it goes back from showing that blue Windows bar of "process not responding" it is frozen completely, it's not reacting to anything and killing it from task manager does nothing.
My WiFi device is a Intel Dualband Wireless N 7260.