Bsod: Irql_not_less_or_equal

By flanders61
Sep 29, 2009
Topic Status:
Not open for further replies.
  1. i have been getting BSOD's since updating my pc to windows SP2 im running vista 32 business with 3 gb of ram it is a dell e520 system

    i have attached with the min dump files i have tried updating my video card drivers my hd management drivers and my network drivers so far if anyone can pin point the driver responsible that would be great thanks.

    i will try to get my full system info and post it anywhere i can find that would be helpful

    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: 00000014, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 82a2ecc5, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81f4c868
    Unable to read MiSystemVaType memory at 81f2c420
    00000014

    CURRENT_IRQL: 2

    FAULTING_IP:
    ndis!ndisFreeConvertedPacket+22
    82a2ecc5 897a14 mov dword ptr [edx+14h],edi

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: TeaTimer.exe

    TRAP_FRAME: 8039db10 -- (.trap 0xffffffff8039db10)
    ErrCode = 00000002
    eax=853b9f38 ebx=86e8b0e8 ecx=86e2fdd8 edx=00000000 esi=86e2fdf8 edi=00000000
    eip=82a2ecc5 esp=8039db84 ebp=8039db8c iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    ndis!ndisFreeConvertedPacket+0x22:
    82a2ecc5 897a14 mov dword ptr [edx+14h],edi ds:0023:00000014=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82a2ecc5 to 81e62fb9

    STACK_TEXT:
    8039db10 82a2ecc5 badb0d00 00000000 8039db2c nt!KiTrap0E+0x2e1
    8039db8c 82a2f703 86e2fdd8 8715c788 00000000 ndis!ndisFreeConvertedPacket+0x22
    8039dba8 82adb45a 86e2fdd8 8039dc10 82afba18 ndis!ndisXlateReturnPacketToNetBufferList+0x33
    8039dbb4 82afba18 86e8b0e8 86e2fdd8 c000009a ndis!ndisReturnPacketToNetBufferList+0xd
    8039dc10 82ad57fa 003b9f38 8039dc30 00000001 ndis!ethFilterDprIndicateReceivePacket+0x7a4
    8039dce0 82ac8c64 0239dcf8 00000000 80c76000 ndis!ndisIndicateXlatedPacketsToNdis5Protocols+0xd1
    8039de5c 82a0957f 86e8b0e8 84e7c860 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0xf1
    8039de78 82ac88f9 86e8b0e8 8715c700 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2c
    8039de94 82a0954a 86e8b0e8 8715c700 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x27
    8039deb0 82b7ff6e 86e8b0e8 8715c700 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x20
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8039def8 82b7a765 01c76000 00000000 00000000 e1e6032+0x6f6e
    8039df2c 82b7ab03 00c76000 871ee000 8039df64 e1e6032+0x1765
    8039df3c 82ac81fd 80c76000 00000000 00000000 e1e6032+0x1b03
    8039df64 82a09468 871eee18 82b7aa50 00000000 ndis!ndisMiniportDpc+0x7a
    8039df88 81ebf6a2 871eee18 86e8b0e8 00000000 ndis!ndisInterruptDpc+0xc4
    8039dff4 81ebd2d5 a285fcf0 00000000 00000000 nt!KiRetireDpcList+0x147
    8039dff8 a285fcf0 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
    81ebd2d5 00000000 0000001b 00c7850f bb830000 0xa285fcf0


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    e1e6032+6f6e
    82b7ff6e ?? ???

    SYMBOL_STACK_INDEX: a

    SYMBOL_NAME: e1e6032+6f6e

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: e1e6032

    IMAGE_NAME: e1e6032.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 455ca8d9

    FAILURE_BUCKET_ID: 0xD1_e1e6032+6f6e

    BUCKET_ID: 0xD1_e1e6032+6f6e

    Followup: MachineOwner
    ---------
  2. Route44

    Route44 TechSpot Ambassador Posts: 12,113   +23

    I read your five most recent dumps dating from 9/25 through 9/29 and all five point to the same driver as the cause of your crashes: e1e6032.sys.

    This is an Intel(R) PRO/1000 Adapter driver. Update your drives. By the way that is a one and not a small L.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.