Killer Network Wireless Adapter 1535 problems

There is no any solution. I've just talked with Killer Support specialist. I have been installing and uninstalling that drivers 1000 times (with Suite, without suite, with/without bandwidth), but link remains the same bad.

So, the only way to change the adapter on Intel.

Hello,

I am a part of the Customer Support team at Rivet Networks.  I believe I was able to locate your support ticket, and it seems the last diagnostic we were sent showed a previous version of our software running on the system.  If you could please send us an up to date diagnostic we would be glad to troubleshoot further.

- Rivet Support

As I said to your employee (but he didn't answer on my emails): after installation of some drivers that he advised to download from your site I don't have any Killer software on my system, because the plan was to install only drivers from INF package without any Killer Network Manager, bandwidth filter etc. I gave him the question: How could I make the diagnostic by Killer Diagnostic (like I did before), if I can't install it using Killer Suite from your site? In that case drivers will update on those that inside the Suite and you will receive the same diagnostic report as before. But you employee didn't respond...

OMG, it's has been a year and Killer still have not fix this. I had to order the intel 8260 and threw away the terrible Killer 1535 November 2015. I remember contacting Killer last year and they blamed windows 10 for all of their problems.

My laptop, 17 R3 still have the Killer Ethernet E2400, which thankfully does not cause disconnections.

What I find amazing about Kiler E2400 the lastest driver is 9.0.0.37 on January 26, 2016.

The intel 8260 wifi card is last updated on August 21, 2016.

How Killer still in business is beyond comprehension.

Not sure why the new Alienware laptops only carry the rubbish Killer stuffs.

Can you please send in a ticket with the title "Attn: Josh" through our support website so I can follow up on this.  I want to make sure I'm looking at the right ticket so I can avoid asking for steps we've already tried.

www.killernetworking.com/.../contact

I've sent the message with title "Attn: Josh" through the link

www.killernetworking.com/.../contact

Anyway, the name is right. Killer is true killer....killing all network in any area) Everybody knows in my office that I came - routers are just switching off :))

OMG, it's has been a year and Killer still have not fix this. I had to order the intel 8260 and threw away the terrible Killer 1535 November 2015. I remember contacting Killer last year and they blamed windows 10 for all of their problems.

To be fair, others have had a different experience (or there would be a lot more posts about this issue) so while there may be a problem, and Killer/Rivet shouldn't get off scott free, this is probably a complex issue.

My own 17r3 was unusable OOB October 2015, one of the big issues was the Killer 1535 wifi; updating with the then current driver from RIvet fixed it and I've learned over the past year to not update drivers on the 17r3 unless something is actually broken.

In the environment that I use my 17r3 in, (ie, combination of routers and APs, other devices) I have no problems with wifi, it seems rock solid - a couple of weeks ago I transferred about 2TB wirelessly in one transfer with no problems.

However, the OP's issues seem to be harder to resolve than in my case.

So, obviously, YMMV; and I wouldn't bash Killer too hard - and at least they are here trying to help - give them credit. Never saw that from Intel and Nvidia with the early graphics driver issues, and Dell never been forthcoming about the BIOS debacle.

I have the same problem. I purchased my 17 R3 back in August. I'm obviously a stickler about keeping things up to date, so I updated to the Sept. 28 update of the killer network suite. Hardline was fine. Nothing wrong. It was when I went wireless. After about 5 minutes, the wireless connection would just drop entirely. I would always have to be hardlined but when I got the laptop, it worked just fine. Gamed on it for hours and never a drop. I beta tested Killer's sniper software they had and it was the most amazing driver and suite setup I've ever experienced. Anyways, I did look up on their site that it's best to use the drivers that are on the support site because they have been tested and deemed compatible, so i rolled back to that for the time being. My question would be why isn't the drivers compatible in the first place? If they're meant for better performance, why would they post them? I also ran the support assist on the dell software and it said there's something wrong with the network card with that update.

These stories are why I ordered an Intel 8260 card for 29.99 from the Egg for my new AW15R2 Skylake. So worth it to save the headache.

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"

1ms for 5-10 different wireless devices.  

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

I'm glad that you have had good luck, but there are clearly too many driver issues for my liking.