GaBeech

Q: Late 2006 iMac, Lines, Kernel Panic, Freeze, Reboot, Restart, Serial W8 ?

Hello,

Let me start by explaining the method I am initially going to adopt in my search for answers;

•All of the keywords and more that would not fit in the title space, relate to my problem.
•I think the *iMac Serial* holds the key to mine and possibly a lot of other peoples search for answers.
•My second post will explain what I know about the Serial and the information it provides.
•I have a strong feeling that a lot of people who have the same or similar problems to me will have a Serial that begins with at least W8.
•I believe that a lot of affected machines will of been produced between 2006 & 2008, yet not confined to that window in time.
•So, to round up, I am looking for people who have had/are having the same/similar problems to the ones listed below.

•Small graphical glitches; Thin lines in random areas on the desktop, growing in number and intensity over time.
•Graphical glitches on, in and around Finder windows. Again, growing in number and intensity over time.
•Horizontal lines across entire screen. Again, growing in number and intensity over time.
•The odd Software Crash/System Freeze. (Which does not happen very often on the iMac we've grown to love)
•More frequent Software Crashes/System Freeze's. (Maybe it's all that freeware and plugins I've been playing with)
•Kernel Panic's, never had one before... it was a new one on me.
•Frequent Kernel Panics.
•System Freeze, recovering after being put to sleep and then woken.
•System Freeze, unrecoverable. Hard reset required.
•Exactly the same behavior after a full reinstall of OSX.
•Exactly the same behavior after wiping system drive with zero's, then a full reinstall of OSX.
•Exactly the same behavior after wiping system drive with zero's, then a full reinstall with a previous version of OSX.
•System Freeze requiring hard reset on nearly every occasion Time Machine was accessed.
•Shut iMac down completely, never to respond to Power Button being pressed again, even after trying to reset the SMC.


The above is a simplified list of key events on a relatively short journey from Perfect Machine to, 'will not power up'.


If you or anyone you know has gone through anything similar, I would love you to join this topic.

Yours,
GaBeech

iMac (20-inch Late 2006) 2.16 GHz Intel Core 2 Duo ~ x1600 Graphics, Mac OS X (10.6.3), Serial Number: W87070ACVUV (Check My Biography To See What A Serial Means)

Posted on May 26, 2010 8:36 PM

Close

Q: Late 2006 iMac, Lines, Kernel Panic, Freeze, Reboot, Restart, Serial W8 ?

  • All replies
  • Helpful answers

first Previous Page 5 of 27 last Next
  • by QuidSquid,

    QuidSquid QuidSquid Jun 15, 2010 10:52 PM in response to dbax
    Level 1 (0 points)
    Jun 15, 2010 10:52 PM in response to dbax
    I ran TechTool after, I wanted to make sure everything was still ok after doing the 10.6.3 reinstall.
  • by QuidSquid,

    QuidSquid QuidSquid Jun 18, 2010 4:52 PM in response to GaBeech
    Level 1 (0 points)
    Jun 18, 2010 4:52 PM in response to GaBeech
    so, it froze on me the other morning and after that I upgraded to 10.6.4 and I have since frozen after upgrading. Have no idea what the problem is, but it's getting annoying. my next step is to call apple.
  • by QuidSquid,

    QuidSquid QuidSquid Jun 18, 2010 5:51 PM in response to GaBeech
    Level 1 (0 points)
    Jun 18, 2010 5:51 PM in response to GaBeech
    Was able to find these 2 possible fixes after searching for freezing issues dealing with 10.6.4.

    One that mentions disabling Spotlight: http://appletoolbox.com/tag/mac-os-x-10-6-3/

    Another from this same board that mentioned installing the 10.6.4 (combo) update. Here is the link to the update: http://support.apple.com/kb/DL1048
  • by adolfopi,

    adolfopi adolfopi Jul 2, 2010 8:40 PM in response to GaBeech
    Level 1 (0 points)
    Jul 2, 2010 8:40 PM in response to GaBeech
    My computer is experiencing some of the same problems you guys are mentioned here: horizontal lines, weird color patches in the screen, etc.

    It is now freezing every single day al least once, some times more.
    I already changed the HD and there is no difference.

    I bought it in August 2006 and of course Apple care does not cover me anymore. It did not even last 4 years!!

    The serial number is: QP6340xxxx
  • by Gorden,

    Gorden Gorden Jul 10, 2010 1:52 AM in response to adolfopi
    Level 1 (0 points)
    Jul 10, 2010 1:52 AM in response to adolfopi
    Serial: QP645xxxxxx

    Had this late 2006 iMac for around 2 years without any problems but since last year, I've been having graphical artifacts, multicolored lines, freezing but audio still runs in the background or an odd 'black screen of death' occasionally (requiring hard reset), and a few other things. No kernel panics though. Higher fan settings with smcFan sorta helped but the problems still pop up.

    With BootCamp in Windows 7, I only encounter 3d distortions/graphic artifacts and BSoDs with heavy gaming, but I get a few different BSoD errors: PFCLISTCORRUPT, Tried to write to read only memory, and one or two that I cant remember.

    Most of the time I have my fans set to 2000-3000 rpm and my internal temps read around 40-50 C, and I crank it up during gaming or watching video reaching around 60-70 C. I have opened the case and cleaned some dust out but that didn't really do anything. I did the Install disk hardware and TechTool tests and reset PRAM and SMC, nothing helped. I havent replaced my HD or reinstalled Snow Leopard though.

    Message was edited by: Gorden
  • by GaBeech,

    GaBeech GaBeech Jul 11, 2010 5:13 AM in response to QuidSquid
    Level 1 (0 points)
    Jul 11, 2010 5:13 AM in response to QuidSquid
    QuidSquid wrote:
    so, it froze on me the other morning and after that I upgraded to 10.6.4 and I have since frozen after upgrading. Have no idea what the problem is, but it's getting annoying. my next step is to call apple.

    I'm 100% sure this issue is hardware related. (Graphics/Logic Board & Cooling, maybe Capacitors)
    The only connection with the software could be; how much it asks of the system.

    The more the user/software asks of the system, the sooner the SAME symptoms reveal themselfs in a certain group of machines.

    If I bought a car and had to ramp up the radiator fan speed/fit a larger radiator fan or replace the engine/parts of it due to heat damage after 3 years...
    I would definately put it down to a manufacturing fault or poor design.

    We should not have to use after market hardware or software to keep our machines alive unless we want to use it above and beyond what it was designed for.

    Turbo charge a car... Upgrade the cooling system...
    Use a car round town and the odd blast down the motorway... Leave everything factory spec...
  • by R C-R,

    R C-R R C-R Jul 11, 2010 7:47 AM in response to GaBeech
    Level 6 (17,700 points)
    Jul 11, 2010 7:47 AM in response to GaBeech
    GaBeech:

    All good points but in terms of the car analogy consider:

    • A three year old car is more likely to fail than a six month old one, even if the design of each is perfectly sound & both are totally free of manufacturing defects.

    • Aftermarket hardware (& software, now that so much of the car is controlled by it) can cause failures that would not normally affect a factory spec car.

    • To credibly attribute a failure to poor design or a widespread manufacturing defect, it is necessary to look not just at the number of the same type of car failing in a similar manner after a similar period of time, but also to look at that number in the context of the fraction it represents of all cars of that type made & in use. IOW, we expect a certain fraction of those cars to fail anyway; what matters is if that fraction is unusually large.
  • by GaBeech,

    GaBeech GaBeech Jul 12, 2010 4:22 AM in response to R C-R
    Level 1 (0 points)
    Jul 12, 2010 4:22 AM in response to R C-R
    R C-R:

    I understand all this.
    Yet my analogy was only aimed at making people realize this issue is not software related and we should not, unless it's all thats left, be looking for aftermarket solutions.

    If this only effects me and a few others accross the whole world, then this is the place for us few to gather and comfort each other.

    If this effects many other people, maybe they will think to look on 'Apple Discussions' and they will find they are not alone.

    So people... I'm no pro, but;

    This is not a 10.6.x to 10.6.x problem, it is not a software compatibility issue.

    whether it can be accepted or not, it's a hardware issue.
    Predominantly showing itself approximately 3 years into normal use.

    ps. A £12,000 car may require a £120 or even £1,000 part after 3 years... Not an £8,000 part!
    I believe them prices roughly represnt the ratio of costs to repair an iMac with these issues.
  • by R C-R,

    R C-R R C-R Jul 12, 2010 9:07 AM in response to GaBeech
    Level 6 (17,700 points)
    Jul 12, 2010 9:07 AM in response to GaBeech
    I'm not disagreeing with you, at least for the most part. For some, a software issue might be involved, but I suspect for most (at least for those with visible lines or other artifacts in the display) it is probably the hardware.

    Regarding the repair costs, it has become cost ineffective to repair complex, highly integrated consumer electronics of any kind. Their affordability & ever better performance comes largely from reducing the number of separately replaceable parts & modules to the bare minimum; eliminating excess connectors, wiring, brackets, etc. & making them easier & cheaper to mass produce on automated assembly lines. This is especially true for very compact items like cell phones & laptops, & unfortunately also for our slim & elegant looking iMacs.

    For that matter, it is also a growing trend for cars: manufacturers are using more integrated modules that are very costly to replace than ever before.
  • by GaBeech,

    GaBeech GaBeech Jul 12, 2010 9:40 AM in response to R C-R
    Level 1 (0 points)
    Jul 12, 2010 9:40 AM in response to R C-R
    All the points you raise are valid regarding integrated components and slimline products.

    It's 2010 now, most of the iMac's in question have been in use for 2-3 years. Each one will be used in a different manner.

    Used for processes that ask more or less of the system. Powered up permanently or only switched on at the wall when a person is in front of it.

    +back to the cars again+
    These differences in use could be refered to collectively as 'milage'.
    I think my 'milage' is just above average.
    I think many users will match my total 'milage' in the coming months.

    +(I've checked, it can be spelled either way... I don't like vowels next to each other in these situations.)+
  • by elice82@,

    elice82@ elice82@ Jul 13, 2010 3:16 PM in response to GaBeech
    Level 1 (9 points)
    Jul 13, 2010 3:16 PM in response to GaBeech
    @ R C-R
    If I buy a car and only mine car fails in 3 years it can happen.
    But if my car and others people car's with the exact type car or the same year are failing too then the company has a problem.
    They greatest example is now Toyota. They are solving the problem because they simply can't look the other way (people are dying). But all ready have damaged there name. For me Apple can go ahead pretending that nothing is wrong... in the end there the ones that paying for it! And that will be Apple!

    Me too are having the exact same problems with my iMac.
    Trying to start a lawsuit in The Netherlands but I can't seem to prove that this problem that exist. It isn't constantly there!
    But really many have this problem but Apple simply looks the other way.

    Also Apple's Time Capsule failed way to soon that one has now been recalled. Probably with the help of a grave site, Media attention and consumer programs.

    The problem with these iMacs is that they are not dead. But there are slowly failing. First you can do a little less then you can't do a lot any more. (I don't believe in the line: IT JUST WORKS, I believe more in: IT FAILS SLOWLY).
  • by QuidSquid,

    QuidSquid QuidSquid Jul 13, 2010 4:08 PM in response to GaBeech
    Level 1 (0 points)
    Jul 13, 2010 4:08 PM in response to GaBeech
    Issue is NOT HARDWARE, it ended up being software related.

    I have been almost a month without any freezes to my system. After a little research online it seems that Spotlight is causing systems to freeze coming out of sleep mode. I posted my solutions as something I was trying above and it seems to have worked:

    disabling Spotlight: http://appletoolbox.com/tag/mac-os-x-10-6-3/

    installing the 10.6.4 (combo) update. Here is the link to the update: http://support.apple.com/kb/DL1048

    This should hopefully help some people given that we do in fact have the same issues. I was not experiencing any of the weird graphical errors and glitches. If you happen to be freezing out of nowhere after switching between programs and/or freezing after waking your computer from sleep mode these 2 solutions above should fix your problem.
  • by Bridget Brown,

    Bridget Brown Bridget Brown Jul 13, 2010 5:45 PM in response to GaBeech
    Level 1 (15 points)
    Jul 13, 2010 5:45 PM in response to GaBeech
    I have had to restart my sad iMac 4 times just since I've read through this thread. I am here because of the same problems. It started about 4 months ago, the screen would just go black and the power light would go off, but I would have to hold down the power button to actually turn it off. Then restart. Then I started noticing the bit fragmented lines across the screen, and I knew that meant it was going down. Then the frozen beach ball of death. Some days I have to restart the Mac 20 times. Some days it's fine.

    I don't believe the fan or heat is the problem, as I have had it off all night and when I turn it on first thing in the a.m. it crashes. Then I've had it crash 20 times in one morning and I thought it was the heat, because it was nearly 100 degrees where I live and I have no A/c, but then all afternoon it was fine!

    I have noticed when I have iTunes on or am talking to someone on Skype, I still have audio when the beach ball is rolling and I'm locked up. So I tend to think it is a video problem.

    Serial number: W8724

    So, I don't care about a class action suit or anything (although that would be sweet), I just want to know what I can do to fix my Mac. Can it even be fixed?
  • by R C-R,

    R C-R R C-R Jul 13, 2010 8:49 PM in response to elice82@
    Level 6 (17,700 points)
    Jul 13, 2010 8:49 PM in response to elice82@
    elice82@ wrote:
    If I buy a car and only mine car fails in 3 years it can happen.
    But if my car and others people car's with the exact type car or the same year are failing too then the company has a problem.


    It is the company's problem only if the failure is due to a defect in its design or manufacturing processes. Failures are expected to occur for other reasons in any large enough sample of exactly the same type of car of the same model year.

    It is the same for iMacs or any other computer. Apple, Dell, or whichever other company made the computer is not responsible for all failures regardless of cause.

    Simply put, it isn't a question of if the problem exists but of what caused it.
  • by elice82@,

    elice82@ elice82@ Jul 14, 2010 1:53 AM in response to R C-R
    Level 1 (9 points)
    Jul 14, 2010 1:53 AM in response to R C-R
    @R C-R
    R C-R wrote:
    It is the same for iMacs or any other computer. Apple, Dell, or whichever other company made the computer is not responsible for all failures regardless of cause.


    If many fail in the same way, you can expect there is a failure in the design or a manufacturing processes. Because it simply not possible that all the people having the same problem that is releated to something different everytime.

    I don't mind if the part is from ATI, Intel or someone else it is a computer from Apple. They are responsible for the total computer. Because they have put together this way (their design).

    Simply put, it isn't a question of if the problem exists but of what caused it.


    I don't want to know what causing it. I want to get solved!
    Apple should have been looking at what's causing it. But they don't want to look at it!
    It will cost them a lot of money! That is what this whole issue is about.
first Previous Page 5 of 27 last Next