memory counting using memtest86
CASTalk.com Forum Index CASTalk.com
Discussion of DSP, FPGA, storage and embedded system.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web castalk.com
memory counting using memtest86

 
Post new topic   Reply to topic    CASTalk.com Forum Index -> Embedded System
Author Message
JuanPedro
Guest





Posted: Wed Dec 08, 2004 5:38 am    Post subject: memory counting using memtest86 Reply with quote

memtest86 (v 3.2) shows me that my laptop has a bad RAM address, at
0b5d9270. It also writes, beside the failing address, what appears to
be a memory count, in this case it writes 181.5MB.
However, when I convert 0b5d9270 from hex to dec, it corresponds to
190.7MB. This is almost 10MB difference and I'd like to find out which
one is correct because if I have to cut off anything about the lowest
bad address, I'll lose 10MB more if the first number is correct. Any
idea of what's going on? I've searched the net for similar situations
and all I could find is that my case is not unique, i.e. other people
report addresses that are always higher than the MB count that
memtest86 gives. To my surprise, nobody asks why ...
Back to top
Ed Beroset
Guest





Posted: Wed Dec 08, 2004 5:55 am    Post subject: Re: memory counting using memtest86 Reply with quote

JuanPedro wrote:
Quote:
memtest86 (v 3.2) shows me that my laptop has a bad RAM address, at
0b5d9270. It also writes, beside the failing address, what appears to
be a memory count, in this case it writes 181.5MB.
However, when I convert 0b5d9270 from hex to dec, it corresponds to
190.7MB. This is almost 10MB difference and I'd like to find out which
one is correct because if I have to cut off anything about the lowest
bad address, I'll lose 10MB more if the first number is correct. Any
idea of what's going on? I've searched the net for similar situations
and all I could find is that my case is not unique, i.e. other people
report addresses that are always higher than the MB count that
memtest86 gives. To my surprise, nobody asks why ...

It's an old question. The answer is that you're using different units.
181 MiB = 190 MB. See http://physics.nist.gov/cuu/Units/binary.html

Ed
Back to top
 
Post new topic   Reply to topic    CASTalk.com Forum Index -> Embedded System All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Electronics Powered by phpBB