Thinkpads Forum

I ran Microsoft's Windows Memory Diagnostic the other day on my Thinkpad 770x as part of some troubleshooting.
http://oca.microsoft.com/en/windiag.asp
It flagged memory location 0009f930 on just about every test. I removed the extra 64MB SODIMM and ran the test again. Got the same result. I was ready to tear apart the 770X and swap the "internal" RAM but ran out of time. I was setting up my other Thinkpad 770 (9549-1AU) today in preparation for the 770X tear down and decide to run the same test. It failed with the same memory location. I then ran the Thinkpad setup memory diagnostic test on both 770's and found no failures.

Anybody heard of this problem with Windows Memory Diagnostic and Thinkpads? Is this just another example of Microsoft's quality software? (I have used this on other PCs with good reults.)

Rodger

Same experience here.

Windows XP Home SP1 running on two 770ED machines.
Both have 288MB (max) memory. The memory was purchased from IBM.
Standard. 2x128MB + 32MB soldered on motherboard. 66MHz.

Microsoft Windows Memory Diagnostic (WMD). both machines report a horrifying number of errors.

IBM ThinkPad built-in diagnostics. No problems with memory or any other component. Both machines.

MemTest86+ v1.20. No problems with memory. Both machines.

MemTest-86 v3.0. No problems with memory. Both machines.

SimTester DocMemory v2.0. No problems with memory. Both machines.

So, what's up with WMD anyway?

Lilla

I have had the same problem using Windows Memory Diagnostic on both my IBM 600 and my IBM 600x. And it was the same memory address on both of them, 0009f930. At first I ran the test on my 600X which has 576mb of ram and when it found the error I took my ram out and it still found the same error. So I thought that it was in the first 64mb which is on the motherboard, but I have used other memory test programs and they didn't find anything. And what are the chances of running the test on two different laptops and it finding an error in the same memory address on both??? That's what made me think something is definitely wrong with Microsoft's Memory Diagnostic utility.

Same here....just a software prob.....every others test fine....

Greg St.L