BSOD: Page_Fault_in_nonpaged_area

Hello again,

I've been having a few issues with my system recently. My system is as follows:

MSI K7T266 Pro (MS-6380) Motherboard
VIA Apollo KT266 Chipset
VIA AC'97 On-Board Audio
AMI Bios
AMD Athlon 1.4GHz
256MB DDR RAM
32MB Geforce 2MX
HPT370 UDMA/ATA-100 RAID
Maxtor 80GB HDD
LG DVD-ROM
HP CD-Writer
RealTek Ethernet Adapter

Windows XP Pro (2600 RTM) Fully updated with all patches & drivers. NVidia Detonator XP 21.83.

Now I'm not sure if this problem with various blue screens I get is because of the well known nv4_disp.dll / loop error problem (because I do get occasionally BSODs about that too)

See http://www.viaarena.com/?PageID=64
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=5270
http://www.theinquirer.net/05120107.htm for more info on that problem.

(I would also be grateful of any ideas/solutions/comments on that problem too or if you are having it also)

But do you think this BSOD "Page_Fault_in_nonpaged_area" is to do with that problem aswell? I don't get it very often and there is no pattern to it either sometimes it can be fine for days and fine in games too, but then sometimes when I'm not even doing anything particular it can do it... extremely random with no pattern that I can tell. That BSOD also usually mentions win32k.sys as the problem file.

Please offer some assistance if you can.

Many Thanks

 

Page_Fault_in_nonpaged_area is way too generic an error to be really useful by itself.

If you could post the entire, exact message including the memory locations it would help.

 

Right I had the BSOD again so I copied down all the useful info from it.

"A problem has been detected and windows has been shutdown to prevent damage to your computer..... etc....etc....

Technical Information:

*** STOP: 0x0000008E (0x0000005, 0x00000000, 0xF5E82540, 0X00000000)

Are these numbers really helpful? Can you actually determine a cause & resolution from these? Is there some MS web site with ADVANCED information on these numbers/codes?

Please help me if you can!

 

That particular set of stop addresses is typical of a problem with your NVidia drivers. At times, you will run an update and it will fail silently - you will think it worked fine.

Check your Control Panel~System~Hardware tree to see if you are running Via or M$ drivers and if Via, do you have the version you expect.

As to your other question, the M$ support site will usually have an article containing the stop addresses if they have dealt with an issue where they were frequent or typical. You can usually search the Kb using the first number (0x0000008E in your case) and see what pops up. Freqently you will find reference to the other addresses and a cause/fix there.

XP is so new that much of the information isn't yet on the M$ site though. In that case, run the numbers thru a good search engine and see if anyone out there is talking about it.

 

Yes, I half expected it to be to do with my NVidia graphics drivers problem. And I assume that this will be fixed, but will just take time because as you say, XP is very new. However, what I don't understand is why for some reason it happens like twice in a row maybe a hour or bit more apart then not for weeks then again a couple of times and then again and then maybe not (ie. completely random) seems very odd that its random and does occur doing all different things (sometimes even not doing anything or running anything at all!).

So you ran that number though the MS KB and found it that way?
I will try the search engine idea actually, but I guess it's still be looked into.

I think MS really need to sort themselves out a bit, ok XP is new and there will be problems with anything new, nothing can solve that, but really need to start fixing stuff and explaining XP a bit more there is really so much of it no-one knows about and so much of it un-documented (even on the thousands of XP sites I've read completely!!).

Well thanks for your help anyway

If you do come across any news/info/solutions/ideas for this problem let me know! (cheers)

 

DJ - best search engine I've found for this sort of thing is www.google.com.

I have technet but if I fail to find a hit on that, I run a google search rather than going directly to M$. It finds their articles too.

 

Don't worrry

Most of this errors are caused by small bugs in random dll. 's wich caused BSODs so it may fixed only recent driver updates.