none
Rt64win7.sys BSoD

    Question

  • I have a Windows 7 Ultimate Laptop that is randomly Blue Screening.  I downloaded the debugger and the symbols and checked it out.  The file causing the Blue Screens is rt64win7.sys.  I was wondering what to do now that I have the file that is causing the problem.  I am also going to post the debugger results.  Any help would be much appreciated.  Please let me know what other information you would need to help me trouble shoot this.

    Debugger results:

    Microsoft (R) Windows Debugger Version 6.11.0001.404 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

    Symbol search path is: C:\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`02a4c000 PsLoadedModuleList = 0xfffff800`02c89e50
    Debug session time: Sun Sep 27 16:18:17.159 2009 (GMT-4)
    System Uptime: 0 days 0:34:37.421
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................................
    Loading User Symbols

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

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {8, 2, 0, fffff80002a077f7}

    Probably caused by : Rt64win7.sys ( Rt64win7!MpHandleSendInterrupt+22c )

    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: 0000000000000008, 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: fffff80002a077f7, address which referenced memory

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


    READ_ADDRESS:  0000000000000008

    CURRENT_IRQL:  2

    FAULTING_IP:
    hal!HalPutScatterGatherList+a7
    fffff800`02a077f7 4d8b642408      mov     r12,qword ptr [r12+8]

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff880031b68e0 -- (.trap 0xfffff880031b68e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000002
    rdx=0000000000000fff rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a077f7 rsp=fffff880031b6a70 rbp=0000000000000be5
     r8=0000000000000000  r9=fffffa8004b1bbe5 r10=ffffffffffffffa6
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    hal!HalPutScatterGatherList+0xa7:
    fffff800`02a077f7 4d8b642408      mov     r12,qword ptr [r12+8] ds:5870:0008=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80002abd469 to fffff80002abdf00

    STACK_TEXT: 
    fffff880`031b6798 fffff800`02abd469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031b67a0 fffff800`02abc0e0 : fffffa80`042e7900 fffffa80`0532df00 fffffa80`06ac37a0 fffff880`014fda47 : nt!KiBugCheckDispatch+0x69
    fffff880`031b68e0 fffff800`02a077f7 : fffffa80`0532df00 fffffa80`04b1bbe5 00000000`00000665 fffffa80`06201540 : nt!KiPageFault+0x260
    fffff880`031b6a70 fffff880`014fe8a1 : fffffa80`04473e60 fffffa80`04473d30 fffffa80`05327440 fffffa80`03d72be0 : hal!HalPutScatterGatherList+0xa7
    fffff880`031b6ad0 fffff880`04288bb8 : fffff800`02c61501 fffffa80`05327440 00000000`00000000 fffff800`02c61501 : ndis!NdisMFreeNetBufferSGList+0x31
    fffff880`031b6b10 fffff880`0427a9fd : 00000000`00000000 00000000`00000000 fffff800`02c61500 00000000`00000000 : Rt64win7!MpHandleSendInterrupt+0x22c
    fffff880`031b6b60 fffff880`0151a329 : fffffa80`051631a0 fffff800`02c61500 fffffa80`0448a390 fffffa80`051631a0 : Rt64win7!MPReset+0x2c9
    fffff880`031b6ba0 fffff800`02acb161 : fffff880`02fc2500 fffff880`02fc2510 fffff800`02c615a0 fffffa80`00000002 : ndis! ?? ::FNODOBFM::`string'+0x8ca4
    fffff880`031b6cb0 fffff800`02d61166 : 00000034`00000008 fffffa80`03cf8680 00000000`00000080 fffffa80`03ce0740 : nt!ExpWorkerThread+0x111
    fffff880`031b6d40 fffff800`02a9c486 : fffff880`009e9180 fffffa80`03cf8680 fffff880`009f3f40 0000000c`00000008 : nt!PspSystemThreadStartup+0x5a
    fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b69f0 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    Rt64win7!MpHandleSendInterrupt+22c
    fffff880`04288bb8 488d8f48050000  lea     rcx,[rdi+548h]

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  Rt64win7!MpHandleSendInterrupt+22c

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Rt64win7

    IMAGE_NAME:  Rt64win7.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  49a65b0d

    FAILURE_BUCKET_ID:  X64_0xA_Rt64win7!MpHandleSendInterrupt+22c

    BUCKET_ID:  X64_0xA_Rt64win7!MpHandleSendInterrupt+22c

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

    1: kd> lmvm Rt64win7
    start             end                 module name
    fffff880`04278000 fffff880`042aa000   Rt64win7   (pdb symbols)          c:\symbols\rt64win7.pdb\D6FC3FB08A034A9BB7970F3220BFD4041\rt64win7.pdb
        Loaded symbol image file: Rt64win7.sys
        Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
        Image name: Rt64win7.sys
        Timestamp:        Thu Feb 26 04:04:13 2009 (49A65B0D)
        CheckSum:         0002EB30
        ImageSize:        00032000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Sunday, September 27, 2009 8:45 PM

Answers

All replies