is something wrong with my brand new macbook???

Discussion in 'Mac Pro' started by bigben334, Jul 4, 2006.

  1. bigben334 macrumors regular

    Joined:
    Apr 30, 2005
    #1
    i just got my macbook last week and yesterday, while i was using safari, the screen dimmed and a message popped up saying that i had to "restart my computer by either holding the power button down for several seconds or by hitting the restart button"!!!!! as u can imagine, this scared me but i didnt panic and i just did wat the message said and my macbook was up and running again about a minute later...but then it just happened AGAIN today about 5 minutes ago....again nothing bad really happens...i just hold the power button down and shut the computer down then i just turn it back on and its fine again.....but somebody please tell me if i can do anything to prevent this....this is my first mac btw so somebody please help!!!
     
  2. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
  3. WildCowboy Administrator/Editor

    WildCowboy

    Staff Member

    Joined:
    Jan 20, 2005
    #3
    What you're experiencing are kernel panics. They are obviously not normal and could be an indication of a hardware problem. Have you made any modifications to your machine since you received it, such as adding RAM? Incorrectly installed or bad RAM can cause this. They can also occasionally be caused by software issues. If you haven't made any adjustments that could have caused this, you should contact Apple.
     
  4. WillMak macrumors 6502a

    Joined:
    Jul 29, 2005
    #4
    AHHH!!!!!!!! This happened to me once as well! I've had my macbook for about a month but it hasn't popped up since then. Is my macbook okay?
     
  5. bigben334 thread starter macrumors regular

    Joined:
    Apr 30, 2005
    #5
    yea...

    i put 2gb of ram into my computer...i really hope thats not the problem...i had a heart attack putting the ram in..i would hate to hav to deal with taht agiain :(....should i just archive and install mac osx....on the apple site it says that almost always fixes the problem
     
  6. WildCowboy Administrator/Editor

    WildCowboy

    Staff Member

    Joined:
    Jan 20, 2005
    #6
    If it's bad RAM or another hardware problem, reinstalling the OS almost certainly won't help. Follow the instructions in yellow's first link...take a look at the panic.log file to see if you can figure out what's causing the panics.
     
  7. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #7
    If you added RAM, then it's 90% likely that's the problem.. don't waste your time with a reinstall. Apple only says that because they want to cut down on the volume of support calls.

    Try running memtest on your RAM..
     
  8. Shadow macrumors 68000

    Shadow

    Joined:
    Feb 17, 2006
    Location:
    Keele, United Kingdom
    #8
    Yes, a kernel panic once in a while is normal, just as long its once every few months, not days ;) .
     
  9. bigben334 thread starter macrumors regular

    Joined:
    Apr 30, 2005
    #9
    Mon Jul 3 17:52:57 2006
    panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x20333921, CR3: 0x00d17000, CR4: 0x000006e0
    EAX: 0x20333920, EBX: 0x00000018, ECX: 0x24aebc8c, EDX: 0x00000018
    ESP: 0x20333921, EBP: 0x24aebad4, ESI: 0x03d62204, EDI: 0x03d62274
    EFL: 0x00010202, EIP: 0x008e623d, CS: 0x00000008, DS: 0x24ae0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24aeb954 : 0x128b5e (0x3bc46c 0x24aeb978 0x131bbc 0x0)
    0x24aeb994 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c)
    0x24aeba44 : 0x197c7d (0x24aeba58 0x24aebad4 0x8e623d 0x500048)
    0x24aeba50 : 0x8e623d (0x500048 0x3680010 0x36b0010 0x24ae0010)
    0x24aebad4 : 0x8e42a6 (0x3d62274 0x3679985e 0x8 0x50c435)
    0x24aebb24 : 0x8d9cb9 (0x3aac804 0x24aebc8c 0x36799800 0x50)
    0x24aebb84 : 0x8ea855 (0x380046c 0x24aebc8c 0x36799800 0x50)
    0x24aebce4 : 0x8fabd9 (0x380046c 0x366bf500 0x3dd8404 0x50)
    0x24aebd34 : 0x8eb9a5 (0x380046c 0x366bf500 0x3dd8404 0x50)
    0x24aebe24 : 0x8fb86a (0x380046c 0x366bf500 0x3dd8404 0x43)
    0x24aebf14 : 0x38dd6d (0x380029c 0x3958180 0x1 0x12)
    0x24aebf64 : 0x38cf19 (0x3958180 0x0 0x0 0x198ce5)
    0x24aebf94 : 0x38cc3d (0x395d540 0x368cdc0 0x0 0x450)
    0x24aebfd4 : 0x197b19 (0x395d540 0x0 0x3a884f8 0x18) Backtrace terminated-invalid frame pointer 0x0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AirPortAtheros5424(104.1)@0x8d8000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x67a000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IO80211Family(112.1)@0x8bf000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *********

    Tue Jul 4 16:04:20 2006
    panic(cpu 0 caller 0x0019CADF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0xefaea182, CR3: 0x00d17000, CR4: 0x000006e0
    EAX: 0xefaea181, EBX: 0x00000009, ECX: 0x24ab3c8c, EDX: 0x00000009
    ESP: 0xefaea182, EBP: 0x24ab3ad4, ESI: 0x03ad6804, EDI: 0x03ad6878
    EFL: 0x00010286, EIP: 0x008e623d, CS: 0x00000008, DS: 0xfff30010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x24ab3954 : 0x128b5e (0x3bc46c 0x24ab3978 0x131bbc 0x0)
    0x24ab3994 : 0x19cadf (0x3c18e4 0x0 0xe 0x3c169c)
    0x24ab3a44 : 0x197c7d (0x24ab3a58 0x24ab3ad4 0x8e623d 0x120048)
    0x24ab3a50 : 0x8e623d (0x120048 0x10 0x10 0xfff30010)
    0x24ab3ad4 : 0x8e42ea (0x3ad6878 0x366b8045 0x8 0x50c435)
    0x24ab3b24 : 0x8d9cb9 (0x3a9e804 0x24ab3c8c 0x366b8000 0x50)
    0x24ab3b84 : 0x8ea855 (0x37f146c 0x24ab3c8c 0x366b8000 0x50)
    0x24ab3ce4 : 0x8fabd9 (0x37f146c 0x366b6400 0x3bf0004 0x50)
    0x24ab3d34 : 0x8eb9a5 (0x37f146c 0x366b6400 0x3bf0004 0x50)
    0x24ab3e24 : 0x8fb86a (0x37f146c 0x366b6400 0x3bf0004 0x38)
    0x24ab3f14 : 0x38dd6d (0x37f129c 0x394a200 0x1 0x3a7a6a8)
    0x24ab3f64 : 0x38cf19 (0x394a200 0x135d18 0x0 0x3a7a6a8)
    0x24ab3f94 : 0x38cc3d (0x3a68140 0x3a68140 0x0 0x450)
    0x24ab3fd4 : 0x197b19 (0x3a68140 0x0 0x3a7a920 0x9) Backtrace terminated-invalid frame pointer 0x0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AirPortAtheros5424(104.1)@0x8d8000
    dependency: com.apple.iokit.IONetworkingFamily(1.5.0)@0x67a000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IO80211Family(112.1)@0x8bf000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *********

    thats my panic.log....i dunno exactly how to read it and figure out wats wrong so if somebody could please figure it out for me that would be greatly appreciated
     
  10. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #10
    Looks to me like a problem with the AirPort (Extreme) card.
    Maybe you bumped it when you were putting in your RAM?

    Try reseating that.
     
  11. erikamsterdam macrumors regular

    erikamsterdam

    Joined:
    Apr 21, 2006
    Location:
    amsterdam
    #11
    Did you push hard putting the memory in? Lots of problems are caused by memory that is not in the slot completely.
    Or, just take it out, and put it back in. Some dirt on a contact or so can also cause trouble. Be sure though that you are grounded when handling memory, you would not be the first person blowing electronics up with rubber shoes on carpet :(
     
  12. bigben334 thread starter macrumors regular

    Joined:
    Apr 30, 2005
    #12
    .....

    try reseating that???

    wat does that mean and how do i do it? thanks
     
  13. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #13
    Maybe you should take it into a Certified Apple Repair center.
     
  14. bigben334 thread starter macrumors regular

    Joined:
    Apr 30, 2005
    #14
    ok...

    i took out each stick of ram...and i put them back in...i did notice that wen i ejected the stick of ram closer to the side of the macbook...it ejected it crooked...like kind of sideways...i had trouble getting it out and then back in...does that mean anything? thanks again
     
  15. Bern macrumors 68000

    Bern

    Joined:
    Nov 10, 2004
    Location:
    Australia
    #15

    The ram is very difficult to get seated, when you are screwing the "L" shaped bracket back into place is it sitting flush all the way around? If not then you probably don't have the ram in properly. I know the ram closest to the hard drive is the hardest to get into the slot, I actually bruised my finger tips getting that one in properly.
     
  16. risc macrumors 68030

    risc

    Joined:
    Jul 23, 2004
    Location:
    Melbourne, Australia
    #16
    You're kidding right? On a computer where the hardware and OS is controlled by 1 company you should never see kernel panics. :rolleyes:
     
  17. Bern macrumors 68000

    Bern

    Joined:
    Nov 10, 2004
    Location:
    Australia
    #17

    LOL, this is not windows. Kernel panics are not normal. A process of elimination needs to be started, beginning with that ram I'd say. Worse case I guess is the motherboard may be flaky, but that is worse case.
     
  18. Shadow macrumors 68000

    Shadow

    Joined:
    Feb 17, 2006
    Location:
    Keele, United Kingdom
    #18
    Yeh, I know. I've just sent my Mac back, and am now facing several error messages on Windows. Must have been the Windows user in me talking :p.
     
  19. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #19
    I think ChrisG's point was.. a kernel panic once a month.. while not good, and not normal, is not worth getting your panties in a bnuch over and flying into a tizzy because your Mac is dying. Certainly one should troubleshoot ths issues, but it's not ultra-critical. Once every couple days.. now that's a different story.
     
  20. gekko513 macrumors 603

    gekko513

    Joined:
    Oct 16, 2003
    #20
    I've never had one, and I've used five different Macs over a period of three years.
     
  21. bigben334 thread starter macrumors regular

    Joined:
    Apr 30, 2005
    #21
    ok well....

    i ran memtest on my 2gb of ram and it passed with flying colors TWICE....so does this mean that the problem definitely is not my ram? thanks
     
  22. yellow Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #22
    As I said, it's not the RAM.. according to your panic logs it's your AirPort card causing the kernel panic.
     

Share This Page