Added 512 MB RDRAM, won't boot

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
Windows XP home last week. Everything was great, but a little slow. I
decided
that I should add some RAM before it was discontinued. I purchased 2 sticks
of
RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in pair
per instructions on website. Machine starts Boot, then failed once after HP
screen and did a scandisk. Machine now gets to a screen to "run windows in
safe
mode, safe mode with command prompt, last good setup, etc." No matter which
one I pick, it always returns to that screen. If I pick safe mode with
command
prompt, I get a string of the following messages
[multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
"\system32\drivers\etc.", etc.,
etc.
I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
I removed the new memory and returned the unit to its original memory setup.
I
still have the same problem. I thought I was going to fix-it-up for a
couple more years....now I wish I followed the old "If it ain't broke don't
fix it"!
Any advice is most appreciated.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
news:18B942F2-96FC-48C6-AA07-AB90A96D1044@microsoft.com...
> Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
> Windows XP home last week. Everything was great, but a little slow. I
> decided
> that I should add some RAM before it was discontinued. I purchased 2
> sticks
> of
> RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in
> pair
> per instructions on website. Machine starts Boot, then failed once after
> HP
> screen and did a scandisk. Machine now gets to a screen to "run windows
> in
> safe
> mode, safe mode with command prompt, last good setup, etc." No matter
> which
> one I pick, it always returns to that screen. If I pick safe mode with
> command
> prompt, I get a string of the following messages
> [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
> items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
> "\system32\drivers\etc.", etc.,
> etc.
> I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
> I removed the new memory and returned the unit to its original memory
> setup.
> I
> still have the same problem. I thought I was going to fix-it-up for a
> couple more years....now I wish I followed the old "If it ain't broke
> don't
> fix it"!
> Any advice is most appreciated.

Remove old ram, install new ram and try again. If this works try it again
with the old and new ram installed. There are several possibilities and you
have to use the process of elimination to figure out which one has occurred.
Some of the possibilities are: new ram is defective or not compatible with
your motherboard., new ram and old ram are not compatible, ram not installed
properly (loose in socket, wrong socket, old ram got knocked loose),
motherboard or old ram got damaged installing new ram, etc., etc. Hope this
helped. Without further testing it's pretty hard to determine the exact
cause.

Kerry

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Hopeful" <Hopeful@discussions.microsoft.com> wrote:

>Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
>Windows XP home last week. Everything was great, but a little slow. I
>decided
>that I should add some RAM before it was discontinued. I purchased 2 sticks
>of
>RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in pair
>per instructions on website. Machine starts Boot, then failed once after HP
>screen and did a scandisk. Machine now gets to a screen to "run windows in
>safe
>mode, safe mode with command prompt, last good setup, etc."

The latest entry that is shown when booting to the Safe Mode usually
is the problem. Windows hangs when loading this driver/software.
Try booting to a command-prompt. If this works, see "How to Start
System Restore Tool From a Command Prompt in Windows XP"
(http://support.microsoft.com/?kbid=304449).

--
(tm)

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Actually, isn't the last one shown the last one that installed successfully?
Isn't it the one immediately "after" the displayed driver/service the one
that has stalled the system?

--
Regards,

Richard Urban

aka Crusty (-: Old B@stard

If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!


"Thorsten Matzner" <tmatzner@gmx.net> wrote in message
news:OupqsHxRFHA.1392@TK2MSFTNGP10.phx.gbl...
> "Hopeful" <Hopeful@discussions.microsoft.com> wrote:
>
>>Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
>>Windows XP home last week. Everything was great, but a little slow. I
>>decided
>>that I should add some RAM before it was discontinued. I purchased 2
>>sticks
>>of
>>RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in
>>pair
>>per instructions on website. Machine starts Boot, then failed once after
>>HP
>>screen and did a scandisk. Machine now gets to a screen to "run windows
>>in
>>safe
>>mode, safe mode with command prompt, last good setup, etc."
>
> The latest entry that is shown when booting to the Safe Mode usually
> is the problem. Windows hangs when loading this driver/software.
> Try booting to a command-prompt. If this works, see "How to Start
> System Restore Tool From a Command Prompt in Windows XP"
> (http://support.microsoft.com/?kbid=304449).
>
> --
> (tm)

 

[bar]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Given that you installed the memory and the system got through POST and BIOS
reported the new memory, it could be a reasonable assumption that it is
compatible with you motherboard.

Try restoring your hardware to its previous state [as it was without the new
RAM].
Reboot and see if Windows will load, as it should.
If it doesn't boot up troubleshoot the configuration, most likely you'll
need to boot to safe mode and restore to a date before you mucked around with
memory.
When it's working, power off and remove the old RAM and install the new.
Try booting up into Windows.
If it boots and get through POST, but Windows gives a BSOD, then check the
message description.

It is more than likely that the memory change has been so great that you
need to run a repair installation to reset the configuration.

Don't perform the repair installation without reviewing the opinions of
others here after you write up the description of the BSOD.


"Hopeful" wrote:

> Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
> Windows XP home last week. Everything was great, but a little slow. I
> decided
> that I should add some RAM before it was discontinued. I purchased 2 sticks
> of
> RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in pair
> per instructions on website. Machine starts Boot, then failed once after HP
> screen and did a scandisk. Machine now gets to a screen to "run windows in
> safe
> mode, safe mode with command prompt, last good setup, etc." No matter which
> one I pick, it always returns to that screen. If I pick safe mode with
> command
> prompt, I get a string of the following messages
> [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
> items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
> "\system32\drivers\etc.", etc.,
> etc.
> I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
> I removed the new memory and returned the unit to its original memory setup.
> I
> still have the same problem. I thought I was going to fix-it-up for a
> couple more years....now I wish I followed the old "If it ain't broke don't
> fix it"!
> Any advice is most appreciated.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Thanks for all the good advice to everyone. I have restored the system to
its original memory configuration and the same symptoms are there. I am
unable to read the BSOD....it flashes by too quickly. I only get the message
list from the "safe boot" screen (or whatever you call it....I have only had
XP active for a week or two, ME didn't have a screen like that except with an
emergency boot disk). Do you have a way to get the BSOD to stay on long
enough to actually read it?

ever grateful!

"BAR" wrote:

> Given that you installed the memory and the system got through POST and BIOS
> reported the new memory, it could be a reasonable assumption that it is
> compatible with you motherboard.
>
> Try restoring your hardware to its previous state [as it was without the new
> RAM].
> Reboot and see if Windows will load, as it should.
> If it doesn't boot up troubleshoot the configuration, most likely you'll
> need to boot to safe mode and restore to a date before you mucked around with
> memory.
> When it's working, power off and remove the old RAM and install the new.
> Try booting up into Windows.
> If it boots and get through POST, but Windows gives a BSOD, then check the
> message description.
>
> It is more than likely that the memory change has been so great that you
> need to run a repair installation to reset the configuration.
>
> Don't perform the repair installation without reviewing the opinions of
> others here after you write up the description of the BSOD.
>
>
> "Hopeful" wrote:
>
> > Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
> > Windows XP home last week. Everything was great, but a little slow. I
> > decided
> > that I should add some RAM before it was discontinued. I purchased 2 sticks
> > of
> > RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in pair
> > per instructions on website. Machine starts Boot, then failed once after HP
> > screen and did a scandisk. Machine now gets to a screen to "run windows in
> > safe
> > mode, safe mode with command prompt, last good setup, etc." No matter which
> > one I pick, it always returns to that screen. If I pick safe mode with
> > command
> > prompt, I get a string of the following messages
> > [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
> > items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
> > "\system32\drivers\etc.", etc.,
> > etc.
> > I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
> > I removed the new memory and returned the unit to its original memory setup.
> > I
> > still have the same problem. I thought I was going to fix-it-up for a
> > couple more years....now I wish I followed the old "If it ain't broke don't
> > fix it"!
> > Any advice is most appreciated.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

Thanks for the advice. I did try it with just the new. Same result. BIOS
recognizes it, but gets to the same screen. I did try it with just the
old...same result. Blew it out, etc.

I am hopeful that it isn't "bad memory" as you say, but fearful it might me
too.

"Kerry Brown" wrote:

> "Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
> news:18B942F2-96FC-48C6-AA07-AB90A96D1044@microsoft.com...
> > Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
> > Windows XP home last week. Everything was great, but a little slow. I
> > decided
> > that I should add some RAM before it was discontinued. I purchased 2
> > sticks
> > of
> > RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in
> > pair
> > per instructions on website. Machine starts Boot, then failed once after
> > HP
> > screen and did a scandisk. Machine now gets to a screen to "run windows
> > in
> > safe
> > mode, safe mode with command prompt, last good setup, etc." No matter
> > which
> > one I pick, it always returns to that screen. If I pick safe mode with
> > command
> > prompt, I get a string of the following messages
> > [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
> > items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
> > "\system32\drivers\etc.", etc.,
> > etc.
> > I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
> > I removed the new memory and returned the unit to its original memory
> > setup.
> > I
> > still have the same problem. I thought I was going to fix-it-up for a
> > couple more years....now I wish I followed the old "If it ain't broke
> > don't
> > fix it"!
> > Any advice is most appreciated.
>
> Remove old ram, install new ram and try again. If this works try it again
> with the old and new ram installed. There are several possibilities and you
> have to use the process of elimination to figure out which one has occurred.
> Some of the possibilities are: new ram is defective or not compatible with
> your motherboard., new ram and old ram are not compatible, ram not installed
> properly (loose in socket, wrong socket, old ram got knocked loose),
> motherboard or old ram got damaged installing new ram, etc., etc. Hope this
> helped. Without further testing it's pretty hard to determine the exact
> cause.
>
> Kerry
>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
news:2CC5817F-4212-4EC3-92A9-4C43C6673CB4@microsoft.com...
> Thanks for the advice. I did try it with just the new. Same result.
> BIOS
> recognizes it, but gets to the same screen. I did try it with just the
> old...same result. Blew it out, etc.
>
> I am hopeful that it isn't "bad memory" as you say, but fearful it might
> me
> too.
>

Another thng that often happens when changing ram is the hard drive cable
gets knocked loose in the socket. I have even seen the CPU somehow get moved
slightly and cause problems (usually Socket A Athlons). Check none of the
cables are loose. I would not check your CPU unless you are absolutely sure
of what you are doing. There is too much potential of causing even more
problems.

Kerry


> "Kerry Brown" wrote:
>
>> "Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
>> news:18B942F2-96FC-48C6-AA07-AB90A96D1044@microsoft.com...
>> > Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
>> > Windows XP home last week. Everything was great, but a little slow. I
>> > decided
>> > that I should add some RAM before it was discontinued. I purchased 2
>> > sticks
>> > of
>> > RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed
>> > in
>> > pair
>> > per instructions on website. Machine starts Boot, then failed once
>> > after
>> > HP
>> > screen and did a scandisk. Machine now gets to a screen to "run
>> > windows
>> > in
>> > safe
>> > mode, safe mode with command prompt, last good setup, etc." No matter
>> > which
>> > one I pick, it always returns to that screen. If I pick safe mode with
>> > command
>> > prompt, I get a string of the following messages
>> > [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where
>> > various
>> > items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
>> > "\system32\drivers\etc.", etc.,
>> > etc.
>> > I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
>> > I removed the new memory and returned the unit to its original memory
>> > setup.
>> > I
>> > still have the same problem. I thought I was going to fix-it-up for a
>> > couple more years....now I wish I followed the old "If it ain't broke
>> > don't
>> > fix it"!
>> > Any advice is most appreciated.
>>
>> Remove old ram, install new ram and try again. If this works try it again
>> with the old and new ram installed. There are several possibilities and
>> you
>> have to use the process of elimination to figure out which one has
>> occurred.
>> Some of the possibilities are: new ram is defective or not compatible
>> with
>> your motherboard., new ram and old ram are not compatible, ram not
>> installed
>> properly (loose in socket, wrong socket, old ram got knocked loose),
>> motherboard or old ram got damaged installing new ram, etc., etc. Hope
>> this
>> helped. Without further testing it's pretty hard to determine the exact
>> cause.
>>
>> Kerry
>>
>>
>>

 

[anna]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

>> "Hopeful" wrote:
>>
>> > Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
>> > Windows XP home last week. Everything was great, but a little slow. I
>> > decided
>> > that I should add some RAM before it was discontinued. I purchased 2
>> > sticks
>> > of
>> > RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed
>> > in pair
>> > per instructions on website. Machine starts Boot, then failed once
>> > after HP
>> > screen and did a scandisk. Machine now gets to a screen to "run
>> > windows in
>> > safe
>> > mode, safe mode with command prompt, last good setup, etc." No matter
>> > which
>> > one I pick, it always returns to that screen. If I pick safe mode with
>> > command
>> > prompt, I get a string of the following messages
>> > [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where
>> > various
>> > items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
>> > "\system32\drivers\etc.", etc.,
>> > etc.
>> > I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
>> > I removed the new memory and returned the unit to its original memory
>> > setup.
>> > I
>> > still have the same problem. I thought I was going to fix-it-up for a
>> > couple more years....now I wish I followed the old "If it ain't broke
>> > don't
>> > fix it"!
>> > Any advice is most appreciated.


> "BAR" wrote:
>
>> Given that you installed the memory and the system got through POST and
>> BIOS
>> reported the new memory, it could be a reasonable assumption that it is
>> compatible with you motherboard.
>>
>> Try restoring your hardware to its previous state [as it was without the
>> new
>> RAM].
>> Reboot and see if Windows will load, as it should.
>> If it doesn't boot up troubleshoot the configuration, most likely you'll
>> need to boot to safe mode and restore to a date before you mucked around
>> with
>> memory.
>> When it's working, power off and remove the old RAM and install the new.
>> Try booting up into Windows.
>> If it boots and get through POST, but Windows gives a BSOD, then check
>> the
>> message description.
>>
>> It is more than likely that the memory change has been so great that you
>> need to run a repair installation to reset the configuration.
>>
>> Don't perform the repair installation without reviewing the opinions of
>> others here after you write up the description of the BSOD.


"Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
news:7A952D58-74F5-473B-92D2-5CE9F189F635@microsoft.com...
> Thanks for all the good advice to everyone. I have restored the system to
> its original memory configuration and the same symptoms are there. I am
> unable to read the BSOD....it flashes by too quickly. I only get the
> message
> list from the "safe boot" screen (or whatever you call it....I have only
> had
> XP active for a week or two, ME didn't have a screen like that except with
> an
> emergency boot disk). Do you have a way to get the BSOD to stay on long
> enough to actually read it?
>
> ever grateful!


Hopeful...
Although one can't be certain about this at this point, it doesn't sound
like a problem involving your RDRAM. Have you tried a Repair install of XP
as BAR suggested?
Anna

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Anna" <myname@myisp.net> wrote in message
news:edxDmP6RFHA.3444@tk2msftngp13.phx.gbl...
> "Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
> news:7A952D58-74F5-473B-92D2-5CE9F189F635@microsoft.com...
>> Thanks for all the good advice to everyone. I have restored the system
>> to
>> its original memory configuration and the same symptoms are there. I am
>> unable to read the BSOD....it flashes by too quickly. I only get the
>> message
>> list from the "safe boot" screen (or whatever you call it....I have only
>> had
>> XP active for a week or two, ME didn't have a screen like that except
>> with an
>> emergency boot disk). Do you have a way to get the BSOD to stay on long
>> enough to actually read it?
>>
>> ever grateful!
>
>
> Hopeful...
> Although one can't be certain about this at this point, it doesn't sound
> like a problem involving your RDRAM. Have you tried a Repair install of XP
> as BAR suggested?
> Anna
>

I think a repair install would be premature at this point. It quit working
immediately after a hardware change. It was working fine before the change.
If there is a hardware problem trying a repair install may cause even more
file corruption. If there is no data that would be lost I would try it. If
there is data that isn't backed up I would find the hardware problem first.

Kerry

 

[anna]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

>> "Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
>> news:7A952D58-74F5-473B-92D2-5CE9F189F635@microsoft.com...
>>> Thanks for all the good advice to everyone. I have restored the system
>>> to
>>> its original memory configuration and the same symptoms are there. I am
>>> unable to read the BSOD....it flashes by too quickly. I only get the
>>> message
>>> list from the "safe boot" screen (or whatever you call it....I have only
>>> had
>>> XP active for a week or two, ME didn't have a screen like that except
>>> with an
>>> emergency boot disk). Do you have a way to get the BSOD to stay on long
>>> enough to actually read it?
>>>
>>> ever grateful!


> "Anna" <myname@myisp.net> wrote in message
> news:edxDmP6RFHA.3444@tk2msftngp13.phx.gbl...

>> Hopeful...
>> Although one can't be certain about this at this point, it doesn't sound
>> like a problem involving your RDRAM. Have you tried a Repair install of
>> XP as BAR suggested?
>> Anna


"Kerry Brown" <kerry@kdbNOSPAMsystems.c*o*m> wrote in message
news:uS9Paz7RFHA.648@TK2MSFTNGP14.phx.gbl...
> I think a repair install would be premature at this point. It quit working
> immediately after a hardware change. It was working fine before the
> change. If there is a hardware problem trying a repair install may cause
> even more file corruption. If there is no data that would be lost I would
> try it. If there is data that isn't backed up I would find the hardware
> problem first.
>
> Kerry


Kerry:
You're absolutely correct that before a Repair install is undertaken, any
critical data should first be backed up. It is *always* prudent to do so and
I should have mentioned that in my previous response. But having said that,
I still think that a Repair install is relevant at this point. Naturally I
may be wrong but I don't believe this is a hardware issue - memory or
otherwise.

As to your comment that "a repair install may cause even more file
corruption", all I can say is that I have undertaken or participated in
scores of XP Repair installs on a large variety of systems and I have never
encountered a *single* instance where the Repair install resulted in
additional file corruption that could be traced to a failed Repair install.
Anything is possible, of course, so neither I, nor anyone else can say that
it can *never* happen. There are no guarantees in this business.
Anna

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

"Anna" <myname@myisp.net> wrote in message
news:uIxaSfBSFHA.3088@TK2MSFTNGP15.phx.gbl...
>>> "Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
>>> news:7A952D58-74F5-473B-92D2-5CE9F189F635@microsoft.com...
>>>> Thanks for all the good advice to everyone. I have restored the system
>>>> to
>>>> its original memory configuration and the same symptoms are there. I
>>>> am
>>>> unable to read the BSOD....it flashes by too quickly. I only get the
>>>> message
>>>> list from the "safe boot" screen (or whatever you call it....I have
>>>> only had
>>>> XP active for a week or two, ME didn't have a screen like that except
>>>> with an
>>>> emergency boot disk). Do you have a way to get the BSOD to stay on
>>>> long
>>>> enough to actually read it?
>>>>
>>>> ever grateful!
>
>
>> "Anna" <myname@myisp.net> wrote in message
>> news:edxDmP6RFHA.3444@tk2msftngp13.phx.gbl...
>
>>> Hopeful...
>>> Although one can't be certain about this at this point, it doesn't sound
>>> like a problem involving your RDRAM. Have you tried a Repair install of
>>> XP as BAR suggested?
>>> Anna
>
>
> "Kerry Brown" <kerry@kdbNOSPAMsystems.c*o*m> wrote in message
> news:uS9Paz7RFHA.648@TK2MSFTNGP14.phx.gbl...
>> I think a repair install would be premature at this point. It quit
>> working immediately after a hardware change. It was working fine before
>> the change. If there is a hardware problem trying a repair install may
>> cause even more file corruption. If there is no data that would be lost I
>> would try it. If there is data that isn't backed up I would find the
>> hardware problem first.
>>
>> Kerry
>
>
> Kerry:
> You're absolutely correct that before a Repair install is undertaken, any
> critical data should first be backed up. It is *always* prudent to do so
> and I should have mentioned that in my previous response. But having said
> that, I still think that a Repair install is relevant at this point.
> Naturally I may be wrong but I don't believe this is a hardware issue -
> memory or otherwise.
>
> As to your comment that "a repair install may cause even more file
> corruption", all I can say is that I have undertaken or participated in
> scores of XP Repair installs on a large variety of systems and I have
> never encountered a *single* instance where the Repair install resulted in
> additional file corruption that could be traced to a failed Repair
> install. Anything is possible, of course, so neither I, nor anyone else
> can say that it can *never* happen. There are no guarantees in this
> business.
> Anna
>

I have seen several cases where hardware problems, mostly bad ram, has
caused a stop error during a repair install. If it happens at the wrong time
it may cause further problems with an XP install that really didn't have any
problems to start with because the original problem was hardware related. I
would make sure the hardware problem is solved before doing anything which
would cause changes to the file system.

Kerry

 

[Guest]

Archived from groups: microsoft.public.windowsxp.hardware (More info?)

May I add, I thought that really you should add memory in identical capacity
on some forms of chips. i.e. 128mb + 128mb or 512mb + 512mb to save any
heartache ?

John


"Hopeful" <Hopeful@discussions.microsoft.com> wrote in message
news:18B942F2-96FC-48C6-AA07-AB90A96D1044@microsoft.com...
> Running HP Pavillion P41.3 GHz. I upgraded from Windows ME to
> Windows XP home last week. Everything was great, but a little slow. I
> decided
> that I should add some RAM before it was discontinued. I purchased 2
> sticks
> of
> RDRAM (SyncMAX PN SM256R368A-653 PC600 256MB/8 Non-ECC). I installed in
> pair
> per instructions on website. Machine starts Boot, then failed once after
> HP
> screen and did a scandisk. Machine now gets to a screen to "run windows
> in
> safe
> mode, safe mode with command prompt, last good setup, etc." No matter
> which
> one I pick, it always returns to that screen. If I pick safe mode with
> command
> prompt, I get a string of the following messages
> [multi(0)disk(0)rdisk(0)partition(1)\winidows\various items]where various
> items = "\fonts\vgaoem.fom", "\apppatch\drvmain.sdb",
> "\system32\drivers\etc.", etc.,
> etc.
> I can see the (new - 512MB)(and the old - 128MB) in the BIOS setup.
> I removed the new memory and returned the unit to its original memory
> setup.
> I
> still have the same problem. I thought I was going to fix-it-up for a
> couple more years....now I wish I followed the old "If it ain't broke
> don't
> fix it"!
> Any advice is most appreciated.