Vista - Page Fault in Nonpage Area 0x00000050

jpeterson92 · 08-11-2008

Hi,

Recently, after varying times of general computer usage (internet, e-mail) ranging from 5 minutes to an hour, I'll get a BSOD, with the above title. I'll attach the dump files, and include the code from it below. I've tried some troubleshooting of my own. I've run memtest86+ on each of my 4 1-gig RAM modules, all clean. I've run Prime95, clean. I've installed new video drivers. I've run a diskcheck, and used Western Digital's diagnostic utility, clean. The culprit always is ntfs.sys. Should I try to repair my windows, or replace the ntfs.sys with a new one? Any advice is greatly appreciated. Also, I don't have any readboost of USB storage devices plugged in.

Code:

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: fffffa610b3a9ff8, memory referenced. 
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. 
Arg3: fffffa6001219130, 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 fffff80002c70080 
 fffffa610b3a9ff8  
 
FAULTING_IP:  
Ntfs!memcpy+2c0 
fffffa60`01219130 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8] 
 
MM_INTERNAL_CODE:  5 
 
CUSTOMER_CRASH_COUNT:  9 
 
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT 
 
BUGCHECK_STR:  0x50 
 
PROCESS_NAME:  System 
 
CURRENT_IRQL:  0 
 
TRAP_FRAME:  fffffa60055b0ce0 -- (.trap 0xfffffa60055b0ce0) 
NOTE: The trap frame does not contain all registers. 
Some register values may be zeroed or incorrect. 
rax=0000000000000040 rbx=0000000000000000 rcx=fffffa8104fea000 
rdx=ffffffe0063c0000 rsi=fffff880090b3140 rdi=fffffa6001220374 
rip=fffffa6001219130 rsp=fffffa60055b0e78 rbp=00000000ffffffff 
 r8=00000000ffffffff  r9=0000000007ffffff r10=fffffa60055b14f0 
r11=fffffa8004fea001 r12=0000000000000000 r13=0000000000000000 
r14=0000000000000000 r15=0000000000000000 
iopl=0         nv up ei ng nz na po nc 
Ntfs!memcpy+0x2c0: 
fffffa60`01219130 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8] ds:1970:fffffa61`0b3a9ff8=???????????????? 
Resetting default scope 
 
LAST_CONTROL_TRANSFER:  from fffff80002aaa4e2 to fffff80002a9c390 
 
STACK_TEXT:   
fffffa60`055b0be8 fffff800`02aaa4e2 : 00000000`00000050 fffffa61`0b3a9ff8 00000000`00000000 fffffa60`055b0ce0 : nt!KeBugCheckEx 
fffffa60`055b0bf0 fffff800`02a9af19 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`ffffffff : nt!MmAccessFault+0x4f2 
fffffa60`055b0ce0 fffffa60`01219130 : fffffa60`0123988e fffffa00`06000000 fffffa60`012d1f9a 00000000`00000000 : nt!KiPageFault+0x119 
fffffa60`055b0e78 fffffa60`0123988e : fffffa00`06000000 fffffa60`012d1f9a 00000000`00000000 fffffa60`055b14f0 : Ntfs!memcpy+0x2c0 
fffffa60`055b0e80 fffffa60`0123a735 : 00000000`00000000 fffffa60`055b1194 fffff880`090b3140 00000000`00000030 : Ntfs!NtfsCopyFromMdl+0x17b 
fffffa60`055b0f60 fffffa60`0120d684 : fffff880`090b3140 fffffa60`055b1140 00000000`00000000 00000000`00010000 : Ntfs!NtfsPrepareSparseWriteBuffer+0x85 
fffffa60`055b0fb0 fffffa60`01221bc7 : fffffa60`055b14f0 fffffa80`04642010 fffff880`090b3101 00000000`00000010 : Ntfs! ?? ::FNODOBFM::`string'+0x46f7 
fffffa60`055b1070 fffffa60`0121f963 : 00000000`00000000 fffffa60`055b14f0 fffffa60`055b1190 00000000`0002d000 : Ntfs!NtfsPrepareBuffers+0x177 
fffffa60`055b10f0 fffffa60`0121bf2e : fffffa60`055b14f0 fffffa80`04642010 00000000`00004000 00000000`00000000 : Ntfs!NtfsNonCachedIo+0x1c3 
fffffa60`055b12c0 fffffa60`0121f118 : fffffa60`055b14f0 fffffa80`04642010 fffffa60`055b1601 fffffa60`055b1600 : Ntfs!NtfsCommonWrite+0x4ce 
fffffa60`055b14c0 fffffa60`00764e17 : fffffa80`046423b0 fffffa80`04642010 fffffa80`03e9c040 fffffa80`09c23cb0 : Ntfs!NtfsFsdWrite+0x208 
fffffa60`055b1730 fffffa60`007640dd : fffffa80`04d82ac0 fffffa80`0958e050 fffffa80`03e9c000 fffff800`02bc0b00 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x227 
fffffa60`055b17a0 fffff800`02abbbcd : fffffa80`03e9c040 fffffa80`03e9c040 00000000`0000000b fffffa80`0958e050 : fltmgr!FltpDispatch+0xcd 
fffffa60`055b1800 fffff800`02aba90d : 00000000`00000008 fffff880`0a4c7180 fffffa60`055b1920 00000000`00000000 : nt!IoSynchronousPageWrite+0x14d 
fffffa60`055b1830 fffff800`02aae069 : fffff880`0a4c7160 fffff880`0a4c7180 fffffa80`0994aea0 fffffa80`0994aea0 : nt!MiFlushSectionInternal+0x7ce 
fffffa60`055b1a30 fffff800`02ab1989 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0896d720 : nt!MmFlushSection+0x2a9 
fffffa60`055b1af0 fffff800`02ab5450 : fffffa80`09dbc360 00000000`00000000 fffffa60`00000001 fffffa60`055b1ca0 : nt!CcFlushCache+0x65a 
fffffa60`055b1be0 fffff800`02ab5f9b : 00000000`00000100 00000000`00000000 00000000`00000000 fffff800`02c45800 : nt!CcWriteBehind+0x1c0 
fffffa60`055b1c70 fffff800`02aa905a : fffffa80`039b74a0 fffff800`02c458a0 fffffa80`09ced520 fffffa80`00000001 : nt!CcWorkerThread+0x17b 
fffffa60`055b1cf0 fffff800`02cbff73 : fffffa80`039b74a0 fffffffe`9a5f4400 fffffa80`0896d720 00000000`00000080 : nt!ExpWorkerThread+0x11a 
fffffa60`055b1d50 fffff800`02ad6526 : fffff800`02bbb680 fffffa80`0896d720 fffffa80`0896d040 00000000`00000001 : nt!PspSystemThreadStartup+0x57 
fffffa60`055b1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 
 
 
STACK_COMMAND:  kb 
 
FOLLOWUP_IP:  
Ntfs!memcpy+2c0 
fffffa60`01219130 4c8b4c0af8      mov     r9,qword ptr [rdx+rcx-8] 
 
SYMBOL_STACK_INDEX:  3 
 
SYMBOL_NAME:  Ntfs!memcpy+2c0 
 
FOLLOWUP_NAME:  MachineOwner 
 
MODULE_NAME: Ntfs 
 
IMAGE_NAME:  Ntfs.sys 
 
DEBUG_FLR_IMAGE_TIMESTAMP:  479190d1 
 
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!memcpy+2c0 
 
BUCKET_ID:  X64_0x50_Ntfs!memcpy+2c0 
 
Followup: MachineOwner 
---------

**dmex** · 08-11-2008

Hi jpeterson92,

Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050.

Cause

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

See Microsofts Blue Screen Of Death Database for ways to resolve the error here:
Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

Steven

jpeterson92 · 08-11-2008

I've already ran the cheskdisk. Does memtest86+ check video ram too, if so then I've checked all my different memory. How do I know if it's a system service or driver causing it? And if it is, how do I fix that? Should I try replacing the ntfs.sys it keeps mentioning?

**johngalt** · 08-11-2008

No, memtest86+ does Physical RAM only.

As far as knowing if it is a service or driver, WinPatrol will show you all non Microsoft services installed, and then you can disable those services and see if it helps, and with drivers, you'll most likely have to uninstall one by one to see if any of them is causing it.

As for replacing ntfs.sys - no. Unless you can prove it is infected with a type of malware, don't replace it. You could cause irreparable harm to your system.

jpeterson92 · 08-11-2008

Should I try to check my video card?

**johngalt** · 08-12-2008

Yes, that would be the next logical step.

08-11-2008	#2 (permalink)
dmex Windows Vista™ Ultimate 2,631 posts	Re: Page Fault in Nonpage Area 0x00000050 Hi jpeterson92, Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk. The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. Cause Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). Another common cause is the installation of a faulty system service. Antivirus software can also trigger this error, as can a corrupted NTFS volume. See Microsofts Blue Screen Of Death Database for ways to resolve the error here: Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA Steven
My System Specs

08-11-2008	#3 (permalink)
jpeterson92 Vista Ultimate x64 3 posts	Re: Page Fault in Nonpage Area 0x00000050 I've already ran the cheskdisk. Does memtest86+ check video ram too, if so then I've checked all my different memory. How do I know if it's a system service or driver causing it? And if it is, how do I fix that? Should I try replacing the ntfs.sys it keeps mentioning?
My System Specs

08-11-2008	#4 (permalink)
johngalt Vista Ultimate x64 MAK, OpenSolaris 5, Gentoo 2008.1.... 3,848 posts	Re: Page Fault in Nonpage Area 0x00000050 No, memtest86+ does Physical RAM only. As far as knowing if it is a service or driver, WinPatrol will show you all non Microsoft services installed, and then you can disable those services and see if it helps, and with drivers, you'll most likely have to uninstall one by one to see if any of them is causing it. As for replacing ntfs.sys - no. Unless you can prove it is infected with a type of malware, don't replace it. You could cause irreparable harm to your system.
My System Specs

08-11-2008	#5 (permalink)
jpeterson92 Vista Ultimate x64 3 posts	Re: Page Fault in Nonpage Area 0x00000050 Should I try to check my video card?
My System Specs

08-12-2008	#6 (permalink)
johngalt Vista Ultimate x64 MAK, OpenSolaris 5, Gentoo 2008.1.... 3,848 posts	Re: Page Fault in Nonpage Area 0x00000050 Yes, that would be the next logical step.
My System Specs

Similar Threads
Thread	Forum
Page Fault in Nonpaged Area	Vista performance & maintenance
Vista Ultimate 64 BSOD 0x00000050 PAGED FAULT IN NON PAGED AREA	Vista hardware & devices
Re: Vista Ultimate 64 BSOD 0x00000050 PAGED FAULT IN NON PAGED AREA	Vista General
Blue Screen - Page fault in non page area	Vista performance & maintenance
Page Fault error Stop 0x00000050 and KB941229?	Vista General