Finder Lock Ups

Hi everyone!
I was going through my computer deleting folders and my Applications and Application Support folders were moved. I'm not sure what went wrong, but my Finder has been locking up ever since--I've returned the folders to where they belong, but something still isn't right. Launching applications from the dock is slow as well.
Any advice?

Hi Lyssa, it's difficult to figure without knowing which folders you deleted and moved. Try this approach.
First Repair Disk:
Steps for using Disk Utility
1. Insert your Mac OS X CD-ROM disc or Restore DVD disc, then restart the computer while holding the C key until you see the spinning gear..
2. Once started up from CD or DVD, choose Disk Utility from the Installer menu.
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from disc to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume, if necessary.
6. Click Repair.
If you repair errors run it until no errors found.
Next, you may be able to repair this with the 10.3.9 Stand Alone Combo Update This is a full install, as opposed to an incremental "delta" update so it should overwrite any files that are damaged or missing. It does not matter if you have applied it before. It has worked well for many.
Remember to Repair Permissions: This should be done BEFORE and AFTER all software installs and updates.
1. Navigate to Utilities/DiskUtility and launch Disk Utility.
2. Choose your volume (usually the second icon)
3. Choose "First Aid" tab
4. Click on "Repair Permissions"
Good luck, let us know.
-mj
[email protected]

Similar Messages

Finder lock ups due to samba shares being invalidated by changing network

I often leave my macbook online for a long time unattended, for simplicity I tend to plug it into its power lead, and also connect it up to my gigabit network. I know i've set the priority in my connections to prefer the wired connection over wireless but just to keep things simple i disable airport so i can be sure that i will be connected via gigabit.
I'll then go in and map a network drive from one of my PCs on the lan, this is mounted and available.
Sometime in the future i'll go mobile again, like i just did today. Disconnecting power and gigabit ethernet, i re-enable airport. After a short while its all good to go.. I then start using the internet connection. All is fine.
Then finally i spot that my samba drive is still mapped, i've had trouble selecting this drive to use it, but sadly also you get real trouble by just trying to eject the mount. Doing so and nothing happens.. after 10-20 seconds everything is frozen, including the animated dock, and top toolbar, and you are presented with the spinning wheel of activity.
applealtesc does NOT bring up the force close dialog, and eventually i was forced to force a shutdown.. apple power button isn't it? I had the power button held down for a long time.
Generally i find the mounting samba drives a bit of a pain in the finder but i can put up with it. Samba shares on windows are a nightmare but they rarely bring down the whole system when a connection has been broken.. i'd love it if mac OS would time out the samba share and just give up, rather than hanging in the way it does do.
Obviously i'm accessing my LAN through a different interface and IP address than i was when i set up the connection. I am not sure if you have a similar problem as described if you just disconnect from the network and have no net connection at all.. not sure what it would do with a share in this way.
Is this worth logging as an actual bug? anyone got any suggestions to fix it?

Ok, no luck yet. Maybe I can ask another question directly related to this issue. I am trying to find the cause of this and I am wondering if there is a brief dropout in the connection to the NAS. By brief, I mean really brief. The NAS is connected via a Homeplug network connection (network via the homes power points) and maybe for a very brief period interferrence on the lines dropped the AFP connection.
Is it normal that it is then impossible for AFP to reconnect, even when the NAS is clearly back on the network?
Any drop will have to be very brief as I can always stream music without issues, and no drop or slow down has caused buffering issues.
But, I don't recall getting this issue when directly connected to the iMac via a short ethernet cable for the initial Time Machine backups that take over a day.
What I don't understand though, is if the connection did briefly drop and loose the AFP link, why can AFP no longer connect back? Why do I need to sleep the iMac and then wake it again.
HTTP connections to the NAS never seem to drop, and when I can't recconnect via AFP, I can always connect via HTTP? Is this expected of the AFP protocol? Or is it an unexpected issue?

Finding the cause of total hardware lock-ups

The new build has been running reasonably well, and I've done no major optimizing so far, and no overclocking (yet). However, I've been having infrequent and seemingly random system lock-ups that would appear to be hardware related.
Last night was about the fourth or fifth of these. I had been working on and off throughout the day on a 4-camera multicamera project, and having no issues at all. This was a TOTALLY different multicam experience than I've had with CS4, where MC was hardly usable. Anyway, I was going to make my last few edits of the night when the system locked up--I had just started playing back a sequence when it happened. No hard drive activity, no keyboard/mouse interaction, no bluescreen--the audio that had started playback, however, got caught in a short loop and made an annoying racket. The only way to return to normal was to hard reboot with the power button depressed. No error or fault is logged in the Windows event logs, beyond the reboot which is recorded as something like, "Your system restarted, probably due to you turning it off... don't do that." The actually fault that perpetuates such a drastic action is not recorded. My initial thoughts were that the RAM has a bad chip somewhere, so I've run a memory test for over 8 hours now, and had 0 errors reported. There were no lock-ups, either--the system has been just humming along that whole time. This obviously does not rule out the RAM, but doesn't make it easy to say it's the problem, either. The only "tweak" I've made to the system is the RAM, and that's by setting the DRAM frequency to 1600MHz; nothing else has been altered in the BIOS.
The last two lock-ups occured in one day, when I was attempting to export to an H.264 file, through the AME queue, with hardware MPE enabled. At different points in the export, the system locked, with similar results as above. After the second lock-up, I disabled GPU acceleration in PPro, and the export completed just fine. Interesting, I thought. However, I'd done other hardware MPE-assisted exports earlier that day and in previous days, with no lock-ups.
As mentioned, I'd encountered at least one other hard freeze, and if I remember correctly, I was in Premiere but not doing anything. I'd walked away from the system for a little while, came back, and it was Living Dead on my return. I hadn't been rendering, importing, playing back, or anything else.
I've been checking my temps with HWmonitor, and there isn't anything out of the ordinary as far as I'm aware. I'm really not stressing the system much, pretty basic and rudimentary edits. The memory test has now done about 600% coverage, and no errors. The bizarre coincidence is that these lock-ups occur when I'm in one of the Adobe programs--but I've never seen software cause a lock-up such as this before.
So... where do I go from here? The lock-ups seem to completely happen at random, with no particular instigation. Is there some sort of other monitor software I can run in the background that might indicate hardware failures that Windows is not able to catch?
I'm hoping you hardware gurus can shed some light on this bizarre predicament... thanks in advance for your insight.
ADDENDUM:
It would seem to make sense to post my hardware... duh:
ASUS P6X58D
i7-930
OCZ Gold 12GB (6 x 2GB) DDR3 1600 (PC3 12800)
GIGABYTE GeForce GTX 480
COOLER MASTER HAF 932
COOLER MASTER Silent Pro 1000W
Western Digital VelociRaptor 150GB (system drive)
HITACHI 500GB 7200 RPM SATA 3.0Gb/s
4x SAMSUNG Spinpoint F3 1TB 7200 RPM SATA 3.0Gb/s (running RAID 5 with onboard controller)
Noctua NH-D14 CPU Cooler

Well, I really wanted Jeff's suggestion to be the solution, but alas, troubles remain. And it would appear that something far more sinister is happening than flaky codecs or software.
The good news is that I can now reliably repeat the lock-up, each and every time. The bad news is that the lock-up occurs whenever I attempt an export. I'm trying to get a 75-minute multicamera edit onto a DVD, and the moment the actual encode begins, the system goes into a hard hang. I have a number of audio clips that are being used, and I see "Adobe Premiere Pro is preparing audio for export" or something like that, and then once the video processing begins, it's curtains.
At first, I thought it was something with the hardware MPE--I'm using a GTX 480 with the hack. Editing works well--remarkably well. Encoding is a different issue, altogether, and it doesnt' matter whether I start the export with the Queue button or the Export button. I tried disabling GPU acceleration, and at first, I thought I had solved the mystery--the encode actually began and progressed for about 30 seconds. However, inevitably it would seem, I got the same hard hang.
The first couple "hangs" were actually system restarts; the Windows desktop would disappear, and moments later, I was back at POST. I then disabled the "Automatically restart" option in Windows, and after doing that, I simply ended up with a frozen system and desktop. I'm not sure those are coincidental, actually; I'm going to test that again this morning to see if I get the restart or the hang.
I've been checking out my temperatures with HWMonitor, and as far as I can tell, I'm not going off the charts with temperatures. Temperatures do climb (I have HWMonitor as I start the encode) for both the CPU cores and GPU, but nothing drastic, and there is no way that it's getting too hot in the 5 seconds that the encode is running before the hang. What about the power supply? I can see wattages for the CPU fluctuating drastically as the encode tries to begin, which I would gather is SOP for the operation of a computer, but is it possible that I am getting too much/too little juice? I've got a 1000W Cooler Master PSU, the components you see listed above, and 6 hard drives--this would seem to be more than sufficient to me (for my current use), but undoubtedly, the system is pulling more watts as it starts to work harder. Unfortunately, there is nothing I can really disconnect to test this theory, since I need all of the components and hard drives connected to do anything.
I'm at a total loss, guys, and I'm more than a little frustrated because I've got a pretty expensive paperweight sitting in my office. Unfortunately, I live in a pretty rural area, so finding a trustworthy computer tech locally is a challenge, so I'm hoping that you tech-savvy folks can through out some places to look.
Help me, Obi-Wan Kenobi... you're my only hope...
Thanks, all...

Total lock-ups with fan running - translate system.log file please!?

Hi, all. My late 2005 2.3 gig dual G5 has been experiencing random lock ups for as long as I can remember. My system is up to date and I have tested each pair of the 5 gigs of ram that I have and the system freezes with each pair. It can happen at any time, when I am doing absolutely nothing, for example, overnight. I am at my wits end!
Here's the system log file for the latest freezes. Can anyone tell me what's going on here??? I really need to get to the root of this problem. Thanks so so much in advance.
Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_Reconnect: connect on /Volumes/Macintosh HD failed 89.
Apr 12 17:32:52 Marc-Weinbergs-Computer kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Macintosh HD, flags 524288, pid 62
Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: Started\n
Apr 12 17:44:46 Marc-Weinbergs-Computer /Library/Application Support/FLEXnet Publisher/Service/11.03.005/FNPLicensingService: This service performs licensing functions on behalf of FLEXnet enabled products.\n
Apr 12 18:01:06 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:01:49 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:08:29 Marc-Weinbergs-Computer diskarbitrationd[69]: SDCopy [1056]:36091 not responding.
Apr 12 18:16:18 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 18:16:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 12 19:24:12 Marc-Weinbergs-Computer ntpd[191]: time reset -0.650307 s
Apr 13 01:05:45 Marc-Weinbergs-Computer ntpd[191]: time reset -0.496917 s
Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
Apr 13 07:15:03 Marc-Weinbergs-Computer postfix/postqueue[1778]: warning: Mail system is down -- accessing queue directly
Apr 13 03:15:03 Marc-Weinbergs-Computer cp: error processing extended attributes: Operation not permitted
Apr 13 15:53:53 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 13 15:53:54 Marc-Weinbergs-Computer KernelEventAgent[62]: tid 00000000 received unknown event (256)
Apr 13 22:15:48 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 13 22:15:47 localhost mDNSResponder-108.6 (Jul 19 2007 11: 33:32)[63]: starting
Apr 13 22:15:48 localhost kernel[0]: vmpagebootstrap: 506550 free pages
Apr 13 22:15:47 localhost memberd[70]: memberd starting up
Apr 13 22:15:49 localhost kernel[0]: migtable_maxdispl = 70
Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.FTATASil3132E" from archive.
Apr 13 22:15:49 localhost kernel[0]: Added extension "com.firmtek.driver.Sil3112DeviceNub" from archive.
Apr 13 22:15:49 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 13 22:15:49 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 13 22:15:49 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Apr 13 22:15:49 localhost kernel[0]: AppleKauaiATA shasta-ata features enabled
Apr 13 22:15:49 localhost kernel[0]: DART enabled
Apr 13 22:15:47 localhost DirectoryService[75]: Launched version 2.1 (v353.6)
Apr 13 22:15:49 localhost kernel[0]: FireWire (OHCI) Apple ID 52 built-in now active, GUID 001451ff fe1b4c7e; max speed s800.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:48 localhost lookupd[71]: lookupd (version 369.5) starting - Sun Apr 13 22:15:48 2008
Apr 13 22:15:49 localhost kernel[0]: USBF: 20.590 OHCI driver: OHCIRootHubPortPower bit not sticking (1). Retrying.
Apr 13 22:15:49 localhost kernel[0]: Extension "com.microsoft.driver.MicrosoftKeyboardUSB" has no kernel dependency.
Apr 13 22:15:49 localhost kernel[0]: AppleSMUparent::clientNotifyData nobody registed for 0x40
Apr 13 22:15:49 localhost kernel[0]: Security auditing service present
Apr 13 22:15:49 localhost kernel[0]: BSM auditing present
Apr 13 22:15:49 localhost kernel[0]: disabled
Apr 13 22:15:49 localhost kernel[0]: rooting via boot-uuid from /chosen: 82827EDF-0263-3B93-BEED-4B114E820B85
Apr 13 22:15:49 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 13 22:15:49 localhost kernel[0]: Got boot device = IOService:/MacRISC4PE/ht@0,f2000000/AppleMacRiscHT/pci@9/IOPCI2PCIBridge/k2-sat a-root@C/AppleK2SATARoot/k2-sata@0/AppleK2SATA/ATADeviceNub@0/IOATABlockStorageD river/IOATABlockStorageDevice/IOBlockStorageDriver/ST3320620AS Media/IOApplePartitionScheme/AppleHFS_Untitled1@10
Apr 13 22:15:49 localhost kernel[0]: BSD root: disk0s10, major 14, minor 12
Apr 13 22:15:49 localhost kernel[0]: jnl: replay_journal: from: 8451584 to: 11420160 (joffset 0x952000)
Apr 13 22:15:50 localhost kernel[0]: AppleSMU -- shutdown cause = 3
Apr 13 22:15:50 localhost kernel[0]: AppleSMU::PMU vers = 0x000d00a0, SPU vers = 0x67, SDB vers = 0x01,
Apr 13 22:15:50 localhost kernel[0]: HFS: Removed 8 orphaned unlinked files
Apr 13 22:15:50 localhost kernel[0]: Jettisoning kernel linker.
Apr 13 22:15:50 localhost kernel[0]: Resetting IOCatalogue.
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 1
Apr 13 22:15:50 localhost kernel[0]: Matching service count = 3
Apr 13 22:15:50 localhost kernel[0]: NVDANV40HAL loaded and registered.
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::start 1
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::end 1
Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - entry
Apr 13 22:15:50 localhost kernel[0]: SMUNeo2PlatformPlugin::initThermalProfile - calling adjust
Apr 13 22:15:50 localhost kernel[0]: PowerMac112ThermalProfile::adjustThermalProfile start
Apr 13 22:15:50 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:78
Apr 13 22:15:50 localhost kernel[0]: BCM5701Enet: Ethernet address 00:14:51:61:ee:79
Apr 13 22:15:51 localhost lookupd[86]: lookupd (version 369.5) starting - Sun Apr 13 22:15:51 2008
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 21611008 to: 7857152 (joffset 0x952000)
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 673280 to: 24382976 (joffset 0x952000)
Apr 13 22:15:51 localhost kernel[0]: jnl: replay_journal: from: 3890176 to: 6294016 (joffset 0x7d01000)
Apr 13 22:15:51 localhost diskarbitrationd[69]: disk0s10 hfs 82827EDF-0263-3B93-BEED-4B114E820B85 NewestSeagate /
Apr 13 22:15:52 localhost kernel[0]: NVDA,Display-A: vram [90020000:10000000]
Apr 13 22:15:52 localhost mDNSResponder: Adding browse domain local.
Apr 13 22:15:53 localhost kernel[0]: hfs mount: enabling extended security on Maxtor
Apr 13 22:15:53 localhost diskarbitrationd[69]: disk1s3 hfs 0DBE2113-B1F5-388F-BF70-2E366A095330 Maxtor /Volumes/Maxtor
Apr 13 22:15:54 localhost kernel[0]: NVDA,Display-B: vram [94000000:08000000]
Apr 13 22:15:54 Marc-Weinbergs-Computer configd[67]: setting hostname to "Marc-Weinbergs-Computer.local"
Apr 13 22:15:54 Marc-Weinbergs-Computer /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Apr 13 22:15:56 Marc-Weinbergs-Computer diskarbitrationd[69]: disk2s3 hfs 971CABB3-C211-38FC-8E91-6B4F8EA5FA20 B08-09-07 /Volumes/B08-09-07
Apr 13 22:15:56 Marc-Weinbergs-Computer loginwindow[110]: Login Window Started Security Agent
Apr 13 22:15:57 Marc-Weinbergs-Computer kernel[0]: AppleBCM5701Ethernet - en1 link active, 1000-Mbit, full duplex, symmetric flow control enabled
Apr 13 22:15:57 Marc-Weinbergs-Computer configd[67]: AppleTalk startup
Apr 13 22:15:57 Marc-Weinbergs-Computer TabletDriver[119]: #### GetFrontProcess failed to get front process (-600)
Apr 13 22:15:59 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Apr 13 22:16:00 Marc-Weinbergs-Computer configd[67]: posting notification com.apple.system.config.network_change
Apr 13 22:16:01 Marc-Weinbergs-Computer lookupd[123]: lookupd (version 369.5) starting - Sun Apr 13 22:16:01 2008
Apr 13 22:16:01 Marc-Weinbergs-Computer kernel[0]: HFS: Removed 2 orphaned unlinked files
Apr 13 22:16:01 Marc-Weinbergs-Computer diskarbitrationd[69]: disk3s3 hfs CDA8BCC5-0CE4-33E8-A910-4B0952DBC230 FullBU-09-07 /Volumes/FullBU-09-07
Apr 13 22:16:04 Marc-Weinbergs-Computer configd[67]: target=enable-network: disabled
Apr 13 22:16:05 Marc-Weinbergs-Computer configd[67]: AppleTalk startup complete
Apr 13 22:16:09 Marc-Weinbergs-Computer TabletDriver[237]: #### GetFrontProcess failed to get front process (-600)
Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: exited with exit code: 253
Apr 13 22:16:09 Marc-Weinbergs-Computer launchd[241]: com.wacom.wacomtablet: 9 more failures without living at least 60 seconds will cause job removal
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0L6LR', reports it is functioning at a temperature of 95.0F (35C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:28 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0L6LR', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '6QF0LGS4', reports it is functioning at a temperature of 100.4F (38C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '6QF0LGS4', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'ST3320620AS', serial number '9RV000FC', reports it is functioning at a temperature of 95.0F (35C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'ST3320620AS', serial number '9RV000FC', appear to still be available. (Total Available: 36) (Use Attempts: 0)
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', reports it is functioning at a temperature of 89.6F (32C) degrees.
Apr 13 22:16:29 Marc-Weinbergs-Computer /Applications/DiskWarrior.app/Contents/MacOS/DiskWarriorDaemon: [Sun Apr 13 22:16:29 EDT 2008] : Spare blocks for ATA device 'Maxtor 6B300S0', serial number 'B6211G0H', appear to still be available. (Total Available: 63) (Use Attempts: 0)
Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
Apr 13 22:16:54 Marc-Weinbergs-Computer /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder: _TIFFVSetField: tiff data provider: Invalid tag "Copyright" (not supported by codec).\n
etc.

Hi-
The machine seems to be having trouble with loading certain drivers, but, as this isn't a crash log, and doesn't show the "hang-up" or freeze, it's hard to tell.
Noted possibilities are:
-Microsoft keyboard (possible USB power problem)
-firmtek driver (from archive) questionable due to the "archive" annotation
-Wacom tablet driver, causing system problems
Running in Safe mode without freezes would help to determine if one of these drivers is the problem.
Other possibilities are outdated drivers, or simply a need to reinstall the OS.
If unnecessary, removing the driver(s) would be a good idea.
External USB and Firewire devices are all suspect, should all be disconnected, revert to Apple keyboard, and test system performance. Adding one device at a time, and testing each will be necessary to clear each device.
I have experienced system trouble when a Wacom tablet was not connected, but the driver was left installed.
Disabling the driver from Startup items may be necessary to test without the Wacom tablet connected.

System lock-ups after upgrading to Tiger

This topic was previously posted in 'Installation & Setup'.
After 3 days (and 18 views) I got no replies.
Maybe that forum was not appropriate, so I decided to try it in this forum.
About 4 months ago I exchanged my 80 GB Hd in favor of an 200 GB Maxtor 6L200P0. One day later I upgraded OS X 10.3.9 to Tiger (retail DVD).
At that time I experienced a frequent (several times a day) lock-up of my system.
No messages, nothing, not even after powering down and restarting.
After some time I figured out that the lock-ups occurred on Internet access. Clicking on a link in Safari, posting messages on Discussions. Even Mail locked the system a few times. Also Corripio (artwork and lyrics finder for iTunes) caused the system to lock.
After that, I decided to perform an Archive & Install (first time after almost 4 years of using this Mac). Except from having to re-install a number of 3rd party apps. the system seemed to perform well. No lock-ups were experienced for a few weeks.
Problem solved, I thought.
Although far less frequent than before, I do experience those annoying lock-ups a few times a week.
Here are my questions:
What could be the cause of the lock-up?
Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I. I'm reluctant to perform a clean install at the moment, because I haven't found a few serials of commercial and shareware applications yet ( I know, I should have written them down :-/ )
Any hints/tips to track down the exact cause?
TIA
M
P.S. ( I do have a bootable complete backup of my HD on an Maxtor Onetouch II )

Hi, M.
1. You wrote: "What could be the cause of the lock-up?"The number of potential causes range from disk corruption or bad applications to serious hardware problems, such as a defective logic board.
2. You wrote: "Any hints/tips to track down the exact cause?"I suggest treating the "lock up" problem — better described as a "freezes and hangs" problem — similar to a kernel panic as the basic troubleshooting and hardware testing steps are virtually the same. See my "Resolving Kernel Panics" FAQ.
It provides a comprehensive roadmap which you should follow from beginning to end, in the order specified in the FAQ.
2. You wrote: "Is is advisable to perform a Clean Install? What advantage do I have of, it opposite to performing an A&I."The term "Clean Install" does not apply in Mac OS X. That is obsolete Mac OS 9 terminology. The closest Mac OS X equivalent to a "Clean Install" is an Archive and Install with the Preserve User and Network Settings option, which it sounds like you've already tried once previously, but you may want to try again as part of the troubleshooting process I outlined above. See my "General advice on performing an Archive and Install" FAQ for some important tips on this process.
The other options are:
• Archive and Install without the Preserve User and Network Settings option: This reinstalls the OS and wipes out both your accounts and your network configuration, but preserves the previous System folder.
• Erase and Install: Erases the hard drive, i.e. Macintosh HD, and reinstalls the OS from scratch, preserving nothing: your accounts, network settings, and everything else on the drive are deleted.
Of those two, and since you have a bootable backup, the second (Erase and Install) would be the second-to-last thing you would try, the last being taking the machine in for service.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

System Lock-ups. What can be wrong?

On to more serious issues.. .
I am experiencing system lock-ups on the brand spanking new computer I just buildt.(Yeah, yeah.. . Anti-static and all other thinkable precautions were taken.. .)
Needless to say it's annoying the hell out of me. I can't work and I can't play with a situation like this.. .
The system just hangs and the only solution is to press the reset button.
This usually happens in games or when scrolling a window. Less frequently it also happens when doing nothing. It only seems like it's getting worse - more frequent that is.
Are there any known issues with TwinMos RAM and nForce2?
The RAM and CPU are running on the same clock. The error persists when running the RAM at it's native clock too.
I'm running Catalyst 4.11 and Bios Information says 113-95702-100.
The BIOS of the MB has not been flashed by me - as out-of-the-box.
Nvidia drivers version 5.10.
No overclocking of any sort of any device.
I will be running the full monty in Memtest x86 over night, but the RAM DIMM is spanking new and has been handeled with the utmost caution. The first five tests returned nothing wrong.
Another peculiar hick-up is that sometimes after the lock-up and after I've pressed the reset button the BIOS seems to take forever to detect the IDE devices. If I power off and on again, the IDE detection happens in a snap. Very, very strange.. .
Edit: I have a sneaking suspicion that it gets worse until I power off/on - after that it will take a longer time for the error to return. I haven't verified this empirically, but I have a hunch.. .
I really hope there's someone with helpful insight to this problem out there!
Thank you for your time.

Woops. Seems like I don't have access rights to the last link.
It seems like downflashing to B30 is the only way to go for me as I'm having *major* stability issues, even with no overclocking.
Heck - I even had to reset and reboot the machine when trying to write this post just now!
I must say I've never experienced such outrageous instability with any of my other MSI MBs before.. . Not from any other make for that matter. This is just incredible.
I'll flash it tomorrow (if I can find a damned floppy somewhere). For now I really have to work.
Fingers crossed!
Thanks again for great input!

Multiple Panics, Lock Ups and Freezes

My MacBook Pro running 10.8.3 has been having some random shut downs and lock ups lately, the latest of which took the internal boot drive totally offline. I was able to recover it after booting to my external recovery drive and running DiskWarrior 4 as Disk Utility simply said I needed to repair the drive before mounting it, but then said it was unrepairable after attempting to do so.
After the DiskWarrior repair, the Mac booted from it's internal drive like there was nothing wrong, but an hour or so later, I had another lock up where everything froze up and was unresponsive and then after a restart I got another hour or so before it shut itself down and then restarted itself, so I'm obviously less than thrilled with the situation.
This is the factory drive which came with the MacBook Pro when purchased new in January of this year, so I have a hard time believing the drive is physically bad, though I guess anything is possible. Another thing that has me thinking it's not the hardware is that the machine runs fine when booted to the external recovery drive and has no errors or any of the symptoms I've been experiencing.
Anyway, I've been looking at the panic reports, but I'm honestly not well versed in what any of this means, so I'm hoping one of the experts can chime in and maybe point me in the right direction as I'm running out of ideas :/
Interval Since Last Panic Report: 2467 sec
Panics Since Last Report:          1
Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
Anonymous UUID:                    BBC20339-6AE8-82EA-4368-DCBBCC912FF4
Thu May 2 13:44:42 2013
panic(cpu 6 caller 0xffffff8025cb7e95): Kernel trap at 0xffffff7fa741c064, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000010, CR3: 0x00000000443ae021, CR4: 0x00000000001606e0
RAX: 0x0000000000000001, RBX: 0xffffff81c60a6000, RCX: 0xffffff8048c44000, RDX: 0xffffff81f7773a38
RSP: 0xffffff81f7773b60, RBP: 0xffffff81f7773b60, RSI: 0x0000000000000000, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0xffffff81c60a6000, R13: 0x0000000000000000, R14: 0x0000000000000002, R15: 0x0000000000000000
RFL: 0x0000000000010246, RIP: 0xffffff7fa741c064, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000010, Error code: 0x0000000000000000, Fault CPU: 0x6
Backtrace (CPU 6), Frame : Return Address
0xffffff81f7773800 : 0xffffff8025c1d626
0xffffff81f7773870 : 0xffffff8025cb7e95
0xffffff81f7773a40 : 0xffffff8025ccd4dd
0xffffff81f7773a60 : 0xffffff7fa741c064
0xffffff81f7773b60 : 0xffffff7fa7405d64
0xffffff81f7773bb0 : 0xffffff7fa7405cba
0xffffff81f7773bd0 : 0xffffff7fa73e17ae
0xffffff81f7773c00 : 0xffffff7fa62b03a0
0xffffff81f7773c40 : 0xffffff7fa62b030f
0xffffff81f7773c60 : 0xffffff7fa62b575c
0xffffff81f7773cf0 : 0xffffff7fa62ade50
0xffffff81f7773d20 : 0xffffff7fa62feb8b
0xffffff81f7773d70 : 0xffffff8026032e7b
0xffffff81f7773dc0 : 0xffffff80260634f7
0xffffff81f7773e30 : 0xffffff8025c97fef
0xffffff81f7773e80 : 0xffffff8025c20aed
0xffffff81f7773eb0 : 0xffffff8025c10448
0xffffff81f7773f00 : 0xffffff8025c1961b
0xffffff81f7773f70 : 0xffffff8025ca5dd6
0xffffff81f7773fb0 : 0xffffff8025ccdd43
      Kernel Extensions in backtrace:
         com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000->0xffffff7fa62dbfff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
         com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62fb 000->0xffffff7fa6608fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
         com.apple.GeForce(8.1)[A15BB65E-3501-340F-87CB-2FD2BAD33E35]@0xffffff7fa73de000 ->0xffffff7fa74aafff
            dependency: com.apple.NVDAResman(8.1.0)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7fa62 fb000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa62e7000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6266000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa62a4000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide:     0x0000000025a00000
Kernel text base: 0xffffff8025c00000
System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)
System uptime in nanoseconds: 187720354206
last loaded kext at 185678984299: com.apple.driver.AudioAUUC          1.60 (addr 0xffffff7fa768f000, size 32768)
loaded kexts:
com.kaspersky.nke          1.0.1d41
com.kaspersky.kext.klif          3.0.0d23
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOBluetoothSerialManager          4.1.3f3
com.apple.filesystems.autofs          3.0
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.driver.AppleHDAHardwareConfigDriver          2.3.7fc4
com.apple.driver.AppleHDA          2.3.7fc4
com.apple.GeForce          8.1.0
com.apple.iokit.IOBluetoothUSBDFU          4.1.3f3
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.driver.AppleMikeyDriver          2.3.7fc4
com.apple.nvidia.NVDAStartup          8.1.0
com.apple.driver.SMCMotionSensor          3.0.3d1
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.AppleIntelHD4000Graphics          8.1.0
com.apple.driver.AppleIntelFramebufferCapri          8.1.0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.3.0
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleMuxControl          3.3.0
com.apple.driver.AppleBacklight          170.2.5
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.driver.AppleUSBTCButtons          237.1
com.apple.driver.AppleIRController          320.15
com.apple.driver.AppleUSBTCKeyEventDriver          237.1
com.apple.driver.AppleUSBTCKeyboard          237.1
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.0
com.apple.iokit.AppleBCM5701Ethernet          3.6.0b1
com.apple.driver.AirPort.Brcm4331          614.20.16
com.apple.driver.AppleFWOHCI          4.9.6
com.apple.driver.AppleAHCIPort          2.5.1
com.apple.driver.AppleUSBEHCI          5.5.0
com.apple.driver.AppleUSBXHCI          5.5.5
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
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.kext.triggers          1.0
com.apple.driver.DspFuncLib          2.3.7fc4
com.apple.iokit.IOAudioFamily          1.8.9fc11
com.apple.kext.OSvKernDSPLib          1.6
com.apple.nvidia.gk100hal          8.1.0
com.apple.NVDAResman          8.1.0
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.3f3
com.apple.driver.AppleThunderboltEDMSink          1.1.8
com.apple.driver.AppleThunderboltEDMSource          1.1.8
com.apple.driver.AppleThunderboltDPOutAdapter          1.8.9
com.apple.driver.X86PlatformPlugin          1.0.0
com.apple.driver.AppleHDAController          2.3.7fc4
com.apple.iokit.IOHDAFamily          2.3.7fc4
com.apple.iokit.IOAcceleratorFamily          30.14
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.3f3
com.apple.driver.AppleSMC          3.1.4d2
com.apple.driver.IOPlatformPluginFamily          5.3.0d51
com.apple.driver.AppleSMBusPCI          1.0.11d0
com.apple.driver.AppleGraphicsControl          3.3.0
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.driver.AppleSMBusController          1.0.11d0
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.driver.AppleThunderboltDPInAdapter          1.8.9
com.apple.driver.AppleThunderboltDPAdapterFamily          1.8.9
com.apple.driver.AppleThunderboltPCIDownAdapter          1.2.6
com.apple.driver.AppleUSBMultitouch          237.3
com.apple.iokit.IOUSBHIDDriver          5.2.5
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.6.3
com.apple.iokit.IOThunderboltFamily          2.2.6
com.apple.iokit.IOUSBUserClient          5.5.5
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IO80211Family          522.4
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOAHCIFamily          2.3.1
com.apple.iokit.IOUSBFamily          5.5.5
com.apple.driver.AppleEFIRuntime          1.7
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.2
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.6 GHz, 16 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, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD 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: 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 / 8
Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 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, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0000, 0x4B4238475F44335F534F31363030434C3130
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 11 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD 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: 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 / 8

1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack. 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.
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.
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 find some other way to bypass Apple's oversight, or the oversight could fail in a particular case due to human error.
For most purposes, applications recognized by Gatekeeper as signed, including App Store products, can be considered safe. Note, however, that at least one trojan for iOS (not for OS X) was briefly distributed by a developer in Russia through the iTunes App Store. That store is under the same oversight by Apple as the Mac App Store, so the protection shouldn't be considered absolute. App Store products may prompt for access to private data, such as your contacts. Think before granting that access. OS X security is based on user input. Never click anything reflexively.
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 presumably effective against known attacks, but maybe not against unknown attacks. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
5. Beyond XProtect, Gatekeeper, and MRT, there’s no evidence of any benefit from other automated protection against malware. The first and best line of defense is always 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 should not be trusted if they do something unexpected, such as asking for permission to access your contacts or your location for no apparent 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. If you need to be able to detect Windows malware in your files, use the free software ClamXav — 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.
By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
8. 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.
ClamXav 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
ClamXav 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 ClamXav unless a network administrator requires you to run an anti-virus application.
9. The greatest harm done by security software, in my opinion, is in its effect on human behavior. It does little or nothing to protect people from emerging threats, but if they get a false sense of security from it, they may feel free to do things that expose them to higher risk. Nothing can lessen the need for safe computing practices.
10. 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.

Constant lock ups with Leopard!

I find myself having to hold in the power button to turn my computer off almost everyday now! I am not sure what is causing these constant lock ups! Ever since upgrading to Leopard have I noticed this. Yesterday It happened when trying to open iTunes. Today it happened when I clicked on MAIL. The icon just bounces in the dock and nothing happens. I hit FORCE QUIT and that doesn't work either.
Do I need to clear something out or get rid of something? Even when I try to restart my computer sometimes that will lock up too! The only way to get around any of these issues is to hold in the power button to turn the whole computer off, wait a few seconds and turn it back on. Once its back on, then I have full functionality out the computer again but its getting on my nerves that I have to do this all to often!
I think they are some cool features with Leopard but I am experiencing way to many bugs/problems with it to be 100% happy with it.
As I am writing this posting, I just clicked on my APPLE icon in the top left of the screen and then clicked ABOUT THIS MAC to make sure I was using the most current version, and NOTHING happened!

Try reinstalling. It sounds like you did an upgrade from an earlier version that may have been corrupt to start with. You may be able to do the following:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Constant stream of lock ups with Lion 10.7.2

At my wits end since upgrading to Lion (10.7.2). I get a constant stream of application lock ups (beach ball) on every app I try: Firefox (8.0.1) , intermitent connectivity to Internet (although I know my connection is good); App Store unable to connect; iTune unable to connect to store; Parallels Desktop locks up; Outlook (Office Mac 2011) locks up, Time Machine locks up, and more not mentioned. None of these seem to occur at the same time; it's more like the app that decides to not work is random. Firefox is good but App Store will not connect; iTunes is good, but Firefox will not connect.
Each time I'm forced to restart or shutdown only to have similar, but not the same, errors after I log back on. The errors (lock ups) started right after the upgrade and have gotten progressively worse as the days/weeks go by. At the point now where the PC is completely unreliable. It's a crap shoot to find out what is working and what is not.
I've tried about everything mentioned in the forums -- verified/fixed permissions, used Mac OS install DVD to verify/fix HDD issues; no help.
Prior to upgrade, I had zero issues running SL -- all of this started with Lion.

simon57 wrote:
In any case, shouldn't Software Update recognise what I am running and what is needed to update it successfully?
To a point. It will inform you of a system update, as with Lion 10.7.2 for example, but that is not the combo update. I set my Systum Updates to install manually, if I see an OS update, I always go to
http://support.apple.com/downloads/
And choose the Combo update whice is always a little bigger, but a cumulative install as mentioned. Always appears to be more stable.
Cheers

Adobe Reader 10.1.4 Lock-Ups

Hello,
When our campus users launch Adobe Reader 10.1.4 after logging on to a campus machine via a network account (with a re-directed app data folder) and launch a PDF from a network location by double-clicking it from Windows Explorer, Adobe Reader will launch, but then lock up and enter a "Not Responding" state after a few seconds of working with the PDF. I can only reproduce this issue with both the Enable Protected Mode at startup and the Show me messages when I launch Reader boxes checked (if either box is unchecked, the lock-up does not occur). If I wait long enough, sometimes, the "Not Responding" state will end and I will be able to view the PDF without issues. However, after a single reboot, the problem re-occurs. Our campus machines are on the 32-bit Windows 7 OS.
I have been able to reproduce this issue in Adobe Reader 10.1.2, 10.1.3, and 10.1.4, but not in Adobe Reader 10.1.1. I am not able to reproduce this issue using a local account opening a local PDF, a local account opening a network PDF, or using a network account to open a local PDF. The issue also does not occur if the user first launches Adobe Reader, and then opens the network PDF using File->Open. In other words, the issue only occurs when a network account opens a network PDF by double-clicking on it from Windows Explorer.
I did some research in the Adobe Reader forums, and here are the workarounds that I found and my success with them:
1) Uncheck Enable Protected Mode at startup
As I stated before, this does work around the problem, but also decreases security. As a troubleshooting step, I tried using the Adobe Reader documentation to white-list everything that Protected Mode was 'blocking'. The lock-ups still occurred even though the Protected Mode log was empty (after whitelisting) and did not indicate that anything was being blocked.
2) Disable Enable Hardware rendering for legacy video cards
This workaround did not work for me, even after disabling the legacy video cards and switching the preferred renderer to software.
3) Uninstall and reinstall Adobe Reader
This workaround was also ineffective.
4) Uncheck Show me messages when I launch Reader
As I stated before, this does work around the problem.
But these are not fixes - just workarounds. Does anyone know what the root problem is and whether or not Adobe will be addressing this issue?
Thank you in advance.

Hi, I can't offer any solution just agreements that it isn't just yourselves but others shared experiences:
The lockup began several years ago and subsequent versions of Reader have not altered the lockup problem one bit.
Typically the whole program loads, as does the document (it doesn't matter which PDF, any and every PDF cause lockup), you have about 4 seconds to scroll down or whatever action then... application completely freezes, states "not responding" and usually it remains entirely locked for at least 1 to 2 minutes while it hogs majority of system resources. When it releases, program again fully responds. Closing and reopening only repeats the same bad user experience.
Uninstalling, reintstalling, new versions, have no effect. Inevitably, the main result is to use PDFs significantly less as it is not worth it, yet ultimately it is unavoidable for documents.
Following your 1,2 and 4 has reduced lockup time to around 50 seconds but still not acceptable for regular use. This reduction and the fact that earlier versions on the same system platform worked 100% fine suggest to me it is additional (and for many users, entirely unecessary) Reader functionality such as trying to get messages, check updates (another to turn off), etc. that halt the software from working smoothly as it should rather than any problem with the host system.
I'd be very surprised to hear Adobe are unaware of the problem as there are many messages about this from a search and yet seemingly no definitive solution as far as I can find.
I too will recheck here in hope of a solution emerging.

Verify Disk results, confusing.. Can they be the cause of system lock ups?

I have been experiencing strange freezes on my Mac Pro 2008 system.
My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
here are the results:
Verify permissions for “Boot Disk”
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
Group differs on "private/etc/hostconfig", should be 0, group is 20.
Permissions verification complete
Verifying volume “Boot Disk”
Performing live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Missing thread record (id = 5888152)
Incorrect number of thread records
Checking multi-linked files.
Checking catalog hierarchy.
Invalid volume directory count
(It should be 184294 instead of 184295)
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Boot Disk was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
As for the problem of the system locking up it does not happen in the same application consistently.
Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
If you need any more details please let me know.
Thanks for reading,
Jannis

These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
Repairing the Hard Drive
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

P7n Dimaond Vista 64 bit lock-ups

Hi, I'm experiencing random hard lock ups of my newly built Vista 64bit PC
I've reinstalled the OS 3 times, i have all the latest drivers.
I've ran memtest several times and the vista memory diag tool with no errors, and on individual sticks. i have stress tested my CPU and GPU with no errors many times.
it sometimes freezes 5 mins after booting up, when surfing the web, when on screen-save,r when typing in word and when playing games, sometimes it will be fine for hours then suddenly just freeze up.
I see nothing in the Event Viewer.
My setup:
MSI p7n Diamond with latest official BIOS version fomr the MSI site.
Intel e8400 @ 3.00GHz (stock)
XFX 9800 GTX Black Edition
4x1GB Corsair DDR2 XMS2 Ram
Antec Quattro 1000W SLI PSU
Trust 5.1 Sound Card.
Hitatchi SATA HDD
Pioneer SATA DVD/RW
Zalman 9700NT CPU cooler.
I updated the BIOS using MSI live update, but it was freezing before the update aswell.
I cant find any pattern to the freez-ups it seems entirely random.
I have manually changed the ram voltage in BIOS to 2.1V (manufacturers reccomendation) and changed timings.
However even at stock values it still freezes
Thanks for reading

Quote from: cliffo88 on 23-September-08, 01:56:38
I updated the BIOS using MSI live update, but it was freezing before the update aswell.
I cant find any pattern to the freez-ups it seems entirely random.
YIKES
Whatever you do, never attempt to update the BIOS of a system that is freezing randomly, especially via MSI Live Update. In fact, you'd be well advised to avoid MSI Live Update entirely.
The most commonly suggested method for flashing BIOS is via USB disk method and only after booting to DOS, not Windows. Even in these conditions, if there are hardware issues that are still preventing the system from running stable (e.g. failing PSU, excessive heat, etc.), you should not attempt to flash the BIOS.
Attempting a BIOS flash under any of these conditions is risking permanent and irreparable damage to your motherboard.
As for your Vista 64 lockups, I personally am not convinced that Vista drivers are completely reliable yet, much less Vista 64. Another possibility is that your PSU is failing.

Finder Locks Up When Using AEBS Attached Drives & Network Backup

This might be more of a general discussion as well as specific to my situation:
I have a new Airport Extreme Base Station with two drives attached via USB powered hub. #1 is an OWC 1TB drive and #2 is a Seagate Momentus 500GB drive. Both are HFS+, and I have never had any issues when attached locally.
I am attempting to back up using CCC and/or SuperDuper to the Seagate with a sparse bundle. Both programs hang up when trying to locate the drive. I am able to Force Quit once, but if I run the programs again the Finder locks up and I can't recover it even using Terminal.
I'm not sure what the problem might be. The network mounted drives are always visible; these lock ups seem to only occur when trying to backup. I've read Finder can be tempermental with networking.
I suppose, for troubleshooting, I should attach one drive directly and go from there?

This might be more of a general discussion as well as specific to my situation:
I have a new Airport Extreme Base Station with two drives attached via USB powered hub. #1 is an OWC 1TB drive and #2 is a Seagate Momentus 500GB drive. Both are HFS+, and I have never had any issues when attached locally.
I am attempting to back up using CCC and/or SuperDuper to the Seagate with a sparse bundle. Both programs hang up when trying to locate the drive. I am able to Force Quit once, but if I run the programs again the Finder locks up and I can't recover it even using Terminal.
I'm not sure what the problem might be. The network mounted drives are always visible; these lock ups seem to only occur when trying to backup. I've read Finder can be tempermental with networking.
I suppose, for troubleshooting, I should attach one drive directly and go from there?

Pages '08 lock ups

A couple months ago, I started having issues with Pages '08. It would lock up while I was typing, or even something as simple as scrolling the page down. All I would get was the little rainbow wheel and a locked up document. At first I thought it was just the one file I was working on, but now it happens all the time. It locks up so bad sometimes that it forces a restart of the computer. No other programs are having this issue. Should i just reinstall Pages '08 from the disc or what. Cause this has made my main wordprocessing program completely useless. I'm on Mac OSX 10.5.8

Update:
Well I think I got it figured out. For some reason, the spell checker was causing the problem. I've always had it set to "Check spelling as you type", but for some reason that is now causing Pages to lock up. So my work around is to simply turn off the "Check Spelling as you type" option, and now there are no more lock ups.

Terca 9100 lock ups

Hi!
I recently got my hands on a second hand tecra 9100. I got it free since the previous owner complained about random lock ups or freezes. As i've testaed the laptop myself i experienced this aswell. It can freeze just about anytime but i've never had it running flawlessly for more than 20 minutes i recon. Sometimes it also refuses to start up. I do not know if this is a lock up in the initial startup sequence.
Anyway it will lock up even in bios and i have dissassembled it and put it back together, replaced the RTC battery (with a non rechargable) and removed any hardware not crucial for useage (i.e WiFi card, extra RAm modules, modem card).
I'm clueless, anyone got any idea of what to try next?
Regards Simon

I think you cant fix it by yourself
In your case the ASP should check the notebook and if necessary replace the faulty part/device.

Finder Lock Ups

Similar Messages

Maybe you are looking for