Help! BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)


  1. Posts : 2
    Windows 7 64 bit
       #1

    Help! BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)


    Hey guys, I recently bought a 2nd hand Alienware ALX that was supposedly barely used, but after getting it I keep getting BSODs. I was hoping someone could help.

    It runs Windows 7 64 bit. The crashing can happen anytime, it happened 3 times while I was reinstalling windows on it, it happens when I play games, and it can happen if I'm doing something as simple as watching youtube. Usually in a single day it'll crash maybe 5-10 times. I haven't observed it crashing while idle.

    At first, the BSOD's were giving "SYSTEM_SERVICE_EXCEPTION" and "Uncorrectable hardware error", so I tried running a diagnostic on the memory (memtest) and hdd (seatools) but no problems seems to have occurred. I also used the alienware command center tool to verify all the fans and liquid cooling was functioning. Temperature in the PC is between 29-31 degrees C. I also tried swapping out 1 ram stick at a time and swapping out the HDD, crashing still occurred.

    Once that found nothing, I tried upgrading the chipset and bios drivers. Although the BSODs still happen, the error is different now. I have copy pasted below the debug output from windbg. Could someone more familiar with windows stuff give me a few suggestions?

    Thanks!


    Code:
    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: 0000000063f735c0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff880085ce7af, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  0000000063f735c0 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    usbccgp!DispatchPdoUrb+97
    fffff880`085ce7af 450fb74c2402    movzx   r9d,word ptr [r12+2]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800313d610 -- (.trap 0xfffff8800313d610)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800ac49c58
    rdx=fffffa8008c0a1a8 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880085ce7af rsp=fffff8800313d7a0 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=fffff88003115b20
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    usbccgp!DispatchPdoUrb+0x97:
    fffff880`085ce7af 450fb74c2402    movzx   r9d,word ptr [r12+2] ds:a1a0:0002=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ebdca9 to fffff80002ebe740
    
    STACK_TEXT:  
    fffff880`0313d4c8 fffff800`02ebdca9 : 00000000`0000000a 00000000`63f735c0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff880`0313d4d0 fffff800`02ebc920 : 0000057f`f535b3a8 fffffa80`0ac4ab58 fffffa80`0c4d1770 fffffa80`08ec5a70 : nt!KiBugCheckDispatch+0x69
    fffff880`0313d610 fffff880`085ce7af : fffffa80`0ac4ab58 fffffa80`08ef6c60 00000000`00000324 fffffa80`08ef6c60 : nt!KiPageFault+0x260
    fffff880`0313d7a0 fffff880`085ceaba : fffffa80`0ac49b58 00000000`00220003 fffffa80`08ef6c60 fffffa80`0ac4ab58 : usbccgp!DispatchPdoUrb+0x97
    fffff880`0313d7e0 fffff880`085cc72e : 00000000`0000000f fffffa80`0ac4ab50 fffffa80`0ac4ab58 fffffa80`08ef6c60 : usbccgp!DispatchPdoInternalDeviceControl+0x17a
    fffff880`0313d810 fffff880`0908a48f : fffffa80`0ac4aa00 fffffa80`08ef6c01 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0x2de
    fffff880`0313d890 fffff880`09089f5b : fffffa80`08ef6fb8 fffffa80`0ac55c01 fffff880`0313d950 fffffa80`0ac55b40 : hidusb!HumReadReport+0x13f
    fffff880`0313d8e0 fffff880`0855a65d : fffffa80`0ac37a01 fffffa80`0ac37a80 fffffa80`08ef6c60 00000000`00000008 : hidusb!HumInternalIoctl+0x137
    fffff880`0313d950 fffff880`0855ae7d : fffffa80`0ac37a80 fffffa80`0ac55cb0 00000000`00000000 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0xdd
    fffff880`0313d9b0 fffff800`02ec0d26 : fffffa80`08ef6fbb 00000000`00000000 fffffa80`0ac55b01 fffffa80`08ef6c00 : HIDCLASS!HidpInterruptReadComplete+0x37d
    fffff880`0313da40 fffff880`041935d9 : fffffa80`09219050 fffffa80`0b323a00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
    fffff880`0313db20 fffff880`04193ab7 : fffffa80`0e621502 fffffa80`08ef6c60 00000000`ffffffff fffffa80`09219ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
    fffff880`0313dc00 fffff880`0419164f : fffffa80`09219ea8 fffffa80`092191a0 fffffa80`0921a040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`0313dc60 fffff880`04182f89 : fffffa80`09219050 00000000`00000000 fffffa80`09219e02 fffffa80`09219ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`0313dca0 fffff800`02ec9bfc : fffff880`03115180 fffffa80`09219ea8 fffffa80`09219ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`0313dcd0 fffff800`02ec6eea : fffff880`03115180 fffff880`031200c0 00000000`00000000 fffff880`04182db0 : nt!KiRetireDpcList+0x1bc
    fffff880`0313dd80 00000000`00000000 : fffff880`0313e000 fffff880`03138000 fffff880`0313dd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    hidusb!HumReadReport+13f
    fffff880`0908a48f 488b4c2460      mov     rcx,qword ptr [rsp+60h]
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  hidusb!HumReadReport+13f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hidusb
    
    IMAGE_NAME:  hidusb.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcbfe
    
    FAILURE_BUCKET_ID:  X64_0xD1_hidusb!HumReadReport+13f
    
    BUCKET_ID:  X64_0xD1_hidusb!HumReadReport+13f
    
    Followup: MachineOwner
      My Computer


  2. Posts : 2
    Windows 7 64 bit
    Thread Starter
       #2

    Blegh, just realized that error is being caused by the new mouse drivers I just added in. So confusing!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:00.
Find Us