Windows 8 and 8.1 Forums

BSOD Page Fault In Non Paged Area when waking

  1. #1

    Posts : 1
    Windows 8.1

    BSOD Page Fault In Non Paged Area when waking

    Hi all,

    I'm getting a BSOD every time i wake my machine from Hibernation or Sleep.

    Running Windows 8.1 on Lenovo Thinkpad e540 that is about 2 months old. I'm a developer so have lots of different dev tools installed but it only started happening a week or so ago.

    Thanks in advance

      My System SpecsSystem Spec

  2. #2

    Posts : 660
    windows 8.1

    The BSods of your dumpfile all are BugCheck 50, {fffff6fb40000000, 0, 0, 6}
    Could not read faulting driver name
    Probably caused by : tcpip.sys ( tcpip!RssDeleteBinding+8a )
    This is probably a networkrelated problem

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffff6fb40000000, 0, 0, 6}
    Could not read faulting driver name
    Probably caused by : tcpip.sys ( tcpip!RssDeleteBinding+8a )
    Followup: MachineOwner
    0: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: fffff6fb40000000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000006, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80213956138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    PROCESS_NAME:  System
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    TRAP_FRAME:  ffffd0002883bd60 -- (.trap 0xffffd0002883bd60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff6fb40000000 rbx=0000000000000000 rcx=00000904c0000000
    rdx=fffff80213602000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802136950e8 rsp=ffffd0002883bef0 rbp=0000000000000001
     r8=0000000000000000  r9=0000000000000000 r10=fffff780000003b0
    r11=ffffd0002883c078 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    fffff802`136950e8 488b00          mov     rax,qword ptr [rax] ds:fffff6fb`40000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff8021377c3b8 to fffff80213755fa0
    ffffd000`2883bb18 fffff802`1377c3b8 : 00000000`00000050 fffff6fb`40000000 00000000`00000000 fffff6fb`7da00000 : nt!KeBugCheckEx
    ffffd000`2883bb20 fffff802`13669523 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd000`2883bc82 : nt! ?? ::FNODOBFM::`string'+0x15f08
    ffffd000`2883bc20 fffff802`1376022f : 00000000`00000000 ffffe001`b8f19f70 00000000`00000000 ffffd000`2883bd60 : nt!MmAccessFault+0x303
    ffffd000`2883bd60 fffff802`136950e8 : fffff802`138e8180 fffff802`13758eef 00000000`00000100 fffff800`10489311 : nt!KiPageFault+0x12f
    ffffd000`2883bef0 fffff802`138979cd : 00000000`00000000 ffffd000`2883c078 00000000`00000000 00000000`00000000 : nt!ExFreeLargePool+0x78
    ffffd000`2883bf90 fffff800`1064796a : fffff800`106224a0 ffffe001`00000000 fffff800`10622c00 00000000`00000000 : nt!ExFreePoolWithTag+0x6ed
    ffffd000`2883c060 fffff800`1063f595 : fffff800`10622400 ffffe001`b8f19f70 00000000`00000010 fffff800`10614101 : tcpip!RssDeleteBinding+0x8a
    ffffd000`2883c0a0 fffff800`104d7155 : 00000000`00000016 ffffd000`2883c1b0 fffff800`10614100 ffffe001`a4dd3510 : tcpip!RssControlDeleteInterface+0x1dcd
    ffffd000`2883c110 fffff800`104ea6e6 : ffffe001`a4df9830 fffff800`10614100 ffffe001`a5f11190 ffffe001`a4df2000 : tcpip!OlmNotifyDeleteInterface+0x25
    ffffd000`2883c140 fffff800`104d4ec0 : ffffe001`a5f31980 ffffe001`00000002 ffffe001`b8f117c0 fffff800`10614180 : tcpip!IppNotifyInterfaceChangeToNlClients+0x1ae
    ffffd000`2883c1f0 fffff800`104d4ce8 : ffffe001`b8f1aa30 ffffd000`2883c330 ffffe001`b8f13d50 ffffd000`2883c330 : tcpip!IpFlcDeleteInterface+0x1b0
    ffffd000`2883c260 fffff800`104d4fb9 : ffffe001`b8f1aa30 fffff800`1061e870 00000000`00000000 fffff802`13660186 : tcpip!FlpDeleteInterface+0xa0
    ffffd000`2883c2d0 fffff800`102c829f : ffffd000`2883c3f0 ffffe001`a5fd4c10 ffffe001`b8f10540 ffffe001`a5fd4c10 : tcpip!FlUnbindAdapter+0xa5
    ffffd000`2883c350 fffff800`102fb414 : ffffe001`b8f10540 ffffe001`b71d21a0 ffffe001`b71d2100 ffffe001`00000000 : ndis!ndisInvokeUnbindAdapter+0x2f
    ffffd000`2883c390 fffff800`102c8ad0 : ffffe001`00000000 ffffe001`b71d35e8 ffffe001`b8f10540 ffffc000`82d6cd90 : ndis!ndisUnbindProtocolOpen+0x168
    ffffd000`2883c4b0 fffff800`102bc252 : ffffc000`82d6cd98 ffffd000`2883c5f0 ffffe001`b71d35e8 fffff802`1366a066 : ndis!ndisUnbindEachProtocolOpenOnMiniport+0x70
    ffffd000`2883c4f0 fffff800`102bc47c : ffffe001`b71d21a0 ffffe001`b71d21a0 ffffd000`2883c700 ffffe001`b71d35e8 : ndis!Ndis::BindEngine::Iterate+0x802
    ffffd000`2883c700 fffff800`102ba708 : ffffe001`b71d35e8 ffffd000`2883c900 ffffd000`2883c780 ffffd000`2883c900 : ndis!Ndis::BindEngine::UpdateBindings+0x64
    ffffd000`2883c730 fffff800`102bc5b7 : ffffe001`b71d35e8 ffffe001`b71d35e8 00000000`00001001 fffff800`102bc514 : ndis!Ndis::BindEngine::DispatchPendingWork+0x50
    ffffd000`2883c760 fffff800`102babdc : ffffe001`b71d21a0 ffffe001`b71d35e8 ffffc000`8534bef0 ffffd000`2883c800 : ndis!Ndis::BindEngine::ApplyBindChanges+0x37
    ffffd000`2883c7b0 fffff800`102fb7ae : ffffe001`b71d21a0 ffffd000`2883c990 ffffe001`b71d35e8 ffffe001`a7964b90 : ndis!ndisMSetMiniportReadyForBinding+0x64
    ffffd000`2883c890 fffff800`102c86d9 : ffffe001`b71d21a0 ffffd000`2883cbd0 ffffe001`b71d21a0 ffffe001`b71d21a0 : ndis!ndisPnPRemoveDevice+0x1ae
    ffffd000`2883cae0 fffff800`102c865d : ffffe001`b71d21a0 ffffe001`b71d21a0 fffff802`138a5300 ffffe001`00000000 : ndis!ndisPnPRemoveDeviceEx+0x59
    ffffd000`2883cb10 fffff802`13655adb : fffff802`13a989bc 00000000`00000000 fffff802`138d57a0 ffffe001`bf4ca040 : ndis!ndisPnPIrpSurpriseRemovalInner+0x79
    ffffd000`2883cb50 fffff802`136d1794 : ffffe001`be6ef890 ffffe001`bf4ca040 ffffe001`bf4ca040 ffffe001`a2c63900 : nt!ExpWorkerThread+0x293
    ffffd000`2883cc00 fffff802`1375c5c6 : ffffd000`a9727180 ffffe001`bf4ca040 ffffe001`bf31d880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`2883cc60 00000000`00000000 : ffffd000`2883d000 ffffd000`28837000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    fffff800`1064796a 8b8380000000    mov     eax,dword ptr [rbx+80h]
    SYMBOL_NAME:  tcpip!RssDeleteBinding+8a
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: tcpip
    IMAGE_NAME:  tcpip.sys
    IMAGE_VERSION:  6.3.9600.17039
    FAILURE_BUCKET_ID:  AV_tcpip!RssDeleteBinding
    BUCKET_ID:  AV_tcpip!RssDeleteBinding
    FAILURE_ID_HASH_STRING:  km:av_tcpip!rssdeletebinding
    FAILURE_ID_HASH:  {399dbea8-29d6-1732-075e-e76fc133ef96}
    Followup: MachineOwner
    In your msinfo32 i found this device has problems:
    <Device><![CDATA[IWD Bus Enumerator]]></Device>
    <Error_Code><![CDATA[This device is not working properly because Windows cannot load the drivers required for this device.]]></Error_Code>
    Please install the drivers.

    Driver Description: Intel WIDI Bus Enumerator driver
    Related to Intel Widi - Wireless Display
    Driver Update Site:
      My System SpecsSystem Spec

BSOD Page Fault In Non Paged Area when waking
Related Threads
Hello, I just had this "page_fault_in_non-paged_area" error show up on a blue screen. It happened right after I woke my laptop up from sleep mode. I have no idea what this means...any ideas what the problem is and how to fix it? Any help would be appreciated. Joshua
Solved Bsod page fault in non paged area ivy bridge in BSOD Crashes and Debugging
this pc was built around 1 year ago 3570K @ 4.2gHZ stock volts max temps around 75c using a hyper 212 plus P8Z77-V Bios 2104 Sapphire 7950 dual x fans running stock with AMD beta 14.4 2x4GB corsair memory they are rated at 1600mhz the motherboard set it to 1333hz as default but i switched...
Hello, I am very new to the forums and was browsing around looking at other people with similar problems and thought I would post up my issues and see if anyone can help point me in the right directions. I have a couple of ideas but I am unsure if I am right... I have attached the ZIP of the...
I got this new pc and whether it be playing league of legends, surfing the internet, i get a whole variety of BSOD's. I've gotten PAGE FAULT IN NON PAGED AREA around 20 times. SYSTEM THREAD EXCEPTION NOT HANDLED 2 or 3 times IRQL NOT LESS OR EQUAL one time system thread exception not handled )...
BSOD - page fault in non paged area in BSOD Crashes and Debugging
Hi guys, A couple of days after i bought my laptop (maybe 4 months ago)I've been experiencing BSOD's. At first it was once a day, until it turns several crashes a day (like maybe 15 crashes). I cant tolerate it anymore so i brought it to a service center. They fixed the issue, they said it's...
Hi, have been having this issue for a few months. 98% of the time my machine crashes on waking from Sleep or Hibernate with BSOD PAGE_FAULT_IN_NONPAGED_AREA. Thought it was maybe due to Intel drivers but have tried uninstalling/reinstalling to no avail. Have also tried Memtest86+ with no...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook