Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

(BSOD) DRIVER_IRQL_NOT_LESS_OR_EQUAL


  • Please log in to reply
No replies to this topic

#1 jeff11

jeff11

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:46 PM

Posted 24 October 2010 - 06:20 PM

Hello...

May I request the community's assistance with the following system crash/BSOD error?

(first, please let me say thank you to Hamluis' pointing to Usasma's excellent "How to receive help diagnosing Blue Screens and Windows crashes " post)

In hope of accurately following directions...

SYSTEM: Dell XPS 710, XP SP 3; if it matters, no recent hardware additions
ISSUE: At seemingly random intervals, I experience a system crash and the following BSOD: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Started ~ 1 month ago(?), but seems to be happening with more frequency.

WINDbg results of the latest (this evening... yuck) minidump:


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini102410-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Oct 24 17:38:18.421 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:42.264
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 1, b6db14a5}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_RemoveBadReqIrp+6b )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b6db14a5, address which referenced memory

Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_RemoveBadReqIrp+6b
b6db14a5 8907 mov dword ptr [edi],eax
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 804f1bdf to b6db14a5
STACK_TEXT:
80551284 804f1bdf 41426d72 88e2ac00 8a9bc0e0 USBPORT!USBPORT_RemoveBadReqIrp+0x6b
8055129c b6db1275 8a9bc102 00000000 8a9bc0e0 nt!IoCsqRemoveNextIrp+0x3d
805512bc b6db1840 8a9bc028 00000000 b6db16dc USBPORT!USBPORT_BadRequestFlush+0x3b
805512e0 8050220f 8a9bc70c 8a9bc028 c5c7e07e USBPORT!USBPORT_DM_TimerDpc+0x164
805513fc 8050232b 8055c0c0 ffdff9c0 ffdff000 nt!KiTimerListExpire+0x14b
80551428 80545ebf 8055c4c0 00000000 0000eb8f nt!KiTimerExpiration+0xb1
80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
80551450 80545da4 00000000 0000000e 00000000 nt!KiIdleThread0
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_RemoveBadReqIrp+6b
b6db14a5 8907 mov dword ptr [edi],eax
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: USBPORT!USBPORT_RemoveBadReqIrp+6b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
FAILURE_BUCKET_ID: 0xD1_USBPORT!USBPORT_RemoveBadReqIrp+6b
BUCKET_ID: 0xD1_USBPORT!USBPORT_RemoveBadReqIrp+6b

Followup: MachineOwner
---------


Just to change things up a bit (I guess) Windows occasionally throws in a different BSOD error: BUGCODE_USB_DRIVER, but I couldn't remember which .dmp file that was. I'll debug that as well the next time it shows up.
In advance, thank you very much for your assistance. I certainly appreciate any advice or guidance you'd care to give.

Cheers.... Jeff

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users