remarked
Level 1 (0 points)

Q: My iMac keeps crashing and I have no idea why

My iMac keeps crashing, and I don't know why. It started yesterday and for some reason just fails. I get an message saying it has shut down due to an error, and this is then the details of the error report it produces.

 

Can anyone please help and tell me what is wrong?

 

Huge thanks.

 

Hardware Overview:

 

  Model Name:          iMac

  Model Identifier:          iMac9,1

  Processor Name:          Intel Core 2 Duo

  Processor Speed:          2.93 GHz

  Number of Processors:          1

  Total Number of Cores:          2

  L2 Cache:          6 MB

  Memory:          8 GB

  Bus Speed:          1.07 GHz

  Boot ROM Version:          IM91.008D.B08

  SMC Version (system):          1.45f0

  Serial Number (system):          VM******0TM

 

 

  Software  OS X 10.9 (13A603)

 

 

 

Error report as follows:

 

Anonymous UUID:       954FEFB3-53EC-843A-0739-711F6D804866

 

 

Sun Nov 24 16:20:47 2013

panic(cpu 0 caller 0xffffff801dadc19e): Kernel trap at 0xffffff7f9fdceef1, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff7f9fdceef1, CR3: 0x00000000012fe000, CR4: 0x0000000000000660

RAX: 0x0000000000000000, RBX: 0x0000000000000006, RCX: 0x0000000003000000, RDX: 0xffffff8034a5d960

RSP: 0xffffff810e0a3740, RBP: 0xffffff810e0a37a0, RSI: 0xffffff81004a1068, RDI: 0xffffff8034a5d960

R8:  0xffffff801e0d2b30, R9:  0xffffff81004a1068, R10: 0xffffff810e0a34b0, R11: 0x0000000000000206

R12: 0x0000000000000020, R13: 0xffffff810e0a3ab4, R14: 0xffffff8030a0ba08, R15: 0x0000000000000001

RFL: 0x0000000000010282, RIP: 0xffffff7f9fdceef1, CS:  0x0000000000000008, SS:  0x0000000000000010

Fault CR2: 0xffffff7f9fdceef1, Error code: 0x0000000000000010, Fault CPU: 0x0

 

 

Backtrace (CPU 0), Frame : Return Address

0xffffff810e0a33d0 : 0xffffff801da22f69

0xffffff810e0a3450 : 0xffffff801dadc19e

0xffffff810e0a3620 : 0xffffff801daf3606

0xffffff810e0a3640 : 0xffffff7f9fdceef1

0xffffff810e0a37a0 : 0xffffff7f9fdcfda2

0xffffff810e0a39b0 : 0xffffff7f9fde0077

0xffffff810e0a3a30 : 0xffffff801ddb3671

0xffffff810e0a3a90 : 0xffffff801dbdf80d

0xffffff810e0a3ae0 : 0xffffff801dbf4360

0xffffff810e0a3b80 : 0xffffff801dbe5f15

0xffffff810e0a3c30 : 0xffffff801dbe67d2

0xffffff810e0a3f50 : 0xffffff801de3de23

0xffffff810e0a3fb0 : 0xffffff801daf3e06

 

 

BSD process name corresponding to current thread: mds_stores

 

 

Mac OS version:

13A603

 

 

Kernel version:

Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64

Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393

Kernel slide:     0x000000001d800000

Kernel text base: 0xffffff801da00000

System model name: iMac9,1 (Mac-F2218FA9)

 

 

System uptime in nanoseconds: 705898990026

last loaded kext at 511933163642: com.apple.filesystems.smbfs          2.0.0 (addr 0xffffff7f9e370000, size 335872)

last unloaded kext at 705842715414: com.trendmicro.kext.filehook          1.5.0 (addr 0xffffff7f9fdce000, size 98304)

loaded kexts:

com.trendmicro.kext.KERedirect          1.0.0

com.seagate.driver.PowSecLeafDriver_10_5          5.1.1

com.seagate.driver.PowSecDriverCore          5.1.1

com.apple.filesystems.smbfs          2.0.0

com.apple.filesystems.msdosfs          1.9

com.apple.filesystems.cddafs          2.6.0

com.apple.driver.AudioAUUC          1.60

com.apple.driver.AppleBluetoothMultitouch          80.14

com.apple.driver.AppleHWSensor          1.9.5d0

com.apple.driver.AGPM          100.14.11

com.apple.driver.AppleTyMCEDriver          1.0.2d2

com.apple.filesystems.autofs          3.0

com.apple.iokit.IOBluetoothSerialManager          4.2.0f6

com.apple.driver.AppleHDAHardwareConfigDriver          2.5.2fc2

com.apple.driver.AppleMikeyHIDDriver          124

com.apple.driver.AppleHDA          2.5.2fc2

com.apple.iokit.IOUserEthernet          1.0.0d1

com.apple.Dont_Steal_Mac_OS_X          7.0.0

com.apple.driver.AppleHWAccess          1

com.apple.iokit.IOBluetoothUSBDFU          4.2.0f6

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6

com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0

com.apple.driver.AppleMikeyDriver          2.5.2fc2

com.apple.driver.AppleLPC          1.7.0

com.apple.driver.AppleMuxControl          3.4.12

com.apple.driver.AppleBacklight          170.3.5

com.apple.GeForceTesla          8.1.8

com.apple.driver.AppleUpstreamUserClient          3.5.13

com.apple.driver.AppleMCCSControl          1.1.12

com.apple.nvidia.NVDAStartup          8.1.8

com.apple.driver.iPodSBCDriver          1.7.0

com.apple.driver.AppleIRController          325.7

com.apple.driver.AppleFileSystemDriver          3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1

com.apple.BootCache          35

com.apple.iokit.SCSITaskUserClient          3.6.0

com.apple.driver.XsanFilter          404

com.apple.iokit.IOAHCIBlockStorage          2.4.0

com.apple.nvenet          2.0.21

com.apple.driver.AppleFWOHCI          4.9.9

com.apple.driver.AirPort.Brcm4331          700.20.22

com.apple.driver.AppleUSBHub          650.4.4

com.apple.driver.AppleUSBEHCI          650.4.1

com.apple.driver.AppleAHCIPort          2.9.5

com.apple.driver.AppleUSBOHCI          650.4.1

com.apple.driver.AppleRTC          2.0

com.apple.driver.AppleHPET          1.8

com.apple.driver.AppleACPIButtons          2.0

com.apple.driver.AppleSMBIOS          2.0

com.apple.driver.AppleACPIEC          2.0

com.apple.driver.AppleAPIC          1.7

com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0

com.apple.nke.applicationfirewall          153

com.apple.security.quarantine          3

com.apple.driver.AppleIntelCPUPowerManagement          216.0.0

com.apple.driver.IOBluetoothHIDDriver          4.2.0f6

com.apple.driver.AppleMultitouchDriver          245.13

com.apple.AppleGraphicsDeviceControl          3.4.12

com.apple.kext.triggers          1.0

com.apple.iokit.IOSerialFamily          10.0.7

com.apple.driver.DspFuncLib          2.5.2fc2

com.apple.vecLib.kext          1.0.0

com.apple.iokit.IOAudioFamily          1.9.4fc11

com.apple.kext.OSvKernDSPLib          1.14

com.apple.iokit.IOSurface          91

com.apple.iokit.IOBluetoothFamily          4.2.0f6

com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6

com.apple.iokit.IOFireWireIP          2.2.5

com.apple.driver.AppleHDAController          2.5.2fc2

com.apple.iokit.IOHDAFamily          2.5.2fc2

com.apple.driver.AppleSMC          3.1.6d1

com.apple.driver.IOPlatformPluginLegacy          1.0.0

com.apple.driver.AppleSMBusPCI          1.0.12d1

com.apple.driver.IOPlatformPluginFamily          5.5.1d27

com.apple.driver.AppleGraphicsControl          3.4.12

com.apple.driver.AppleBacklightExpert          1.0.4

com.apple.nvidia.classic.NVDANV50HalTesla          8.1.8

com.apple.driver.AppleSMBusController          1.0.11d1

com.apple.nvidia.classic.NVDAResmanTesla          8.1.8

com.apple.iokit.IONDRVSupport          2.3.6

com.apple.iokit.IOGraphicsFamily          2.3.6

com.apple.iokit.IOUSBMassStorageClass          3.6.0

com.apple.driver.AppleUSBHIDKeyboard          170.15

com.apple.driver.AppleHIDKeyboard          170.15

com.apple.iokit.IOUSBHIDDriver          650.4.4

com.apple.driver.AppleUSBMergeNub          650.4.0

com.apple.driver.AppleUSBComposite          650.4.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.0

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.6.0

com.apple.iokit.IOFireWireSBP2          4.2.5

com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0

com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0

com.apple.iokit.IOFireWireFamily          4.5.5

com.apple.iokit.IO80211Family          600.34

com.apple.iokit.IONetworkingFamily          3.2

com.apple.iokit.IOUSBUserClient          650.4.4

com.apple.driver.AppleEFINVRAM          2.0

com.apple.driver.NVSMU          2.2.9

com.apple.driver.AppleEFIRuntime          2.0

com.apple.iokit.IOAHCIFamily          2.6.0

com.apple.iokit.IOUSBFamily          650.4.4

com.apple.iokit.IOHIDFamily          2.0.0

com.apple.iokit.IOSMBusFamily          1.1

com.apple.security.sandbox          278.10

com.apple.kext.AppleMatch          1.0.0d1

com.apple.security.TMSafetyNet          7

com.apple.driver.AppleKeyStore          2

com.apple.driver.DiskImages          371.1

com.apple.iokit.IOStorageFamily          1.9

com.apple.iokit.IOReportFamily          21

com.apple.driver.AppleFDEKeyStore          28.30

com.apple.driver.AppleACPIPlatform          2.0

com.apple.iokit.IOPCIFamily          2.8

com.apple.iokit.IOACPIFamily          1.4

com.apple.kec.pthread          1

com.apple.kec.corecrypto          1.0

Model: iMac9,1, BootROM IM91.008D.B08, 2 processors, Intel Core 2 Duo, 2.93 GHz, 8 GB, SMC 1.45f0

Graphics: NVIDIA GeForce GT 130, NVIDIA GeForce GT 130, PCIe, 512 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x8783, 0x53524433344731333333534D414300000000

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x8783, 0x53524433344731333333534D414300000000

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)

Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

Serial ATA Device: ST31000342ASQ, 1 TB

Serial ATA Device: OPTIARC DVD RW AD-5670S, 295 MB

USB Device: Built-in iSight

USB Device: Keyboard Hub

USB Device: Apple Keyboard

USB Device: IR Receiver

USB Device: BRCM2046 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus:

 

<Edited by Host>

iMac, Mac OS X (10.6.1), iPhone

Posted on Nov 24, 2013 4:21 AM

Close
remarked

Q: My iMac keeps crashing and I have no idea why

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Nov 24, 2013 1:33 AM in response to remarked
    Level 10 (208,037 points)
    Applications
    Nov 24, 2013 1:33 AM in response to remarked

    The memory you installed doesn't match the specifications for your model (1066 MHz DDR3 SDRAM.) Reinstall the original memory, or new memory of the right type.

  • by Paul_31,

    Paul_31 Paul_31 Nov 24, 2013 1:33 AM in response to remarked
    Level 6 (13,925 points)
    Nov 24, 2013 1:33 AM in response to remarked

    com.trendmicro.kext.filehook          1.5.0 (addr 0xffffff7f9fdce000, size 98304)

    loaded kexts:

    com.trendmicro.kext.KERedirect          1.0.0

    com.seagate.driver.PowSecLeafDriver_10_5          5.1.1

    com.seagate.driver.PowSecDriverCore          5.1.1

    Trouble-shooting kernel panics can be difficult, but it's often suggested on here to start by removing the non-Apple stuff.

    It's always best to remove the software using an uninstaller program which is hopefully available from the developer/vendor.

    You can always re-install them if they prove not to be the cause of the KP's.

    Alternatively, you could startup in Safe Mode, which will prevent them from loading. However, you may find that it's difficult to run in Safe Mode for long as various other things don't get loaded as well and the Mac will feel like it's not operating at its full potential.

    Safe Boot: Restart holding down the Shift key until you see a grey progress bar, input your admin password when prompted and let it boot.

     

    Another common cause of KP's is incompatible or malfunctioning RAM modules. Have you added any new RAM chips recently?

  • by Paul_31,

    Paul_31 Paul_31 Nov 24, 2013 1:34 AM in response to Paul_31
    Level 6 (13,925 points)
    Nov 24, 2013 1:34 AM in response to Paul_31

    I've just seen Linc's posted - go with his advice first .

  • by remarked,

    remarked remarked Nov 24, 2013 1:55 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 24, 2013 1:55 AM in response to Linc Davis

    Hi Linc, and Paul,

     

    This memory has been in this machine for at least 3 years now, if not longer. Indeed it is that long ago I can't even remember when or where I got it. I'm even wondering if I had ordered the Mac with this extra memory included within it...

     

    So in answer no new memory has been added for a long time.. Would that suggest it is faulty?

     

    Cheers, and thanks. I do really appreciate the support.

  • by Paul_31,

    Paul_31 Paul_31 Nov 24, 2013 2:03 AM in response to remarked
    Level 6 (13,925 points)
    Nov 24, 2013 2:03 AM in response to remarked

    Has this started since upgrading to Mavericks 10.9? I'd still consider removing the items as described above.

     

    There is software called Rember that you can run to test your RAM, although I think the results it delivers might not be 100% reliable, but it might give an indication.

    https://www.macupdate.com/app/mac/15837/rember

  • by Linc Davis,

    Linc Davis Linc Davis Nov 24, 2013 10:07 AM in response to remarked
    Level 10 (208,037 points)
    Applications
    Nov 24, 2013 10:07 AM in response to remarked

    The memory is still wrong, no matter when it was installed. Mavericks uses memory differently than previous versions of OS X, and that may be why you can no longer get away with using it. The type of panic you're getting is usually caused by a memory fault.

     

    Regardless of that, you should remove the worthless "Trend Micro" product. I don't think it's causing this problem, but it's certainly capable of causing others.

    Uninstall the Trend Micro product by following the instructions on whichever of the pages linked below is applicable:

    Removing Trend Micro Titanium Internet Security

    Uninstalling Trend Micro Smart Surfing

    Reboot. Back up all data before making any changes.

  • by remarked,

    remarked remarked Nov 27, 2013 2:41 AM in response to Linc Davis
    Level 1 (0 points)
    Nov 27, 2013 2:41 AM in response to Linc Davis

    Hi Paul,

     

    Yes it has. But not straight away. It started this weekend and I updated to Mavericks when it came out.

     

    Now it hasn't happened since...

     

    I also ran Rember, results as follows:

     

    Rember Test Results

     

    All tests passed!

     

    Total built-in memory: 8 GB

     

     

      This is the total amount of physical memory that the computer has installed.  If this figure is not showing the correct amount of memory there may be a problem with one or more installed DIMMS.

     

    Available memory: 1361 MB

     

      Available memory is the amount of physical memory that is currently not in use by any other processes.  All available memory will be used for testing when the "All" option is selected. To increase the amount of available memory, you can restart your computer before testing. If you are familiar with the command line (CLI), you can run memtest (the core of Rember) in single-user mode. See Rember help, or http://www.memtestosx.org for more information.

     

    Requested amount: All MB

     

      The total amount of memory requested for testing by the Rember application. Not all requested memory can be allocated for testing. See information on "Available memory" for more information.

     

    Memory allocated for testing: 1361 MB

     

      This is the total amount of memory that memtest was able to allocate for testing.  See "Available memory" section for more information.

     

    -------

     

    Loops selected: 1

     

      Total loops selected by user for testing. All loops should complete when testing is successful. Test failure when the "Continue on Error" preference is selected will cancel tests before this number of loops has been completed. Users can also cancel testing before this number is reached.

     

    Loops completed: 1

     

      Total loops completed by memtest.  Note that the Rember is not always able to identify how many loops ran.  If there are discrepancies between this and the loops selected, the log should be examined to determine exactly how many loops were performed.

    -------

     

    Total execution time: All tests passed!  Execution time: 1346  seconds

     

      This is the total amount of time that it took to execute the selected tests. Execution time may vary from system to system, and is provided as a guide for determining how long users can expect tests to run based on the amount of memory installed on the system.

     

    Testing start time: 2013-11-27 07:34:48 +0000

     

    Testing end time: 2013-11-27 07:57:18 +0000

     

     

    Rember version: 0.3.7b Memtest version: 4.22

     

    And what is wrong with Trend Micro Titanium as a package?

  • by Paul_31,

    Paul_31 Paul_31 Nov 27, 2013 3:12 AM in response to remarked
    Level 6 (13,925 points)
    Nov 27, 2013 3:12 AM in response to remarked

    Not sure what to suggest next. Good that your RAM passes the tests, but Linc is not often wrong with his analysis. If you look at Macsales for your particular Mac, how does what they say will work compare with what you have installed?

    http://eshop.macsales.com/shop/apple/memory/iMac

     

    To be honest, I don't even know what Trend Micro Titanium is, but I do know that it often figures in panic reports posted on here. I'd still suggest removing and testing - you can always re-install it if you need it if it proves not to be the problem.

     

    Another thing you could do is run EtreCheck and post the contents of its report on here. I'm not expert in fully anlaysing the contents, but many on here are and someone else might spot a possible cause:

    http://www.etresoft.com/etrecheck

  • by Linc Davis,

    Linc Davis Linc Davis Nov 27, 2013 6:34 AM in response to remarked
    Level 10 (208,037 points)
    Applications
    Nov 27, 2013 6:34 AM in response to remarked

    And what is wrong with Trend Micro Titanium as a package?

     

    1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack, and what you should and should not do to protect yourself from that threat. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
      
    If you find this comment too long or too technical, read only sections 5, 6, and 10.
      
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.

    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
       
    The following caveats apply to XProtect:
    • It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    • It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
      
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
       
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    • It can easily be disabled or overridden by the user.
    • A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
    • An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
    For the reasons given above, App Store products, and other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. OS X security is based on user input. Never click through any request for authorization without thinking.
           
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
     
    5. The built-in security features of OS X reduce the risk of malware attack, but they're not absolute protection. The first and best line of defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
        
    That means, in practice, that you never use software that comes from an untrustworthy source, or that does something inherently untrustworthy. How do you know what is trustworthy?
    • Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is untrustworthy.
    • A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    • Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
    • Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
    • Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are in this category, though not all are necessarily harmful.
    • Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe.
    • Even signed applications, no matter what the source, should not be trusted if they do something unexpected, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
      
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
       
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it — not JavaScript — in your browsers.
       
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.

    Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself from malware.

    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. Any database of known threats is always going to be out of date. Most of the danger is from unknown threats. If you need to be able to detect Windows malware in your files, use one of the free anti-virus products in the Mac App Store — nothing else.
      
    Why shouldn't you use commercial "anti-virus" products?
    • Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    • In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    • To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. Most of the real-world danger of malware attack comes from highly targeted "zero-day" exploits that are not yet recognized.
    • By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. An anti-malware product from the App Store, such as "ClamXav," doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
        
    An anti-virus app is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
        
    A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
      
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
       
    Anti-virus software may be able to tell you which particular virus or trojan it is, but do you care? In practice, there's seldom a reason to use the software unless a network administrator requires you to do it.
      
    The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have the disadvantages mentioned in section 7.
      
    9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
        
    10. As a Mac user you don't have to live in fear that your computer is going to be infected every time you install an application, read email, or visit a web page. But neither should you have the false idea that you will always be safe, no matter what you do. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.