I have exactly the same issue on my i9400. I use BT with my SE W810i mobile phone. Data transfer and remote control work perfectly, but when I try to use the virtual COM-port (tried it with the programm "My Phone Explorer"), I get the same Bluescreen as you. I thought it had to do with the programm and didn't worry about it as the other BT functions work fine.
More details... I still need this resolved... help??
I've been receiving the 'infamous' stop error IRQL_NOT_LESS_OR_EQUAL. I can
get it to happen EVERYTIME i do the following...
-I open COM 9 from within a VB6 project (COM 9 is my bluetooth
communications port) The port opens fine...
-if I perform a .output to the port, the PC blue screens instantly
I can perform 'other' bluetooth operations fine...
below is my crash info..
I've uninstalled bluetooth drivers, reinstalled... performed a Windows
repair install (XP Pro SP2)... been back and forth with Dell support
(not helpful)....
help?
-----------------
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121806-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Dec 18 11:40:57.000 2006 (GMT-6)
System Uptime: 0 days 0:13:51.354
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Unable to load image btport.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for btport.sys
*** ERROR: Module load completed but symbols could not be loaded for
btport.sys
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {ffdf, 2, 1, 806e4a8e}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : btport.sys ( btport+3f9c )
Unfortunately, there's no 100% legal way to solve the problem. The Toshiba Bluetooth stack is junk, simple as that.
The WIDCOMM stack works much better, 5.somethingorother.2100 is the latest version that will still work with CSR-based Bluetooth chipsets such as the 350. (Or did you say the 355? I think that's Broadcom-based and may work with newer WIDCOMM stacks). Unfortunately it can't legally be used with the Dell 3xx modules. There are ways to get them to work, but not in a legal manner. :( That's all I can really say, other than that Google is your friend.
I believe its a deeper problem. (irq conflict of some sort) but not sure..
any help/thoughts??
Hmm, the description page doesn't specifically say it is WIDCOMM, but the version number does look like it's a WIDCOMM version number.
This is the first time I've seen someone having Bluetooth bluescreen issues with non-Toshiba stacks (typically one would see "TOSRFUSB.SYS" somewhere on the bluescreen.) I know WIDCOMM has solved all Bluetooth-related bluescreens on my E1705. (The Dell 350 on my E1705 came with a Toshiba BT stack.)
As to IRQ conflicts - Not likely, if there are it would affect other USB devices too, as the Bluetooth modules are basically USB dongles in a special form factor with an extra control line so they can be disabled by Fn-F2. (They appear to the OS as just another USB device attached to the system's USB controller.)
I uninstalled the 'widcomm' 'stack' (from add/remove programs), disabled the Dell 355 Bluetooth (not wifi) and installed a linksys usb bluetooth adapter (which also uses WIDCOMM but in add/remove programs, it appears as 'linksys bluetooth utility 1.05')
this works fine... no blue screen stop error...
although this is a 'band-aid', its not an acceptable long run solution...
I uninstalled the 'widcomm' 'stack' (from add/remove programs), disabled the Dell 355 Bluetooth (not wifi) and installed a linksys usb bluetooth adapter (which also uses WIDCOMM but in add/remove programs, it appears as 'linksys bluetooth utility 1.05')
this works fine... no blue screen stop error...
although this is a 'band-aid', its not an acceptable long run solution...
It may be that Dell's particular WIDCOMM stack is a bad one.
The approach for using a newer WIDCOMM stack than what you have is the same as replacing another stack with WIDCOMM - do some Googling to find out how.
Tobi1982
15 Posts
0
December 14th, 2006 17:00
Message Edited by Tobi1982 on 12-14-200601:31 PM
tdweekly
9 Posts
0
December 14th, 2006 20:00
tdweekly
9 Posts
0
December 20th, 2006 17:00
get it to happen EVERYTIME i do the following...
-I open COM 9 from within a VB6 project (COM 9 is my bluetooth
communications port) The port opens fine...
-if I perform a .output to the port, the PC blue screens instantly
I can perform 'other' bluetooth operations fine...
below is my crash info..
I've uninstalled bluetooth drivers, reinstalled... performed a Windows
repair install (XP Pro SP2)... been back and forth with Dell support
(not helpful)....
help?
-----------------
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini121806-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Dec 18 11:40:57.000 2006 (GMT-6)
System Uptime: 0 days 0:13:51.354
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Unable to load image btport.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for btport.sys
*** ERROR: Module load completed but symbols could not be loaded for
btport.sys
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {ffdf, 2, 1, 806e4a8e}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : btport.sys ( btport+3f9c )
Followup: MachineOwner
---------
tdweekly
9 Posts
0
December 27th, 2006 19:00
Entropy42
529 Posts
0
January 2nd, 2007 12:00
The WIDCOMM stack works much better, 5.somethingorother.2100 is the latest version that will still work with CSR-based Bluetooth chipsets such as the 350. (Or did you say the 355? I think that's Broadcom-based and may work with newer WIDCOMM stacks). Unfortunately it can't legally be used with the Dell 3xx modules. There are ways to get them to work, but not in a legal manner. :( That's all I can really say, other than that Google is your friend.
tdweekly
9 Posts
0
January 2nd, 2007 15:00
Entropy42
529 Posts
0
January 2nd, 2007 18:00
Hmm, the description page doesn't specifically say it is WIDCOMM, but the version number does look like it's a WIDCOMM version number.
This is the first time I've seen someone having Bluetooth bluescreen issues with non-Toshiba stacks (typically one would see "TOSRFUSB.SYS" somewhere on the bluescreen.) I know WIDCOMM has solved all Bluetooth-related bluescreens on my E1705. (The Dell 350 on my E1705 came with a Toshiba BT stack.)
As to IRQ conflicts - Not likely, if there are it would affect other USB devices too, as the Bluetooth modules are basically USB dongles in a special form factor with an extra control line so they can be disabled by Fn-F2. (They appear to the OS as just another USB device attached to the system's USB controller.)
tdweekly
9 Posts
0
January 2nd, 2007 19:00
Entropy42
529 Posts
0
January 5th, 2007 12:00
It may be that Dell's particular WIDCOMM stack is a bad one.
The approach for using a newer WIDCOMM stack than what you have is the same as replacing another stack with WIDCOMM - do some Googling to find out how.