GT60-2OC-022US Bluetooth Recognized but Does Not Pair

Hey all. I picked up a used GT60 a few months ago. I love the laptop so far, and everything works perfect except for the bluetooth. The bluetooth device is recognized in device manager, and by all accounts in windows appears to be working properly. It just never discovers another device in pairing mode, and is never discovered by other devices searching nearby.

It is currently running a clean install of Windows 10 Pro x64, otherwise it's all stock. I have tried letting Windows find drivers and using the drivers provided by MSI. Both have the exact same issue. It had the exact same issue on Windows 8 before I reformatted, so it doesn't appear to be a software issue. I could be missing something, but I'm not sure what. I couldn't find other instances of this exact issue by searching, just other general bluetooth issues. Hopefully someone has an idea.

Thanks!

 

Try the most current drivers from the vendor (i.e. if you have an Intel WLAN card, go to Intel's support page for your card and get the latest driver). Usually the stock drivers work (or they should), but I've seen a couple of isolated situations where an updated driver resolved pairing issues.

 

What WiFi card do you have in the laptop?

 

I believe the default choice would have been the Killer N1202 a/b/g/n. The Intel Wireless-AC 7260 was an option.

Killer Drivers: http://www.killernetworking.com/support/driver-downloads

Intel Drivers: https://downloadcenter.intel.com/product/75439/Intel-Dual-Band-Wireless-AC-7260

 

Drivers are a start. You may want to check the cable connection at the card, too.

 

Sorry! Didn't see all the posts. I did some more checking, and it definitely appears to be a driver issue. I just finished installing Linux as a second OS, and decided to try Bluetooth in there. It worked and paired just perfectly there. Saw my phone instantly and my phone saw it. So Linux has working drivers, lol.

It is the Killer N1202. The Bluetooth registers as a Qualcomm QCA61x4.

 

Might mention that, when I bought my GT70-2OC, I chose the AC 7260 so I could play with WiDi. And while there were some driver issues for a while, it seems to be a problem that has been remedied. Something you might consider (cheap part, easy installation).

http://www.amazon.com/Intel-7260-HM...00MY9S692/ref=cm_cr_arp_d_product_top?ie=UTF8

 

Well, thanks to you guys mentioning it is a Killer network card, I checked the Killer site for drivers where I had only tried the MSI site and Qualcomm site before. MSI didn't have the most current version and Qualcomm just says they don't produce the drivers for end-users. Downloaded and installed the Windows 10 drivers from the Killer Neworking site, and it works perfectly. Finds and pairs with devices perfectly. I sent a file both ways no issue, then connected to a Bluetooth headset and listened to music through the headset no issue. Glad it was as simple as a driver.

To anyone with issues with this card and 10, I'd try going here and installing their drivers if you haven't already:

http://www.killernetworking.com/support/driver-downloads/category/bluetooth-drivers

Thanks again everyone.

 

Gotta say I love this laptop so far. I know it's a few years old at this point, but I just came from a G50vt with a 9800m GS. With that I was scraping by at low-medium settings on BF3 at 1366x768. Not horrible for the old card, but with this I'm doing everything on Ultra in BF4 at 1080p. GPU only gets up to 75ish at graphics heavy points with the fan on auto, and almost never goes above 55 with the fan on max (Cooler Boost or what-not). Media creation and encoding with CS6 is night and day difference as well, and it's still all stock.

 

Well done, the driver is frequently updated on component manufacturer's website that's why we don't always rely on system manufacturer's driver page.

 

Great! I seem to recall Killer making mention of either a prevalent Bluetooth issue, or maybe it was a WLAN problem... but in any case, I recall some scuttlebutt that they admitted to and resolved with a driver revision. Maybe you ran into said issue. Anyway, also glad here that the driver got you back up and running.