[Eyenovation]

Arghhh.. OSX keeps crashing. Can anyone interprety this, PLEASE?!?!?!

Date/Time: 2003-12-14 00:18:33 -0800
OS Version: 10.3.1 (Build 7C107)

Command: Final Cut Pro (/Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro)
PID: 417
Thread: 5

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000588

etc... etc..

[asdasd]

You need to post more of the crashing thread than that.( thread 5)


BTW it is a crash in Final Cut Pro, not Mac Os X

[Eyenovation]

I get the same crash in damn near every OSX application at least once a day. I'd have posted more, but I cannot due to size limitations in the thread.

http://www.mac-forums.com/forums/showthread.php?t=3121

I got the same crash using Illustrator, and did manage to fit the code into another forum.

Any ideas?
I get:

KERN_PROTECTION_FAILURE

At LEAST 3 times a day, and it NEVER started until I installed Panther.

[qyn]

That's usually an illegal pointer dereference. Your chance of diagnosing a crashing system from console logs is about nil unless you have the source code.

[Eyenovation]

Originally posted by qyn:
That's usually an illegal pointer dereference. Your chance of diagnosing a crashing system from console logs is about nil unless you have the source code.

So in other words... I'm screwed?

[Chuckit]

There were several questions and suggestions on the Mac-Forums board (any third-party RAM, how Panther was installed, what kind of computer), and they were the same things I'd say given the limited information we have here. What happened with those?

[Eyenovation]

Originally posted by Chuckit:
There were several questions and suggestions on the Mac-Forums board (any third-party RAM, how Panther was installed, what kind of computer), and they were the same things I'd say given the limited information we have here. What happened with those?

As for the RAM, I have 2 GB of Crucial 2700 DDR RAM. Panther was installed, overwriting Jaguar (meaning, I didn't reformat the drive), The computer is a Dual 1.42 GHz G4 purchased the VERY day the G5 was announced.

The problems persisted ONLY when using Panther leading me to believe:

a. It's OS related
b. That I don't know what a Kernel is
c. That Jaguar wasn't so bad after all

[wadesworld]

If Jaguar is the end-all be-all of operating systems, then reformat your disk, reinstall Jaguar and never upgrade again.

If, on the other hand, it's possible that you might run into a problem with any OS upgrade, including Jaguar, then you might be better served to work on solving the problem, rather than talking about how much greener the grass is on the other side of the fence.

If the crash is really the same in multiple applications as you state, then it's very likely one of three things:

1) Some hack you've installed
2) A bad font
3) A not-so-good OS installation

The crash you posted occurs in the process of drawing Windows. Thus, some haxie could definitely cause it, as could a bad font. When all applications are suffering the same crash, a bad font is definitely something to look for.

If you remove any hacks, and spend some time trying to eliminate fonts and still have no success, then it's time to assume something got a bit corrupted during install and it's time to backup, reformat and reinstall.

Bad memory is another possibility, but less likely if the crash is occurring in the same place every time. Bad memory is also much more likely to produce kernel panics rather than just application crashes.

Wade

[Eyenovation]

here is another one:

Date/Time: 2003-12-14 16:21:28 -0800
OS Version: 10.3.1 (Build 7C107)

Command: Remote Desktop Connection (/Applications/Remote Desktop Connection/Remote Desktop Connection)
PID: 383
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
#0 0x004243f0 in 0x4243f0
#1 0x004367b0 in 0x4367b0
#2 0x0041501c in 0x41501c
#3 0x00414f98 in 0x414f98
#4 0x00454b08 in 0x454b08
#5 0x00454e00 in 0x454e00
#6 0x927d1f94 in DispatchEventToHandlers (DispatchEventToHandlers + 336)
#7 0x927d2208 in SendEventToEventTargetInternal (SendEventToEventTargetInternal + 372)
#8 0x927d6600 in SendEventToEventTargetWithOptions (SendEventToEventTargetWithOptions + 40)
#9 0x927e2ca4 in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHan dlerCallRefP14OpaqueEventRefPv (_Z29ToolboxEventDispatcherHandlerP25OpaqueEventHa ndlerCallRefP14OpaqueEventRefPv + 696)
#10 0x927d2050 in DispatchEventToHandlers (DispatchEventToHandlers + 524)
#11 0x927d2208 in SendEventToEventTargetInternal (SendEventToEventTargetInternal + 372)
#12 0x927e4634 in SendEventToEventTarget (SendEventToEventTarget + 40)
#13 0x927e8560 in ToolboxEventDispatcher (ToolboxEventDispatcher + 92)
#14 0x92805814 in HLTBEventDispatcher (HLTBEventDispatcher + 16)
#15 0x927fb6b0 in RunApplicationEventLoop (RunApplicationEventLoop + 152)
#16 0x00426d60 in 0x426d60
#17 0x00428760 in 0x428760

[Eyenovation]

I appreciate the help - sincerely.

A bad font? I've never heard of such a thing. How would I know?? How can I fix it?
The crashes seem to be happening a lot more.

How can I test if my RAM is bad? How would I know which of the four sticks IS bad (should that be it).

As far as hacks I've never installed such a thing - nor would I mess with something I didn't know anything about.

If anyone can help, I'd be VERY appreciative.

[wadesworld]

[quote]Originally posted by Eyenovation:

A bad font? I've never heard of such a thing. How would I know?? How can I fix it?
The crashes seem to be happening a lot more.

Looking at that latest crash, I'm less suspicious of a bad font. I've seen fonts actually show up with a name like ??????.dfnt. That was crashing every app on the system until removed. But generally you have to just start removing fonts you're suspicious of and see if the problem goes away.

How can I test if my RAM is bad? How would I know which of the four sticks IS bad (should that be it).

Trial and error. Remove half the memory and see if the problem goes away. If it does, you know which half is bad.

Given that you're still getting crashes and in some fairly random places, I'm betting it's either memory or disk corruption at this point.

The easiest thing to check is the RAM. Run wihtout half your RAM for a day or two. If it crashes, put the other half in and run with that. If it still crashes, it's time to reformat and reinstall.

If it still crashes after that, it's time to take it in for service.

Wade

[Developer]

I guess it's bad RAM.