Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / General / General / January 2006



Tip: Looking for answers? Try searching our database.

Kernel Panic - finding "memory element"

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Steve Emerson - 31 Jan 2006 18:47 GMT
I'm getting a Kernel Panic of the "Unresolved Kernel Trap" variety, and
the effective address of the memory element (DAR) is always the same:
DAR=0x00000490.

Anybody know how to decipher where that memory element is? These crashes
are all since I installed one particular hunk of memory, which may or
may not be the cause; for one thing, it was at least a month
post-install that the Unresolved Kernel Traps began.

The newer RAM:

DIMM1/J13   512 MB SDRAM   PC133-333

Thanks for any insights.

Steve.

iMac G4   OS 10.3.8  768 MB RAM
Garner Miller - 31 Jan 2006 19:03 GMT
> Anybody know how to decipher where that memory element is? These crashes
> are all since I installed one particular hunk of memory, which may or
> may not be the cause; for one thing, it was at least a month
> post-install that the Unresolved Kernel Traps began.

I can't answer your specific question, but I can relay that I started
getting lockups and kernel panics on my G4 iMac about two years after I
installed extra memory (a 512MB module from Ramjet.com).  Not long
after, the module started reporting that it was only 256MB!  Removing
the memory cured the problem, but of course made the machine very slow
with only 256MB in it.

I called the memory vendor and explained the symptoms.  He talked me
through a few things to try to ensure that it really was the memory
that went bad.  He said it's unusual for it to fail like that, but
cheerfully exchanged it for new memory that's been working flawlessly
ever since.  (I'd happily do business with ramjet.com again.)

If removing the suspect memory fixes your problem, I'd say there's a
very good chance that's where your problem lies.  If it's still under
warranty, call the vendor where you bought the memory and see what they
can suggest.

Signature

Garner R. Miller
Clifton Park, NY =USA=
http://www.garnermiller.com/

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.