crwdns2933423:0crwdne2933423:0

Model A1225 / Early 2009 / 2.66, 2.93, or 3.06 GHz Core 2 Duo processor

crwdns2934591:0163crwdne2934591:0 crwdns2934593:0crwdne2934593:0

The mac hangs on blue screen and doesn't starts the systemsoftware

At startup the mac doesn't go true with its startup sequence and hangs on the blue screen.

The machine is still acessable as a external harddrive (at startup hold the letter T) but is slow and cant copy much at the same time.

- Multiple times cleaned PRAM didn't help

- HDD check was OK

- Hardware check didn't complete (hanged on the check)

- Did a clean instal of OSX 10.5 (original disc) no luck their either

What i didn't check yet is the RAM.

What can be the problem

crwdns2934081:0crwdne2934081:0 crwdns2934083:0crwdne2934083:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 -1
crwdns2944067:02crwdne2944067:0

How did you check the hard drive? From the system installation disk or in target mode and with what?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

See comment below.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2933315:03crwdne2933315:0

crwdns2934051:0crwdne2934051:0

At this point, if it starts in target mode, I would reformat the drive and use the "write zeros" option to map out any bad blocks the drive has and reinstall the system. That failing, I would replace the drive.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 1

crwdns2944067:02crwdne2944067:0:

I formatted the drive and did a clean install. But did not perform a 'write zeros option', YET. Isn't their any change that it could be the RAM?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

You can check the RAM if you want to by removing one stick and booting then switch the RAM stick and boot, then do the same in the other slot. But I really see no indication of a RAM problem.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

I checked the hard drive from the system installation disk but diskaid did not find the drive at that point. So i checked the drive with Disk Warrior 4.2 and the drive came out fine. I can also see the drive if I do a computer to computer link with option letter T at startup. And that works fine to.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0

crwdns2942205:01crwdne2942205:0:

If the system installation disk does not see the drive, somethings wrong with the system disk or the hard drive. Try it in Target mode - with the firewire and see if you can run disk utilities from t he other computer. Repair the drive and also the permissions.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

Thanks for the comments so far. I am going to check everything mentioned.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

u2peer crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 0

crwdns2936753:030crwdne2936753:0 0

crwdns2942667:0crwdne2942667:0 2,678