This is called a "kernel panic". Apple's troubleshooting instructions for kernel panics are here:
http://support.apple.
Another
http://www.thexlab.co
Main Topics
Browse All TopicsPowerMac G4, Model No. M8570, EMC No. 1914
OSX 10.4.11, Dual 1 GHz PowerPC G4, 1MB L3 cache per processor, Memory 2GB DDR SDRAM
The machine is off. The user powers on the machine. The machine starts and gets to the login screen. A message then appears that says "You need to restart your computer. Hold down the Power button for several seconds or press the Restart button." (See attached screen1.jpg.)
The user holds down the button & the machine restarts. The user is able to login, but the machine/fan is now noticably louder & slowly tapers off to it's normal volume in @ 5 minutes.
The user says the above has been happening every morning when they turn on the machine, and has been happening every day for the past week.
In addition, this morning the following appeared on the user's desktop after they successfully logged in:
System Failure: cpu=0; code=00000008 (unaligned stack)
Latest crash info for cpu 0:
Exception state (sv=0x57F4B280)
PC=0x0000ABC08; MSR=0x00001030; DAR=0xB760DA26; DSISR=0x42000000; LR=0x000ABACC; R1=0x003DA240;
XCP=0x00000098 (System Failure)
Backtrace:
0x00366000
backtrace terminated - unaligned frame address: 0x00000008
alias
Proceeding back via exception chain:
Exception state (sv=0x57F4B280)
PC=0x000ABAD0; MSR=0x00001030; DAR=0xB760DA26; DSISR=0x42000000; LR=0x000ABACC; R1=0x003DA240; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00366000
backtrace terminated - unaligned frame address: 0x00000008
Exception state (sv=0x8760DA22) Not mapped or invalid. stopping...
Kernel version:
Darwin Kernel Version 8.11.0; Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17-1/RELEA
Memory access exception (1,0,0)
Waiting for remote debugger connection.
What is happening and would should I do?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
This is called a "kernel panic". Apple's troubleshooting instructions for kernel panics are here:
http://support.apple.
Another
http://www.thexlab.co
Has the computer recently been upgraded or had any patches installed?
Had a memory upgrade? How long has it been doing this?
Boot from the Install CD and run disk diagnostics (disk utility).. ..or boot to single user mode and run fsck -y until you see no more errors.
Alternatively, boot from a firewire drive with a running OS on it and see if the computer still has the same behaviour. Run the disk diagnostics while booted from the firewire boot disk. This usually clean up the disk and any problems better than any other method.
If you have updated the OS prior to the problems you may need to back up your user's data and reinstall the OS fresh. Then restore the settings and docs and stuff from the backup.
Business Accounts
Answer for Membership
by: MiniDevoPosted on 2009-09-08 at 08:00:33ID: 25282570
I would run the hardware diagnostic ASAP. To be honest, I've seen this with CPU failures/overheating.