Comments on: Memtest86+ Adds Intel Mac Support (Second Update)

By: Josh Powell

Josh Powell — Sat, 12 Feb 2011 23:13:00 +0000

Threw many many errors on my new MacBook Pro with Core i7, but seems to work fine on Mac Pro with dual quadcore Xeons. Just another couple data points. Email if more details would help.

By: Christopher Price

Christopher Price — Mon, 30 Nov 2009 14:18:42 +0000

BIOS errors are possible, albeit not a frequent cause of memory errors. This is much more of a problem on overclocking-friendly boards that presume the user will know what speed to set their memory (for the purposes of overclocking the front side bus).

Typically, resetting motherboard defaults is a prudent thing to do when running into any system-level errors.

By: Norm

Norm — Sun, 29 Nov 2009 19:36:25 +0000

Well I used this to diagnose a buddy’s system stability issues. When I first ran it I got a slew of errors. When I looked at the RAM info I saw the system had misconfigured the RAM CAS settings and the voltage. I went into the BIOS and manually configured the RAM and then ran the test again. This time I had zero errors. I tel it run 3 times just to be sure. Just because you get errors does not mean the RAM is bad. It could simply mean your RAM isn’t configured properly by your BOIS.

Hope this helps.

By: Jeremiah

Jeremiah — Thu, 26 Feb 2009 20:56:01 +0000

Thought i should report in that i also got many errors from new memory in my Core 2 Duo MacBook Pro using Memtest86+ 2.01.

But the good news is that i grabbed the latest 2.11 version, and the memory tested clear.

By: Oskar

Oskar — Tue, 29 Apr 2008 20:10:48 +0000

Can confirm this on a MacBook Pro 17″ with new Crucial 2x2GB RAM. Spews errors.

By: Derek Schrock

Derek Schrock — Mon, 31 Mar 2008 03:46:10 +0000

I ran MemTest on a Macbook Pro with 4GB (2x2GB) and once per stick. Each test produced about ~1500 errors. Apple Hardware Test said that the RAM is “fine.”

By: Christopher Price

Christopher Price — Thu, 28 Feb 2008 01:23:40 +0000

Thanks for reminding me, I’ve posted an update above.

The only system you’d be able to use the Serial port on, is Intel-based XServes, which do have an RS-232 port on them for access and control. I wonder if that is routed so it would work without a drive (it could be powered by USB, not sure on that).

By: tck42

tck42 — Thu, 28 Feb 2008 00:18:25 +0000

(Hopefully) false positives here, too; figured I’d give it a try on my recently upgraded macbook (brand new 2x2GB Mushkin), reported a slew of errors. Was about to initiate RMA, and then decided to swap in the stock ram, same issue (not the same addresses, but a ton of errors). And I’d not had any problems with the system.

Was your keyboard working? Mine wasn’t, not sure they’re supporting USB keyboards?

You ever get a hold of the devs? I didn’t see any similar reports in the forums since September, when the original patcher for mac support apparently mentioned he was seeing similar issues… Though there’s a french section in the forums and I don’t speak french…

Anyways, good luck to you; perhaps I’ll post something to the forums. There’s support for a serial port but I’m not sure that really maps to any of the macbook’s hardware…

Nobody else tried this yet?!