Page Fault in Non Paged Area

Some more info (power font)

BTW, I have changed the power font (power supply), iniside the computer, just to see if this change could help. No, no help. Reboots... more reboots...
Tks for all, in advance.

2 minidumps have memory corruption 1 minidump has invalid call. They are symptoms of faulty motherborad or CPU. According to my experience, 80% is faulty M/B and 20% is faulty CPU.

Mini061005-03.dmp
BugCheck 10000050, {bf7fc94c, 0, bf7fc94c, 0}
Probably caused by : hardware
*** Possible invalid call from bf81c595 ( win32k!EngLpkInstalled+0x2d16 )
*** Expected target bf800d5a ( win32k+0xd5a )

Mini061405-01.dmp
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : memory_corruption
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
31 errors : !nt (804dd907-804dd9ff)
804dd900 db 89 7d 2c 0f 23 fb *00 8b 3d 20 00 00 00 8b *c9 ..},.#...= .....
804dd910 f8 02 00 00 8b 8f fc *00 00 00 0f 23 c3 0f 23 *0f ...........#..#.
804dd920 8b 9f 00 03 00 00 8b *24 04 03 00 00 0f 23 d3 *23 .......$.....#.#
804dd930 23 d9 8b 9f 08 03 00 00 8b 8f 0c 03 00 00 0f *04 #...............
804dd940 f3 0f 23 f9 eb 78 8b *0d 8b 85 84 00 00 00 8b *45 ..#..x.........E
804dd950 88 00 00 00 8b 4d 7c *1d 95 80 00 00 00 66 89 *04 .....M|......f..
804dd960 50 66 89 5d 30 66 89 *41 34 66 89 55 38 eb 41 *00 Pf.]0f.A4f.U8.A.
804dd970 66 c7 44 24 02 00 00 *00 53 56 57 0f a0 bb 30 *9d f.D$....SVW...0.
804dd980 00 00 66 8e e3 64 8b *66 00 00 00 00 53 83 ec *8e ..f..d.f....S...
804dd990 50 51 52 1e 06 0f a8 *c4 b8 23 00 83 ec 30 66 *98 PQR......#...0f.
804dd9a0 d8 66 8e c0 8b ec f7 *1d 24 70 00 00 02 00 75 *3d .f......$p....u=
804dd9b0 fc f6 05 50 f0 df ff *24 0f 85 0a ff ff ff 83 *00 ...P...$........
804dd9c0 54 f0 df ff 00 0f 85 *00 01 00 00 8b c4 2b 05 *a1 T............+..
804dd9d0 f0 df ff 05 8c 00 00 *01 74 15 83 f8 90 72 10 *0f ........t....r..
804dd9e0 18 f0 df ff 0b c0 7e *f0 e8 3d dd ff ff 8d 09 *fb ......~..=......
804dd9f0 20 d7 80 3d 91 51 54 *00 00 0f 85 92 fe ff ff *00 ..=.QT.........

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE


Mini061005-01.dmp
BugCheck 1000008E, {c000001d, 804dd970, f4a57d54, 0}
Probably caused by : memory_corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
59 errors : !nt (804dd900-804dd97b)
804dd900 *d8 *02 *00 *00 0f 23 fb 64 *00 *00 *0f *23 00 00 8b 9f .....#.d...#....
804dd910 *89 *9b 00 *03 8b 8f fc 02 *04 *03 *00 *00 c3 0f 23 c9 ..............#.
804dd920 *23 *d9 *ab *9f 00 00 8b 8f *8b *8f *0c *03 0f 23 d3 0f #............#..
804dd930 *54 *b0 *00 *83 08 03 00 00 *01 *00 *00 *8b 00 00 0f 23 T..............#
804dd940 *88 *00 *00 *00 eb 78 8b ff *95 *80 *00 00 00 00 8b 9d .....x..........
804dd950 *00 00 *66 *8e 8b 4d 7c 8b *00 *00 00 00 00 66 89 45 ..f..M|......f.E
804dd960 *66 *c7 *44 *24 30 66 89 4d *53 *56 *57 *0f 38 eb 41 90 f.D$0f.MSVW.8.A.
804dd970 *f0 *0b *01 *f9 02 00 00 55 *8b *85 *84 *00 a0 bb 30 00 .......U......0.

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE

hello!
i'm new in forum..

I have a problem, with my PC with XP SP2
randomly BSOD with following words:

PFN_LIST_CORRUPTED
0x0000004E (0x0000008F, 0x0003DBFF, 0x0003DBFE, 0x00000000)

BSOD is appear, only when i enabling the Cool and Quiet A64 function in the BIOS.
i have the latest BIOS for my motherboard (1.7)
running the memtest86 same time, and every result 100% pass the tests.
complete (default) test twice, test No. 5 about a hour and Test No. 9 three times..

sorry my bad english..

the dump files attached.

- Debilon -

Hi Debelion,

This is memory corruption and I believe that it is faulty RAM or faulty cache memory of the CPU. It is no need to run the memtest as memtest cannot report the whether it is RAM or cache memory problem. Reseat the memory to new memory slot. If the problem still exist, take out a memory stick. If the problem still occurs, it is cache memory of the CPU.

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: 00035ff7, new page
Arg3: 00035ff6, old page
Arg4: 00000000, 0

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

PFN_PAGE_SINGLE_BIT_ERROR: Bugcheck args 2 and 3 differ by a bit, its hardware error.

MEMORY_CORRUPTOR: ONE_BIT
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT

Hello cpc2004!

thanks the quick answer!

this is a strange thing to me, because hangup my PC, just when C'n'Q enabled. any other state is work correctly and stable through hours and hours..

hm..weak PSU don't caused this error?
because my PSU is a Chieftec 300W unit.
the +12 V rail only 13A..

but i have a new dump file, BSOD with MEMORY_MANAGEMENT error
0x0000001A (0x00041785, 0xC0E00000, 0x000307B6, 0x00000000)

- Debilon -

Your new minidump also have working set list is corrupt which is another evidence of memory corruption.


MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041785, The working set list is corrupt.
Arg2: c0e00000
Arg3: 000307b6
Arg4: 00000000

Some questions (in reply to cpc2004)

Hello, cpc2004, thanks for your help.

Your new reply told me that:"2 minidumps have memory corruption 1 minidump has invalid call. They are symptoms of faulty motherborad or CPU. According to my experience, 80% is faulty M/B and 20% is faulty CPU."

Now, I would like to change some info: yesterday, I have removed all the memory sticks (I had 512MB+256MB+256MB). After that, I put back just one of them: 256 MB. From that time until now, I had no more reboots. 24 hours have gone ok.
Just to do some "hardware stress", I have made a fresh win xp install, some softwares, I have ran some antivirus scan (just to access the hd´s),
I have copied several archives, from hd to hd, using some other softwares... and it seems to be ok. No unexpected reboots yet. Until now...

Then, I ask 3 questions: 1) could be all the problems related to some faulty ram? Even "memory corruption" and "invalid call", as you have pointed?
2) If yes, may my MB and CPU be ok?
3) If yes, I think (and I hope) the problems could be solved just removing all memories and buying new ram.Tks for your kindness and attention.

Tks for your kindness.

thanks!
i now probe the memory modules swap and use other dimm slots..
now dimm1 and dimm3 slots are memory sticks.

i probe the memory sticks in my friend PC, and absolute error free.. or :bounce: i don't decide this..

now i have this dump file, it was after win32k.sys error..
0x0000008E (0xC0000005, 0xBF801872, 0xAA86ACBC, 0X00000000)

can you see this last dump file..and my drwatson's log?

IMPORTANT! my DrWatson log language is hungarian..maybe not wrong..

My DrWatson log file

Help - Page fault in non paged area

Hi,

I just joined this forum in the hopes that someone can give me a clue what's going on. A little background....

The PC only seems to crash when stressed. I have 4 internal SCSI disks, they are mirrored (via Windows 2000 disk management). Every time the PC crashes, the disks must re-sync which goes on for about an hour. Sometimes, it can't get through that even though I run nothing while doing it. In other times, it happens while doing something graphic like running Photoshop.

It tanks with one of two errors:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xb111b000, 0x00000001, 0x80463693, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000002c, 0x00000002, 0x00000000, 0x80444148). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

I am suspecting memory here as this machine started acting kinda similar a year ago...I replaced the memory and all was well...but realize this could be caused by any number of problems.

I've attached a minidump... if anyone could look at it and tell me what it says, I'd be most appreciative!

Patti

Your nVidia Display card driver is incompatible with SP2. Install http://www.nvidia.com/object/winxp_2k_61.77.html

How do you know?

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

Pattir7,

You only attached a minidump here and the nVidia Display card driver is the known issue that I find from your dump. Refer this webpage starting at page 3 to page 8 and there have a lot of problem relating to nVidia Display card driver. If you can provide more information, I will have more finding. Don't expect one 90K minidump have the solution. Usually you have to provide 6 to 8 minidumps for trouble shooting.

cpc2004.

Error while formatting

OK i am getting really wierd errors.

When i try to format i either get the "page fault in non paged area" error or a "Irq not less or equal to" error.

The computer was working fine before i formatted it tho i did notice on anonamly that when i went to back up some data by putting the HDD in another computer i could not access "my documents" folder in one of the user accounts.

ANY help is greatly appreciated.

I've been having restart problems for awhile. Before, I just repaired the installation of windows and everything was fine. Now, I'm getting STOP error 000...50. It's a PAGE_FAULT_IN_NON_PAGED_AREA, being caused by a missing or corrupted ntfs.sys. I bought new RAM and installed it, no dice. I try to run the recovery console, but as soon as the console starts, I bluescreen to the STOP 000...50. I can't load windows, period, and I can't even reinstall or repair the installation. Is my computer being so overworked at startup that it shuts down like this? Is my power supply insufficient? Is my harddrive toast? I honestly have no idea what to do next. Any help would be greatly appreciated.

Hello, cpc 2004

Hello, I have posted this message http://www.techspot.com/vb/post160130-267.html, after your message below and I would like to know your opinion about the problem.

Thanks for all.

Gee, but it is hot today. We're having a bit of a heat wave at the moment and it is playing hell with my crystal ball. So ish maybe you'd like to help out and fill in some details in your profile. Cheers.

Sorry about that. Info updated as best as I can from this location. If you need something else, let me know, I'll do my best to dig it up.

Another minidump

Hi again,

I upgraded the video driver as was suggested. I thought I was 'outta the woods' but today, it crashed again (numerous times actually)..only one made it to the event log because all the other crashes occured before even booting into windows. I could not even get the thing into safe mode...

I took it apart and blew out all the dust (yuck!) and disconnected my mirrored drives so windows wouldn't try to re-sync them. Most crashes seem to occur while it is trying to resync and if it gets past that, it's usually good for a while. Even though the crashes occur during disk sync's, I don't think it's a disk problem because doing a disk sync is very memory and cpu intensive as well...and usually when the first crash occurs, I'm not even using the disk. The last time it happened, I only had a browser open.

I'm just not sure where to begin looking for the problem here... please, please help if you can....

Here is the latest error message and minidump...

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\MEMORY.DMP.

You want a firm answer. I am not a hardware engineer so I cannot answer your question. Hardware engineers have hardware diagnostic tools to test the RAM. If your RAM is still under warrenty, send back the ram to the manufacturer for hardware diagnostic.

The analysis reports of the your minidump confirms it is memory corruption. Memory corruption can be caused by hardware or software. But invalid CPU call is caused by faulty hardware as one of my resolved case the problem owner confirmed that it was faulty M/B. Up till now no one confirms me that invalid CPU call is caused by faulty CPU even it seems that it is related to CPU.

However I can't confirm my finding is 100% correct. You had better forward to your problem to hardware forum or post your problem to microsoft. The fresh windows install resolves a lot of software driver issues, but it cannot resolve hardware problem. If your PC still get BSOD, you will be convince that it is hardware problem. If no more BSOD, put back all of your memory sticks. If no more BSOD, your problem is resolved. If you still gets BSOD and it implies that the two of your memory stick is bad

The following comment is my assumption and you have to take your own risk.

Maybe you have double hardware failure. Faulty ram and M/B. . If the failure rate of hardware is much higher than motherboard, your PC have a lot of memory corruption or access violation. There has no good memest diagostic tool to distinguish the problem is related to RAM or cache memory at CPU.

I had a resolved case the problem is definitely related to faulty CPU. After the CPU is replaced, the BSOD is reduced from daily to biweekly. Finally replace the ram and then BSOD is disppeared

For your case I think the frequnecy of m/b fault is much lower than RAM. As you have three memory stick, are you sure that they are at the same speed. Downclock the ram. Maybe it can resolve your problem.

now, i hope my problem is solved..
the BSOD's caused by ZoneAlarm..i disabled it, and now seems everything OK 2 days ago..