Re: IRQL_NOT_LESS_OR_EQUAL when using Bluetooth COM port

Tech-Archive recommends: Fix windows errors by optimizing your registry

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

  • Re: Help for debug a BSOD with microsoft debugging tools
    ... *** 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. ...
    (microsoft.public.windowsxp.help_and_support)
  • Ntfs crash
    ... Debugger entered on first try; ... Use!analyze -v to get detailed debugging information. ... *** In order for this command to work properly, ... *** must point to .pdb files that have full type information. ...
    (microsoft.public.development.device.drivers)
  • Re: driver_irql_less_or_equal - Driver causes crash
    ... *** 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. ...
    (microsoft.public.development.device.drivers)
  • IRQL not less or equal (bugcheck 0x0A)
    ... If a kernel debugger is available get the stack backtrace. ... *** In order for this command to work properly, ... *** must point to .pdb files that have full type information. ...
    (microsoft.public.development.device.drivers)
  • Re: driver_irql_less_or_equal - Driver causes crash
    ... *** 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. ...
    (microsoft.public.development.device.drivers)