Corrupt NVRAM - Possibly????

Hi,
I have a really funny problem with my iMac 21" Intel Core 2 Duo.
It boots really slowly and when it reaches that login screen it has a kind of blue hue faded look. The keyboard and mouse clicks are unresponsive but the mouse cursor moves. I can ARD to the machine and the remote keyboard and mouse work fine. However the machine is slow.
I have tried to rest the NVRAM but I have the firmware password enabled so the keyboard shortcut is not working.
NVRAM terminal command errors with the command not supported on this system. This is odd is it works fine on the other machines I have which are identical models.
I have booted to the installation disc and used the firmware password utility but it doesnt remove the password. I have tried altering the RAM but again it doesnt remove the password.
I have booted to a known good OS via target disc mode and all problems still exist. I have tested the keyboard and mouse and they are OK.
I'm sure this is just an NVRAM prob but is there another way to reset it.
Thanks
Keith
iMac 21" (Silva)
Intel Core 2 Duo
10.6.8

Solved.
I just started taking out RAM and replacing it until it eventually removed the EFI password (had to try both modules a few times each before it work).
Zapped the PRAM and hey presto all is working sweet.
Keith

Similar Messages

  • MB 7,1 Mid2010 corrupt nvram

    Hi,
    i have a bunch of MB7,1 mid 2010 Macbook with problems
    Slow start, integrated keyboard and touchpad not responding until 10 minutes after boot.
    from network access in system.log appears "cfgethostuuidstring unable to determine uuid for host. error 35"
    Seems that reseting nvram and smc should recover them but ...
    They have efi password, but i'm unable to change/clean since nvram command said "nvram not working on this platform".
    I can't reset NVRAM using keyboard since is password protected.
    Boot from install media and using Firmware password util is not working either.
    Any magical recipe i can try before sending them to tech support.
    Thanks

    I lost 4 hours of work.
    You can help make sure that never happens again.
    http://forums.adobe.com/thread/1369232?tstart=0

  • ITunes download error -100000/corrupted file possible solution

    I just would like to acknowledge Kate G back in an older discussion for this simple solution that helped others and I. May not work for everyone, but could for some.
    If you have Kaspersky as your primary internet security, then disable the protection under "settings" then in "general settings" temporarily until the download(s) are finished. Also try disabling the firewall just in case. Then re enable everything is once they are finished.
    I would assume this could work for other internet security software like Norton or whichever you have.
    Hopefully this helps, and if not, then at least it was a try. Doesn't hurt to try.

    I'd report the problem to the iTunes Store. 
    Log in to the Store. Click on "Account" in your Quick Links. When you're in your Account information screen, go down to Purchase History and click "See all".
    Find the item that is not downloading properly. If you can't see "Report a Problem" next to the item, click the "Report a problem" button. Now click the "Report a Problem" link next to the item.

  • External hard drive corruption issues

    Hey folks. Really not sure what the best place would be for my question, but I'll try here.
    I have a 4 year old LaCie external HD with a 160GB capacity. It stores my iPhoto and iTunes libraries for my iBook, along with a few other bits and pieces.
    About a year ago, I noticed some of my files were corrupted and couldn't be played. Whenever I tried to open one of those files, the drive would start knocking and whatever program was trying to access the file would need to be Force Quit. Hoping to solve the issue, I moved the data,(or course, getting stuck on corrupted files along the way) erased and reformatted the drive and moved the data back. Unfortunately, that didn't solve the problem.
    I have the data backed up on another, newer external drive, but I'm wondering if there's a way to isolate the bad sectors in the old drive so they can't be written to anymore? Should I use Disk Utility and repair the disk?
    I know the drive's old and could fail at any time, but I'd like to keep using it as long as possible. Also, when it does finally fail, could I just purchase another hard drive and place it in the enclosure? I suppose I should also note that the FireWire 400 ports don't work on the enclosure. I'm sure it's not a defect, as I accidentally dropped the drive shortly after I'd purchased it. That fall is probably the cause of the corruptions as well =/
    The USB port works fine and I haven't been able to test the FireWire 800.
    Thanks for any advice y'all have!
    ~Lyssa

    Your drive sounds very sick. I am not sure how likely it is but I would be concerned about your OS becoming seriously corrupted and possibly unbootable as a result of continuing to use this bad external drive.
    It would be better if you could test it connected to a non-critical computer.
    Do you know the drive specification? - not the make of the box.
    Many drives self-repair and also communicate likely future difficulties to the OS but eventually you come to the end of this process.
    I am not sure if disk utilities any longer map out bad sectors. Years ago I used a mounting screw that was too long and damaged the magnetic surface. In those days you could manually map out the bad sectors. I then put partitions each side of the mapped out sectors and continued to use the drive for many years.
    More recently I had a drive with an intermittent power connection. However even after repairing this and reformatting the drive was never very reliable.
    Good drives are relatively inexpensive. You could try a new drive in your box. I always advise buying server quality drives normally identified by a 5 year guarantee. I prefer Western Digital but Seagate also make reliable drives.

  • 4s backs up ok, but when I try to recover get corruption error

    When I try to recover my phone from a backup get corruption error everytime.  Yet I can backup just fine with no errors.  Then on that same backup I just created I try to restore it and get an error.  I tried backing up another iphone, and tried recovering from that backup file and get the same error.  Whats making all my backups get corrupted?  I can sync just fine with no errors.  But can't recover ever from any of my backups, not even one that I create right now.
    Using a PC.
    Thanks
    DJ

    "So you believe the phone is corrupted ...?"  Well, not exactly.  I believe you had been carrying around some corrupted data, possibly associated with a misbehaving app or some such thing.
    "... I'm afraid that if all my backups are corrupted ...".  Yes, this is not absolutely guaranteed to work.  But I think there is a high likelihood it will do an orderly transition of only the good data from the backup to your device.  No guarantee, but for what it's worth, if I were in your situation, I would try this.

  • Kernel panic - hard drive or corrupt journal system?

    Hi,
    My powerbook G4 shut down today with a kernel panic and now won't boot up (giving a kernel panic error after reaching the gray screen). The computer has been working fine, though the battery has run down, with the exception of not shutting down properly (I would have to power off manually). I tried various things to fix this (repair permissions, check hard drive, checking logs, etc.), but all those checked out and I could never get it figured out. I have been leaving the computer running because of this and it has been working fine. It is a stock G4 with no peripherals, except for a 1 GB RAM upgrade. The RAM was installed two years ago and tested strenuously with memtest with no issues.
    I did have my hard drive near full, as I didn't realize that this could case severe issues. It's probably too full to do a clean Archive and Install. My fault.
    I have reset my PMU/PRAM, but the computer won't boot up in safe mode or single-user mode. I get the following message at the end of single-user mode:
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007: root:xnu-792.24.17~1/RELEASE_PPC
    panic: We are hanging here ...
    Unfortunately, I do not have my backup disks with me right now, as I recently moved (I will have them in a couple weeks).
    There's some data on the computer it would be nice to pull off, but not absolutely essential. So my question is: Does this sound like a hard drive problem or a journal system/file system problem or something else? I hear no strange noises from the drive (the fan is a little noisy, though). What can I do at this point while I wait for my discs to arrive from across country?
    If this is a file problem, I have heard these are difficult to fix or even deal with in terms of data recovery, since the disk won't mount even in firewire target mode. Should I invest in a firewire external drive in order to create a bootable second drive? Purchase DiskWarrior? Create a bootable Linux CD? Any help would be appreciated!

    darksurtur:
    If you have the original HDD with which the computer was bought you likely have a failed HDD and should have it replaced with a newer, faster and large capacity HDD. The average life of an internal HDD is 3 to 5 years, and although it may not suddenly stop functioning after that performance gradually decreases until the drive fails completely.
    A too full drive can cause serious directory corruption which can in turn lead to data corruption and possible loss, and eventually a crash. You should maintain a minimum of 15% to total disk capacity (5 GB minimum on HDDs of 40 GB or less) as contiguous free space to allow for swap files and directory expansion.
    You should always maintain a current backup of everything you do not wish to lose as even a new HDD can fail suddenly. Using an external firewire drive and making a bootable clone using a utility like SuperDuper or Carbon Copy Cloner is an excellent way to accomplish this. Dr. Smoke's FAQ Backup and Recovery has excellent tips on backup strategies.
    Please do post back if you have further questions or comments.
    cornelius

  • Oracle 10g to 9i possible?

    hello,
    Is it possible to migrate 10g database to 9i database?
    let me explain the situation here:-
    I had 9i database cold backup which upgraded to 10g.
    now when I open 10g database it gives SYSAUX01.DBF file corruption.
    I brought it to offline and opened the database. but still I am not able to do anything (whenever I go import or export, the system gives
    ORA-00376: file 13 cannot be read at this time
    ORA-01110: data file 13: 'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SYSAUX01.DBF' )
    I have oracle 9i database running on my test lab, is there any way to go back to 9i?
    how to fix this file corruption in 10g
    awaiting your guidance...
    thanks

    now when I open 10g database it gives SYSAUX01.DBF
    file corruption.
    I brought it to offline and opened the database. but
    still I am not able to do anything (whenever I go
    import or export, the system gives
    ORA-00376: file 13 cannot be read at this time
    ORA-01110: data file 13:
    'C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SYSAUX01.DBF'
    )What was the error you received when you brought the database up with the SYSAUX tablesapce online? That corruption, if possible, needs to be fixed first as the SYSAUX tablesapce is needed for operation in 10g.

  • Run DB Verify and has some files corrupt. Need help

    In our system, after we run the DB Verify and two data files have the following message:
    Page 254582 is marked media corrupt
    Page 254583 is marked software corrupt
    Page 254584 is marked software corrupt
    Page 254585 is marked software corrupt
    Page 254586 is marked software corrupt
    Page 254587 is marked software corrupt
    A few questions:
    What is the difference between the 'media corrupt'and 'software corrupt'?
    How to verify if the data is really corrupted or not?
    If is corrupted, is possible to repair it?
    How to recover from this?
    In general, what are the procedures after finding files are currupted?
    Thanks for advises.

    While I think that Mylenium and Dec9 have solved your problem with installation, here is a CHECKLIST on installing most Adobe programs, that might also help.
    Good luck,
    Hunt

  • MSFC boot NVRAM error

    Hi, after reloading a Catalyst 6009, MSFC2 boots in ROMmon. I've tried to boot the image from rommon but i receive the following message:
    "Environment checksum in NVRAM failed.
    Bus Error exception"
    What does it mean?
    What can i do?
    does it look a hardware or software error?
    Thanks

    Hello,
    This looks like a corrupted nvram,  I'm afraid there is little you can do from rommon. In your case it seems that it can't even read the environment variable and the device won't boot without it. I agree that usually this is highlighting a bad hardware, see TAC Case collection (unfortunately you won't have access to IOS CLI as suggested there):
    https://www.ciscotaccc.com/kaidara-advisor/core/showcase?case=K10149421

  • Recovery disks process corrupted BIOS

    Hp laptop 2000-350US. Hard disk failed. Ordered new disk and recovery CDs through HP site. Recovery started, last message I remember seeing is "hard disk will be formattedd blah blah". Next time I looked the screen is black and caps lock is blinking. Found a couple tips on what the blinking means, 2 blinks is BIOS corruption and possible solution is to reset it. Tried the hard reset trick but no good. Was going to try the next step in trying to locate jumpers or cmos battery. I have zero interest in sending this back to HP for more than I paid for new. Has anybody located the top secret jumpers or battery and maybe save me a few screws and cracked plastic to get to?

    Don't bother wasting the $14 on 'recover' disks as they don't work for beans. It is sad to see 40 years of time has not helped software at all. This package could not even handle a different size drive making it next to worthless. I found an .iso of Win7 and a Microsoft tool that let me put it on a USB stick then recovered using that. Nice thing is all that HP bloatware is gone. Just install specific drivers that Windows does not have.

  • What is WRONG with my MAC G5?

    Hi all,
    I've posted several times in various forums about a number of problems I've been having that remain unresolved, and would like to appeal once more for help. I have a 6 year old 2GHz PowerPC G5 (2004) with 4GB of RAM, running FCS 6.0.6 and OS 10.5.8. I must reiterate that, despite the computer's age, it was working just fine until a kernel panic in December that has since left the computer feeling sluggish. I've performed a clean install (twice) of both the OS and FCS. I've bought new RAM and reseated in every possible way. I bought a new external harddrive (used to store my media) in case that was the culprit. I even took the computer and display into an Apple Store where they tested it for 2 days finding "nothing wrong with it". Yet even they couldn't get the "High" quality setting back in FCP. It defaults to medium now (unlike before) - which is my biggest concern. The computer's internal drive has 30% free space. The external more than 15%. And naturally, I've repaired permissions and trashed pref files, etc., with no results. Oh! And I've run the Hardware Diagnostics disk, three times, and everything keeps passing. I also just cloned the internal Maxtor drive onto an external Lacie drive and booted up from that - with no obvious improvement. Trying to eliminate the hard drive as a factor.
    One more symptom -- perhaps related, perhaps not -- is that I can no longer put the computer to sleep without it crashing, followed by jet engine fans coming on. This happens every single time. Unfortunately it wasn't happening (as frequently) when I took the computer to the Apple geniuses.
    And last week, when I turned the computer on, the screen remained black. The LED flashed in what I think was a series of three fast flashes. I rebooted and everything has been fine since (with the display).
    I think I've found some suspicious items in the console logs. But I don't have a clue how to accurately read them or fix the problem. Can someone please help me?
    The windowserver_last.log is full of the following:
    May 21 10:57:47 52 kCGErrorIllegalArgument: CGXGetWindowWorkspace: invalid window id: a2
    May 21 10:58:33 52 kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Final Cut Pro" for over 1 second. Server has re-enabled them.
    May 21 10:59:42 52 kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Final Cut Pro" for over 1 second. Server has re-enabled them.
    May 21 11:03:52 52 kCGErrorFailure: CGXDisableUpdate: UI updates were forcibly disabled by application "Final Cut Pro" for over 1 second. Server has re-enabled them.
    Then there's these ones that keep popping up in the console or system logs:
    24/05/10 1:47:43 PM /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro115 _RemoveTimeTask(), the current time manager task 0x416c943c being removed is also currently executing its tmAddr routine, so unexpected things may result ( Radar #4555679 ).
    24/05/10 1:48:39 PM Final Cut Pro115 startDelayedNoDataDetection
    (the startdelayed... is probably due to dropped frames during capture with stop/start detection on)
    These ones are less frequent, but still showing up:
    22/05/10 6:30:17 PM Dock104 QL ERROR Generator database update takes too long... we will use what we currently have
    May 17 16:22:07 macdaddys-power-mac-g5 Finder100: QL ERROR Generator database update takes too long... we will use what we currently have
    May 18 08:56:18 macdaddys-power-mac-g5 Finder96: QL ERROR Generator database update takes too long... we will use what we currently have
    May 18 13:03:07 macdaddys-power-mac-g5 Finder101: QL ERROR Generator database update takes too long... we will use what we currently have
    May 19 11:47:56 macdaddys-power-mac-g5 Finder112: QL ERROR Generator database update takes too long... we will use what we currently have
    May 19 14:31:15 macdaddys-power-mac-g5 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder118: StatusMonitor::volumesChangedCallBack returned -47
    May 19 15:23:14 macdaddys-power-mac-g5 Finder102: QL ERROR Generator database update takes too long... we will use what we currently have
    May 21 09:54:32 macdaddys-power-mac-g5 Finder102: QL ERROR Generator database update takes too long... we will use what we currently have
    May 21 14:28:45 macdaddys-power-mac-g5 Finder111: QL ERROR Generator database update takes too long... we will use what we currently have
    22/05/10 6:30:31 PM quicklookd123 QL ERROR 'Creating thumbnail' timed out for ''
    23/05/10 2:27:25 PM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 3 seconds
    23/05/10 2:27:28 PM com.apple.quicklook109 invalid #-escape sequence.
    23/05/10 2:27:28 PM com.apple.quicklook109 encountered unexpected object type: 7.
    23/05/10 2:27:29 PM com.apple.launchd78 (0x0-0xd00d.com.apple.AddressBook.abd112) Check-in of Mach service failed. PID 112 is not privileged: com.apple.AddressBook.abd
    23/05/10 2:27:29 PM com.apple.quicklook109 xref table size mismatch: calculated 462; /Size = 463.
    ===============
    If I had the money, of course I'd buy another computer. But I don't. And deep inside, I still believe there's a fix. Am I right or wrong???
    Chris
    P.S.
    I don't have a clue how to read Power Fractal (suggested to someone else in another post), but here's my score:
    Elapsed time: 1.6 seconds
    Achieving 6261.1 Megaflops
    Color Speed: 10
    Maximum Count: 4096
    One more thing I gleaned from another post are similar istat readings that seemed unusual to that person. Backside fans: 51rpm. ???

    First thing I would do is make your post clear(-er) (I find it easier to break things down into one item per paragraph or into lists); and what HARDWARE tests and steps you have tried - that we tend to repeat over and over with system failures.
    I've posted several times in various forums about a number of problems I've been having that remain unresolved,
    *I have a 6 year old 2GHz PowerPC G5 (2004) with 4GB of RAM, running FCS 6.0.6 and OS 10.5.8.*
    I must reiterate that, despite the computer's age...
    +*it was working just fine until a kernel panic in December that has since left the computer feeling sluggish.*+
    +I've performed a clean install (twice) of both the OS and FCS.+
    +I've bought new RAM and reseated in every possible way.+
    +I bought a new external hard drive (used to store my media) in case that was the culprit.+
    +I even took the computer and display into an Apple Store where they tested it for 2 days finding "nothing wrong with it". Yet even they couldn't get the "High" quality setting back in FCP. It defaults to medium now (unlike before) - which is my biggest concern.+
    +The computer's internal drive has 30% free space.+
    +The external more than 15%.+ 15% is still low and can be highly fragmented, but not germaine to hardware problems.
    +I've run the Hardware Diagnostics disk, three times, and everything keeps passing.+
    +I also just cloned the internal Maxtor drive onto an external Lacie drive and booted up from that - with no obvious improvement.+
    +Trying to eliminate the hard drive as a factor.+
    I'd even say LaCie might just be one more layer of possible problems.
    There are FAQs on kernel panics which:
    A/ Been there, done that?
    B/ Do they need to be listed (again)? revisited?
    C/ panics are hardware almost always, RAM, controllers, sometimes drivers, even corrupt NVRAM
    Does it boot into Open Firmware?
    If yes, redo reset-nvram
    If no, DOA
    G5 Logicboards:
    http://www.dvwarehouse.com/Power-Mac-G5-Logic-Boards-c-24553701074.html
    Power Mac G5 PowerMac G5 Dual 2.0Ghz M9032LL/A, A1047 1969C
    NOTE: Power Mac G5 Thermal Calibration Service It is vital for all Power Mac G5 to run thermal calibration after fitting a new logic board or processors, without it, Temperature Control will not be able to detect the system temperture correctly. As a result, it could cause the cooling fans to run at high speed, eventually damgaging the logic board or processors.
    Lastly, I would never run a Mac w/o UPS, which can lengthen life and protect equipment and even the PSU.
    And for $1500 the iMac Apple Store Specials can be a good fast alternative to G5.
    http://store.apple.com/us/browse/home/specialdeals/mac/imac

  • Macbook Pro 2012 Kernel Panic

    During graphic intensive applications(gaming, netflix, etc), my macbook pro will randomly hard freeze(sometimes it's after a few minutes and other times several hours). I can't access any other applications during this, and I can't force quit using the shortcut. The only thing I can do is press the power button and turn it off. Somtimes I can move my mouse, and sometimes I can't. When I can, it is the colorful pinwheel.
    I disabled automatic graphics switching, and that did not help. I then ran a hardware test, and it was hanging on the memory portion of the test. I took my mac to the apple store two weeks ago with this problem, and they thought it was a memory problem and replaced my memory (sidenote: I had taken my apple back for repairs in last October because of kernel panics. They replaced my hardrive, logicboard, and my memory, but they only put back in 4GB when I originally upgraded to 8GB).  They upgraded my memory to the 8GB again with the replacement, and it seemed fine. I was using it without problems, but now my mac is having problems again.
    Random freezes where I have to forcibly shut off my mac happen a couple times a day, and now I'm starting to get kernel panics. The kernel panics both involved the NVDAResman and Geforce in the extension backtrace. (I've had two kernel panics the past two days). It's also a lot slower starting up, and sometimes it freezes during the startup with the mac icon and the gray backdrop or the login screen forcing me to restart.
    I ran the hardware test again out of curiosity, and it's still hanging at the memory portion of the test. I'm a little at a loss as to what to do.
    My latest panic report:
    Thu Jul 18 13:28:49 2013
    panic(cpu 4 caller 0xffffff7f8e6e2f1a): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0x0fd510de 0x00100406 0xc0000000, BAR0 0x103000000 0xffffff80fe005000 0x0e7150a2, D0, P2/3\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
    Backtrace (CPU 4), Frame : Return Address
    0xffffff80fdb8aa90 : 0xffffff800c41d626
    0xffffff80fdb8ab00 : 0xffffff7f8e6e2f1a
    0xffffff80fdb8abd0 : 0xffffff7f8cb9cf1e
    0xffffff80fdb8ac90 : 0xffffff7f8cc7112d
    0xffffff80fdb8acd0 : 0xffffff7f8cc7118e
    0xffffff80fdb8ad40 : 0xffffff7f8cf94146
    0xffffff80fdb8adb0 : 0xffffff7f8cc99a75
    0xffffff80fdb8add0 : 0xffffff7f8cba3d50
    0xffffff80fdb8ae80 : 0xffffff7f8cba17d0
    0xffffff80fdb8b080 : 0xffffff7f8cba310a
    0xffffff80fdb8b150 : 0xffffff7f8dc174a8
    0xffffff80fdb8b290 : 0xffffff7f8dbd585f
    0xffffff80fdb8bc70 : 0xffffff7f8dbb449c
    0xffffff80fdb8bde0 : 0xffffff800c8655cd
    0xffffff80fdb8be40 : 0xffffff800c4988b4
    0xffffff80fdb8be80 : 0xffffff800c420b3d
    0xffffff80fdb8beb0 : 0xffffff800c410448
    0xffffff80fdb8bf00 : 0xffffff800c41961b
    0xffffff80fdb8bf70 : 0xffffff800c4a6536
    0xffffff80fdb8bfb0 : 0xffffff800c4ce9e3
          Kernel Extensions in backtrace:
             com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f8cb 3b000->0xffffff7f8cde0fff
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8caa5000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8cb27000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8cae4000
             com.apple.GeForce(8.1.2)[7EC545A4-4B57-32F1-8DC3-C31023AFBDCB]@0xffffff7f8dbb10 00->0xffffff7f8dc7efff
                dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f8cb 3b000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8cb27000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8caa5000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8cae4000
             com.apple.driver.AppleMuxControl(3.4.5)[49FEF732-D7A3-327B-A7AA-6AC5A6E3DCFF]@0 xffffff7f8e6d5000->0xffffff7f8e6e7fff
                dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[1D0BB11E-7D71-34CF-ACC3-57DF01CADA 08]@0xffffff7f8e6d0000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8caa5000
                dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7f8e6bc000
                dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f8c9e8000
                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f8cb27000
                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f8cae4000
             com.apple.nvidia.gk100hal(8.1.2)[8007AA34-6789-37E9-B069-A414AA26C6B6]@0xffffff 7f8cdec000->0xffffff7f8d11dfff
                dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f8cb 3b000
                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8caa5000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    12E55
    Kernel version:
    Darwin Kernel Version 12.4.0: Wed May  1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
    Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
    Kernel slide:     0x000000000c200000
    Kernel text base: 0xffffff800c400000
    System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)
    System uptime in nanoseconds: 44968965432
    last loaded kext at 23342058276: com.apple.driver.AudioAUUC    1.60 (addr 0xffffff7f8de68000, size 32768)
    loaded kexts:
    com.driver.LogJoystick    2.0
    com.logitech.driver.LogiGamingMouseFilter    1
    com.apple.driver.AudioAUUC    1.60
    com.apple.driver.AppleHWSensor    1.9.5d0
    com.apple.driver.AGPM    100.12.87
    com.apple.driver.ApplePlatformEnabler    2.0.6d1
    com.apple.driver.X86PlatformShim    1.0.0
    com.apple.driver.AppleMikeyHIDDriver    122
    com.apple.iokit.IOUserEthernet    1.0.0d1
    com.apple.filesystems.autofs    3.0
    com.apple.driver.AppleHDAHardwareConfigDriver    2.3.7fc4
    com.apple.iokit.IOBluetoothSerialManager    4.1.4f2
    com.apple.iokit.IOBluetoothUSBDFU    4.1.4f2
    com.apple.driver.AppleHDA    2.3.7fc4
    com.apple.Dont_Steal_Mac_OS_X    7.0.0
    com.apple.driver.AppleBacklight    170.2.5
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport    4.1.4f2
    com.apple.driver.ApplePolicyControl    3.4.5
    com.apple.driver.AppleSMCPDRC    1.0.0
    com.apple.driver.AppleSMCLMU    2.0.3d0
    com.apple.driver.AppleMuxControl    3.4.5
    com.apple.driver.AppleMikeyDriver    2.3.7fc4
    com.apple.driver.AppleUpstreamUserClient    3.5.10
    com.apple.driver.AppleMCCSControl    1.1.11
    com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
    com.apple.GeForce    8.1.2
    com.apple.driver.AppleIntelHD4000Graphics    8.1.2
    com.apple.driver.AppleLPC    1.6.0
    com.apple.driver.AppleIntelFramebufferCapri    8.1.2
    com.apple.nvidia.NVDAStartup    8.1.2
    com.apple.driver.SMCMotionSensor    3.0.3d1
    com.apple.driver.AppleUSBTCButtons    237.1
    com.apple.driver.AppleUSBTCKeyEventDriver    237.1
    com.apple.driver.AppleUSBTCKeyboard    237.1
    com.apple.driver.AppleIRController    320.15
    com.apple.driver.AppleFileSystemDriver    3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0d1
    com.apple.BootCache    34
    com.apple.iokit.SCSITaskUserClient    3.5.5
    com.apple.driver.XsanFilter    404
    com.apple.iokit.IOAHCIBlockStorage    2.3.1
    com.apple.driver.AppleUSBHub    5.5.5
    com.apple.driver.AppleSDXC    1.4.2
    com.apple.iokit.AppleBCM5701Ethernet    3.6.1b4
    com.apple.driver.AppleFWOHCI    4.9.6
    com.apple.driver.AirPort.Brcm4331    615.20.17
    com.apple.driver.AppleAHCIPort    2.5.2
    com.apple.driver.AppleUSBEHCI    5.5.0
    com.apple.driver.AppleUSBXHCI    5.6.0
    com.apple.driver.AppleEFINVRAM    1.7
    com.apple.driver.AppleSmartBatteryManager    161.0.0
    com.apple.driver.AppleACPIButtons    1.7
    com.apple.driver.AppleRTC    1.5
    com.apple.driver.AppleHPET    1.8
    com.apple.driver.AppleSMBIOS    1.9
    com.apple.driver.AppleACPIEC    1.7
    com.apple.driver.AppleAPIC    1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient    196.0.0
    com.apple.nke.applicationfirewall    4.0.39
    com.apple.security.quarantine    2.1
    com.apple.driver.AppleIntelCPUPowerManagement    196.0.0
    com.apple.iokit.IOSurface    86.0.4
    com.apple.kext.triggers    1.0
    com.apple.iokit.IOSerialFamily    10.0.6
    com.apple.iokit.IOBluetoothFamily    4.1.4f2
    com.apple.driver.DspFuncLib    2.3.7fc4
    com.apple.iokit.IOAudioFamily    1.8.9fc11
    com.apple.kext.OSvKernDSPLib    1.6
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport    4.1.4f2
    com.apple.nvidia.gk100hal    8.1.2
    com.apple.driver.AppleGraphicsControl    3.4.5
    com.apple.driver.AppleBacklightExpert    1.0.4
    com.apple.driver.AppleThunderboltEDMSink    1.1.8
    com.apple.driver.AppleThunderboltEDMSource    1.1.8
    com.apple.driver.AppleThunderboltDPOutAdapter    1.8.9
    com.apple.driver.AppleSMBusController    1.0.11d0
    com.apple.driver.AppleSMBusPCI    1.0.11d0
    com.apple.driver.IOPlatformPluginLegacy    1.0.0
    com.apple.driver.X86PlatformPlugin    1.0.0
    com.apple.NVDAResman    8.1.2
    com.apple.iokit.IOAcceleratorFamily    74.5.1
    com.apple.driver.IOPlatformPluginFamily    5.3.0d51
    com.apple.iokit.IOFireWireIP    2.2.5
    com.apple.iokit.IONDRVSupport    2.3.7
    com.apple.driver.AppleHDAController    2.3.7fc4
    com.apple.iokit.IOGraphicsFamily    2.3.7
    com.apple.iokit.IOHDAFamily    2.3.7fc4
    com.apple.driver.AppleSMC    3.1.4d2
    com.apple.driver.AppleUSBMultitouch    237.3
    com.apple.iokit.IOUSBHIDDriver    5.2.5
    com.apple.driver.AppleThunderboltDPInAdapter    1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily    1.8.9
    com.apple.driver.AppleThunderboltPCIDownAdapter    1.2.6
    com.apple.driver.AppleUSBMergeNub    5.5.5
    com.apple.driver.AppleUSBComposite    5.2.5
    com.apple.iokit.IOSCSIMultimediaCommandsDevice    3.5.5
    com.apple.iokit.IOBDStorageFamily    1.7
    com.apple.iokit.IODVDStorageFamily    1.7.1
    com.apple.iokit.IOCDStorageFamily    1.7.1
    com.apple.iokit.IOAHCISerialATAPI    2.5.1
    com.apple.iokit.IOSCSIArchitectureModelFamily    3.5.5
    com.apple.driver.AppleThunderboltNHI    1.7.8
    com.apple.iokit.IOThunderboltFamily    2.4.0
    com.apple.iokit.IOEthernetAVBController    1.0.2b1
    com.apple.iokit.IOFireWireFamily    4.5.5
    com.apple.iokit.IO80211Family    530.4
    com.apple.iokit.IONetworkingFamily    3.0
    com.apple.iokit.IOUSBUserClient    5.5.5
    com.apple.iokit.IOAHCIFamily    2.3.1
    com.apple.iokit.IOUSBFamily    5.6.0
    com.apple.driver.AppleEFIRuntime    1.7
    com.apple.iokit.IOHIDFamily    1.8.1
    com.apple.iokit.IOSMBusFamily    1.1
    com.apple.security.sandbox    220.3
    com.apple.kext.AppleMatch    1.0.0d1
    com.apple.security.TMSafetyNet    7
    com.apple.driver.DiskImages    345
    com.apple.iokit.IOStorageFamily    1.8
    com.apple.driver.AppleKeyStore    28.21
    com.apple.driver.AppleACPIPlatform    1.7
    com.apple.iokit.IOPCIFamily    2.7.3
    com.apple.iokit.IOACPIFamily    1.4
    com.apple.kec.corecrypto    1.0
    System Profile:
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.1f173
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455302D474E2D4620
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455302D474E2D4620
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.17)
    Bluetooth: Version 4.1.4f2 12041, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
    Serial ATA Device: HL-DT-ST DVDRW  GS31N
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 6
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
    A stale or corrupt kernel cache
    A damaged OS X installation
    A fault in a peripheral device, if any
    Corrupt non-volatile memory (NVRAM)
    An internal hardware fault (including incompatible memory)
    An obscure bug in OS X
    You may already have ruled out some of these.
    Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    You can rule out #2 and #3 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't solved by reinstalling in place, without erasing.
    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.
    The Apple Hardware Test or Apple Diagnostics, though generally unreliable, will sometimes detect a fault. A negative test can'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.
    Connecting more than one display is another reported trigger for OS X bugs.
    If your system is not fully up to date, running Software Update might get you a bug fix.
    In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.
    If none of the above applies, 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't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it'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't need to be zeroed.

  • Why does my MBP restart itself randomly several times a day? Something about a "Panic Report".

    Ok so my MacBook Pro shuts itself down and restarts at least 4 times a day. Usually this happens when im away from my computer and its been idle or sleeping or whatever it does, however just 30 minutes ago this happened while i was using it and then it wouldnt restart it just kept showing the loading "apple" logo with loading bars comntinuously spinning... I had to shut it down manually and then it took an extra long time to load before finally loading to the user login page. Now generally... upon start up after this "panic" i will recieve a"Panic report" that says something aloong the lines of...
    Interval Since Last Panic Report:  27841 sec Panics Since Last Report:          2 Anonymous UUID:                    6EBC0F43-E7CB-480C-8D91-9EA7C74EEECC  Wed Jun  5 01:28:29 2013 panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f816c8e1f, type 14=page fault, registers: CR0: 0x0000000080010033, CR2: 0xffffff80d17a0628, CR3: 0x000000008a22e00d, CR4: 0x00000000001606e0 RAX: 0xffffff80d15621f8, RBX: 0xffffff80d1562000, RCX: 0x000000000003cb26, RDX: 0x0000000000000000 RSP: 0xffffff80ef4f3960, RBP: 0xffffff80ef4f3a40, RSI: 0x000000807e876986, RDI: 0xffffff80ef4f39d9 R8:  0x000000000000001f, R9:  0xffffffffffffff00, R10: 0xffffffffffffffdf, R11: 0x0000000000000000 R12: 0xffffff80d179e000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffff80ef4f3960 RFL: 0x0000000000010286, RIP: 0xffffff7f816c8e1f, CS:  0x0000000000000008, SS:  0x0000000000000010 CR2: 0xffffff80d17a0628, Error code: 0x0000000000000000, Faulting CPU: 0x0  Backtrace (CPU 0), Frame : Return Address 0xffffff80ef4f3610 : 0xffffff8000220792  0xffffff80ef4f3690 : 0xffffff80002c4794  0xffffff80ef4f3840 : 0xffffff80002da55d  0xffffff80ef4f3860 : 0xffffff7f816c8e1f  0xffffff80ef4f3a40 : 0xffffff7f816e5c05  0xffffff80ef4f3a80 : 0xffffff7f816c7257  0xffffff80ef4f3ab0 : 0xffffff7f80c95832  0xffffff80ef4f3af0 : 0xffffff7f80c9593d  0xffffff80ef4f3b10 : 0xffffff7f80c9ecff  0xffffff80ef4f3b70 : 0xffffff7f80c9edc8  0xffffff80ef4f3b90 : 0xffffff7f80c9c138  0xffffff80ef4f3bb0 : 0xffffff7f80c9c4bc  0xffffff80ef4f3be0 : 0xffffff80006565fe  0xffffff80ef4f3c40 : 0xffffff8000656fbb  0xffffff80ef4f3d80 : 0xffffff80002a3f08  0xffffff80ef4f3e80 : 0xffffff8000223096  0xffffff80ef4f3eb0 : 0xffffff80002148a9  0xffffff80ef4f3f10 : 0xffffff800021bbd8  0xffffff80ef4f3f70 : 0xffffff80002aef10  0xffffff80ef4f3fb0 : 0xffffff80002daec3        Kernel Extensions in backtrace:          com.apple.iokit.IOGraphicsFamily(2.3.4)[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80c8a000->0xffffff7f80cc2fff             dependency: com.apple.iokit.IOPCIFamily(2.7)[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f80849000          com.apple.driver.AppleIntelHD4000Graphics(7.3.2)[AD64F3E5-2838-3046-A9EA-1CB6C9 769436]@0xffffff7f816c4000->0xffffff7f8172afff             dependency: com.apple.iokit.IOPCIFamily(2.7)[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f80849000             dependency: com.apple.iokit.IONDRVSupport(2.3.4)[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f80cc3000             dependency: com.apple.iokit.IOGraphicsFamily(2.3.4)[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80c8a000  BSD process name corresponding to current thread: WindowServer  Mac OS version: 11G63  Kernel version: Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5 System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)  System uptime in nanoseconds: 5870204567267 last loaded kext at 49584802694: com.apple.driver.AppleMikeyHIDDriver     122 (addr 0xffffff7f8167a000, size 20480) last unloaded kext at 200341249727: com.apple.driver.AppleUSBTCKeyEventDriver     227.6 (addr 0xffffff7f814f7000, size 8192) loaded kexts: com.apple.driver.AppleMikeyHIDDriver     122 com.apple.driver.X86PlatformShim     5.0.0d8 com.apple.driver.AGPM     100.12.75 com.apple.driver.AppleHDA     2.2.5a5 com.apple.driver.AppleUpstreamUserClient     3.5.9 com.apple.driver.AudioAUUC     1.59 com.apple.driver.AppleMikeyDriver     2.2.5a5 com.apple.driver.AppleSMCLMU     2.0.1d2 com.apple.driver.AppleIntelHD4000Graphics     7.3.2 com.apple.driver.SMCMotionSensor     3.0.2d6 com.apple.driver.AppleSMCPDRC     5.0.0d8 com.apple.iokit.IOUserEthernet     1.0.0d1 com.apple.iokit.IOBluetoothSerialManager     4.0.8f17 com.apple.Dont_Steal_Mac_OS_X     7.0.0 com.apple.driver.AudioIPCDriver     1.2.3 com.apple.driver.ApplePolicyControl     3.1.33 com.apple.driver.AppleLPC     1.6.0 com.apple.driver.AppleBacklight     170.2.2 com.apple.driver.AppleMCCSControl     1.0.33 com.apple.driver.AppleIntelFramebufferCapri     7.3.2 com.apple.filesystems.autofs     3.0 com.apple.driver.BroadcomUSBBluetoothHCIController     4.0.8f17 com.apple.driver.AppleUSBTCButtons     227.6 com.apple.driver.AppleUSBTCKeyboard     227.6 com.apple.driver.AppleIRController     312 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1 com.apple.BootCache     33 com.apple.iokit.SCSITaskUserClient     3.2.1 com.apple.driver.XsanFilter     404 com.apple.iokit.IOAHCISerialATAPI     2.0.3 com.apple.iokit.IOAHCIBlockStorage     2.1.0 com.apple.driver.AppleSmartBatteryManager     161.0.0 com.apple.driver.AppleFWOHCI     4.9.0 com.apple.driver.AirPort.Brcm4331     561.7.22 com.apple.driver.AppleSDXC     1.2.2 com.apple.driver.AppleUSBHub     5.1.0 com.apple.iokit.AppleBCM5701Ethernet     3.2.4b8 com.apple.driver.AppleEFINVRAM     1.6.1 com.apple.driver.AppleAHCIPort     2.3.1 com.apple.driver.AppleUSBEHCI     5.1.0 com.apple.driver.AppleUSBXHCI     1.1.0 com.apple.driver.AppleACPIButtons     1.5 com.apple.driver.AppleRTC     1.5 com.apple.driver.AppleHPET     1.7 com.apple.driver.AppleSMBIOS     1.9 com.apple.driver.AppleACPIEC     1.5 com.apple.driver.AppleAPIC     1.6 com.apple.driver.AppleIntelCPUPowerManagementClient     195.0.0 com.apple.nke.applicationfirewall     3.2.30 com.apple.security.quarantine     1.4 com.apple.security.TMSafetyNet     8 com.apple.driver.AppleIntelCPUPowerManagement     195.0.0 com.apple.driver.DspFuncLib     2.2.5a5 com.apple.iokit.IOSurface     80.0.2 com.apple.iokit.IOSerialFamily     10.0.5 com.apple.iokit.IOFireWireIP     2.2.5 com.apple.iokit.IOAudioFamily     1.8.6fc18 com.apple.kext.OSvKernDSPLib     1.3 com.apple.driver.AppleHDAController     2.2.5a5 com.apple.iokit.IOHDAFamily     2.2.5a5 com.apple.driver.X86PlatformPlugin     5.1.1d6 com.apple.driver.AppleSMC     3.1.3d10 com.apple.driver.AppleSMBusPCI     1.0.10d0 com.apple.driver.IOPlatformPluginFamily     5.1.1d6 com.apple.driver.AppleGraphicsControl     3.1.33 com.apple.driver.AppleBacklightExpert     1.0.4 com.apple.iokit.IONDRVSupport     2.3.4 com.apple.driver.AppleSMBusController     1.0.10d0 com.apple.iokit.IOGraphicsFamily     2.3.4 com.apple.kext.triggers     1.0 com.apple.driver.AppleUSBBluetoothHCIController     4.0.8f17 com.apple.iokit.IOBluetoothFamily     4.0.8f17 com.apple.driver.AppleUSBMultitouch     230.5 com.apple.driver.AppleThunderboltDPInAdapter     1.8.5 com.apple.driver.AppleThunderboltDPAdapterFamily     1.8.5 com.apple.driver.AppleThunderboltPCIDownAdapter     1.2.5 com.apple.iokit.IOUSBHIDDriver     5.0.0 com.apple.driver.AppleUSBMergeNub     5.1.0 com.apple.driver.AppleUSBComposite     5.0.0 com.apple.iokit.IOSCSIMultimediaCommandsDevice     3.2.1 com.apple.iokit.IOBDStorageFamily     1.7 com.apple.iokit.IODVDStorageFamily     1.7.1 com.apple.iokit.IOCDStorageFamily     1.7.1 com.apple.iokit.IOSCSIArchitectureModelFamily     3.2.1 com.apple.driver.AppleThunderboltNHI     1.6.0 com.apple.iokit.IOThunderboltFamily     2.0.3 com.apple.iokit.IOFireWireFamily     4.4.8 com.apple.iokit.IO80211Family     420.3 com.apple.iokit.IOEthernetAVBController     1.0.1b1 com.apple.iokit.IONetworkingFamily     2.1 com.apple.iokit.IOUSBUserClient     5.0.0 com.apple.iokit.IOAHCIFamily     2.0.8 com.apple.iokit.IOUSBFamily     5.1.0 com.apple.driver.AppleEFIRuntime     1.6.1 com.apple.iokit.IOHIDFamily     1.7.1 com.apple.iokit.IOSMBusFamily     1.1 com.apple.security.sandbox     177.9 com.apple.kext.AppleMatch     1.0.0d1 com.apple.driver.DiskImages     331.7 com.apple.iokit.IOStorageFamily     1.7.2 com.apple.driver.AppleKeyStore     28.18 com.apple.driver.AppleACPIPlatform     1.5 com.apple.iokit.IOPCIFamily     2.7 com.apple.iokit.IOACPIFamily     1.4 Model: MacBookPro9,2, BootROM MBP91.00D3.B08, 2 processors, Intel Core i7, 2.9 GHz, 8 GB, SMC 2.2f38 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4D34373142353237334448302D434B302020 Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4D34373142353237334448302D434B302020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.198.19.22) Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: TOSHIBA MK7559GSXF, 750.16 GB Serial ATA Device: HL-DT-ST DVDRW  GS31N USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2 USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3 USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2 USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3 USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 6 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9 USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 5 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 4
    What the HECK is happening and whats causing this???? How do i fix it?

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
    A stale or corrupt kernel cache
    A damaged OS X installation
    A fault in a peripheral device, if any
    Corrupt non-volatile memory (NVRAM)
    An internal hardware fault (including incompatible memory)
    An obscure bug in OS X
    You may already have ruled out some of these.
    Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    You can rule out #2 and #3 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't solved by reinstalling in place, without erasing.
    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.
    The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can'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.
    Connecting more than one display is another reported trigger for OS X bugs.
    In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.
    If none of the above applies, 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't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it'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't need to be zeroed.

  • How come my Macbook Air 11inch mid 2013 is running very slow?

    I recently bought it new, then couple months later, the fan would play very loudly, and everything went slow and laggy. I checked activity monitor and it says kernel_task is taking up a lot. Please let me know if there are any ways to make my macbook run back to normal, thank you!
    EtreCheck version: 2.1.1 (104)
    Report generated December 6, 2014 at 10:21:26 AM EST
    Hardware Information: ℹ️
      MacBook Air (11-inch, Mid 2013) (Verified)
      MacBook Air - model: MacBookAir6,1
      1 1.3 GHz Intel Core i5 CPU: 2-core
      4 GB RAM Not upgradeable
      BANK 0/DIMM0
      2 GB DDR3 1600 MHz ok
      BANK 1/DIMM0
      2 GB DDR3 1600 MHz ok
      Bluetooth: Good - Handoff/Airdrop2 supported
      Wireless:  en0: 802.11 a/b/g/n/ac
    Video Information: ℹ️
      Intel HD Graphics 5000 -
      Color LCD 1366 x 768
    System Software: ℹ️
      OS X 10.9.5 (13F34) - Uptime: 5 days 20:36:42
    Disk Information: ℹ️
      APPLE SSD SD0128F disk0 : (121.33 GB)
      S.M.A.R.T. Status: Verified
      EFI (disk0s1) <not mounted> : 210 MB
      Mavericks (disk0s2) / : 120.47 GB (103.02 GB free)
      Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
    USB Information: ℹ️
      Apple Inc. BRCM20702 Hub
      Apple Inc. Bluetooth USB Host Controller
    Thunderbolt Information: ℹ️
      Apple Inc. thunderbolt_bus
    Gatekeeper: ℹ️
      Mac App Store and identified developers
    Launch Daemons: ℹ️
      [loaded] com.adobe.fpsaud.plist [Support]
    User Login Items: ℹ️
      iTunesHelper Application (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
    Internet Plug-ins: ℹ️
      FlashPlayer-10.6: Version: 15.0.0.239 - SDK 10.6 [Support]
      Flash Player: Version: 15.0.0.239 - SDK 10.6 [Support]
      QuickTime Plugin: Version: 7.7.3
      Default Browser: Version: 537 - SDK 10.9
    Safari Extensions: ℹ️
      Extensions: No such file or directory
    User iTunes Plug-ins: ℹ️
      iTunes Plug-ins: No such file or directory: Version: Unknown
    3rd Party Preference Panes: ℹ️
      Flash Player  [Support]
    Time Machine: ℹ️
      Time Machine not configured!
    Top Processes by CPU: ℹ️
          6% WindowServer
          1% AppleSpell
          0% sysmond
          0% Activity Monitor
          0% imagent
    Top Processes by Memory: ℹ️
      248 MB com.apple.WebKit.WebContent
      69 MB Safari
      47 MB Twitter
      39 MB WindowServer
      26 MB mds
    Virtual Memory Information: ℹ️
      1.91 GB Free RAM
      1.33 GB Active RAM
      275 MB Inactive RAM
      526 MB Wired RAM
      2.11 GB Page-ins
      0 B Page-outs
    Diagnostics Information: ℹ️
      Nov 29, 2014, 09:13:59 PM Kernel_2014-11-29-211359_owner1s-iMac-2.panic [Details]
      Nov 29, 2014, 09:12:39 PM Kernel_2014-11-29-211239_owner1s-iMac-2.panic [Details]
      Nov 28, 2014, 06:31:12 PM Kernel_2014-11-28-183112_owner1s-iMac-2.panic [Details]
      Nov 28, 2014, 06:23:06 PM Kernel_2014-11-28-182306_owner1s-iMac-2.panic [Details]
      Nov 28, 2014, 03:07:44 PM Kernel_2014-11-28-150744_owner1s-iMac-2.panic [Details]
      Nov 28, 2014, 03:03:16 PM Kernel_2014-11-28-150316_owner1s-iMac-2.panic [Details]
      Nov 28, 2014, 01:39:08 PM Kernel_2014-11-28-133908_owner1s-iMac-2.panic [Details]
      Nov 27, 2014, 05:35:04 PM Kernel_2014-11-27-173504_owner1s-iMac-2.panic [Details]
      Nov 16, 2014, 09:57:33 PM Kernel_2014-11-16-215733_owner1s-iMac-2.panic [Details]
      Nov 11, 2014, 05:08:59 PM Kernel_2014-11-11-170859_owner1s-iMac-2.panic [Details]
      Nov 8, 2014, 10:07:50 AM Kernel_2014-11-08-100750_owner1s-iMac-2.panic [Details]
      Nov 7, 2014, 10:51:50 PM Kernel_2014-11-07-225150_owner1s-iMac-2.panic [Details]

    The kernel is using excessive processor cycles. Below are some possible causes for the condition.
    Throttling
    When it gets high temperature readings from the hardware, or low voltage readings from the battery of a MacBook, the kernel may try to compensate by interrupting the processor(s) to slow them down and reduce power consumption. This condition can be due to:
    ☞ a buildup of dust on the logic board
    ☞ high ambient temperature
    ☞ a worn-out or faulty battery in a portable
    ☞ the malfunction of a cooling fan, a temperature sensor, a voltage sensor, or some other internal component
    Note that if the problem is caused by a sensor, there may be no actual overheating or undervoltage.
    If the computer is portable, test with and without the AC adapter connected. If kernel_task hogs the processor only on AC power, charging is causing the machine to heat up. That behavior may be normal for some models. CPU usage should drop when charging is complete.
    Apple Diagnostics or the Apple Hardware Test, though not very reliable, is sometimes able to detect a fault. For more thorough hardware testing, make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
    If nothing is wrong with the hardware, then whatever you can do to improve cooling may help.
    Installed software
    User-installed software that includes a device driver or other kernel code may thrash the kernel. That category includes virtualization software, such as Parallels and VMware, as well as most commercial "anti-virus" products. Some system-monitoring applications, such as "iStat," can also contribute to the problem. You can test for this possibility by completely disabling or removing the software according to the developer's instructions, or starting in safe mode. Note, however, that disabling a system modification without removing it or testing in safe mode may not be as easy as you think.
    Corrupt NVRAM or SMC data
    Sometimes the problem is cleared up by resetting the NVRAM or the SMC.
    External display
    Connecting an external LCD display to some MacBook Pro models while the lid is open may cause this issue. If applicable, test by closing the lid or disconnecting the display. You might get better results with a newer LED display.

  • Your Computer was restarted because of a problem

    Hi, I got a Macbook pro last year and it was working fine until a few months back the model is an old A1150 and I am getting this problem. Everytime I turn on the computer it restart by itself after that it works fine and I get this error.
    I have replace my HD and installed the new OS X wich resolve the problem but its back again.
    Interval Since Last Panic Report:  15573 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    002EE0A1-29E0-171B-0595-E4D1229996BE
    Thu Oct 10 10:33:32 2013
    panic(cpu 0 caller 0xffffff800604450e): "a freed zone element has been modified in zone: HFS node"@/SourceCache/xnu/xnu-2050.48.11/osfmk/kern/zalloc.c:219
    Backtrace (CPU 0), Frame : Return Address
    0xffffff80bc60b570 : 0xffffff800601d636
    0xffffff80bc60b5e0 : 0xffffff800604450e
    0xffffff80bc60b620 : 0xffffff8006043d52
    0xffffff80bc60b700 : 0xffffff80062f6bf2
    0xffffff80bc60b770 : 0xffffff80062f83ce
    0xffffff80bc60b870 : 0xffffff8006300b42
    0xffffff80bc60ba90 : 0xffffff8006118894
    0xffffff80bc60bad0 : 0xffffff80060f27cc
    0xffffff80bc60bb50 : 0xffffff80060f21ae
    0xffffff80bc60bc10 : 0xffffff800610cac2
    0xffffff80bc60bd90 : 0xffffff800610572c
    0xffffff80bc60bf50 : 0xffffff80063e97ba
    0xffffff80bc60bfb0 : 0xffffff80060cf453
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    12F37
    Kernel version:
    Darwin Kernel Version 12.5.0: Mon Jul 29 16:33:49 PDT 2013; root:xnu-2050.48.11~1/RELEASE_X86_64
    Kernel UUID: B1B58405-A2B2-3C44-B25D-495053D52AB5
    Kernel slide:     0x0000000005e00000
    Kernel text base: 0xffffff8006000000
    System model name: MacBookPro4,1 (Mac-F42C89C8)
    System uptime in nanoseconds: 72173589356
    last loaded kext at 25062844072: com.apple.driver.AudioAUUC          1.60 (addr 0xffffff7f878e1000, size 32768)
    loaded kexts:
    com.apple.driver.AudioAUUC          1.60
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.iokit.IOBluetoothSerialManager          4.1.7f2
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.AppleHDAHardwareConfigDriver          2.4.7fc2
    com.apple.driver.AppleHDA          2.4.7fc2
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.iokit.CSRBluetoothHostControllerUSBTransport          4.1.7f2
    com.apple.GeForce          8.1.6
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.ApplePolicyControl          3.4.5
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleSMBusPCI          1.0.11d1
    com.apple.driver.AppleUpstreamUserClient          3.5.12
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.AppleSMCLMU          2.0.3d0
    com.apple.driver.AppleLPC          1.6.3
    com.apple.driver.AppleMuxControl          3.4.5
    com.apple.driver.AppleBacklight          170.3.5
    com.apple.driver.AppleMCCSControl          1.1.11
    com.apple.nvidia.NVDAStartup          8.1.6
    com.apple.driver.SMCMotionSensor          3.0.3d1
    com.apple.driver.AppleUSBTrackpad          237.1
    com.apple.driver.AppleUSBTCKeyEventDriver          237.1
    com.apple.driver.AppleUSBTCKeyboard          237.1
    com.apple.driver.AppleIRController          320.15
    com.apple.driver.CSRHIDTransitionDriver          4.1.7f2
    com.apple.driver.AppleFileSystemDriver          3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          34
    com.apple.iokit.SCSITaskUserClient          3.5.6
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.3.5
    com.apple.driver.AppleUSBHub          623.4.4
    com.apple.driver.AirPortBrcm43224          600.36.17
    com.apple.driver.AppleIntelPIIXATA          2.5.1
    com.apple.driver.AppleFWOHCI          4.9.9
    com.apple.driver.AppleAHCIPort          2.6.6
    com.apple.iokit.AppleYukon2          3.2.3b1
    com.apple.driver.AppleUSBEHCI          621.4.6
    com.apple.driver.AppleUSBUHCI          621.4.0
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleACPIButtons          1.8
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.8
    com.apple.driver.AppleAPIC          1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient          214.0.0
    com.apple.nke.applicationfirewall          4.0.39
    com.apple.security.quarantine          2.1
    com.apple.driver.AppleIntelCPUPowerManagement          214.0.0
    com.apple.iokit.IOSerialFamily          10.0.6
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.4.7fc2
    com.apple.iokit.IOAudioFamily          1.9.2fc7
    com.apple.kext.OSvKernDSPLib          1.12
    com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.1.7f2
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.AppleHDAController          2.4.7fc2
    com.apple.iokit.IOHDAFamily          2.4.7fc2
    com.apple.nvidia.nv50hal          8.1.6
    com.apple.iokit.IOSurface          86.0.4
    com.apple.iokit.IOBluetoothFamily          4.1.7f2
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.NVDAResman          8.1.6
    com.apple.driver.IOPlatformPluginFamily          5.4.1d11
    com.apple.driver.AppleGraphicsControl          3.4.5
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleSMBusController          1.0.11d1
    com.apple.iokit.IONDRVSupport          2.3.7
    com.apple.iokit.IOGraphicsFamily          2.3.7
    com.apple.driver.AppleSMC          3.1.5d4
    com.apple.iokit.IOUSBHIDDriver          623.4.0
    com.apple.driver.AppleUSBMergeNub          621.4.6
    com.apple.driver.AppleUSBComposite          621.4.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.6
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOATAPIProtocolTransport          3.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.6
    com.apple.iokit.IOUSBUserClient          630.4.4
    com.apple.iokit.IO80211Family          530.5
    com.apple.driver.AppleEFINVRAM          2.0
    com.apple.iokit.IOATAFamily          2.5.1
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.5.1
    com.apple.driver.AppleEFIRuntime          2.0
    com.apple.iokit.IONetworkingFamily          3.0
    com.apple.iokit.IOUSBFamily          630.4.5
    com.apple.iokit.IOHIDFamily          1.8.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          220.3
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.DiskImages          345
    com.apple.iokit.IOStorageFamily          1.8
    com.apple.driver.AppleKeyStore          28.21
    com.apple.driver.AppleACPIPlatform          1.8
    com.apple.iokit.IOPCIFamily          2.8
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    Model: MacBookPro4,1, BootROM MBP41.00C1.B03, 2 processors, Intel Core 2 Duo, 2.5 GHz, 6 GB, SMC 1.27f3
    Graphics: NVIDIA GeForce 8600M GT, GeForce 8600M GT, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 4 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435323637415A332D43463720
    Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0xCE00000000000000, 0x4D342037305435363633435A332D43453620
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16)
    Bluetooth: Version 4.1.7f2 12718, 3 service, 12 devices, 3 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: WDC WD10JPVX-22JC3T0, 1 TB
    Parallel ATA Device: HL-DT-ST DVDRW  GSA-S10N
    USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd400000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x021a, 0x5d200000 / 3
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x5d100000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x1a100000 / 2

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
    A stale or corrupt kernel cache
    A damaged OS X installation
    A fault in a peripheral device, if any
    Corrupt non-volatile memory (NVRAM)
    An internal hardware fault (including incompatible memory)
    An obscure bug in OS X
    You may already have ruled out some of these.
    Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
    You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation may solve a problem that isn't solved by reinstalling in place.
    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model.
    The Apple Hardware Test or Apple Diagnostics, though generally unreliable, will sometimes detect a fault. A negative test can'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.
    Connecting more than one display is another reported trigger for OS X bugs.
    If your system is not fully up to date, running Software Update might get you a bug fix.
    In rare cases, a malformed network packet from a defective router or other network device can cause panics. Such packets could also be sent deliberately by a skillful attacker. This possibility is something to consider if you run a public server that might be the target of such an attack.
    If none of the above applies, 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't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it'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't need to be zeroed.

Maybe you are looking for