Sad Mac - how to identify which RAM modules are bad

[joshlac]

Hi,
I've an original Macintosh from 1984 and the sad Mac error I get on boot is 04ACBA
How to pinpoint which RAM chips are bad?
Where to get replacements? I'm based in Dublin, Ireland.

 

[Builder68]

Go here:

Sad Mac Error Codes

UPDATE! :) Gary Rice generously released the Black & Bleu - The Ultimate Mac Error Codes Utility on Macintosh Garden. This is an excellent resource for making sense of the Sad Mac codes, more than what is listed below. Apple's overview below is...

tinkerdifferent.com

 

[joshlac]

Go here:

Sad Mac Error Codes

UPDATE! :) Gary Rice generously released the Black & Bleu - The Ultimate Mac Error Codes Utility on Macintosh Garden. This is an excellent resource for making sense of the Sad Mac codes, more than what is listed below. Apple's overview below is...

tinkerdifferent.com

Thank you. I found this website earlier, but I've no idea how to indetify the bad chip/chips.

So, for 04ACBA
Class Code: 04 - Memory test--Mod3 test
Subcode: ACBA - Do I convert it like below:

• Hex: ACBA
• Decimal: 44218
• Binary: 1010110010111010

But then I don't know in what location the bad chip is...

 

[Builder68]

My best advice is to replace them all. That subcode usually means that more than one IC is gone bad. The RAM chips on the original 128k and IIc are known for going bad after some time. Some failed even back in the day. Could be also one of the 74244s.

Have you try to clean the ROM sockets re-seat the ROM ICs?.

04= Bad RAM, you should start by replacing all RAM ICs.

 

[joshlac]

Ok, thank you. Where would I source them? EBay?

 

[cheesestraws]

Yes, if it's a 128k those use Micron DRAMs that are a bit notable for self-destructing. You may wish to replace them all, or if you don't, you may wish to keep (non-Micron) spares for when the remaining micron ones disintegrate.

I think I got mine from ebay, but it was so long ago I can't remember.

 

[bibilit]

I agree, probably too many bad chips to generate a correct fault code.

You can try the piggybackîng method to narrow down the issue.

 

[Juror22]

You can try the piggybackîng method to narrow down the issue.

This worked for me when I had a similar problem on an old Compaq PC - its good to be reminded of the options for troubleshooting!