At 2:22 PM -0700 4/18/2010, tentengrrl wrote:
g3 600 iMac running Tiger w/256K RAM
256 MB is a bit low, but should work if you're reasonable with it.
The main problem is I can't get the Safari to stay open, it keeps
unexpectedly quitting or freezing but sometimes it's after an hour
and other times, 5 min or 10 seconds. After that happens the other
programs MIGHT do the same thing.
It was like this when I first got it so I did the combo udpate to
Tiger 10.4.11 and Safari is version 3.0.4 thinking it would help but
no.
Like I said, it's mostly Safari but during my testing of the sticks
and slots by swapping them around, sometimes other programs will
unexpectedly quit, I restart, Safari goes fine, other programs, too,
and then a crash. Sometimes, after using only one stick I think the
spinning beach ball freeze is due to just not enough RAM to load a
page? But then I have enough RAM to run iTunes, Preview, Safari, and
stickies all at once. (So I'm not sure. I'm still learning as I go
along!
Ok. You seem to be jumping to a conclusion that this is a memory
related issue? How so? Memory errors RARELY cause app crashes.
Typically a memory error will result in a kernel panic - the whole OS
crashes.
When I look at the Problem Report it says Kern_bad_access and
Kern-invalid address, or Kern_bad access and Kern_protection failure.
Yea, that's the fundamental class of errors that causes apps to crash
(the OS' scream that it's in pain). It says nothing about what
actually caused the crash - could be that pesky anvil that hit your
toe, or the desk that hit your forehead. You need to look further
on in the log, at the backtrace of the crashed thread to see what
actually caused the problem.
It would also be a good idea to take a look at the system and console
logs, to see if there are any hareware failures being noted. Use
Console.app to view the logs.
If you can't make sense of them, zip a few up and email the archives
directly to me. I'll take a look.
I just can't get a definite pattern on it b/c it seems so random but
sometimes it does ramp up, crashing quicker and quicker but I can't
determine if it's one stick/slot all the way. I have looked online
and this seems not uncommon and to be attributed to bad RAM to a
preferences file all the way to "just totally random".
Install Memtest, then boot your Mac into single user mode (cmd-S),
and run Memtest overnight.
Memtest is an optional install, included in the AppleJack package.
AppleJack is an emergency repair tool for OS X - a sledgehammer, if
you will, for when polite tools like Disk Utility and OnyX don't
quite fix things.
AppleJack lives here:
<http://sourceforge.net/projects/applejack/>
but digging around in a software force can be daunting, so here's the
installer direct:
<http://dl.dropbox.com/u/610326/AppleJack-1.5.dmg>
The command to start Memtest is as follows. Note that in Single User
Mode, you're dealing with the raw Unix underbelly of OS X -- so
commands are case sensitive!
/usr/local/sbin/memtest all 3 -L
HTH,
- Dan.
--
- Psychoceramic Emeritus; South Jersey, USA, Earth.
--
You received this message because you are a member of G-Group, a group for
those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs.
The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette
guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/g3-5-list
