Possible RAM failure cuasing random BSoD?

  • Thread starter Thread starter Fuzzy
  • Start date Start date
F

Fuzzy

I see I have bad RAM somewhere (there are 4 512mb modules arranged in 2 pairs
). Windows Memory Diagnostic shows details of address that fails
but not which module its in? Am I reading the mapping correctly that
0x00001000-0x00002000 is slot 1, 0x00030000-0x0009f000 is slot 2,
0x000100000-0x00400000 is slot 3 and 0x004de000-0x7fe480000 is slot 4?

I'm a bit confused why the mapping jumps between 0x00400000 and
0x004de000?

How do I figure out which modules need replacing all the test says is that
some address failed and it floats off the screen?

so far all the addresses appear to be in the > 0x00400000 range which I'm
guessing is the module in slot 4?
 
Mapping from logical/physical/slot can get very confusing. I suggest that
you remove two of the modules and run test. If then you know the other pair
is bad, or this pair is bad. Change which ones you are using till you get a
pair that work. Then swap in one at a time from the bad pair till you know
which module is the bad one.

Don't be too surprised if you end up with all of them working. One of the
modules may have dirty contacts, be poorly seated in its socket etc. and
moving things around might fix the problem.

Michael
Vista Home premium


"Fuzzy" <Fuzzy@discussions.microsoft.com> wrote in message
news:CE60F262-7D55-48F2-8EE8-32E656867CEF@microsoft.com...
> I see I have bad RAM somewhere (there are 4 512mb modules arranged in 2
> pairs
> ). Windows Memory Diagnostic shows details of address that fails
> but not which module its in? Am I reading the mapping correctly that
> 0x00001000-0x00002000 is slot 1, 0x00030000-0x0009f000 is slot 2,
> 0x000100000-0x00400000 is slot 3 and 0x004de000-0x7fe480000 is slot 4?
>
> I'm a bit confused why the mapping jumps between 0x00400000 and
> 0x004de000?
>
> How do I figure out which modules need replacing all the test says is that
> some address failed and it floats off the screen?
>
> so far all the addresses appear to be in the > 0x00400000 range which I'm
> guessing is the module in slot 4?
>
>
 
looks one moduleswas consistant failing, returning it for exchange
under its warrenty.

:)

hopefully that will stop the BSoD random stops

thanks again :)

"Michael Walraven" wrote:

> Mapping from logical/physical/slot can get very confusing. I suggest that
> you remove two of the modules and run test. If then you know the other pair
> is bad, or this pair is bad. Change which ones you are using till you get a
> pair that work. Then swap in one at a time from the bad pair till you know
> which module is the bad one.
>
> Don't be too surprised if you end up with all of them working. One of the
> modules may have dirty contacts, be poorly seated in its socket etc. and
> moving things around might fix the problem.
>
> Michael
> Vista Home premium
>
>
> "Fuzzy" <Fuzzy@discussions.microsoft.com> wrote in message
> news:CE60F262-7D55-48F2-8EE8-32E656867CEF@microsoft.com...
> > I see I have bad RAM somewhere (there are 4 512mb modules arranged in 2
> > pairs
> > ). Windows Memory Diagnostic shows details of address that fails
> > but not which module its in? Am I reading the mapping correctly that
> > 0x00001000-0x00002000 is slot 1, 0x00030000-0x0009f000 is slot 2,
> > 0x000100000-0x00400000 is slot 3 and 0x004de000-0x7fe480000 is slot 4?
> >
> > I'm a bit confused why the mapping jumps between 0x00400000 and
> > 0x004de000?
> >
> > How do I figure out which modules need replacing all the test says is that
> > some address failed and it floats off the screen?
> >
> > so far all the addresses appear to be in the > 0x00400000 range which I'm
> > guessing is the module in slot 4?
> >
> >
 
Back
Top