My G5 is hanging up way too often - why is this?

kabzkabz
Posted:
in Genius Bar edited January 2014
It seems as if every week, my G5 gets the gray rolldown screen "You must Restart Your Computer"



In the past week....it has happened almost every day, sometimes twice a day!



What am I doing? All I'm doing generally is using my browser.

I use Firefox, and I am on OSX 10.3.9



Now I noticed that this happens during

scrolling



apparently Firefox doesn't like when you grab the scroll bar with your mouse and move it up and down.

Once I do that, I am susceptible to a hang up or so it seems, but that seems so silly at the same time. However it almost exclusively happens when I am scrolling with my wheel (if I have done the drag scroll already) or use the page down key, or again drag the scroll bar.



Now does anyone have any ideas if this is even the cause or a weird coincidence? Is there a way I can fix this or check for a reason why this could be happening. Its terribly annoying, I have had this G5 for maybe 4 months now only

Comments

  • Reply 1 of 16
    the cool gutthe cool gut Posts: 1,714member
    That's a kernal panic and pretty serious. Are you running the os off an external hard drive? What do you have plugged in the computer. Unless someone here can think of something else, I would recommend running disk warrior, or re-installing the OS.
  • Reply 2 of 16
    karl kuehnkarl kuehn Posts: 756member
    The usual suspects are memory and peripherals (non-apple ones first). With the scrolling thing I am a little concerned with the video sub-system.
  • Reply 3 of 16
    kabzkabz Posts: 53member
    well.....my RAM was bought separately.

    I am using a Microsoft Mouse, but everything else besides the speakers is straight from Apple.

    Should I really be concerned? I am trying to download Disk Warrior, but in the meantime is there something Free that I can use to ease my worries.



    I mean its not like I can't use my mac at all, its just that this happens occasionally and sometimes more often.



    I don't want to have to have a headace to deal with now....so let me know what I can do besides Disk Warrior to see if I should actually worry
  • Reply 4 of 16
    wingnutwingnut Posts: 197member
    I get a lockup occasionally on my PM, too. It's not under high-load, like one would expect either. The only non-Apple components are my logitech mouse and 1GB of dual channel Corsair XMS. I recently put in an ATI 9800pro, but that was made for the G5 exclusively. I don't get locks everyday or anything, but I did have 2 crashes since I plugged a second monitor into the 9800. \
  • Reply 5 of 16
    kabzkabz Posts: 53member
    I never thought about the total number of times it has happened.



    I would say more than 10 definitely but not over 20



    And this is since March of this year.



    meh.....I'm starting to not worry so much anymore
  • Reply 6 of 16
    the cool gutthe cool gut Posts: 1,714member
    What kind of Mac do you have?
  • Reply 7 of 16
    mikefmikef Posts: 698member
    Remove all the non-Apple hardware and do the same operation and see if there's still a problem.



    I'd be very concerned about this many crashes in 5 months. It's certainly not normal.
  • Reply 8 of 16
    kabzkabz Posts: 53member
    Quote:

    Originally posted by the cool gut

    What kind of Mac do you have?



    PowerMac G5
  • Reply 9 of 16
    kabzkabz Posts: 53member
    Ok....

    not quite sure how Disk Warrior works but.



    I ran the Hardware Device Test and it said "Functioning Normally"



    Now I ran the Directory HD Graph, and it says 31% out of order...I don't know if this is normal but thats all I can test now as it won't let me choose "rebuild"



    Anyone care to analyze what these results mean?
  • Reply 10 of 16
    wingnutwingnut Posts: 197member
    My guess is that it has something to do with fragmenting on the drive, but I'm not totally sure.

  • Reply 11 of 16
    kabzkabz Posts: 53member
    I think it may just have to do with overheating maybe?

    I live in sunny Florida, and my tower is right next to the window....plus the room has poor ventilation so maybe thats a contributing factor.

    Anyways....thanks for the replies
  • Reply 12 of 16
    messiahmessiah Posts: 1,689member
    I had exactly the same problem ? I got about four kernel panics a day ? and I never got to the bottom of it.



    Moving from Panther to Tiger fixed it for me. I've been running Tiger since day one, and I haven't seen a single kernel panic. Not one.



    Panther was an absolute disaster for me.
  • Reply 13 of 16
    kabzkabz Posts: 53member
    Quote:

    Originally posted by Messiah

    I had exactly the same problem ? I got about four kernel panics a day ? and I never got to the bottom of it.



    Moving from Panther to Tiger fixed it for me. I've been running Tiger since day one, and I haven't seen a single kernel panic. Not one.



    Panther was an absolute disaster for me.



    I think I may just have to do that...



    thanks man
  • Reply 14 of 16
    mr. hmr. h Posts: 4,870member
    Kernel panics are caused by serious bugs in either the kernel or a kernel extension (device driver), or by a hardware problem. Normal applications (such as firefox, finder etc.) and things like hard drive fragmentation really should not be able to cause a kernel panic.



    The hot environment in which you are using the computer could have an affect.



    In order to try and narrow down on the culprit of your problems:



    1) launch the "console" application which can be found in /applications/utilities/



    2) When you launch console, it should present a window with a source list down the left hand side (if there is no source list, press the "logs" button in the toolbar).



    3) If you click on the disclosure triangle next to /library/logs (NOT ~/library/logs), there should be an entry called "panic.log"; click on it. In the main part of the window, a load of text should appear, looking pretty unintelligible with weird hex numbers like 0x00000000001EA42C all over the place and the word "backtrace" mentioned every so often.



    4) Copy a goodly amount of that gobledegook and paste it here, maybe we'll be able to find something useful. If we can't, you could always try the Apple Discussions route by following these instructions



    Hope that helps and that it wasn't too patronising.
  • Reply 15 of 16
    kabzkabz Posts: 53member
    thanks.....



    here is some goodness

    ______________



    *********



    Thu Jun 16 22:06:00 2005









    Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000A000C514 PC=0x000000000002A300

    Latest crash info for cpu 0:

    Exception state (sv=0x3371FA00)

    PC=0x0002A300; MSR=0x00089030; DAR=0xA000C514; DSISR=0x0A000000; LR=0x0002A300; R1=0x1D813CC0; XCP=0x0000001C (0x700 - Program)

    Backtrace:

    0x00312CA0

    backtrace terminated - unaligned frame address: 0xA1B1C1D3



    Proceeding back via exception chain:

    Exception state (sv=0x3371FA00)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x33A8E000)

    PC=0x91B92308; MSR=0x0200F930; DAR=0x00767C0C; DSISR=0x40000000; LR=0x91B8363C; R1=0xBFFF93A0; XCP=0x0000000C (0x300 - Data access)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    panic(cpu 1): We can't get a mutex interlock lock on mutex_lock



    Latest stack backtrace for cpu 1:

    Backtrace:

    0x00083498 0x0008397C 0x0001EDA4 0x0008D894 0x0008D86C 0x00018144 0x0001CA48 0x00041848

    0x00021668 0x0001BCE8 0x0001C0F0 0x00094318 0xFFC7C7C7

    Proceeding back via exception chain:

    Exception state (sv=0x34959A00)

    PC=0x8FE26728; MSR=0x0000D030; DAR=0xF0080EF4; DSISR=0x42000000; LR=0x8FE31F34; R1=0xF00807E0; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC







    *********



    Sat Jun 25 16:11:43 2005









    Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x00000000E0112570 PC=0x0000000000086D00

    Latest crash info for cpu 0:

    Exception state (sv=0x347D8C80)

    PC=0x00086D00; MSR=0x00081030; DAR=0xE0112570; DSISR=0x42000000; LR=0x00086CF8; R1=0x1D88B8C0; XCP=0x0000001C (0x700 - Program)

    Backtrace:

    0x00515714 0x0008618C 0x000852CC 0x00058C38 0x00090B00 0x0009402C 0x00093D30 0x00013B2C

    0x0001B028 0x0001B11C 0x00015B9C

    Kernel loadable modules in backtrace (with dependencies):

    com.apple.iokit.IOUSBFamily(2.1.5)@0x503000

    Proceeding back via exception chain:

    Exception state (sv=0x347D8C80)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x337CAA00)

    PC=0x00095488; MSR=0x00009030; DAR=0xE0112570; DSISR=0x42000000; LR=0x00093D7C; R1=0x1D88BD20; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00093D30 0x00013B2C 0x0001B028 0x0001B11C 0x00015B9C

    Exception state (sv=0x3413B000)

    PC=0x90007878; MSR=0x0000D030; DAR=0xF0112EF4; DSISR=0x42000000; LR=0x900073F8; R1=0xF01124D0; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    panic(cpu 0): 0x700 - Program

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C

    Proceeding back via exception chain:

    Exception state (sv=0x347D8C80)

    PC=0x00086D00; MSR=0x00081030; DAR=0xE0112570; DSISR=0x42000000; LR=0x00086CF8; R1=0x1D88B8C0; XCP=0x0000001C (0x700 - Program)

    Backtrace:

    0x00515714 0x0008618C 0x000852CC 0x00058C38 0x00090B00 0x0009402C 0x00093D30 0x00013B2C

    0x0001B028 0x0001B11C 0x00015B9C

    Kernel loadable modules in backtrace (with dependencies):

    com.apple.iokit.IOUSBFamily(2.1.5)@0x503000

    Exception state (sv=0x337CAA00)

    PC=0x00095488; MSR=0x00009030; DAR=0xE0112570; DSISR=0x42000000; LR=0x00093D7C; R1=0x1D88BD20; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00093D30 0x00013B2C 0x0001B028 0x0001B11C 0x00015B9C

    Exception state (sv=0x3413B000)

    PC=0x90007878; MSR=0x0000D030; DAR=0xF0112EF4; DSISR=0x42000000; LR=0x900073F8; R1=0xF01124D0; XCP=0x00000030 (0xC00 - System call)



    Kernel version:

    Darwin Kernel Versi`

    *********



    Tue Jun 28 00:44:52 2005









    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000036C563C0 PC=0x0000000000087104

    Latest crash info for cpu 0:

    Exception state (sv=0x00AA2780)

    PC=0x00087104; MSR=0x00009030; DAR=0x36C563C0; DSISR=0x42000000; LR=0x00087100; R1=0x1D993C40; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00338000 0x0008618C 0x000852CC 0x00058C38 0x00091074 0x0009402C

    backtrace terminated - frame not mapped or invalid: 0xBFFFF810



    Proceeding back via exception chain:

    Exception state (sv=0x00AA2780)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x337CA280)

    PC=0x901C17A0; MSR=0x0000D030; DAR=0xA01C229C; DSISR=0x40000000; LR=0x901C16E0; R1=0xBFFFF810; XCP=0x0000000C (0x300 - Data access)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    panic(cpu 0): 0x300 - Data access

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C

    Proceeding back via exception chain:

    Exception state (sv=0x00AA2780)

    PC=0x00087104; MSR=0x00009030; DAR=0x36C563C0; DSISR=0x42000000; LR=0x00087100; R1=0x1D993C40; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00338000 0x0008618C 0x000852CC 0x00058C38 0x00091074 0x0009402C

    backtrace terminated - frame not mapped or invalid: 0xBFFFF810



    Exception state (sv=0x337CA280)

    PC=0x901C17A0; MSR=0x0000D030; DAR=0xA01C229C; DSISR=0x40000000; LR=0x901C16E0; R1=0xBFFFF810; XCP=0x0000000C (0x300 - Data access)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    *********



    Tue Jun 28 18:39:23 2005









    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000036C563C0 PC=0x0000000000087104

    Latest crash info for cpu 0:

    Exception state (sv=0x00AA2780)

    PC=0x00087104; MSR=0x00009030; DAR=0x36C563C0; DSISR=0x42000000; LR=0x00087100; R1=0x1D993C40; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00338000 0x0008618C 0x000852CC 0x00058C38 0x00091074 0x0009402C

    backtrace terminated - frame not mapped or invalid: 0xBFFFF810



    Proceeding back via exception chain:

    Exception state (sv=0x00AA2780)

    previously dumped as "Latest" state. skipping...

    Exception state (sv=0x337CA280)

    PC=0x901C17A0; MSR=0x0000D030; DAR=0xA01C229C; DSISR=0x40000000; LR=0x901C16E0; R1=0xBFFFF810; XCP=0x0000000C (0x300 - Data access)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    panic(cpu 0): 0x300 - Data access

    Latest stack backtrace for cpu 0:

    Backtrace:

    0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C

    Proceeding back via exception chain:

    Exception state (sv=0x00AA2780)

    PC=0x00087104; MSR=0x00009030; DAR=0x36C563C0; DSISR=0x42000000; LR=0x00087100; R1=0x1D993C40; XCP=0x0000000C (0x300 - Data access)

    Backtrace:

    0x00338000 0x0008618C 0x000852CC 0x00058C38 0x00091074 0x0009402C

    backtrace terminated - frame not mapped or invalid: 0xBFFFF810



    Exception state (sv=0x337CA280)

    PC=0x901C17A0; MSR=0x0000D030; DAR=0xA01C229C; DSISR=0x40000000; LR=0x901C16E0; R1=0xBFFFF810; XCP=0x0000000C (0x300 - Data access)



    Kernel version:

    Darwin Kernel Version 7.9.0:

    Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC





    *********
  • Reply 16 of 16
    mr. hmr. h Posts: 4,870member
    hmmm...



    on the face of it, there isn't any one thing that is causing the kernel panics. That would probably lead me to suspect the RAM.



    You could try all of the usual voodoo:



    Repair permissions



    Repair any hard drive problems (boot from the OS X install CD 1 that came with your machine, when the machine is booted, instead of running the installer, launch disk utility from the apple menu and run disk first aid)



    reset PRAM and NVRAM



    If once you have done all this, you are still having regular panics, try taking out the third party RAM. If you are still having panics after that, take it to a genius bar. You really shouldn't have to face this many panics. I think I've had a total of about 5 panics since OS X public beta.
Sign In or Register to comment.