adding system memory

  • Thread starter Thread starter x
  • Start date Start date
X

x

Guest
I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
replaced the first pair with a matched pair of 1gig modules which gave a
total of 2.5 gig. The system boots fine in safe mode but not in standard
mode. I went through the boot from CD repair process (following the recover
console option) but no change. Is there a boot.ini setting or other update
required so the system will run under WinXP 64 bit standard mode?
 
RE: adding system memory

x:
What happens exactly when you do not boot in safe mode.
Do you have an error message, lockup, sudden reboot, etc.?
Please explain this situation in greater detail.

Have you tried removing the 2x256MB modules and booting with only the 2x1Gig
sticks?

Carlos
"x" wrote:

> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
> replaced the first pair with a matched pair of 1gig modules which gave a
> total of 2.5 gig. The system boots fine in safe mode but not in standard
> mode. I went through the boot from CD repair process (following the recover
> console option) but no change. Is there a boot.ini setting or other update
> required so the system will run under WinXP 64 bit standard mode?
>
>
>
 
Re: adding system memory

No, since it boots in safe mode using both modules pairs I've put removing
the smaller set for last.

The Window startup screen appears then after a while goes blank and then
after a while the monitor says no video then nothing.

I've tried the recovery console but found nothing there related to fixing a
memory or configuration or setup problem.

I've tried reinstalling the OS by using repair (after bypassing the recovery
console option)

I've tried changing the boot.ini settings.

Someone has suggested the following...

1. Use MSconfig to:
a. hide or disable all services (I'm currently here.)
b. disable all startups
2. Reboot
3. If system will reboot in standard mode then show or reenable each service
and startup, one at a time and goto step 2, else step 4.
4. If still won't reboot in standard mode then remove smaller pair and goto
step 1 else step 5.
5. ...?




"Carlos" <Carlos@discussions.microsoft.com> wrote in message
news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> x:
> What happens exactly when you do not boot in safe mode.
> Do you have an error message, lockup, sudden reboot, etc.?
> Please explain this situation in greater detail.
>
> Have you tried removing the 2x256MB modules and booting with only the
> 2x1Gig
> sticks?
>
> Carlos
> "x" wrote:
>
>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
>> replaced the first pair with a matched pair of 1gig modules which gave a
>> total of 2.5 gig. The system boots fine in safe mode but not in standard
>> mode. I went through the boot from CD repair process (following the
>> recover
>> console option) but no change. Is there a boot.ini setting or other
>> update
>> required so the system will run under WinXP 64 bit standard mode?
>>
>>
>>
 
Re: adding system memory

X:
If you remove the 2x256 pair, then try to boot, you verify that the
2x1024 pair is compatible with your motherboard. There is a chance that the
new ram isn't compatible or 1 stick has errors. If you're running XP x64
there is a good chance that ram that works with XP x86 may have errors since
the addressing is different. I haven't noticed this problem with Vista
between x86 and x64 but I switched to all premium ram since I found this
problem running XP x64. Have a great day.

--
Dennis Pack
XP x64 SP2, Vista Enterprise x64
Office Professional Plus 2007

"x" <pce3@ij.net> wrote in message
news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
> No, since it boots in safe mode using both modules pairs I've put removing
> the smaller set for last.
>
> The Window startup screen appears then after a while goes blank and then
> after a while the monitor says no video then nothing.
>
> I've tried the recovery console but found nothing there related to fixing
> a memory or configuration or setup problem.
>
> I've tried reinstalling the OS by using repair (after bypassing the
> recovery console option)
>
> I've tried changing the boot.ini settings.
>
> Someone has suggested the following...
>
> 1. Use MSconfig to:
> a. hide or disable all services (I'm currently here.)
> b. disable all startups
> 2. Reboot
> 3. If system will reboot in standard mode then show or reenable each
> service and startup, one at a time and goto step 2, else step 4.
> 4. If still won't reboot in standard mode then remove smaller pair and
> goto step 1 else step 5.
> 5. ...?
>
>
>
>
> "Carlos" <Carlos@discussions.microsoft.com> wrote in message
> news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
>> x:
>> What happens exactly when you do not boot in safe mode.
>> Do you have an error message, lockup, sudden reboot, etc.?
>> Please explain this situation in greater detail.
>>
>> Have you tried removing the 2x256MB modules and booting with only the
>> 2x1Gig
>> sticks?
>>
>> Carlos
>> "x" wrote:
>>
>>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
>>> replaced the first pair with a matched pair of 1gig modules which gave a
>>> total of 2.5 gig. The system boots fine in safe mode but not in standard
>>> mode. I went through the boot from CD repair process (following the
>>> recover
>>> console option) but no change. Is there a boot.ini setting or other
>>> update
>>> required so the system will run under WinXP 64 bit standard mode?
>>>
>>>
>>>
>
>
 
Re: adding system memory

Hello,
You may be able to do this with boot.ini switches rather than removing the
memory. Just tell the system the amount of memory you want to use for
example:

/maxmem= number
This switch specifies the amount of RAM, in bytes, that Windows can use.
For example, if you want Windows to use less than 64 MB of memory, use the
/maxmem=64 switch.

In your case:
/maxmem=2048
.
833721 Available switch options for the Windows XP and the Windows Server
2003 Boot.ini files
http://support.microsoft.com/default.aspx?scid=kb;EN-US;833721



Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> From: "Dennis Pack" <dennispack@hotmail.nospam.com>
|> References: <uMNJLAdAIHA.1184@TK2MSFTNGP04.phx.gbl>
<8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com>
<#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl>
|> Subject: Re: adding system memory
|> Date: Fri, 28 Sep 2007 13:26:48 -0400
|> Lines: 1
|> Message-ID: <E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com>
|> MIME-Version: 1.0
|> Content-Type: text/plain;
|> format=flowed;
|> charset="iso-8859-1";
|> reply-type=response
|> Content-Transfer-Encoding: 7bit
|> X-Priority: 3
|> X-MSMail-Priority: Normal
|> Importance: Normal
|> X-Newsreader: Microsoft Windows Live Mail 12.0.1184
|> X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1184
|> X-MS-CommunityGroup-PostID: {E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A}
|> X-MS-CommunityGroup-ThreadID: B1FAD2C5-1FC6-4EB2-A236-4C2CCFFB0445
|> X-MS-CommunityGroup-ParentID: 153384E6-94B3-4622-B361-3386321EFFC5
|> Newsgroups: microsoft.public.windows.64bit.general
|> Path: TK2MSFTNGHUB02.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.64bit.general:9981
|> NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
|> X-Tomcat-NG: microsoft.public.windows.64bit.general
|>
|> X:
|> If you remove the 2x256 pair, then try to boot, you verify that the
|> 2x1024 pair is compatible with your motherboard. There is a chance that
the
|> new ram isn't compatible or 1 stick has errors. If you're running XP x64
|> there is a good chance that ram that works with XP x86 may have errors
since
|> the addressing is different. I haven't noticed this problem with Vista
|> between x86 and x64 but I switched to all premium ram since I found this
|> problem running XP x64. Have a great day.
|>
|> --
|> Dennis Pack
|> XP x64 SP2, Vista Enterprise x64
|> Office Professional Plus 2007
|>
|> "x" <pce3@ij.net> wrote in message
|> news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
|> > No, since it boots in safe mode using both modules pairs I've put
removing
|> > the smaller set for last.
|> >
|> > The Window startup screen appears then after a while goes blank and
then
|> > after a while the monitor says no video then nothing.
|> >
|> > I've tried the recovery console but found nothing there related to
fixing
|> > a memory or configuration or setup problem.
|> >
|> > I've tried reinstalling the OS by using repair (after bypassing the
|> > recovery console option)
|> >
|> > I've tried changing the boot.ini settings.
|> >
|> > Someone has suggested the following...
|> >
|> > 1. Use MSconfig to:
|> > a. hide or disable all services (I'm currently here.)
|> > b. disable all startups
|> > 2. Reboot
|> > 3. If system will reboot in standard mode then show or reenable each
|> > service and startup, one at a time and goto step 2, else step 4.
|> > 4. If still won't reboot in standard mode then remove smaller pair and
|> > goto step 1 else step 5.
|> > 5. ...?
|> >
|> >
|> >
|> >
|> > "Carlos" <Carlos@discussions.microsoft.com> wrote in message
|> > news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
|> >> x:
|> >> What happens exactly when you do not boot in safe mode.
|> >> Do you have an error message, lockup, sudden reboot, etc.?
|> >> Please explain this situation in greater detail.
|> >>
|> >> Have you tried removing the 2x256MB modules and booting with only the
|> >> 2x1Gig
|> >> sticks?
|> >>
|> >> Carlos
|> >> "x" wrote:
|> >>
|> >>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots
and
|> >>> replaced the first pair with a matched pair of 1gig modules which
gave a
|> >>> total of 2.5 gig. The system boots fine in safe mode but not in
standard
|> >>> mode. I went through the boot from CD repair process (following the
|> >>> recover
|> >>> console option) but no change. Is there a boot.ini setting or other
|> >>> update
|> >>> required so the system will run under WinXP 64 bit standard mode?
|> >>>
|> >>>
|> >>>
|> >
|> >
|>
 
Re: adding system memory

Darrell:
But wouldn't be that a "logical" memory size that could be composed of a mix
of 512 MB from the 2x256 sticks + 1.5 GB from the 2x1GB sticks?
Carlos

""Darrell Gorter[MSFT]"" wrote:

> Hello,
> You may be able to do this with boot.ini switches rather than removing the
> memory. Just tell the system the amount of memory you want to use for
> example:
>
> /maxmem= number
> This switch specifies the amount of RAM, in bytes, that Windows can use.
> For example, if you want Windows to use less than 64 MB of memory, use the
> /maxmem=64 switch.
>
> In your case:
> /maxmem=2048
> .
> 833721 Available switch options for the Windows XP and the Windows Server
> 2003 Boot.ini files
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;833721
>
>
>
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> |> From: "Dennis Pack" <dennispack@hotmail.nospam.com>
> |> References: <uMNJLAdAIHA.1184@TK2MSFTNGP04.phx.gbl>
> <8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com>
> <#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl>
> |> Subject: Re: adding system memory
> |> Date: Fri, 28 Sep 2007 13:26:48 -0400
> |> Lines: 1
> |> Message-ID: <E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com>
> |> MIME-Version: 1.0
> |> Content-Type: text/plain;
> |> format=flowed;
> |> charset="iso-8859-1";
> |> reply-type=response
> |> Content-Transfer-Encoding: 7bit
> |> X-Priority: 3
> |> X-MSMail-Priority: Normal
> |> Importance: Normal
> |> X-Newsreader: Microsoft Windows Live Mail 12.0.1184
> |> X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1184
> |> X-MS-CommunityGroup-PostID: {E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A}
> |> X-MS-CommunityGroup-ThreadID: B1FAD2C5-1FC6-4EB2-A236-4C2CCFFB0445
> |> X-MS-CommunityGroup-ParentID: 153384E6-94B3-4622-B361-3386321EFFC5
> |> Newsgroups: microsoft.public.windows.64bit.general
> |> Path: TK2MSFTNGHUB02.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.64bit.general:9981
> |> NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> |> X-Tomcat-NG: microsoft.public.windows.64bit.general
> |>
> |> X:
> |> If you remove the 2x256 pair, then try to boot, you verify that the
> |> 2x1024 pair is compatible with your motherboard. There is a chance that
> the
> |> new ram isn't compatible or 1 stick has errors. If you're running XP x64
> |> there is a good chance that ram that works with XP x86 may have errors
> since
> |> the addressing is different. I haven't noticed this problem with Vista
> |> between x86 and x64 but I switched to all premium ram since I found this
> |> problem running XP x64. Have a great day.
> |>
> |> --
> |> Dennis Pack
> |> XP x64 SP2, Vista Enterprise x64
> |> Office Professional Plus 2007
> |>
> |> "x" <pce3@ij.net> wrote in message
> |> news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
> |> > No, since it boots in safe mode using both modules pairs I've put
> removing
> |> > the smaller set for last.
> |> >
> |> > The Window startup screen appears then after a while goes blank and
> then
> |> > after a while the monitor says no video then nothing.
> |> >
> |> > I've tried the recovery console but found nothing there related to
> fixing
> |> > a memory or configuration or setup problem.
> |> >
> |> > I've tried reinstalling the OS by using repair (after bypassing the
> |> > recovery console option)
> |> >
> |> > I've tried changing the boot.ini settings.
> |> >
> |> > Someone has suggested the following...
> |> >
> |> > 1. Use MSconfig to:
> |> > a. hide or disable all services (I'm currently here.)
> |> > b. disable all startups
> |> > 2. Reboot
> |> > 3. If system will reboot in standard mode then show or reenable each
> |> > service and startup, one at a time and goto step 2, else step 4.
> |> > 4. If still won't reboot in standard mode then remove smaller pair and
> |> > goto step 1 else step 5.
> |> > 5. ...?
> |> >
> |> >
> |> >
> |> >
> |> > "Carlos" <Carlos@discussions.microsoft.com> wrote in message
> |> > news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> |> >> x:
> |> >> What happens exactly when you do not boot in safe mode.
> |> >> Do you have an error message, lockup, sudden reboot, etc.?
> |> >> Please explain this situation in greater detail.
> |> >>
> |> >> Have you tried removing the 2x256MB modules and booting with only the
> |> >> 2x1Gig
> |> >> sticks?
> |> >>
> |> >> Carlos
> |> >> "x" wrote:
> |> >>
> |> >>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots
> and
> |> >>> replaced the first pair with a matched pair of 1gig modules which
> gave a
> |> >>> total of 2.5 gig. The system boots fine in safe mode but not in
> standard
> |> >>> mode. I went through the boot from CD repair process (following the
> |> >>> recover
> |> >>> console option) but no change. Is there a boot.ini setting or other
> |> >>> update
> |> >>> required so the system will run under WinXP 64 bit standard mode?
> |> >>>
> |> >>>
> |> >>>
> |> >
> |> >
> |>
>
>
 
Re: adding system memory

I do not understand your thinking. How can the issue be motherboard related
if Windows XP x64 boots in safe mode with the 2x1024 and the 2x256
installed?


"Dennis Pack" <dennispack@hotmail.nospam.com> wrote in message
news:E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com...
> X:
> If you remove the 2x256 pair, then try to boot, you verify that the
> 2x1024 pair is compatible with your motherboard. There is a chance that
> the new ram isn't compatible or 1 stick has errors. If you're running XP
> x64 there is a good chance that ram that works with XP x86 may have errors
> since the addressing is different. I haven't noticed this problem with
> Vista between x86 and x64 but I switched to all premium ram since I found
> this problem running XP x64. Have a great day.
>
> --
> Dennis Pack
> XP x64 SP2, Vista Enterprise x64
> Office Professional Plus 2007
>
> "x" <pce3@ij.net> wrote in message
> news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
>> No, since it boots in safe mode using both modules pairs I've put
>> removing the smaller set for last.
>>
>> The Window startup screen appears then after a while goes blank and then
>> after a while the monitor says no video then nothing.
>>
>> I've tried the recovery console but found nothing there related to fixing
>> a memory or configuration or setup problem.
>>
>> I've tried reinstalling the OS by using repair (after bypassing the
>> recovery console option)
>>
>> I've tried changing the boot.ini settings.
>>
>> Someone has suggested the following...
>>
>> 1. Use MSconfig to:
>> a. hide or disable all services (I'm currently here.)
>> b. disable all startups
>> 2. Reboot
>> 3. If system will reboot in standard mode then show or reenable each
>> service and startup, one at a time and goto step 2, else step 4.
>> 4. If still won't reboot in standard mode then remove smaller pair and
>> goto step 1 else step 5.
>> 5. ...?
>>
>>
>>
>>
>> "Carlos" <Carlos@discussions.microsoft.com> wrote in message
>> news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
>>> x:
>>> What happens exactly when you do not boot in safe mode.
>>> Do you have an error message, lockup, sudden reboot, etc.?
>>> Please explain this situation in greater detail.
>>>
>>> Have you tried removing the 2x256MB modules and booting with only the
>>> 2x1Gig
>>> sticks?
>>>
>>> Carlos
>>> "x" wrote:
>>>
>>>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots
>>>> and
>>>> replaced the first pair with a matched pair of 1gig modules which gave
>>>> a
>>>> total of 2.5 gig. The system boots fine in safe mode but not in
>>>> standard
>>>> mode. I went through the boot from CD repair process (following the
>>>> recover
>>>> console option) but no change. Is there a boot.ini setting or other
>>>> update
>>>> required so the system will run under WinXP 64 bit standard mode?
>>>>
>>>>
>>>>
>>
>>
 
Re: adding system memory

Reducing the amount of memory using /maxmem did not solve the problem but I
have yet to try several other switches that may eliminate the problem.
Thanks.

""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
news:ha4I9uhAIHA.5204@TK2MSFTNGHUB02.phx.gbl...
> Hello,
> You may be able to do this with boot.ini switches rather than removing the
> memory. Just tell the system the amount of memory you want to use for
> example:
>
> /maxmem= number
> This switch specifies the amount of RAM, in bytes, that Windows can use.
> For example, if you want Windows to use less than 64 MB of memory, use the
> /maxmem=64 switch.
>
> In your case:
> /maxmem=2048
>
> 833721 Available switch options for the Windows XP and the Windows Server
> 2003 Boot.ini files
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;833721
>
>
>
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> |> From: "Dennis Pack" <dennispack@hotmail.nospam.com>
> |> References: <uMNJLAdAIHA.1184@TK2MSFTNGP04.phx.gbl>
> <8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com>
> <#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl>
> |> Subject: Re: adding system memory
> |> Date: Fri, 28 Sep 2007 13:26:48 -0400
> |> Lines: 1
> |> Message-ID: <E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com>
> |> MIME-Version: 1.0
> |> Content-Type: text/plain;
> |> format=flowed;
> |> charset="iso-8859-1";
> |> reply-type=response
> |> Content-Transfer-Encoding: 7bit
> |> X-Priority: 3
> |> X-MSMail-Priority: Normal
> |> Importance: Normal
> |> X-Newsreader: Microsoft Windows Live Mail 12.0.1184
> |> X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1184
> |> X-MS-CommunityGroup-PostID: {E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A}
> |> X-MS-CommunityGroup-ThreadID: B1FAD2C5-1FC6-4EB2-A236-4C2CCFFB0445
> |> X-MS-CommunityGroup-ParentID: 153384E6-94B3-4622-B361-3386321EFFC5
> |> Newsgroups: microsoft.public.windows.64bit.general
> |> Path: TK2MSFTNGHUB02.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.64bit.general:9981
> |> NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> |> X-Tomcat-NG: microsoft.public.windows.64bit.general
> |>
> |> X:
> |> If you remove the 2x256 pair, then try to boot, you verify that the
> |> 2x1024 pair is compatible with your motherboard. There is a chance that
> the
> |> new ram isn't compatible or 1 stick has errors. If you're running XP
> x64
> |> there is a good chance that ram that works with XP x86 may have errors
> since
> |> the addressing is different. I haven't noticed this problem with Vista
> |> between x86 and x64 but I switched to all premium ram since I found
> this
> |> problem running XP x64. Have a great day.
> |>
> |> --
> |> Dennis Pack
> |> XP x64 SP2, Vista Enterprise x64
> |> Office Professional Plus 2007
> |>
> |> "x" <pce3@ij.net> wrote in message
> |> news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
> |> > No, since it boots in safe mode using both modules pairs I've put
> removing
> |> > the smaller set for last.
> |> >
> |> > The Window startup screen appears then after a while goes blank and
> then
> |> > after a while the monitor says no video then nothing.
> |> >
> |> > I've tried the recovery console but found nothing there related to
> fixing
> |> > a memory or configuration or setup problem.
> |> >
> |> > I've tried reinstalling the OS by using repair (after bypassing the
> |> > recovery console option)
> |> >
> |> > I've tried changing the boot.ini settings.
> |> >
> |> > Someone has suggested the following...
> |> >
> |> > 1. Use MSconfig to:
> |> > a. hide or disable all services (I'm currently here.)
> |> > b. disable all startups
> |> > 2. Reboot
> |> > 3. If system will reboot in standard mode then show or reenable each
> |> > service and startup, one at a time and goto step 2, else step 4.
> |> > 4. If still won't reboot in standard mode then remove smaller pair
> and
> |> > goto step 1 else step 5.
> |> > 5. ...?
> |> >
> |> >
> |> >
> |> >
> |> > "Carlos" <Carlos@discussions.microsoft.com> wrote in message
> |> > news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> |> >> x:
> |> >> What happens exactly when you do not boot in safe mode.
> |> >> Do you have an error message, lockup, sudden reboot, etc.?
> |> >> Please explain this situation in greater detail.
> |> >>
> |> >> Have you tried removing the 2x256MB modules and booting with only
> the
> |> >> 2x1Gig
> |> >> sticks?
> |> >>
> |> >> Carlos
> |> >> "x" wrote:
> |> >>
> |> >>> I was running 1gig using 2 pairs of 256Mb matched modules in 4
> slots
> and
> |> >>> replaced the first pair with a matched pair of 1gig modules which
> gave a
> |> >>> total of 2.5 gig. The system boots fine in safe mode but not in
> standard
> |> >>> mode. I went through the boot from CD repair process (following the
> |> >>> recover
> |> >>> console option) but no change. Is there a boot.ini setting or other
> |> >>> update
> |> >>> required so the system will run under WinXP 64 bit standard mode?
> |> >>>
> |> >>>
> |> >>>
> |> >
> |> >
> |>
>
 
Re: adding system memory

x:
Just give Dennis a shot.
Call it a "hunch", which I happen to share.
Carlos

"x" wrote:

> I do not understand your thinking. How can the issue be motherboard related
> if Windows XP x64 boots in safe mode with the 2x1024 and the 2x256
> installed?
>
>
> "Dennis Pack" <dennispack@hotmail.nospam.com> wrote in message
> news:E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com...
> > X:
> > If you remove the 2x256 pair, then try to boot, you verify that the
> > 2x1024 pair is compatible with your motherboard. There is a chance that
> > the new ram isn't compatible or 1 stick has errors. If you're running XP
> > x64 there is a good chance that ram that works with XP x86 may have errors
> > since the addressing is different. I haven't noticed this problem with
> > Vista between x86 and x64 but I switched to all premium ram since I found
> > this problem running XP x64. Have a great day.
> >
> > --
> > Dennis Pack
> > XP x64 SP2, Vista Enterprise x64
> > Office Professional Plus 2007
> >
> > "x" <pce3@ij.net> wrote in message
> > news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
> >> No, since it boots in safe mode using both modules pairs I've put
> >> removing the smaller set for last.
> >>
> >> The Window startup screen appears then after a while goes blank and then
> >> after a while the monitor says no video then nothing.
> >>
> >> I've tried the recovery console but found nothing there related to fixing
> >> a memory or configuration or setup problem.
> >>
> >> I've tried reinstalling the OS by using repair (after bypassing the
> >> recovery console option)
> >>
> >> I've tried changing the boot.ini settings.
> >>
> >> Someone has suggested the following...
> >>
> >> 1. Use MSconfig to:
> >> a. hide or disable all services (I'm currently here.)
> >> b. disable all startups
> >> 2. Reboot
> >> 3. If system will reboot in standard mode then show or reenable each
> >> service and startup, one at a time and goto step 2, else step 4.
> >> 4. If still won't reboot in standard mode then remove smaller pair and
> >> goto step 1 else step 5.
> >> 5. ...?
> >>
> >>
> >>
> >>
> >> "Carlos" <Carlos@discussions.microsoft.com> wrote in message
> >> news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> >>> x:
> >>> What happens exactly when you do not boot in safe mode.
> >>> Do you have an error message, lockup, sudden reboot, etc.?
> >>> Please explain this situation in greater detail.
> >>>
> >>> Have you tried removing the 2x256MB modules and booting with only the
> >>> 2x1Gig
> >>> sticks?
> >>>
> >>> Carlos
> >>> "x" wrote:
> >>>
> >>>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots
> >>>> and
> >>>> replaced the first pair with a matched pair of 1gig modules which gave
> >>>> a
> >>>> total of 2.5 gig. The system boots fine in safe mode but not in
> >>>> standard
> >>>> mode. I went through the boot from CD repair process (following the
> >>>> recover
> >>>> console option) but no change. Is there a boot.ini setting or other
> >>>> update
> >>>> required so the system will run under WinXP 64 bit standard mode?
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>
>
 
Re: adding system memory

Okay, found it.

Carlos and "Dennis Pack"

Your concern about it being a motherboard turns out maybe to be a bios
configuration issue regarding memory hole remapping which I have enabled.

""Darrell Gorter[MSFT]""

Your /maxmem suggestion and link to boot.ini switch descriptions resulted in
my trying /burnmemory instead of /maxmem which failed. I have yet to explore
in detail whether remapping or /burnmemory has allowed standard mode to
boot. I also added /pcilock since it lets the bios handle hardware
configuration so I have yet to explore whether this is the remedy or not

In any case it is now resolved with one or all of these changes.


"x" <pce3@ij.net> wrote in message
news:uMNJLAdAIHA.1184@TK2MSFTNGP04.phx.gbl...
>I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
>replaced the first pair with a matched pair of 1gig modules which gave a
>total of 2.5 gig. The system boots fine in safe mode but not in standard
>mode. I went through the boot from CD repair process (following the recover
>console option) but no change. Is there a boot.ini setting or other update
>required so the system will run under WinXP 64 bit standard mode?
>
 
Re: adding system memory

Removal of 2x256mb modules or using /burnmemory=576 will allow Windows XP
x64 to boot in standard mode. Windows XP x64 will run in safe mode except
when all services and all startups are disabled.

Consequently the problem is not the motherboard or the bios but an issue
with Windows XP x64.



"Carlos" <Carlos@discussions.microsoft.com> wrote in message
news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> x:
> What happens exactly when you do not boot in safe mode.
> Do you have an error message, lockup, sudden reboot, etc.?
> Please explain this situation in greater detail.
>
> Have you tried removing the 2x256MB modules and booting with only the
> 2x1Gig
> sticks?
>
> Carlos
> "x" wrote:
>
>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
>> replaced the first pair with a matched pair of 1gig modules which gave a
>> total of 2.5 gig. The system boots fine in safe mode but not in standard
>> mode. I went through the boot from CD repair process (following the
>> recover
>> console option) but no change. Is there a boot.ini setting or other
>> update
>> required so the system will run under WinXP 64 bit standard mode?
>>
>>
>>
 
Re: adding system memory

/burnmemory=576 or greater (and maybe a little less but greater than at
least 513) is the only requirement for Windows XP x64 to boot in standard
mode. My conclusion therefore is that the problem, whatever it is, belongs
to Windows XP x64 alone.


""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
news:ha4I9uhAIHA.5204@TK2MSFTNGHUB02.phx.gbl...
> Hello,
> You may be able to do this with boot.ini switches rather than removing the
> memory. Just tell the system the amount of memory you want to use for
> example:
>
> /maxmem= number
> This switch specifies the amount of RAM, in bytes, that Windows can use.
> For example, if you want Windows to use less than 64 MB of memory, use the
> /maxmem=64 switch.
>
> In your case:
> /maxmem=2048
>
> 833721 Available switch options for the Windows XP and the Windows Server
> 2003 Boot.ini files
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;833721
>
>
>
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> |> From: "Dennis Pack" <dennispack@hotmail.nospam.com>
> |> References: <uMNJLAdAIHA.1184@TK2MSFTNGP04.phx.gbl>
> <8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com>
> <#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl>
> |> Subject: Re: adding system memory
> |> Date: Fri, 28 Sep 2007 13:26:48 -0400
> |> Lines: 1
> |> Message-ID: <E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A@microsoft.com>
> |> MIME-Version: 1.0
> |> Content-Type: text/plain;
> |> format=flowed;
> |> charset="iso-8859-1";
> |> reply-type=response
> |> Content-Transfer-Encoding: 7bit
> |> X-Priority: 3
> |> X-MSMail-Priority: Normal
> |> Importance: Normal
> |> X-Newsreader: Microsoft Windows Live Mail 12.0.1184
> |> X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1184
> |> X-MS-CommunityGroup-PostID: {E5575C9C-C1DA-4E2C-8815-D7979BAFEE0A}
> |> X-MS-CommunityGroup-ThreadID: B1FAD2C5-1FC6-4EB2-A236-4C2CCFFB0445
> |> X-MS-CommunityGroup-ParentID: 153384E6-94B3-4622-B361-3386321EFFC5
> |> Newsgroups: microsoft.public.windows.64bit.general
> |> Path: TK2MSFTNGHUB02.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.64bit.general:9981
> |> NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
> |> X-Tomcat-NG: microsoft.public.windows.64bit.general
> |>
> |> X:
> |> If you remove the 2x256 pair, then try to boot, you verify that the
> |> 2x1024 pair is compatible with your motherboard. There is a chance that
> the
> |> new ram isn't compatible or 1 stick has errors. If you're running XP
> x64
> |> there is a good chance that ram that works with XP x86 may have errors
> since
> |> the addressing is different. I haven't noticed this problem with Vista
> |> between x86 and x64 but I switched to all premium ram since I found
> this
> |> problem running XP x64. Have a great day.
> |>
> |> --
> |> Dennis Pack
> |> XP x64 SP2, Vista Enterprise x64
> |> Office Professional Plus 2007
> |>
> |> "x" <pce3@ij.net> wrote in message
> |> news:#nkcN4eAIHA.5960@TK2MSFTNGP05.phx.gbl...
> |> > No, since it boots in safe mode using both modules pairs I've put
> removing
> |> > the smaller set for last.
> |> >
> |> > The Window startup screen appears then after a while goes blank and
> then
> |> > after a while the monitor says no video then nothing.
> |> >
> |> > I've tried the recovery console but found nothing there related to
> fixing
> |> > a memory or configuration or setup problem.
> |> >
> |> > I've tried reinstalling the OS by using repair (after bypassing the
> |> > recovery console option)
> |> >
> |> > I've tried changing the boot.ini settings.
> |> >
> |> > Someone has suggested the following...
> |> >
> |> > 1. Use MSconfig to:
> |> > a. hide or disable all services (I'm currently here.)
> |> > b. disable all startups
> |> > 2. Reboot
> |> > 3. If system will reboot in standard mode then show or reenable each
> |> > service and startup, one at a time and goto step 2, else step 4.
> |> > 4. If still won't reboot in standard mode then remove smaller pair
> and
> |> > goto step 1 else step 5.
> |> > 5. ...?
> |> >
> |> >
> |> >
> |> >
> |> > "Carlos" <Carlos@discussions.microsoft.com> wrote in message
> |> > news:8CF7A3CB-C96D-4287-A28A-0AE22130AAF8@microsoft.com...
> |> >> x:
> |> >> What happens exactly when you do not boot in safe mode.
> |> >> Do you have an error message, lockup, sudden reboot, etc.?
> |> >> Please explain this situation in greater detail.
> |> >>
> |> >> Have you tried removing the 2x256MB modules and booting with only
> the
> |> >> 2x1Gig
> |> >> sticks?
> |> >>
> |> >> Carlos
> |> >> "x" wrote:
> |> >>
> |> >>> I was running 1gig using 2 pairs of 256Mb matched modules in 4
> slots
> and
> |> >>> replaced the first pair with a matched pair of 1gig modules which
> gave a
> |> >>> total of 2.5 gig. The system boots fine in safe mode but not in
> standard
> |> >>> mode. I went through the boot from CD repair process (following the
> |> >>> recover
> |> >>> console option) but no change. Is there a boot.ini setting or other
> |> >>> update
> |> >>> required so the system will run under WinXP 64 bit standard mode?
> |> >>>
> |> >>>
> |> >>>
> |> >
> |> >
> |>
>
 
Re: adding system memory

Resolution of operating system deficiency by means of hardware extrication.

> x:
> Just give Dennis a shot.
> Call it a "hunch", which I happen to share.
> Carlos
 
Re: adding system memory

The important question is the new 1 gb modules the exact
same brand and specification as the 256 mb modules? Any
difference in timing and other memory specs such as speed
will cause the system to not function correctly. The memory
in ALL four slots need to be the same brand and speed of memory.


x wrote:
> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
> replaced the first pair with a matched pair of 1gig modules which gave a
> total of 2.5 gig. The system boots fine in safe mode but not in standard
> mode. I went through the boot from CD repair process (following the recover
> console option) but no change. Is there a boot.ini setting or other update
> required so the system will run under WinXP 64 bit standard mode?
>
>
 
Re: adding system memory

Exact same brand, speed and timings. Memory size is only difference.

"Theo" <theo@discussions.microsoft.com> wrote in message
news:eum0G2pAIHA.3940@TK2MSFTNGP05.phx.gbl...
> The important question is the new 1 gb modules the exact same brand and
> specification as the 256 mb modules? Any difference in timing and other
> memory specs such as speed will cause the system to not function
> correctly. The memory in ALL four slots need to be the same brand and
> speed of memory.
>
>
> x wrote:
>> I was running 1gig using 2 pairs of 256Mb matched modules in 4 slots and
>> replaced the first pair with a matched pair of 1gig modules which gave a
>> total of 2.5 gig. The system boots fine in safe mode but not in standard
>> mode. I went through the boot from CD repair process (following the
>> recover console option) but no change. Is there a boot.ini setting or
>> other update required so the system will run under WinXP 64 bit standard
>> mode?
 
Back
Top