Page Fault in Non Paged Area

Status
Not open for further replies.
I wish I could but I always prevented those from running. I guess in retrospect that was a bad idea. I think I'm just going to order a new mobo and cpu. I'm about due for an upgrade. Thank you for all your help.
 
Help

Can someone please have a look at my minidumps and tell me if my problem is most likely hardware or software related. I really need to get to the bottom of this!

thankyou..

Ben
 
Greetings... I am having very similar problems to what I'm seeing here. My bug checks (0x7f/8e/0a/50/etc) occur randomly and annoyingly frequently. I've tried changing video cards, drivers, testing/changing ram, and reinstalling XP Pro to no avail. Windows debugger often points to win32k.sys as the culprit, but I doubt that's the case. How do I find out what is wrong? I am at my wit's end. Thanks for taking the time to read this.
 
Howdy and thank you! My power supply is the generic 250W(?) unit that came stock with my Compaq Presario 7000US. It doesn't seem to be running particularly hot, as far as I can tell.
 
Please go HERE and read my post.

The reason I asked about your psu, is because if it is underpowered for your system it could well be causing the problems you are having.

The generic 250watt psu that came with your case, is deffinitely suspect. I doubt if it is capable of putting out 200watts. And I wouldn`t mind betting that the amps it gives are really low.

Go HERE for a handy psu wattage calculator.

Also go HERE for an excellent article on psu`s.

Regards Howard :) :)
 
First off, thanks for your prompt replies and for the helpful links. I filled out the form in my profile as suggested- sorry about not being clearer! According to the wattage calculator, my devices come in at just under the 250 watts that the PSU allegedly puts out- that can't be good. The problems with the BSODs have been getting worse over time, and they tend to be rather random as I explained in my original post; they can occur whether I'm trying to play a game, or when the computer's just idling. It also froze once. A tech-savvy friend told me it was likely the MB, but the PSU sounds like it could be the culprit as well. It definitely isn't the RAM as I've tested various sticks under Memtest overnight and none of them have returned errors, although one crashed my comp during a bit fade test.
 
ObiWanShinobi said:
First off, thanks for your prompt replies and for the helpful links. I filled out the form in my profile as suggested- sorry about not being clearer! According to the wattage calculator, my devices come in at just under the 250 watts that the PSU allegedly puts out- that can't be good. The problems with the BSODs have been getting worse over time, and they tend to be rather random as I explained in my original post; they can occur whether I'm trying to play a game, or when the computer's just idling. It also froze once. A tech-savvy friend told me it was likely the MB, but the PSU sounds like it could be the culprit as well. It definitely isn't the RAM as I've tested various sticks under Memtest overnight and none of them have returned errors, although one crashed my comp during a bit fade test.

Ironduke is spot on.

Go and get a new good quality psu. Somewhere in the region of 400watts should be about right.

Regards Howard :grinthumb
 
IronDuke & Howard,

Okiedokie. The system wasn't that unstable when I first got it (therefore the PSU thing never occurred to me) but it started edging toward that direction after a couple of years of use. I did notice that during the summer the pc would run rather hot, which should have been a clue. Duh. I'll give that a try. Thank you both for your help. You guys are awesome!
 
Please I need Help

Ok, I'll try a third time ;)

I am getting about one blue screen a day at the moment - mainly featuring the ***STOP: 0x0000008E message. I have recently bought a 550W power supply and have an AMD Athlon XP 2800+ 2.09 GHz and 1.5 GB ram. I just really want to get to the bottom of this, as I am a web designer and this is causing me great annoyance. I would just like to know if this is likely a hardware or software issue.

Thanks in advance..

Ben
 
also having problems

hello i am new to the boards and came across this topic. i have a similar problem on my newly built system.

amd 3000 1.8
asus a8v
ocz 512x2
geforce fx5200 (old card) driver 71.89
ultra 400 watt power supply



the description is as follows:

the computer has rebooted from a bugcheck. the bug check was: 0x00000050 (0xe123043c, 0x00000001, 0x805368a2, 0x00000001)

i attached also my last 4 minidumps.

please help me if possible.


thank you in advance
 
Kwest19 said:
Ok, I'll try a third time ;)

I am getting about one blue screen a day at the moment - mainly featuring the ***STOP: 0x0000008E message. I have recently bought a 550W power supply and have an AMD Athlon XP 2800+ 2.09 GHz and 1.5 GB ram. I just really want to get to the bottom of this, as I am a web designer and this is causing me great annoyance. I would just like to know if this is likely a hardware or software issue.

Thanks in advance..

Ben
Your computer crashed with nt status code c000001d (ie illegal instruction) which is usually caused by faulty mother board or CPU. The problem is not related to RAM.

Mini060705-01.dmp
BugCheck 1000008E, {c000001d, bf8be0ff, ab8eea98, 0}
Probably caused by : hardware ( win32k!xxxHkCallHook+24d )
 
mister rp said:
hello i am new to the boards and came across this topic. i have a similar problem on my newly built system.

amd 3000 1.8
asus a8v
ocz 512x2
geforce fx5200 (old card) driver 71.89
ultra 400 watt power supply



the description is as follows:

the computer has rebooted from a bugcheck. the bug check was: 0x00000050 (0xe123043c, 0x00000001, 0x805368a2, 0x00000001)

i attached also my last 4 minidumps.

please help me if possible.


thank you in advance

Your 2nd dump is inaccesible and the first dump failed at nt!ExAllocatePoolWithTag+671. Faulty ram is the culprit. Reseat the memory may resolve the problem. If it doesn't work, take out a memory stick if you have more than one memory stick. Trouble shoot which memory stick is one.

cpc2004
 
It'll be a few days before I get that new power supply as was suggested, so (in the meantime) I wanted to try and rule out other possible causes for my random blue screens. I've run several of my recent dumps through Windows Debugger along with the !analyze -v command and saved them as text files. (One of them I missed because my computer BSODed during the analysis.... I believe it was an IRQL_NOT_LESS_OR_EQUAL dump) Could one of you possibly take a quick look at them and tell me what you think? I'm not quite sure how to decipher what's going on and, if nothing else, I'd like to be able to understand things a tad better. Thanks again!
 
cpc2004 said:
Your 2nd dump is inaccesible and the first dump failed at nt!ExAllocatePoolWithTag+671. Faulty ram is the culprit. Reseat the memory may resolve the problem. If it doesn't work, take out a memory stick if you have more than one memory stick. Trouble shoot which memory stick is one.

cpc2004


thank you very much cpc2004 for your help! it was indeed one of the memory sticks. too bad i bought my hardware overseas =\
 
Hi,

I'm currently having the same problem, but first of all my pc system:

AMD 64XP 3500+
Asus A8V Deluxe
MSI Geforce 6800GT
TwinMOS Dual 1024MB RAM

Now the problem:
After playing maybe 5-8 hours World of Warcraft, I get strange graphical bugs like those:

http://zuLu-tourney.de/bug1.jpg
http://zuLu-tourney.de/bug2.jpg

Of course I can't keep playing like that, so I either have to restart my PC or close the game. I also found out that as soon as this problem occurs, my pc seems to be very slow until I close the game. Sometimes a BSOD arrives before I'm able to do that. If I close the game, I seem to have only few hours until that bug occurs again, but if I restart the PC, i have those 5-8h again.
Maybe I should mention that I changed the GPU Cooler twice (i've never done that before), so maybe I damaged a ram on the graphic board or something.

What I've already done:
- Checked the Mainboard and CPU temperature just after restarting and it was ok (20-30°C mb and 40-50°C CPU)
- Installed latest nvidia drivers => nothing changed
- formatted my HDD => the bug seemed to be gone but soon arrived again..
- Memtest 15hours => no error

and one week ago, after reading some pages of this topic, I downloaded Nvidia 61.77 drivers and uninstalled my AV Program (FreeAntiVir). The bug hasnt occured again, at least until 30mins ago.... (and thats why i write this post).

A friend of mine said that the rams on the graphic board might have been damaged. That would be bad because i changed the cooler so i lost my guarantee of the graphic card.

I attached a Dump log of the BSOD which happened a few minutes ago ^^.

Thanks for any help in advance.
 
I've got a P4 2.4B and an Asus P4PE. One of them are faulty.

Normally I run my p4 2.4 at 2.7 (since i got it over 2 years ago), then some months ago windows was blue screening, and I found pulling back on the speed (to stock) and it was fine, and since it worked I had other things to worry about.

Come two weeks ago, again blue screening... pretty random, hard to replicate but very quickly got worse... sometimes I'd get into windows, and bam bsod... or maybe i'tll be fine for a few hours THEN bsod, eventually it would just BSOD on loading too.
The blue screens are stop errors, most commonly irql not less or equal or page fault in non paged area (0x0000008E with (0xC0000005, 0x805122DE, 0xED334C04, 0x00000000) is pretty common). I ended up putting the fsb to 100 (from stock of 133), and cpu runs at 1.8 and it was fine (after swapping out everything (psu, ram, video card, pci cards, hard disks, etc), the only things I havent tried are swapping mobo/cpu. ), and it was fine running under the stock speed at 1.8. And it's not a heat issue either - cpu and mobo temps are always relatively low.

Come yesterday, same **** again... bsod, reboot and bsod again, reboot agian, i log in, 2 mins later, bsod... I give up and I cant make it go any slower
Either the cpu or mobo need to be replaced/rma'd, I dunno which, although I'm slightly leaning more towards cpu.

Ok I've finally pulled the minidumps out of it...
Getting the minidumps was hell, just bsod after bsod on loading windows or logging in... I put the vcore from 1.5 to 1.65 and it lasted long enough to get explorer and event viewer open...and crash... Pushed the vcore to 1.7 (EEK), and it's been stable not only for seconds, but a good 15 minutes! looks like 99% it's the cpu now
Having the expert here taking a look at the dump files would really be appreciated

I think it's time for a new PC anyways, hopefully Athlon64 here I come :)
 
might help...

hey..ive read about fixes for this problem...although mine still resumes..but its not as frequent as it used to be..my problem is i installed the ram backwards...and now the ram is faulty. still need to replace it. but im not sure if i messed up my mombo.. i have no extra ram to test it..my windows runs fine now except the crashes..well i havent crashed in about 3 days now.
this error is really comon. and happens to people with mainly ati or nvidia cards and nforce or sis and via chipsets...which is almost everone i think...
if you know any way i can find out if i screwed up my mainboard i would apreciate it...thanks....

one most common fix is.. cleaning ram with an eraser and alcohol(isopropyl)70% or greater(90%recomended)...(cleaning the pins)
or by simply reseating ram.
lowering ram clock speeds(making sure ram is compatible with board)
changing the power supply
upgrading bios
cooling northbridge/southbridge
cooling your tower(upgrading thermal,heatsinks, fans,cleaning....)
upgrading graphic drivers
installing hotfix from microsoft(have to call)
 
sunrise3500 said:
I've got a P4 2.4B and an Asus P4PE. One of them are faulty.

Normally I run my p4 2.4 at 2.7 (since i got it over 2 years ago), then some months ago windows was blue screening, and I found pulling back on the speed (to stock) and it was fine, and since it worked I had other things to worry about.

Come two weeks ago, again blue screening... pretty random, hard to replicate but very quickly got worse... sometimes I'd get into windows, and bam bsod... or maybe i'tll be fine for a few hours THEN bsod, eventually it would just BSOD on loading too.
The blue screens are stop errors, most commonly irql not less or equal or page fault in non paged area (0x0000008E with (0xC0000005, 0x805122DE, 0xED334C04, 0x00000000) is pretty common). I ended up putting the fsb to 100 (from stock of 133), and cpu runs at 1.8 and it was fine (after swapping out everything (psu, ram, video card, pci cards, hard disks, etc), the only things I havent tried are swapping mobo/cpu. ), and it was fine running under the stock speed at 1.8. And it's not a heat issue either - cpu and mobo temps are always relatively low.

Come yesterday, same **** again... bsod, reboot and bsod again, reboot agian, i log in, 2 mins later, bsod... I give up and I cant make it go any slower
Either the cpu or mobo need to be replaced/rma'd, I dunno which, although I'm slightly leaning more towards cpu.

Ok I've finally pulled the minidumps out of it...
Getting the minidumps was hell, just bsod after bsod on loading windows or logging in... I put the vcore from 1.5 to 1.65 and it lasted long enough to get explorer and event viewer open...and crash... Pushed the vcore to 1.7 (EEK), and it's been stable not only for seconds, but a good 15 minutes! looks like 99% it's the cpu now
Having the expert here taking a look at the dump files would really be appreciated

I think it's time for a new PC anyways, hopefully Athlon64 here I come :)

I don't believe that it is hardware error as the failing instruction is consistent.
I think the problem is related to firewall or anti-virus software. De-install avg7core.sys. Maybe it resolves the problem

cpc2004
 
TrunkZ said:
Hi,

I'm currently having the same problem, but first of all my pc system:

AMD 64XP 3500+
Asus A8V Deluxe
MSI Geforce 6800GT
TwinMOS Dual 1024MB RAM

Now the problem:
After playing maybe 5-8 hours World of Warcraft, I get strange graphical bugs like those:

http://zuLu-tourney.de/bug1.jpg
http://zuLu-tourney.de/bug2.jpg

Of course I can't keep playing like that, so I either have to restart my PC or close the game. I also found out that as soon as this problem occurs, my pc seems to be very slow until I close the game. Sometimes a BSOD arrives before I'm able to do that. If I close the game, I seem to have only few hours until that bug occurs again, but if I restart the PC, i have those 5-8h again.
Maybe I should mention that I changed the GPU Cooler twice (i've never done that before), so maybe I damaged a ram on the graphic board or something.

What I've already done:
- Checked the Mainboard and CPU temperature just after restarting and it was ok (20-30°C mb and 40-50°C CPU)
- Installed latest nvidia drivers => nothing changed
- formatted my HDD => the bug seemed to be gone but soon arrived again..
- Memtest 15hours => no error

and one week ago, after reading some pages of this topic, I downloaded Nvidia 61.77 drivers and uninstalled my AV Program (FreeAntiVir). The bug hasnt occured again until now (and thats why i write this post).

A friend of mine said that the rams on the graphic board might have been damaged. That would be bad because i changed the cooler so i lost my guarantee of the graphic card.

I attached a Dump log of the BSOD which happened a few minutes ago ^^.

Thanks for any help in advance.

Software error at nVidia Display Card Driver. Install nVidia Display Card Driver 61.77 http://www.nvidia.com/object/winxp_2k_61.77.html

cpc2004
 
cpc2004 said:
I don't believe that it is hardware error as the failing instruction is consistent.
I think the problem is related to firewall or anti-virus software. De-install avg7core.sys. Maybe it resolves the problem

cpc2004
(ive since put the vcore back to stock..) tried going into windows, blue screen pretty much as soon as it started loading with a stop 0x00000050 message O_o i tried booting knoppix (linux off cd, im sure you're familiar with it)... segmentation fault in loading

it's hardware..
 
Status
Not open for further replies.
Back