Memtest report, can you help reading it?

Question: When I run "Rember", It gives me an error message:

"Attempting memory lock... WARNING: Testing with unlocked memory may be slower and less reliable

ERROR: Memory lock failed - reason unknown."

What does this mean, and what should I do?

Answer: The error message is stating that the machine cannot "lock" the memory (which allows for faster and more precise testing).

http://kelleycomputing.net/support/rember/

Requested memory: 4531MB (4752113664 bytes)

Available memory: 4531MB (4752113664 bytes)

Allocated memory: 4531MB (4752113664 bytes) at local address 0x0000000001000000

Attempting memory lock... ERROR: Memory lock failed - reason unknown.

That's the in excess of 4 GB lid for 32 bit systems.

A benign error.

If you like, pull a pair of DIMMs and run again.

The error should not occur with less memory.

(Crucial claimed there's no 4200 available anymore)

If Crucial sold you memory slower than what you need (the report is actually true) then you have a problem.

ASD (Apple Service Disc) notes refer to issues in systems with memory that is slower than the system is rated for.

Slower than spec RAM could be the reason for the system/CPU hangs that you experience.

Crucial may not have the proper RAM, but OWC does:

http://eshop.macsales.com/item/Other%20World%20Computing/4200DDR2M4GP/

Also, I did a regular restart before running Memtest (via the Terminal), because when trying to start up as single-user (Command-S) I got a DOS-like screen that was not at all clear to me....

In Single User mode, all that you have to do is type a command and press Enter.

Type

/Applications/memtest/memtest all 3 -L

and press Return.

To boot into single-user mode, hold down the "Command" and "S" keys during startup. You will be automatically logged in as the user root with a minimal command line environment. The login directory for the root account is "/" which is the top-level directory of the boot volume. Assuming that the memtest folder resides in your Applications folder, a typical invocation of memtest would be the following:

> /Applications/memtest/memtest all 3 -L <RETURN> ( <RETURN> means press the Return key)

This would run three passes of the test suite, testing all available free memory. The "-L" switch instructs memtest to save the transcript of the run to a file named "memtest.log" within the working directory from which you invoked memtest

Read the instructions. It's all in there......

User Guide - Memtest OS X

Memtest is not an application, and it doesn't reside in the Application folder.

If it isn't an application, then what is it???

Where ever you put the Memtest Application. If it's on the Desktop, Type Desktop. If its in Downloads, Type Downloads.

but that doesn't mean my Mac is happy with the slower speed, right?

IF the RAM is, IN FACT, not PC4200 and is a slower, PC3200 DIMM, it isn't the right RAM and will cause issues, sometime, somewhere. I have a hard time believing that the machine actually runs.

hat upgrading from Tiger to Leopard made my Mac more sensitive and less stable because of it

Leopard is far more discerning regarding RAM.

Crucial claims they've sold many of thise w/o any issues. They're actually shipping me replacement RAM for free, same 3200

I don't buy it. PC5300, OK, but not slower. Many people got Crucial PC5300 and it works, but always misreports as PC3200.

What does the sticker on the side of the DIMM say?

For anyone reading (because RAM is important and misinformation and confusion is bad):

NEVER install RAM that is slower than spec'd RAM.

In the Dual Core G5, since DDR2 PC4200 DIMMs are harder to find, many people opt for DDR2 PC5300 DIMMs. That is likely fine, as the RAM will be backwards compatible to the slower 533 MHz controller of the G5.

Misreports ARE common with the faster RAM, however.

Do NOT install DDR2 PC3200 DIMMs as they are not rated beyond 400 MHz.

Power Mac G5: Memory Specifications and ... - Support - Apple

Jeez, now you will argue that a command line utility is not an application???!!!!

If you know everything, why do you ask?

You don't seem to believe anything that I tell you.

I'm tired......

Remember everyone here is a volunteer and NOT an Apple employee. They are only responding to you out of the kindness of their hearts. They don't have to do that.

In all of the postings I seen from Japamac so far I have never seen one of his with the wrong information. He is one of the best users I have seen on this forum.

Allan

to MY understanding it won't find Memtest there, since there's no such an application there (I searched for it)....

The application Memtest is where ever you put it AFTER you downloaded it.

Of course it's not in Applications UNLESS you put it there OR downloaded it TO Applications.

It's not part of the OS X install, is it?

, I think I've learned a few things about my RAM,

But you don't wish to learn, PROPERLY, how to BEST utilize the APPLICATION (YES, a command line tool IS an application).

Whatever.

You know better. Good luck with the CPU hangs.

Indeed! 🙂

in terminal, type

which memtest

On my Mac, the system replies with...

/usr/bin/memtest

This means that on my Mac it says memtest is in /usr/bin/memtest

if I were to boot in single user mode and run memtest, I would run it with the following command:

/usr/bin/memtest all 2

I have 16 GB of Centon RAM in a late 2011 MBP. I've had a few crashes and kernel panics so I reluctantly ran memtest. So far there are two errors so I guess I'll find the time to boot in single user mode and run it on all of my RAM. I know I'll have to swap back my factory 4 GB if I keep finding errors with memtest or getting the occasional kernel panic. BTW, behaving well for a period of time is not as important as loading up memory and behaving well. For me, iPhoto is the culprit that causes the panic. Perhaps it's because I have about 10,000 faces but iPhoto crashes pretty reliably if I bring up my daughter's face (she has about 2000 of those 10,000 pictures).

The next time I install RAM, I'll run memtest the same day. Darn. Looks like the data mismatch occurred in the same spot on the second pass as well. I pretty much have to dig into this further.

.