locked
Blue Screen - BSOD - Windows 7 Pro 64 bit - DMP file attached! RRS feed

  • Question

  • Greetings, I'm occasionally getting a BSOD.  I'd just like to figure out what causes it.  I'm assuming it's hardware, but I don't know a simple way to locate the problem.  It's a fresh build and was doing it before it was wiped.  Maybe I need new thermal-paste or to reseat something? Who knows!?

    https://www.dropbox.com/s/c3ktpprx29a37p9/012313-11060-01.dmp

    If I can provide anything else, please let me know.  Thanks for any assistance!

    Wednesday, January 23, 2013 8:10 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa7fffffffe0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002af44f0, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfe100
    GetUlongFromAddress: unable to read from fffff80002cfe1c0
     fffffa7fffffffe0 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02af44f0 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  WmiPrvSE.exe
    TRAP_FRAME:  fffff8800c41afc0 -- (.trap 0xfffff8800c41afc0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
    rdx=0000000000000043 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002af44f0 rsp=fffff8800c41b150 rbp=0000000000000000
     r8=fffff80002d01500  r9=fffffa8003900000 r10=fffffa80039003b8
    r11=fffff880009b1180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReplenishPageSlist+0xc0:
    fffff800`02af44f0 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002ace569 to fffff80002acefc0
    STACK_TEXT:  
    fffff880`0c41ae78 fffff800`02ace569 : 00000000`0000000a fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0c41ae80 fffff800`02acd1e0 : fffffa80`03acc148 fffffa80`03acc040 fffff880`009b1180 fffffa7f`ffffffd0 : nt!KiBugCheckDispatch+0x69
    fffff880`0c41afc0 fffff800`02af44f0 : 00000000`00000000 fffffa80`0584a010 00000000`00000000 fffff880`01730755 : nt!KiPageFault+0x260
    fffff880`0c41b150 fffff800`02af2caf : fffffa80`03900398 00000000`00000017 fffffa80`009ed450 00000000`00000017 : nt!MiReplenishPageSlist+0xc0
    fffff880`0c41b1c0 fffff800`02bf800f : 2aaaaaaa`aaaaaaab fffff880`00000004 fffffa80`03907000 fffffa80`00051420 : nt!MiRemoveAnyPage+0x24f
    fffff880`0c41b2e0 fffff800`02aeed50 : 00000000`0000d930 fffff800`02c56580 00000000`00000008 fffff800`02ae0848 : nt!MiAllocatePoolPages+0x98f
    fffff880`0c41b420 fffff800`02bfa90e : 00000000`00000000 fffff800`02bfafbd 00000000`00000000 00000000`0000d930 : nt!ExpAllocateBigPool+0xb0
    fffff880`0c41b510 fffff800`02ae22f6 : 00000000`005355c8 00000000`00000008 fffffa80`05b2e1e0 fffff880`02f8a4e9 : nt!ExAllocatePoolWithTag+0x82e
    fffff880`0c41b600 fffff880`02f8aa1b : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`041d1f40 : nt!ExAllocatePoolWithQuotaTag+0x56
    fffff880`0c41b650 fffff880`02f8bd8a : 00000000`00ffd060 fffff8a0`00000070 fffffa80`07b160e0 00000000`00ffd060 : nsiproxy!NsippProbeAndAllocateParameters+0x447
    fffff880`0c41b7b0 fffff880`02f8d8e8 : fffffa80`07b160e0 fffffa80`07b16010 00000000`00000000 fffffa80`07b16048 : nsiproxy!NsippEnumerateObjectsAllParameters+0x266
    fffff880`0c41b9a0 fffff880`02f8d9db : fffffa80`046237f0 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
    fffff880`0c41b9e0 fffff800`02de5687 : fffffa80`055a3b00 fffffa80`055a3b00 fffffa80`07b16128 fffffa80`07b16010 : nsiproxy!NsippDispatch+0x4b
    fffff880`0c41ba10 fffff800`02de5ee6 : 00000000`00ffcee0 00000000`00000330 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`0c41bb40 fffff800`02ace253 : fffffa80`07970b50 00000000`00ffcec8 fffff880`0c41bbc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
    fffff880`0c41bbb0 00000000`777a138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00ffcf58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777a138a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nsiproxy!NsippProbeAndAllocateParameters+447
    fffff880`02f8aa1b 488bf0          mov     rsi,rax
    SYMBOL_STACK_INDEX:  9
    SYMBOL_NAME:  nsiproxy!NsippProbeAndAllocateParameters+447
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nsiproxy
    IMAGE_NAME:  nsiproxy.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc15e
    FAILURE_BUCKET_ID:  X64_0xA_nsiproxy!NsippProbeAndAllocateParameters+447
    BUCKET_ID:  X64_0xA_nsiproxy!NsippProbeAndAllocateParameters+447
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0xAhttp://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    The Blue Screen caused by ( nsiproxy.sys ) :

    Nsiproxy.sys file information
    The process known as NSI Proxy or NSI proxy service driver belongs to software Microsoft Windows Operating System by Microsoft (www.microsoft.com).

    Please Update the NSI Proxy Driver to the latest version it solve your Blue Screen.

    Regards,


    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

    Thursday, January 24, 2013 8:26 AM
  • Hi,


    Also try to the NIC drivers, and Please be ensured that you have installed the latest drivers and all the updates


    Regards,


    Vincent Wang
    TechNet Community Support

    Friday, January 25, 2013 7:49 AM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa7fffffffe0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002af44f0, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfe100
    GetUlongFromAddress: unable to read from fffff80002cfe1c0
     fffffa7fffffffe0 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!MiReplenishPageSlist+c0
    fffff800`02af44f0 f00fba6b1000    lock bts dword ptr [rbx+10h],0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  WmiPrvSE.exe
    TRAP_FRAME:  fffff8800c41afc0 -- (.trap 0xfffff8800c41afc0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffffff rbx=0000000000000000 rcx=0000058000000000
    rdx=0000000000000043 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002af44f0 rsp=fffff8800c41b150 rbp=0000000000000000
     r8=fffff80002d01500  r9=fffffa8003900000 r10=fffffa80039003b8
    r11=fffff880009b1180 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!MiReplenishPageSlist+0xc0:
    fffff800`02af44f0 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002ace569 to fffff80002acefc0
    STACK_TEXT:  
    fffff880`0c41ae78 fffff800`02ace569 : 00000000`0000000a fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0c41ae80 fffff800`02acd1e0 : fffffa80`03acc148 fffffa80`03acc040 fffff880`009b1180 fffffa7f`ffffffd0 : nt!KiBugCheckDispatch+0x69
    fffff880`0c41afc0 fffff800`02af44f0 : 00000000`00000000 fffffa80`0584a010 00000000`00000000 fffff880`01730755 : nt!KiPageFault+0x260
    fffff880`0c41b150 fffff800`02af2caf : fffffa80`03900398 00000000`00000017 fffffa80`009ed450 00000000`00000017 : nt!MiReplenishPageSlist+0xc0
    fffff880`0c41b1c0 fffff800`02bf800f : 2aaaaaaa`aaaaaaab fffff880`00000004 fffffa80`03907000 fffffa80`00051420 : nt!MiRemoveAnyPage+0x24f
    fffff880`0c41b2e0 fffff800`02aeed50 : 00000000`0000d930 fffff800`02c56580 00000000`00000008 fffff800`02ae0848 : nt!MiAllocatePoolPages+0x98f
    fffff880`0c41b420 fffff800`02bfa90e : 00000000`00000000 fffff800`02bfafbd 00000000`00000000 00000000`0000d930 : nt!ExpAllocateBigPool+0xb0
    fffff880`0c41b510 fffff800`02ae22f6 : 00000000`005355c8 00000000`00000008 fffffa80`05b2e1e0 fffff880`02f8a4e9 : nt!ExAllocatePoolWithTag+0x82e
    fffff880`0c41b600 fffff880`02f8aa1b : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`041d1f40 : nt!ExAllocatePoolWithQuotaTag+0x56
    fffff880`0c41b650 fffff880`02f8bd8a : 00000000`00ffd060 fffff8a0`00000070 fffffa80`07b160e0 00000000`00ffd060 : nsiproxy!NsippProbeAndAllocateParameters+0x447
    fffff880`0c41b7b0 fffff880`02f8d8e8 : fffffa80`07b160e0 fffffa80`07b16010 00000000`00000000 fffffa80`07b16048 : nsiproxy!NsippEnumerateObjectsAllParameters+0x266
    fffff880`0c41b9a0 fffff880`02f8d9db : fffffa80`046237f0 00000000`00000000 00000000`00000001 00000000`00000003 : nsiproxy!NsippDispatchDeviceControl+0x70
    fffff880`0c41b9e0 fffff800`02de5687 : fffffa80`055a3b00 fffffa80`055a3b00 fffffa80`07b16128 fffffa80`07b16010 : nsiproxy!NsippDispatch+0x4b
    fffff880`0c41ba10 fffff800`02de5ee6 : 00000000`00ffcee0 00000000`00000330 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`0c41bb40 fffff800`02ace253 : fffffa80`07970b50 00000000`00ffcec8 fffff880`0c41bbc8 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
    fffff880`0c41bbb0 00000000`777a138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00ffcf58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777a138a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nsiproxy!NsippProbeAndAllocateParameters+447
    fffff880`02f8aa1b 488bf0          mov     rsi,rax
    SYMBOL_STACK_INDEX:  9
    SYMBOL_NAME:  nsiproxy!NsippProbeAndAllocateParameters+447
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nsiproxy
    IMAGE_NAME:  nsiproxy.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc15e
    FAILURE_BUCKET_ID:  X64_0xA_nsiproxy!NsippProbeAndAllocateParameters+447
    BUCKET_ID:  X64_0xA_nsiproxy!NsippProbeAndAllocateParameters+447
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0xAhttp://msdn.microsoft.com/en-us/library/windows/hardware/ff560129(v=vs.85).aspx

    The Blue Screen caused by ( nsiproxy.sys ) :

    Nsiproxy.sys file information
    The process known as NSI Proxy or NSI proxy service driver belongs to software Microsoft Windows Operating System by Microsoft (www.microsoft.com).

    Please Update the NSI Proxy Driver to the latest version it solve your Blue Screen.

    Regards,


    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

    Thursday, January 24, 2013 8:26 AM
  • Hi,


    Also try to the NIC drivers, and Please be ensured that you have installed the latest drivers and all the updates


    Regards,


    Vincent Wang
    TechNet Community Support

    Friday, January 25, 2013 7:49 AM