Rember is a front-end GUI to the 'memtest' command line memory testing program. This application will allow the user to select the number of test loops, as well as the amount of memory to test. There is a 'Log' tab that will allow the user to monitor memory testing. The user can toggle a 'verbose' switch to limit the amount of output.The user can choose to quit Finder and other applications.
Defective memory can cause computers to malfunction, crash, and behave in a variety of ways which can sometimes baffle end users and computer technicians alike. Apple provides hardware
What's New
Version 0.3.7b: Release notes were unavailable when this listing was updated.
Thanks for updating the unique+good memory test app !
HINT: PPC User should first try 100MB (not all available ram) to see how much time your whole RAM (500M++) needs. On fast Intel Macs you get an speed from 20-35 Minutes for 2 GB RAM (=3 GB installed). PPC G4 will take > 30 Min for 500MB!!
0.3.4b Worked flawlessly on my G4.
Nice output and simple.
If you buy new RAM or used this is the utility to have installed to test
it. Don't waste time with RAM when you buy it, test it ASAP and get
your $'s worth. I've been fortunate to never have had defective RAM, and
testing it just confirms it. I'm happy.
The newest version of Rember (0.3.4b) includes a memtest executable that is more compatible with 64-bit Intel based machines. This should eliminate crashing and slow testing on Apple's newest hardware.
I am very grateful for Rember and Memtest, and only want to help improve them.
It would be very nice if the memory test would permit different ranges of memory to be tested sequentially (or by some other algorithm that covers the entire memory range). If this is already done, then, in the immortal words of SNL great Emily LaTella -- never mind!)
Thus before each test a different memory range would be allocated and locked in, which would slow things down a bit. A possible algorithm for 2 GB RAM, where (say) only 1.5 GB can be tested by Rember, would be to do #1-to-#1.5GB on the 1st pass, #1.5GB-to-#2GB and #1-to-#1GB on the 2nd pass, etc.
Does it tell you that your ram is bad by freezing up your mac and forcing you to do a hard shut down? Or is that it's way of telling you Rember/Memtest itself is bad?
When Rember found a bad stick of RAM, I guess the RAM was so bad that a kernel panic and crash resulted. But after I figured out which RAM was bad and removed it, my system was better. Rember was able to test the remaining RAM without crashing.
I downloaded Rember in order to help diagnose an on-going kernel crash problem. It definitely helped me!
Anonymousreviewed on 19 Aug 2005
doesn't like my B&W G3. "dyld: incompatible cpu-subtype"
Version 0.2.3b of Rember is compatible with the G3 processor. I would recommend using it. That version can be found at www.kelleycomputing.net/rember.
Anonymouscommented on 20 Aug 2005
You can dl the orig. memtest 411 and copy the g3 build into the same place in rember.
orig. 411 memtest has all builds, but have problems to use the G3 one.
This happen to the gui also.
With this way, memtest (with rember) works with the new memtest 411
Anonymouscommented on 20 Aug 2005
Forgoten:
DL Link for V411 (g3):
http://www.memtestosx.org/download2/
Its named pre1039, butt runs with tiger too.
I have posted a version of Rember that includes the alternative memtest executable (for systems lower than 10.3.9 and G3 based machines) on the Rember download page (http://www.kelleycomputing.net/rember).
Anonymousreviewed on 04 Mar 2005
useful when you get a kernel panic and dont want to wait through the hardware test on the OSX cd to confirm that it is bad ram.
running rember should be the first thing you do after installing new ram.
There is a limit in 10.3 and lower that only allow any one application to allocate 2 GB of RAM. Apple's memory testing utilities have the same problems. Tiger (Mac OS 10.4) should solve this issue, as it is a 64 bit operating system.
in the last 5 months, my iMac (i5, 3.6 GHz, 4x2 GB RAM) four times died, beeping like Apple describes in
http://support.apple.com/kb/HT2538
(3 successive tones, a 5-second pause, 3 successive tones -- RAM does not pass data integrity check)
First time I thought corrupt video/cut data were causing the crahs, but not for crash no. 3 and 4.
I let Rember do 8 loops of checking all my memory, with a result that no errors could be found.
Apple Hardware Tests also say that my hardware is okay.
Can you give me a hint how to try to find out what's causing these crashes?
I removed all the RAM and put it back using different slots. Maybe one module was loose??? Don't know...
I've got 8 GB of ram installed on a new 2011 i5 iMac but the test log shows that it's only checking 6331 MB. Is this normal? I've clicked the option to allocate all ram for testing. The pop-up window that comes up when you launch Rember shows that I have 4 x 2 GB sticks with green lights next to all of them.
Previous version and this newest version seem to be buggy. I no longer see my ram slots or visual info like it used to do before I updated to 10.5.8.
Something's broken.
Here is what I see instead - http://i29.tinypic.com/6yfedg.jpg
The Console log shows nothing useful.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetFrontProcess(): This call is deprecated and should not be called
Why does my CPU temp shoot over 125 C (according to iStat Pro and SMC Fan Control) when running the memory test? This can't be safe! I have a Macbook Pro running Leopard 10.5.4.
When processor activity is high, the temperature of the processor increases. This is normal behavior in all computer processors. If a cooling mechanism in your computer fails, the temperature increase may be problematic, but for most machines the increase in temperature should be harmless.
Please login or create a new MacUpdate Member account to use this feature
Watch Lists are available to MacUpdate Desktop Members Upgrade Now
Download and auto-install
using MacUpdate Desktop. Save
time moving folders and cleaning-up.
Rember is a front-end GUI to the 'memtest' command line memory testing program. This application will allow the user to select the number of test loops, as well as the amount of memory to test. There is a 'Log' tab that will allow the user to monitor memory testing. The user can toggle a 'verbose' switch to limit the amount of output.The user can choose to quit Finder and other applications.
Defective memory can cause computers to malfunction, crash, and behave in a variety of ways which can sometimes baffle end users and computer technicians alike. Apple provides hardware test CDs with most of their products, and there are some third-party utilties for Mac OS X which perform memory testing. In my experience, these tools have not always been able to quickly and efficiently diagnose memory problems. Rember has been designed to simplify the testing, and diagnosis of these problems.
This software is free, and is covered under the GNU GPL. Please read accompanying "COPYING" file for more info.
Features:
Easy to use testing console
Human-readable test report summarizes test results
+69
HINT: PPC User should first try 100MB (not all available ram) to see how much time your whole RAM (500M++) needs. On fast Intel Macs you get an speed from 20-35 Minutes for 2 GB RAM (=3 GB installed). PPC G4 will take > 30 Min for 500MB!!
+2
- MacBookPro 6,2 (i7 2.66GHz) took 53 min for 6713MB (all available; total 8GB).
Thanks for this app, very useful if you update memory imho.
+2
-30
MicG reviewed on 13 Sep 2009
Nice output and simple.
If you buy new RAM or used this is the utility to have installed to test
it. Don't waste time with RAM when you buy it, test it ASAP and get
your $'s worth. I've been fortunate to never have had defective RAM, and
testing it just confirms it. I'm happy.
+1
Racer27x reviewed on 03 Jan 2008
+1
It would be very nice if the memory test would permit different ranges of memory to be tested sequentially (or by some other algorithm that covers the entire memory range). If this is already done, then, in the immortal words of SNL great Emily LaTella -- never mind!)
Thus before each test a different memory range would be allocated and locked in, which would slow things down a bit. A possible algorithm for 2 GB RAM, where (say) only 1.5 GB can be tested by Rember, would be to do #1-to-#1.5GB on the 1st pass, #1.5GB-to-#2GB and #1-to-#1GB on the 2nd pass, etc.
+1
Machine type (ie. G4, G5, Intel)
Operating system version (ie. 10.3, 10.4)
Amount of installed memory
At what point is the program freezing? Does it freeze on launch? Does it freeze once you've started tests?
+1
+1
I downloaded Rember in order to help diagnose an on-going kernel crash problem. It definitely helped me!
Anonymous reviewed on 19 Aug 2005
orig. 411 memtest has all builds, but have problems to use the G3 one.
This happen to the gui also.
With this way, memtest (with rember) works with the new memtest 411
DL Link for V411 (g3):
http://www.memtestosx.org/download2/
Its named pre1039, butt runs with tiger too.
Anonymous reviewed on 04 Mar 2005
running rember should be the first thing you do after installing new ram.
+4
Cabbage reviewed on 06 Jan 2005
? for the dev: does this only test the first 2gb of memory?
Requested memory: 1988MB (2084569088 bytes)
Available memory: 1988MB (2085318656 bytes)
Allocated memory: 1988MB (2084569088 bytes)
I have a G5 with 6.5gb of memory I want to test.
in the last 5 months, my iMac (i5, 3.6 GHz, 4x2 GB RAM) four times died, beeping like Apple describes in
http://support.apple.com/kb/HT2538
(3 successive tones, a 5-second pause, 3 successive tones -- RAM does not pass data integrity check)
First time I thought corrupt video/cut data were causing the crahs, but not for crash no. 3 and 4.
I let Rember do 8 loops of checking all my memory, with a result that no errors could be found.
Apple Hardware Tests also say that my hardware is okay.
Can you give me a hint how to try to find out what's causing these crashes?
I removed all the RAM and put it back using different slots. Maybe one module was loose??? Don't know...
-1
-206
Something's broken.
Here is what I see instead - http://i29.tinypic.com/6yfedg.jpg
The Console log shows nothing useful.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
/Rember.app/Contents/MacOS/Rember[5539] CPSGetFrontProcess(): This call is deprecated and should not be called
+2
+49
No Error when I test less memory…
Is it a Bug or my memory ?