2010 mini 8 gig ram upgrade = constant kernel panics

[wgscott]

I've got a stock 2010 mini booting into the 64-bit kernel. I purchased 2X4 gig ram from OWC. Either or both give kernel panics during playback. Usually this happens when a new track is loaded into memory, but if I try to boot off of an install CD, it panics upon boot.

 

Using one at a time still yields kernel panics. It would seem the probability of getting two bad ram modules is low, so could I be doing something else wrong?

 

I had to zap the v/p ram to get it going.

 

[audiofox]

Have you run any memory check or other hardware utilities yet (ie, memtest component of applejack, the Apple Hardware Test on your install DVD)? Also, which OWC memory modules did you purchase? Did your PRAM zap solve your problem, or are you still getting crashes? AS you probably already know, kernel panics are one typical sign of bad RAM modules, although it does seem unlikely that both of your modules are bad. Have you swapped your original modules back in to see if you still have the panics? I have the same machine with 2x4GB OWC RAM (their el cheapo non-name modules) and have had no problems (so far-knock on wood!). Fortunately, OWC is one of the best vendors in the business with respect to warranty and replacement support, so given them a call and let them help you out. Good luck, and please let us know how you fare.

 

[barron]

I have updated 2 2010 Mac Mini's with OWC ram and have had no problems. One thing you may want to check is that the ram modules are seated properly. As you know, they are inserted at an angle before being pushed down to their final position. Make sure you get them all the way in (push hard) when inserting them on the angle before pushing them down where they will click into place.

 

Barron

 

[wgscott]

It won't stay up long enough for a memory check.

 

As for seating, they are in there good enough to be recognized as being present, and I think about the same way as the two original memory boards, which I now have back in there (with no panics).

 

However, I am definitely a woos (sp?) when it comes to shoving memory in, so I will try. Could it cause a panic if it is in good enough to be recognized as present?

 

[barron]

Wimp + pussy = Wuss or Wussy

 

If the contacts aren't firmly touching, there could be an issue. But if the old memory works fine and you're putting it in the same way then it's probably seated correctly.

 

The OWC memory I purchased is #OWC8566DDR3S8GP and heres's the link:

http://eshop.macsales.com/item/Other%20World%20Computing/8566DDR3S8GP/

 

Is that what you're using?

 

Barron

 

[wgscott]

It is the same.

 

I am booting into 64-bit kernel. Are you?

 

It beeped at me until I reset the v/p/ram and after doing this multiple times I got it to boot up, etc. That seemed a bit odd, but a check on the apple forums suggested it wasn't that uncommon.

 

[audiofox]

Wgscott, what 64 bit programs are you running, and do they still run when you boot normally, ie, in "32 bit" mode? According to a thread I saw in the Apple discussions forum, the Mini and other 64 bit capable machines will run 64 bit apps in 64 bit mode without the need to force the machine to boot into an exclusively 64 bit mode. To that end, are you certain that your other kernel extensions are also 64 bit? If they are not, that cold be another explanation for your constant kernel panics if it is not traceable to the hardware.

 

[wgscott]

Everything but iTunes and Finder has been running in 64-bit. The 64-bit player programs (AyreWare, Audirvana, etc) will run that way whether you are booted into 64-bit or 32-bit kernel. The 2010 mini is the first one that will boot into 64-bit without having to be coerced. I've had it running that way with my 2 gig of memory since I bought it, with no issues. All other things equal, 64-bit software will run a bit better with a 64-bit kernel, and can address larger quantities of memory (which is why I am wondering whether I unmasked a problem).

 

I guess I should put the new memory back in and boot into the 32-bit kernel and see if that "solves" the problem.

 

[audiofox]

Hmmm, I've been reading a lot of threads on 32 and 64 bit mode and have not seen any that discuss a difference in speed/quality/etc for a 64 bit app if it is run in 32 or 64 bit "system kernel" mode (even for apps like Photoshop, which I think would be VERY noticeable and probably measurable)-can you point me to some info on that? FWIW, my office MBP has all 64 bit kernels except for a few core system kernels, which are presumably the "32 bit" system kernels mentioned elsewhere. I plan to check my Mini when I get home, but I suspect it is the same, since it is almost a virgin machine, with very little aftermarket apps installed on it.

 

[wgscott]

The 32-bit Kernel places a limitation upon how much memory a single program can access. I can't remember off the top of my head what that limit is but it is somewhere around 4 gig.

 

There are a lot of people who claim to be able to "hear" the difference between 32-bit and 64-bit kernels. I personally think that is kind of unlikely, but it is not an unusual claim.

 

[damien78]

One thing you may also try is to put one of your old module in bank #0 so that the system uses it first to boot.

And place one of the new modules in bank #1.

So you should be able to boot the SL DVD and be able to run the HW check, or even boot normally from the HDD and run a memcheck freeware.

And finally pinpoint the defective module.

 

[wgscott]

That is how I arrived at the conclusion that both are behaving the same way, which then leads me to suspect it might be something else that is going on. Unfortunately I haven't had any time to mess with this.

 

[wgscott]

I rebooted into the 32 bit Kernel, then shut down, swapped in the new memory, and I can't even go through the boot sequence without a kernel panic. So for whatever reason, the OWC memory is simply incompatible with my 2010 mini.

 

I guess I will have to send it back. I have 4 gig in a 2009 mini. I am tempted to swap that memory in to see what happens. If only each day had 4 more hours.

 

[wgscott]

I got replacement RAM today and it works flawlessly. Installation this time did not require pram or whatever zapping. I just put the memory in and it worked, and I have been taxing it heavily with memory play ever since.

 

So the moral of the story is that it IS possible for two modules to be problematic. Maybe they had a bad batch.

 

OWC stood behind its product and did everything to make it right, by the way (although shipping to and fro took forever).

 

 

 

[audiofox]

Wgscott, good to hear that you're up and running.