BSOD Page fault in non paged area

I'd suggest you once again to uninstall Avast! internet security and replace with MSE to test.

The errors you are getting on your dumps are usually caused by stubborn Antivirus software.

Code:

fffff880`0335b9c0  fffff880`0177d200 tcpip!LruContext
fffff880`0335b9c8  fffff880`015807e6 NETIO!WfppIncrementIndexAndPurgeEntries+0x166
fffff880`0335b9d0  fffff880`0177d200 tcpip!LruContext
fffff880`0335b9d8  fffffa80`0dd203b0
fffff880`0335b9e0  00000000`00000000
fffff880`0335b9e8  fffff880`0177d200 tcpip!LruContext
fffff880`0335b9f0  fffff880`0335b9f0
fffff880`0335b9f8  fffff880`0335b9f0
fffff880`0335ba00  00000000`00000000
fffff880`0335ba08  fffff880`0177e200 tcpip!LruContext+0x1000
fffff880`0335ba10  fffffa80`0cade148
fffff880`0335ba18  00000000`00000000
fffff880`0335ba20  fffff880`0177d200 tcpip!LruContext
fffff880`0335ba28  fffffa80`0cade040
fffff880`0335ba30  fffff880`0177d8c0 tcpip!LruContext+0x6c0
fffff880`0335ba38  fffff880`01580839 NETIO!WfppLeastRecentlyUsedTimerRoutine+0x19
fffff880`0335ba40  00000000`00000004
fffff880`0335ba48  fffff880`0177d240 tcpip!LruContext+0x40
fffff880`0335ba50  fffff880`0177d990 tcpip!LruContext+0x790
fffff880`0335ba58  fffff880`0177d200 tcpip!LruContext
fffff880`0335ba60  fffff880`0335bb10
fffff880`0335ba68  fffff880`0177d601 tcpip!LruContext+0x401
fffff880`0335ba70  fffffa80`0dd58f30
fffff880`0335ba78  00000000`00000000
fffff880`0335ba80  fffff880`0177d240 tcpip!LruContext+0x40
fffff880`0335ba88  fffff880`0158041f NETIO!WfpTimerWheelTimeoutHandler+0xff
fffff880`0335ba90  fffff880`0177d650 tcpip!LruContext+0x450
fffff880`0335ba98  fffff880`0177d990 tcpip!LruContext+0x790
fffff880`0335baa0  00000000`00000000
fffff880`0335baa8  fffffa80`0dd58f30
fffff880`0335bab0  fffffa80`0cade040
fffff880`0335bab8  fffffa80`12ad9220
fffff880`0335bac0  0000057f`00000000
fffff880`0335bac8  fffff800`038672d8 nt!ExWorkerQueue+0x58
fffff880`0335bad0  00000000`00000000
fffff880`0335bad8  fffffa80`0f6239e0
fffff880`0335bae0  00000000`00000000
fffff880`0335bae8  00000000`00000001
fffff880`0335baf0  fffffa80`0d4d5e00
fffff880`0335baf8  fffffa80`0dd58f30
fffff880`0335bb00  fffff800`038672d8 nt!ExWorkerQueue+0x58
fffff880`0335bb08  fffff880`01580a2e NETIO!WfpSysTimerPassiveCallback+0x2e
fffff880`0335bb10  00000000`000000ff
fffff880`0335bb18  00000000`00000000
fffff880`0335bb20  fffff880`0177d8c0 tcpip!LruContext+0x6c0
fffff880`0335bb28  fffffa80`0cade040
fffff880`0335bb30  fffffa80`0d4d5e00
fffff880`0335bb38  fffff800`039bc583 nt!IopProcessWorkItem+0x23
fffff880`0335bb40  fffffa80`0dd0e6c0
fffff880`0335bb48  00000000`00000001
fffff880`0335bb50  fffffa80`126f0bc0
fffff880`0335bb58  fffffa80`0cade040
fffff880`0335bb60  fffff800`039bc560 nt!IopProcessWorkItem
fffff880`0335bb68  fffff800`036d3641 nt!ExpWorkerThread+0x111
fffff880`0335bb70  fffff800`03867200 nt!ExpWorkerThreadBalanceManagerPtr
fffff880`0335bb78  fffff800`039bc501 nt!ObpWaitForMultipleObjects+0x47b
fffff880`0335bb80  fffffa80`0cade000

Code:

fffff880`0b4c3b78  fffff800`03683fc0 nt!KiSystemCall64
fffff880`0b4c3b80  fffff880`01162320 fltmgr!FltpCloseCommunicationPort
fffff880`0b4c3b88  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3b90  fffff880`0114d630 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e630)
fffff880`0b4c3b98  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3ba0  fffff880`0114d318 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e318)
fffff880`0b4c3ba8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3bb0  fffff880`0114e284 fltmgr!__PchSym_ <PERF> (fltmgr+0x1f284)
fffff880`0b4c3bb8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3bc0  fffff880`0114e5a8 fltmgr!__PchSym_ <PERF> (fltmgr+0x1f5a8)
fffff880`0b4c3bc8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3bd0  fffff880`0114f610 fltmgr!__PchSym_ <PERF> (fltmgr+0x20610)
fffff880`0b4c3bd8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3be0  fffff880`0114ed88 fltmgr!__PchSym_ <PERF> (fltmgr+0x1fd88)
fffff880`0b4c3be8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3bf0  fffff880`0114e5cc fltmgr!__PchSym_ <PERF> (fltmgr+0x1f5cc)
fffff880`0b4c3bf8  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3c00  fffff880`0114dabc fltmgr!__PchSym_ <PERF> (fltmgr+0x1eabc)
fffff880`0b4c3c08  fffff880`0112f000 fltmgr!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`0b4c3c10  fffff880`0114d054 fltmgr!__PchSym_ <PERF> (fltmgr+0x1e054)
fffff880`0b4c3c18  fffff800`03606000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0b4c3c20  fffff800`0389eb74 nt!BBTBuffer <PERF> (nt+0x298b74)
fffff880`0b4c3c28  fffff800`03606000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`0b4c3c30  fffff800`0388ae94 nt!BBTBuffer <PERF> (nt+0x284e94)
fffff880`0b4c3c38  fffff880`01136628 fltmgr!TreeUnlinkNoBalance+0x8
fffff880`0b4c3c40  fffff880`0b4c3cd0
fffff880`0b4c3c48  fffff880`0b4c4478
fffff880`0b4c3c50  fffff880`01136627 fltmgr!TreeUnlinkNoBalance+0x7

Test your ram sticks again.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Thanks for the update..
Let us know how things are after a few weeks and you can mark the thread as solved.