Problems with booting yesterday

After upgrading my HD and RAM and working out a few subsequent kinks I thought I had everything worked out. Then yesterday when I started booting it sat at the apple logo screen for about 40 seconds, then it went to a blue screen and never got past that. It kept changing from one shade of blue to another, and every so often the little circular "thinking" thing showed up at the bottom (not the beach ball). Then it was swap back to the original shade of blue and start over. After cycling through this about 5 times I finally forced a shutdown by holding down the power button, and on the second attempt it booted normally.

Here's part of the boot log from yesterday morning. The entire log exceeded the maximum length for a post...if you need more I'll post it below. Can someone give me any suggestions?

3/7/11 5:39:23 AM com.apple.launchd[1] *** launchd[1] has started up. ***
3/7/11 5:39:56 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:39:56.773 ReportCrash[60:2907] Saved crash report for lsregister[59] version ??? (???) to /Library/Logs/DiagnosticReports/lsregister_2011-03-07-053956_localhost.crash
3/7/11 5:39:57 AM com.apple.launchd[1] (com.apple.FontWorker[58]) Job appears to have crashed: Bus error
3/7/11 5:39:57 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:39:57.628 ReportCrash[60:2a03] Saved crash report for fontworker[58] version ??? (???) to /Library/Logs/DiagnosticReports/fontworker_2011-03-07-053957_localhost.crash
3/7/11 5:39:57 AM com.apple.launchd[1] (com.apple.FontWorker[76]) Job appears to have crashed: Bus error
3/7/11 5:39:57 AM com.apple.fontd[57] 2011-03-07 05:39 fontd[57] (CarbonCore.framework) FSEventStreamCreate: _FSEventStreamCreate: ERROR: could not allocate 0 bytes for array of path strings
3/7/11 5:39:57 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:39:57.736 ReportCrash[60:3003] Saved crash report for fontworker[76] version ??? (???) to /Library/Logs/DiagnosticReports/fontworker_2011-03-07-053957-1_localhost.crash
3/7/11 5:39:59 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:39:59.248 ReportCrash[60:2e57] Saved crash report for DMProxy[81] version ??? (???) to /Library/Logs/DiagnosticReports/DMProxy_2011-03-07-053959_localhost.crash
3/7/11 5:40:00 AM com.apple.launchd[1] (com.apple.loginwindow[37]) Job appears to have crashed: Bus error
3/7/11 5:40:00 AM com.apple.UserEventAgent-LoginWindow[84] ALF error: cannot find useragent 1102
3/7/11 5:40:00 AM com.apple.UserEventAgent-LoginWindow[84] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
3/7/11 5:40:00 AM com.apple.launchd[1] (com.apple.WindowServer) Throttling respawn: Will start in 3 seconds
3/7/11 5:40:00 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:00.783 ReportCrash[60:34df] Saved crash report for loginwindow[37] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow_2011-03-07-054000_localhost.crash
3/7/11 5:40:04 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:04.134 ReportCrash[60:2c1b] Saved crash report for DMProxy[90] version ??? (???) to /Library/Logs/DiagnosticReports/DMProxy_2011-03-07-054004_localhost.crash
3/7/11 5:40:04 AM com.apple.launchd[1] (com.apple.coreservicesd[25]) Job appears to have crashed: Bus error
3/7/11 5:40:04 AM com.apple.loginwindow[88] _RegisterApplication(), FAILED TO REGISTER PROCESS WITH CPS/CoreGraphics in WindowServer, err=-50
3/7/11 5:40:04 AM com.apple.audio.coreaudiod[87] coreaudiod: CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
3/7/11 5:40:04 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:04.448 ReportCrash[60:4537] Saved crash report for coreservicesd[25] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054004_localhost.crash
3/7/11 5:40:04 AM com.apple.launchd[1] (com.apple.coreservicesd[96]) Job appears to have crashed: Bus error
3/7/11 5:40:04 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:04.924 ReportCrash[60:400b] Saved crash report for coreservicesd[96] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054004-1_localhost.crash
3/7/11 5:40:04 AM com.apple.loginwindow[88] _RegisterApplication(), FAILED TO REGISTER PROCESS WITH CPS/CoreGraphics in WindowServer, err=-50
3/7/11 5:40:04 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 10 seconds
3/7/11 5:40:15 AM com.apple.launchd[1] (com.apple.coreservicesd[101]) Job appears to have crashed: Bus error
3/7/11 5:40:15 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:15.504 ReportCrash[60:2c23] Saved crash report for coreservicesd[101] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054015_localhost.crash
3/7/11 5:40:15 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 10 seconds
3/7/11 5:40:25 AM com.apple.launchd[1] (com.apple.coreservicesd[103]) Job appears to have crashed: Bus error
3/7/11 5:40:25 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:25.862 ReportCrash[60:253f] Saved crash report for coreservicesd[103] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054025_localhost.crash
3/7/11 5:40:26 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 10 seconds
3/7/11 5:40:27 AM com.apple.launchd[1] (com.apple.metadata.mds[36]) Job appears to have crashed: Segmentation fault
3/7/11 5:40:27 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:27.886 ReportCrash[60:5033] Saved crash report for mds[36] version ??? (???) to /Library/Logs/DiagnosticReports/mds_2011-03-07-054027_localhost.crash
3/7/11 5:40:28 AM com.apple.UserEventAgent-LoginWindow[92] ALF error: cannot find useragent 1102
3/7/11 5:40:28 AM com.apple.UserEventAgent-LoginWindow[92] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
3/7/11 5:40:28 AM com.apple.launchd.peruser.501[108] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
3/7/11 5:40:28 AM com.apple.launchd[1] (com.apple.loginwindow[88]) Job appears to have crashed: Segmentation fault
3/7/11 5:40:28 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:28.742 ReportCrash[60:5333] Saved crash report for loginwindow[88] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow_2011-03-07-054028_localhost.crash
3/7/11 5:40:45 AM com.apple.launchd[1] (com.apple.coreservicesd[114]) Job appears to have crashed: Bus error
3/7/11 5:40:45 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:45.190 ReportCrash[60:5833] Saved crash report for coreservicesd[114] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054045_localhost.crash
3/7/11 5:40:45 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 1 seconds
3/7/11 5:40:45 AM com.apple.loginwindow[112] FAILED TO GET ASN FROM CORESERVICES so aborting.
3/7/11 5:40:45 AM com.apple.launchd[1] (com.apple.loginwindow[112]) Job appears to have crashed: Abort trap
3/7/11 5:40:45 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:45.961 ReportCrash[60:503b] Saved crash report for loginwindow[112] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow_2011-03-07-054045_localhost.crash
3/7/11 5:40:46 AM com.apple.UserEventAgent-LoginWindow[119] ALF error: cannot find useragent 1102
3/7/11 5:40:46 AM com.apple.UserEventAgent-LoginWindow[119] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
3/7/11 5:40:48 AM com.apple.launchd[1] (com.apple.coreservicesd[124]) Job appears to have crashed: Bus error
3/7/11 5:40:48 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:48.967 ReportCrash[60:533b] Saved crash report for coreservicesd[124] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054048_localhost.crash
3/7/11 5:40:48 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 8 seconds
3/7/11 5:40:48 AM com.apple.loginwindow[122] FAILED TO GET ASN FROM CORESERVICES so aborting.
3/7/11 5:40:49 AM com.apple.launchd[1] (com.apple.loginwindow[122]) Job appears to have crashed: Abort trap
3/7/11 5:40:49 AM com.apple.launchd[1] (com.apple.loginwindow) Throttling respawn: Will start in 7 seconds
3/7/11 5:40:49 AM com.apple.ReportCrash.Root[60] 2011-03-07 05:40:49.645 ReportCrash[60:583b] Saved crash report for loginwindow[122] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow_2011-03-07-054049_localhost.crash
3/7/11 5:40:57 AM com.apple.UserEventAgent-LoginWindow[129] ALF error: cannot find useragent 1102
3/7/11 5:40:57 AM com.apple.UserEventAgent-LoginWindow[129] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
3/7/11 5:40:57 AM com.apple.launchd[1] (com.apple.coreservicesd[134]) Job appears to have crashed: Bus error
3/7/11 5:40:57 AM com.apple.ReportCrash.Root[137] 2011-03-07 05:40:57.401 ReportCrash[137:2a03] Saved crash report for coreservicesd[134] version ??? (???) to /Library/Logs/DiagnosticReports/coreservicesd_2011-03-07-054057_localhost.crash
3/7/11 5:40:57 AM com.apple.loginwindow[132] FAILED TO GET ASN FROM CORESERVICES so aborting.
3/7/11 5:40:57 AM com.apple.launchd[1] (com.apple.coreservicesd) Throttling respawn: Will start in 10 seconds
3/7/11 5:40:58 AM com.apple.launchd[1] (com.apple.loginwindow[132]) Job appears to have crashed: Abort trap
3/7/11 5:40:58 AM com.apple.launchd[1] (com.apple.loginwindow) Throttling respawn: Will start in 9 seconds

Take out the new RAM, re-insert the old RAM. If the problem goes away, you have your answer.

Plus 1 for that, it could be a simple problem of bad RAM, if the suggestion above works for you then I would recommend A: Checking you have the right RAM for the machine and B: Getting replacement RAM.

HTH
- Simon

Alrighty. The upgrade was done in late December and yesterday was the first time I've had a problem with booting. I bought the RAM from OWC and simply added it to the 1 GB that was already in the computer and had no ill effects 'til yesterday.

I'll take out the new stick and see how the computer responds...but the problem is I've only had one faulty boot, and I've booted it twice since yesterday with no problems...so I'm not sure if a clean boot will mean anything.

FWIW, system profiler reads the RAM just fine.

AUZambo said:

Alrighty. The upgrade was done in late December and yesterday was the first time I've had a problem with booting. I bought the RAM from OWC and simply added it to the 1 GB that was already in the computer and had no ill effects 'til yesterday.

I'll take out the new stick and see how the computer responds...but the problem is I've only had one faulty boot, and I've booted it twice since yesterday with no problems...so I'm not sure if a clean boot will mean anything.

FWIW, system profiler reads the RAM just fine.

Click to expand...

Well now that timeline is a significant detail. Reading your prior post, one would think you just did the upgrades. Given this, it's less likely the RAM, but still worth looking into.

I see a lot of mentions of a "bus error". That is a bit worrisome... sounds like perhaps the motherboard is failing. You should run an Apple Hardware Test to check things out. You didn't mention what Mac you have. Assuming Intel-based...
Intel-based Macs: Using Apple Hardware Test

lifeisabeach said:

Well now that timeline is a significant detail. Reading your prior post, one would think you just did the upgrades. Given this, it's less likely the RAM, but still worth looking into.

I see a lot of mentions of a "bus error". That is a bit worrisome... sounds like perhaps the motherboard is failing. You should run an Apple Hardware Test to check things out. You didn't mention what Mac you have. Assuming Intel-based...
Intel-based Macs: Using Apple Hardware Test

Click to expand...

Yeah...I just read my OP and I wasn't exactly clear! I was focusing more on staying under the 10,000 character limit!

I ran the hardware test a few weeks ago and it didn't uncover any problems...but I'll do it again as soon as I have time. I'm guessing it won't find anything wrong. Is the hardware test fool proof, or can something slip past it?

When I opened up my computer today I got this error message:



Apparently my hard drive was renamed "bqw" at some point (probably when my 18 month old was "typing" on the keyboard).

I'm about to run the hardware test to see if that uncovers anything else...but I'm going to get in touch with Newegg and Samsung (the maker of my new HD) to request a replacement. I'll see if I can swap HD types or if I'm locked into the samsung model now.