none
BSOD из за L1C62x86.sys RRS feed

  • Общие обсуждения

  • Помогите разобраться с BSOD из за L1C62x86.sys
    soft: Windows Developer Preview Build 8102 (работал без проблем с 09.2011)
    hard: MSI motherboard G41M-P28(MS7592), Atheros AR8131 PCI-E Gigabit Ethernet Controller на борту.
          Драйвер L1c62x86.sys Atheros Communications, file version 2.0.4.4 built by: WinDDK, driver date: 03.08.2011
          Для Atheros AR8131 PCI-E Gigabit Ethernet Controller выделены ресурсы:
          *Memory Range: FEAC0000 - FEAFFFFF
          *I/O Range: DC00 - DC7F
          *IRQ: 0x00000011 (17) No conflicts

    ******************************************************************************************************************

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\110711-59483-01.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: srv*C:\symbols*http://msdl.microsoft.com/download/sym
    bols
    Windows 7 Kernel Version 8102 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 8102.109.x86fre.winmain_win8m3.110912-1733
    Machine Name:
    Kernel base = 0x811c7000 PsLoadedModuleList = 0x8135ae38
    Debug session time: Mon Nov  7 09:48:55.310 2011 (UTC + 2:00)
    System Uptime: 0 days 0:24:46.921
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {4, 2, 0, 8117e5e2}

    *** WARNING: Unable to verify timestamp for L1C62x86.sys
    *** ERROR: Module load completed but symbols could not be loaded for L1C62x86.sy
    s
    Probably caused by : L1C62x86.sys ( L1C62x86+58fa )

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

    0: kd> kd: Reading initial command '!analyze -v; q'
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000004, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, bitfield :
            bit 0 : value 0 = read operation, 1 = write operation
            bit 3 : value 0 = not an execute operation, 1 = execute operation (only
    on chips which support this level of status)
    Arg4: 8117e5e2, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 81372484
    Unable to read MiSystemVaType memory at 8135a060
     00000004

    CURRENT_IRQL:  2

    FAULTING_IP:
    hal!HalPutScatterGatherListV2+d0
    8117e5e2 8b4904          mov     ecx,dword ptr [ecx+4]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    LAST_CONTROL_TRANSFER:  from 8117aa21 to 8117e5e2

    STACK_TEXT:
    b9e77be0 8117aa21 850ac4a8 00000001 b9e77c10 hal!HalPutScatterGatherListV2+0xd0
    b9e77bf0 81a2746a 850ac4a8 8519ccc0 00000001 hal!HalPutScatterGatherList+0x2d
    b9e77c10 905378fa 850b0418 8519ccc0 84415ad8 ndis!NdisMFreeNetBufferSGList+0x30
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b9e77c48 9053c1d8 8508b94c 000000db 00000000 L1C62x86+0x58fa
    b9e77c68 9053c3ae 00010000 b9e77cb0 b9e77ccc L1C62x86+0xa1d8
    b9e77c78 81a8f784 8508b000 00000000 b9e77cb0 L1C62x86+0xa3ae
    b9e77ccc 81a36a3b 850abf64 00000000 00000000 ndis!ndisMiniportDpc+0x172
    b9e77d2c 81a36905 850abfa4 83f4fd40 00000000 ndis!ndisQueuedMiniportDpcWorkItem+
    0xb7
    b9e77d6c 81490c70 00000000 79a1b6a6 00000000 ndis!ndisReceiveWorkerThread+0x14b
    b9e77db0 812c59c1 81a367ba 00000000 00000000 nt!PspSystemThreadStartup+0xa1
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    L1C62x86+58fa
    905378fa ??              ???

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  L1C62x86+58fa

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: L1C62x86

    IMAGE_NAME:  L1C62x86.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d883465

    FAILURE_BUCKET_ID:  0xA_L1C62x86+58fa

    BUCKET_ID:  0xA_L1C62x86+58fa

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

    quit:
    Press any key to continue . . .
    SEM7r540
    7 ноября 2011 г. 18:13

Все ответы