This discussion is archived
11346 Views 12 Replies Latest reply: Aug 8, 2010 10:20 AM by Allan Jones
Currently Being ModeratedAug 6, 2010 1:45 PM (in response to Allen Rubin)Allen,
During the startup process (Apple logo with spinning gear) the system is going through a series of basic self checks and the loading of the OS. Interestingly enough the startup process is no different in a shut down to power on scenario then a restart scenario.
Do you notice any performance issues with your machine when you're in the operating system? Any sluggishness? Any issues with peripherals that are connected to the machine?
I'd vote you try a Safe Boot and force a full directory check, in addition to possibly running some basic diagnostics from the OS X Installation disc that came with your machine.
Safe Mode - http://support.apple.com/kb/ht1455
Disk Verification Troubleshooting - http://support.apple.com/kb/ts141713" MacBook Pro (2.4GHz/4GB/250), Mac OS X (10.6.4)
Currently Being ModeratedAug 6, 2010 10:18 PM (in response to JasonFear)OK, here's what I have done (not in order)
1. Reset the Pram
2. Reset the SMU
3. Safe Boot
4. Reinstalled the system (Snow Leopard) and 10.6.4 update
5. Ran TechTool Pro to check hardware (no problems found)
The only thing I haven't done is run DiskWarrior (I ordered the latest version but it hasn't arrived yet.)
The problem still persists.....eMac G4 1.25 GHz, Mac OS X (10.4.11), 17" MacBook Pro - Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 1:05 AM (in response to Allen Rubin)Hi Allen,
I'd say that DiskWarrior might be excessive at this point, especially after you reinstalled the OS. A reinstall of the OS would theoretically resolve any sort of directory corruption. Regarding TechTool Pro, regrettably that isn't much for finding hardware faults. In my 5+ years of providing direct hardware support in multiple environments has brought me to the conclusion that the best hardware failure detection software out there is the stuff that Apple gives their service centers and Genius Bars (not consumer available stuff).
But I digress... what you probably did was an Archive & Install of Snow Leopard. Unlike in previous versions of OS X, Snow Leopard doesn't give you the choice of Archive & Install vs. Erase & Install, it just performs an Archive & Install. You have to go into Disk Utility and erase the drive first if you want the benefit of the "E&I" approach. That'd be my vote for the next step, backup your data and perform the Erase & Install. At that point if you're still having difficulties... it's most likely a hardware issue.13" MacBook Pro (2.4GHz/4GB/250), Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 10:44 AM (in response to JasonFear)Thanks, Jason... I didn't do an archive/install.... I had backed up to an external drive (SuperDuper) so I erased the partition and did a clean install. Then I used migration assistant to copy files from the backup drive.
What's puzzling is that once booted, everything runs normally. Last night I shut down, and this morning here's what happened, in sequence:
1. Pressed start button, no chime, black screen. Waited about a minute.
2. Pressed start button and held it down to shut down (I have a USB LED that shows when computer is on.) Waited about two minutes.
3. Pressed start button, immediate chime, gray screen, chime again, chime again, chime again, continuous chiming.
4. Pressed start button and held it to shut down.
5. Pressed start button, no chime, black screen.
That's where I am right now.....eMac G4 1.25 GHz, Mac OS X (10.4.11), 17" MacBook Pro - Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 12:13 PM (in response to Allen Rubin)Hi A,
So your computer is not normal, first to do is to find out if is the computer or any other connected device. Here is the next step (this should be the first when you are debugging):
DISCONNECT EVERYTHING that is plugged in your Mac, wait about a minute, turn your computer on, this way you can find out if your USB mentioned device or any other is causing this or if it is really your Mac.
Good luck.MacBook Pro 1,1, Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 1:01 PM (in response to Allen Rubin)Hi Allen,
I don't know how familiar you are with the startup sequence of a Mac. But that "chime" you're describing is what's called a POST chime. POST stands for Power On Self Test, a basic check, by the operating system of critical hardware components that the machine requires to run.
It sounds like something is causing POST to either false positive or fail. What's interesting is that when the machine finally does start running it's perfectly fine. Definitely a weird one...
I agree with the above poster, unplug any USB related peripherals. I'd also add unplugging the battery and just trying to run the machine on A/C power (for the purposes of troubleshooting). See if there's any change or improvements. If not, then I think the next course of action is a Genius Bar / Service Provider.13" MacBook Pro (2.4GHz/4GB/250), Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 2:50 PM (in response to Allen Rubin)Hi Allen,
Even though the POST does not specifically indicate a RAM issue, I would be suspicious, especially if the RAM is not the original as supplied by Apple.
If it is not, install the original.
If it is, take one module out and try running the MBP. Move it to the other slot and try running the MBP. Repeat with the other module. In this way you check out both RAM modules and the RAM slots.
Thank you one and all for the wealth of information, insights, and suggestions. Although I finally got the MBP running (reset SMC then reset PRAM), I decided it was time to get some "expert" help and took it to the Genius Bar. Cursory examination suggested a memory problem (even though TechTool Pro said it was OK). Anyway, they are running a complete diagnostic and will call me in a few hours with the results and what needs to be done to solve the problem.
Again, please accept my deepest thanks for your kind attention to my posts, and I'll post again when the problem is fixed so we can tie the symptoms to the disease.eMac G4 1.25 GHz, Mac OS X (10.4.11), 17" MacBook Pro - Mac OS X (10.6.4)
Currently Being ModeratedAug 7, 2010 11:07 PM (in response to Allen Rubin)
Allen Rubin wrote:
(even though TechTool Pro said it was OK).
Allen, happy to hear we're making progress towards a resolution. No surprise with TechTool Pro. From my experience that software is rarely capable of detecting the problem and in most situations will tell you something's wrong on a component that isn't the problem.13" MacBook Pro (2.4GHz/4GB/250), Mac OS X (10.6.4)
Currently Being ModeratedAug 8, 2010 10:01 AM (in response to JasonFear)Jason (and all),
Problem solved! Apple's diagnostics found a faulty memory controller on the logic board. Otherwise the remaining hardware passed all tests. Apparently, during POST, the malfunctioning of the controller interrupted startup. That's why the PRAM reset worked... it bypassed the controller. Once operating, the faulty controller only caused sporadic problems (kernel panics).
Anyway, the memory controller is not replaceable, it's soldered to the logic board, so I'm out about $300 for a new (replacement) logic board.
Once again, thanks to all for your help. If this had not been a hardware problem, I'm certain your advice would have done the trick!!
-AleMac G4 1.25 GHz, Mac OS X (10.4.11), 17" MacBook Pro - Mac OS X (10.6.4)
Currently Being ModeratedAug 8, 2010 10:20 AM (in response to Allen Rubin)The good news, or maybe the "better" news is the the $300 charge indicates a "depot repair." Computers often come back with other little deficits fixed, all covered under the flat-fee system. You should have a nicely refurbed computer when it comes back for far less than the cost of a new unit.PowerMac G4 MDD 1.25G SP;, Mac OS X (10.4.11), ; MacBookPro Late2007 2.2G 15" (10.5.8); PowerBook G4 1Ghz 17" (10.4.11)