FW: bad RAM


    Sponsored Links


  • 1. Why Cyrillic letters do not show up in Google earch Window?
    Dear Everyone: I am now using a Mac OS X (Version 10.5.4) machine and Firefox (Version as the web-browser. In the Google search window, I can input German letters, Chinese characters and some other non-English letters, but I cannot input Cyrillic (Russian) letters. Every Cyrillic letter shows up as a "?" (question mark). when I proceed with the search, however, it still recognizes the Russian words I have input. I just asked our system manager and, he did not have an immediate answer. Could anyone tell why the Cyrillic letters do not show up properly in the Google search window? And how can you resolve the problem? Thank you for reading and replying! --Roland
  • 2. Old solaris curmudgeon trying to learn OS X filesystem internals
    I am trying to get my knowledge of OS X up to the level of my old knowledge of Solaris, for reasons of doing computer compromise investigations. I know about inodes, and the capabilities of the OS calls that update the Create, Modify, and Access times for files and directories. It is important from a timeline analysis standpoint. I don't have a clue for OS X and their CINDs Catalog File, and Extents overflow file. Anyone have a reference to the internals of the OS X files system? Anyone have a reference to the system calls that open files, directories, etc. Also, like Harlan Carvey, I like perl, and perl has an interface to the "stat" call to dump the information about a posix inode (which of course isn't an inode underneath), does anyone know of a lower level equivalent for perl that doesn't go through the posix filter? I will cross post this to the other investigations group, so if you are like me, and a member of both groups, I apologize in advance. Thanks in advance. Jim
  • 3. Something interesting that I noticed
    If you press the option key in TextEdit (also in Script Editor), the mouse pointer changes to crosshairs. You can then drag-select a rectangular block of text. Curiously, this does not work in Pages or in any third-party software that I've tried. -- Don't repeat the mistakes of the past eight years. Vote for Obama and Biden.

FW: Re: bad RAM

Postby Herlind Wurth » Tue, 25 Jan 2005 21:48:18 GMT

It seems my post from last Friday didn't make it to the list, so I am
reposting it again.


------ Forwarded Message

------ End of Forwarded Message

Re: FW: Re: bad RAM

Postby Mark Conrad » Wed, 26 Jan 2005 06:38:59 GMT

In article <BE1AAD22.1318C% XXXX@XXXXX.COM >, Herlind Wurth

Hello again, Herlind.   As before, only use one module at a time in
your Mac, while you are doing this particular troubleshooting.

What I need to know now is whether your original RAM module of 256-MB 
_always_  works okay as long as it is in slot#1   ( _only_  slot#1)

...and I also need to know if that original module  _always_  tests as
"passed" with your RAM testing utility, as long as it remains in slot#1

Given all the present possibilities as to what might be wrong, you will
have your hands full troubleshooting this problem.

The more we can do to eliminate other slots #2, #3, #4 - then the more
likely we are to make progress with the troubleshooting.

Hang in there,


Similar Threads:

1.Bad Ram on Apple IIc

2.bad RAM?

When one of our G5s started getting a lot of kernel panics, we ran the 
Apple Hardware Test CD.  It came up with bad RAM.  By process of 
elimination, we narrowed it down to one of two modules.  Since they have 
to be installed in pairs, we didn't bother going any further.  We pulled 
both of them and the computer has been running perfectly since.

Out of curiosity, I put the RAM in another G5 (one that had only 4 
slots).  When I ran the hardware test again, everything checked out OK.  
Both computers run fine, even though one has the "bad" RAM.

Can anyone explain this?  If the RAM is good, we certainly don't want 
throw it away.  Any thoughts?


3.Bad ram story & advice needed, please

Several months ago, my Wallstreet (320 megs ram, 64 in bottom slot, 256 
in top) started having problems with weird crashes out of the blue and 
then a flashing question mark on re-boot. After that, the system would 
not install on either of the two partitions like it should have. 
Sometimes it would install on first try, maybe not. Sometimes I'd have 
to make several tries to get it installed on either partition.  It 
seemed I could never get a full install on both partitions in one try 
towards the end of these several months of difficulties. Then, even 
after I got a good install, I'd have boot problems of some kind or 
another. Checking the hard disk found no problems. Finally I decided to 
ask for help.

I posted a question in the powerbook forum on apple's site, whereupon 
someone advised me that I may have a bad ram chip.

This morning I finally found the time to remove the top 256-meg chip. 
Then I re-booted, initialized the disk into two partitions, and 
re-installed the system on each partition with nary a hiccup. Re-booted, 
configured the system for our home LAN, and it's up and running on the 
first try.

I think the ram chip *may* have been the problem. 

And the question is:
Where should I buy a new 256-meg ram chip for that top slot? I have only 
the bottom 64 megs and it won't be enough to run the PB comfortably.  I 
want the top-notch ram in it, even if it costs a bit more.

Thanks in advance for your considerations,

4.bad RAM


I have a G4, MDD, that has been "behaving badly" = system crashes and hangs.
But it didn't have any real pattern to it. Sometimes it would work just fine
for some time, then it crashed again.

The RAM that is installed:
slot 1 - apple original with 256MB
slot 2 - 3rd party, 512MB
slot 3 - 3rd party, 512MB
slot 4 - empty

I suspected bad RAM and ran Apple Hardware Test on the computer. It reported
an error: 2 MEM/4/4: DIMM2/J23

So I exchanged the RAM with a new one. And did the test again.
Again I got an error message: 2 MEM/3/4: DIMM2/J23

I tried various combinations (different RAM-chips, different slots) and got
error messages for slot 3 and 4 for various RAMs. But not always, sometimes
the test is passed ok, next time it claims an error for the same module in
the same slot, that passed before.

When I start the system, sometimes it runs fine, sometimes it hangs,
sometimes I even get a kernel panic.

First it seemed that I only got errors on slots 3 and 4. So I tried with 3rd
party RAM in only 1 and 2 --> error in slot 1. Then I put in the original in
slot 1 again (with 3rd party in slot 2) --> again error for slot 1. (This
was the first time, that I got the error on the original RAM).

So any idea if there is a chance for this system?

I doubt that it is the RAM-modules, I tried 5 different in different
combinations - they can't be all bad (I have used many of this kind in other
Macs and never had problems).

Thanks, Herlind

5.Finding Bad RAM


This is the culmination of a few related threads over the past few weeks.

About a year ago, I sadly concluded that my Pismo laptop had a 
hopelessly sick motherboard, because no matter what I did, the boot 
drive -- and backup drives -- developed an endless succession of 
increasingly serious directory errors, until the machine became 
unuseable. I put the Pismo away for backup parts and bought another one.

Yes, I was using DiskWarrior. Like, about ten times per day, until I 
gave up.

Now, through a series of happenstances, I have discovered that the 
directory errors probably occurred because the RAM SIMM or DIMM in the 
old Pismo was defective. The GURU utility has demonstrated the defect in 
the old RAM card very clearly. The defect shows up every time, on the 
first pass.

So, the good news is, I might be able to resuscitate my old Pismo.

The bad news is, the native RAM check in OS 9 doesn't seem so good. This 
machine passed the startup RAM test every time, yet the RAM card was 
clearly defective. I thought the startup RAM test was supposed to be 
better than that.

I'd like to understand the startup RAM check in OS 9 and OS X a little 
better. How good is it? How could a problem like this slip through?

OS X seems to check RAM very differently. My G4 now has 1 GB of physical 
RAM. Since I added more RAM, it takes a lot more time to start in OS 9, 
presumably because it is running through the startup RAM check. By 
comparison, OS X starts quite a bit faster than OS 9 on the same 
machine. Does OS X check RAM at some other time, like during idle clock 
cycles, or when the machine has been idle for awhile, or what?

Does OS X have a native RAM test utility? If so, I guess I need to learn 
how to use it. If not, is GURU adequate? Is there an alternative to the 
high-priced TechTool Pro?

I don't never wanna go through nothing like this again. I can't tell you 
how many precious hours it wasted. A lot... Not to mention the needless 
expense of a new-second-hand laptop.

Thanks in advance,

Tim Miller

6. bad RAM - (final final final summary, thanks everyone)

7. bad RAM - (final observations) l-o-o-o-n-g

8. Woe Is Me (CrossPost) Bad RAM/Testing

Return to mac


Who is online

Users browsing this forum: No registered users and 59 guest