XP Pro with 4 GB RAM keeps asking for activation...

.... And then fails due to an error that reads something like "Cannot read
license information." Then it locks up solid. It started doing this more than
two weeks after the RAM on this system was upgraded from 2 GB to 4 GB -
without issue at the time.

The machine's owner is understandably concerned - they cannot log on to this
system at all. It either hangs or refuses to boot. Remember, it booted fine
for over two weeks of use, and no other hardware or software changes have
been made to the system.

Any ideas?

How to Perform a Windows XP Repair Install
http://www.michaelstevenstech.com/XPrepairinstall.htm

--
Carey Frisch
Microsoft MVP
Windows - Shell/User
Microsoft Community Newsgroups
news://msnews.microsoft.com/

-------------------------------------------------------------------------------------------

"Paul in Vancouver" wrote:

| ... And then fails due to an error that reads something like "Cannot read
| license information." Then it locks up solid. It started doing this more than
| two weeks after the RAM on this system was upgraded from 2 GB to 4 GB -
| without issue at the time.
|
| The machine's owner is understandably concerned - they cannot log on to this
| system at all. It either hangs or refuses to boot. Remember, it booted fine
| for over two weeks of use, and no other hardware or software changes have
| been made to the system.
|
| Any ideas?

Hmm, but why would I want to repair an installation that works fine when I
back the amount of RAM off to 3 GB? While it might be bad RAM, both sets of
modules work fine on their own. Maybe this system just can't deal with it at
the chipset level?

I was just looking for comments and advice especially from anyone else who
might have configured this much RAM on an XP Pro workstation.

"Carey Frisch [MVP]" wrote:

> How to Perform a Windows XP Repair Install
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> --
> Carey Frisch
> Microsoft MVP
> Windows - Shell/User
> Microsoft Community Newsgroups
> news://msnews.microsoft.com/
>
> -------------------------------------------------------------------------------------------
>
> "Paul in Vancouver" wrote:
>
> | ... And then fails due to an error that reads something like "Cannot read
> | license information." Then it locks up solid. It started doing this more than
> | two weeks after the RAM on this system was upgraded from 2 GB to 4 GB -
> | without issue at the time.
> |
> | The machine's owner is understandably concerned - they cannot log on to this
> | system at all. It either hangs or refuses to boot. Remember, it booted fine
> | for over two weeks of use, and no other hardware or software changes have
> | been made to the system.
> |
> | Any ideas?
>

Paul in Vancouver wrote:
> Hmm, but why would I want to repair an installation that works fine when I
> back the amount of RAM off to 3 GB? While it might be bad RAM, both sets of
> modules work fine on their own. Maybe this system just can't deal with it at
> the chipset level?
>
> I was just looking for comments and advice especially from anyone else who
> might have configured this much RAM on an XP Pro workstation.
>
> "Carey Frisch [MVP]" wrote:
>
> > How to Perform a Windows XP Repair Install
> > http://www.michaelstevenstech.com/XPrepairinstall.htm
> >
> > --
> > Carey Frisch
> > Microsoft MVP
> > Windows - Shell/User
> > Microsoft Community Newsgroups
> > news://msnews.microsoft.com/

May be you need to look at the motherboard manual to see what sort and
how much memory the MB can handle.

You could always test the RAM useing Memtest-86 (
http://www.memtest86.com/ )
> >
> > -------------------------------------------------------------------------------------------
> >
> > "Paul in Vancouver" wrote:
> >
> > | ... And then fails due to an error that reads something like "Cannot read
> > | license information." Then it locks up solid. It started doing this more than
> > | two weeks after the RAM on this system was upgraded from 2 GB to 4 GB -
> > | without issue at the time.
> > |
> > | The machine's owner is understandably concerned - they cannot log on to this
> > | system at all. It either hangs or refuses to boot. Remember, it booted fine
> > | for over two weeks of use, and no other hardware or software changes have
> > | been made to the system.
> > |
> > | Any ideas?
> >

You may have a point. The manual does indicate support for 1 GB modules, but
it just might not like all four slots full.

Thanks for the MEMTEST link. I will definitely test the RAM.

"GreenieLeBrun" wrote:

>
> Paul in Vancouver wrote:
> > Hmm, but why would I want to repair an installation that works fine when I
> > back the amount of RAM off to 3 GB? While it might be bad RAM, both sets of
> > modules work fine on their own. Maybe this system just can't deal with it at
> > the chipset level?
> >
> > I was just looking for comments and advice especially from anyone else who
> > might have configured this much RAM on an XP Pro workstation.
> >
> > "Carey Frisch [MVP]" wrote:
> >
> > > How to Perform a Windows XP Repair Install
> > > http://www.michaelstevenstech.com/XPrepairinstall.htm
> > >
> > > --
> > > Carey Frisch
> > > Microsoft MVP
> > > Windows - Shell/User
> > > Microsoft Community Newsgroups
> > > news://msnews.microsoft.com/
>
> May be you need to look at the motherboard manual to see what sort and
> how much memory the MB can handle.
>
> You could always test the RAM useing Memtest-86 (
> http://www.memtest86.com/ )
> > >
> > > -------------------------------------------------------------------------------------------
> > >
> > > "Paul in Vancouver" wrote:
> > >
> > > | ... And then fails due to an error that reads something like "Cannot read
> > > | license information." Then it locks up solid. It started doing this more than
> > > | two weeks after the RAM on this system was upgraded from 2 GB to 4 GB -
> > > | without issue at the time.
> > > |
> > > | The machine's owner is understandably concerned - they cannot log on to this
> > > | system at all. It either hangs or refuses to boot. Remember, it booted fine
> > > | for over two weeks of use, and no other hardware or software changes have
> > > | been made to the system.
> > > |
> > > | Any ideas?
> > >
>
>