BSOD - PAGE_FAULT_IN_NONPAGED_AREA

[BigAl.NZ]

Hi Guys,

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

win32k.sys - Address BF8B5D36 base at BF800000, datestamp 43446a58"

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was
okay until the BSOD errors started. Subsequent to the BSOD errors
various items in device manager have been getting yellow exclamations
marks. Namely CDROM drive got Code 41 - device driver present but
cannot find hardware (cd drive is there in bios and a little regfix i
found on the net fixed it) but I also have a fail on network card
(code 19 registry corrupt/damaged) and a code 19 also on sound card.

I have run memtest86+ and it is failing on test 7 twice out of 4 runs.
The memory address is it failing at is different tho.....

I am gonna try to get it to fault again and see if its always
win32k.sys, but does anyone else have any help on this one? Something
is causing failures...

Oh and it has a cheap and nasty 300W Hyena PSU....which has been in it
for some time.

Cheers

-Al

 

[Cadae]

Hi Guys,

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

win32k.sys - Address BF8B5D36 base at BF800000, datestamp 43446a58"

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was
okay until the BSOD errors started. Subsequent to the BSOD errors
various items in device manager have been getting yellow exclamations
marks. Namely CDROM drive got Code 41 - device driver present but
cannot find hardware (cd drive is there in bios and a little regfix i
found on the net fixed it) but I also have a fail on network card
(code 19 registry corrupt/damaged) and a code 19 also on sound card.

I have run memtest86+ and it is failing on test 7 twice out of 4 runs.
The memory address is it failing at is different tho.....

I am gonna try to get it to fault again and see if its always
win32k.sys, but does anyone else have any help on this one? Something
is causing failures...

Oh and it has a cheap and nasty 300W Hyena PSU....which has been in it
for some time.

Cheers

-Al

Sounds like a hardware problem - could be any one of (in order of
likelihood):
RAM, PSU, hard disk,Motherboard,CPU. I'd try swapping each of these with a
borrowed or old working component till the fault goes away.

PC

 

[bok]

Hi Guys,

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

win32k.sys - Address BF8B5D36 base at BF800000, datestamp 43446a58"

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was
okay until the BSOD errors started.

The change from rebooting to BSOD could be accounted for by turning off
the XP Startup and Recovery 'Automatically Restart' on system failure
option accessible from system properties.

This error normally means kernel mode software (O/S or device driver) is
attempting to access memory using an invalid memory address. It's most
likely a hardware issue as suggested by Cadae. I'd also add overheating
to your check list. Check CPU and M/B temp sensors if possible.

 

[Pennywise]

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

From the NT resourse kit but it still holds true.

STOP: 0x00000050 (<parameter>, <parameter>, <parameter>, <parameter>)
PAGE_FAULT_IN_NONPAGED_AREA

Component: Executive STOP


Explanation:
This is a Windows NT Executive character-mode STOP message. It
indicates a page fault in the address space reserved for nonpaged
data.

User Action:
If this is the first time you have booted after installing additional
hardware, remove the hardware and boot again. Check the Microsoft
Hardware Compatibility List to verify that the hardware and its
drivers are compatible with Windows NT. For information about the
hardware, contact the supplier.If you are installing Windows NT for
the first time, check the Windows NT system requirements, including
amount of RAM and disk space required to load the operating system.
Also check the Hardware Compatibility List to verify that the system
can run Windows NT. If Windows NT is loaded and no new hardware has
been installed, reboot with recovery options set to create a dump
file. If the message continues to appear, select the Last Known Good
option when you reboot. If there is no Last Known Good configuration,
try using the Emergency Repair Disk. If you do not have an Emergency
Repair Disk, contact your technical support group.

 

[Otter]

In

Hi Guys,

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

win32k.sys - Address BF8B5D36 base at BF800000, datestamp 43446a58"

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was
okay until the BSOD errors started. Subsequent to the BSOD errors
various items in device manager have been getting yellow exclamations
marks. Namely CDROM drive got Code 41 - device driver present but
cannot find hardware (cd drive is there in bios and a little regfix i
found on the net fixed it) but I also have a fail on network card
(code 19 registry corrupt/damaged) and a code 19 also on sound card.

I have run memtest86+ and it is failing on test 7 twice out of 4 runs.
The memory address is it failing at is different tho.....

I am gonna try to get it to fault again and see if its always
win32k.sys, but does anyone else have any help on this one? Something
is causing failures...

Oh and it has a cheap and nasty 300W Hyena PSU....which has been in it
for some time.

Seen page 50 of the MB manual? It warns about loading optimized default
options...

 

[BigAl.NZ]

Thanks - all good suggestions.

I was very suspect of the PSU or RAM. Doesnt the fact that there are
errors in the registry suggest bad sectors on the HDD?

Bad sectors on the HDD could be caused by low or faulty PSU?

Cheers

-Al

 

[BigAl.NZ]

The change from rebooting to BSOD could be accounted for by turning off
the XP Startup and Recovery 'Automatically Restart' on system failure
option accessible from system properties.

Good point.

 

[BigAl.NZ]

One more thing. The PC stayed on all night without BSOD.

Whats a good program to stress test the PC in various ways?

I tried that prime one but it complained about not getting the result
it expected and terminated the tests.

-Al

 

[Rock]

One more thing. The PC stayed on all night without BSOD.

Whats a good program to stress test the PC in various ways?

I tried that prime one but it complained about not getting the result
it expected and terminated the tests.

You tested the memory and got errors so have you changed the memory?

 

[§ñühw¤£f]

X-Newsreader: slrn/0.9.8.1pl1 (Debian)
Date: 30 Jan 2007 15:56:20 GMT
Lines: 42
Message-ID: <[email protected]>
NNTP-Posting-Date: 30 Jan 2007 09:56:20 CST
X-Trace: DXC=Sj>3g?0ng@;RmO[JoT=VM:]AGWjF5PjP9465Ue@WB_5?hl3V<;dXeE4]nK=3`F;XS;Y9S_[G10WaRLQ9UOPd84?3UWj4Kaio=
Xref: number1.nntp.dca.giganews.com 24hoursupport.helpdesk:1485255 alt.os.windows-xp:547277 alt.usenet.kooks:1444670 microsoft.public.windowsxp.general:1729671 nz.comp:462332

Yuhai the hagfish-butter <[email protected]> pinched out a
steaming pile of<F7FF15FF.25654792.A03040F7.827B8BD4@teensy-purple-
piledriver.net.nz>:

Supersano <[email protected]> Thou kindless villain. Tempt not too
much the hatred of my spirit, for I am sick when I do look on thee. Thou
tardy son. As goodness is poison to your stomach. Ye spouted and ye
hollered:


That's a ****ing joke, yeh?

Lets be *real* irresponsible and tell them to lick it before sticking
it back on.

FYI the special goo is made of:
http://en.wikipedia.org/wiki/Thermal_grease

The silver based shit is toxic btw...HTH

 

[BigAl.NZ]

You tested the memory and got errors so have you changed the memory?

No, each time the memory test ran it faulted in different areas? And i
think I read somewhere that sometimes memory errors can actually be
other things?

-Al

 

[Rock]

No, each time the memory test ran it faulted in different areas? And i
think I read somewhere that sometimes memory errors can actually be
other things?

What memory testing utils did you use. Here are three. Run at least two of
them.
But I would swap out the memory for known good sticks.

Memtest86+
http://www.memtest.org/

Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

DocMemory Memory Diagnostic
http://www.simmtester.com/page/products/doc/download.asp

 

[Ron Martell]

Hi Guys,

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Technical Info:
*** STOP: 0x00000050 (0xDFFF0829, 0x00000000, 0xBF8B5D36, 0x00000000)

win32k.sys - Address BF8B5D36 base at BF800000, datestamp 43446a58"

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was
okay until the BSOD errors started. Subsequent to the BSOD errors
various items in device manager have been getting yellow exclamations
marks. Namely CDROM drive got Code 41 - device driver present but
cannot find hardware (cd drive is there in bios and a little regfix i
found on the net fixed it) but I also have a fail on network card
(code 19 registry corrupt/damaged) and a code 19 also on sound card.

I have run memtest86+ and it is failing on test 7 twice out of 4 runs.
The memory address is it failing at is different tho.....

I am gonna try to get it to fault again and see if its always
win32k.sys, but does anyone else have any help on this one? Something
is causing failures...

Oh and it has a cheap and nasty 300W Hyena PSU....which has been in it
for some time.

Defective RAM is one of the common causes of the error message that
you reported. And if Memtest86+ has reported failures in the RAM
then that is all the confirmation you should need.

At a very miminum you need to take the RAM to a repair shop that has a
hardware memory tester and have them check out the RAM. Either that
or replace the RAM.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[Supersano]

I have in front of me a Pentium 4 Socket 478 PC. Motherboard is a ECS
L4S8A2. Also has a internal dialup modem (not used) and a AGP graphics
card. Running XP SP2.

The computer is giving BSOD's. Details are:

"The problem seems to be casued by the following file: win32k.sys

PAGE_FAULT_IN_NONPAGED_AREA

Another little bit of history to this problem. Before christmas it was
spontaneous rebooting. So they had a guy format it. After that it was

Have you pulled the processor heat sink and checked the transfer paste?
Could be dried up.

 

[BigAl.NZ]

Hi Ron,

Defective RAM is one of the common causes of the error message that
you reported. And if Memtest86+ has reported failures in the RAM
then that is all the confirmation you should need.

At a very miminum you need to take the RAM to a repair shop that has a
hardware memory tester and have them check out the RAM. Either that
or replace the RAM.

Before I swapped out the RAM I tried Prime95 which on torture test. It
would only run for about 5 seconds before reporting:
Test1
FATAL ERROR: Rounding ...... expected less than ........
Hardware Failure Detected

I assume this must be reflective of the underlying error casuing the
BSOD?

So I swapped out the RAM and PSU and run prime95 - again it said
hardware error after a few seconds and stopped.

Assuming that when I fix Prime95, I will also fix the BSOD, then it
cant be the RAM because Prime95 faulted with known good RAM in.

I am thinking maybe CPU now?

Any other thoughts?

-Al

 

[Ron Martell]

Before I swapped out the RAM I tried Prime95 which on torture test. It
would only run for about 5 seconds before reporting:
Test1
FATAL ERROR: Rounding ...... expected less than ........
Hardware Failure Detected

I assume this must be reflective of the underlying error casuing the
BSOD?

So I swapped out the RAM and PSU and run prime95 - again it said
hardware error after a few seconds and stopped.

Assuming that when I fix Prime95, I will also fix the BSOD, then it
cant be the RAM because Prime95 faulted with known good RAM in.

I am thinking maybe CPU now?

Any other thoughts?

Motherboard? Damaged DIMM sockets?


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[BigAl.NZ]

For anyone still following this thread it turned out to be the
motherboard.

Swapped it out today and ran Prime95 for hours - no errors.

Thanks for everyones helpful suggestions.

-Al

 

[Rock]

For anyone still following this thread it turned out to be the
motherboard.

Swapped it out today and ran Prime95 for hours - no errors.

Thanks for everyones helpful suggestions.

Thanks for posting back the resolution. No surprise that it was hardware.