ntfs.sys PAGE FAULT IN NONPAGE AREA bluescreen

Yep, It was the USB drive, I reformatted it under linux and it was then fine.

cpc,
I know you are probably tired of looking at minidumps but I am still trying to determine what my problem. I have done a fresh install and have tried different ram. Tonight I received an IRQL BSOD. I am attaching the minidump. Nothing shows up in the event logger. If you don't mind, please take a look at it and see what you think. Thanks.

Hi Razorback,

Refer my previous post, base upon my record, 50% is CPU% and 33.3% is RAM. You should replace CPU. However overheat may also cause system crash at IRQL x'1c'. Check the temperature of the CPU. BTW, do you use AMD CPU?

cpc2004

Hey cpc2004,
I am using a 3.2c P4. Had it for about a year. Temps in my bios show around 95 F which should be fine. I guess my last IRQL showed the same info. Besides the BSOD's which have been from PFN_LIST to PAGE_FAULT to KERNEL_APC_PENDING_DURING_EXIT, on boot I get the couldn't find or corrupt SYSTEM file black screen error. I can reset the mobo and reboot and get into the desktop after that. So you think it is the cpu? Bummer.

This is hardware poblem. What do you mean you have to try all different ram? I guess you mean you reseat the RAM and the BSOD still occurs

I borrowed another set of ram - 512 MB of PC4000 to see if my new ram was the problem. Just to recap, I replaced my ram a couple of months back. I went from 512 MB of OCZ PC4000 to 1 GB of OCZ PC3700. I wanted to rule out the new ram so I used the ram that borrowed from work.

How often does your windows crash? Open the computer case. If your windows does not crash, it is overheat.

My problem

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 ....

hdragon

dear cpc2004

i have also been having trouble with the page fault and ntfs.sys error.
problem is that i have allot of tests at my college, I have to learn JAVA and C++ so I don't really have the time to learn how to debug the minidump files, i know you got allot of work from everyone else here, but my computer is very unstable, and it's not helping me study well, so if you could please help me out, it would be greatly appreciated, but like I said, if it is too much work, no offense taken.

Hi Metamorphosis,

Faulty RAM is the culprit. One minidump crashed at IRQL x'1c' which is clock level interrupt. It crashes only if hardware error. Bugcheck C5 is the symptom of bad ram.

BugCheck A, {a8f5ab1c, 1c, 1, 804f7826}
BugCheck C5, {80a6d5c8, 2, 0, 805395de}

As your hardware problem does not occur very frequently. Reseat the memory stick to another memory or downclock the RAM may resolve the problem.

If it still crashes, you have to diagnostic which memory stick is faulty.

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

Hi Swat,

Faulty RAM is the culprit.

thanks man u help me to understand what the problem in my computer.

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

cpc 2004 how u know to read this dump files ?
and with what program u use to read this files?

and again thanks a lot for your help

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 ***
*** ***