BOSD Non-Page


  1. Posts : 225
    windows 7 professional x32
       #1

    BOSD Non-Page


    I got a laptop that keeps BSOD randomly and it on gives me a Non-page BSOD. Attach is the docs on the subject.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi ZMan.

    Upload your MSINFO32.nfo file to give us a proper/deeper view.

    1. Click on the start button
    2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
    3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
    4. Give the time for processing, it will save a .nfo file on your desktop.
    5. Zip it, and upload it following the instruction.

    _____________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffffa80086dd046, 2, 0, fffff8800569292a}
    
    *** 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+792a )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    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: fffffa80086dd046, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800569292a, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100
    GetUlongFromAddress: unable to read from fffff800032fe1c0
     fffffa80086dd046 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    NETw5s64+792a
    fffff880`0569292a 8b444f04        mov     eax,dword ptr [rdi+rcx*2+4]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA2FB0
    
    TRAP_FRAME:  fffff80000b9b460 -- (.trap 0xfffff80000b9b460)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80086dcf70 rbx=0000000000000000 rcx=0000000000000065
    rdx=0000000000000806 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800569292a rsp=fffff80000b9b5f0 rbp=fffffa8005578030
     r8=fffff80000b9b6d0  r9=fffff80000b9b650 r10=fffffa80086dcf68
    r11=fffffa80086dcf50 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    NETw5s64+0x792a:
    fffff880`0569292a 8b444f04        mov     eax,dword ptr [rdi+rcx*2+4] ds:00000000`000000ce=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030c6169 to fffff800030c6bc0
    
    STACK_TEXT:  
    fffff800`00b9b318 fffff800`030c6169 : 00000000`0000000a fffffa80`086dd046 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9b320 fffff800`030c4de0 : 00000000`00000000 fffff800`00b9b460 00000000`00000000 fffffa80`086dcf10 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9b460 fffff880`0569292a : 00000000`00000008 fffff880`0176e9a0 00000000`00000000 fffffa80`04a5dc38 : nt!KiPageFault+0x260
    fffff800`00b9b5f0 00000000`00000008 : fffff880`0176e9a0 00000000`00000000 fffffa80`04a5dc38 00000000`00000006 : NETw5s64+0x792a
    fffff800`00b9b5f8 fffff880`0176e9a0 : 00000000`00000000 fffffa80`04a5dc38 00000000`00000006 fffff880`0168dce6 : 0x8
    fffff800`00b9b600 00000000`00000000 : fffffa80`04a5dc38 00000000`00000006 fffff880`0168dce6 00000000`00000018 : tcpip!Ipv4Global
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    NETw5s64+792a
    fffff880`0569292a 8b444f04        mov     eax,dword ptr [rdi+rcx*2+4]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  NETw5s64+792a
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETw5s64
    
    IMAGE_NAME:  NETw5s64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4aafedb7
    
    FAILURE_BUCKET_ID:  X64_0xD1_NETw5s64+792a
    
    BUCKET_ID:  X64_0xD1_NETw5s64+792a
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_netw5s64+792a
    
    FAILURE_ID_HASH:  {8646f7a1-4970-e01b-3fc9-293f1bd3094b}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm NETw5s64
    start             end                 module name
    fffff880`0568b000 fffff880`05d38000   NETw5s64 T (no symbols)           
        Loaded symbol image file: NETw5s64.sys
        Image path: \SystemRoot\system32\DRIVERS\NETw5s64.sys
        Image name: NETw5s64.sys
        Timestamp:        Wed Sep 16 01:10:39 2009 (4AAFEDB7)
        CheckSum:         006A6E93
        ImageSize:        006AD000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 225
    windows 7 professional x32
    Thread Starter
       #3

    Here it is I thought it was already in the batch sorry about that.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4
      My Computer


  5. Posts : 225
    windows 7 professional x32
    Thread Starter
       #5

    The wireless drivers was the cause of BSOD? Downloading now.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    What is the situation after applying it?
      My Computer


  7. Posts : 225
    windows 7 professional x32
    Thread Starter
       #7

    Arc said:
    What is the situation after applying it?
    Ran some test on it and no more BSOD! Thanks Arc!
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Good news.

    Let us know about any further issue.
      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 09:02.
Find Us