New
#51
Do my errors have anything to do with the gateway???
Default gateway keeps dropping
-
-
New #52
File explorer crashing should not be related to the gateway issues but way down in Windows amazing things can happen.
As I read the thread you got the file explorer issue after disabling IPv6. This too should have nothing to do with File Explorer but appears to have started after this change. Maybe it was there before the change.
By all means you can run sfc /scannow at anytime for peace of mind.
I think I would run the inplace repair and test file manager. I would also remove the adapter prior to the inplace repair and get the updates through a wired connection.
Assuming the file manager issue resolves I strongly recommend buying a new adapter.
-
New #53
Sfc didn't show any issues.is the inplace repair the same as an inplace upgrade? And what is a test file manager?
-
-
New #55
i dont think that the file explorer has any issues.still cant fix the internet.should i just go to windows 7?
-
New #56
Not sure that Windows 7 is the answer. Yes it may work.
If you are prepared to clean install 7 I might first try V1809 as a clean install or 1803.
Windows 7 may provide a tactical fix, we both know it is for one year.
To be honest I would replace the adapter. It very well is the cheapest alternative when you consider the cost of your time.
-
New #57
Got another of these disconnects on a new TP-Link card (as opposed to the USB adapter previously) not nearly as often and this driver is dated 09 Jan 2018 so should be Win10 compatible. Something is wonky with Win 10 networking (...but then what's new? LOL)
-
New #58
i bought a new tp link wireless adapter and my internet connection is better. it also has drivers for windows 10.however now i am facing new problems. like when i start up the system the device sometimes may be disabled error 22. when i restart the pc(i dont think that this is because of the wireless adapter) it takes to much time and the event viewer shows this The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffffe202b0a944c0, 0xfffff805410a7900). A dump was saved in: C:\WINDOWS\Minidump\012019-23218-01.dmp. Report Id: 3fd172f5-29db-4d96-bfa0-6b0d9a805a12.
and sometimes my devices just restart usbehci A timeout occurred while waiting for the EHCI host controller Interrupt on Async Advance Doorbell response.
WLAN Extensibility Module has stopped.
Module Path: C:\WINDOWS\system32\Rtlihvs.dll
Name resolution for the name ubistatic3-a.akamaihd.net timed out after none of the configured DNS servers responded.
Name resolution for the name static.doubleclick.net timed out after none of the configured DNS servers responded.
there are also plenty of distributed coms
-
-
New #59
Have you got Windows Fast Startup disabled?
Did you remove all the old drivers for your other adapter and any hidden devices in Network section of Network Adapters.
To show hidden devices head to device manager, click on view tab, click on show hidden. Then expand Network section. If asked remove any software associated with device (drivers).
To see drivers that maybe installed use DriverStore.
https://github.com/lostindark/Driver...orer/releases/
I might also run these four reset commands. The stuff in brackets is for your info, commands bolded
ipconfig /flushdns (Clear the dns cache)
nbtstat -RR (release and refesh NetBIOS names)
netsh int ip reset (reset ip settings)
netsh winsock reset (Reset Winsock Catalog)
If you continue getting a bugcheck I would head to the BSOD section of forums, complete the prework and submit.
-
New #60
when i ran nbstat it said that it could recognize it.
Quote
Related Discussions
