Page Fault in Non Paged Area

PAGE_FAULT_IN_NONPAGED_AREA - faulty RAM

Folks: One of my Windows 2000 PCs has been unstable for a while, crashing with BSOD and PAGE_FAULT... When I read about the possibility that RAM could be faulty, I remembered a tool I had used before. At http://www.simmtester.com/ I got the latest docmemory simmtester, created the boot floppy, and tested the PC. On the first pass, it identified an error at address 116M. I took out the suspect module, tested the rest, they were fine. Ordered new memory, installed, tested, and the system is stable now! What a relief.

Wayne Scott

cpc2004, thanks for all your help on here.

I'm having regular BSOD's for a few months now.

I ran memtest86+ last night, and found semi-regular errors at one address.

From the MSDN articles, it looks like my problems are related to "A memory access violation occurred."

Can you confirm this from my 1001's and minidumps attached?

If it is a RAM problem, is there any way to bypass that address, or is my only option to buy new RAM?

I put the 5 1001's into a txt file, and the minidumps are zipped.

Let me know if you want any more event info, or my system configuration.

-Tom

Howdy: Glad I could help; however, I am not familiar with minidumps and other bit-level details. All I know is that DocMemory simmtester identified the problem for me.

As for bypassing memory - in my case, the system is an old Compaq with EDO SIMMs, installed in 4 pairs. So I could figure the 2nd pair is where 116M was and remove them. Then I operated with 192MB while ordering new RAM.

As long as your system has more than one module, you can remove the suspected faulty one (unless they're all bad), and decide how to attack the problem.

My personal preference on memory is www.crucial.com ; however, for this old dog, I used www.18004memory.com and got a pair of SIMMs for $22. Hope this helps,
Wayne Scott

Your XP crashes at different modules may be caused by hardware or software error. In order to make sure that it is hardware problem. Upgrade the software which cause BSOD at your windows.

Software
1. S3 display card driver
2. Upgrade Norton AV
3. Upgrade deamon tool

Hardware
1. Reseat the memory to another slot
2. If you have two memory stick, take out a memory stick and trouble shoot which memory stick is faulty.

Debug report of your minidumps
Mini071705-01.dmp 7E (c0000005, 804eda4b, f7c3ca28, f7c3c724) nt!ExInsertTailNBQueue+35
Mini071205-03.dmp 8E (c0000005, bf837815, f1be4b94, 00000000) win32k!HMUnlockObjectInternal+1c
Mini071405-02.dmp 8E (c0000005, 80557692, f1a42954, 00000000) nt!PaletteBmp+52
Mini071205-02.dmp 50 (f0badb8f, 00000001, 80567682, 00000000) nt!CmpParseKey+10d
Mini071405-01.dmp 50 (f0d3e337, 00000001, 80567682, 00000003) nt!CmpParseKey+10d
Mini071705-02.dmp 50 (f41d0bab, 00000001, 80567682, 00000003) nt!CmpParseKey+10d

s3gnb s3gnb.dll Tue Mar 02 14:02:24 2004 (40442370) <-- s3 display card driver
SAVRT SAVRT.SYS Fri Sep 19 04:22:55 2003 (3F6A141F)
NavEx15 NavEx15.Sys Sat Jul 24 01:50:12 2004 (41014FD4)
SYMEVENT SYMEVENT.SYS Thu Aug 07 09:32:39 2003 (3F31AC37) <-- Norton AV
f77c1000 f77e7480 d346bus d346bus.sys Sat Mar 13 04:41:28 2004 (40522078) <-- daemon tools

Hi Omega,

Do you any update of your problem? Your feedback will help us to resolve similar problem.

Do you have any update of your problem? Your feedback will help us to resolve similar problem.

CPC2004, I updated the S3 display driver, uninstalled Daemon Tools (which I don't use anymore) and Norton (for now).

I didn't touch the hardware issues for now, since I would prefer it be software.

However, I'm still crashing. See attached for three more minidumps and 1001's. If these are new software issues, I'll start playing with the hardware fixes, as I doubt all my software is bad.

[Edit: I've added three more attachments for 6 more dumps (split into two files to get it under 100k) and 6 1001's]

Thanks,

-Tom

Your Winodws may be infected by virus or faulty ram. Attach the following files here.
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp

Reseat memory stick to another memory slot. Let me know if you still need any help.

my dr watson log is 14 megs, so I just took the last failure, and put it in a new file, since file size is limited to 100k.

I also had to change the extension to .txt to get them upladed.

See attached for the log and user.dmp

I still haven't reseated the memory.

I need at least the last 10 DrWatson log in order to confirm whether it is hardware error or not. Can you zip the last 10 DrWatson log and attach the zip files here.

i formated my computer and it still does the bug check i will post my files here again plz help me
and sorry i couldnt anwser ur past post i lost this site due to format

Here's two zipped txt files I pulled out of the DrWatson log. Each one has 8 application exceptions, for a total of 16.

I don't want to jinx it by mentioning it, but I moved my memory to my other slot, and haven't had a BSOD for about 24 hours (although I have had some DrWatson events).

I ran memtest 86+ overnight, and only had one error.

Thanks again for the help.

can u plz check the files i attached
the format i did didnt affect it at all

The RAM is faulty. From DrWaston log, I find four modules crashed at various instruction address and all fail with "access violation"

i reinstaled windows xp pro and i still have the bug checks i used all the drivers i used before i didnt install anything execpt one game to try to check if it does the bug check and i sadly found out it does

if u can take a look in the file that would mean alot to me

Your problem is related to bad ram. Reseat the memory to another memory slot and downclock the ram. If it still does not work, replace the ram.

are u sure its just the Ram and not anything else?

Hi Omega,

The following are my suggestion on 3th July. Which one have you implemented?

One minidump crashed at nVdia Display card. Two minidumps crashes at smwdm.sys (ie sound card driver) and one minidump at avg7core.sys.

Your nVidia display card is at 2003. Install nVidia Display Card Driver 61.77 cos it is stable version http://www.nvidia.com/object/winxp_2k_61.77.html
Your sound card driver is also at 2003. Upgrade it to latest version. Your avg7core.sys is at 23rd May 2005. Download the latest version of AVG or de-install AVG.


From your latest dump, you are using install nVidia Display Card 61.77 and you haven't updated the sound card driver. You de-install AVG but you install Norton AV and the version that you install has problem. You can refer to the following case.
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21485954.html

You are supposed to implement my suggestion before you ask for further help. I have to use a lot of time to find out the root cause of your problem at my free time. Resolve the above problem. If your PC still gets BSOD, replace the ram.

I am not Jesus. Even I am sure the root cause and it does not mean that my answer is always correct. You have to take your risk whether you accept my suggestion or not.

thank u for taking ur time to help me.
about norton even my friend is using this version and he doesnt have any problems with it and its the most up to date one
and i have to pay money to see the soltution in the http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21485954.html
and i didnt de install avg i did format and installed norton
and yes i take ur advice since u know more about this bug then me

ok i have downloaded the latest drivers for SoundMAX and when i go to install it i get:

"Driver not found! Reboot your system,and run the setup again."