Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

OSX "unexpectedly quits" after waking up from sleep on Mac Pro

P

Pat H

macrumors member
Original poster
I've been a windows user all my life, and I switched to a mac a few weeks ago because I was tired of all the instability with windows and the crappy hardware that many PC manufacturers turned out. Since I got my Mac pro, OSX has "unexpectedly quit" 2 times after waking the computer up from sleep mode. I'm assuming this is the Mac equivalent of the blue screen of death, and quite frankly I haven't experienced an OS-wide malfunction in almost a year on any of my PC's.

I realize that OSX Leopard is still waiting for the 10.5.2 update, but just how unstable is .1? Somehow I doubt this is normal, and I'm wondering if it's because of installed software or some other issue in system settings. I still know relatively nothing about OSX vs what I know about Windows, so I'm trying not to pass judgement on the OS until I get some input. On a side note, Adobe Encore CS3 also isn't functioning on leopard even with the supposed compatibility updates, so right now I have a several hundred dollar software suite that's partially non-functional. So far this transition hasn't "just worked" by any means 🙁
 
As in you get a grey box asking you to turn off your computer? First, open disk utility and repair your permissions. If that doesn't help, I recommend you reinstall from the disks included with your computer. Just one in and restart holding down the "c" key until the apple appears. Proceed and you want to archive and install.
 
iToaster said:
As in you get a grey box asking you to turn off your computer? First, open disk utility and repair your permissions. If that doesn't help, I recommend you reinstall from the disks included with your computer. Just one in and restart holding down the "c" key until the apple appears. Proceed and you want to archive and install.
Click to expand...

Thanks. I'll try repairing the permissions and see if it happens again.
 
You can open up the Console (Applications/Utilities). Go to Open Quickly-->panic.log (that's the kernel panic log, aka crash log)

Copy and paste the last entry here; we can then read what it says and see if we can figure it out.
 
Did you upgrade the RAM on your mac pro?? Bad RAM or improperly installed RAM is one a pretty common cause for kernel panics on a mac.
 
Mechcozmo said:
You can open up the Console (Applications/Utilities). Go to Open Quickly-->panic.log (that's the kernel panic log, aka crash log)

Copy and paste the last entry here; we can then read what it says and see if we can figure it out.
Click to expand...

Ok, here goes.....


----------
Crash Log for 2-3-08
---------

Sun Feb 3 22:33:21 2008
panic(cpu 4 caller 0x001A7C7F): Kernel trap at 0x65726944, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x65726944, CR3: 0x0106f000, CR4: 0x00000660
EAX: 0x09dccd40, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x0bc02000
CR2: 0x65726944, EBP: 0x77d7fd18, ESI: 0x0a4f8800, EDI: 0x09926000
EFL: 0x00010206, EIP: 0x65726944, CS: 0x00000008, DS: 0x09670010
Error code: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x77d7fad8 : 0x12b0e1 (0x456c94 0x77d7fb0c 0x13321a 0x0)
0x77d7fb28 : 0x1a7c7f (0x460174 0x65726944 0xe 0x45f924)
0x77d7fc08 : 0x19e807 (0x77d7fc20 0x80 0x77d7fd18 0x65726944)
0x77d7fc18 : 0x65726944 (0xe 0x48 0x77d70010 0x420010)
0x77d7fd18 : 0x9dbb03 (0x9926000 0x287 0x77d7fd48 0xffffffc3)
0x77d7fd88 : 0x9e031a (0x9926000 0x0 0x0 0x77d7fe1c)
0x77d7fe38 : 0x9ccf72 (0x9926000 0x0 0x10 0x69373000)
0x77d7fe58 : 0x9b6196 (0x9e2bf80 0x96da410 0x77d7fec8 0x1a63c8)
0x77d7fe88 : 0x9b5f77 (0x69373000 0x1 0x13cffb 0x96da410)
0x77d7fea8 : 0x9b64dd (0x69373000 0x0 0x920ad7c9 0x0)
0x77d7fec8 : 0x9b3e5b (0x69373000 0x9f91f8 0x77d7fef8 0x402961)
0x77d7fef8 : 0x41ed75 (0x69373000 0xa4d0000 0x0 0x0)
0x77d7ff48 : 0x9b3fa7 (0x9bd2b80 0x9b3d2e 0xa4d0000 0x0)
0x77d7ff78 : 0x13ea34 (0x69373000 0x9cefb80 0x1a136f 0xb3825d0)
0x77d7ffc8 : 0x19e5dc (0x0 0x0 0x1a10b5 0xb381a78)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleFWAudio(2.4.0fc8)@0x9ab000->0x9f9fff
dependency: com.apple.iokit.IOFireWireFamily(3.4.0)@0x60f000
dependency: com.apple.iokit.IOFireWireAVC(2.2.1)@0x99b000
dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0x912000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9B2117

Kernel version:
Darwin Kernel Version 9.1.1: Fri Dec 14 19:00:14 PST 2007; root:xnu-1228.1.30~1/RELEASE_I386
System model name: MacPro3,1 (Mac-F42C88C8)
Click to expand...
 
f1 said:
Did you upgrade the RAM on your mac pro?? Bad RAM or improperly installed RAM is one a pretty common cause for kernel panics on a mac.
Click to expand...

I did actually, 4GB worth. But it's all registering in the system specs as "status: OK" and the sticks are apple certified, error correcting and equipped with heat sinks, so they're by no means garbage sticks (got 'em from transintl.com). But I'd really hate for this to be the problem because I'd rather not take out a mortgage to buy apple's ram.

Also, don't know if it would have anything to do with anything, but I did mistakenly install them improperly the first time (didn't pair them right), so the extra ones weren't registerring. But I went back in and moved the sticks to the proper configuration so they registered sucessfully. Did I maybe fry something? I really hope not 😱
 
Pat H said:
I did actually, 4GB worth. But it's all registering in the system specs as "status: OK" and the sticks are apple certified, error correcting and equipped with heat sinks, so they're by no means garbage sticks (got 'em from transintl.com). But I'd really hate for this to be the problem because I'd rather not take out a mortgage to buy apple's ram.

Also, don't know if it would have anything to do with anything, but I did mistakenly install them improperly the first time (didn't pair them right), so the extra ones weren't registerring. But I went back in and moved the sticks to the proper configuration so they registered sucessfully. Did I maybe fry something? I really hope not 😱
Click to expand...

Just because your RAM is showing up as ok in system profiler doesn't mean its not defective. I remeber when i upgraded the RAM in my macbook, it showed up in system profiler as being "ok" and i also ran Tech Tool Deluxe diagnostics and the RAM test passed. Had the RAM removed and went back to my reseller for a swap and everything was fine. I would suggest taking out your upgraded RAM and trying out your computer with just the standard apple ram it came with, and if that works you need to go back to wherever you bought the RAM and have it swapped. If your problems persist contact apple.
 
I have this problem OP

OP, I have this same problem. I have a Mac Pro (not this revision, but one revision back). When I sleep the computer there is a chance that the OS will unexpectedly quit and force a hard reset. This chance increases as the length of sleep increases. Sometimes it will sleep, then immediately wake up showing the "unexpected quit" grey box of death. Sometimes it will sleep and I can leave it on all night, and it will wake up normally. Usually if I leave it sleeped all night, when I wake it up, I have a kernel crash on my hands.

I'm pretty sure it's not our RAM. It is unclear why a RAM issue would only manifest itself in this way. I, too, have ECC / Heatsinked aftermarket RAM, from owc.

In my case I am pretty sure that it has something to do with one of my USB peripherals. Try this simple test: unplug all of your peripherals. Now sleep the computer and wake it up a hundred times. See if you can get it to crash. I can't. I'm starting to lean towards my Logitech MX revolution or my Griffin iMic as the problem, but I am not sure yet.

Here is a knowledgebase article. Please let me know what you've come up with.
http://docs.info.apple.com/article.html?artnum=303698

Edit: By the way, there are a few ways to sleep and wake up the computer while testing peripherals. One is to leave the keyboard in and use it to wake up, the power button to sleep, then leave the mouse in and check the keyboard. My feeling is that it probably is not the keyboard, though.

Edit: By the way, I was just checking your error log. It looks like a firewire audio device is the cause of your problems. If you have a firewire audio device plugged in to your computer, I would be mighty suspicious of it.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back