PAGE FAULT - doesn't look like a RAM issue. Advice please?

[Adam Steiner]

Hi,



I have a Sceptre SoundX 69002 (Dell Inspiron 5000e/Compal NW32, etc) that
had Microsoft ME on it. I've recently tried putting Windows XP SP1 on
it.with rather terrible results.



Initially, the computer ran well. However, after the second time I turned
it on and off, it began crashing with various errors such as
PAGE_FAULT_IN_NONPAGED_AREA and SESSION3_INITIALIZATION_FAILED.



I managed to do a System Restore to the beginning, when Windows was freshly
installed, only to have the same thing occur. I now receive the
PAGE_FAULT_IN_NONPAGED_AREA error every time the machine is turned on,
always immediately after the Microsoft Windows login screen for XP appears.
I tried 2 256MB chips and a 128MB chip (all three are PC100 and come from
two different manufacturers), singly and in all combinations, in each slot.
Same error, so I've pretty much ruled the RAM out (besides they all worked
fine under other versions of Windows).



I went to the MS website for error information. The second parameter is
always 0x00000000 (meaning a read operation). The following is the
information I received for the first (memory address accessed) and third
(referencing address) on the errors:



0xC97C0000, 0X8056AAA4

0XC9680000, 0X8056AAA4

0xC96C0000, 0X8056AAA4

0xC9840000, 0X8056AAA4

As you can see, the first parameter is always in a relatively narrow region
of memory, regardless of the RAM chip used. The third parameter is always
the same. I must admit that I do recall seeing the first parameter
beginning with a 0xF at times.



Any recommendations? Is there a way I can figure out what part of the
memory belongs to both the referencing and referenced locations? Can I turn
them off so that they aren't used (if they are bad). Perhaps they refer to
a system file that needs to be replaced?



Thoughts, ideas?



Thanks in advance,



Adam

[Kent W. England [MVP]]

XP is rather more finicky about memory than previous versions of
Windows. Pull the 128 MB memory chip out and see if it runs better.
There are many reports of problems with mismatched memory. Otherwise,
it's a driver, but you said it persists when you rollback to the install
date, so I think it's memory.

--
Kent W. England, Microsoft MVP for Windows



"Adam Steiner" > wrote in message
news:f4c50bb95ec2e64d576827b8ea4d7c0c@TeraNews...
> Hi,
>
>
>
> I have a Sceptre SoundX 69002 (Dell Inspiron 5000e/Compal NW32, etc)
that
> had Microsoft ME on it. I've recently tried putting Windows XP SP1 on
> it.with rather terrible results.
>
>
>
> Initially, the computer ran well. However, after the second time I
turned
> it on and off, it began crashing with various errors such as
> PAGE_FAULT_IN_NONPAGED_AREA and SESSION3_INITIALIZATION_FAILED.
>
>
>
> I managed to do a System Restore to the beginning, when Windows was
freshly
> installed, only to have the same thing occur. I now receive the
> PAGE_FAULT_IN_NONPAGED_AREA error every time the machine is turned on,
> always immediately after the Microsoft Windows login screen for XP
appears.
> I tried 2 256MB chips and a 128MB chip (all three are PC100 and come
from
> two different manufacturers), singly and in all combinations, in each
slot.
> Same error, so I've pretty much ruled the RAM out (besides they all
worked
> fine under other versions of Windows).
>
>
>
> I went to the MS website for error information. The second parameter
is
> always 0x00000000 (meaning a read operation). The following is the
> information I received for the first (memory address accessed) and
third
> (referencing address) on the errors:
>
>
>
> 0xC97C0000, 0X8056AAA4
>
> 0XC9680000, 0X8056AAA4
>
> 0xC96C0000, 0X8056AAA4
>
> 0xC9840000, 0X8056AAA4
>
> As you can see, the first parameter is always in a relatively narrow
region
> of memory, regardless of the RAM chip used. The third parameter is
always
> the same. I must admit that I do recall seeing the first parameter
> beginning with a 0xF at times.
>
>
>
> Any recommendations? Is there a way I can figure out what part of the
> memory belongs to both the referencing and referenced locations? Can
I turn
> them off so that they aren't used (if they are bad). Perhaps they
refer to
> a system file that needs to be replaced?
>
>
>
> Thoughts, ideas?
>
>
>
> Thanks in advance,
>
>
>
> Adam
>
>

[Adam Steiner]

I've tried it with the single 128, both 256's (one at a time and together).
That the error for parameter three stays the same makes me assume it is not
the RAM causing the problem...three bad chips? From different
manufacturers? I don't know...
--adam

"Kent W. England [MVP]" > wrote in message
...
> XP is rather more finicky about memory than previous versions of
> Windows. Pull the 128 MB memory chip out and see if it runs better.
> There are many reports of problems with mismatched memory. Otherwise,
> it's a driver, but you said it persists when you rollback to the install
> date, so I think it's memory.
>
> --
> Kent W. England, Microsoft MVP for Windows
>
>
>
> "Adam Steiner" > wrote in message
> news:f4c50bb95ec2e64d576827b8ea4d7c0c@TeraNews...
> > Hi,
> >
> >
> >
> > I have a Sceptre SoundX 69002 (Dell Inspiron 5000e/Compal NW32, etc)
> that
> > had Microsoft ME on it. I've recently tried putting Windows XP SP1 on
> > it.with rather terrible results.
> >
> >
> >
> > Initially, the computer ran well. However, after the second time I
> turned
> > it on and off, it began crashing with various errors such as
> > PAGE_FAULT_IN_NONPAGED_AREA and SESSION3_INITIALIZATION_FAILED.
> >
> >
> >
> > I managed to do a System Restore to the beginning, when Windows was
> freshly
> > installed, only to have the same thing occur. I now receive the
> > PAGE_FAULT_IN_NONPAGED_AREA error every time the machine is turned on,
> > always immediately after the Microsoft Windows login screen for XP
> appears.
> > I tried 2 256MB chips and a 128MB chip (all three are PC100 and come
> from
> > two different manufacturers), singly and in all combinations, in each
> slot.
> > Same error, so I've pretty much ruled the RAM out (besides they all
> worked
> > fine under other versions of Windows).
> >
> >
> >
> > I went to the MS website for error information. The second parameter
> is
> > always 0x00000000 (meaning a read operation). The following is the
> > information I received for the first (memory address accessed) and
> third
> > (referencing address) on the errors:
> >
> >
> >
> > 0xC97C0000, 0X8056AAA4
> >
> > 0XC9680000, 0X8056AAA4
> >
> > 0xC96C0000, 0X8056AAA4
> >
> > 0xC9840000, 0X8056AAA4
> >
> > As you can see, the first parameter is always in a relatively narrow
> region
> > of memory, regardless of the RAM chip used. The third parameter is
> always
> > the same. I must admit that I do recall seeing the first parameter
> > beginning with a 0xF at times.
> >
> >
> >
> > Any recommendations? Is there a way I can figure out what part of the
> > memory belongs to both the referencing and referenced locations? Can
> I turn
> > them off so that they aren't used (if they are bad). Perhaps they
> refer to
> > a system file that needs to be replaced?
> >
> >
> >
> > Thoughts, ideas?
> >
> >
> >
> > Thanks in advance,
> >
> >
> >
> > Adam
> >
> >
>

[Kent W. England [MVP]]

Nah, not the memory. Thanks for trying. ...

--
Kent W. England, Microsoft MVP for Windows



"Adam Steiner" > wrote in message
news:55f586555959826407a5195f54a79a4c@TeraNews...
> I've tried it with the single 128, both 256's (one at a time and
together).
> That the error for parameter three stays the same makes me assume it
is not
> the RAM causing the problem...three bad chips? From different
> manufacturers? I don't know...
> --adam
>
> "Kent W. England [MVP]" > wrote in message
> ...
> > XP is rather more finicky about memory than previous versions of
> > Windows. Pull the 128 MB memory chip out and see if it runs better.
> > There are many reports of problems with mismatched memory.
Otherwise,
> > it's a driver, but you said it persists when you rollback to the
install
> > date, so I think it's memory.

[Adam Steiner]

any other suggestions? does Windows have a utility (or is there an
independant program) that will tell me what the address corresponds to?

thanks
"Kent W. England [MVP]" > wrote in message
...
> Nah, not the memory. Thanks for trying. ...
>
> --
> Kent W. England, Microsoft MVP for Windows
>
>
>
> "Adam Steiner" > wrote in message
> news:55f586555959826407a5195f54a79a4c@TeraNews...
> > I've tried it with the single 128, both 256's (one at a time and
> together).
> > That the error for parameter three stays the same makes me assume it
> is not
> > the RAM causing the problem...three bad chips? From different
> > manufacturers? I don't know...
> > --adam
> >
> > "Kent W. England [MVP]" > wrote in message
> > ...
> > > XP is rather more finicky about memory than previous versions of
> > > Windows. Pull the 128 MB memory chip out and see if it runs better.
> > > There are many reports of problems with mismatched memory.
> Otherwise,
> > > it's a driver, but you said it persists when you rollback to the
> install
> > > date, so I think it's memory.
>

[Kent W. England [MVP]]

I once read a note about a tedious process to figure out what .dll was
using what memory, but these errors always turned out to be memory
timing or bad drivers.

Undo the last driver install you did.

--
Kent W. England, Microsoft MVP for Windows



"Adam Steiner" > wrote in message
news:b6193d68b377dc7bd3b92bc9e045fc37@TeraNews...
> any other suggestions? does Windows have a utility (or is there an
> independant program) that will tell me what the address corresponds
to?
>
> thanks
> "Kent W. England [MVP]" > wrote in message
> ...
> > Nah, not the memory. Thanks for trying. ...
> >
> >
> > "Adam Steiner" > wrote in message
> > news:55f586555959826407a5195f54a79a4c@TeraNews...
> > > I've tried it with the single 128, both 256's (one at a time and
> > together).
> > > That the error for parameter three stays the same makes me assume
it
> > is not
> > > the RAM causing the problem...three bad chips? From different
> > > manufacturers? I don't know...