Excluding RAM address(es)?

  • Thread starter Thread starter Ronny D'Hoore
  • Start date Start date
R

Ronny D'Hoore

I had sporadic BSoD's like 0A in ntoskrnl.exe, or even
spontaneous reboots, which made me suspect a problem with
the RAM. I ran MemTest86 (www.memtest86.com) and it
consistently reports that one specific address is bad.
Now, do I have to throw away the whole memory stick and
buy a new one (I hope not), or can I just somehow
somewhere exclude that memory address/segment just as one
could in the old DOS?

I run Win2K Prof.

(I've searched the web far and wide about this, but only
found solutions for Linux.....)

Thanks.

Ronny
 
Ronny D'Hoore said:
I had sporadic BSoD's like 0A in ntoskrnl.exe, or even
spontaneous reboots, which made me suspect a problem with
the RAM. I ran MemTest86 (www.memtest86.com) and it
consistently reports that one specific address is bad.
Now, do I have to throw away the whole memory stick and
buy a new one (I hope not), or can I just somehow
somewhere exclude that memory address/segment just as one
could in the old DOS?

I run Win2K Prof.

(I've searched the web far and wide about this, but only
found solutions for Linux.....)

Thanks.

Ronny
Click to expand...

Single-bit errors are remapped and won't cause a problem,
but BSODs and random reboots indicate multiple-bit errors
in the dimm. Replace it.

Rick
 
But is there any way to exclude a segment of memory? The
problem is always with address 00013D89F20. I will
probably replace it at one point, but rather not just now.

Ronny
 
Back
Top