Currently Being ModeratedJul 12, 2011 3:35 PM (in response to Sam Beaver)
The only definitive way to know if RAM is the issue is to remove RAM in pairs until you find the pair that is causing the problem. Then replace the pair. A pair is usually one from Riser A and the matching slot in Riser B.
Currently Being ModeratedJul 12, 2011 3:45 PM (in response to Sam Beaver)
The modules need not have completely failed. All that's required is for a bit or byte to go bad then each time software tries accessing that area of RAM it will fail.
If it's not the memory then it may be a motherboard problem.
Is your problem only with the Terminal application? If so then you may just have a bad preference file.
Currently Being ModeratedJul 12, 2011 5:22 PM (in response to Sam Beaver)
terminal error and shuts down
You are playing a little loosely with the terminology.
Do you get kernel panics? If so, those are logged, and you can look at the log and try to determine the cause of the problem.
Do you mean your Mac Powers Off? that is most often caused by overheating, which is most often caused by dust bunnies inside -- but do not vacuum !!
Home vacuum cleaners plastic wands generate large static charges that can kill electronics. Move your Mac to an area where you don't care about dust and blast them airborne and out of your Mac with compressed air.Beige G3, G4/867, G4/dual 1.25 MDD, MacPro'09 w cheap SSD, Mac OS 8.6 or Earlier, and 9.2, 10.5 and Server - LW IIg, LW 4/600, ATalk ImageWriter L
Currently Being ModeratedJul 13, 2011 8:05 AM (in response to Sam Beaver)
Heat, air flow, etc
Monitor the temps and sensor readings
Boost the fan speed before it warms up
make sure the case has good air flow and circulation
fbdimms are hot, they also consume 10-15W for each DIMM
there should be very hot air out the back
graphic cards and air along with temps
Take a look at iStatPro and/or Temperature Monitor along with SmcFanControl 2.2.x
Currently Being ModeratedJul 18, 2011 3:57 PM (in response to Sam Beaver)
yes, better terminology would be a kernal panic.
my bad, can never remember or screen clip the proper name.
not a dust issue. mac has plenty of breathing space.
motherboard issue would present itself in either OS leopard or Snow Leopard.
checked and verified all of the RAM was working 100% with an app that checks that sort of thing.
nothing in the kernal logs consistent to determine any specific problem with a devise or a software. and, since the kernal panic happens anytime in SNow Leopard: on a clean install with no software or external hardware attached as well as a completely loaded system, by process of eliminating neither software nor the drive would not be a source of problem-error occurs tested using multiple internal hard drives.
Hopefully, Lion will fix whatever has prevented a lasting upgrade over all of this time.
Currently Being ModeratedJul 18, 2011 7:22 PM (in response to Sam Beaver)
If you are getting kernel panics, the reason stated in the log can be very helpful. You can post the entire log of an event here, and readers can help you decipher it.
Reasons like machine check indicate Hardware failures. Reasons like pagefault/segfault could be caused by lots of things. There are tons of others.
A new version of Mac OS X is unlikely to make things better -- very likely to make things worse.Beige G3, G4/867, G4/dual 1.25 MDD, MacPro'09 w cheap SSD, Mac OS 8.6 or Earlier, and 9.2, 10.5 and Server - LW IIg, LW 4/600, ATalk ImageWriter L
Currently Being ModeratedJul 20, 2011 3:41 PM (in response to Sam Beaver)
So far, looks like lion solved whatever problem it had.
when lion instaled, it said to remove what i assume was an old hp printer or scanner driver from system /ibrary/extentions/hpplugininit.kext (got rid of the printer). looks promising.
Currently Being ModeratedNov 12, 2013 1:31 PM (in response to Sam Beaver)
never could get the computer to go past 10.5.8, but have had no problems running leopard.
all ram checked out perfectly, but i read somewhere that higher os'es did not play nicely with aftermarket Ram, even RAm from reputable vendor.
Currently Being ModeratedNov 15, 2013 10:11 AM (in response to The hatter)
thanks, I'm thinking the problem I have might be related to ancient hp.kext files. doing a full flush on all hp, seein' if it'll clear it out.
reading about the issue, it seems that the hp scanning driver would run hidden in the background and take up alot of the CPU.
now that it is flushed, I no longer seem to be running at 10-20% CPU while idle.
will see if this works as i'm trying to get back into running snow leopard.
spent over 3 grand on my ram, so it's not going anywhere.