
Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
Killer Network Wireless Adapter 1535 problems
Hello!
I have Alienware 15 R2 with Killer Network Wireless Adapter 1535 on board, Windows 10. And link quality is awful! Freezes, disconnects, huge ping to 3 meters far router (1100 ms) and other...
I saw several topics about the same problem, but I didn't find any solution.
I’ve updated to the latest version of Killer Siute from Killer web-site and from Dell web-site several times. Before I’ve deleted all Killer Software, all devices and drivers and then installed that suite….The same.
Then I repeated the same steps in safe mode (because just after deleting of Killer wireless adapter in device manager, Win 10 installs it automatically again), but Suite installation is finishing with error…Problem remains.
I tried to delete Killer Bandwidth Control from Wireless adapter properties – worse; I deleted and reinstalled Killer Bandwidth – problem remains. I disabled Killer network manager, putted the correct link speed – nothing…
Have I any chances to make this adapter workable or it’s better to change it on Intel?
Responses (29)
Solutions (0)
Look, I don't "think" my Killer chip is workable, I know it is. I've used it for the past year with zero problems after the initial bad driver debacle, it is running just fine. While there are clearly some issues around this product, the assumption that all 1535 are bad is just wrong. There may be wifi environment and other issues also at work here.
Driver as shown by Device Manager is:
Qualcomm Atheros Communications Inc. 15/01/2016 12.0.0.210
See:
Ping statistics for 192.168.0.1:
Packets: Sent = 374, Received = 374, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 26ms, Average = 2ms
While I may be one of the lucky ones, and the situation is not ideal, it is just too simplistic to say the 1535 is totally unusable or broken.
And while it might be easiest to just replace the wifi with Intel, that doesn't fix the problem for most people - why should they have to pay to get someone to fix this?
I think a better approach would be to help Killer fix this (since they are already here) and one of the ways of doing this is to provide more information - something remarkably lacking in most of the posts here. For example, nobody else has even posted what drivers they are using.
I'm also not using the Killer Network Manager to manage speed or app priorities - that could be a factor.
Then could somebody explain me, please, how killer chip can be the fastest, if signal's speed (ping) is worse then on Acer's old laptop?
For example, my laptop is downloading (f.e. from torrents) good (on a high speed), but when you are browsing it's horrible! Bad ping is showing himself.
That's why I've used the word "think" that yours Killer chip is workable.
Then could somebody explain me, please, how killer chip can be the fastest, if signal's speed (ping) is worse then on Acer's old laptop?
Sorry, somebody else will have to, I can't, because my pings are just fine (also, I don't have an old Acer laptop). Could not be happier with it. :-)
For example, my laptop is downloading (f.e. from torrents) good (on a high speed), but when you are browsing it's horrible! Bad ping is showing himself.
That's why I've used the word "think" that yours Killer chip is workable.
I'm sorry, I got the impression that you thought maybe I was mistaken about how well my Killer wifi is working. Believe me, I'm not; it is excellent. Browsing is fine, can't tell the difference between wired and wireless. File transfers of all sizes work fine, and I have long uptimes with no need to reset the wifi, ever (quite different from how this was when I received the laptop).
I think a 2TB directory sync over wireless is a pretty fair test, no problems there.
Look, I know exactly what you are experiencing, because my laptop was the same when new, but it is 100% OK now, has been for the past 11 months or so. Originally wifi wouldn't run for even a few hours without slowing down and dying.
Network Card - Killer Wireless-n|a|ac 1535 Wireless Network Adapter Vendor Name Qualcomm Atheros Interface PCI Express x1 MAC Address 9c:b2:d0:02:44:0f Adapter Connected Yes Current Speed 144.40 Mbps IP Address 192.168.0.61 IP Mask 255.255.255.0 Gateway IP Address 192.168.0.1 DHCP Server 192.168.0.1 Adapter DHCP Enabled Yes Driver Provider Qualcomm Atheros Communications Inc. Driver Version 12.0.0.210, 1-15-2016 Killer Network Manager is 1.1.57.1686, but previous releases worked fine (as long as they weren't the original Dell one). IIRC, 1.1.56.1590 fixed the problem, subsequent updates (1.1.56.1603, 1.1.56.1651, 1.1.57.1679) all worked fine. I've had 1.1.57.1686 installed since March 2016.
I've used the same driver's version 210 as you. It's pre-installed version by Windows (the oldest one). But my problem remains anyway.
I can transfer 2TB on my home router (Linksys) also without drops, but huge ping remains and I can't use wireless desktop properly.
On 3 office routers (two TP-links, one Asus) it's just impossible to work for anyone, when i'm starting my laptop.
Cause Dell support had send me another Killer chip after Techical diagnostic, I' writing now the memoirs letter about "how I am having problems for 2.5 bucks?" And only then they will send me the Intel chip maybe.

B4gy
1 Rookie
•
16 Posts
2252
0
Posted October 28th, 2016 12:00
So! I brought my laptop in Technical Service. They've ordered the new Killer wifi chip.
I told them that it's not hardware problem (Killer support think opposite), but they said Dell support is working like that: they will send the same hardware and only after second appeal they will send MAYBE the Intel wifi chip!
Today I've installed the new Killer chip and the problem remains!
Could somebody, who think their Killer chip is workable, check the ping to your router? Cause every chip shows 1 ms (like Intel and others), but Killer shows at least 5 ms and then 30, 100, 1000....until drop!
You can do it like that:
in command panel (perform - cmd) put "ping 192.168.1.1 (address of your router) - t"