Unknown crashes

Discussion in 'General Mac Discussion' started by EGT, Feb 18, 2005.

Most Liked Posts
  1. EGT, Feb 18, 2005

    EGT macrumors 68000

    EGT

    Joined:
    Sep 4, 2003
    #1
    For some reason I've been getting a lot of crashes lately and I don't know what’s causing them. I don't mean application crashes, i mean that god awful black out of the screen and the "Hold down your power button to restart" ... whatever it is.

    I know there is some way of looking up crash logs. Where can i find these and what should i look for to tell me where the problem is?

    I haven't installed any new hardware since i bought RAM about 7 months ago so i don't think that's the problem. When it happened again tonight, i had just pressed "apple-shift-I" to import some photos to iPhoto. Other times it's happened just when listening to songs on iTunes. They froze in a short, continuous loop and then that ugly screen was staring at me :( ... so painful.

    I'm thinking it might be something to do with having the iPod connected at the time through firewire (???) Other than that, i have no ideas.
     
    share
    + Quote Reply
  2. mklos, Feb 18, 2005

    mklos macrumors 68000

    mklos

    Joined:
    Dec 4, 2002
    Location:
    My house!
    #2
    Take that extra RAM out and see if it still happens. When OS X continuously crashes all of a sudden then its mostly likely a hardware problem. The easiest thing to start with is the RAM. Put in ONLY the stardard RAM.

    I would also look at running the hardware test CD that came with your Mac. First though I would take out the RAM and see if that helps.

    If you can make your OS run long enough, try repairing the permissions. I doubt that will help, but it never helps to trying little things like that.
     
    share
    + Quote Reply
  3. john1123, Feb 18, 2005

    john1123 macrumors regular

    john1123

    Joined:
    Jan 26, 2005
    Location:
    Down Under
    #3
    the crash logs can be viewed using the console (Applications:Utilities). Once you're in the console, expand "/Library/Logs" and there should be a CrashReporter with all the logs of system crashes in it.

    Otherwise you might want to Repair Permission and run the maintenance scripts. There is a good program called Onyx (freeware) that can take care of all things maintenance for you.
     
    share
    + Quote Reply
  4. EGT, Feb 18, 2005

    EGT thread starter macrumors 68000

    EGT

    Joined:
    Sep 4, 2003
    #4
    ok, i will try hardware test in the morning and also have a look at the crash logs.

    I should have metioned that i have the latest version of Onyx but I've been using Macaroni to run the maintenance scripts etc so things should be running sweet.

    thanks :)
     
    share
    + Quote Reply
  5. EGT, Feb 21, 2005

    EGT thread starter macrumors 68000

    EGT

    Joined:
    Sep 4, 2003
    #5
    I'm still getting these crashes :( I've just ran the extended hardware test and there seems to be no problems with memory or Logicboard etc.

    Should just reinstall the OS from scratch?
     
    share
    + Quote Reply
  6. yellow, Feb 21, 2005

    yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #6
    1) What you described are kernel panics. Those logs are found on /Library/Logs/panics.log

    2) The hardware test CD that apple gives you sucks. Try using an application like memtest to accurately test your memory. Let it run for along time.

    3) Unplug all your peripherals except keyboard/mouse/monitor. If you're using a 3rd party mouse or keyboard, go back to the Apple ones. See if your kernel panics go away. If they do, add back peripherals one at a time and use the Mac until you find the culprit.
     
    share
    + Quote Reply
  7. EGT, Feb 21, 2005

    EGT thread starter macrumors 68000

    EGT

    Joined:
    Sep 4, 2003
    #7
    The panic logs show this:

    Sat Feb 19 00:08:12 2005




    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000048007F4 PC=0x0000000000581368
    Latest crash info for cpu 0:
    Exception state (sv=0x2A670C80)
    PC=0x00581368; MSR=0x00009030; DAR=0x048007F4; DSISR=0x42000000; LR=0x0057E948; R1=0x17523A40; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x00581458 0x0057E948 0x00520F0C 0x0051F9D4 0x00520F0C 0x006EB3B8 0x006EB0CC 0x006EC324
    0x006EC4AC 0x0026762C 0x0026650C 0x00266470
    Kernel loadable modules in backtrace (with dependencies):
    com.draytek.driver.xUTA(1.0.0d1)@0x57c000
    dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49a000
    com.apple.driver.AppleUSBOHCI(2.1.4)@0x6e8000
    dependency: com.apple.iokit.IOPCIFamily(1.4)@0x395000
    dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    Proceeding back via exception chain:
    Exception state (sv=0x2A670C80)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x2A01CA00)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

    Kernel version:
    Darwin Kernel Version 7.8.0:
    Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC


    panic(cpu 0): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC
    Proceeding back via exception chain:
    Exception state (sv=0x2A670C80)
    PC=0x00581368; MSR=0x00009030; DAR=0x048007F4; DSISR=0x42000000; LR=0x0057E948; R1=0x17523A40; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x00581458 0x0057E948 0x00520F0C 0x0051F9D4 0x00520F0C 0x006EB3B8 0x006EB0CC 0x006EC324
    0x006EC4AC 0x0026762C 0x0026650C 0x00266470
    Kernel loadable modules in backtrace (with dependencies):
    com.draytek.driver.xUTA(1.0.0d1)@0x57c000
    dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49a000
    com.apple.driver.AppleUSBOHCI(2.1.4)@0x6e8000
    dependency: com.apple.iokit.IOPCIFamily(1.4)@0x395000
    dependency: com.apple.iokit.IOUSBFamilp
    *********

    Mon Feb 21 19:32:47 2005




    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000018 PC=0x0000000000095014
    Latest crash info for cpu 0:
    Exception state (sv=0x2AC24C80)
    PC=0x00095014; MSR=0x00009030; DAR=0x00000018; DSISR=0x42000000; LR=0x005AAD08; R1=0x176532C0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x005AACE4 0x00593F60 0x0059A650 0x0059E5D8 0x005A2304 0x005A208C 0x005A27C8 0x005A2648
    0x0059C4B8 0x0059CF04 0x0059D700 0x00592094 0x005901E8 0x00593CB4 0x00593B6C 0x0058CAE4
    0x00580B6C 0x0057E984 0x00520F0C 0x0051F9D4 0x00520F0C 0x006EB3B8 0x006EB0CC 0x006EC324
    0x006EC4AC 0x0026762C 0x0026650C 0x00266470
    Kernel loadable modules in backtrace (with dependencies):
    com.draytek.driver.xUTA(1.0.0d1)@0x57c000
    dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    dependency: com.apple.iokit.IOSerialFamily(6.0.1d20)@0x49a000
    com.apple.driver.AppleUSBOHCI(2.1.4)@0x6e8000
    dependency: com.apple.iokit.IOPCIFamily(1.4)@0x395000
    dependency: com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    com.apple.iokit.IOUSBFamily(2.1.5)@0x51d000
    Proceeding back via exception chain:
    Exception state (sv=0x2AC24C80)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x2A029000)
    PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

    Kernel version:
    Darwin Kernel Version 7.8.0:
    Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC


    panic(cpu 0): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC
    Proceeding back via exception chain:
    Exception state (sv=0x2AC24C80)
    PC=0x00095014; MSR=0x00009030; DAR=0x00000018; DSISR=0x42000000; LR=0x005AAD08; R1=0x176532C0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x005AACE4 0x00593F60 0x0059A650 0x0059E5D8 0x005A2304 0x005A208C 0x005A27C8 0x005A2648
    0x0059C4B8 0x0059CF04 0x0059D700 0x00592094 0x005901E8 0x00593CB4 0x00593B6C 0x0058CAE4
    0x00580B6C 0x0057E984 0x00520F0C 0x0051F9D4 0x00520F0C 0x006EB3B8 0x006EB0CC 0x006EC324
    0x006EC4AC 0x0026762C 0x0026650C 0x00266470
    Kernel loadable modules in bac`
    *********

    Way over my head :p

    Going to try memtest now, post the results later on or tomorrow.

    The only peripherals i have connected are an ISDN USD Adaptor and a set of speakers. I just use the powerbooks keyboard and trackpad.

    Thanks for helping out.
     
    share
    + Quote Reply
  8. yellow, Feb 21, 2005

    yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #8
    com.draytek.driver.xUTA(1.0.0d1)@0x57c000

    ANd then mention of the apple USB driver.

    Looks to me like your USB ADSL modem is the culprit, assuming that's what the draytek thing is all about.
     
    share
    + Quote Reply
  9. EGT, Feb 21, 2005

    EGT thread starter macrumors 68000

    EGT

    Joined:
    Sep 4, 2003
    #9
    Phew! I was thinking that it was something more serious for a while. You've made my day! Thanks for the help!!!

    :) :)
     
    share
    + Quote Reply
  10. boneca, Feb 22, 2005

    boneca macrumors 6502

    Joined:
    Jan 2, 2005
    Location:
    Boston, MA
    #10
    sorry I'm kinda new to Mac can you point me how to get there (crash logs) exactly. I tried to locate Library/Logs under Applications but wasn't able to.

    TIA
     
    share
    + Quote Reply
  11. yellow, Feb 25, 2005

    yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #11
    ~/Library/Logs/CrashReporter/
     
    share
    + Quote Reply
(You must log in or sign up to post here.)

Share This Page