Bluetooth connection failures

[jmm]

Hi! I got a Logitech BT receiver (to replace an old Anycom Bar-10 that used to work like a charm but died ) wired to a stereo, and the idea is for my laptop to connect to it on startup so that all sounds go to the stereo.
My problem is that I often and unpredictably get device connection failures on startup, which entails restarting my machine, sometimes even twice (so far there is no failure after the second reboot). The failures can manifest either as the Logitech being disconnected in the Sound Manager or even disappearing from it (in which cases the built-in speaker system takes over).
There does not seem to be any problem with the driver, which I reinstalled many times.
I tried monitoring the Event Viewer, which does not reveal any obvious issue differences whether the connection succeeds or not.
I tried saving a boot time log with Systernals' Process Monitor but the result is a major headache with 2 million events some of which with issues not particularly related to bluetooth.
BT services (Bluetooth Support Service, which starts Handsfree Headset Service) appear to run OK both in success and failure conditions.

Therefore, my question is: is there any way to monitor startup to track (and hopefully fix) faulty events related to this issue? BT device connection appears to occur (or fail!) between the black "Starting Windows" screen and the blue "Welcome" screen (I know because there is a little blue light that goes on on the Logitech when connection succeeds).

Any help/ideas greatly appreciated!
JM

 

[ICIT2LOL]

Hello JM mate just so I have it right the sound system is connected BT and you are using a dongle for the connection and it does not work until after you reboot the system ??

Now if you haven't already can you please run these for starters and the sfc best run for three consecutive scans.
SFC /SCANNOW Command - System File Checker - Windows 7 Help Forums
Disk Check - Windows 7 Help Forums < if necessary include the /f and /r in the command line as per Option2

if no fix then try these
SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Malwarebytes | Malwarebytes for Windows
AdwCleaner Download
ADW download from bleeping computer delete any rubbish found with the malware scans
NB If anyone who has Kaspersky as their security they may find it will not like ADW running and to stop the nagging just temporarily disbale the Kaspersky while one runs ADW

Out of interest just what antivirus are you running??

 

[jmm]

The Logitech BT receiver is RCA-connected to the sound system.
I ran sfc /scannow 3 times from Windows and also once at boot and got no integrity violation.
I ran chkdsk /f /r and got 588 unused index entries cleaned + "Fixed errors in the volume map + Windows made corrections to the file system".
The connection failures are totally unpredictable but these days I seem to be in a lucky series with no failure for the past 10-15 startups... So I think I can live with that, just having to reboot once or twice when failures do occur. Perhaps also the above repair with chkdsk fixed the issue? I forgot to mention I do have 24 KB in bad sectors, but I've had those for years without any obvious issue (unless every little glitch I occasionally get is due to those bad sectors?).
I use Avast antivirus and MBAM for malware. I did download the installer for AdwCleaner, but I wonder if I should use it given that MBAM is pretty reliable...
Thanks a lot for your help anyway!
PS: I live in France and go to the USA twice a year. So this summer I did buy an Insignia BT dongle at Bestbuy, thinking of resolving the problem that way. As I was able to connect my Android phone to it I thought it was OK. Wrong! Returning home I found out that the dongle was unable to discover any of the BT devices I have. Why it was able to detect my phone, I have no idea, but now it's too late to return it to Bestbuy. From what I saw in forums, the dongle needs a driver that is no longer available!!! Never buy that "pos"!

 

[ICIT2LOL]

Ok mate well just as a by the by ADW was acquired by MBAM some time ago and it was originally a French software site and not wanting to sound patronising it is a very good scanner and will pick up stuff that other softwares will not. The same goes for the SAS too it does catch a few malwares and a lot of Adwares that like cookies will clutter you devices I use SAS on a regular basis as one does with CCleaner too.

Now the chkdsk with the /r switch may have repaired the faults but it isn't something that you cannot run again it is a system tool as you know so can do no harm.

Now just a little something you can try if you ever have little problems like this with drivers is to temporarily disable the AV and then turn it back on again once the driver is installed and a full scan will soon pick the driver up if it is bad.
PS
Just a little something that will make your machine a little faster and more efficient is this Optimize Windows 7 - Windows 7 Help Forums
It is my bible when installing an OS on my machines and also when I am fixing friends and family machines too.
Now if you go through it slowly you will find lots of tweaks and they are all really thoroughly done by the authour Brink a fellow who is in my mind brilliant and if you need to ask questions he is just the most obliging person around.
The other thing is that you may lose some of the "bling" such as transparency (you don't have to I find it unnecessary) and all the tweaks are reversible.
If you do get stuck just post back in that tutorial and you will get help. Another bonus using this tutorial is that it helps you find your way around your machine and Windows 7!
Just one tip I would say you start with is do this Registry - Backup and Restore - Windows 7 Help Forums do this and it will save you a lot of grief if you are ever doing things in the registry and even if you don't it is a good back up to have if your system ever gets corrupted.
(pretyped to save time)

 

[jmm]

Thanks for the Brink list! I did a few tweaks and we'll see if it helps...
I suspect BT failures might be related to timeout issues, e.g. when startup is somehow overwhelmed with stuff. If that's the case, I'd be interested in finding out what BT feature(s) is/are involved during connection and how timeout can be changed (if that makes any sense).
Thanks again for your time!

 

[ICIT2LOL]

No worries and I think you will find some of the tweaks will at last give you a faster start up and shut down if nothing else. The other of course save a lot through pruning the effects out a bit freeing up memory and the system in general.

The BT well I have found it to be quite finicky at times for example this machine I am on now worked fine a with an el cheapo BY mouse and 7 yet not with some of the more recognised (and expensive) brands yet when I switched to 10 that same mouse would not hook up and took yet another el cheapo purchase to get it going again. So I think that sometimes it is the system rather than the devices themselves but I agree it is very frustrating. Having said that I do like to have as many USB ports available to me as opposed to having easily broken dongles fora wifi mouse hanging off the machine.
The time out feature again I think is more system related than the hardware but just how do you pin that one down??

 

[jmm]

End of the lucky series: couple of failures on startup yesterday! Fine after first reboot though...
I got a boot ProcMon file recorded before/during/after failure. I'll keep it for a few days in case someone would like to take a look at it, though I'm not sure how to transmit it as it's 1.1 GB. In it I can see several BT-related issues such as "Name not found", "Buffer overflow", "No more entries" or "Fast I/O disallowed", meaning there could be timeout and request conflict issues as well... In the end, I'm thinking that even if I found the faulty process I wouldn't know how to fix it. I don't think it's possible to "fix drivers" (which makes me think this post could/should now be moved to "Drivers"?). (The driver for the Logitech device uses 3 files: bthav.sys, drmk.sys and portcls.sys.) It's true that my old machine's BT radio uses BT 3.0 (no way to update), and most devices now are BT 4.0, so perhaps this is the root of the problem and the best solution would be for me to find a BT-3.0 receiver, such as Anycom Bar-10. Ebay? (suggestions welcome).
I'll consider this post as not solved/not solvable...