MacBook Kernel Panics Frequently

Hi Everyone,


I am new to Apple Support Communities. In fact this is my 1st attempt.


In the past 3 weeks I have had numerous Kernel panics. I have done several CLEAN installs of SL along with individual installations of Mac approved apps.


I have done several tests using TechTool Pro 6 and it tells me that everything is good and proper. My Hardware and RAM are ALL Approved gear.


User uploaded file


I personally suspect a "Software" issue. The last Kernel Panic occured whilst I was Browsing the net using "Safari".


When I rebooted again in "SafebootMode", a NEW message appeared saying my Time machine was currupt. Since that message, I have made another TM backup on a Different External HD.


I have browsed through the Kernal Panic report but I am unable pinpont the offending application. Attached please find my Kernal Panic Report.


Can some one, Please Please help.


"Start of Panic Report"


Tue Oct 2 11:28:32 2012

panic(cpu 1 caller 0x498af4): assertion failed: MBUF_IS_COMPOSITE(m), file: /SourceCache/xnu/xnu-1504.15.3/bsd/kern/uipc_mbuf.c, line: 3593

Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)

0x1043c78 : 0x21b837 (0x5dd7fc 0x1043cac 0x223ce1 0x0)

0x1043cc8 : 0x498af4 (0x5d1dd8 0x5d5720 0x5d410c 0xe09)

0x1043ce8 : 0x4b234d (0x5d5720 0x5d410c 0xe09 0x201)

0x1043d68 : 0x4966df (0x1043d9c 0x5ee 0x0 0x1)

0x1043da8 : 0xd6f91e (0x1 0x5ee 0x0 0x1043ddc)

0x1043df8 : 0xd6fb7b (0x0 0x7bdd549c 0xe7024ec 0x2)

0x1043e28 : 0x1600a5f (0xd097800 0xd22ceec 0x5ea 0x1043e7f)

0x1043e98 : 0x16051a4 (0xd097800 0x0 0x1043f48 0x13918dc)

0x1043ed8 : 0x553ec7 (0xd097800 0xd23fc80 0x1 0x6)

0x1043f28 : 0x552ea6 (0xd23fc80 0x0 0x0 0x0)

0x1043f88 : 0x552eea (0xd009c80 0xd009c80 0x0 0x8b03)

0x1043fc8 : 0x2a179c (0xd009c80 0x0 0x10 0xe006064)

Kernel Extensions in backtrace (with dependencies):

com.apple.nvenet(2.0.17)@0x15f8000->0x160efff

dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0x942000

dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x956000

dependency: com.apple.driver.NVSMU(2.2.7)@0x1527000

dependency: com.apple.iokit.IONetworkingFamily(1.10)@0xd68000

com.apple.iokit.IONetworkingFamily(1.10)@0xd68000->0xd7efff



BSD process name corresponding to current thread: kernel_task



Mac OS version:

10K549



Kernel version:

Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386

System model name: MacBook5,1 (Mac-F42D89C8)



System uptime in nanoseconds: 295464258214436

unloaded kexts:

com.apple.driver.AirPortBrcm43xx 423.91.27 (addr 0xf19000, size 0x1900544) - last unloaded 89137908567

loaded kexts:

com.displaylink.driver.DisplayLinkDriver 1.8

at.obdev.nke.LittleSnitch 2.5.4

com.apple.filesystems.afpfs 9.7.1 - last loaded 145538262353608

com.apple.nke.asp_tcp 5.0

com.apple.driver.AppleHWSensor 1.9.3d0

com.apple.driver.AppleHDA 2.0.5f14

com.apple.driver.AppleMikeyHIDDriver 1.2.0

com.apple.driver.AudioAUUC 1.57

com.apple.driver.AGPM 100.12.31

com.apple.driver.AppleMikeyDriver 2.0.5f14

com.apple.driver.AppleLPC 1.5.1

com.apple.driver.AppleBacklight 170.0.46

com.apple.kext.AppleSMCLMU 1.5.2d10

com.apple.driver.SMCMotionSensor 3.0.1d2

com.apple.filesystems.autofs 2.1.0

com.apple.driver.AppleUpstreamUserClient 3.5.7

com.apple.driver.AppleMCCSControl 1.0.20

com.apple.driver.AppleIntelPenrynProfile 17

com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1

com.apple.GeForce 6.3.6

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AudioIPCDriver 1.1.6

com.apple.driver.AppleUSBTCButtons 201.6

com.apple.driver.AppleUSBTCKeyboard 201.6

com.apple.driver.AppleIRController 303.8

com.apple.iokit.SCSITaskUserClient 2.6.8

com.apple.BootCache 31.1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.iokit.IOAHCIBlockStorage 1.6.4

com.apple.driver.AppleSmartBatteryManager 160.0.0

com.apple.driver.AirPortBrcm43224 428.42.4

com.apple.driver.AppleAHCIPort 2.1.7

com.apple.nvenet 2.0.17

com.apple.driver.AppleUSBHub 4.2.4

com.apple.driver.AppleUSBOHCI 4.2.0

com.apple.driver.AppleUSBEHCI 4.2.4

com.apple.driver.AppleEFINVRAM 1.4.0

com.apple.driver.AppleRTC 1.3.1

com.apple.driver.AppleHPET 1.5

com.apple.driver.AppleACPIButtons 1.3.6

com.apple.driver.AppleSMBIOS 1.7

com.apple.driver.AppleACPIEC 1.3.6

com.apple.driver.AppleAPIC 1.4

com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0

com.apple.security.sandbox 1

com.apple.security.quarantine 0

com.apple.nke.applicationfirewall 2.1.14

com.apple.driver.AppleIntelCPUPowerManagement 142.6.0

com.apple.iokit.IOBluetoothSerialManager 2.4.5f3

com.apple.iokit.IOSerialFamily 10.0.3

com.apple.driver.DspFuncLib 2.0.5f14

com.apple.driver.AppleHDAController 2.0.5f14

com.apple.iokit.IOHDAFamily 2.0.5f14

com.apple.driver.AppleProfileReadCounterAction 17

com.apple.driver.AppleSMBusController 1.0.10d0

com.apple.driver.AppleSMBusPCI 1.0.10d0

com.apple.driver.AppleBacklightExpert 1.0.1

com.apple.nvidia.nv50hal 6.3.6

com.apple.driver.IOPlatformPluginFamily 4.7.0a1

com.apple.NVDAResman 6.3.6

com.apple.iokit.IONDRVSupport 2.2.1

com.apple.driver.AppleProfileTimestampAction 10

com.apple.driver.AppleProfileThreadInfoAction 14

com.apple.driver.AppleProfileRegisterStateAction 10

com.apple.driver.AppleProfileKEventAction 10

com.apple.driver.AppleProfileCallstackAction 20

com.apple.iokit.IOSurface 74.2

com.apple.driver.AppleSMC 3.1.0d5

com.apple.iokit.IOGraphicsFamily 2.2.1

com.apple.iokit.IOAudioFamily 1.8.3fc2

com.apple.kext.OSvKernDSPLib 1.3

com.apple.iokit.AppleProfileFamily 41

com.apple.driver.AppleUSBHIDKeyboard 141.5

com.apple.driver.AppleHIDKeyboard 141.5

com.apple.driver.AppleUSBMultitouch 207.7

com.apple.driver.BroadcomUSBBluetoothHCIController 2.4.5f3

com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3

com.apple.iokit.IOBluetoothFamily 2.4.5f3

com.apple.iokit.IOUSBHIDDriver 4.2.0

com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8

com.apple.iokit.IOUSBMassStorageClass 2.6.7

com.apple.driver.AppleUSBMergeNub 4.2.4

com.apple.driver.AppleUSBComposite 3.9.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8

com.apple.iokit.IOBDStorageFamily 1.6

com.apple.iokit.IODVDStorageFamily 1.6

com.apple.iokit.IOCDStorageFamily 1.6.1

com.apple.driver.XsanFilter 402.1

com.apple.iokit.IOAHCISerialATAPI 1.2.6

com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8

com.apple.iokit.IO80211Family 320.1

com.apple.iokit.IOAHCIFamily 2.0.6

com.apple.iokit.IONetworkingFamily 1.10

com.apple.iokit.IOUSBUserClient 4.2.4

com.apple.iokit.IOUSBFamily 4.2.4

com.apple.driver.NVSMU 2.2.7

com.apple.driver.AppleEFIRuntime 1.4.0

com.apple.iokit.IOHIDFamily 1.6.6

com.apple.iokit.IOSMBusFamily 1.1

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 6

com.apple.driver.DiskImages 289.1

com.apple.iokit.IOStorageFamily 1.6.3

com.apple.driver.AppleACPIPlatform 1.3.6

com.apple.iokit.IOPCIFamily 2.6.5

com.apple.iokit.IOACPIFamily 1.3.0


"End of Panic Report"


Following are some other reports from previous Error reporting.


2/10/12 11:53:36 AMkernelUSBMSC Identifier (non-unique): 5743415A4131363032373539 0x1058 0x1110 0x2018
2/10/12 11:53:38 AMkerneljnl: disk1s2: replay_journal: from: 42901504 to: 50032640 (joffset 0x2ba5000)
2/10/12 11:53:39 AMkerneljnl: disk1s2: txn starting at 48173056 (48173056) @ index 87 bnum 950105 (8192) with disk cksum != blhdr cksum (0x75f01900 0xa0f5e7e6)
2/10/12 11:53:39 AMkerneljnl: 0x189a0000 0xe98d0000 0x1c0001ff 0x1e000000 0x12000000 0x69000c00 0x6f004e00 0x65006400
2/10/12 11:53:39 AMkerneljnl: disk1s2: restarting journal replay (42901504 - 48173056)!
2/10/12 11:53:39 AMkerneljnl: disk1s2: replay_journal: from: 42901504 to: 48173056 (joffset 0x2ba5000)
2/10/12 11:53:49 AMkerneljnl: disk1s2: journal replay done.
2/10/12 11:53:49 AMkernelhfs_swap_BTNode: record #-1 invalid offset (0x0000)
2/10/12 11:53:49 AMkernelhfs: node=53162 fileID=4 volume=MacBk 13 Tm Bkup 9.9.12 device=/dev/disk1s2
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs: cat_delete() failed to delete thread record on volume MacBk 13 Tm Bkup 9.9.12
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs_swap_BTNode: record #-1 invalid offset (0x0000)
2/10/12 11:53:49 AMkernelhfs: node=53179 fileID=4 volume=MacBk 13 Tm Bkup 9.9.12 device=/dev/disk1s2
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs: cat_delete() failed to delete thread record on volume MacBk 13 Tm Bkup 9.9.12
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs_swap_BTNode: record #-1 invalid offset (0x0000)
2/10/12 11:53:49 AMkernelhfs: node=53163 fileID=4 volume=MacBk 13 Tm Bkup 9.9.12 device=/dev/disk1s2
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs: cat_delete() failed to delete thread record on volume MacBk 13 Tm Bkup 9.9.12
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs_swap_BTNode: record #-1 invalid offset (0x0000)
2/10/12 11:53:49 AMkernelhfs: node=53163 fileID=4 volume=MacBk 13 Tm Bkup 9.9.12 device=/dev/disk1s2
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs: cat_delete() failed to delete thread record on volume MacBk 13 Tm Bkup 9.9.12
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs_swap_BTNode: record #-1 invalid offset (0x0000)
2/10/12 11:53:49 AMkernelhfs: node=53163 fileID=4 volume=MacBk 13 Tm Bkup 9.9.12 device=/dev/disk1s2
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:49 AMkernelhfs: cat_delete() failed to delete thread record on volume MacBk 13 Tm Bkup 9.9.12
2/10/12 11:53:49 AMkernel
2/10/12 11:53:49 AMkernelhfs: Runtime corruption detected on MacBk 13 Tm Bkup 9.9.12, fsck will be forced on next mount.
2/10/12 11:53:51 AMfseventsd[36]event logs in /Volumes/MacBk 13 Tm Bkup 9.9.12/.fseventsd out of sync with volume. destroying old logs. (297450 14 297450)
2/10/12 11:53:52 AMkernelhfs: Removed 0 orphaned / unlinked files and 179 directories
2/10/12 11:53:52 AMfseventsd[36]log dir: /Volumes/MacBk 13 Tm Bkup 9.9.12/.fseventsd getting new uuid: DF550D5D-1693-49FC-AB35-5106EE44CA33
2/10/12 11:56:03 AMLKDCHelper[276]Starting (uid=501)
2/10/12 11:56:27 AMkernelAFP_VFS afpfs_mount: /Volumes/maxsaverimutto, pid 271
2/10/12 12:06:03 PM/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[275]No valid tickets, timing out
2/10/12 12:08:10 PMkernelAFP_VFS afpfs_unmount: /Volumes/maxsaverimutto, flags 0, pid 300
2/10/12 12:08:10 PMkernelASP_TCP CancelOneRequest: cancelling slot 23 error 89 reqID 22208 flags 0x9 afpCmd 0xF0000002 so 0xec3051c

MacBook, Mac OS X (10.6.8)

Posted on Oct 2, 2012 7:14 AM

Reply
19 replies

Oct 2, 2012 8:33 AM in response to MaxAus

Kernel panics can be caused either by software or hardware faults. Faulty RAM is often a cause and can be very tricky to track down. It may sometimes be necessary to test the RAM using many loops, even overnight, before an error shows up. That you got one good report doesn't really mean that much. If the following doesn't resolve the problem, post back and I can give you instructions for a much more thorough check of your RAM.


If it's software, it might be a third-party program. This is a likely suspect:


com.displaylink.driver.DisplayLinkDriver


from whatever program that might be. You could try uninstalling that program or temporarily just unload that .kext (kernel extension) which will have the effect of disabling the program in order to see if the KPs stop.


For any of the possible culprit kernel extensions, it is not necessary to completely uninstall the parent program.


You can temporarily uninstall any .kext, which may be causing the problem, by doing the following: Open Terminal in Applications>Utilties and copy/paste


sudo kextunload


Important, leave a space after kextunload


Next, navigate to the /System/Library/ and select Extensions. Inside that folder, find the related .kext in question, which you should drag into the Terminal window. (After dragging it in, the file will stay where it belongs in its original location.) This will automatically fill the Terminal window with the name and path to the file.


This is an example only of what the full command will then look like; it will not necessarily be found on your computer.


sudo kextunload /System/Library/Extensions/PaceSupportFamily.kext/


Hit return. If you have never used the sudo prefix before, you will get a warning, which you can disregard. Then enter your admin password, which you won't see on the screen as you type it in and hit return. Wait for the $ sign prompt to reappear, which will indicate the extension has been unloaded. Then just close the window.


This will have the effect of disabling the program. If it fails to be the source of the problem, to reload/enable it, substitute kextload for kextunload, using the above procedure.


Other than that, have a look at this article on resolving kernel panics. Faulty RAM is a frequent cause.

http://www.thexlab.com/faqs/kernelpanics.html

Oct 2, 2012 9:18 AM in response to WZZZ

Hi WZZZ,


Thanks for the response. Much Appreciated.


I am using 2x4GB OWC Apple Certified RAM on this MacBook. See below for details;


Model Name: MacBook

Model Identifier: MacBook5,1

Processor Name: Intel Core 2 Duo

Processor Speed: 2.4 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache: 3 MB

Memory: 8 GB

Bus Speed: 1.07 GHz

Boot ROM Version: MB51.007D.B03

SMC Version (system): 1.32f8


When I run TechTool Pro 6.0.4, it tells me all is sweet and fine.

To be doubly sure I replaced the RAM with identical OWC 2x4GB. The KP's still continued. Is there any other

test I could do to check out my RAM Sticks.


At this stage, I have NOT tried unloading any kext files. As for the DisplayLinkDriver, this was an extra monitor

screen that I only installed a few days ago. [Extra monitor to view Console & Activity Monitor reports etc]

The KP's have been "On Going" for nearly three weeks now.


Even the local Apple store couldn't tell me what was causing the KP's.


All I can say is that my Macbook works like a dream for a couple days then it goes crazy by having 10 ~ 15

KP's a day without much indication.


After the last KP approx 12 hours ago, it complained saying my TM was currupt and wanted me back it up

immediately.

This is what I found in the console reports:

Hfs: Run Time Corruption detected on TM Backup. "fsck will be forced on next mount".

On the next reboot the Macbook could not even find the TM Back Drive.


Since then, I have backed it up using a NEW External HD.


Any other suggestions will be most appreciated.


Thanks

Oct 2, 2012 9:42 AM in response to MaxAus

Well it's not that .kext, since the KPs predate that. And not likely the RAM itself, since you've already replaced that. But it still might be the RAM slots which are at fault. For how long did the Apple Store have the computer? Did they just look at it at the front counter or did they take it in? Have you looked at the Xlab article?


To test the memory, get memtest and run it in single user mode, where it will test as much memory as possible, more than with the OS loaded.


You can get memtest + directions from the link below. However, ignore running it from Terminal. Instead, boot into SU Mode, Cmd-s at the startup chime. (Best to startup from a full shutdown.)


At the prompt, simply type /usr/bin/memtest all 3 -L (From this link It will be installed in /usr/bin/) Then hit return. This will run three loops of memtest and create a log in Console in Utilties.


If you want to run memtest longer, which may be advisable, since RAM errors can be very elusive, just remove the "all 3" which will give you /usr/bin/memtest -L and hit return. It will keep testing until you quit it. This is what you probably want to try.


If you want to quit the test, just hit control-c


When finished, you can just type in "reboot" and hit return.


http://osxdaily.com/2011/05/03/memtest-mac-ram-test/


Direct link for the download.


http://cdn.command-tab.com/2008/memtest_422.zip

Oct 2, 2012 10:37 AM in response to MaxAus

Hi again, WZZZ,


Thanks for the speedy response.


I am not sure, if I am unstanding / reading your answer above correctly??!!.


1) Is there a difference between testing "RAM" and Testing "RAM SLOTS".


I happy to do a "Memory Test" using Memtest. I will use the links provided and give it a try soon.


Right now, I am formatting my "OLD TM External HD to Mac OS Extended Journalled". The OLD corrupted Backup!. This is going to take me a few hours to complete as I selected the "Zero out" method!.


I don't want to do Memtest whilst formatting an External HD.!!


Once that is completed, I will give your suggestion a try with Memtest.


Personnally, I want to load this "MemTest" to the Maximum. Can you please advise on the following, Thanks.


1) Duration of Memtest in hours or number of recommended loops for a heavy loaded Max'ed OUT Testing!!.

2) Should I disconnect, ALL External HD's hanging off my MacBook including TM during the MemTest.

3) Currently, I have TWO external 27" Montors hanging off the Macbook. Do I keep them Connected or Disconnected for the Memtest.

4) This Macbook is hooked up via a ethernet cable to a network of Two other iMacs. Whats your recommendation here. During Memtest do I leave it hooked up to the Network or Not ??!!.


Please advise.


Sorry, I forgot to answer some your other questions:

The Mac Store ONLY had my Macbook for a few hours at the front counter. They did a standard Mac approved diagnostics test run. Sorry, I can't remember the name of the app they were using. The test only took about 10 minutes. At the store the MacBook ran like a champion. A few days later the KP's appeared a again. In brief the KP's appear to be "Intermittant". Hope this info helps.


Thanks.


I eagerly await your response.


Thank you.

:-)


Message was edited by: MaxAus

Oct 2, 2012 11:48 AM in response to MaxAus

I'd disconnect the externals and remove it from the Network and anything external, though not sure it will make any difference.


Duration of memtest: let it run for as long as you have the patience. At least a few hours. Some have left it running overnight. It was the only way it found a RAM problem. If you set it up to run without any loops, it will just keep running until you quit it.


Doesn't sound like the Apple Store went into anything very deeply. !0 minutes is trivial. I think what they did was worthless. The not very good Apple Hardware Test for end users won't finish in 10 minutes. In extended mode, it will take much, much longer, depending on how much RAM is installed.


Yes, the RAM can be OK but a memory fault might show up that's related to the slots, not the RAM.


Even though I realize it may be unlikely, I'd still test for KPs with the DisplayLink disabled for a while.

Oct 2, 2012 8:19 PM in response to WZZZ

Hi WZZZ,


Thanks for the good information above.


I now plan to do a overnight "Memtest" as suggested.


Please stay tuned. When available, I will update the outcome.


Thx.


[PS: The hardest thing with this MacBook is, that it is CURRENTLY running like a True Champ. (24 Hrs hours since last KP), Because the KP's are so sporadic, I am sure it will happen again in a couple of days!!!. Prove me wrong!!. This MacBook currently runs at about 70 ~ 80 Mb/sec on my local Net work, and it constantly achieves around 40 ~ 45 MB/sec on the Internet when connected to reputed organizations, such as Apple etc etc. In the past, this Macbook has run for TWO PLUS years without a single KP]

Oct 3, 2012 7:20 AM in response to MaxAus

Hi WZZZ,


Just a quick update on the progress I have made so far. [Currently I am up updating this thread, using another Mac on my Home Network!!]


Downloaded and ran "memtest" on my "MacBook" from the links you provided.


In Single User Mode, I did the following command line:

"/usr/bin/memtest -L" [without the quotes ofcourse!]

after a total of 7863 seconds [Approx 131 minutes], the system returned a message as follows:

"All tests passed!. Excution time 7863 seconds"


Without any intravention from me the above result was posted by "memtest". I was surprised that the system stopped automatically. With the above mentioned command I was expecting "memtest" to continue until I told it to STOP.


Anyway, I have entered the following command line hoping it will NOT STOP this time until I tell it to do so.

Here is my latest command line.


"/usr/bin/memtest all -L"


I intend running the test overnight.


Thanks.

Oct 3, 2012 8:24 AM in response to WZZZ

Thanks WZZZ,


Please stay tuned, I will update when more info is available at hand.


Now on a slightly different can you please advise on the following:

OK, Assuming "memtest' returns 100% success [I.E. ZERO Faults] on RAM / RAM SLOT testing what would you recommend next.


In the PAST 36 hours, this MacBook is going like a "Rocket". Fully shutdown, then restart and running in 27 Seconds. [Standard, WD 750GB 7200Rpm. NOT a SSD].


What is mind numbing in my situation is that this Macbook works Magnificently for few a days then KP's constantly sometimes approx 10 ~ 15 per day.


The KP logs just don't seem to indicate any "Fatal Errors" !!??.


Are there any Software tools that test for "Motherboard / Graphics Cards" etc that could be causing these KP's.


What are the other tricks, I can try besides buying another MacBook.


Please advice

Oct 3, 2012 8:45 AM in response to MaxAus

The only "end user" test is the AHT. Apple and Apple authorized will have a more sophisticated diagnostic. I may have mentioned this, but you could run a number of loops of the AHT. But it's really not known for picking up errors that well. It's pretty time consuming, mostly because of the RAM checking. I don't think there's anyway to skip that. I wish there were.


I'm reading that the ASD, or Apple Service Diagnostic, which is what the Apple Store will use, may be available for purchase, but that it's pretty expensive.


http://support.apple.com/kb/ht1509


You may have to bring it in to that Apple Store again and insist that they keep it and keep testing until they find what's wrong.

Oct 3, 2012 9:55 AM in response to WZZZ

Hi WZZZ,


Thanks for the above info.


Yep, "memtest" automatically stopped after another SINGLE sequence.


Again 100% Pass rate. NIL Faults.


This time I have done the following command line;

"/usr/bin/memtest all 6 -L"


It is now telling me that it is on sequence "1 of 6" [On previous attempts, it always said sequence 1of 1]. So it appears that it's going to do 6 complete cycles on this attempt. Both my previous tests took approx TWO hours to complete. So for 6 cycles approx 12 hours estimated.


As for the AHT, that sounds like a pointsless test as I am right now flogging the RAM test to death with a total of 8 cycles approx 16 Hours.


Upon completion of the remaining 6 memtest cycles, if it returns a 100% Pass Rate, then it's a given conclusion that the KP's are NOT happening due to Faulty RAM / RAM SLOTS.


By any chance do you feel that TM was causing the previously mentioned KP's. "FSCK" will be forced on next mount.


File corruptions / Permissions corruptions etc etc. These are the ONLY errors I have ever seen on the console panel.


Additionally, I feel that the Files were getting worse after each KP. Obviously when a KP occurs, you are forced to power off the machine effectively causing file corruptions etc etc. [Apple claims HFS is hard to corrupt, I strongly disagree that claim specially on UNCONTROLLED "FORCED POWER SHUTDOWNS].


By the way when a KP occurs, are there any special tricks for a "Controlled shut down" rather than the Deadly Power Button Option.


Please advise.


Thanks



Thanks.


Message was edited by: MaxAus

Oct 3, 2012 10:02 AM in response to MaxAus

By any chance do you feel that TM was causing the previously mentioned KP's. "FSCK" will be forced on next mount.

Could be but here I don't know enough to answer. Searching "Time Machine + Kernel Panic" gives me a number of hits. You might want to read those. I don't use TM and don't have any hands on experience with it. Why don't you at least verify that volume in Disk Utility?


The AHT may be pointless for checking RAM, but it might turn up something else. As I said, it's really too bad the RAM part of the test can't be skipped. But the AHT just isn't a very good tool to begin with. It did once find a graphics error on my old iMac G5, but that was really blatant. For something random like this, it will be very hit or miss.

Oct 3, 2012 11:01 AM in response to WZZZ

Hi WZZZ,


Thanks for the above info.


I am not quite sure what you mean on the following sentence.

Why don't you at least verify that volume in Disk Utility?


Right NOW, I have put away that OLD TM Backup on the shelf.


After the LAST KP 36 Hours ago, I backed up My MacBook with a Brand NEW External HD for TM Use. This NEW TM backup seems to be OK so far!!.


When you say verify the OLD TM Backup in Disk utility, what do you exactly mean here??!!.


1) Do you mean try to fix up the OLD corrupt files / permissions using Disk Repair or First aid In the Disk Utility.app


All the files on my Macbook seem to be fine after those numerous KP's. It's the OLD TM Backup that kept getting corrupt after those uncontrolled Power shut downs. I am NOT sure if the OLD TM Backup External HD was causing the MacBook to KP.


Hopefully with the NEWLY backed up TM things might change and I may get back to normality like the good old days.


By the way the OLD TM External HD was over TWO years old and may have been on it's last legs, causing the file corruptions during the hourly backups. [This is just another guess of mine for KP's that have occured over past three weeks].


I will now do some reading up on TM corruption in the forum.


As a general rule when Mac KP's our 1st culprit is RAM. So that's why I wanted to be sure to be sure in eliminating the RAM issue. The TM issue is ONLY another thought of mine as the ONLY CONSOLE Error messages, I ever saw said TM Corruption etc etc.


Thanks


Oct 4, 2012 2:12 AM in response to WZZZ

Hi WZZZ,


An update on my progress to date.

I have now completed a total of 8 Memtest loops / cycles.

All 8 cycles confirmed 100% Pass Rate.

Each complete cycle took around 2hours 15Minutes to complete.Total test time was approx 18 hours.


The TEST is very conclusive that there is NO FAULTY RAM on my MacBook.


See copy of report below.


Start Of Memtest Report

Memtest version 4.22 (64-bit)

Copyright (C) 2004

Copyright (C) 2004 - 2008 (Macintosh port)

Licensed under the GNU General Public License version 2 only


Log file written to //memtest.log


Mac OS X 10.6.8 (10K549) running in single user mode

Memory Page Size: 4096

System has 2 Intel core(s) with SSE

Requested memory: 7648MB (8020426752 bytes)

Available memory: 7648MB (8020426752 bytes)

NOTE: Memory request is too large, reducing to acceptable value...

Allocated memory: 7434MB (7795854784 bytes) at local address 0x0000000101000000

Attempting memory lock... ERROR: Memory lock failed - reason unknown.


WARNING: Testing with unlocked memory may be slower and less reliable


Splitting allocated memory into 2 comparison buffers...

Buffer A: 3717MB (3897927392 bytes) starts at local address 0x0000000101000000

Buffer B: 3717MB (3897927392 bytes) starts at local address 0x00000001e955a6e0


Running 6 test sequences... (CTRL-C to quit)


Test sequence 1 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


Test sequence 2 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


Test sequence 3 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


Test sequence 4 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


Test sequence 5 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


Test sequence 6 of 6:


Running tests on entire 7434MB region...

Stuck Address : ok

Linear PRN : ok

Running comparison tests using 3717MB buffers...

Random Value : ok

Compare XOR : ok

Compare SUB : ok

Compare MUL : ok

Compare DIV : ok

Compare OR : ok

Compare AND : ok

Sequential Increment: ok

Solid Bits : ok

Block Sequential : ok

Checkerboard : ok

Bit Spread : ok

Bit Flip : ok

Walking Ones : ok

Walking Zeroes : ok


All tests passed! Execution time: 47271 seconds.


End Of Memtest Report


The MacBook now appears to be running OK again.

BUT, as I have previously said it runs well for a few days then KP's on me miserably. 10 ~ 15 KP's per day.


Please stay tuned and I will update my progress in due course!!.


WZZZ, If know of any other Tricks OR How to READ KP logs please let me know.


Thanks.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Kernel Panics Frequently

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.