One of the ram modules in my computer has sudden developed a fault that
prevents Vista from booting up without causing a bluescreen. If I run the
memory diagnostic it says there is an error, and then the subsequent reboot
will let Vista boot up. And this is now the only procedure that lets Vista
boot up. It blue screens on boot up even in Safe Mode. Well, anyway, once I
have run the memory diagnostic tool and gotten Vista to fully boot, it
appears to work just fine. What I would like to know, is if there is a way to
force Vista to boot up without me having to first run the memory diagnostic
tool? I will be replacing the module that is faulty but until then, it would
be nice to have a temporary workaround. Perhaps even something I could use to
tell the OS to simply not use the 16 MB region where the fault exists. Anyone?

Hi,

Sorry, no method exists to map around bad memory. Remove the stick as it is
unreleliable even if you are able to get the system booted.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org

"Dfrey1969" <Dfrey1969@discussions.microsoft.com> wrote in message
news:6EDA98AD-9362-4080-86C8-2E1CD20BBF77@microsoft.com...
> One of the ram modules in my computer has sudden developed a fault that
> prevents Vista from booting up without causing a bluescreen. If I run the
> memory diagnostic it says there is an error, and then the subsequent
> reboot
> will let Vista boot up. And this is now the only procedure that lets Vista
> boot up. It blue screens on boot up even in Safe Mode. Well, anyway, once
> I
> have run the memory diagnostic tool and gotten Vista to fully boot, it
> appears to work just fine. What I would like to know, is if there is a way
> to
> force Vista to boot up without me having to first run the memory
> diagnostic
> tool? I will be replacing the module that is faulty but until then, it
> would
> be nice to have a temporary workaround. Perhaps even something I could use
> to
> tell the OS to simply not use the 16 MB region where the fault exists.
> Anyone?
>