Fails to boot, could bad ram cause failure to boot?

About a 2010 MacBook Pro fails to boot. The Apple logo comes up with the spinning gear and never goes further. The hard drive sounds like it's running and it will not boot up from an external drive with OS installed.
I'm thinking it's a bad logic board but could bad ram cause it to fail to boot?

Do you get any beeps?
1 - No RAM
2 - Incompatible RAM
3 - Faulty RAM
4 - No good boot image in boot ROM
5 - Failed processor
Those are beeps, not the normal startup chime.

Similar Messages

Could Bad RAM Cause Video Problems in 1st Gen 24" iMac

I have been having video problems with my 1st Gen 24" iMac over the past 6 months, but recently the machine wouldn't turn on at all. I left it at my local Apple Store to be diagnosed and they said that it was just a bad stick of RAM (not a big deal, its cheap these days). But what I forgot to ask them was, could that bad RAM be causing the video problems I've been having or is it the video card also?
Thanks!

Are you still having video problems since the ram was replaced? If the problem went away then it was the cause, it not then something else is.

Could bad RAM be the cause??

When I ordered this iMac from SmallDog, I had them add a 512MB module and it hasn't appeared to cause a problem (it shows up in Profiler and no tests have ever shown a problem).
However, almost since I got the iMac in late June, I have had nothing but problems with
(1) staying connected to the internet (dialup), disconnecting me anywhere from less than 60 seconds to an hour or so repeatedly, and
(2) I have gone through 5 different USB hubs from two different manufacturers (Macally and Iogear) with the same problem continuing: One or more of my peripherals lose power / become unresponsive intermittently. The only fix is to repeatedly unplug/plug back in. This happens anywhere from 5 minutes to ? after booting up.
After troubleshooting with my ISP and getting hubs replaced, I've spent a lot of time with Apple tech support and after all the software troubleshooting incl. running fsck (all ok) and erase/install, they have now issued an order to test (replace?) the power board strip (or whatever the part is called that connects all the ports in back of the iMac), the logic board, the modem cable assembly and card.
Anyway, I will have to take it in tomorrow and here (finally) is my question:
Could the added RAM have anything to do with my problems and should I remove the added 512MB before taking it in?
FYI, my iMac is on the Apple list of first generation iMacs with logic board/capacitor/etc problems.

I don't think RAM is the issue since it relates to the USB power. If the issue persists with factory only RAM, then that would be significant to know. I would test that first, and let the repair center know if you can reproduce it with only factory RAM. Removing the RAM though be careful, static electricity can damage the logic board. If you don't feel comfortable doing it, ask a repair center to do it for you, so you can eliminate that as a potential problem.

Neo2 Plat wont boot for 10+ minutes after failure to boot.

I have had my system fail to boot twice now because I OCed something it did not like... unplugged everything, re-set j-bat and pulled C-Mos battery still nothing.
Leave it unplugged and come back in a half hour it starts right up.
?? What is this all about?
If you guys dont have an explanation for me then I will have to blame my PSU.
At least now I have the D-Bracket installed for when it happens again I can see if any power is on the board at all....as it seemed there was nothing at all.

Quote
Originally posted by bentvalve
I have had my system fail to boot twice now because I OCed something it did not like... unplugged everything, re-set j-bat and pulled C-Mos battery still nothing.
Leave it unplugged and come back in a half hour it starts right up.
?? What is this all about?
If you guys dont have an explanation for me then I will have to blame my PSU.
At least now I have the D-Bracket installed for when it happens again I can see if any power is on the board at all....as it seemed there was nothing at all.
Sounds to me like the PSU is overloaded and goes into protection mode. When a PSU is overloaded thats what usually happens.
Of course, if you had a sig... or gave any system details at all... then we might have more of a clue.
Chip

Macbook Problems: Hard Drive Failure or Bad Ram?

I bought a used Black Macbook several months ago. Everything was fine until recently I ran into some problems. It wouldn't boot one day at all, so I wiped the drive clean and reinstalled Snow Leopard. Once again everything was fine for a while until the same thing happened and I once again wiped and reinstalled. The first time it happened I used diskwarrior and disk utility to try and repair the drive with no luck. The weird thing is that after reinstalling I can check the disk and it verifies as ok until one day it fails.
I know that the guy I bought the laptop from upgraded the RAM and the HDD. He didn't do such a good installing the HDD since the IR port and Sleep Indicator Light don't function properly anymore. I've read that happens a lot when installing a new HDD.
So, Here are the symptoms:
Disk Failures
Erratic boot times: Sometimes only 90 seconds, sometimes as long as 13 minutes
Hang ups, beach balls in normal every day tasks
Complete system freezes during normal use
I've never had a kernel panic.
Recently when the system wouldn't boot I ran in verbose mode and it said something about error reading kernel cache Error 0x80000020
Is this definitely my HDD, or could my RAM be causing this?

Thanks for the replies!
Yeah, I think it's the HDD. I was just worried that the RAM was bad and corrupted the HDD or something, but given the symptoms I think you guys are right. Ordered a 7200RPM 320GB HDD off Amazon Prime...will be here tomorrow
I'll post how it goes after I finish installing it. I'm backing up as I type.
I wonder if I can fix the ir port and the sleep indicator light when I install the hard-drive. The sleep indicator light never turns off. It stays on as long as my computer is on, only turns off when I shut it down.

IMac Drive Failures and Boot Camp - large install experience and question

We have a large 24" iMac install, purchased in August of '08, 49 machines spread across 6 offices. All run Windows Vista in Boot Camp as their primary (and mostly sole) operating mode - I will be happy to explain why after we get this cleared up, but that is not the point of this question.
We have had 11 hard drive failures, a rate of over 22% in one year. No machine has failed twice. The equipment was purchased in different groups so a bad lot is unlikely. I am aware that there is an HD failure issue with the iMac's but this seems to be extreme. Personally I've been building apples and pc's since my first apple kit, have a mac plus in a box somewhere, and am fond of these machines (as is the staff) but I've never seen a failure rate like this.
It has been suggested that it is the use of Boot Camp that is causing these failures. While I have seen viruses over the years that can lead to hardware failure I've never seen validated (or even simply non-malignant) software have the same effect.
Any thoughts on this? Could BC be the cause? Is this failure rate unusual? Have folks heard of similar cases? Thanks.

no one has any thoughts on this?

RAM slot failure on a Equium P300-16T

Hi, Ive got a RAM slot failure on a Equium p300-16T. I have tested both RAM modules and there in perfect working order. RAM slot 1 works and laptop boots successfully but as soon as RAM module inputed into RAM slot 2 no boot.
My frustration comes from when i began a warranty repair on Friday night through the website and it refused to accept it stating that the server had timed out. Unfortunately this timing out seem to happen every time i went to finish the warranty claim. And to my dismay my Serial number is no longer available on the website due to the warranty running out today (2nd of August).
Is there anything i can do?
Kind Regards
Ian Watt

What size RAM are you installing?
The system is capable of 2GB Max in total, so if you are installing RAM above 2GB, booting will/may fail.
You may be able to install a 2GB Module in Slot A, but it will probably be unstable and cause intermittent BSOD's. Or not boot at all. (not recommended)
I believe your laptop has the Santa Rosa chipset, which requires RAM in at least Slot A.
If you install RAM in Slot B only, it wont boot.
So basically to get the most out of the system, you should have a 1GB Module in each slot, which is how it comes from the factory if the specs found in google are correct.

Mac Pro Display flicker & failure to boot

Hello people who are smarter than me.
I have a 2008 Mac Pro 3.2/ 8CX 8800GT with the original Geforce video card installed. When I turn the machine on I get a grey screen with a black bar at the top, with no evidence of an actual boot (such as a darker grey apple in the middle of the screen.
After a minute or so, the screen retains the form of the black and white horizontal bar at the top but adds a rapidly cycling/strobing organge red and yellow flicker reminiscent of the old Monty Python crazy title screens.... It looks like this if you blink fast enough... or take a still photo.
I live in Haiti, where a fair amount of dust is constantly invading my tower, so I've had dust related issues before with memory... THis time, I don't think it's that. I've cleaned out the tower with pressurized air, reseated the memory and reseated the video card as well, to no advantage. The problem first came when the computer was working fine and while my daughter was opening a page on Firefox the screen just started jittering with this little color show. At the time, though, you could still see the desktop behind all the flickering. Now the computer doesn't seem to even boot. If I have to fly to the states to fix this, I'd love to not have to haul the whole machine, so if we can get this down to a couple likely parts that I could travel with, test and replace, that would be great. This is a hardware issue, right? Would video card failure make sense of this AND the failure to boot? AND if I do replace it, is the ATI Radeon HD 5770 Graphics Upgrade Kit still the ticket? If you help me, you'll be helping a lot of Haitians too, as I use this computer for humanitarian work with the Apparent Project. Help me Obi Geeks, you're my only hope!

Okay, so after doing all of the above, the computer still takes between 40 seconds and 1 minute or so to boot up, and the VersionCue messages still appear. However I discovered that the "kdcmond cannot retrieve..." messages disappeared after I disabled my ethernet connections. So at least I know that that had nothing to do with the extended boot-up time.
I have heard that the more RAM you have, the longer it takes to boot due to the RAM count. Since I have 10 GB, maybe this is why?
I've included the most recent Console messages below:
22/4/08 9:56:16 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
22/4/08 9:56:16 AM com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
22/4/08 9:56:16 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
22/4/08 9:56:39 AM com.apple.SystemStarter[28] Starting Aladdin USB daemon
22/4/08 9:56:39 AM org.ntp.ntpd[25] Error : nodename nor servname provided, or not known
22/4/08 9:56:39 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
22/4/08 9:56:39 AM com.apple.launchctl.Aqua[90] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
22/4/08 9:56:42 AM com.apple.launchd[82] (0x1011e0.VersionCueCS3monitor) Failed to check-in!

Failure to boot after restarting, no distinct pattern.

My Mac Pro has an issue where every third or fourth restart the mac will fail to boot, needing me to hold the power button until it turns off.
I get the grey apple and the spinning progress wheel for 30 seconds, then the screen stays grey and the apple is replaced by what looks like a circle with a diagonal bar through it. I believe this means something along the lines of 'No Bootable Directory Found'.
Before the 10.5.2 update this happened almost every restart. I'm using a Samsung Spinpoint 750gig drive as my boot drive, and the stock 500gig drive as a media disk.
I have tried several solutions. Repair permissions, Disk Utility from CD and run verify and repair disk, AHT extensive, TechTool Deluxe with surface scan, Format and Reinstall (twice), Memtest, NVRam.
Could the Samsung drive be bad even though I can't get any software to find a fault?

Here is a console log of the most recent failure to boot. The events here are a restart, a failure to boot, a forced off and a power on. Hopefully this helps.
27/02/2008 02:31:00 com.apple.launchd[68] (0x10a650.Locum[2615]) Exited: Terminated
27/02/2008 02:31:57 com.apple.launchd[68] ([0x0-0xa00a].com.apple.dock[94]) Stray process with PGID equal to this dead job: PID 2586 PPID 1 DashboardClient
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein: 0 entries in power event schedule table
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein: 1 entries in power event schedule table
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * date: 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * appName: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * eventType: wakepoweron
27/02/2008 02:32:07 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:32:07 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:32:07 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:32:08 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 02:34:04 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 02:34:04 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 02:34:04 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 02:34:04 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 02:34:22 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 02:34:23 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 02:34:23 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 02:34:23 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 02:34:23 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 02:34:23 com.apple.launchd[69] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 02:34:24 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 02:34:31 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 02:34:33 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:38:49 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 0 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 0 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 1 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * date: 02/27/08 21:35:00
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * appName: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * eventType: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 0 entries in power event schedule table
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 1 entries in power event schedule table
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * date: 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * appName: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * eventType: wakepoweron
27/02/2008 02:39:48 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:39:48 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:39:48 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:39:48 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 02:40:11 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 02:40:11 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 02:40:11 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 02:40:11 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 02:40:30 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 02:40:30 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 02:40:30 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 02:40:30 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 02:40:30 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 02:40:30 Dock[97] _DESCRegisterDockExtraClient failed 268435459
27/02/2008 02:40:31 com.apple.launchd[69] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 02:40:31 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 02:40:37 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 02:40:40 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 0 entries in power event schedule table
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 1 entries in power event schedule table
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * date: 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * appName: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * eventType: wakepoweron
27/02/2008 02:40:45 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:40:45 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:40:45 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:40:45 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 04:06:51 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 04:06:51 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 04:06:51 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 04:06:51 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 04:07:07 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 04:07:07 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 04:07:07 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 04:07:07 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 04:07:07 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 04:07:07 Dock[96] _DESCRegisterDockExtraClient failed 268435459
27/02/2008 04:07:08 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 04:07:08 com.apple.launchd[73] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 04:07:15 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 04:07:18 com.apple.SystemStarter[16] Starting Aladdin USB daemon

Memory corruption due to bad RAM in late 2012 iMac

I just unpacked a brand new late-2012 iMac a few days ago. Its specs are basically maxed out, only choice being the 3TB fusion drive. To summarize:
3.4 GHz Core i7
32GB RAM
3TB Fusion Drive
2GB NVidia
Latest patches for Mountain Lion
Since I got it, I have been experiencing intermittent abnormalities with it. Programs randomly crash with error messages along the lines of "such and such file appears corrupt, please run --repair".
I do a lot of programming in my job and just today I started getting bizarre 'segmentation fault' messages in Terminal. What worked just a few minutes ago started crashing with a segfault. The exact same programs have no negative effect on my Macbook Pro and work just fine. In a matter of minutes, the entire iMac became unresponsive and I got the "we shut down your computer to prevent damage" panic screen.
After a reboot, I started thinking it could be some sort of memory corruption. I downloaded the 'memtest' utility and started the basic test with:
memtest all 2
In just a few minutes, below are the results I receive (I re-ran multiple times to the same effect).
Any opinions on whether this is indeed bad RAM? How do I handle this with Apple support? Any suggestions/comments are most welcome.
Thank you,
Ozgun
Excerpt from the crash report in Console:
Process:         ghc [96618]
Path:            /usr/local/lib/ghc-7.6.2/ghc
Identifier:      ghc
Version:         ???
Code Type:       X86-64 (Native)
Parent Process: Emacs-10.7 [37299]
User ID:         501
Date/Time:       2013-03-20 21:06:30.389 -0400
OS Version:      Mac OS X 10.8.3 (12D78)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ghc                                     0x000000010bb44b10 evacuate1 + 5296
1   ghc                                     0x000000010bb4927f scavenge_block1 + 703
2   ghc                                     0x000000010bb4a78c scavenge_loop1 + 1548
3   ghc                                     0x000000010bb4639e scavenge_until_all_done + 798
4   ghc                                     0x000000010bb46c57 GarbageCollect + 1639
5   ghc                                     0x000000010bb378ff scheduleDoGC + 991
6   ghc                                     0x000000010bb3982b schedule + 1579
7   ghc                                     0x000000010bb39df4 scheduleWaitThread + 164
8   ghc                                     0x000000010bb3478e real_main + 68
Memtest Results:
Memtest version 4.22 (64-bit)
Copyright (C) 2004 Charles Cazabon
Copyright (C) 2004-2008 Tony Scaminaci (Macintosh port)
Licensed under the GNU General Public License version 2 only
Mac OS X 10.8.3 (12D78) running in multiuser mode
Memory Page Size: 4096
System has 8 Intel core(s) with SSE
Requested memory: 24009MB (25176211456 bytes)
Available memory: 24009MB (25176211456 bytes)
Allocated memory: 24009MB (25176211456 bytes) at local address 0x0000000101000000
Attempting memory lock... locked successfully
Partitioning memory into 2 comparison buffers...
Buffer A: 12004MB (12588105728 bytes) starts at local address 0x0000000101000000
Buffer B: 12004MB (12588105728 bytes) starts at local address 0x00000003ef4f4000
Running 2 test sequences... (CTRL-C to quit)
Test sequence 1 of 2:
Running tests on full 24009MB region...
Stuck Address       : testing 1 of 16
FAILURE! Data mismatch at local address 0x0000000262d778c0
Actual Data: 0x0200000262d778c0
Linear PRN          : testing 1 of 16
FAILURE! Data mismatch at local address 0x0000000262d77900
Expected Data: 0xa378ecfaa3ecf6b9, Actual Data: 0x0178ecfaa3ecf6b9
Running comparison tests using 12004MB buffers...
Random Value        :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x3ddd57d041eb5a06, BUFB Data: 0x3fdd57d041eb5a06
Compare XOR         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x826aabfcebf44332, BUFB Data: 0x806aabfcebf44332
Compare SUB         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x8e6cbb4010b8a88d, BUFB Data: 0x8a6cbb4010b8a88d
Compare MUL         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x54fd2f0176d1ab9e, BUFB Data: 0xfefd2f0176d1ab9e
Compare DIV         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000002
Compare OR          :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x6eaf35c4f7fc13fb, BUFB Data: 0x6caf35c4f7fc13fb
Compare AND         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x6ea704c077fc1399, BUFB Data: 0x6ca704c077fc1399
Sequential Increment:
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x7caad7e9fb32b8ca, BUFB Data: 0x7eaad7e9fb32b8ca
Solid Bits          : testing 1 of 64
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0xfdffffffffffffff, BUFB Data: 0xffffffffffffffff
Block Sequential    : testing   1 of 256
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000000
Checkerboard        : testing 1 of 64
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x0155555555555555, BUFB Data: 0x5555555555555555
Bit Spread          : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000005, BUFB Data: 0x0000000000000005
Bit Flip            : testing   1 of 512
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0xfdfffffffffffffe, BUFB Data: 0xfffffffffffffffe
Walking Ones        : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x11fffffffffffffe, BUFB Data: 0xfffffffffffffffe
Walking Zeroes      : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000001, BUFB Data: 0x0000000000000001
Test sequence 2 of 2:
Running tests on full 24009MB region...
Stuck Address       : testing 1 of 16
FAILURE! Data mismatch at local address 0x0000000262d778c0
Actual Data: 0x0200000262d778c0
Linear PRN          : testing 1 of 16
FAILURE! Data mismatch at local address 0x0000000262d77900
Expected Data: 0xa378ecfaa3ecf6b9, Actual Data: 0x0178ecfaa3ecf6b9
Running comparison tests using 12004MB buffers...
Random Value        :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0xf54d78773a1d75d1, BUFB Data: 0xf74d78773a1d75d1
Compare XOR         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x01e08f19e0bd343d, BUFB Data: 0xbbe08f19e0bd343d
Compare SUB         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x01e38c4ae6cbd9e0, BUFB Data: 0x5be38c4ae6cbd9e0
Compare MUL         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x01d2ccf452aabcc0, BUFB Data: 0x5ed2ccf452aabcc0
Compare DIV         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000003, BUFB Data: 0x0000000000000003
Compare OR          :
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x01f97d3f343b8641, BUFB Data: 0xe7f97d3f343b8641
Compare AND         :
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x0181413c143a0641, BUFB Data: 0xe381413c143a0641
Sequential Increment:
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x11df0c80ebf82821, BUFB Data: 0xf2df0c80ebf82821
Solid Bits          : testing 1 of 64
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x11ffffffffffffff, BUFB Data: 0xffffffffffffffff
Block Sequential    : testing   1 of 256
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000000, BUFB Data: 0x0000000000000000
Checkerboard        : testing 1 of 64
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x0155555555555555, BUFB Data: 0x5555555555555555
Bit Spread          : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000005, BUFB Data: 0x0000000000000005
Bit Flip            : testing   1 of 512
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0xfdfffffffffffffe, BUFB Data: 0xfffffffffffffffe
Walking Ones        : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d77900, BUFB address 0x000000055126b900
BUFA Data: 0x11fffffffffffffe, BUFB Data: 0xfffffffffffffffe
Walking Zeroes      : testing   1 of 128
FAILURE! Data mismatch at local BUFA address 0x0000000262d778c0, BUFB address 0x000000055126b8c0
BUFA Data: 0x0200000000000001, BUFB Data: 0x0000000000000001
*** Address Test Failed *** One or more DIMM address lines are non-functional.
Execution time: 230 seconds.
➜ ~ memtest all 2

This must be my last last thing. AHT was on an iMac I bought in 2009. It was included on my "disk 2" along with several other applications. When I wiped and installed the full Lion, AHT was gone. Same is true for the full Mountain Lion installation media. It does not have AHT. I'm not at all sure how to get it back from Apple.
I was able to find it on my SL disc 2 and extract it again from that. Disc 2 won't install on Mountain Lion (the packages are too out of date) but the AHT pkg does.
Since you have it, consider packing it up and keeping it safe. Maybe someone who knows AHT better than I can elaborate on AHT. From what I've seen, you get it when your mac ships but if you ever wipe and reinstall the OS, you lose it.

Bad RAM indication on D-LED diagnostics

What error code combination would the D-LED diagnostics indicate if one had bad motherboard RAM? Would it be the Boot Attempt indication?
Thanks!
Charles

Arioch said:
Well as a sidenote (not saying that it is not ram since that is the primary suspect), I just wanted to add that I have managed to get the "Bad ram" (mostly it was early chipset intialisation error) error message if my previous graphicscard was not 100% seated properly.
My D-LED error code appears without any video adapter installed. In fact, it occurs without any RAM installed. Just powering the board alone caused the D-LED error message. I'm thinking the motherboard may be defective now.
"Also have learned that seating RAM modules on these boards are much tougher than any other encountered. When you belive it is seated it might not be so. The plastic locks must fully click into place before it is seated.
When I mean click into place I mean really click into place. 99% of the times the plastic locks feels and looks like they are in place, but they can usually be "locked" more, which is needed."
This is interesting! However, I have only 1 stick of RAM and I did notice it was not seated properly at first. But the error code continues to come up even with the RAM completely removed from the m/b. I'm beginning to suspect the m/b as being defective.
Dont know if this was a good explanation, wish I could explain it more properly in english.
You've done just fine and I appreciate your trying to help! Thanks.
Charles

Intermittent failure to boot, flashing question mark or white screen

So, I've had two MacBooks with similar problems (I am a Mac consultant). The first one would intermittently boot to a white screen, often enough to be annoying. This current one is occasionally booting to a flashing question mark. My first thought is, of course, the hard drive, but in both cases the hard drive tests fine using SMART Utility, which is usually great at giving advance warning when a drive starts experiencing hardware errors.
On the first MacBook, the one with the white-screen boots, I tried reinstalling the system with no effect; replacing the drive eventually made the problem go away. The current MacBook, with the question-mark boots, has already had its drive replaced once, when the stock drive failed.
I will reseat the drive, which is all Apple could suggest. I just wonder if anybody else had experienced something like this and can offer any information about what might be going on.

Thanks for the reply. Aside from finding that holding the mouse button down at boot might cause a flashing question mark, I already knew all that. I will ask the owner if she is leaning on the trackpad button when she starts up her computer in the morning.
I've already reset the power manager and the PRAM; we'll see if that makes any difference. The puzzling thing here is that the problem is intermittent.
I also need to ask her if, when the computer does boot to the question mark, there has been a chime first. Somehow I think there has to be, for the system to have gotten as far as looking for a boot drive. I couldn't find anything useful in the logs; not surprising, since if it can't find a drive to boot to, it won't have anything to write a log to.
Again, the mystery is why the failure to boot is intermittent. If it happened every time, I'd know what to do!
Thanks
cavenewt

How Can I Tell if I Have a Bad RAM Terminal?

A few weeks ago, my MacBook Pro started freezing several times a day, and it was to the point where I couldn't use it for even 10 minutes. It would also beep three times most of the time that it froze. So I turned it off for like 3 weeks and then took it in to the Genius Bar.
He ran some tests and said it was a RAM issue and I could buy new RAM chips (or whatever) and so I did, and when I installed two of them, my computer wouldn't start. I thought maybe the MHz was too big. I took one out, and the computer worked fine. For thirty minutes. Then BEEEEP beeeeeep BEEEEEP
I removed the one RAM and reseated it in the other terminal, and my computer has been working fine for most of the morning. I am running Chrome and playing youtube, Facebook, uploading pictures, and using iPhoto.
My MacBookPro came with 2 2GB RAMs (1333 MHz). The new RAMs are 2 4GB DDR3 OC3-10666 and compatible with 1333MHz and 1066MHz, according to the package.
The closest Apple store to me is more than an hour drive, and I'm wondering if there are any tests I can do at home. To me, an inexperienced computer repairwoman, it looks like I have a bad RAM terminal. Tonight I will reseat the RAM in the first terminal I tried, and see if it freezes and beeps again. It's possible that it was just seated incorrectly, perhaps?
Please send any and all advice, thoughts, questions, etc. Thank you!

As John Galt says, not all RAM is created equal. Crucial.com or MacSales.com (OWC) are well respected Mac RAM vendors.
Rember
<https://www.macupdate.com/app/mac/15837/rember/>
is a wrapper around memtest.
Note: If you Mac refuses to run the app, you can force it by doing Control-Click -> Open, and then agreeing to the dialog box. Rember is an unsigned app, which is why the Mac may complain. The Control-Click -> Open trick is a way to force the Mac to run the unsigned app.
If you are having problems betting into a full Mac OS X GUI, then you might want to get memtest which can be run from the command line in Single-User mode (boot holding Command-S). If you have installed 'Rember' you can find a copy of 'memtest' buried inside
./Rember.app/Contents/Resources/memtest all
the ./ means you have to figure out the front part of the directory path to Rember.app where ever you stored it.
Here are some additional web sites, but keep in mind that 'Rember' is a wrapper for 'memtest' so when those sites discuss 'memtest', 'Rember' is essentially the same thing.
<http://guides.macrumors.com/Testing_RAM>
<http://osxdaily.com/2011/05/03/memtest-mac-ram-test/>
<http://support.apple.com/kb/ht1509>
<http://support.apple.com/kb/PH11342>

Bad PBR sig and dual booting with Windows

This site's menu config is too difficult for me...
fyi.
=>
Below is the cases that happened in my environment
when installing Solaris 8 Operating Environment, Intel Platform Edition
Some will help you, and some may be just for your thinking.
Bad PBR sig
You know what it means?
I don't know.
If you know, let me know please...
@ Case 1
My Seagate ST39236LW 9.2GB HARD DISK fdisk info
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 Solaris 7183 14341 7159 50
(I use cylinder number to partition hard disk. Why?
When I use % and insert 1% to partition 2 then
fdisk makes start cylinder 7155.
It overlays with partition 1's end cylinder number.
So fdisk save(menu no 4) fails...
because the partition 1's start cylinder number is 0 ?)
After rebooting, bizarre Bad PBR sig, and my system dies...
So I boots my PC with Windows(or Dos) booting diskette.
A> fdisk
First Hard Disk partition info
1 NTFS 4377 50%
2 NON-DOS 10 0%
3 A NON-DOS 10 0% <= Solaris created x86 boot
4 NON-DOS 4363 0%
Solaris created extra X86 boot partition 3 and made it active.
But partition 3 could not boot...
I made partition 2 active from dos fdisk menu,
and pc boots well.
After rebooting, my disk partition info is like this
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7166 7182 17 0
3 x86 boot 7183 7199 17 0
4 Solaris 7200 14341 7142 50
Then after installation?
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active x86 boot 7165 7181 17 0
3 Solaris 7200 14341 7142 50
Partition 2 and 3 changed...
Where did partition 3 go???
Just deleted?
Then why partition 2 Start cylinder changed?
@ Case 2.
Another queer thing....
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 IFS:NTFS 0 7165 7166 50
2 Active Solaris 7166 14341 7176 50
In Solaris x86 format fdisk menu,
if I've allocated remaining disk space all to Solaris(without x86 boot),
then Solaris also makes x86 boot partition(size 10MB), reboots well.
But install fails due to not enough free disk space
when install begins slicing Solaris partition.
error log says
Installing 32 Bit Solaris Packages
- Configuring boot device
- Using disk(c0t0d0) for "rootdisk"
- Deleting x86 boot fdisk partition (c0t0d0)
- Creating x86 boot fdisk partition (c0t0d0)
ERROR:Not enough free space to create x86 Boot fdisk partition(c0t0d0)
Why does Solaris delete and create x86 boot partition?
Why did it exist?
Case 3.
If I've fdisked like this, what will happen???
Total disk size is 14342 cylinders
Cylinder size is 1251 (512 byte) blocks
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1

BAD PBR SIG message comes from your BIOS - no partition boot record.
Sorry but it's not clear what else is going on - might be worth running a ODS based fdisk to clear the disk before installing Solaris?

V1.2.1 found my problem - bad RAM!

FCP HD 4.5 QT 7.0.3 Compressor 1.2.1
Bad RAM in my G5 was my problem. I never had the "cannot connect to back ground process" problem just kernel panics message forcing shutdown.
I removed 2x1Gb sticks installed by Apple reseller, so far so good w/ factory 512MB. Importantly, although I hardly stressed the machine in 4 days nothing else crashed - only compressor even on 3min short QT self-contained movies. FCP HD editing for 3-4 hrs = fine, CS fine, Internet, mail, newsreaders etc all okay - just compressor seemed to allocate well into my faulty 2gb sticks.
After a doom & gloom weekend trying to get a client DVD done I am very much relieved my $2,200 purchase is now working and just wanted to post my experience.
I didn't really consider I had a hardware problem. PULL THAT RAM back to factory installed is a must check for unexplained crashes on G5...I knew that too but I took some convincing before removing RAM tonight!
**** I thought I'd never see the back of my trusty G4DP - I think it's earned its place to remain as back-up/server/disc burning machine

Okay, this is weird. I can get around this by setting the 'Select default path for scripts' preference to something other than blank!
I'm wondering if this is because a group policy sets the default homedrive / My Documents folder to something on a network share. Could it be that having this value blank is causing SQL Developer to poll this share, and therefore the network, causing the performance issue?
As it is, setting the value to something on the local drive (C:\) seems to fix it - contrary to what other posts have had to say on the matter of this preference!

Fails to boot, could bad ram cause failure to boot?

Similar Messages

Maybe you are looking for