[houseoftwits]

The apps on my iMac are crashing repetitively and I need help determining what's causing the crashes. I was once handy with DOS, but GUIs, networks and servers, not so much... the Mac often confounds me (I over-think or just don't get it), so any help would be truly appreciated.

Machine specs: 24" 2.33GHz iMac, 4G RAM

I upgraded to Leopard on Friday evening and after the upgrade was successful, I upgraded the memory from 2G to 4G (yes, I was grounded). That evening, I had no problems surfing, checking mail, or using iTunes & my iPod.

Saturday morning, I started having apps repetitively crash: RollerCoaster Tycoon III (Soaked), Firefox, Safari, Mail, Crash Reporter and Quicken. Crucial (memory vendor) believes it is bad memory cards and wants to exchange them. But, after looking around online, it seems that a lot of other people are getting the same error, so I'm not convinced it's bad memory cards - maybe it's just Leopard being obnoxious.

I uninstalled the memory and put back the original cards. I got an error within 4 mintues: ReportCrash, EXC_BAD_ACCESS (SIGBUS), KERN_PROTECTION_FAILURE at [], Crashed Thread 1. After returning to the machine 3 hours later, I got another crash: Firefox, EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS at [], Crashed Thread 0. Since the machine kept crashing and was running slower, I re-installed the 4G memory and the machine continues to crash with the same error messages.

Thus, I am unconvinced that it's bad memory cards: I don't want to run in circles exchanging memory when I might just need to roll-back to 10.4.X until Leopard's next release. Here's a run-down of the basic crash messages:

First 2 errors were EXC_BAD_INSTRUCTION

Remaining errors were EXC_BAD_ACCESS and most were followed by (SIGSEGV) and KERN_BAD_INSTRUCTION.

So, is this a Leopard issue or do I have bad memory cards?

A final note is that based on solutions found online, I've already put in a fresh install of DivX, the 10.5.1 update and have verified/repaired permissions.

[Cold Warrior]

Insert your iMac's restore/install DVD, restart the Mac, and hold down the d key at startup (right when you hear the chime). Keep holding d until you see it booting from the disc. This will bring up a hardware test interface. Run the hardware tests to test your iMac's hardware.

When those tests are complete, restart and hold down the c key. This brings up the OS X installation interface. From here you click the Utilities menu and choose Disk Utility. On the left you'll see some hard drive icons. Choose yours, and select Verify Disk from the right-hand pane's options. This will test your iMac's hard drive for volume and drive errors.

[seanc]

What type of Leopard install did you do? Upgrade, Archive and Install or Clean Install? Upgrade seems to have caused a lot of problems, so an Archive and Install is recommended.

I'm usually one to jump in straight away and scream bad memory, but now I'm confused. If the originals are doing it then it doesn't quite make sense.
Can you try one stick at a time in one slot, see if it has problems, if it's fine, move it to the other slot, if it's not fine, move it to the other slot etc. I have had memory slots go bad before.

[houseoftwits]

seanc, I did some reading beforehand and used the "Archive & Install" option.

Ironically, since posting my problem and getting the 2 replies (thanks!) I haven't had a lockup...

Thanks for your suggestion, Cold Warrior. For some reason, I cannot get the freaking machine to boot up on the DVD; I hold down d at the "chime" but end up on the desktop with the finder showing the DVD's contents... My husband will be home in a few hours and then we'll see if my technique just sucks.

One bit of clarification would be terrific - the hardware test should discover problems with the memory cards OR the memory slot, right?

[seanc]

Well yes in theory. If the card was bad, it would say slotx has a problem. If the slot is causing the memory to misbehave, it will still say slotx has a problem.

Check the disc that you've got inserted, it should say how to enter the hardware test. If it doesn't you may have the wrong disc or it may be on a separate disc.

[CharlesS]

Hold down the Option key at startup instead of 'C' or 'D', and you'll get into the bootloader, from where you can see all the bootable discs that are present and choose the one you want.

However, first I'd try something simpler: check your /Library/InputManagers folder. Move anything that's in there to the Desktop, reboot, and see if your problem goes away. Also, APE shouldn't be functional on Leopard, but just in case, check /Library/Frameworks and ~/Library/Frameworks to make sure Application Enhancer.framework isn't in there. If it is, delete it.

[houseoftwits]

My problem yesterday with the disk was sheer operator failure - I had the wrong one... This morning, I successfully ran the Hardware Test - I chose extended test - and everything came out okay - no problems found.

I rebooted, went into disk utility and verified the harddrive (no problem found).

I checked the Library folder; I do not have an InputManager folder or the Application Enhancer.Framework.

Any other suggestions? At this point, I'm ready to roll-back to 10.4 and wait for 10.5.2.

[seanc]

Leave the extended test running in loop mode for a while. I think it's activated by pressing command + l

[JKT]

If you have any external USB equipment attached such as a hub, I would also unplug those from your system and see if that helps (not including the Apple keyboard and mouse for obvious reasons). Try without for a while.

Also, maybe resetting your power management would help - for your system you do this by shutting down the iMac and pulling the power cord out then leaving it out for 5 mins +. Once it's been out for that time, put it back in and restart. Note, this will reset the time and date settings on your system so, unless you use a network server for those settings, you'll need to put in the correct settings once you reboot.

I sincerely doubt this has anything to do with Leopard, unless it is a software incompatibility with any third-party USB hardware like a hub. It sounds much more like a hardware issue than a software one, given the way you have installed the system.

[houseoftwits]

The only items plugged into my iMac are an HP Photosmart 8450 via USB and a Westell 327W modem via ethernet cable.

I'm going to do the power management reset.

I heard of a list of apps that conflict with Leopard - anyone know where I can find that list?

[JKT]

If the reset doesn't help, I would still try disconnecting the third party hardware to see if that is a source of the problem.

Also, what happens if you do a safe boot (hold down shift as you start up the Mac and keep it held down) to disable any third party kexts etc.? If it works fine then that points to a driver for third party hardware or software as the source of the problem.

[MacNNUK]

Is there a way to report crashes, without using crash reporter, having just clicked to bypass it ?

Pls don't quote terminal or console, a nice easy email is all I'm after sending.

Mail crashes often now after latest security! update, 10.4.11, mail 2.1.2

Understand it may be something to do with HTML emails, though last time it crashed with my draft email with photo jpg attachments, before I sent it, saved draft though.

[analogika]

Originally Posted by houseoftwits 

The only items plugged into my iMac are an HP Photosmart 8450 via USB

Ten to one you didn't update the printer driver when upgrading to Leopard, right?

Download the latest driver version from hp.com (make sure it's explicitly compatible with OS X 10.5).

[analogika]

Originally Posted by houseoftwits 

I got an error within 4 mintues: ReportCrash, EXC_BAD_ACCESS (SIGBUS), KERN_PROTECTION_FAILURE at [], Crashed Thread 1. After returning to the machine 3 hours later, I got another crash: Firefox, EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS at [], Crashed Thread 0.

[...]

First 2 errors were EXC_BAD_INSTRUCTION

Remaining errors were EXC_BAD_ACCESS and most were followed by (SIGSEGV) and KERN_BAD_INSTRUCTION.

So, is this a Leopard issue or do I have bad memory cards?

Also, unfortunately, those error titles you posted are the *least* useful part of a crash report.

What's actually relevant is *which* threads were involved in the crash - if there is, for example, any mention of com.hp.somethingsomething or anything that looks like it might involve the printer architecture or the USB controller, that could be a hint that the outdated driver might be at fault.

[MacNNUK]

I've discovered how to stop Mail crashing.

Post the question here, since I did, Mail hasn't crashed once !!

I have downloaded a couple of Apple updates, QT and one other, but no security d/l's

Figure that !

UPDATE: Spoke too soon.

Crashed twice today !!!

[bearcatrp]

If your set on upgrading to leopard (would suggest you wait until the next update), Do a clean install. If you have an external drive, clone your tiger set up to it, that way, you can boot from it when leopard rears its buggy head. Then, bring one app at a time to leopard AFTER you check to see if its leopard compatible. Let it run a day or two then bring another. The next update will hopefully fix alot of problems but the apps need to updated to work with leopard. I went back to tiger because of software issues but sits eagerly awaiting the next update. Good luck.