Page Fault in Non Paged Area

[Twobit_za]

Thanks. So no hardware errors then in the dmps?
I removed Zone-Alarm and put on the Sygate Personal Firewall.
And updated AVG.

 

[dicksyo]

This is insane.......y not buy another one?... :unch:

 

[IronDuke]

Alternatives for a firewall see earlier post
https://www.techspot.com/vb/topic26830.html

 

[Vullcan]

I'm getting page faults too, right after a reformat (well, ive reinstalled some stuff).

Please help me out here, thanks.

http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-01.dmp
http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-02.dmp
http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-03.dmp

from event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xbe80f1d4, 0x00000008, 0xbe80f1d4, 0x00000002). A dump was saved in: C:\WINDOWS\Minidump\Mini062505-03.dmp.

 

[IronDuke]

Please read these two posts by RealBlackStuff
https://www.techspot.com/vb/topic17297.html
and
https://www.techspot.com/vb/topic19133.html

After doing that you may start a fresh thread.

 

[js123]

Can anyone look at my minidumps? I am getting the page fault BSOD. Memtest86 didn't find anything.

 

[omega]

Can u plz check my mini dump it always boots me and i dont know how to get rid of it

 

[cpc2004]

I'm getting page faults too, right after a reformat (well, ive reinstalled some stuff).

Please help me out here, thanks.

http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-01.dmp
http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-02.dmp
http://www.cadaveria.vullcan.net/dont_delete_contents/Mini062505-03.dmp

from event viewer:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xbe80f1d4, 0x00000008, 0xbe80f1d4, 0x00000002). A dump was saved in: C:\WINDOWS\Minidump\Mini062505-03.dmp.

I've studied your dump and the only thing I find the failing routine is at nt!KeBugCheckEx+0x1b. Most likely it is faulty ram. Reseat the memory may resolve your problem. Attach more dumps if your PC still gets BSOD.

 

[cpc2004]

Can anyone look at my minidumps? I am getting the page fault BSOD. Memtest86 didn't find anything.

The analysis report of your dump shows that it is RAM or CPU L2 cache memory problem. Some faulty RAM can pass memtest86. Reseat the memory to another memory slot.

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

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

READ_ADDRESS: e606da10
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from 80523f44 to 8053331e

STACK_TEXT:
f4f42bd8 80523f44 00000050 e606da10 00000000 nt!KeBugCheckEx+0x1b
f4f42c24 80522142 00000000 e606da10 00000000 nt!MmAccessFault+0x6f5
f4f42c50 804f1285 ff5f0288 001df558 f4f42c88 nt!MiMakeSystemAddressValidPfnWs+0x5d
f4f42c60 8056c65b e606da10 ff39c3a8 045adddc nt!MiCaptureSystemPte+0x1c
f4f42c88 8056c4ca 00000000 ff5f0288 ff39c3a8 nt!MiQueryAddressState+0x1aa
f4f42d44 804de7ec ffffffff 77d48830 00000000 nt!NtQueryVirtualMemory+0x477
f4f42d44 7c90eb94 ffffffff 77d48830 00000000 nt!KiFastCallEntry+0xf8

 

[cpc2004]

Can u plz check my mini dump it always boots me and i dont know how to get rid of it

No attachment ??

 

[cpc2004]

Hi,

Thanks for the quick response. How do you know? Is there something in the minidump file that points to it? Could you possibly post what the minidump deciphers to?

I only ask because the PC had been running fine with this driver for about a year....and now all of a sudden, it is unstable.

Thanks so much!

Patti

Patti,

I mixed up your problem with another cases. Your PC does not install nVidia Display card and your minidump has a lot of corruption. I can't determine the root cause. If you want to purse the problem. Attach the latest minidump here.

 

[omega]

here is the files



ok i have a problem and i cant post my files do u have msn or something i can send u the files?

 

[IronDuke]

Try again Omega. There's nothing attached.

 

[IronDuke]

You won't be able to attach until the 3rd of even 4th post.

 

[omega]

oh i see the problem it says invailed file

 

[IronDuke]

What type of file are you trying to send?

 

[omega]

here are the files


another thing to say about the bug check is it only occurs when i am playing games such as MU online im not sure the reason though it just brings the BSOD (blue screen of death) plz help me solve this error

 

[omega]

plz check the post as soon as u can

 

[IronDuke]

I'm sure he will. Its Sunday, maybe has gone out for the day.

 

[cpc2004]

plz check the post as soon as u can

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.

 

[wscott44]

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

 

[theberle]

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

 

[wscott44]

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

 

[cpc2004]

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

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

 

[cpc2004]

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.

Hi Omega,

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