ntfs.sys PAGE FAULT IN NONPAGE AREA bluescreen

Status
Not open for further replies.

cpc2004

Posts: 1,994   +0
hdragon689 said:
Dear cpc2004,
I just found this discussion thread today. I have
experiencd the same problem for few months. The
system automatically reboot randomly, few times a day.
Can you also help me check my system? My minidumps
files is uploaded to this place,
http://www.unc.edu/~hlyu/temp/hdragonMinidump.rar
Thank you very much .... :D

hdragon
You attached 7 minidumps. 2 minidumps are corrupted and 2 minidumps are partially corrupted. The minidumps crashed with 0A, BE and C5. They are symptoms of bad RAM. Replace the RAM.
 
Thx a million cpc2004
i'll get on replacing it, if it is the RAM and I don't think you make mistakes :) then you've saved me a lot of trouble.

be seeing you.
 
ok, until yesterday i was allso this problem of : page fault in non paged area

i solve this problem in 3 way (i not shore what way was the reason of succes so thi what i do:

1. i change my keyboard (i plug in new keyboard)/
2. i do disk defragmenter in all my hard disk (this take alot of time i have 400 GB hard disk)
3. i scan my computer with the program error nuker

until now my pc is not shut down to bsod (blue screen) and before i do this thing my pc allways shut down after 2 hours of work , the last time this happen to me was before 26 hours so its mean that its work

but i have allso problem with my ram memory i check its with dos program (i dont rember the name of the program) and its write to me that there 5000 errors and i check this program allso in my scond(pentim4) and third computer(amd 64) and in the both computer the program wirte 0 errores

so if this happen to me again the reason is my ram.

but my solution can help u too/

i hope i help u/
 
Ok , the blue screen is back

I have minidump files if someone know how to read this files please help , I upload now the files , please tell me whats worng with my pc
 

Attachments

  • Minidump.zip
    81.3 KB · Views: 5
cpc2004 said:
You attached 7 minidumps. 2 minidumps are corrupted and 2 minidumps are partially corrupted. The minidumps crashed with 0A, BE and C5. They are symptoms of bad RAM. Replace the RAM.

Thanks a lot for solving my problem. I will replace my ram...
 

cpc2004

Posts: 1,994   +0
Create folder c:\windows
Install Debugging Tools from Microsoft
1) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
2) Locate your latest memory.dmp file- C:\WINDOWS\ Minidump\Mini011005-01.dmp or whatever
3) open a CMD prompt and cd\program files\debugging tools for windows\
4) type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\WINDOWS\ Minidump\Mini011005-01.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
5) You now have a debuglog.txt in c:

Windbg is the full screen on-line debugger and kd is the line mode debugger. You can use windbg to process the minidump. Use the debugger is easy but it is very difficult to interpret the output.
 
BSOD & NTFS.SYS-infinite reboot - STUCK!!!

Hiya,

I've been reading your responses about the BSOD and ntfs.sys files. Hopefully someone can lend a hand with their expertise!

I got the bsod one day out of the blue. Nothing changed. I've reseated ram, same thing. I cannot boot to the drive at all. Infininte reboot cycle. Can't load ghost as it locks. Can't boot hdd as slave as pc reboots. Cannot get to safe mode. Cannot access drive in anyway, shape or form except via ntfsdos but read only. Cannot chkdsk /f...Nothing. I'm stuck and have been banging my head for 3 days now until I came across the posts.

Thanks so much in advance if anyone can help.


dump below-------


Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Administrator\Desktop\RBEAR PC CRASH FILES\MINI08~1.DMP]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Aug 30 01:20:11.843 2005 (GMT-4)
System Uptime: 0 days 0:20:45.428
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {f12ac544, 1, f84b4f4e, 3}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
 
Ntfs.sys Page_fault Bsod Bluescreen Help!

Hiya,

I've been reading your responses about the BSOD and ntfs.sys files. Hopefully someone can lend a hand with their expertise!

I got the bsod one day out of the blue. Nothing changed. I've reseated ram, same thing. I cannot boot to the drive at all. Infininte reboot cycle. Can't load ghost as it locks. Can't boot hdd as slave as pc reboots. Cannot get to safe mode. Cannot access drive in anyway, shape or form except via ntfsdos but read only. Cannot chkdsk /f...Nothing. I'm stuck and have been banging my head for 3 days now until I came across the posts.

Thanks so much in advance if anyone can help.


dump below-------


Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Administrator\Desktop\RBEAR PC CRASH FILES\MINI08~1.DMP]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
********************************************************************** ******
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
********************************************************************** ******
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue Aug 30 01:20:11.843 2005 (GMT-4)
System Uptime: 0 days 0:20:45.428
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...................................................................... ...................................................................... ............................................
Loading unloaded module list
..........
Loading User Symbols
********************************************************************** *********
* *
* Bugcheck Analysis *
* *
********************************************************************** *********

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {f12ac544, 1, f84b4f4e, 3}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image Ntfs.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
********************************************************************** ***
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
 
Hi.
Surprisingly I'm having the same problem as well.
It happened one day, out of the blue, there was a blue screen.
PAGE FAULT IN NONPAGE AREA.

Now sometimes when windows is starting or when i'm uninstalling a program and even when i'm browsing the internet , the blue screen will appear.

I have no idea what is wrong. I've attached the minidumps and I hope the experts here will shed me some light.


Thanks
 
can anyone help me out???

I got errors when I use xp.

it ramdomly restart or I get a blue screen

I have a minidump file can anyone fix this.


please reply..... need to fix this before it becomes worst .......
 

Attachments

  • minidump.zip
    95.8 KB · Views: 5
help!!!!!

Hi, i am new to this site and have just signed up, i have been having a lot of problems with my pc. I will sometimes recieve the Windows stop error screen and it seems like a few system files may be corrupt. One that i noticed last nite was ntfs.sys. I also find that when i run programs a windows error message will appear. I am not sure wot to do?? r these the symptoms of bad ram. Please help drws2kuk :mad:
 

cpc2004

Posts: 1,994   +0
luluSantos said:
Hi.
Surprisingly I'm having the same problem as well.
It happened one day, out of the blue, there was a blue screen.
PAGE FAULT IN NONPAGE AREA.

Now sometimes when windows is starting or when i'm uninstalling a program and even when i'm browsing the internet , the blue screen will appear.

I have no idea what is wrong. I've attached the minidumps and I hope the experts here will shed me some light.


Thanks
Hi,
All of your minidumps crash at nt!RtlInitUnicodeString+1b. I have no idea why your windows crash. Probably it is faulty ram but I am not sure. Maybe some experts have the answer.
 

cpc2004

Posts: 1,994   +0
goneout said:
i got errors when I use xp.

it ramdomly restart or i get a blue screen

i have a minidump file can anyone fix this.


please reply..... need to fix this before it becomes worst .......
Hi goneout,

5 of your minidumps have memory corruption. Probably it is overheat within the CPU or m/b. If your PC is not overheat, it is faulty ram.


AGE_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: e1340c84, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bfdba85c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e1340c84

FAULTING_IP:
nv4_bfdb0000+a85c
bfdba85c ?? ???

MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 00000000 to bfdba85c

TRAP_FRAME: f844d1f4 -- (.trap fffffffff844d1f4)
ErrCode = 00000000
eax=e1ae54b8 ebx=00001500 ecx=0000005e edx=0000000e esi=e1340c70 edi=00000240
eip=bfdba85c esp=f844d268 ebp=f844d274 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
nv4_bfdb0000+0xa85c:
bfdba85c ?? ???
Resetting default scope

STACK_TEXT:
f844d264 00000000 00000180 e1ae5010 f844d290 nv4_bfdb0000+0xa85c

CHKIMG_EXTENSION: !chkimg -lo 50 -d !hal
806b5fa9-806b5faa 2 bytes - hal!KeGetCurrentIrql+a85
[ 00 00:40 38 ]
806b5fad-806b5fae 2 bytes - hal!KeGetCurrentIrql+a89 (+0x04)
[ 00 00:02 10 ]
806b5fb0-806b5fb6 7 bytes - hal!KeGetCurrentIrql+a8c (+0x03)
[ 00 00 00 00 00 00 00:62 50 70 73 df ff 02 ]
806b5fb8-806b5fb9 2 bytes - hal!KeGetCurrentIrql+a94 (+0x08)
[ 00 00:d4 03 ]
806b5fbb-806b5fbc 2 bytes - hal!KeGetCurrentIrql+a97 (+0x03)
[ 00 00:20 79 ]
806b5fbf-806b5fc0 2 bytes - hal!KeGetCurrentIrql+a9b (+0x04)
[ 00 00:30 79 ]
806b5fc3-806b5fc4 2 bytes - hal!KeGetCurrentIrql+a9f (+0x04)
[ 00 00:40 38 ]
806b5fc6-806b5fc8 3 bytes - hal!KeGetCurrentIrql+aa2 (+0x03)
[ 00 00 00:08 06 68 ]
806b5fca-806b5fd0 7 bytes - hal!KeGetCurrentIrql+aa6 (+0x04)
[ 00 00 00 00 00 00 00:62 50 f0 89 df ff 40 ]
806b5fd2-806b5fd7 6 bytes - hal!KeGetCurrentIrql+aae (+0x08)
[ 00 00 00 00 00 00:c4 03 40 10 4d 80 ]
806b5fdb-806b5fdf 5 bytes - hal!KeGetCurrentIrql+ab7 (+0x09)
[ 00 00 00 00 00:10 eb a8 01 01 ]
806b5fe2-806b5fe7 6 bytes - hal!KeGetCurrentIrql+abe (+0x07)
[ 00 00 00 00 00 00:a7 73 04 80 e2 1f ]
806b5feb - hal!KeGetCurrentIrql+ac7 (+0x09)
[ 00:f0 ]
806b5fee-806b5ffa 13 bytes - hal!KeGetCurrentIrql+aca (+0x03)
[ 00 00 00 00 00 00 00 00:30 cd fa 0f 10 73 2c 99 ]
806b5ffc-806b5ffe 3 bytes - hal!KeGetCurrentIrql+ad8 (+0x0e)
[ 00 00 00:02 08 12 ]
63 errors : !hal (806b5fa9-806b5ffe)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .trap fffffffff844d1f4 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
 

boaby

Posts: 12   +0
Hey cpc2004, could you *please* check out my thread here. I spent half of my student-loan building this pc and I fear I'm going to have to spend more if I can't diagnose this problem. Thanks in advance for any help.
 

cpc2004

Posts: 1,994   +0
Hi Boaby,

Maybe it is faulty ram but I am not very sure. Do you have any minidumps not crash with bugcheck code '50'? If yes, attach the minidump here.
 

cpc2004

Posts: 1,994   +0
Metamorphosis said:
Thx a million cpc2004
i'll get on replacing it, if it is the RAM and I don't think you make mistakes :) then you've saved me a lot of trouble.

be seeing you.
Do you have any update of your problem?
 

boaby

Posts: 12   +0
cpc2004 said:
Hi Boaby,

Maybe it is faulty ram but I am not very sure. Do you have any minidumps not crash with bugcheck code '50'? If yes, attach the minidump here.

hey cpc, thanks for looking into it.

I've attached a minidump obtained from an 8E error.


As i mentioned i get the blue screen when zonealarm tries to start up (specifically when it starts the TrueVector Client). But this was zonealarm v4.5. I wanted this older version as i find the later versions quite bloated. I've been using v4.5 for some time on my other pc which btw is running the exact same OS as installed on this new system.

However i decided to see if i got the same problem with v6. So I've installed v6 on the new system and been using it for a day or so and have had no problems with it so far.......confused.
 

boaby

Posts: 12   +0
hey man, any joy with the above dump?

There's definately some specific problem why v4.5 won't work on this machine when it works on the other, but I still can't determine whether its a hardware issue or not.

I've tried both the ram sticks in different ways and i get the same error with both and im thinking its unlikely that i could have TWO faulty sticks of ram so im suspecting the mobo. Wondering whether to just RMA it (?)

:confused:
 

cpc2004

Posts: 1,994   +0
drws2kuk said:
I am not sure whether this is the stuff to be anaylsed but would appreciate it if someone could help me out
Hi drw2kuk,

I've investigate your minidumps and it is faulty ram.

Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Make sure that the ram is compatible to the motherboard
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
 
Ntfs.sys problems

I am having problems with this also. My system was automatically restarting after 15-20 minutes of idling. I changed the option in the control panal to disable automatic reboots on crashes, and I could then see on the blue screen that the problem is with Ntfs.sys. I have a 256mb memory stick and a 128mb memory stick. I haven't changed anything in my PC in a looooong time and this just started out of the blue. I took the memory sticks out and cleaned everything really good, but it did not help.

I have attached some minidumps.

Thanks in advance for any help you can offer!!

Thanks,

Mikey
 
Status
Not open for further replies.