Killer Wireless 1535 Bluetooth Stopped Working

So I just got my 17 today and was having the great fun of getting all the drivers and windows up to date. I just completed the Windows 10 Creators Update install and my bluetooth stopped working. After trying to reinstall the drivers a number of times i decided to just roll back the creators update only to discover that i am still unable to use bluetooth. Right now it is not seeing any devices as discoverable. I verified with my phone that they are ready to pair and apart from just starting my windows install over i am unsure of what to do.

 

Reinstall BT drivers but this time, use drivers for Windows 7 as it installs some extra drivers which are useful.

 

I am currently trying this to get my Bluetooth working again with the same problem (except I didn't roll back). It doesn't seem to be working for me though when trying the W7 Version

 

It's highly likely due to the Creators Update of Win10, as hardware is not fully functional. Can you try rolling back to the Anniversary update and see if BT works?

Sent from my SM-N900 using Tapatalk

 

Funny thing, before I saw this post my C: SSD was low on space and a popup came up showing me where a lot of it was being used, which the old Windows 10 was using. So I can't go back even if I wanted, but the guy above me says that didn't help him anyway

 

try this driver http://www.killernetworking.com/driver-downloads/item/1525-1535-1435bt-w7

 

kqmaverick,

I am with Rivet Networks, the company who creates and supports the Killer products. We have seen a few cases of this reported lately with the CU. We have confirmed that this is due to non-enumeration by BIOS/motherboard. This can be fixed by draining power to your machine fully. There are 2 ways to do this:

1. Battery Drain reset: Let the laptop use all battery power, thus emptying the battery and allowing power to the motherboard to actually allow a reset of the device enumeration

2. Unplug power and disconnect the battery: The Alienware notebooks have their battery connector in a easy to access place, usually only requiring removal of 2 screws to remove the bottom access panel. You can then disconnect the battery, accomplishing the same result as #1 without the need to take time to drain the battery.

Leave battery drain/disconnect for a few minutes, then reconnect/power on. Bluetooth should then show up normally.

Regards,
Thomas
Killer Networking

 

So is this going to be the fix every time the Bluetooth stops working? I mean its better than No fix... but I wouldn't want to have to fully drain it or open it to fix it every time yaknow haha

 

illuMinniti,

I would surely hope that this doesn't occur every again. We have only recently started getting a small number of reports of this, and in every case it seemed to be after the Windows 10 Creators Update.

Regards,
Thomas
Killer Networking

 

Sorry for the late reply, i wound up doing the above on my own right after i posted this and forgot to update the thread. I haven't had any issues since i did a power drain.

 

I have a three month old desktop computer. Motherboard Gigabyte GA-Z270X-GAMING 9 (Killer 1535). It came with windows 10 and bluetooth fully functional. I reinstalled windows 10 the day after receiving the computer (BEFORE Creators Update) and bluetooth stopped working since then (i.e. three months ago). I would have thought it was a hardware problem shouldn't I have seen it working the first day. I tried almost everything to fix the issue with no result (including latest Killer drivers). I even contacted Gigabyte support but they just told me to reinstall drivers (what an usefull advice!!!).

Thankfully I found your post about draining the battery. Although this is a desktop computer I decided to give it a go. I unplugged the power source and left it for about half hour. Then I plugged it again and... great!!!! Bluetooth just came to live! No configuration required. It was there as it should have always be!

But please, bear in mind this problem was there BEFORE Windows 10 Creators Update.

Please share this experience with your colleages so you can help more users.

Thank you!

 

I apologize for bringing up this post but i believe the issue is not resolved by this method. Fortunately it is a quick fix but the problem comes back. I have done the battery(laptop)/power supply (desktop) drain as it was suggested and it fix my problem temporarily. It worked for a couple of reboots but eventually the problem came back. Since this thread was created back in may is there now a solution?

 

Have you tried BT drivers for Win 7?

 

Actually just as i was making this post i decided to try the official website for the Killer Networking, and it seems this is a common issue for them. They have a post on their site that has some nice troubleshooting for this issue.

http://www.killernetworking.com/driver-downloads/kb/faq/31-bluetooth-missing-from-device-manager

so far I tried their troubleshooting steps and it has fixed my issue for the time being. It seems to not be a problem with the drivers and more of a problem with the system recognizing the chip and all.

i appreciate your speedy reply.

 

I suspect its a loose antenna cable check that black and white cables.

 

I suspect it is a deeper problem than that. If the cables were an issue then it wouldnt be fixed by the troubleshooting steps above. its more of a BIOS or motherboard not recognizing the device at boot.

 

Been very inactive but I got a email notification for this. I never let my laptops battery fully drain, however the Bluetooth on my laptop is working fine. There has been many driver updates, hopefully it was due to one of those. Maybe it randomly fixed itself, who knows. I just hope they have a better "fix" than to let the battery drain, someday. I know it works because I use the laptop Bluetooth for Xbox One S controllers and I use a ASUS USB dongle for PS3 controllers

 

Christopher Bello hit the nail on the head. The issue is actually an issue with the UEFI BIOS architecture, Windows 10, and the M.2 slot standard. You can see it in all kind of M.2 Wi-Fi adapters, and even different keyed devices, like SSDs. The solution comes from a properly updated BIOS, chipset driver, and operating system. However, once you have updated all of that, sometimes you do still have to do the power drain to get the device to re-enumerate. From there, if the issue returns, it's best to contact the mainboard or machine manufacturer as they need to know that their BIOS or chipset drivers aren't enumerating the M.2 slot.

If the issue were anything but the BIOS or operating system completely not powering or enumerating the M.2 slot, then the Device Manager would list the device as an "Unknown Device" or something similar. It wouldn't just vanish.

Edit - The KB article wasn't due to an upswing in reports in this issue. Reports of this issue are actually declining as BIOSes get updated and the Fall Creator's Update didn't seem to cause an explosion of them. The KB article is because we're building a comprehensive KB.

--Anthony with Killer Networking