Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Alan Bishop2
Alan Bishop2 Author
User level: Level 2
388 points

Bus error

Hi everyone,

When I start up after the imac has been shut down overnight all is normal until it gets to OS 9.2 starting up and then I get Sorry a system error occurred. Bus Error. To temporarily turn off extensions restart and hold down the shift key It will not restart by clicking restart in the notice so I press the restart button and hold down shift key. It starts with extensions off. Then I do a normal restart from the drop down menu to start with extensions on and all is OK. This has just started happening the last 3 days.

What is a Bus error. Any help would be appreciated.

Indigo 350 mhz. slot loading imac. OS 9.2.1 320 mgs. Ram

indigo imac 350 slot loading + 256 mg Ram = 320. 6 gig hard drive Mac OS 9.2.x Blueberry g3 clamshell ibook OS 9.2.2

Posted on Jan 8, 2006 1:27 AM

Reply
Question marked as Best reply
User profile for user: Baby-Boomer-USofA
Baby-Boomer-USofA
User level: Level 9
58,098 points

Posted on Jan 8, 2006 11:25 AM

Bus and address errors occur when a segment of memory is inaccessible -- either because it is reserved for another use or it doesn't exist. These are the most common system errors and are likely caused by an extension conflict, insufficient memory, or corruption in an application or an application's support file (e.g., a preferences file).

Other causes could include faulty application code, or a bad logic board. Because these causes are less likely causes, you should for them only after troubleshooting for the most common causes.

Possible Solutions: When either of these errors occur in only one application, try running the application with extensions disabled. If the error does not recur, troubleshoot for extension conflicts.
http://docs.info.apple.com/article.html?artnum=30929 Mac OS: Extension Conflict Troubleshooting/Extensions Manager Features.

If the error occurs in only one application and while extensions are disabled, try trashing the application's preferences file so the application creates a new one. If the error does not recur, a damaged preferences file was the cause.
Preferences are found inside the Preferences Folder which is located inside the System Folder.

You should also try allocating more memory (RAM) to the application.
http://docs.info.apple.com/article.html?artnum=18278 Mac OS: Assigning More Memory to an Application Program. The same directions are also in the OS Mac Help Menu.

If the error occurs in more than one application, the cause may be a problem with either the system software or, perhaps, the hardware. Reinstalling your system software will likely resolve errors caused by damaged system software. If the error is caused by hardware, SCSI devices attached to your Macintosh may be the cause and you should troubleshoot the SCSI chain.
(The last sentence does not pertain to your iMac)
View in context
5 replies
Question marked as Best reply
User profile for user: Baby-Boomer-USofA
Baby-Boomer-USofA
User level: Level 9
58,098 points

Jan 8, 2006 11:25 AM in response to Alan Bishop2

Bus and address errors occur when a segment of memory is inaccessible -- either because it is reserved for another use or it doesn't exist. These are the most common system errors and are likely caused by an extension conflict, insufficient memory, or corruption in an application or an application's support file (e.g., a preferences file).

Other causes could include faulty application code, or a bad logic board. Because these causes are less likely causes, you should for them only after troubleshooting for the most common causes.

Possible Solutions: When either of these errors occur in only one application, try running the application with extensions disabled. If the error does not recur, troubleshoot for extension conflicts.
http://docs.info.apple.com/article.html?artnum=30929 Mac OS: Extension Conflict Troubleshooting/Extensions Manager Features.

If the error occurs in only one application and while extensions are disabled, try trashing the application's preferences file so the application creates a new one. If the error does not recur, a damaged preferences file was the cause.
Preferences are found inside the Preferences Folder which is located inside the System Folder.

You should also try allocating more memory (RAM) to the application.
http://docs.info.apple.com/article.html?artnum=18278 Mac OS: Assigning More Memory to an Application Program. The same directions are also in the OS Mac Help Menu.

If the error occurs in more than one application, the cause may be a problem with either the system software or, perhaps, the hardware. Reinstalling your system software will likely resolve errors caused by damaged system software. If the error is caused by hardware, SCSI devices attached to your Macintosh may be the cause and you should troubleshoot the SCSI chain.
(The last sentence does not pertain to your iMac)
Reply
User profile for user: Alan Bishop2
Alan Bishop2 Author
User level: Level 2
388 points

Jan 9, 2006 8:18 AM in response to Baby-Boomer-USofA

Hi Baby Boomer,

Thanks for your reply. When I started up today everything started as normal. No bomb messages no problems.2 weeks ago I downloaded the latest IE 5.1.7 and have it up and running. The earlier one is stil in the applications. Could this cause a conflict. If it happens again I will try your suggestions.

Regards from England,

Alan
Reply
User profile for user: Ed Hanna
Ed Hanna
User level: Level 4
1,240 points

Jan 9, 2006 2:14 PM in response to Alan Bishop2

Hi Alan, just to let you know, you're not alone. I occasionaly get this message, or the even more cryptic "Code fragement could not be prepared". Booting w/ extensions off, rebuilding the Desktop then re-booting normally always fixes it—for a couple of weeks. But a fortnightly desktop rebuild's not a bad running maintenance routine.

FWIW, somewhere, someone whose advice I read suggested that these (your prob and mine) were intermittant conflicts likely caused by OS components of varying ages—some of OS 9 does go back to System 7 and who knows how far back 3d part extensions were coded—trying to access the same sweet spot simultaneously, or out of proper sequence by just a tad. Like most intermittants, in most spheres, it seems easier to allow for it and carry on arounfd the problem.

But it should be fun to attempt the more thorough-going sort of fix Boomer outlined.
Reply

Bus error

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up