Re: IRQL_NOT_LESS_OR_EQUAL when using Bluetooth COM port

Sorry I printed off your earlier message intending to post the next day but it got buried under the pile of paper which resides on my computer desk.

Background information on original Stop Error
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/DevTest_g/hh/DevTest_g/t05_bugs_60_299217d6-98d1-4d1d-8068-883e89933845.xml.asp
if link broken try
http://snipurl.com/l6o7

The report included with your first post referred to btport.sys.

The link below would seem to be a software update for your bluetooth device
http://www.broadcom.com/products/bluetooth_update.php

Is your software up to date?

Dell updates. The site below is a UK site but I got no results from the USA for Model MP061. Ask your Dell Support, whether software and drivers from the UK site are appropriate for your machine.

This seems to be a more up to date BIOS
http://support.euro.dell.com/support/downloads/download.aspx?c=uk&cs=ukdhs1&l=en&s=dhs&releaseid=R136297&formatcnt=1&libid=0&fileid=181599
if link broken try
http://snipurl.com/15xct

The link below lists other drivers, some may be appropriate for your system, but I am unable to tell from the information you have provided, whether they are or are not updates for those already installed on your system. The link is worth keeping as it will be updated:
http://search.euro.dell.com/results.aspx?cat=sup&subcat=dyd&c=uk&l=en&s=dhs&cs=ukdhs1&k=MP061
if link broken try
http://snipurl.com/15xdo

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~




schwantizzmo wrote:
Here's some of my system details, as requested... any
help/suggestions is appreciated.

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc.
System Model MP061
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 6 GenuineIntel ~1997 Mhz
Processor x86 Family 6 Model 15 Stepping 6 GenuineIntel ~1997 Mhz
BIOS Version/Date Dell Inc. A04, 9/29/2006
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)"
Total Physical Memory 2,048.00 MB
Available Physical Memory 1.28 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 3.85 GB
Page File C:\pagefile.sys
[Conflicts/Sharing]

Resource Device
I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

IRQ 20 Intel(R) 82801G (ICH7 Family) USB Universal Host Controller -
27C8 IRQ 20 Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host
Controller - 27CC

I/O Port 0x000003C0-0x000003DF Mobile Intel(R)
955XM/945GM/PM/GMS/940GML Express PCI Express Root Port - 27A1
I/O Port 0x000003C0-0x000003DF ATI Mobility Radeon X1400

IRQ 21 Microsoft UAA Bus Driver for High Definition Audio
IRQ 21 Intel(R) 82801G (ICH7 Family) USB Universal Host Controller -
27C9

Memory Address 0xFFA80000-0xFFA83FFF System board
Memory Address 0xFFA80000-0xFFA83FFF Intel(R) 82801G (ICH7 Family)
USB2 Enhanced Host Controller - 27CC

I/O Port 0x000010C0-0x000010DF Intel(R) 82801G (ICH7 Family) SMBus
Controller - 27DA
I/O Port 0x000010C0-0x000010DF System board

IRQ 16 Mobile Intel(R) 955XM/945GM/PM/GMS/940GML Express PCI Express
Root Port - 27A1
IRQ 16 ATI Mobility Radeon X1400
IRQ 16 Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0

IRQ 17 Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D2
IRQ 17 Dell Wireless 1390 WLAN Mini-Card
IRQ 17 Broadcom 440x 10/100 Integrated Controller

Memory Address 0xD0000000-0xDFFFFFFF Mobile Intel(R)
955XM/945GM/PM/GMS/940GML Express PCI Express Root Port - 27A1
Memory Address 0xD0000000-0xDFFFFFFF ATI Mobility Radeon X1400

IRQ 18 SDA Standard Compliant SD Host Controller
IRQ 18 Ricoh MMC Host Controller
IRQ 18 Ricoh Memory Stick Host Controller
IRQ 18 Ricoh xD-Picture Card Host Controller

IRQ 19 Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D6
IRQ 19 OHCI Compliant IEEE 1394 Host Controller

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF Mobile Intel(R)
955XM/945GM/PM/GMS/940GML Express PCI Express Root Port - 27A1
Memory Address 0xA0000-0xBFFFF ATI Mobility Radeon X1400

I/O Port 0x000003B0-0x000003BB Mobile Intel(R)
955XM/945GM/PM/GMS/940GML Express PCI Express Root Port - 27A1
I/O Port 0x000003B0-0x000003BB ATI Mobility Radeon X1400
[IRQs]

Resource Device Status
IRQ 9 Microsoft ACPI-Compliant System OK
IRQ 16 Mobile Intel(R) 955XM/945GM/PM/GMS/940GML Express PCI Express
Root Port - 27A1 OK
IRQ 16 ATI Mobility Radeon X1400 OK
IRQ 16 Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D0 OK
IRQ 21 Microsoft UAA Bus Driver for High Definition Audio OK
IRQ 21 Intel(R) 82801G (ICH7 Family) USB Universal Host Controller -
27C9 OK IRQ 17 Intel(R) 82801G (ICH7 Family) PCI Express Root Port -
27D2 OK
IRQ 17 Dell Wireless 1390 WLAN Mini-Card OK
IRQ 17 Broadcom 440x 10/100 Integrated Controller OK
IRQ 19 Intel(R) 82801G (ICH7 Family) PCI Express Root Port - 27D6 OK
IRQ 19 OHCI Compliant IEEE 1394 Host Controller OK
IRQ 20 Intel(R) 82801G (ICH7 Family) USB Universal Host Controller -
27C8 OK IRQ 20 Intel(R) 82801G (ICH7 Family) USB2 Enhanced Host
Controller - 27CC OK IRQ 22 Intel(R) 82801G (ICH7 Family) USB
Universal Host Controller - 27CA OK IRQ 23 Intel(R) 82801G (ICH7
Family) USB Universal Host Controller - 27CB OK IRQ 18 SDA Standard
Compliant SD Host Controller OK
IRQ 18 Ricoh MMC Host Controller OK
IRQ 18 Ricoh Memory Stick Host Controller OK
IRQ 18 Ricoh xD-Picture Card Host Controller OK
IRQ 12 Synaptics PS/2 Port Pointing Device OK
IRQ 1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
IRQ 8 System CMOS/real time clock OK
IRQ 2 System timer OK
IRQ 13 Numeric data processor OK
IRQ 14 Primary IDE Channel OK
IRQ 15 Secondary IDE Channel OK
IRQ 5 Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA OK
IRQ 0 System board OK
"Gerry Cornell" wrote:

Can you please post information about your motherboard, bios,
and blue tooth device.

This freeware programme is excellent for getting information
about your computer:
Everest Home Edition (freeware)
http://www.majorgeeks.com/download4181.html

Tip: To copy select Report, Quick Report, Plain Text, highlight
required text, right click and select copy. However, whilst this is
fine for posting small amounts of information into newsgroup
messages longer reports will irritate other newsgroup subscribers.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"schwantizzmo" <schwantizzmo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:FB3227FB-04A2-44B5-AA69-237BA595FF39@xxxxxxxxxxxxxxxx

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 (useless)....

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 <symbol_path> 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 <symbol_path> 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
---------

.

Relevant Pages