Bsod page_fault_in_nonpaged_area

Good information.
Glad to hear it's running stable now, the BIOS update could very well have solved the issue.
Next time, please post the information so everyone can see without downloading the files.
That will make it easier for us.

How to Post a Screenshot in Seven Forums

Your CPUZ and Temps:
Attachment 194881Attachment 194880
Attachment 194879Attachment 194878
Attachment 194877
Attachment 194882

Your CPUZ Main Board page is showing BIOS version 23.5, the latest version on your motherboard website is 23.6.
Did you just flash the BIOS to 23.5 or 23.6?
23.6 states - Improved memory compatibility.

You CPU core temps are ok, do you have the stock Intel CPU cooler?
What is your ambient temp?
Intel® Core™ i7-2600K Processor
Your Tcase (CPU case) max temp is 72.6°C add 5°C for core temps gives you a max CPU core temp of 77.6°C.
If you are going to OC to 4.4GHz, or more in the future, you should get an aftermarket CPU cooler.
The air coolers are cheap, for U$30 you can lower the prime95 temps by 10°C.
Mine will run prime95 at 56°C, with my previous Cooler Master 212+ air cooler.

Checked your motherboard manual for the CPU IMC voltage.

Did you set the CPU I/O to 1.344v?
What was the default setting?
That seems a bit high for an Intel board, I would try bumping the DRAM voltage to 1.550v and bring down the CPU I/O (IMC) voltage a little at a time, 0.05v at a time, until it's not stable, then bump it up by 0.02v until it's stable.
The lower the stable voltage the better and cooler for your system.
You don't want the CPU to run un-necessarily hot.

Let us know if you want to leave it 'as is' or adjust settings a little to get it running cooler.

Testing apps:
Ram - memtest86+, Prime 95 torture test
CPU - Prime95, Intel Burn Test,

Playing games can get things running pretty hard.

For +rep, click on the scales in the top right corner of their post.

Attachment 194918....sigh.....BSOD again, 3 more. First two was MEMORY MANAGEMENT and third one was bad pool header. All happened while browsing (with firefox if its any help) while the third happened exactly after a restart. I attach the corresponding files. As for my temps I think that I am ok, but I'm interested about that CPU I/O Voltage. I can't find how much it's supposed to be. Do you reckon the bsod are a result of that or the low ram voltage?

P.S. Actually firefox crashed many times before the BSODs. Oh and I managed to play more than one hour of bf3 perfectly, the BSODs happened after I decided to just browse. The irony is that I was about to put thr thread's status to 'resolved'.

Oh and the new BIOS I use is version 23.6.
Are those voltages ok? I just read that the default CPU I/O voltage for 2600k is about 1.05-1.08 volts, so I think I'll have to change that to manual (the 1.344 value for IMC in the bios was not set by me, it was on auto)

Set your DRAM voltage to Manual and 1.550v.
Set the CPU I/O (IMC) voltage to Manual and 1.150v

Save and exit EUFI.
Test for stability, regular use or run Prime95 torture test.
First open Real Temp to monitor CPU temperatures, don't go over 77.6°C.
Open Prime95 and stop the test if it is running, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 8, then click OK to start the test.


If this doesn't get your system stable then we can lock in the first four RAM timings and the frequency manually.

Next step after that will be to remove your OC and check for stability.

Same type of crash as before.
Both of these are likely due to RAM setting issues.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003eb1910
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003eb35c0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

PROCESS_NAME:  WerFault.exe

Your Firefox crash.
STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Usual causes: Device driver, Memory
This looks like it is due to a RAM error.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff6fb40003ff8, Virtual address for the attempted write.
Arg2: 008000015007f025, PTE contents.
Arg3: fffff88009b426c0, (reserved)
Arg4: 000000000000000b, (reserved)

Debugging Details:
------------------
PROCESS_NAME:  firefox.exe

Hello, thank you again for helping me. Still, no good news...

Before you posted the above I tried some things on my own yesterday. With the system overclocked at 4.4 ghz, IMC at 1.12 and RAM at 1.51 I tried browsing (multiple tabs), playing an hd video and doing a microsoft security essentials full system scan...in 5 mins BSOD. Without changing anything, I restarted, fired up BF3 and played for half an hour, no issues, then started browsing this time with IE and (can you guess?) BSOD. I then revert to default clocks and all other settings for voltages to auto apart from IMC manually set to 1.12 (for some reason, when it's left to auto it is defaulting at 1.344 V). I start the same procedure (browsing, HD videos and scans) and encounter no problems. I play BF3 mp for 2 hours straight and then go to work at which point my brother continues playing bf3 for another 3 hours with no problems at all...after that he calls me and asks me if I want to him to shut down my pc and I tell him to open firefox, open a million tabs, open utorrent, fire up any hd movie he things and start an MSE full scan and leave it there. When I got back everything was running okay. I assumed that my OC was too high or my bios settings were wrong and just leave it to default....and BAM, half an hour later BSOD....

Today when I saw your post I changed the ram voltages to the values you suggested and OCed to my previous 4.4 ghz. After a little browsing again BSOD. I restart, no changes and ran prime95, dollowing your instructions to the letter and passed it with no errors. I even re-run it but instead of 'blend' I use 'In-place large FFTs' and again no problems.....Am I to assume that my CPU and RAM are working ok and something else is the cause for the crashes?

It could possibly be a driver, but with memtest86+ errors previously makes the 16GB RAM the most likely culprit.

First, check your SSD firmware version.
The latest firmware is v2.15.
SSD Firmware Updates and Tools for OCZ Vertex 3
If you need to update it, read the info and recommended procedure at the link above.

Even if memtest86+ passes several times with no errors, then shows an error (one is too many) it is a RAM card or settings issue.

Your system was more stable with the CPU frequency set at stock, this indicates an issue with your OC.

Set your DRAM voltage to Manual and 1.550v.
Set the CPU I/O (IMC) voltage to Manual and 1.150v
Manually set your RAM frequency to 800MHz (will be running at 1600MHz).
Manually set your first four RAM timings to 9-9-9-24, leave the rest on 'Auto'.
Make sure the 'Command Rate' is at 2T.

Save and Exit EUFI.

Try to re-create the crash scenario with CPU frequency OC'ed.
If it crashes, leave all the RAM settings as listed above and set your CPU OC back to stock settings, try to re-create the crash scenario.

Let us know the results.

Your can leave the tRTL on 'Auto'.
Make sure both Channels have the same timing settings, 9-9-9-24, and the Command Rate at 2T.
Set the 'DRAM Timing Mode' to 'Link' will give you the same timings in both channels.
Set the 'Extreme Memory Profile (X.M.P.)' to 'Disable'.

1. Spread Spectrum - enabled.
2. VDroop - Low VDroop.
3. Bump the CPU I/O Voltage to 1.160v, DRAM Voltage is ok.
4. System agent voltage - auto
5. Internal PLL Overvoltage and CPU PLL Voltage - both on Auto

Let's try the above settings first.


Latest dump files.

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

This is indicating fltmgr.sys - Microsoft Filesystem Filter Manager.
This is pointing at the SSD, file system.
What do you have your memory Page File set to?

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
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.
Arguments:
Arg1: fffffab40f92fc58, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880011c40fe, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efd100
 fffffab40f92fc58 

FAULTING_IP: 
fltmgr! ?? ::NNGAKEGL::`string'+1087
fffff880`011c40fe 0fb74818        movzx   ecx,word ptr [rax+18h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880039385e0 -- (.trap 0xfffff880039385e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffab40f92fc40 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8011eed430 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880011c40fe rsp=fffff88003938770 rbp=fffff8800119a000
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002c4e000
r11=fffff8a011205c38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr! ?? ::NNGAKEGL::`string'+0x1087:
fffff880`011c40fe 0fb74818        movzx   ecx,word ptr [rax+18h] ds:5c38:fffffab4`0f92fc58=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c753bf to fffff80002ccac40

STACK_TEXT:  
fffff880`03938478 fffff800`02c753bf : 00000000`00000050 fffffab4`0f92fc58 00000000`00000000 fffff880`039385e0 : nt!KeBugCheckEx
fffff880`03938480 fffff800`02cc8d6e : 00000000`00000000 fffffab4`0f92fc58 00000000`00000000 fffff8a0`11205c38 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`039385e0 fffff880`011c40fe : fffff8a0`11a52230 00000000`00000040 fffffa80`121f3538 00000000`000007ff : nt!KiPageFault+0x16e
fffff880`03938770 fffff880`011bf311 : fffffa80`0cd88800 00000000`00000130 fffff8a0`11123760 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1087
fffff880`039387a0 fffff880`011bf3fb : fffffa80`0cd88800 fffff8a0`111239c8 fffffa80`0cd88800 fffffa80`0cdf3040 : fltmgr!CleanupStreamListCtrl+0x21
fffff880`039387e0 fffff800`02f8390e : 00000000`00000001 fffff800`02ca6c2f 00000000`00000705 fffff880`01618f49 : fltmgr!DeleteStreamListCtrlCallback+0x6b
fffff880`03938810 fffff880`0169bbac : fffff8a0`11123760 fffffa80`0cdf3040 fffff880`039388e8 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2
fffff880`03938860 fffff880`016a0cc1 : 00000000`01010000 00000000`00000000 fffff800`02e6b200 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108
fffff880`039388a0 fffff880`0161985c : fffff8a0`11123660 fffff8a0`11123760 fffff800`02e6b200 fffff880`03938a12 : Ntfs!NtfsRemoveScb+0x61
fffff880`039388e0 fffff880`0169e64c : fffff8a0`11123630 fffff800`02e6b260 fffff880`03938a12 fffffa80`12175010 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`03938910 fffff880`016200e2 : fffffa80`12175010 fffffa80`12175010 fffff8a0`11123630 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`03938990 fffff880`016ae193 : fffffa80`12175010 fffff800`02e6b260 fffff8a0`11123630 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`039389d0 fffff880`0169d357 : fffffa80`12175010 fffff8a0`11123760 fffff8a0`11123630 fffffa80`0f9be180 : Ntfs!NtfsCommonClose+0x353
fffff880`03938aa0 fffff800`02cd5001 : 00000000`00000000 fffff800`02fc1900 fffff800`02ecc801 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`03938b70 fffff800`02f65fee : 00000000`00000000 fffffa80`0cdf3040 00000000`00000080 fffffa80`0cd02740 : nt!ExpWorkerThread+0x111
fffff880`03938c00 fffff800`02cbc5e6 : fffff880`0376d180 fffffa80`0cdf3040 fffff880`037780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03938c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fltmgr! ?? ::NNGAKEGL::`string'+1087
fffff880`011c40fe 0fb74818        movzx   ecx,word ptr [rax+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  fltmgr! ?? ::NNGAKEGL::`string'+1087

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929c

FAILURE_BUCKET_ID:  X64_0x50_fltmgr!_??_::NNGAKEGL::_string_+1087

BUCKET_ID:  X64_0x50_fltmgr!_??_::NNGAKEGL::_string_+1087

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

Do you have a HDD in your system?
You may need to install the OS on the HDD for testing, just to rule out that this is a SSD, SandForce controller, issue.

Let us know how the RAM settings testing is going first.