Event ID 18 - BTHUSB Problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all. I'm having a problem during my Windows startup (using XP SP2) and
it's driving me insane. During the boot, my taskbar will completely freeze
for a good three minutes, hence I can't hit the startbutton or use any of the
quick launch buttons. I can use icons on the desktop fine, but the entire
taskbar freezes and then starts to work after about three minutes. I've
checked the log and narrowoed the problem down to this error:

"Windows cannot store Bluetooth link keys on the local transceiver because
it cannot determine whether proper security is enabled for the device."

The source of the problem appears to be BTHUSB. I checked on Microsoft's
site and they say this problem can be ignored, but clearly it's causing my
boot to freeze, and I've tried just about everything to fix this. I rarely
use Bluetooth (occasionally I do), but I've deleted all my bluetooth links
from Control Panel, unchecked all the options, even disabled bluetooth in
device manager and the error still occurs. Any help would be GREATLY
appreciated. Thanks!
 
I do not think that the bluetooth driver is causing the problem. Try using
verifier.exe from the Run prompt and select this driver. I doubt anything
useful will come from this, but an error might pop up indicating some memory
issues. Maybe. To be absolutely sure that the driver is not faulty, try
temporarily moving it out of the windows\system32\drivers folder.

I personally think that this is a Windows File Protection issue because XP
does a "quick" scan at boot I believe. The UI features that you talk about
are usually hung up during this period. Check up on this possibility.
 
Thanks for the reply, Will. I followed your advice and tried moving the file
out of the system32\drivers folder, and the error still occured (which I
don't understand; how can the service be starting if I took the file out of
the folder?), so the "hanging" problem was still there. I looked into the
Windows File Protection; more specifically, I disabled the Windows File
Protection (via the registry) and I still continue to have the problem. Any
other suggestions? I greatly appreciate the reply, though this problem is
becoming a huge nuisance.
 
Back
Top