Can anyone debug recurrent start-up error from this?

Question

Interval Since Last Panic Report:  225960 secPanics Since Last Report:          2Anonymous UUID:                    0683A925-5462-6E6E-3637-48BD8C72ABFFThu Jan 31 11:13:02 2013panic(cpu 0 caller 0xffffff801e0b7bd5): Kernel trap at 0xffffff801e02e906, type 12&#x3D;stack bounds, registers:CR0: 0x000000008001003b, CR2: 0xffffff8090a3e000, CR3: 0x0000000020ca2000, CR4: 0x0000000000000660RAX: 0xbb28671817b400ee, RBX: 0xffffff8029502000, RCX: 0x0000000009000000, RDX: 0xffffff808a9e5078RSP: 0xffffff809620be40, RBP: 0x01ffff809620beb0, RSI: 0xffffff808a9e5068, RDI: 0x0000000000000000R8:  0xffffff801e6bec60, R9:  0xffffffffffffffff, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80R12: 0x0000000000000001, R13: 0x0000000000000000, R14: 0xffffff80295cc550, R15: 0x0000000000000000RFL: 0x0000000000010046, RIP: 0xffffff801e02e906, CS:  0x0000000000000008, SS:  0x0000000000000000Fault CR2: 0xffffff8090a3e000, Error code: 0x0000000000000000, Fault CPU: 0x0Backtrace (CPU 0), Frame : Return Address0xffffff809620bae0 : 0xffffff801e01d626 0xffffff809620bb50 : 0xffffff801e0b7bd5 0xffffff809620bd20 : 0xffffff801e0ce4ed 0xffffff809620bd40 : 0xffffff801e02e906 No mapping exists for frame pointerBacktrace terminated-invalid frame pointer 0x1ffff809620beb0BSD process name corresponding to current thread: kernel_taskMac OS version:Not yet setKernel version:Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333Kernel slide:     0x000000001de00000Kernel text base: 0xffffff801e000000System model name: MacBookPro5,3 (Mac-F22587C8)System uptime in nanoseconds: 2126671824last loaded kext at 259589052: com.apple.driver.XsanFilter          404 (addr 0xffffff7f9fc95000, size 20480)loaded kexts:com.apple.driver.XsanFilter          404com.apple.iokit.IOAHCIBlockStorage          2.2.2com.apple.driver.AppleFWOHCI          4.9.6com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0com.apple.driver.AppleUSBHub          5.2.5com.apple.driver.AppleSmartBatteryManager          161.0.0com.apple.driver.AirPort.Brcm4331          602.15.22com.apple.nvenet          2.0.19com.apple.driver.AppleEFINVRAM          1.6.1com.apple.driver.AppleAHCIPort          2.4.1com.apple.driver.AppleUSBEHCI          5.4.0com.apple.driver.AppleUSBOHCI          5.2.5com.apple.driver.AppleRTC          1.5com.apple.driver.AppleHPET          1.7com.apple.driver.AppleACPIButtons          1.6com.apple.driver.AppleSMBIOS          1.9com.apple.driver.AppleACPIEC          1.6com.apple.driver.AppleAPIC          1.6com.apple.nke.applicationfirewall          4.0.39com.apple.security.quarantine          2com.apple.driver.AppleIntelCPUPowerManagement          196.0.0com.apple.iokit.IOAHCISerialATAPI          2.5.0com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1com.apple.iokit.IOFireWireFamily          4.5.5com.apple.iokit.IOUSBUserClient          5.2.5com.apple.iokit.IO80211Family          500.15com.apple.iokit.IONetworkingFamily          3.0com.apple.iokit.IOAHCIFamily          2.2.1com.apple.iokit.IOUSBFamily          5.4.0com.apple.driver.NVSMU          2.2.9com.apple.driver.AppleEFIRuntime          1.6.1com.apple.iokit.IOHIDFamily          1.8.0com.apple.iokit.IOSMBusFamily          1.1com.apple.security.sandbox          220com.apple.kext.AppleMatch          1.0.0d1com.apple.security.TMSafetyNet          7com.apple.driver.DiskImages          344com.apple.iokit.IOStorageFamily          1.8com.apple.driver.AppleKeyStore          28.21com.apple.driver.AppleACPIPlatform          1.6com.apple.iokit.IOPCIFamily          2.7.2com.apple.iokit.IOACPIFamily          1.4com.apple.kec.corecrypto          1.0Model: MacBookPro5,3, BootROM MBP53.00AC.B03, 2 processors, Intel Core 2 Duo, 2.8 GHz, 4 GB, SMC 1.48f2Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MBGraphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MBMemory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.81.22)Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial portsNetwork Service: AirPort, AirPort, en1Serial ATA Device: ST9320423ASG, 320.07 GBSerial ATA Device: HL-DT-ST DVDRW  GS23NUSB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26500000 / 2USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x04600000 / 3USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000 / 2USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06110000 / 3

Kappy · Answer

Why are you running Xsan software? If you boot into Safe Mode and operate, do you still have recurring panics?

Porsche996420 · Answer

Thanks for quick response.1.  Xsan:  This is nothing that I consciously loaded.  The MacBook in question does access an iMac and a couple of external drives that are attached to my AirPort Extreme.  Is it feasible that it was installed when I built the network?2.  I will try booting in Safe Mode, but I don&#x27;t see a quick answer there as the problem occurs sporadically.  Perhaps 5% of boots (&amp; only on boot-up).  I need to research the process for starting without loading specific pieces.3.  Do you see other suspicious software that I might look at?

Linc Davis · Answer

That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:A damaged OS X installationA fault in a peripheral device, if anyCorrupt non-volatile memory (NVRAM)An internal hardware faultAn obscure bug in OS XYou can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn&#x27;t solved by reinstalling in place, without erasing.Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it as directed in this support article.If you&#x27;ve recently upgraded the memory, reinstall the original memory and see whether there&#x27;s any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can&#x27;t be depended on. Run the extended version of the test.In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.Otherwise, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn&#x27;t much point in doing this unless you can reproduce the panic, or if you can&#x27;t, it happens often enough that it&#x27;s likely to be repeated at the store. Otherwise you may be told that nothing is wrong.Print the first page of the panic report and bring it with you.Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.Keeping your confidential data secure during hardware repair*An SSD doesn&#x27;t need to be zeroed.

Kappy · Answer

Try reinstalling OS X.Reinstalling Lion/Mountain Lion Without Erasing the DriveBoot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.&#x27;s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.