going to test further , but latencymon doesn't say that ndis.sys causes problems. so if it's fixed the problem was in windows 10 itself, rather the drivers from NIC manufacters. LE: false alarm. nothing is fixed. just got a "brrr" (mini-freeze) while watching criminal minds. I think it's time to go back to windows 8.1. windows 10 is nothing but a weak joke of an OS.
I installed windows 8.1 and my troubles are gone. Windows 10 just ins't ready enough to be called anything but a spying piece of crap alpha OS
Word. I've just gone back to 8.1 because of the audio glitches. The way Win10 is *not* progressing, I'll be able to update at the end of the year or next year
So what's new guys? Are you still on win7/8.x or is there a workaround on win10 today? I never did go back to win7/8.x permanently. Only for testing, and yes, can't be reproduced. Only on win10 this s**te happens.
still living with it. waiting for the anniversary update this summer to do a fresh install. will see if it still happens then.
Has there been some kind of hardware comparison for those affected? We are in great numbers, but there are those on win10 who don't have this issue AT ALL. I'm Intel. quite old as well, Q6600... but I've seen threads on different sites with the same issue and they have i5/i7.. AMD folks also experience this? Perhaps it's chipset related. SSD's ? Jesus.. Well, it's annoying as f**k. What a shame, I really like win10 apart from this major clusterf**k