|
|
clamshell system failure-corrupt stack? advice
|
|
|
|
Fresh-Faced Recruit
Join Date: Nov 2006
Status:
Offline
|
|
Hi, I've been modding ibook clamshells for a few years...one indigo I upgraded for a friend that had been working fine recently has been giving a 'system failure' message at start up..a white on black message starts with:
sSystem Failure: cpu=0; code=00000001 (Corrupt stack)
Latest crash info for cpu 0:
Exception state (sv=0x008C7000)
and a number more lines of info, including:
Backtrace terminated - unaligned frame address: 0xFFFSA77C
Does anyone have an idea of what's up...software or hardware....fixable part(s) or fried logic board (about the only thing I don't mess with).
Any advice or suggestions for figuring out appreciated. Search here for system failure corrupt stack didn't lead anywhere...
Thanks, Rick
|
|
|
|
|
|
|
|
|
Moderator Emeritus
Join Date: Apr 2005
Location: Cambridge, UK
Status:
Offline
|
|
Have you tried different RAM in it?
|
|
|
|
|
|
|
|
|
Grizzled Veteran
Join Date: Feb 2004
Location: The O.C.
Status:
Offline
|
|
did you try google search to see if other mac threads come up?
|
MacBook 2.4GHz Intel Core 2 Duo | Clamshell iBook G3 366MHz | 22" Cinema Display | iPod Mini | iPod shuffle | AirPort Express | Mighty Mouse
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Apr 2002
Location: Illinois
Status:
Offline
|
|
You didn't give us the real lines to check the problem.
It'll look something like this:
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleAPIC(1.2.0)@0xa1b000->0xa1dfff
com.apple.driver.AppleACPIPlatform(1.2.1)@0x87e000->0x8bafff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x6b9000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x720000
But, yea, check google (One of the first hits was reset/replace PRAM battery)
|
|
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Nov 2006
Status:
Offline
|
|
Thanks so far I have tried different Ram, no luck. Did search Google and much good advice, can't do many tests as i consistently get the kernel problem. Will try again later today (after real job) to reboot with OS X disc, reset PRAM (no battery) and can post all 'real lines' as King Bob suggested. Someone said do hardware test, also can try to reset PRAM, PMU, and NVRAM and report back. Really appreciate the help, don't want to assume CPU is fried yet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|