Memory Slot Utility dialog every boot

Hi Jeff Handy;

Has the memory utility been added to the start on login list?

Some of the utility writers are so proud of their work they add then to start on login list so that you always see them.

Allan

It should tell you why or suggest what to change, maybe leave empty a different slot.

I assume you removed and don't have anything other than the three 4GB (they don't mix).
http://eshop.macsales.com/Customized_Pages/memory/spn1066.html

Install video:
http://eshop.macsales.com/installvideos/macpro2009mem/

Have you tried Repairing Permissions and doing a Disk Verify/Repair?

Jeff Handy wrote:
the Memory Slot Utility dialog now comes up each time I boot SL.

That definitely doesn't sound right. It came up once for me when I added more RAM, basically confirming I had everything installed correctly, and then never appeared again.

It almost sounds like the PRAM isn't updating with the new config.

And yes, it's still there and it can be reset:

http://support.apple.com/kb/HT1379?viewlocale=en_US

My problem is just like the title says. This has been happening for over 4 months now. Been working with Apple for more then 2 months. Spent hours on the phone with 3 maybe 4 or more high level techs. Have had on site authorized Apple tech here 3 times and still have the Memory Slot..... window show up from time to time. The on site Tech and his boss feel have spent more time and money than it i worth to fix my machine. BTW - all the sim cards have been replaced twice. I feel and so does Tech and his boss it is time to have my machine replaced via my apple care. The person in Executive Customer Relations or Care Dept. does not feel this way and has been me jumping through loop after loop and I am now tired of this mess. It is now costing me time. ALL COMMENTS, SUGGESTIONS, OR HELP would be greatly appreciated. Thank you, David tfphoto99@yahoo.com

Message was edited by: David_K99

the above should read Hoop after Hoop not loop

Hardware profile, ie, Device Tree list, is stored in nvram, not pram.

I'd reset SMC when changing hardware if there is a problem.

With RAM, I'd send it back to OWC. Must as they sell and people swear by (or at!) I stopped buying from them after repeated failures and slow to resolve.

My problem is just like the title says. This has been happening for over 4 months now. Been working with Apple for more then 2 months. Spent hours on the phone with 3 maybe 4 or more high level techs. Have had on site authorized Apple tech here 3 times and still have the Memory Slot..... window show up from time to time. The on site Tech and his boss feel have spent more time and money than it i worth to fix my machine. BTW - all the sim cards have been calcolatrice online replaced twice. I feel and so does Tech and his boss it is time to have my machine replaced via my apple care. The person in Executive Customer Relations or Care Dept. does not feel this way and has been me jumping through loop after loop and I am now tired of this mess. It is now costing me time. ALL COMMENTS, SUGGESTIONS, OR HELP would be greatly appreciated.


-------------------------------------------------------------------------------- --



My device is placed alone

If your Mac were much older, I would suspect that the button battery that maintains the parameters had gone dead. Do you, by any change, shut off the power strip at night? that can lead to premature failure.

In any case, removing and testing the button battery (BR 2032 Lithium Coin Cell) should be done. The Voltage should measure the same as a new battery (somewhere in excess of the nominal 3 Volts.)

The utility is only supposed to come up if the system detects a change in the memory configuration. It may be a case where you have a DIMM that's intermittently not being detected at startup. The next time you reboot, it's seen again - and this registers as a "change" in the memory configuration, so the message comes up.

Try checking "About this Mac" before shutting down/restarting to confirm all RAM is being recognized each time to see whether this could explain the behavior.

You can also try testing with only the stock/original RAM in the system, to see if the message persists, as a means of isolating it to the added/3rd party RAM.