BSOD with Bluesoleil 8

[Ronin51]

I am having an awful time trying to get Bluetooth set up on my new PC. The machine is based on an Asus M4A79XTD mobo and running Win 7 x64 with an AMD Phenom II x4 955 cpu. Originally, I had a Dell SD card reader with an integrated Bluetooth unit. This was from the Dell 531 that I replaced. Everything worked fine. No problems, no crashes, and my Logitech MX5000 Bluetooth keyboard and mouse worked fine.

I could not get my Rocketfish headset to connect. So, I decided to replace the Bluetooth (and card reader) with a new unit. The new card reader did not have integrated Bluetooth, so I installed a Ultra BT dongle. The software that it came with was Bluesoleil 2. Initially it worked, I was able to connect my keyboard and mouse, but even though it recognized and paired with the Rocketfish, it would not connect to the headset. When I checked online, I found that the latest build of Bluesoleil was 8, so I downloaded and installed the latest version as a trial. I connected the keyboard and mouse and started having the BSOD. Windows would launch, the desktop would come up, and then BSOD.

I did a system restore to a point prior to installing the Bluesoleil 8. The BSOD stopped. I installed Broadcom BT drivers. BT Devices shows a BT Bus Enumerator that is working with the latest drivers. My Devices and Printers panel shows three Broadcomm items; BT Com Port (COM3), BT Hands-free Audio, and BT Stereo Audio. I could not get any of my BT devices to pair or connect. I have a 'My BT Places' icon on the desktop, but if I double click it, Explorer crashes and restarts. The Logitech Mouse and Keyboard program does not see a BT transmitter.

I attempted to reload Bluesoleil 8 (the assumption was maybe I had a corrupt file). It installed fine. I managed to get all three devices to pair with the software. As soon as I connected the keyboard - BSOD. Each reboot would result in a BSOD as soon as the desktop was fully up (I assume this was Bluesoleil connecting to the keyboard.) I tried another system restore, which failed. I pulled the BT dongle, got my desktop up, killed Bluesoleil using msconfig, and then uninstalled the program.

I am currently using a wired mouse and keyboard. I have no idea why I am having so much trouble getting a simple BT dongle to work. Any help would be appreciated. Is it possible the MX5000 is incompatible with Win 7 x64? It was working fine with the old Dell card reader/BT unit.

 

[Ronin51]

BSOD with Bluesoleil 8 update

I just wanted to update my previous post. I pulled the BT dongle and deleted all the BT drivers. I then reinstalled the dongle after rebooting and let the default drivers load. I was then able to use the 'add device' function to add my Logitech MX5000 keyboard and MX1000 mouse. I could get the Rocketfish headset to be recognized, but it would not pair. Every time it timed out even though the headset was still in discovery mode.

My system did crash again. When I reviewed the system log I noticed a number of 'critical' events identifying Kernal-power and indicating the system shut down. In nearly every case about 2 events priors was an error related to 'BTHidMgr.sys. That is a Bluesoleil file that remains in the System32 folder even after the Bluesoleil program is uninstalled. I went through the System32 folder and tried to delete any file that was related to Bluesoleil or IVT. We'll if this resolves the problems. There appears to be something rather hinky about Bluesoleil.

Is there a way to search for files that are created by a specific company?

 

[usasma]

Please provide this info so we can see what we can figure out: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Ronin51]

I added the requested files to my original post. I hope I got this right, it's the first time I did this.

My system is based on an Asus M2A79XTD EVO mobo, an AMD Phenom II X4 955 cpu, 4GB of Patriot DD3 RAM, and I'm running Win7 Ultimate X64. There are two 500 GB WD HDDs, two Plextor optical drives, and an external 1TB WD external HD. The graphics card is a NVIDIA GeForce 9500 GT. I'm using the onboard audio - no sound card. As I indicated, my BT transmitter is an Ultra dongle, now running the generic Windows driver and emulator.

The externals are two monitors; a Dell E207WFP, and a Samsung SyncMaster 2220WM, the keyboard is an older BT Logitech MX5000 with a MX1000 mouse. There is also a Logitech Orbit AF webcam.

Since I removed the Bluesoleil software and drivers the system has been stable and everything is working. But, I still cannot get my Rocketfish stereo BT headphones to connect.

 

[usasma]

What happens when you try to install the RocketFish headphones software? What are the exact error messages?
If you can get the software installed, what happens when you try to connect? What are the exact error messages?

The systeminfo report only shows 80 hotfixes installed - please visit Windows Update and get all available updates (don't get Service Pack 1 yet, we'll save that for later).

It also shows that your Bluetooth PAN is setup - but the media is disconnected.

And the BSOD's appear to be caused by the BlueSolei software - so I'd stay away from that for the time being.

If you have AMD Overdrive running, please stop it as it may have issues with Win7

You have lot's of old Bluetooth stuff running on your system, please see the devices highlighted below. You're going to have to replace it with updated versions - or remove them using the program(s) uninstallers. Same thing goes for your sound devices:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
mv61xx.sys             Thu Mar 19 23:48:21 2009 (49C31205)
amdxata.sys            Tue May 19 13:56:59 2009 (4A12F2EB)
PxHlpa64.sys           Tue Jun 23 19:16:35 2009 (4A416253)
BtHidBus.sys           Tue Apr 06 06:31:30 2010 (4BBB0D82)
AtiPcie.sys            Mon Aug 24 04:25:26 2009 (4A924E76)
WsAudio_DeviceS(2).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
WsAudio_DeviceS(3).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
WsAudio_DeviceS(4).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
WsAudio_DeviceS(5).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
GEARAspiWDM.sys        Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys             Wed Jul 15 23:31:29 2009 (4A5E9F11)
WsAudio_DeviceS(1).sys Thu Jul 23 08:04:10 2009 (4A6851BA)
[Color=Red]RtNdPt60.sys           Mon Dec 10 21:49:52 2007 (475DFAD0)[/Color]
AsUpIO.sys             Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys               Mon Aug 03 03:03:16 2009 (4A768BB4)
SBFWIM.sys             Tue Feb 08 06:37:58 2011 (4D512B16)
viahduaa.sys           Mon Jan 11 05:05:18 2010 (4B4AF7DE)
hiber_atapi.sys        Mon Jul 13 19:19:47 2009 (4A5BC113)
hiber_dumpfve.sys      Mon Jul 13 19:21:51 2009 (4A5BC18F)
hidbth.sys             Mon Jul 13 20:06:52 2009 (4A5BCC1C)
LHidFilt.Sys           Wed Jun 17 12:49:39 2009 (4A391EA3)
LMouFilt.Sys           Wed Jun 17 12:49:43 2009 (4A391EA7)
hiber_dumpata.sys      Mon Jul 13 19:19:47 2009 (4A5BC113)
nvlddmkm.sys           Fri Jul 09 17:15:58 2010 (4C37918E)
nvBridge.kmd           Fri Jul 09 17:07:54 2010 (4C378FAA)
SbFw.sys               Tue Apr 05 14:12:59 2011 (4D9B5BAB)
btnetBus.sys           Tue Apr 06 06:31:58 2010 (4BBB0D9E)
btcombus.sys           Thu Aug 26 09:28:08 2010 (4C766BE8)
IvtBtBus.sys           Tue Apr 06 06:31:35 2010 (4BBB0D87)
[Color=Red]btkrnl.sys             Fri Mar 30 00:44:53 2007 (460C95C5)[/Color]
sbapifs.sys            Wed May 11 12:20:27 2011 (4DCAB74B)
btcomport.sys          Thu Aug 26 09:28:04 2010 (4C766BE4)
[Color=Red]btport.sys             Tue Mar 20 13:02:10 2007 (46001392)[/Color]
[Color=Red]btaudio.sys            Thu Mar 22 12:29:54 2007 (4602AF02)[/Color]
btcusb.sys             Wed Jun 23 23:33:17 2010 (4C22D1FD)
LUsbFilt.Sys           Wed Jun 17 12:49:46 2009 (4A391EAA)
btnetdrv.sys           Wed Aug 18 10:18:09 2010 (4C6BEBA1)
VHIDMini.sys           Tue Apr 06 06:31:25 2010 (4BBB0D7D)
mozy.sys               Tue Feb 08 12:28:42 2011 (4D517D4A)
SBREdrv.sys            Fri Apr 29 11:51:13 2011 (4DBADE71)
sbtis.sys              Tue Apr 05 14:12:37 2011 (4D9B5B95)
lvuvc64.sys            Fri Apr 01 01:02:12 2011 (4D955C54)
[/font]

http://www.carrona.org/dvrref.html#mv61xx.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#PxHlpa64.sys
http://www.carrona.org/dvrref.html#AtiPcie.sys
http://www.carrona.org/dvrref.html#GEARAspiWDM.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#RtNdPt60.sys
http://www.carrona.org/dvrref.html#AsUpIO.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#SBFWIM.sys
http://www.carrona.org/dvrref.html#viahduaa.sys
http://www.carrona.org/dvrref.html#hiber_atapi.sys
http://www.carrona.org/dvrref.html#hiber_dumpfve.sys
http://www.carrona.org/dvrref.html#hidbth.sys
http://www.carrona.org/dvrref.html#LHidFilt.Sys
http://www.carrona.org/dvrref.html#LMouFilt.Sys
http://www.carrona.org/dvrref.html#hiber_dumpata.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#nvBridge.kmd
http://www.carrona.org/dvrref.html#SbFw.sys
http://www.carrona.org/dvrref.html#sbapifs.sys
http://www.carrona.org/dvrref.html#LUsbFilt.Sys
http://www.carrona.org/dvrref.html#btnetdrv.sys
http://www.carrona.org/dvrref.html#VHIDMini.sys
http://www.carrona.org/dvrref.html#mozy.sys
http://www.carrona.org/dvrref.html#SBREdrv.sys
http://www.carrona.org/dvrref.html#sbtis.sys
http://www.carrona.org/dvrref.html#lvuvc64.sys

More to follow as I have to research the older drivers and find out what they belong to. I presume that some of the older BlueTooth drivers are from an older version of the BlueSoleil software - so uninstall that completely (you may have to install it, then uninstall it to remove all traces).

Also uninstall your audio stuff - then download and install a fresh copy from the manufacturer's website.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-32370-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 21:21:34.800 2011 (UTC - 4:00)
System Uptime: 0 days 0:55:15.174
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42b65 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  OUTLOOK.EXE
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42b65
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`000000c0 00000000`00000000 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-31964-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 19:21:20.736 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:48.110
*** WARNING: Unable to verify timestamp for BtHidBus.sys
*** ERROR: Module load completed but symbols could not be loaded for BtHidBus.sys
Probably caused by : BtHidBus.sys ( BtHidBus+11ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BlueSoleilCS.e
FAILURE_BUCKET_ID:  X64_0x3B_BtHidBus+11ba
Bugcheck code 0000003B
Arguments 00000000`c0000047 fffff800`02cf40b4 fffff880`06e30400 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-29452-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 19:13:10.396 2011 (UTC - 4:00)
System Uptime: 0 days 0:47:50.159
*** WARNING: Unable to verify timestamp for BtHidBus.sys
*** ERROR: Module load completed but symbols could not be loaded for BtHidBus.sys
Probably caused by : BtHidBus.sys ( BtHidBus+11ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BlueSoleilCS.e
FAILURE_BUCKET_ID:  X64_0x3B_BtHidBus+11ba
Bugcheck code 0000003B
Arguments 00000000`c0000047 fffff800`02cac0b4 fffff880`07178400 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-27549-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 18:20:07.140 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:29.903
*** WARNING: Unable to verify timestamp for BtHidBus.sys
*** ERROR: Module load completed but symbols could not be loaded for BtHidBus.sys
Probably caused by : BtHidBus.sys ( BtHidBus+11ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BlueSoleilCS.e
FAILURE_BUCKET_ID:  X64_0x3B_BtHidBus+11ba
Bugcheck code 0000003B
Arguments 00000000`c0000047 fffff800`02ca40b4 fffff880`07c3d400 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052211-23930-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Sun May 22 18:16:38.317 2011 (UTC - 4:00)
System Uptime: 0 days 0:33:47.080
*** WARNING: Unable to verify timestamp for BtHidBus.sys
*** ERROR: Module load completed but symbols could not be loaded for BtHidBus.sys
Probably caused by : BtHidBus.sys ( BtHidBus+11ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  BlueSoleilCS.e
FAILURE_BUCKET_ID:  X64_0x3B_BtHidBus+11ba
Bugcheck code 0000003B
Arguments 00000000`c0000047 fffff800`02cf80b4 fffff880`0700d400 00000000`00000000
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051911-32073-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu May 19 01:13:40.339 2011 (UTC - 4:00)
System Uptime: 0 days 4:22:29.103
*** WARNING: Unable to verify timestamp for SBFWIM.sys
*** ERROR: Module load completed but symbols could not be loaded for SBFWIM.sys
Probably caused by : ntkrnlmp
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ntkrnlmp
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`03a10bb0 fffff800`00b9c518 fffffa80`09242ad0
BiosVersion = 2102   
BiosReleaseDate = 06/17/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[usasma]

Here's the drivers from above that I didn't have time to research:

Audio devices:
http://www.carrona.org/dvrref.html#WsAudio_DeviceS(1).sys
http://www.carrona.org/dvrref.html#WsAudio_DeviceS(2).sys
http://www.carrona.org/dvrref.html#WsAudio_DeviceS(3).sys
http://www.carrona.org/dvrref.html#WsAudio_DeviceS(4).sys
http://www.carrona.org/dvrref.html#WsAudio_DeviceS(5).sys


BlueTooth drivers:
http://www.carrona.org/dvrref.html#BtHidBus.sys - BlueSoleil
http://www.carrona.org/dvrref.html#btnetBus.sys - BlueSoleil
http://www.carrona.org/dvrref.html#btcombus.sys - BlueSoleil
http://www.carrona.org/dvrref.html#IvtBtBus.sys - BlueSoleil
http://www.carrona.org/dvrref.html#btkrnl.sys - BlueSoleil
http://www.carrona.org/dvrref.html#btcomport.sys - BlueSoleil
http://www.carrona.org/dvrref.html#btport.sys - Broadcom
http://www.carrona.org/dvrref.html#btaudio.sys - Broadcom
http://www.carrona.org/dvrref.html#btcusb.sys - BlueSoleil

 

[Ronin51]

BSOD with Bluesoleil 8 update

Wow - that's a lot of stuff. How could a clean install of Win7 on a brand new system get so screwed up just trying to get a pair of Bluetooth headphones to work?

OK, this is good, because I do want to try to understand this better.

First, I manually went through the list of .sys files. The following is a blow by blow of the results of trying to update the various files. Many were already the latest files, some I did update, the Windows files I could not find - those are typically shown in red.
1. Created restore point
2. Updated VIA Audio from Asus website - old driver 6017900, new is 6018300 (successful - interesting the old driver 6017900 is shown as a 2010/02/08 Beta Version - the new drive has a 2010/07/15)
3. mv61xx.sys Marvell Thor Windows Driver; the Asus shows this a ESATA Controller Driver, the old driver is dated 2009/03/19, the new driver was 2010/07/28 (successful on second try). After rebooting the system Storage Controller Marvel drive is back to the 3/20/2009 version, even though the newer version indicated that it loaded successfully???)
4. amdxata.sys shows 'Windows Update' with no link, can't find it.
5. PxHIpa64.sys (Roxio) -changed .sys to .bak
6. ATiPcie.sys (Ati Radeon) - My graphic card is NVIDIA - I updated the to the latest NVIDIA drivers.
7. GEARAspiWDM.sys (GEAR - probably related to iTunes) old version was 2009, new is 2/5/2010
8. ASACPI.sys (Asus all the drivers are the latest available - the carrona.org record indicated this was a BSOD maker for Win7 - so far I haven't had a problem as long as BlueSoleil wasn't loaded.) No change was made.
9. WsAudio_DeviceS(1).sys - no carrona.org link. Wondershare, might be part of a video converter program I used once. Not related to any current programs that I know of.
10. RtNdPt60.sys (Realtek) I already installed the latest HD Audio Codec Driver
11. RtNdPt60.sys directed me to Realtek, latest download for HD Audio; REaltek HD Audio Driver R2.6 (successful)
12. AsUpIO.sys (Asus monitoring program - PC Probe II, I suspect. It is the latest update)
13. AsIO.sys (Asus monitoring program - PC Probe II, I suspect. It is the latest update)
14. sbfwim.sys (Sunbelt software Vipre antivirus and firewall installation) - recently reinstalled from their website.)
15. viahduaa.sys (VIA HD Audo - the newest driver was installed #2) The VIA website suggested downloading drives for Asus - which I already have done.
16. hiber_atapi.sys (no link - Windows Update indicated)
17. hiber_dupfve.sys (no link - Windows Update indicated)
18. hidbth.sys (no link - Windows Update indicated) MS BT Miniport Driver for HID Devices
19. LHidFilt.Sys (Logitech SetPoint HID Filter Driver) Latest software is installed.
20. LMouFilt.Sys Latest software is installed.
21. hiber_dumpata.sys (no link - Windows Update indicated)
22. nvlddmkm.sys (NVIDIA Video drivers) updated to latest drivers 270.61 desktop Win 7 64bit.
23. Device Manager showed both optical drives were disabled.
24. Undid #5; renamed PxHIpa64.sys back to .sys (OK, I'll stay out of System32 from now on)
25. Reboot
26. Error: Plexradar - Cannot Create System Shell Notification Icon, but optical drives are functional again. But, both optical drives are working properly - again.
27. nvlddmkm.sys (NVIDIA Video drivers) updated to latest drivers 270.61 desktop Win 7 64bit.)
28. nvBridge.kmd (NVIDIA Video drivers) updated to latest drivers 270.61 desktop Win 7 64bit.)
29. SbFw.sys (Sunbelt software Vipre antivirus and firewall installation) - recently reinstalled from their website.)
30. sbaphd.sys (Sunbelt software Vipre antivirus and firewall installation) - recently reinstalled from their website.)
31. LUsbFilt.Sys (Logitech SetPoint HID Filter Driver) Latest software is installed.
32. btnetdrv.sys (Bluetooth PAN Network Adapter Driver (IVT BlueSolei) May not be compatible with Win7)
33. btkrnl.sys (Bluetooth Network Protocol Stack - BlueSoleil http://www.ivtcorporation.com/download/BlueSoleil_Download.php) file only showed up in temp folders - deleted
34. vhidmini.sys (most likely an IVT Corporation BlueSolei Bluetooth HID Mini driver BlueSoleil - Bluetooth Software,Bluetooth Driver,Bluetooth Dongle) - deleted
35. mozy.sys (online backup service - recently reinstalled)
36. SBREdrv.sys (Sunbelt software Vipre antivirus and firewall installation) - recently reinstalled from their website.)
37. sbtis.sys (Sunbelt software Vipre antivirus and firewall installation) - recently reinstalled from their website.)
38. lvuvc64.sys (Logitech USB Video Class Driver WebCam - carrona.org link just brings me to Logitech site - webcam - reinstalled full software package)


Rocketfish installation - Devices and Printers - Add a Device - start RF discovery -


This happens while the headset is still in discovery mode.

"The systeminfo report only shows 80 hotfixes installed - please visit Windows Update and get all available updates (don't get Service Pack 1 yet, we'll save that for later)." I don't know how to do this. I've run 'Check for Updates' multiple times. Everything that has been identified has been installed.

"It also shows that your Bluetooth PAN is setup - but the media is disconnected." I don't know what this means - my BT keyboard and mouse are working fine.

"And the BSOD's appear to be caused by the BlueSolei software - so I'd stay away from that for the time being." On this we fully agree, when I uninstalled BlueSoleil, the BSOD stopped.

"If you have AMD Overdrive running, please stop it as it may have issues with Win7" AMD Overdrive utility is installed, but I have not used it.

"You have lot's of old Bluetooth stuff running on your system, please see the devices highlighted below. You're going to have to replace it with updated versions - or remove them using the program(s) uninstallers. Same thing goes for your sound devices" This is confusing. I did a clean install of Win7 on a new machine. The only BT devices I have running are my MX5000 keyboard and my MX1000 mouse. If there are BT drivers on the system it is probably because I installed BlueSoleil 2 and BlueSoleil 8 a couple of times. Later I installed a Broadcomm BT driver. I also installed some Rocketfish software. But, again, currently the only BT devices running are a keyboard and a mouse.

My primary failure has been that I have not been able to locate the Windows drivers in your list to update. I keep getting referred to using Windows Update, which you've suggested avoiding. (I did try it a couple of time and found that even though it indicated the driver was up to date, there was in fact a newer driver on the software website.)

Given the problems that I have had, I really don't want to reinstall BlueSoleil just to uninstall it. I'd rather hunt down the files one at a time and delete them. The system is running without major problems. I want to get my Rocketfish headset to work, but I don't want to got back to BlueSoleil induced BSOD.

Any thoughts on how a new installation could get so screwed up in a couple of days?

 

[Ronin51]

I looked for some of these files on my system:

BlueTooth drivers:
Driver Reference - BlueSoleil not found
Driver Reference - BlueSoleil not found
Driver Reference - BlueSolei lnot found
Driver Reference - BlueSoleil found /System32 - deleted
Driver Reference - BlueSoleil not found
Driver Reference - BlueSoleil not found
Driver Reference - Broadcom found only in Temp folders - deleted
Driver Reference - Broadcom found only in Temp folders - deleted
Driver Reference - BlueSoleil not found

It seems that all but one of the BlueSoleil files had been deleted - there all gone now. I'll look into the Audio files tomorrow.

 

[Ronin51]

I made a mistake when I attempted to answer your question about the 'exact error message' when I try to connect my Rocketfish RF-MAB2 headset. I forgot you can't just cut and paste a picture into the post.

Devices and Printers > Add a Device (put RF into discovery mode)>after a few seconds the "Bluetooth headset" is found (a phone BT earpiece icon pops up) >highlight the icon and click next > after about 20 seconds > "Adding this device to this computer failed: t took too long to add this device. Devices usually stay in discovery mode for only a short period of time to prevent power drain." (When this message pops up, the headset is still in discovery model.)

Is it possible that the cheap Ultra BT dongle that I have installed does not support A2DP, which the RF headset requires? BTW; I know the RF headset works fine, because I use it with my Droid X for music.

 

[Ronin51]

I looked up the drivers 'WsAudio_DeviceS(1).sys [1 through 5]. These are all WonderShare drives. I visited their website and do not recognize any of their software. I have on occasion used PDF converters, but none of the programs listed. Could these drivers been included in some other software? Can I just delete them?

 

[Ronin51]

I found this posted in a 2009 post on this forum:

Broadcomm v6.2.0.9700, unlocks A2DP for Win 7 x86 and x64. http://www.kf4ytr.com/drivers/BTW_6.2.0.9700.rar

I also found something that might explain some the problems on an A2DP.info site.

Installing and Configuring Widcomm Desktop Drivers for A2DP Bluetooth Stereo Playback - A2DP, Bluetooth Stereo Headsets, Bluetooth Headphones, Wireless devices, Gadgets Review, Nokia Headsets, Plantronics, Motorola, Jabra, Sony, iTech

The information seems to be a bit dated - it doesn't discuss Windows 7 specifically. But, it does state that A2DP is not supported by Windows and needs to be added using either BlueSoleil (Ugh) or Widcomm software. It also states that Widcomm and native Windows BT drivers interfere with each other. It gives instructions how to remove the Windows BT drivers, before installing the Widcomm software. The instructions are specific to XP, but I'm wondering if this is related to what's currently preventing the Rocketfish headset from working on my computer.

One other thing. The new Targus BT dongle that I ordered (not here yet) is advertised to be compatible with Windows 7 and support A2DP. The software that comes with it is Widcomm.

 

[Ronin51]

I did a little more reading on the A2DP.info site. They discuss the proper installation of BlueSoleil software. And again, recommend disabling the native bth.inf and bth.PNF files first to avoid interference. Could the root cause of these problems, including the BlueSoleil BSOD, be caused by incompatibility between the Windows native BT drivers and newer BT drivers from BlueSoleil and Widcomm? I looked at the properties of bth files. Both had creation dates of mid 2009.

 

[usasma]

DO NOT worry about the Windows Update referrals - that means that you can only get what Windows Update has. So if it doesn't have an update, then you don't need to update it.

The Windows Update thing only applies to Microsoft Windows built-in drivers. Any drivers that aren't Microsoft Windows drivers shouldn't be updated through Windows Update. Normally this only happens once - when you're installing Windows while connected to the web (and Windows goes out and gets the drivers that it needs from Windows Update). After that, you'll only see the non-Microsoft drivers if you choose any of the optional updates at Windows Updates.

For quite some time the 2005 version of ASACPI.sys was installed on systems when Windows was being installed. Later on, after a significant number of updates, that version caused BSOD's galore - and it took us a while to figure out where it was coming from. The fix was to update it to a later, Win7 compatible version. That's why we make the distinction between Windows drivers and non-Windows drivers.

More to follow after I feed the dogs.....

 

[usasma]

I have no idea about the Audio drivers. Let's see what they have to say with the next BSOD. FYI - we identify older drivers, NOT defective drivers (in the Older Drivers listing). So that means that the older drivers may not be causing problems - bur rather that the older drivers are more likely to cause problems.

Too many pieces of different BlueTooth stuff installed to make sense of all this.
So, leave the Windows BlueTooth drivers alone and see what the system does.

What was the purpose of adding the BlueSoleil 2 drivers? I wonder if they were the cause of the issues. Most BlueSoleil 2 drivers date from 2007 or earlier.
But regardless, in the future only add one new set of bluetooth drivers at a time - and then test to be sure that they're working properly.

Beware of trying to apply XP fixes to Vista/Win7 systems - the differences are liable to make for problems. Be sure to set System Restore points and have your Startup Repair disk handy (in case you can't boot into Windows). Also, investigate the Knowledge Base/FAQ's at each of the different BlueTooth programs' website to see if the issues that you've identified have been fixed/changed with the newer OS's (and only use versions that specifically state that they are compatible with Win7).

In particular I noticed this:

One other thing. The new Targus BT dongle that I ordered (not here yet) is advertised to be compatible with Windows 7 and support A2DP. The software that comes with it is Widcomm.

And I wonder if Widcomm has fixed those issues in the latest version that they've released?

 

[Ronin51]

"Too many pieces of different BlueTooth stuff installed to make sense of all this.
So, leave the Windows BlueTooth drivers alone and see what the system does."

So far the system has been stable. No more BSOD. The BlueSoleil software does appear to have been the culprit. Since it was removed I have not had a crash. I've been up and down quite a few times; all normal and uneventful.

"What was the purpose of adding the BlueSoleil 2 drivers? I wonder if they were the cause of the issues. Most BlueSoleil 2 drivers date from 2007 or earlier."

I replaced an old internal SD card reader that had built in BT with a newer Ultra BT dongle. The new dongle came with BlueSoleil 2 software that I loaded from a CD. When that wouldn't connect to the Rocketfish headset, I tried the newer BlueSoleil 8 from the website. (It's kind of funny, because I replaced the original internal BT with the dongle because I couldn't connect to the headset and I assumed it was just the old BT hardware.)

"But regardless, in the future only add one new set of bluetooth drivers at a time - and then test to be sure that they're working properly."

Hopefully, I've learned a valuable lesson. I do often set restore points before I do anything significant. I just got in a hurry. I think I also couldn't imagine just adding a BT dongle and some software could turn into this kind of mess.

" Beware of trying to apply XP fixes to Vista/Windows 7 systems - the differences are liable to make for problems. Be sure to set System Restore points and have your Startup Repair disk handy (in case you can't boot into Windows). Also, investigate the Knowledge Base/FAQ's at each of the different BlueTooth programs' website to see if the issues that you've identified have been fixed/changed with the newer OS's (and only use versions that specifically state that they are compatible with Windows 7)."

For now, I'm going to give things a rest and see if any more BSOD events pop up. I'll settle for using my speakers to play music. While I wait for the Targus BT dongle, I'll do a bit more digging into the compatibility of Widcomm and BlueSoleil software with Windows 7. It looks like I'll need one or the other to get the BT headset to work.

 

[Ronin51]

Happy ending.

I pulled the cheap BT dongle and replaced it with a Class 1, Azio BTD211. Using the Win 7 native drivers and the 'add device' utility, I was able to connect my Logitech MX1000 mouse, Logitech MX5000 keyboard, and my Rocketfish stereo headphones (which was the the device that started this entire saga). Everything works, I haven't had an BSOD issues as long as I stay with the native BT drivers and away from Bluesoleil.

One other thing; the new Azio dongle did come with a disk that had Bluesoleil 5 software. I thought I would try one last time. After I installed Bluesoleil and rebooted, just after Windows loaded ---- BSOD. I tried two more times - same thing. I restored the system pre-Bluesoleil -- no more BSOD. I know people use this BT software, but there is something in my system that will not tolerate any version of it from 2 to 8. It will have to remain a mystery, because I'm just happy to have a stable system and my stereo headphones working.

Thanks for the help in getting this issue resolved.