Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 7 64 Bit Bluetooth issue when waking from sleep


  • Please log in to reply
1 reply to this topic

#1 JamesGrey

JamesGrey

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:41 PM

Posted 03 November 2014 - 07:06 PM

I am stumped.

 

The Bluetooth service BTHSERV, runs fine when my system is started, my Bluetooth devices all connect and everything is fine.

 

However if my PC sleeps, upon waking the Bluetooth service no longer functions and no devices connect.

 

If I try to restart the service, nothing happens it just says trying to stop. The only way to get BTHSERV to stop and restart is to completely reboot the PC.

 

I ran a scan and all the files on windows check out as okay.

 

I even have the Bluetooth radio set that it will not turn off to conserve power but this makes no difference.

 

It appears that the service is the issue.

 

This is a brand new motherboard, and a fresh install of windows 7 64 bit with all updates.

 

Small Update: If I put the PC to sleep twice when it wakes up the Bluetooth service starts to work again. This is strange. Must be a better solution though.

 

Any help is very much appreciated.


Edited by JamesGrey, 03 November 2014 - 08:54 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,386 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:41 PM

Posted 04 November 2014 - 01:28 PM

My guess would be a damaged or poorly written driver.

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users