[nebberz]

1.25 GHZ PowerPC G4
1 Gig DDR SDRAM
Mac OS X 10.5.6

Let me start off by saying that I have no previous experience with Macs so please bear with me.

I am the community pc fixing guy and so I thought I would try my hand at a Mac for a local family that has pretty much given up on it.

I have been banging my head against this thing learning as much as I can about macs while I work on repairing this thing.

So basically the machine really likes to freeze, sometimes after just sitting there a while, sometimes it'll be ok for an hour or two. It especially likes to freeze if you shake a window around. The strange thing is, it doesn't seem to freeze at all while in safe mode. Seems like it wouldn't be a hardware problem at that point.

I've done disk verify, verified disk/permissions and all that and everything checked out good. I ran the repair disk option from the os x installation file and that came back ok as well. (I'm using a dmg file because they do not know where their copy of os x has gone and this machine only reads cd's anyways.)

I have all of their files backed up, so I then attempted to do a reinstall of OS X through an external firewire. It showed the same symptoms, and so I then proceeded to erase the disk and installed from scratch. End result = still the same symptoms! Doing the installation process it freezes occasionally and I'll have to start it over. If I open a window like disk utility and stuff, I have to shake that window around quite a bit to make it freeze...maybe for like a minute. (In normal boot-up it'll freeze if I shake around a window even for a couple of seconds)

I have no idea where to go from this point. My only guesses are faulty gpu, faulty motherboard. (RAM has been swapped out, and I figured it can't be the hard drive since it freezes when I boot from the external drive as well to start installing osx.)

Should I see if I can get an older copy of a mac operating system and that maybe this machine just is not liking os x for some reason? Or is there another idea floating out there somewhere? (:

Any help would be appreciated, thanks!

[CharlesS]

Check /Library/Logs/PanicReporter for panic logs. If there are any, post the most recent one here. Maybe it will have some clues in it.

[nebberz]

There is only a diskutility.log there. No panicreporter folder.

Do I need to enable something? I looked in Utilities and opened the console. I read there may be an option there somewhere to enable such a thing. I don't see any option but I do see a system.log. Maybe that will be of some help? I would load it as an attachment but I don't see an option to do as such.

Pasting:

Dec 6 00:17:42 admins-emac newsyslog[197]: logfile turned over
Dec 6 00:22:08 localhost kernel[0]: ireWire (OHCI) Apple ID 31 built-in now active, GUID 000d93fffe34a8ce; max speed s400.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** /dev/rdisk0s3
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Root file system
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking Journaled HFS Plus volume.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking Extents Overflow file.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking Catalog file.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking multi-linked files.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking Catalog hierarchy.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking Extended Attributes file.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking volume bitmap.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** Checking volume information.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ** The volume hope appears to be OK.
Dec 6 00:22:05 localhost com.apple.launchctl.System[2]: ***** FILE SYSTEM WAS MODIFIED *****
Dec 6 00:22:07 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Dec 6 00:22:07 localhost com.apple.launchd[1] (com.apple.blued): Unknown key for boolean: EnableTransactions
Dec 6 00:22:07 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Dec 6 00:22:07 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Dec 6 00:22:08 localhost kextd[9]: safe boot detected
Dec 6 00:22:08 localhost kernel[0]: com.apple.driver.AppleIntelCPUPowerManagement isn't a valid mach-o (magic is cefaedfe)
Dec 6 00:22:08 localhost kextd[9]: safe boot; invalidating extensions caches
Dec 6 00:22:08 localhost kernel[0]: error mapping module file com.apple.driver.AppleIntelCPUPowerManagement
Dec 6 00:22:08 localhost kernel[0]: can't map com.apple.driver.AppleIntelCPUPowerManagement in preparation for loading
Dec 6 00:22:08 localhost kernel[0]: Can't determine dependencies for com.apple.driver.AppleIntelCPUPowerManagement.
Dec 6 00:22:08 localhost kernel[0]: Couldn't alloc class "AppleIntelCPUPowerManagement"
Dec 6 00:22:08 localhost kernel[0]: mbinit: done
Dec 6 00:22:08 localhost kernel[0]: Security auditing service present
Dec 6 00:22:08 localhost kernel[0]: BSM auditing present
Dec 6 00:22:08 localhost kernel[0]: rooting via boot-uuid from /chosen: 24D5F4B2-A191-39A7-B106-5401B9280A83
Dec 6 00:22:08 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Dec 6 00:22:08 localhost kernel[0]: com.apple.driver.AppleIntelCPUPowerManagement isn't a valid mach-o (magic is cefaedfe)
Dec 6 00:22:08 localhost kernel[0]: error mapping module file com.apple.driver.AppleIntelCPUPowerManagement
Dec 6 00:22:08 localhost kernel[0]: can't map com.apple.driver.AppleIntelCPUPowerManagement in preparation for loading
Dec 6 00:22:08 localhost kernel[0]: Can't determine dependencies for com.apple.driver.AppleIntelCPUPowerManagement.
Dec 6 00:22:08 localhost kernel[0]: Couldn't alloc class "AppleIntelCPUPowerManagement"
Dec 6 00:22:08 localhost kernel[0]: com.apple.driver.AppleIntelCPUPowerManagement isn't a valid mach-o (magic is cefaedfe)
Dec 6 00:22:08 localhost kernel[0]: error mapping module file com.apple.driver.AppleIntelCPUPowerManagement
Dec 6 00:22:08 localhost kernel[0]: can't map com.apple.driver.AppleIntelCPUPowerManagement in preparation for loading
Dec 6 00:22:08 localhost kernel[0]: Can't determine dependencies for com.apple.driver.AppleIntelCPUPowerManagement.
Dec 6 00:22:08 localhost kernel[0]: Couldn't alloc class "AppleIntelCPUPowerManagement"
Dec 6 00:22:08 localhost kernel[0]: Got boot device = IOService:/MacRISC2PE/pci@f4000000/AppleMacRiscPCI/ata-6@D/AppleKauaiATA/ATADeviceNub@0/AppleATADiskDriver/IOATABlockStorageDevice/IOBlockStorageDriver/Maxtor 2F040L0 Maxtor 2F040L0/IOApplePartitionScheme/Untitled@3
Dec 6 00:22:08 localhost kernel[0]: BSD root: disk0s3, major 14, minor 2
Dec 6 00:22:08 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 6836224 to: 1969152 (joffset 0x134000)
Dec 6 00:22:08 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Dec 6 00:22:08 localhost kernel[0]: HFS: Removed 1 orphaned unlinked files or directories
Dec 6 00:22:08 localhost kernel[0]: Jettisoning kernel linker.
Dec 6 00:22:14 localhost bootlog[34]: BOOT_TIME: 1260087597 0
Dec 6 00:22:14 localhost rpc.statd[16]: statd.notify - no notifications needed
Dec 6 00:22:15 localhost fseventsd[25]: event logs in /.fseventsd out of sync with volume. destroying old logs. (3410 138 3622)
Dec 6 00:22:15 localhost fseventsd[25]: log dir: /.fseventsd getting new uuid: AAE2A314-12C9-4822-BD63-61E17063B70E
Dec 6 00:22:19 localhost DirectoryService[30]: Launched version 5.6 (v514.24)
Dec 6 00:22:20 localhost DirectoryService[30]: Improper shutdown detected
Dec 6 00:22:26 localhost kernel[0]: UniNEnet: Ethernet address 00:0d:93:34:a8:ce
Dec 6 00:22:26 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[21]: Login Window Application Started -- Threaded auth
Dec 6 00:22:33 localhost kernel[0]: Resetting IOCatalogue.
Dec 6 00:22:33 localhost kextd[9]: 0 cached, 283 uncached personalities to catalog
Dec 6 00:22:34 localhost mDNSResponder mDNSResponder-176.3 (Sep 30 2008 16:59:41)[20]: starting
Dec 6 00:22:35 localhost kernel[0]: Matching service count = 0
Dec 6 00:22:42 admins-emac configd[32]: setting hostname to "admins-emac.local"
Dec 6 00:22:46 admins-emac org.ntp.ntpd[13]: Error : nodename nor servname provided, or not known
Dec 6 00:22:46 admins-emac ntpdate[62]: can't find host time.apple.com
Dec 6 00:22:46 admins-emac ntpdate[62]: no servers can be used, exiting
Dec 6 00:22:50 admins-emac kextd[9]: writing kernel link data to /var/run/mach.sym
Dec 6 00:22:52 admins-emac com.apple.ATSServer[66]: FODBCheck: New annex file created
Dec 6 00:22:52 admins-emac /usr/sbin/ocspd[67]: starting
Dec 6 00:23:03 admins-emac loginwindow[21]: Login Window Started Security Agent
Dec 6 00:23:09 admins-emac kernel[0]: hfs: early journal init: volume on disk1s3 is read-only and journal is dirty. Can not mount volume.
Dec 6 00:23:09 admins-emac kernel[0]: jnl: disk1s3: replay_journal: from: 308736 to: 1022464 (joffset 0x8bd000)
Dec 6 00:23:09 admins-emac fseventsd[25]: event logs in /Volumes/Untitled 1/.fseventsd out of sync with volume. destroying old logs. (3361 0 3647)
Dec 6 00:23:09 admins-emac kernel[0]: jnl: disk1s3: journal replay done.
Dec 6 00:23:09 admins-emac fseventsd[25]: log dir: /Volumes/Untitled 1/.fseventsd getting new uuid: 8F194E6C-709C-468E-9DA4-B57549392778
Dec 6 00:23:09 admins-emac mds[19]: (/Volumes/Untitled 1/.Spotlight-V100/Store-V1/Stores/E50819B6-BF51-4E0C-BB83-30D6FA817920)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Untitled 1/.Spotlight-V100/Store-V1/Stores/E50819B6-BF51-4E0C-BB83-30D6FA817920/live.2.; needs recovery
Dec 6 00:23:09 admins-emac mds[19]: (/Volumes/Untitled 1/.Spotlight-V100/Store-V1/Stores/E50819B6-BF51-4E0C-BB83-30D6FA817920)(Error) IndexCI in copyFileOrFd:write failed - expected:2, actual: 0
Dec 6 00:23:09 admins-emac mds[19]: (/Volumes/Untitled 1/.Spotlight-V100/Store-V1/Stores/E50819B6-BF51-4E0C-BB83-30D6FA817920)(Error) IndexCI in recoverIndex:recover canceled (0.)
Dec 6 00:23:33 admins-emac authorizationhost[76]: MechanismInvoke 0x1e14cb0 retainCount 2
Dec 6 00:23:33 admins-emac SecurityAgent[77]: MechanismInvoke 0x5c01680 retainCount 1
Dec 6 00:23:34 admins-emac SecurityAgent[77]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Dec 6 00:23:34 admins-emac SecurityAgent[77]: MechanismDestroy 0x5c01680 retainCount 1
Dec 6 00:23:34 admins-emac authorizationhost[76]: MechanismDestroy 0x1e14cb0 retainCount 2
Dec 6 00:23:34 admins-emac loginwindow[21]: Login Window - Returned from Security Agent
Dec 6 00:23:35 admins-emac loginwindow[21]: USER_PROCESS: 21 console
Dec 6 00:23:35 admins-emac com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[73]): Exited: Terminated
Dec 6 00:23:38 admins-emac /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer[111]: (-3230) Cannot use ATS Persistent Store - switching to old FODB cache code
Dec 6 00:23:48 admins-emac /System/Library/CoreServices/coreservicesd[42]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(admin's Public Folder) returned -14135
Dec 6 00:24:31 admins-emac com.apple.dyld[10]: update_dyld_shared_cache[10] regenerated cache for arch=ppc

[reader50]

What you've pasted is the startup log sequence. We'd rather look at the panic log, which ought to be in /Library/Logs/

When the eMac freezes, does the screen dim, and you get a message that you need to restart the mac?

Missing log and no-message on screen suggests a hardware failure to me. Shaking a window excercises the GPU and CPU in that order. In safe boot, the system may disable Quartz Extreme from doing layer compositing on the graphics card, which would move load from GPU to CPU.

Following this chain of reasoning, the GPU is overheating. Possibly because it's nearing failure, possibly heatsink badly dusted up, possibly heatsink grease dried out. My next step would be to crack the case open and do some vacuuming. Then take a closer look at the GPU heat sink.

[nebberz]

Yes, sadly there were no panic logs in said folder.

The screen does not dim and I do not receive any messages. I can click things and move around windows and then everything but the mouse stops responding. Clicking has no effect on anything. 5 seconds to a minute later the cursor freezes as well and the machine appears to have completely locked up.

Is there anything I should be aware of before cracking open the case cleaning it out?

How expensive/easy would it be to swap out a gpu for one of these things? More/less difficult than a PC?

Thanks for all the help thus far!

[CharlesS]

Make sure you’re checking /Library folder at the root of the drive, not the one in your home folder. That is where the panic logs should be.

[reader50]

The GPU chip is soldered down on the motherboard, so let's hope the problem is with dust, the heatsink, or failing case fan. Dissassembly isn't so easy on an eMac.

As CharlesS mentions, there are several Library folders:

Mac HD/Users/-your user name here-/Library/ <- user data and prefs
Mac HD/Library/ <- system-level info, incl panic logs
Mac HD/System/Library/ <- base OS install, stay out of here

The system composits the folders normally. Normal bootup = /System/Library/ + /Library/ + the /Users/admin/Library/ folder for whoever logs in. During safe boot, it only does /System/Library/ + the user Library. This omits the root /Library/, which is where non-Apple additions are. Like 3rd party preference panes, screen savers, frameworks, or specialized content some applications install.

This is slightly oversimplified, but it's accurate as a rule of thumb.

[nebberz]

I told you guys I was new to macs! Sure enough I was in the wrong folder. Sadly I do not see any panic logs in Drive/Library/Logs either.

There is CoreRAID.log, SingleSignOnTools.log and a DirectoryService folder.

Inside the folder there is a directoryservice.error.log and a directoryservice.server.log.

Doesn't look like any of that would be of any use.

[reader50]

I'd say it has to be overheating by GPU, CPU, or motherboard chipset (in order of likelihood). Slight chance of a weak power supply. Opening it up is the next step. If the heat problem can't be solved by cleaning, HS reseating, fan replacement ... then you'd need a motherboard swap, since all 3 suspects are soldered down.

Replacement motherboards from Apple are ridiculously overpriced - the only hope for a cheap replacement would be eBay or the like. So let's hope for a solvable heat problem.

btw - it would help somewhat if you could tell us the exact model. In Apple System Profiler, the hardware tab will give a model number like "PowerMac6,4" which would let us know. ASP is in your Utilities folder, it can also be reached from Apple Menu -> About This Mac -> More Info (button)

Alternatively, you can get the specs from the back or bottom, along with a model number that looks something like this: M9425LL/A

[nebberz]

Model - PowerMac6,4 would be spot on.

Time to find a guide on cracking this thing open I suppose!

[nebberz]

I read into how crt screens like to hold voltages and felt that I did not have the hardware know-how to bust into this thing so was ready to give up on it. I have been encouraged to follow through so future users with similar problems may find the answers they are looking for. Seems reasonable enough seeing as how I have used hundreds of previously made threads in the past that have helped me with this or that on many things in life.

Apparently the caps used to charge the screen should have discharged if it has been unplugged for a day. I suppose I should give back a little and see about opening this thing up tonight.

[applelemminh]

batches of eMac 1.25 GHZ, combo-drive (doesn't burn DVD just plays them) are known to have bad capacitors. My eMac being one of them. For a quick check, just open up the memory access cover and look at the visible capacitors. If they are bulging at the top, you have bad capacitors. Your machine will randomly freeze regardless of what you do. New motherboard or replacing all bad capacitors on the motherboard is the only solution. If you want more info let me know or google it and research on your own.

Could also be defective RAM if the capacitors aren't bulging.

[MTsett]

You have to be really, REALLY careful with cracking open an eMac.
Even it you let the eMac sit off of power for a day or so, the CRT could still have enough
voltage/amps to cause serious injury and or death.
Also, when cracking the case, you need to take real care in making sure you do not damage the power switch and its connecting cable to the motherboard.
It wouldn't hurt before going to this extreme, to check the condition of the capacitors in this eMac. If they look OK, then, take out the existing RAM and replace with a new, purchased one or a spare one that is of the right specs and of known operation is fine to check to see if the eMac has a bad RAM stick. This is a very easy thing to do and check, first, before going to the extreme of actually cracking into the eMac's case and start mucking about in there.
Also, if you take the eMac off of power for a day or so, you may need to purchase and replace the 1/2 size AA battery, that's found in the same place as the RAM, as this will discharge and become fairly dead in a relatively short time. Especially if it's the original battery that came with this eMac.
Check for bad RAM, first. Always check for the easiest and obvious solutions, first, before proceeding to a more complex solution.