Page Fault in Non Paged Area

Status
Not open for further replies.
Dump Files

These are some random dumps I've had lately and such.
ALSO. I went into the place i got my mobo, and they said there's nothing wrong with my board! brilliant, i thought, although i dont really trust them because they're stupid and they proably dont know jack. The guy didnt run any memory tests. System 'ran' with my CPU and another Celeron CPU. They gave me the same stick of ram, but the system is crashing still. Is it my CPU, or are they just inept? Pentium 3.0 HT 512k cache. cheers! (p.s. most crashes occur in NFSU2, Rome Total War)
 
To Techiseen,

It fails at ati display dirver and I believed that it is the software error ATI driver and not hardware error. You are using the latest ATI display driver which maybe unstable. Maybe it is incompatible with your W2k3.

Suggestion
1. Install minus one version of ATI display card driver
2. Your W2K3 is one year, download the latest patch from microsoft.

FAULTING_IP:
ati3duag+e150a
bfb1e50a 837b0403 cmp dword ptr [ebx+0x4],0x3
 
thanks cpc, but i dont know...

i had experienced the same crashes in XP as well, with all sorts of graphics drivers. What version would you reccomend (im switching to 4.11 right now i think i had 4.12 before) i hope this works. cheers!

UPDATED:

rolling back the graphics drivers to 4.11 did nothing to stop the crashes. it still crashes frequently with NFSU2. I will try later rolling back to 4.9

cheers

cpc2004 said:
To Tchiseen,

It fails at ati display dirver and I believed that it is the software error ATI driver and not hardware error. You are using the latest ATI display driver which maybe unstable. Maybe it is incompatible with your W2k3.

Suggestion
1. Install minus one version of ATI display card driver
2. Your W2K3 is one year, download the latest patch from microsoft.

FAULTING_IP:
ati3duag+e150a
bfb1e50a 837b0403 cmp dword ptr [ebx+0x4],0x3
 
Also continue to dump

Hello,
I have problem like are discussed here.
I read all and not find my identic problem. How someone can help.
In attach I put dump file. Last weeks they are "regulary" but can happens immediate after startup (first time in day) or after few hours and not depend what program are open.
When look Even viewer I see also that every minute I receive this error:
\Device\ACPIEC: The embedded controller (EC) hardware returned data when none was requested. This may indicate that the BIOS is incorectly trying to access the EC without syncronizing with the OS. The data is being ignored.

I don't know if this is connect to dump file or not.

Hope someone can help to resolve this
 
Hi Kigor,

Your minidump is inaccesible by windbg. Usually it is a hardware problem at the motherboard or CPU and cause the minidump is inaccessible. Post system event 1001 or attach another minidump here.
 
Here is last two dump file. I just rename dmp to txt, like see before. Hope now you can access and see it.

In Event viewer I receive this error:

1003

Error code 1000007e, parameter1 c0000005, parameter2 f93c9485, parameter3 fbf82b9c, parameter4 fbf8289c.

And like write before
\Device\ACPIEC: The embedded controller (EC) hardware returned data when none was requested. This may indicate that the BIOS is incorectly trying to access the EC without syncronizing with the OS. The data is being ignored.
 
Hi!

It's me again, I encountered two BSOD in a row just now, one while booting and the other after XP had just been booted (I didn't do anything with XP yet)

Could you please have a look at those new dumps?

0x1000008e (0xc0000005, 0x805f5421, 0xf6e91c50, 0x00000000). Ein volles Abbild wurde gespeichert in: C:\WINDOWS\Minidump\Mini020405-02.dmp.

Thanks a lot!
 
Hi Yarden,

As you've installed nVidia Display Card Driver 61.77, we can eliminate the problem is not related to display card driver. From the minidump, the crash is caused by the instruction is mis-aligned. It is a hardware error at the motherboard or CPU and shift the instruction one byte.

FOLLOWUP_IP:
nt!CmpRaiseSelfHealWarningForSystemHives+3d
805f5421 1881fe900000 sbb [ecx+0x90fe],al

The valid instruction should be look like this
805f541f 83c618 add esi,0x18
805f5422 81fe90000000 cmp esi,0x90

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!CmpRaiseSelfHealWarningForSystemHives+3d
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .trap fffffffff6e91c50 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED


nt!CmpRaiseSelfHealWarningForSystemHives+0x2c:
805f5410 50 push eax
805f5411 e8fe36f2ff call nt!RtlInitUnicodeString (80518b14)
805f5416 8d45f8 lea eax,[ebp-0x8]
805f5419 50 push eax
805f541a e843ffffff call nt!CmpRaiseSelfHealWarning (805f5362)
805f541f 83c618 add esi,0x18
805f5422 81fe90000000 cmp esi,0x90
805f5428 72c2 jb nt!CmpRaiseSelfHealWarningForSystemHives+0x8 (805f53ec)
805f542a 5e pop esi
 
Hm, I just got a 0x24 error (ntfs.sys)...
The strange thing is: with all those errors I get, I just reboot and it most of the time the system is stable then. Mostly the blue screens come up while booting XP not when it's up and running.
Does anyone have a clue what it yould be (the hdd even - but shouldn't the error persist then?) - or the RAM (which I thoroughly tested with memtest86+ and which is brandnew and not cheap) - or my psu (350watts) - or my soundcard (Creative SBLive Value)?

My system is : Athlon Sempron 2600+, 512MB RAM, MSI Geforce FX 5200 128MB,...not much more, network card, DVD-ROM.
The power supplied should be enough, but it could be instabilities of the current...?
 
Similar Problem

I've had this problem for a while now--it was bad in the beginning, started to happen here and there after warranty service, and now seems to happen once or twice daily in the last month.

What my computer used to do was flash the BSOD very quickly and then restart. When this first happened (almost two years ago now), it became a very big problem because I couldn't run the machine for more than 5-10 minutes without the page fault occurring. After a few days I had it warranty serviced, and the problem was said to be my video card, which was then replaced by the company (ABS) with a Radeon 9500 (I originally thought the problem was heat-related, as one of my motherboard fans was never on--I've since replaced it, and last I looked inside my case, this same fan wasn't spinning).

Eventually I learned how to disable XP automatic restart so that I could actually see what the BSOD was saying. Over time, it has had two different trends (ie I"ve gotten two different types of messages):

1. PAGE FAULT IN NONPAGED AREA followed by some memory addresses
2. PAGE FAULT IN NONPAGED AREA followed by a message saying that "win32.sys seems to be causing the problem"--this one first appeared a week or two ago

A few nights ago I checked XP Event Viewer for the first time to try and get more of a sense of what is going on. The most recent crash was about 40 minutes ago, and the last one before that was in the afternoon today. Here are some of the events leading up to each crash, as told by the Event Viewer, in descending order of time:

-Most Recent Crash:
1. Warning at 12:12 AM:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
2. System Error at 12:11 AM:
Error code 10000050, parameter1 9f8046c7, parameter2 00000000, parameter3 9f8046c7, parameter4 00000000.
3. Save Dump at 12:10:05 AM:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0x9f8046c7, 0x00000000, 0x9f8046c7, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini020505-01.dmp.
4. eventlog at 12:10:03 AM:
The Event log service was started.
5. eventlog at 12:10:03 AM:
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

-Last Crash Before the One Above (8 hours earlier):
1. Warning at 4:27:17 PM:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
2. System Error at 4:24:19 PM:
Error code 1000008e, parameter1 c0000005, parameter2 bf8fdfa9, parameter3 ebb51d6c, parameter4 00000000.
3. Save Dump at 4:22:30 PM:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8fdfa9, 0xebb51d6c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini020405-02.dmp.
4. eventlog at 4:22:30 PM:
The Event log service was started.
5. eventlog at 4:22:30 PM:
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

The next entries after that are a W32Time Warning preceded by another TCP/IP warning.

The TCP/IP warning seems to FOLLOW almost every crash recorded by Event Viewer, which leads me to believe that it's connected to my system startup (although the one that was recorded after the first crash described occurred about a minute and a half after the System Error).

Up until about a month ago, I thought this was a memory problem. I ran GoldMemory about a week ago, and the extended test was passed. Next I checked the HDD that XP is installed on with Western Digital's Data Lifeguard Diagnostics, and this test passed as well. My next thought is to test the power supply, as I've read that it can cause problems such as this.

The one piece of suspect hardware other than memory and the HDD that I have been considering is my ATI VE TV Tuner, which has given me problems since day one. It was a pain to install with XP in the first place, then it stopped working with cable, and then recently it stopped working with VCR composite input. I've disabled it, but it's still physically installed (and the page fault has occurred since I disabled the card).

Lastly, the crash's occurrences seem to me to happen during more memory-demanding situations. For example, it used to happen during certain parts of Far Cry about a year ago, it happens when I have many Firefox or IE windows open at one time, it happens when I simultaneously play MP3s with one app and send them to an MP3 player with another app, and it happened the last time while I was transferring video files between HDDs (and using Firefox, and listening to MP3s with WMP).

Any help would be very much appreciated. Please let me know if you need any more information to make your assessments. Some of my specs are below.

AMD Athlon 2200+
512 MB of DDR RAM
WD Caviar SE 80 GB HDD (with Windows XP Pro SP2 installed)
WD Caviar SE 120 GB HDD

As far as software goes, I've had Symantec Antivirus Corporate 8.0 installed for most of the time I've had this computer. Almost every resource I've found on this problem says that antivirus software is something to consider, but so far I haven't done anything about it...
 
Okay, getting the same errors (0x0A and 0x50). Went through my minidumps (about 5 of the 20 or so) and win32k.sys is the culprit as of right now. Went and did the Prime95 torture test and failed at the first test with an ILLEGAL SUMOUT, any ideas? Still haven't done the memtest yet.

Stats:
Asus A8v Deluxe mobo
AMD 3200+ 2.0Ghz
1Gb Kingston DDR
nVidia GeForce 6800 128mb AGP
Maxtor 120 Gb SATA hd
 
hey everyone... i've been reading these problems and i too have the same problem but worst... everytime i try to start my computer... it crashes before i get to windows... it varies with the BSOD... sometime it shows the page fault... then the IRQL... and many more... i dont know what to do... please someone help..
 
Hi Stormshadow,

If your PC cannot passes Prime 95 stress test, it is a hardware error. Attach 3 to 4 minidumps, if you want to confirm whether it is hardware error or not
 
To SuperTai,

If you cannot boot into safe mode, it is a hardware error. If you can boot into safe mode, disable some unncessary component and restart windows.
 
hey thanks for the advice.. but i founded out the problem... it took me forever tho... it was one of the memory card... it was defective.. so i removed it and the computer started.. but i have half the memory now tho.. :)
 
To Atrice,

Probably it is hardware problem at your motherboard or CPU. All of your dump fail at the different instruction address and it is the symptom of hardware error.

Summary of windbg analyze result
BugCheck 10000050, {be800a72, 0, be800a72, 2}
Could not read faulting driver name
Probably caused by : hardware

Followup: MachineOwner
---------
*** Possible invalid call from bf87ce3e ( win32k!NtUserDeferWindowPos+0x85 )
*** Expected target bf800a66 ( win32k!LeaveCrit+0x0 )

Attach three to four more minidumps so I have better idea which hardware component is the culprit.
 
I was beginning to think so. My first thought was memory, then the HDD. Both passed tests though (not that that means they are fine). Here are the four most recent dumps. And thank you very much for doing this.
 
Okay so I went in and UNDER-clocked my CPU's fsb from 200 to 190 so it's running at 2.85 instead of 3.0, and now the crashes are gone. weird? i dont know. but i do know my CPU is running at ~71-72 C no load. ouchie. is this > bad ? hehe. lemme know!
 
CPC2004 (or anyone), can you help?

Hi all,
My system's been BSOD'ing a lot lately. About 2 weeks ago it was stable, since then I added RAM, a USB card, uninstalled and reinstalled 2 different USB memory card readers, a USB hub, and a new hard drive. I need help determining the cause of my errors. CPC2004 seems to be rather good at debugging them, so I hope he can help.

Here's my errors:
1. 2/03/2005 09:44:57 PM
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x1175c08d, 0x00000002, 0x00000000, 0x8065d063). A dump was saved in: C:\WINDOWS\Minidump\Mini020305-01.dmp

2. 2/05/2005 11:21:09 AM
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2 (0x00000007, 0x00000cd4, 0x05070000, 0x85f4b430). A dump was saved in: C:\WINDOWS\Minidump\Mini020505-01.dmp.

3. 2/05/2005 02:54:58 PM
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x87179108, 0x87179940, 0x0b070000). A dump was saved in: C:\WINDOWS\Minidump\Mini020505-02.dmp

4. 2/05/2005 11:46:19 PM
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0x8af000ed, 0x00000000, 0x8af000ed, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini020505-03.dmp.

5. 2/06/2005 12:00:05 AM
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8054b01a, 0xf775ec4c, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini020605-01.dmp.

6. 2/08/2005 03:35:53 PM
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000c5 (0x00000000, 0x00000002, 0x00000001, 0x8054ba39). A dump was saved in: C:\WINDOWS\Minidump\Mini020805-01.dmp.

I also have two other minidumps that I don't have Event Viewer listings for available right now, Mini020605-02.dmp and Mini020605-03.dmp

If anyone could help me, that would be great. No rush, but I would like assistance in trying to determine which new part is at fault. Minidumps are spread across the followin three zips.

Please let me know if you require any additional information.
 
Ah, just my thread. For the past month, I have received BSoD whenever I play games on my computer. I can use any other application just fine, but games just don't work anymore. The Sims 2 merely crashes and goes back to the desktop, whereas KotOR gets me a STOP message. Reasons for the stops vary, but it's either the IRQL or the Page Fault blue screen. The page fault specifies no file causing the error, the IRQL stop specifies cmuda.sys, which happens to be the driver for the on-board audio. I bought a new RAM stick, 512 MB, just last week, same result. I installed the most recent audio driver, still no luck. I disabled sound via BIOS, still no luck.

My specs:
AMD Duron 1.2 Ghz
Elitegroup K7SOM+ board
GeForce2 PCI video card
768 MB RAM, PC400
80 GB HD
OS: XP Professional SP 2

I am using the 61.77 Nvdia Driver, as 66.93 did not work for me. That was when my system was still working. I have used the same configuration for many months, it's only been recently the problems popped up. I can trace the problem back to running two 256 MB RAM sticks in my computer, one a PC400, one a PC333. The PC400 one has worked just fine for almost a year, I might note. Ever since I added the PC333 stick, the crashes began. I have since replaced the PC333 with a 512 MB PC400 stick. Maybe too fast for my board which is fairly old?

My suspicion is that my board is toast. I have always had great heat problems with my CPU, in summer the CPU gets to 167 degrees F, and the case temperature not much cooler (according to Motherboard Monitor). My case is fairly small and air flow is very reduced.

I have attached the minidumps of this week, and would appreciate any help you can give me. Thanks!
 
To Stiletto,

Bugcheck code C5 is usually casued by faulty ram. Run memtest to stress test your memory stick. Maybe the memory slot contact is bad. Reseat memory stick to another memory slot and it may resolve your problem.
 
thank you pc for your time, however, i read the link you gave and wasnt able to come up with anything with which i might fix my system. I'm still getting crashes when i play games especially. I will attach the last 6 .dmp i have recieved. I just upgraded my ATI drivers and control panel. CPU is at 71 C but system is at 35 C.
I've got a new stick in my system and it's crashing.

Cheers
 
Status
Not open for further replies.
Back