Two Recent BDODs with STOP 0x0000000A


  1. Posts : 6
    Windows 7
       #1

    Two Recent BDODs with STOP 0x0000000A


    I am currently running Windows 7 Professional 64 bit on a Thinkpad T400, and very recently I got two BSODs with the following message in the Event Viewer:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff80002ff5477). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 032710-51870-01.
    The Dump files are provided in an attached zip.

    Any help would be appreciated.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Looks like your NIC driver NETw5s64.sys is throwing fits.

    Try looking for an updated driver for your network card.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\Desktop\032710-51870-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: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a16000 PsLoadedModuleList = 0xfffff800`02c53e50
    Debug session time: Sat Mar 27 14:03:36.304 2010 (GMT-4)
    System Uptime: 0 days 2:08:41.099
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 0, fffff80002ff5477}
    
    Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for NETw5s64.sys
    *** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
    Probably caused by : NETw5s64.sys ( NETw5s64+b76b )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002ff5477, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbe0e0
     0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    hal!HalpDmaNextContiguousPiece+103
    fffff800`02ff5477 448b08          mov     r9d,dword ptr [rax]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880031e7750 -- (.trap 0xfffff880031e7750)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000278
    rdx=0000000000000278 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ff5477 rsp=fffff880031e78e8 rbp=0000000000000000
     r8=0000000000000030  r9=0000000000000000 r10=00000000000fffff
    r11=fffffa8008136a70 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    hal!HalpDmaNextContiguousPiece+0x103:
    fffff800`02ff5477 448b08          mov     r9d,dword ptr [rax] ds:0001:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a87469 to fffff80002a87f00
    
    STACK_TEXT:  
    fffff880`031e7608 fffff800`02a87469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031e7610 fffff800`02a860e0 : fffffa80`0ac025f0 fffffa80`0acaa3d0 fffffa80`077a5480 fffff880`058f0893 : nt!KiBugCheckDispatch+0x69
    fffff880`031e7750 fffff800`02ff5477 : fffffa80`0449f160 fffffa80`0abdcd88 fffff800`02ff5524 fffffa80`0acaa3d0 : nt!KiPageFault+0x260
    fffff880`031e78e8 fffff800`02ff5524 : fffffa80`0acaa3d0 fffffa80`08136a70 fffffa80`0af95720 00000000`00000000 : hal!HalpDmaNextContiguousPiece+0x103
    fffff880`031e7900 fffff800`02ff84fb : fffffa80`0acaa3d0 fffffa80`08136a70 fffffa80`0449f160 fffffa80`0a1a5fd8 : hal!HalpDmaMapScatterTransfer+0x34
    fffff880`031e7950 fffff800`02ff8472 : fffffa80`0acaa3d0 fffffa80`0acaa3c8 00000000`00000030 00000000`00000000 : hal!HalpMapTransfer+0x7b
    fffff880`031e79e0 fffff800`02ff794f : 00000000`00000000 fffff800`02ff501e 00000000`00000000 00000000`00000003 : hal!IoMapTransfer+0x8e
    fffff880`031e7a20 fffff800`02ff7afd : fffffa80`08a3d050 fffffa80`08136a70 00000000`00000001 fffffa80`0000053e : hal!HalpAllocateAdapterCallback+0xc7
    fffff880`031e7ac0 fffff800`02ff8156 : fffffa80`08136a70 00000000`00000000 fffffa80`08136a00 00000000`00000005 : hal!IoFreeAdapterChannel+0x109
    fffff880`031e7af0 fffff800`02ff771f : fffffa80`09e62e40 00000000`0000009c fffffa80`08136a70 fffffa80`04dd7020 : hal!HalAllocateAdapterChannel+0x11a
    fffff880`031e7b30 fffff880`0189a7c0 : fffffa80`092d9030 fffffa80`081366e0 fffffa80`000000b8 fffff880`05aeac40 : hal!HalBuildScatterGatherList+0x2f3
    fffff880`031e7ba0 fffff880`058a676b : fffffa80`08a3d1a0 00000000`00000000 fffffa80`0a732020 fffff880`05a4baa0 : ndis!NdisMAllocateNetBufferSGList+0x110
    fffff880`031e7c40 fffffa80`08a3d1a0 : 00000000`00000000 fffffa80`0a732020 fffff880`05a4baa0 00000000`00000000 : NETw5s64+0xb76b
    fffff880`031e7c48 00000000`00000000 : fffffa80`0a732020 fffff880`05a4baa0 00000000`00000000 0000009c`00000100 : 0xfffffa80`08a3d1a0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    NETw5s64+b76b
    fffff880`058a676b ??              ???
    
    SYMBOL_STACK_INDEX:  c
    
    SYMBOL_NAME:  NETw5s64+b76b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETw5s64
    
    IMAGE_NAME:  NETw5s64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7
    
    FAILURE_BUCKET_ID:  X64_0xA_NETw5s64+b76b
    
    BUCKET_ID:  X64_0xA_NETw5s64+b76b
    
    Followup: MachineOwner
    ---------
      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 18:05.
Find Us