- Category: Wi-Fi and Bluetooth Troubleshooting
- Last Updated: 10 February 2018
- Hits: 68
Internet Problems With New Computers With Killer 1550
Some users may encounter issues with new computers with the Killer Wireless-AC 1550 installed. These issues can usually be resolved by updating the Killer Control Center to the latest version, available here - https://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. If you are unable to download the updated package, click Settings in the Killer Control Center, and toggle Advanced Stream Detect to Off. This will temporarily disable all latency reducing and bandwidth prioritizing features from your Killer networking adapter, but should allow you to download the updated package. Once you have the latest Killer Control Center downloaded, double-click it to begin the install. When the install is complete, Advanced Stream Detect will be activated by default.
- Category: Wi-Fi and Bluetooth Troubleshooting
- Last Updated: 30 January 2018
- Hits: 114
There are a few things that can cause your Wi-Fi adapter to disable itself, but, unfortunately they don't really make themselves known up front. Here are some steps you can try to correct the issue:
- Update to the latest Killer Control Center available from our website - http://killernetworking.com/driver-downloads/item/killer-control-center-x64. If you experience any problems while updating to the latest Killer Control Center, please see this article - http://killernetworking.com/driver-downloads/kb/faq/6-troubleshooting-killer-ethernet-wireless-drivers-software
- Update your machine's BIOS, if an update is available, from your machine or mainboard manufacturer.
- Update your machine's chipset driver from your machine or mainboard manufacturer.
- Update your wireless access point's (whatever you connect to wirelessly, be it a Wi-Fi modem, router, or extender) firmware. If the access point is a Wi-Fi modem that is owned by your ISP, you'll have to contact them and have them update the firmware for you. Old firmware can cause this issue as the adapter will disable itself if it receives a large number of bad frames from the access point.
- Completely uninstall and reinstall your Killer suite and drivers, using this guide - http://killernetworking.com/driver-downloads/kb/faq/58-clean-install-any-driver - which will ensure that Windows is using only the latest driver files for the Wi-Fi adapter.
- Change your Wi-Fi adapter's power settings using this guide - http://killernetworking.com/driver-downloads/kb/faq/59-wi-fi-power-settings.
- Use the built-in Network Reset for Windows 10. You can do this by clicking Start and typing Network Reset. You may have to reinstall any VPN adapters, and re-input any Wi-Fi or VPN passwords after using the Network Reset. You may also need to reinstall the network adapter drivers.
If you have done all of the above, but still find that your Wi-Fi adapter is disabling itself, please contact us directly so that we may assist you further!
- Category: Ethernet and General Troubleshooting
- Last Updated: 08 November 2017
- Hits: 2100
Slow Network Speeds
If you are experiencing slow Internet or network speeds, you can follow this troubleshooting guide to address and correct the most common problems.
If you haven't already, please try installing the latest Killer Control Center from our website, and only from our website. It includes many fixes and improvements that are not be included in other packages. If you are still using the Killer Network Manager, you'll want to download the Killer Control Center, and then manually uninstall the Killer Network Manager, as well as the "Killer Drivers" entry in your programs list. You can find the latest Killer Control Center here: http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64. Please download and run this installer, which will also install the latest drivers. If you experience any problems installing the Killer Control Center, you can refer to this article for help - http://www.killernetworking.com/driver-downloads/kb/faq/6-troubleshooting-killer-ethernet-wireless-drivers-software
Once you have successfully updated your drivers, you will want to restart your computer by clicking Start > Power > Restart. It is important to note that closing the lid or pressing the power button on many modern computers does not shut them down, but instead activates sleep mode. You must restart them by clicking Start > Power > Restart for them to restart.
If updating the drivers does not solve the issue, try resetting your networking equipment in this specific order, even if you have reset your some or all of your equipment previously. This order is proven to help your devices sync up properly, and will help to get a clean slate with further troubleshooting. Doing this can help even if only one device is experiencing problems.
- Shut down your computer.
- Locate your modem and note the lights on your modem when it is normal and ready. There may be a "Ready" light.
- Unplug your modem, router, and any switches or hubs, between your computer and the modem, as well as any wireless boosters or access points, and leave them all unplugged for now.
- Plug in your modem.
- Wait until your modem's lights show normal operation again.
- Plug in your router, if you have one, and give it about five minutes to boot.
- Plug in anything else between your computer and the modem
- Power on your computer.
- Once your computer is booted and connected to the Internet, you will want to reset its network stack:
- In the search box on the taskbar, type Command prompt, right-click Command prompt, and then select Run as administrator > Yes.
- At the command prompt, run the following commands in the listed order, and then check to see if that fixes your connection problem:
- Type netsh winsock reset and press Enter.
- Type netsh int ip reset and press Enter.
- Type ipconfig /release and press Enter.
- Type ipconfig /renew and press Enter.
- Type ipconfig /flushdns and press Enter.
- Now reboot your machine once more and test to see if the issue is resolved.
If not, the next step is to make sure that your Windows installation is completely up to date. Microsoft has been updating Windows more often than with any previous release, so it's important to keep things up to date. To do this, simply search Windows Updates, hit Enter, and then click Check for Updates. If your machine finds updates, check again once it finishes installing. Once your machine finds no updates, restart again, and then check for updates once more. Once your machine finds no updates upon a fresh reboot, your Windows installation should be fully up to date.
If you have performed the above, and you are still experiencing issues with slow network speeds, there are some other things to try:
- Set a benchmark. Place the device in one place, if dealing with Wi-Fi, and run a test using one speed test. Turn off all other network usage while troubleshooting. Speedtest.net and Testmy.net are both good bandwidth tests. Run three tests in short succession and record an average as your starting point. Test after each change to see if there has been improvement. Record what you changed, and what the speeds the change produced. If the change seems dramatic, restart the machine and test again to be sure.
- Make sure your BIOS is up to date from your machine or mainboard manufacturer's support page.
- Make sure your chipset drivers are up to date from your machine or mainboard manufacturer's support page.
- Make sure all of the other drivers are up to date from your machine or mainboard manufacturer's support page. You can safely download and install all available driver packages. If the driver does not apply, it will either not install, or will not be used. If the only options in a driver installer package are "Repair" or "Uninstall", choosing "Repair" will update the driver, if there is a newer driver available.
- Update the firmware on your router if you own the router.
- Update the firmware on your modem if you own the modem, but only if your ISP accepts the firmware. Your ISP's support team can help you with this. Some ISPs also have this information listed somewhere, but they may need to do something on their end if you update the firmware, in order to re-authorize your modem.
- Have your ISP update the firmware on your modem or router if they own your modem or router.
- If you are using Wi-Fi, minimize the number of solid objects between the access point's antenna and the device suffering from low speeds, using line-of-sight. Moving a device or antenna even an inch to one side could bypass multiple solid objects, making an enormous difference.
- If you are using Wi-Fi, use the Killer Control Center's Wi-Fi analyzer to make changes to your router's settings.
- 5 GHz routers should be set to channels 36-48, and/or 149-165 that are as far away from other channels as possible.
- 2.4 GHz routers should be set to channels 1, 6, or 11, depending on which channels have the least powerful conflicting radios present.
- Sideband, or side channel should be set to 20 MHz if there are many other Wi-Fi access points in your area, especially if you are forced to share a channel. Higher side channels are less powerful, but provide a wider band, allowing the signal to get around solid objects better, theoretically improving performance in situations where there are no interference concerns, but the Wi-Fi signal needs to "get around" solid objects. Many, however, report that, in real life testing, 20 MHz still provides the better signal, so your mileage may vary.
- If you are using Wi-Fi and your router has both a 5 GHz radio and a 2.4 GHz radio, name them something different. Although it might seem simpler to name them the same thing, many routers do not handle this very well, and you can see performance issues by having them named the same thing. Many people opt to simply add "5" to the end of the 5 GHz radio.
- If you are using Wi-Fi extenders, name each of your extenders something different, so that you know which access point you are connected to. Wi-Fi extenders have limited radio capacity, and will, always provide at least slightly slower speeds than connecting directly to the router, as they have to use the same radio to receive and transmit, at the same time.
- If it seems like other machines using the same access point are having no issues, try to verify this. Borrow their machine and run a speed test. Ask for permission first, of course. If you are experiencing issues on a public access point, you might just find that the public access point is just terrible, and that no one else is having a problem because you're the only one playing latency-intensive first person shooters.
- If you are using a Wireless-N router in a crowded Wi-Fi environment, you are very likely to encounter drops and speed issues no matter what settings you change. Unfortunately, the 2.4 GHz spectrum is very limited on how many channels are available, and conflicts arise quickly. Updating to a Wireless-AC router may be required to increase your speeds and reduce wireless drops.
- If you are using an antivirus or firewall application, try completely uninstalling it for testing purposes. Unfortunately, simply disabling these programs do not work for troubleshooting purposes, as they often continue to manipulate network traffic. They must be fully uninstalled. If you notice that your speeds increase dramatically with the antivirus or firewall application uninstalled, try installing a freshly downloaded version from their website. If that doesn't help, then the issue may be one with the antivirus application itself. In that case, you will want to contact the support team for the antivirus application.
If you are unable to get your speed issues sorted out using the above tips, feel free to contact us directly using the information below!
- Category: Frequently Asked Questions
- Last Updated: 02 November 2017
- Hits: 789
Ad-Hoc and Hotspot Functionality with Killer Adapters in Windows 10
You may wish to create an Ad-Hoc or Hotspot network with your Killer Adapter on your Windows 10 machine.
With Windows 10, all Ad-Hoc and Hotspot functionality has been officially moved away from the drivers, and into the operating system itself.
If you would like to create a Hotspot or Ad-Hoc network with Windows 10, you simply need to click Start, type Hotspot, and press Enter. All of the relevant settings for your Hotspot network will be on that page.
The Windows 10 version of our driver does not support the "Hosted Network" feature because Microsoft's own WDI driver does not have support for this. Microsoft is having all wireless vendors move to the WDI model, thus this feature will not work on Windows 10 drivers until after (and if) Microsoft expands support for SoftAP/Wi-Fi Direct.
In the meantime, if you need this feature back for certain older applications that made use of their own Hotspot or Ad-Hoc features, you can load the Windows 8.1 drivers via Device Manager from our INF download. We have verified that this works, and have had confirmation from other users as well.
However, we cannot guarantee that Windows Update will not automatically update these drivers, or that they will work flawlessly with Windows 10, as they are, after all, Windows 8.1 drivers. Use Windows 8.1 drivers in Windows 10 at your own risk.
- Category: Wi-Fi and Bluetooth Troubleshooting
- Last Updated: 30 January 2018
- Hits: 239
Some users may experience issues with their Killer Wi-Fi adapter not being able to detect certain specific Wi-Fi access points. Here are the things to check for:
- If you are in Europe and the access point might be on the 2.4 GHz band, it may be using channels 12 or 13. If you have access to the settings on this access point, try changing the the channel to 1, 6, or 11. If not, try updating to the latest version of drivers, which should be able to make use of channels 12 and 13 in European countries - http://www.killernetworking.com/driver-downloads/item/killer-control-center-x64
- Your router or modem may be using a DFS channel. DFS channels are 5 GHz channels that can be used by the public, but public devices receive a "leave the channel" command if official use is necessary. Although Killer Wi-Fi adapters ordinarily have no problem operating on DFS channels, if your laptop has been used in an area where the DFS channel was being used in an official capacity (such as an airport), it may have received the signal to stay off of that channel. For example, in the United States and some parts of Europe, DFS channels are 5 GHz channels 50-144. When troubleshooting a wireless network that does not appear for a specific device, these channels should be avoided in these areas. You can use the chart available on this Wiki page to quickly see which channels are available in your area of the world. We have also noted that some routers will automatically choose DFS channels even though they are not compatible with those same channels, and they must be manually set to a channel in order to not use them.
- Your router or modem may need to be power cycled. All routers and modems rely on a very small amount of physical resources and, eventually, those resources will hang, making it necessary to restart them from time to time. The fastest and simplest way to do this is to unplug the device for ten seconds, then plug it back in. This can help even if only one device is having problems with the access point.
- Your computer may need to be restarted. Restart your computer by clicking Start > Power > Restart. Note that pressing the power button on most modern computers activates sleep mode - it does not shut them down. In order for your computer to reboot, you must either click Shut Down or Restart.
- You may be too far away from the wireless access point. Wireless signals rely on line of sight and, as such, each individual solid object between your device and the access point diminishes the signal. A single wall may contain multiple solid objects. A floor contains concrete subflooring, wood framing, piping, and various other solid objects. If at all possible, make sure you can connect with another device before assuming any one device is faulty.
- There may be interference. 2.4 GHz routers in crowded apartment complexes are especially susceptible to this. You can use the KIller Control Center's Wi-Fi Analyzer to see how many people are sharing your current channel. If too many people are on the same channel as you, it may not be possible to connect to your own access point from too far away. Setting your sideband, or side channel, to 20 MHz can help mitigate this, as the smaller ths sideband, the stronger the signal.
- Your wireless profile may have become corrupted. If you have connected to this access point before, but it is no longer visible, you may need to delete the connection's profile and reconnect. Here are the steps:
- Click the rectangular "Connect" button, where you would normally click to connect to a wireless network, on the bottom, right-hand side of your screen.
- Click Network and Internet Settings.
- Click Wi-Fi on the left, if it is not already selected.
- Click Manage Known Networks
- Click the network that you are not able to detect.
- Click the Forget button.
- Close the Settings window, and connect like normal. If the access point still does not appear, try restarting your machine by clicking Start > Power > Restart.
If you are still unable to connect to a specific wireless access point, feel free to reach out to our support here - http://www.killernetworking.com/about/contact.
- Category: Frequently Asked Questions
- Last Updated: 15 February 2018
- Hits: 33
Can the E2500/E2400/E2200 Be Used Wirelessly?
Users have asked if the E2500, E2400, and E2200 can be used wirelessly. These are Ethernet adapters, so they cannot be used wirelessly. They require an Ethernet cable to be connected to your machine, and to an Internet gateway, such as a modem or router.
Your machine may also come with a wireless adapter, which may or may not be a Killer Networking adapter. If the wireless adapter is not a Killer Networking adapter, the Killer Control Center will report "No Killer Network Interfaces Connected" when you are connected to the Internet with only the non-Killer adapter. This is normal, as the Killer Control Center can only be used with Killer Networking adapters.
- Category: Wi-Fi and Bluetooth Troubleshooting
- Last Updated: 12 February 2018
- Hits: 84
Verizon FIOS 5 GHz Issues
Users may encounter a situation where their Killer Wireless-AC adapter will not connect to their FIOS router on the 5 GHz Wi-Fi band.
This seems to be due to the FIOS routers automatically choosing specific DFS channels that they may not fully support. There are a multitude of reports about this phenomenon around the web - where certain devices can connect to them while others cannot - but this post explains it fairly well - https://www.reddit.com/r/HomeNetworking/comments/2tu2so/why_some_devices_cant_see_the_verizon_fios_g1100s.
Fortunately, the fix is simple:
- Log in to your FIOS router's setup page. This page explains how to do so with some FIOS routers. It may not include all models. You may have to seek assistance from your ISP. https://www.howtogeek.com/197382/how-to-change-the-wi-fi-channel-on-your-verizon-fios-router/
- Change your router's 5 GHz channel. You can use the Killer Control Center's Wi-Fi analyzer to find which channel has the least traffic, but changing to any channel that is not a DFS channel should allow your devices to connect. Channels 36-48 and 149-165 are non-DFS channels in the United States. Your area may vary. You can reference this chart to find out which channels are DFS channels, and which are not, in your area of the world - - https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax)
- Restart your machine, if necessary, and see if the issue is resolved.
- Category: Linux
- Last Updated: 07 February 2018
- Hits: 76
Wi-Fi Disconnects and Latency on Debian, Ubuntu, and Arch
Some users have noted Wi-Fi disconnects and latency on some distros of Linux after recent updates.
This issue likely affects Debian, Ubuntu, and Arch, and may also affect any other Debian-based distros such as Mint, Kali, etc.
As the ath10k Wi-Fi driver that is used by our Wi-Fi devices in these versions of Linux is a community sourced driver, we have no direct impact on its stability, but since some users have indicated that they have found a fix for these issues, we wanted to share the fix with the rest of our users.
In summary, the fix is to install the updated firmware and firmware repo, following these steps:
- Download https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/board-2.bin and overwrite /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin with the downloaded file.
- Download https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/4.4.1/firmware-6.bin_WLAN.RM.4.4.1-00065-QCARMSWP-1and overwrite /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin.
Following is a much more detailed, step-by-step guide on how to implement this fix:
- Open a Terminal window and navigate to the following location:
- Backup your board-2.bin and firmware-6.bin files:
sudo mv /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin.bak
sudo mv /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin.bak
- Download the two replacement versions and place them into the '/lib/firmware/ath10k/QCA6174/hw3.0/' folder:
- Rename your new 'firmware-6...' file to 'firmware-6.bin':
sudo mv firmware-6.bin_WLAN.RM.4.4.1-00065-QCARMSWP-1 firmware-6.bin
- Enter ls -la into your terminal to verify the directory looks something like this:
user@Ubuntu-XPS:/lib/firmware/ath10k/QCA6174/hw3.0$ ls -la
drwxr-xr-x 2 root root 4096 Feb 6 15:29 .
drwxr-xr-x 4 root root 4096 Jun 24 2016 ..
-rw-r--r-- 1 root root 271412 Feb 6 15:30 board-2.bin
-rw-r--r-- 1 root root 271412 Feb 6 15:28 board-2.bin.bak
-rw-r--r-- 1 root root 337204 Nov 15 15:56 board-2.bin.wifi-qca6174
-rw-r--r-- 1 root root 8124 May 12 2016 board.bin
-rw-r--r-- 1 root root 8124 Dec 1 2016 board.bin.wifi-qca6174
-rw-r--r-- 1 root root 733784 Dec 1 2016 firmware-4.bin
-rw-r--r-- 1 root root 711408 Feb 6 15:30 firmware-6.bin
-rw-r--r-- 1 root root 711408 Feb 6 15:28 firmware-6.bin.bak
-rw-r--r-- 1 root root 79689 Dec 1 2016 notice_ath10k_firmware-4.txt
-rw-r--r-- 1 root root 82663 Nov 15 15:44 notice_ath10k_firmware-6.txt
- Restart your computer.
Please let us know if you have any issues following this guide, or if you note any errors. You can reach at firstname.lastname@example.org.