- Joined
- Oct 27, 2007
- Messages
- 1,132 (0.19/day)
System Name | Grandpa |
---|---|
Processor | i5 4690K |
Motherboard | Gigabyte Z97X-UD5H-BK |
Cooling | water |
Memory | 8GB Corsair Vengence 2400MHz |
Video Card(s) | Gigabyte 5850 x2 |
Storage | Samsung SM951 |
Display(s) | Catleap 27" |
Case | coolermaster stacker |
Power Supply | corsair AX860i |
Mouse | logitech g5 original |
Keyboard | Ducky |
Software | Windows 8.1 |
I recently upgraded to creators update and immediately began to have problems with Chrome. After about 3 -10 minutes of use it would begin to stop responding.
It starts with bits of a page not responding. After about 15 seconds or so this would spread to the whole page. Then one by one the other tabs would stop. Eventually the entire PC will stop responding. the whole hang takes about 1 minute
Occasionally I would get a response from something but in all circumstances I eventually had to restart in order to get everything back working again. I tried to use Edge and it also had the same issue except it took a little longer to occur.
If I avoid opening a browser, then no problems occur. I put a resource monitor window up and watched that - no peaks in CPU, Memory, disk or network.
So I gave up and rolled back the update and everything was fixed. Has anyone experienced this also? I'm thinking of trying the update again and was wondering if there might be something I can do to avoid the problem again.
It starts with bits of a page not responding. After about 15 seconds or so this would spread to the whole page. Then one by one the other tabs would stop. Eventually the entire PC will stop responding. the whole hang takes about 1 minute
Occasionally I would get a response from something but in all circumstances I eventually had to restart in order to get everything back working again. I tried to use Edge and it also had the same issue except it took a little longer to occur.
If I avoid opening a browser, then no problems occur. I put a resource monitor window up and watched that - no peaks in CPU, Memory, disk or network.
So I gave up and rolled back the update and everything was fixed. Has anyone experienced this also? I'm thinking of trying the update again and was wondering if there might be something I can do to avoid the problem again.