Has anyone used Memtest86? And could lend some advice?

Fredrow

Active Member
Just like the title says....

Need some help on reading the data of memtest86. I know someone out here has used it before?? Jets, Im betting you have??

Just need some tips from people on the data Im reading. Was never to good at reading software data/programming, I still got a lot to learn
and seeing who has advice to drop into my brain??

Thanks!!
 

Xx Binno xX

New Member
Just like the title says....

Need some help on reading the data of memtest86. I know someone out here has used it before?? Jets, Im betting you have??

Just need some tips from people on the data Im reading. Was never to good at reading software data/programming, I still got a lot to learn
and seeing who has advice to drop into my brain??

Thanks!!
From what I am reading on the website its just a seems like a software that detects errors on the cpu, helps measure your cpu if overclocked. This sounds like a very interesting thing. I would be willing to learn about this man thanks a lot, I wish I could of helped you!!
 

Fredrow

Active Member
Do you know much about computer memory address at all? Like how to read them to figure stuff out?
 

Fredrow

Active Member
Can you give me an example?

Yeah I think I might be able to explain it, but just to warn you I might give you false information too...lol...

Like the memory address for my ATI Radeon graphics card is 0xFBC00000-0xFBCFFFFF

All of your programs, hardware and such are all ran through different address.

I was just tying to pick peoples brains before I start to get lost into my Google searches about it... Its funny when I start to do research on things through Google I always ended up loosing track of time because I get so focused on learning about different stuff....
 

Krier023

Useful Poster
I feel the same way. I google search and start looking around, then I find an answer to one of my other problems, and forget about the original problem I was trying to fix.

What does memtest run tests and give you back the addresses where your problems arise?
 

Fredrow

Active Member
You have to burn memtest86 ISO.file onto a CD then setup your PC (through BIOS) to boot from CD/DVD drive first.

memtest86 with scan your RAM, and then from there you can figure out which if any of your RAM is defective. Now it will not fix your RAM just lets you know which of your RAM is a fault....
 

PS3andCOD

Contributor
Or just try booting your PC with each stick of RAM? That's what I do. Takes a couple minutes but it's easy as pie.
 

HippieMagic

New Member
Or just try booting your PC with each stick of RAM? That's what I do. Takes a couple minutes but it's easy as pie.

That may not find the error. If he is running Memtest it is either because he is experiencing a BSOD when his PC tries to access a certain point on one of his sticks of RAM or he has just installed new RAM and wants to make sure there is nothing wrong with it. If he is just running it to run it... well that makes no sense.

RAM CAN be damaged and still allow you to work fine until it reaches the point in your ram that has the damage.
 
Last edited:

Fredrow

Active Member
That may not find the error. If he is running Memtest it is either because he is experiencing a BSOD when his PC tries to access a certain point on one of his sticks of RAM or he has just installed new RAM and wants to make sure there is nothing wrong with it. If he is just running it to run it... well that makes no sense.

RAM CAN be damaged and still allow you to work fine until it reaches the point in your ram that has the damage.

Great points Hippie......

To add onto what Hippie stated; I do know that some software and OS will skip over a bad sector in RAM so one could go a long time before even getting signs that he has a bad RAM stick. Another thing also that could be bad is the actual RAM socket on the motherboard..... That is one thing a lot of people never think about!
 

HippieMagic

New Member
A good idea when you first build a PC is to run a lot of tests like Memtest, Prime95, Futuremark tests... just all sorts of benchmarking and torture tests to make sure it is stable and that all of the parts are functioning properly. This is really so you can just take care of your RMAs right off the bat if needed. Now as to how to read memory locations... well... that is beyond me. I know 0x indicates a memory error and if it is consistent in that location it could point to bad RAM. The only way I know to test ram to find the bad stick is trial and error through using one at a time and running memtest on each. I recall my A+ certification exam touching on memory errors but not really to the extent of determining the exact location on a stick of ram. I am not even sure that the locations are consistent to be honest.
 

Fredrow

Active Member
A good idea when you first build a PC is to run a lot of tests like Memtest, Prime95, Futuremark tests... just all sorts of benchmarking and torture tests to make sure it is stable and that all of the parts are functioning properly. This is really so you can just take care of your RMAs right off the bat if needed. Now as to how to read memory locations... well... that is beyond me. I know 0x indicates a memory error and if it is consistent in that location it could point to bad RAM. The only way I know to test ram to find the bad stick is trial and error through using one at a time and running memtest on each. I recall my A+ certification exam touching on memory errors but not really to the extent of determining the exact location on a stick of ram. I am not even sure that the locations are consistent to be honest.

Yo its all good dude. I really only made this thread to see if anyone had cool time saving tips but I don't need that 'ish anymore.... I already discovered the bad RAM stick......
 
Top