Forums » MacOS X
Out of curiosity are you running a Radeon? Last I checked there was still a very long standing and obnoxious crashing bug related to running with multisampling on.
im not even running vendetta! im running safari and itunes.
YEESH. That's not good thing. Have you tried running a full memory test?
f that it only happened after upgrading to 10.4.7
You're right. It's not prudent to investigate the most common cause of OS crashes. After all, it's IMPOSSIBLE that your memory could have gone bad some time in the past couple of weeks, right? Wait. You're a troll. You complain in every forum about your hardware hard-locking and how much such-and-such sucks. Why am I feeding you?
watch your mouth.
the most common cause of OSes locking up is arrogant programmers who think they are gods gift to creation and their shit doesnt stink, like Linus Torvalds in the 2.6 kernel tree, like Bill Gates in the 1990s, like Mac OS 7, 8, and 9, and like Mac OS 10.4.7.
RAM can go bad, but almost never does, its a commonly understood phenomena of electronics engineering.
the most common cause of OSes locking up is arrogant programmers who think they are gods gift to creation and their shit doesnt stink, like Linus Torvalds in the 2.6 kernel tree, like Bill Gates in the 1990s, like Mac OS 7, 8, and 9, and like Mac OS 10.4.7.
RAM can go bad, but almost never does, its a commonly understood phenomena of electronics engineering.
It's true, RAM going bad is indeed a rare occurence! That's not to say that it's impossible that it's happened. It's a very reasonable thing to check and it is indeed one of the most common explanation of random crashses. (Other hardware failures and core level software problems sharing the good company.) It does no harm to check what the cause is, and unlike asuming the cause blindly it ha s a fairly good chance of at least making some sort of progress as you can either check off one possibility or find your culprit.
Likewise if you're having crashes post 10.4.7, something indeed is wrong. You're crashing after all. But if most people are running along nice and smoothly then logically you should still be investigating any possible cause rather than just pointing the finger.
Likewise if you're having crashes post 10.4.7, something indeed is wrong. You're crashing after all. But if most people are running along nice and smoothly then logically you should still be investigating any possible cause rather than just pointing the finger.
Still running 10.4.7, still no unexpected crashes, except some software, like VLC or Tomato, during high CPU workload intervals. On a heavily-used PBook G4 867, too.
With faulty RAM, and a Radeon graphics card.
With faulty RAM, and a Radeon graphics card.
no problems here, running 10.4.7 for quite some time....
Hmmm... Ananzi, you're absolutely right. That's why Mac's OS:X 10.4.7 only fails for YOU, because it's horrible software that sucks and doesn't work right, and the programmers were arrogant buffoons. That's why several million Mac users aren't having problems, but you are.
Oh, wait, I just checked and I haven't rebooted or had a program crash since I installed 10.4.7. Could it possibly be that the problems you're encountering maybe AREN'T universal to the operating system?
Nah. You go on and blame everyone else for your own problems. I find it amusing.
~D.
"Nigel"
Oh, wait, I just checked and I haven't rebooted or had a program crash since I installed 10.4.7. Could it possibly be that the problems you're encountering maybe AREN'T universal to the operating system?
Nah. You go on and blame everyone else for your own problems. I find it amusing.
~D.
"Nigel"
Hear hear
Running 10.4.7 on a macbook (non pro) with 2gb of ram and no problems.
Except some weird screen redraw issues on safari after using parallales.
Except some weird screen redraw issues on safari after using parallales.
Running OSX 10.4.7 on a three year old 1 Ghz x 2 G4. 1.5 G RAM. No crashes
of ANY kind.
of ANY kind.
in the history of personal computing, most lockups are caused by bad programming, bad testing, bad product development, etc, not by bad RAM. statistically, if one were to bet money, one should bet money not on RAM but on software flaws.
http://www.macintouch.com/readerreports/macosx10_4_7/topic4303.html
http://www.macfixitforums.com/showflat.php?Cat=&Board=tiger&Number=771846&page=0&view=collapsed&sb=5&o=31&fpart=1
http://www.macfixitforums.com/showflat.php?Cat=&Board=tiger&Number=769075&page=0&view=collapsed&sb=5&o=31
http://forums.macosxhints.com/archive/index.php/t-57595.html
http://www.quark.com/service/forums/viewtopic.php?t=13192
http://trac.adiumx.com/ticket/4371
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
http://www.macintouch.com/readerreports/macosx10_4_7/topic4303.html
http://www.macfixitforums.com/showflat.php?Cat=&Board=tiger&Number=771846&page=0&view=collapsed&sb=5&o=31&fpart=1
http://www.macfixitforums.com/showflat.php?Cat=&Board=tiger&Number=769075&page=0&view=collapsed&sb=5&o=31
http://forums.macosxhints.com/archive/index.php/t-57595.html
http://www.quark.com/service/forums/viewtopic.php?t=13192
http://trac.adiumx.com/ticket/4371
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
http://www.newsgator.com/forum/shwmessage.aspx?ForumID=9&MessageID=19564
also i dont know how to run a memory test on a mac. and this machine wont boot linux CDROMS (known hardware design flaw)
No one here is saying that bugs don't happen, by far. Simply that if you're having lots of lockups, and no one else is; clearly the problem lies in something specific with your setup. That's just basic reasoning there. So listing reports of there being bugs in software doesn't help you any.
Also I find it rather cute that in spite of that, only two out of nine (scratch that, the last three are all the same link, so seven!) links reports of any freezes! (Considering the first one's a big bad list of 10.4.7 bugs and only one person mentions a lock up - and even then not random while using as you report, that's pretty good!) Again, stop blindly pointing your finger or at least find someone else having the same problem you report.
As for testing your memory, http://www.memtestosx.org/ will get you started. It's recommended you run it from single user mode that way it's able to test all your memory. (It can't test what's being used by the system if you boot up into OS X proper.) It'll take a while, especially if you have a lot of RAM as it's quite extensive. If there's a problem there, it'll spot it. Also keep in mind that even if the RAM passes, that doesn't mean that something else isn't wrong other than the freaking software. Several Mac models have sported bad boards elsewhere, and G5's are quite prone towards heat related crashes due to dusty video cards.
Also I find it rather cute that in spite of that, only two out of nine (scratch that, the last three are all the same link, so seven!) links reports of any freezes! (Considering the first one's a big bad list of 10.4.7 bugs and only one person mentions a lock up - and even then not random while using as you report, that's pretty good!) Again, stop blindly pointing your finger or at least find someone else having the same problem you report.
As for testing your memory, http://www.memtestosx.org/ will get you started. It's recommended you run it from single user mode that way it's able to test all your memory. (It can't test what's being used by the system if you boot up into OS X proper.) It'll take a while, especially if you have a lot of RAM as it's quite extensive. If there's a problem there, it'll spot it. Also keep in mind that even if the RAM passes, that doesn't mean that something else isn't wrong other than the freaking software. Several Mac models have sported bad boards elsewhere, and G5's are quite prone towards heat related crashes due to dusty video cards.
Most G3 and upwards Apple boxes should boot under ubuntu for PPC