TechSpot

Driver IRQL not less or equal BSOD

By Bubbet
Nov 15, 2008
  1. I had to re-image my computer and now I have been getting this BSOD lately. It happens at random intervals sometimes when gaming but other times when just surfing the web. I have run memtest 86 as well as windows memory test and also check disk with no problems. I have tried different video drivers and changing overclocks etc. The system was stable at the exact clock its running at now for over a year so why this is happening now does not make sense. I clocked back my ram and HT but that still did not help. Here is the latest memory dump it seems to refer to a usb port?? Why would this be causing a bsod??

    System:
    Vista Ultimate 64-Bit
    AMD Athlon 64 X2 4800+ (2.7Ghz)
    4GB DDR400 OCZ EL Platinum 2-2-2-5
    2x EVGA 8800GT SLI
    3x WD Caviar SE16 250GB SATA Raid0
    Auzentech X-FI Prelude

    Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Executable search path is:
    Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c1fdb0
    Debug session time: Fri Nov 14 23:50:45.922 2008 (GMT-7)
    System Uptime: 0 days 3:11:27.388
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list

    *Bugcheck Analysis*

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffffae003011055, 2, 8, fffffae003011055}

    Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ReferenceEndpoint+55 )

    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: fffffae003011055, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffffae003011055, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002c83080
    fffffae003011055

    CURRENT_IRQL: 2

    FAULTING_IP:
    +fffffae003011055
    fffffae0`03011055 ?? ???

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: ra3_1.3.game

    TRAP_FRAME: fffff80003c3f500 -- (.trap 0xfffff80003c3f500)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000002b4c7874 rbx=fffffa8004f6a050 rcx=fffffa8004f6a1a0
    rdx=000000004f444648 rsi=fffffa8007f87bc8 rdi=fffffa8005dd46d8
    rip=fffffae003011055 rsp=fffff80003c3f690 rbp=0000000000000000
    r8=000000004f444648 r9=fffffa8007f87a60 r10=0000000000000001
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    fffffae0`03011055 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002aaf0ee to fffff80002aaf350

    FAILED_INSTRUCTION_ADDRESS:
    +fffffae003011055
    fffffae0`03011055 ?? ???

    STACK_TEXT:
    fffff800`03c3f3b8 fffff800`02aaf0ee : 00000000`0000000a fffffae0`03011055 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff800`03c3f3c0 fffff800`02aadfcb : 00000000`00000008 fffffa80`05e2c060 0000057f`f85d6f00 fffff800`03c3f6f0 : nt!KiBugCheckDispatch+0x6e
    fffff800`03c3f500 fffffae0`03011055 : 00000000`00000388 00000000`00000001 fffffa80`07f87bc8 fffffa60`03012781 : nt!KiPageFault+0x20b
    fffff800`03c3f690 00000000`00000388 : 00000000`00000001 fffffa80`07f87bc8 fffffa60`03012781 fffff800`03c3f730 : 0xfffffae0`03011055
    fffff800`03c3f698 00000000`00000001 : fffffa80`07f87bc8 fffffa60`03012781 fffff800`03c3f730 fffffa60`0301ec01 : 0x388
    fffff800`03c3f6a0 fffffa80`07f87bc8 : fffffa60`03012781 fffff800`03c3f730 fffffa60`0301ec01 fffffa80`04f6a050 : 0x1
    fffff800`03c3f6a8 fffffa60`03012781 : fffff800`03c3f730 fffffa60`0301ec01 fffffa80`04f6a050 fffffa60`0300b045 : 0xfffffa80`07f87bc8
    fffff800`03c3f6b0 fffffa60`2b4c7874 : fffffa80`04f6a4a0 fffffa80`07f87c50 fffffa80`04f6a1a0 fffffa80`06238010 : USBPORT!USBPORT_ReferenceEndpoint+0x55
    fffff800`03c3f700 fffffa80`04f6a4a0 : fffffa80`07f87c50 fffffa80`04f6a1a0 fffffa80`06238010 fffffa80`04f6a050 : 0xfffffa60`2b4c7874
    fffff800`03c3f708 fffffa80`07f87c50 : fffffa80`04f6a1a0 fffffa80`06238010 fffffa80`04f6a050 fffffa60`03021f81 : 0xfffffa80`04f6a4a0
    fffff800`03c3f710 fffffa80`04f6a1a0 : fffffa80`06238010 fffffa80`04f6a050 fffffa60`03021f81 fffffa80`07f87a60 : 0xfffffa80`07f87c50
    fffff800`03c3f718 fffffa80`06238010 : fffffa80`04f6a050 fffffa60`03021f81 fffffa80`07f87a60 fffffa80`07f87a60 : 0xfffffa80`04f6a1a0
    fffff800`03c3f720 fffffa80`04f6a050 : fffffa60`03021f81 fffffa80`07f87a60 fffffa80`07f87a60 fffffa80`079e3010 : 0xfffffa80`06238010
    fffff800`03c3f728 fffffa60`03021f81 : fffffa80`07f87a60 fffffa80`07f87a60 fffffa80`079e3010 fffffa80`05dbab80 : 0xfffffa80`04f6a050
    fffff800`03c3f730 fffffa60`03037007 : fffffa80`079e3010 fffffa80`52547571 fffffa80`079e3010 00000000`80000300 : USBPORT!USBPORT_Core_QueueTransferUrb+0x1a9
    fffff800`03c3f770 fffffa60`030369e1 : fffffa80`04f6a1a0 fffffa80`52546c61 fffffa80`079e64f0 fffffa80`06238010 : USBPORT!USBPORT_AsyncTransfer+0x8f
    fffff800`03c3f7a0 fffffa60`0303e6d2 : fffffa80`0636c050 fffffa80`04f6a050 fffffa80`06238010 fffffa80`06360009 : USBPORT!USBPORT_ProcessURB+0x9d1
    fffff800`03c3f880 fffffa60`0300f662 : fffffa80`06238010 fffffa80`06238248 fffffa80`052b45c0 00000000`00000000 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x1ea
    fffff800`03c3f8d0 fffffa60`03c5f134 : fffffa80`06450050 fffffa80`0797c060 fffffa80`06238010 fffffa80`0797c1b0 : USBPORT!USBPORT_Dispatch+0x396
    fffff800`03c3f940 fffffa60`03c8accd : 00000000`00000000 00000000`00000000 fffffa80`0797c060 00000000`00000002 : usbhub!UsbhFdoUrbPdoFilter+0xe0
    fffff800`03c3f970 fffffa60`03c5dbc7 : fffffa80`07a131b8 fffffa80`079cdb88 00000000`00000000 fffffa80`06238010 : usbhub!UsbhPdoInternalDeviceControl+0x375
    fffff800`03c3f9c0 fffffa60`089a8d83 : fffffa80`079cdb88 00000000`00220003 fffffa80`06238010 00000000`00000324 : usbhub!UsbhGenDispatch+0x57
    fffff800`03c3fa00 fffffa60`089a5484 : fffffa80`07a131b8 00000000`00000000 fffffa80`079cdb88 fffffa80`06238010 : usbccgp!UsbcForwardIrp+0x87
    fffff800`03c3fa50 fffffa60`089a573a : fffffa80`07a131b8 00000000`00220003 fffffa80`06238010 fffffa80`079cdb88 : usbccgp!DispatchPdoUrb+0x108
    fffff800`03c3fa90 fffffa60`089a3695 : fffffa80`07a131b8 fffffa80`079cdb88 fffffa80`07a131b0 fffffa80`06238010 : usbccgp!DispatchPdoInternalDeviceControl+0x18a
    fffff800`03c3fad0 fffffa60`089c17c0 : fffffa80`07a13060 00000000`00000001 fffffa80`079b2000 fffffa80`06238010 : usbccgp!USBC_Dispatch+0x269
    fffff800`03c3fb40 fffffa60`089c13b9 : fffffa80`079b2060 00000000`00000000 fffff800`03c3fbe0 fffffa80`06238010 : hidusb!HumReadReport+0x138
    fffff800`03c3fb90 fffffa60`089cc173 : fffffa80`0798bc01 00000000`00000000 fffffa80`0798bcf0 fffffa80`079b21d0 : hidusb!HumInternalIoctl+0x99
    fffff800`03c3fbe0 fffffa60`089cc69c : fffffa80`0798bcf0 00000000`00000000 00000000`00000008 00000000`00000000 : HIDCLASS!HidpSubmitInterruptRead+0xa7
    fffff800`03c3fc20 fffff800`02ab16c5 : fffffa80`06238010 fffffa80`05dbab00 fffffa80`04f6b301 00000000`00000000 : HIDCLASS!HidpInterruptReadComplete+0x218
    fffff800`03c3fc90 fffffa60`03022d68 : fffffa80`04f6a050 fffffa80`04f6a000 fffffa80`04f6a1a0 fffffa80`04f6a050 : nt!IopfCompleteRequest+0x315
    fffff800`03c3fd50 fffffa60`03023420 : fffffa80`54546b63 fffffa80`06238010 fffff800`32466d64 fffffa80`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x898
    fffff800`03c3fe30 fffffa60`03020872 : fffffa80`39585043 fffffa80`04f6a1a0 fffffa80`04f6b088 fffffa80`04f6a1a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514
    fffff800`03c3fea0 fffffa60`0300d18b : fffffa80`31636f49 fffffa80`04f6b088 fffffa60`11c0cc02 fffffa80`04f6a1a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a
    fffff800`03c3fef0 fffff800`02ab89d7 : fffffa80`04f6b0a0 fffffa60`34776478 fffffa60`11c0cca0 fffff800`02bd1a80 : USBPORT!USBPORT_Xdpc_Worker+0x26f
    fffff800`03c3ff40 fffff800`02ab2825 : fffffa60`0300cf1c fffff800`02bce680 fffffa60`11c0cca0 fffffa80`04b51c00 : nt!KiRetireDpcList+0x117
    fffff800`03c3ffb0 fffff800`02ab2637 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffffa60`11c0cbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    USBPORT!USBPORT_ReferenceEndpoint+55
    fffffa60`03012781 488b6c2458 mov rbp,qword ptr [rsp+58h]

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: USBPORT!USBPORT_ReferenceEndpoint+55

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: USBPORT

    IMAGE_NAME: USBPORT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 479199d8

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_ReferenceEndpoint+55

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_USBPORT!USBPORT_ReferenceEndpoint+55

    Followup: MachineOwner
    ---------
     
  2. Bubbet

    Bubbet TS Rookie Topic Starter

    Just got 2 more BSOD's playing lord of the rings online. These ones did not say driver irql only a plain blue screen. I had to delete the stack text as it would not fit in the post...too many characters

    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught. This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
    Typically the code is 0x1001 (deadlock detected) and you can
    issue a '!deadlock' KD command to get more information.
    Arguments:
    Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
    Arg2: 0000000000000000
    Arg3: fffffa800892cbb0
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0xc4_91

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: lotroclient.exe

    CURRENT_IRQL: 0

    EXCEPTION_RECORD: fffffa80057867b8 -- (.exr 0xfffffa80057867b8)
    ExceptionAddress: fffffa80057402f7
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000001
    Parameter[1]: 00000000c00000a3
    Attempt to write to address 00000000c00000a3

    TRAP_FRAME: fffffa8005786860 -- (.trap 0xfffffa8005786860)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c00000a3 rbx=0000000000000aa0 rcx=fffffa800577d2c0
    rdx=0000000000000078 rsi=0000000000000aa0 rdi=0000000000000aa0
    rip=fffffa80057402f7 rsp=fffffa80057869f8 rbp=fffffffffffffffc
    r8=0000000000000000 r9=fffffa6011059a70 r10=0000000000000000
    r11=fffffa800892cbb0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz ac pe cy
    fffffa80`057402f7 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002a73f73 to fffff80002a5c350

    STACK_COMMAND: .trap 0xfffffa8005786860 ; kb

    FOLLOWUP_IP:
    nvrd64+18da0
    fffffa60`009ceda0 ?? ???

    SYMBOL_STACK_INDEX: 3a

    SYMBOL_NAME: nvrd64+18da0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvrd64

    IMAGE_NAME: nvrd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 468999e7

    FAILURE_BUCKET_ID: X64_0xc4_91_nvrd64+18da0

    BUCKET_ID: X64_0xc4_91_nvrd64+18da0

    Followup: MachineOwner
    ---------
     
  3. Bubbet

    Bubbet TS Rookie Topic Starter

    Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    ......................................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 6f8, fffff80002a5af65}

    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )

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

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

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000006f8
    Arg4: fffff80002a5af65

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: lotroclient.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002a5b0ee to fffff80002a5b350

    STACK_TEXT:
    fffff800`03c41d28 fffff800`02a5b0ee : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
    fffff800`03c41d30 fffff800`02a59938 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x6e
    fffff800`03c41e70 fffff800`02a5af65 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb8
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x16a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiDoubleFaultAbort+b8
    fffff800`02a59938 90 nop

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiDoubleFaultAbort+b8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

    FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8

    BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b8

    Followup: MachineOwner
    ---------
     
  4. Bubbet

    Bubbet TS Rookie Topic Starter

    Did a clean install in hopes it would clear the issue but it did not. Just got this BSOD:


    Microsoft (R) Windows Debugger Version 6.10.0003.233 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Executable search path is:
    Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
    Machine Name:
    Kernel base = 0xfffff800`01c5e000 PsLoadedModuleList = 0xfffff800`01e23db0
    Debug session time: Wed Nov 19 22:19:11.680 2008 (GMT-7)
    System Uptime: 0 days 0:29:16.537
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffffae000b9c726, 2, 8, fffffae000b9c726}

    Page 7bf11 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
    Probably caused by : usbccgp.sys ( usbccgp!DispatchPdoInternalDeviceControl+18a )

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

    1: 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: fffffae000b9c726, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffffae000b9c726, address which referenced memory

    Debugging Details:
    ------------------

    Page 7bf11 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
    PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details

    READ_ADDRESS: fffffae000b9c726

    CURRENT_IRQL: 2

    FAULTING_IP:
    +fffffae000b9c726
    fffffae0`00b9c726 ?? ???

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: lotroclient.exe

    TRAP_FRAME: fffffa60019228e0 -- (.trap 0xfffffa60019228e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000030627573 rbx=0000000000000000 rcx=fffffa8004ec71a0
    rdx=000000004f444648 rsi=0000000000000002 rdi=fffffa80090cc2b8
    rip=fffffae000b9c726 rsp=fffffa6001922a70 rbp=fffffa8004ec7050
    r8=000000004f444648 r9=0000000000000001 r10=0000000000000008
    r11=fffffa6001922ba0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    fffffae0`00b9c726 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80001cb30ee to fffff80001cb3350

    FAILED_INSTRUCTION_ADDRESS:
    +fffffae000b9c726
    fffffae0`00b9c726 ?? ???


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbccgp!DispatchPdoInternalDeviceControl+18a
    fffffa60`08d9473a 488b5c2440 mov rbx,qword ptr [rsp+40h]

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: usbccgp!DispatchPdoInternalDeviceControl+18a

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbccgp

    IMAGE_NAME: usbccgp.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 479199dc

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbccgp!DispatchPdoInternalDeviceControl+18a

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_usbccgp!DispatchPdoInternalDeviceControl+18a

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

    1: kd> lmvm usbccgp
    start end module name
    fffffa60`08d91000 fffffa60`08dad000 usbccgp (pdb symbols) c:\websymbols\usbccgp.pdb\B33BD87FD6874415B7DCBB3F45CED5631\usbccgp.pdb
    Loaded symbol image file: usbccgp.sys
    Image path: \SystemRoot\system32\DRIVERS\usbccgp.sys
    Image name: usbccgp.sys
    Timestamp: Fri Jan 18 23:34:04 2008 (479199DC)
    CheckSum: 000229C9
    ImageSize: 0001C000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...