Aperture 3.3 continues to process non-stop

So I finally broke down and purchased A3 after using the demo... I installed on a 2.4 MBP, 4 gigs of RAM. I imported nearly 200 gigs off an external drive that contained my iphoto library onto a new external fw800 drive. THe entire import ran fine, everything seems to be there, however I noticed that whenever I launch A3 it never ceases to stop "processing". I even let the machine run A3 all day today to see if it would ever finish "processing".. negatory. Is this normal? I am not editing anything... I am simply launching the app and it continues to process.... Anybody out experience the same thing? Is this normal? Is this connected to the fact that my library is pretty huge?

Thanks Eric!
Apparently it was a faces issue... it is tracking through all my photos looking for faces I've marked.

Similar Messages

Aperture Library accessed once a second, non-stop?

Sat down to my iMac this morning and, within seconds of waking up, I noticed that the hard drive was being accessed once a second, non-stop. After 5-10 minutes, it started getting annoying, so I did some digging in Terminal. It appears a java process is hitting my Aperture library non-stop. Killing the process leads to some quiet, but the system relaunches the process and I'm right back to where I started. Anyone have any idea what's going on? My internet connection is seeing fairly consistent use at about 50 KB/s, which could be related. I do, however, have Photo Library turned off.

Constant entries such as the following when I check file system usage (e.g. sudo fs_usage -w -f "filesys").
09:35:11.032847 getattrlist                            /Users/xxx/Pictures/Aperture/Aperture 3 Library.aplibrary/Database/Versions/2010/02/14/20100214-170149/NibiNOTbQbmtXcZK cDsx5A/Master.apmaster                     0.000011   java.2096958
09:35:11.032916 getattrlist                            /Users/xxx/Pictures/Aperture/Aperture 3 Library.aplibrary/Database/Versions/2010/02/14/20100214-170149/NibiNOTbQbmtXcZK cDsx5A/Master.apmaster                     0.000012   java.2096958
09:35:11.032970 pwrite            F=93   B=0x1a       O=0x06ac2304                                                                                                                                                             0.000006   java.2096959
09:35:11.033137 lstat                                  /Users/xxx/Pictures/Aperture/Aperture 3 Library.aplibrary/Database/Versions/2010/02/14/20100214-170149/NibiNOTbQbmtXcZK cDsx5A/Master.apmaster                     0.000008   java.2096958
09:35:11.033267 listxattr                              /Users/xxx/Pictures/Aperture/Aperture 3 Library.aplibrary/Database/Versions/2010/02/14/20100214-170149/NibiNOTbQbmtXcZK cDsx5A/Master.apmaster                     0.000008   java.2096958
09:35:11.033302 stat_extended64                        /Users/xxx/Pictures/Aperture/Aperture 3 Library.aplibrary/Database/Versions/2010/02/14/20100214-170149/NibiNOTbQbmtXcZK cDsx5A/Master.apmaster                     0.000007   java.2096958
There's a little bit of mds activity scattered throughout the log, but not enough to explain the constant accessing. I'm rebuilding the library right now to see if that has any effect. Malware is highly unlikely (I run a pretty tight ship), but I won't rule it out.

Inbound Idocs: Queue Processing (non-stop queue?)

Hi everyone!
I have an issue with a File to Idoc interface. The customer would want the IDocs arriving to R3 to be in the same order they were sent from the legacy. From the File Adapter there isn't any problem using the EOIO QoS, and in the IDoc Receiver Adapter I checked the "Queue Processing".
There is something in the R3 side that the customer doesn't like much and it's about the stop of queue when an IDoc gets in error status: all the subsequent IDocs stay in status 75 ("IDoc received via qRFC").
I can change the status of the wrong IDoc and then release the stopped queue but: Is there a way to process serialized inbound IDocs avoiding the stop of the queue if an error occurs?
I'm using PI 7.0 SP30.
Thank you in advance!

First, this is not serialization, it's the queuing design EOIO... they are not the same.
So, since you activated EOIO in the Sender CC it's normal to have such behave (i.e. 75 status)...
Basically the serialization is not a good fit for these requirements.
Here is one solution:
1- Use dynamic queue name (via UDF) to create more parallelism since I dont think you have to queue all the IDOCs in one single queue.
2- Copy the IDOCs with 75 status to a new IDOCS with 64 (You must have very few)
3- Use RC1_IDOC_SET_STATUS to change the status of the IDOCS from 75 to something 73
4- There is standard report that you have to schedule and restart the queues
5- Reprocess the IDOCs from steps 2
The enemy of EOIO design is the user locks in the target system...
Cheers,
Fouad

Restarted ipod and it continues to restart non-stop

hey, i reset my ipod nano and it continues to restart nonstop, also, my computer (windows xp) is not reading my ipod, i need to use this tommorow on a trip so will someone please respond!! can anyone help!!??
??? Windows XP

Well, it's after "tomorrow"...
Start you iPod in Disk Mode by holding Select (middle button) and Play/Pause for a few seconds. You can now connect to your iPod with iTunes and remove the last files added.
Reboot your Ipod by holding Menu and Select a few seconds.
It seems to be a problem with some mp3-files, either strange header-information or some weird problen with gapless playback.
Thomas

Latest upgrade continues to load non stop for hours.

Tried several times to download to latest version of Fire fox software from my laptop. First I get "connecting to the upgrade server" then "downloading Fire Fox". However download continues for several hours nonstop. This has never happened before. I am mystified.
Harry Goh

See:
* http://kb.mozillazine.org/Software_Update (Software Update not working properly)
Remove the files in the updates and updates\0 folder.
You may need to delete active-update.xml and updates.xml as well if present.
C:\Documents and Settings\<user>\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox\updates
(%USERPROFILE%\Local Settings\Application Data\Mozilla\Firefox\Mozilla Firefox)
If you have problems with updating then easiest is to download the full version and uninstall the currently installed version and remove the Firefox program folder to do a clean install of the new version.
Do a clean (re-)install:
* Download a fresh Firefox copy and save the file to the desktop.
* Firefox 4.0.x: http://www.mozilla.com/en-US/firefox/all.html
* You may need to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder] and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.

Ipod 80gb is stuck on apple screen and clicks. Continue to restart non stop

I have two ipods and both are having the same problem. One is a 2gb nano and the other is an 80gb 5th gen. Both will go to the apple load screen and sit there for a second or two and restart and never end this sequence for hours. The 80gb 5th gen will make clicking noises between restarts. Both batteries have been charged and I even replaced the battery in the 80 gb with a new one and still the same problem. I thought maybe the hard drive was to blame but the nano doesn't have one. I have no idea what it could me.
Here is a video I posted on you tube as well. Not the best quality but you get the idea.
http://www.youtube.com/watch?v=F_3nFCFZFlA
I have tried restoring to factory settings and reinstalling software but no luck.
Message was edited by: LT Respect
Message was edited by: LT Respect

i have the same problem with my 30gb ipod video. what happens with my ipod is it sits with the apple logo(with no back light on) on and then will keep doing this with an occational sad ipod face. i was conivinced it was the harddrive so i bougt a new one and installed it my self but nothing has changed. i have tryed putting it in to dfu mode and restoreing it that way but once it is pluged into the usb cable it will shut off and go back to the apple icon.

How can i stop my aperture, my aperture now is non stop transfer in the movies

How can i stop my aperture, my aperture now is non stop transfer in the movies.

non stop transfer in the movies
Transfer movies from where? Sorry, I don't understand. Are you importing movies? Or rendering a slideshow as a movie and exporting a movie? Syncing with iCloud, Flickr, Facebook?
If importing movies into Aperture is hanging, and there is no progress at all, force quit Aperture (From the Apple -menu > Force quit ⌥⇧⌘⎋)
Then repair your Aperture library using the Aperture library First Aid Tools:
Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library

A non-stop background process

We want to build a non-stop background process under SGI IRIX OS environment,
which can access Oracle DB and transmits large volume data files to other machine.
so, we just want to know whether we can build such a program using Java language.
and also, if we can, will it impact other system processes and resources???

Yes you can. As for the impact it depends on how are you going to build the application.

HP Pavilion DV2000 Laptop makes continuous "none stop" loud whining noise.

HP Pavilion DV2000 laptop makes continuous "none stop" loud whining noise. This happens when the computer is on and only stops if it is shut off.
The noise is very frustrating and just never goes away.
I googled for clues and read that proplems with the processor power management, something to do with AMD but the explaination were not clear and I don't want to ruin the computer. Here is a link to what I read. http://forum.notebookreview.com/showthread.php?t=192213
The sound is mainly coming from the left speaker area. So I disabled the sound card but the noise continues.
The fan appeares to be working well and no over heating.
Any clues as to how I can make this stop?
Thanks everyone.
AI

The fan is so loud that when I have people around me they always ask me what's wrong with my computer. I bought it about 2 years ago but the warranty was only valid for a year and the fan problem got really bad after a year so there was nothing I could do about it. My old Toshiba, which is now more than 5 years old and which I had given to my brother after buying the HP, is still going strong and its fan, even during a hot summer day and while running some rather powerful graphic application on it, is never as loud as the fan which is normally on at all times on the HP. Besides, right after buying the HP and diligently doing all the updates that were recommended by HP Health Check, it died and I had to send it back to HP but because I was outside of the US, at the time, I had no computer for weeks until I returned to the US, got a free box from HP, shipped it to them and got it back. It didn't cost any money but it was a big hassle and not a very promising sign of future problems to come. Good luck to everyone who will buy an HP computer in the future. I am going back to Toshiba.

Upon entering aperture, hard drive sticks, says 'processing" nothing works, any ideas?

When I open aperture, the hardrive sticks, indicates "processing." Started when a canon camera was downloading files. Any way to find out what it is "processing" and get it to stop?

Thanks for your help. The activity box came up, said 'processing" but wouldn't let me cancel it. I tried taking out the library and the "processing" continued the next time I opened apertature. The only solution I have found to make it work, strangely enough, is to open it, force quit, open it again, minimize it, and open it - then it works and the activity viewer says nothing is going on.

Aperture won't "quit" and processing very slowly

I'm running Aperture 3.4.1 on a late 2009, 27 inch iMac with 8GB of RAM.
Since I downloaded version 3.4.1 I'm finding that Aperture is incredibly slow in processing smallish batches of photos (e.g. 60 x 15.5MB RAW files).
I've left it running for 24 hours and find that as soon as I try to edit a photo adjustments don't show up in the preview, because it's either "loading" (and never stops loading) or "processing."
When I try to quit Aperture either by selecting Quit or the little x in the top left of the window, nothing happens. And yet, I'm not getting any indication that Aperture is "not responding" if I open Force Quit or the Activity Monitor.
Very frustrating, as I'm trying to edit some photos for family member, and can't really do a thing.
My library is 421GB and not referenced (maybe that's part of the problem; I don't know)
Any sage advice will be appreciated.
cheers,
Nick

The first step did nothing for me,
You really could not work with a new, empty library from your account?
Switching back to my main account though and removing the user preferences did not change a thing though.
o.k., did you also try to remove your presets, not only the preferences com.aperture.plist?
The presets are in the folder:
~/Library/Application Support/Aperture/
and especially the Raw decode Presets occasionally are causing trouble.
Remove the Image capture preferences as well; see this post by fof:
Re: Aperture 3.4 will not open after 10.8.2 installed
Quit Aperture, if it is running:
Open the user library by using the Finder's "Go > Go to Folder" menu,
enter ~/Library/Preferences/ByHost into the textfield.
In the widow that will open, remove all files from the "ByHost" folder, that have "com.apple.ImageCapture......" in its name.
From the "Preferences" folder remove "com.apple.Image_Capture.plist".
Then try to launch Aperture again.
Regards

Curve 8520 Non-Stop Rebooting and stuck on reboot mode. HELP

My phone is on this weird state now that it freezes and nothing happens, not even the little watch comes out and so I have to reboot it. But when I do, I have to use it non stop doing whatever for about 3 hours or so, not being able to leave it alone because if I do, even for a minute it will freeze all over again and the process will start over.
But also, sometimes when I reboot it, it doesn't being to reboot. It just stays with the screen shut off and eventually the little red light would turn on and off but nothing else will happen. I left it in that state for about 10 hours and nothing.
Right now it has been frozen for almost an hour, Ive had to reboot it about 25times today and I´m beginning to give up and getting scared for my phone.
Can't anyone please help me with a solution or proposition?
Thanks in advance.

Hello AnaVS and welcome to the BlackBerry Support Community Forums.
I would suggest you reinstall your BlackBerry device software. It sounds like something is malfunction causing the rebooting.
Do you have the Desktop Software installed? If not, you can download it at www.blackberry.com/software/desktop
After it is installed, connect your BlackBerry and back up your data.
Once you have backed up, follow the steps in KB11320 to reinstall your BlackBerry device data. Once the reinstall completes, test before restoring ANY data.
If the same thing happens without any data on it, you will want to contact your mobile carrier for further investigation.
-HMthePirate
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Running The Mac Mini Non-stop

Does anyone have experience or an opinion on running the Mac Mini continuously non-stop for long periods of time (e.g. months)? Let's assume that sleep mode is disabled.
How will this affect the reliability of the machine?
I do this to my PC and they seem fine. Just wondering if the Mac Mini will do okay.
Mac Mini Intel Core Duo 1.66GHz; 2 GB RAM; OS X 10.4.6

A few quick items:
1) I agree with all who posted. You should have no problem leaving the Mini on indefinitely.
2) Go to your System Preferences and select the Energy Saving Option (It looks like a light bulb). Check off to turn the Hard Drive off when possible, Select Sleep, Never and set your monitor to power down when you want it to.
3) If you have a broadband internet connection where it is always on, you want to make sure your firewall is up. Go to System Preferences, select Sharing and then select Firewall. Turn it on for your protection. You probably don't need it if you have a router, but just in case.
Good luck!

Why is iPhoto doing this none stop?

My iPhoto does this none stop.
I've restarted.
I've restarted the computer, deleted the plist file and it still does it none stop no matter how long I leave it open.
Is there a quick fix. It started this after I created another library.

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

MacBook Pro- 2011- non-stop KERNAL PANICS.

Hello,
To whom is may concern I have been having non-stop kernal panics attached I have my system info and the report logged when computer boots back up.
below is the problem I'm getting, anything helps sorry for the long error report.
Model Name: MacBook Pro
Model Identif
Anonymous UUID:       B1A33785-89F9-DC2C-9D5A-F487A552831A
Sun Mar 8 11:03:08 2015
panic(cpu 2 caller 0xffffff7f90b4ef7c): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00070000: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff80b6128000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.6.22/src/Apple MuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff80a539a460 : 0xffffff800ea23139
0xffffff80a539a4e0 : 0xffffff7f90b4ef7c
0xffffff80a539a5b0 : 0xffffff7f8f428f1b
0xffffff80a539a670 : 0xffffff7f8f4f250a
0xffffff80a539a6b0 : 0xffffff7f8f673b73
0xffffff80a539a700 : 0xffffff7f8f6e56e0
0xffffff80a539a980 : 0xffffff7f8f6e3fa9
0xffffff80a539ab20 : 0xffffff7f8f4cd58f
0xffffff80a539abb0 : 0xffffff7f8f3ff1b6
0xffffff80a539ace0 : 0xffffff7f8f404eda
0xffffff80a539ada0 : 0xffffff7f8f42d9d7
0xffffff80a539afa0 : 0xffffff7f8f42f4e3
0xffffff80a539b090 : 0xffffff7f903c540c
0xffffff80a539b1d0 : 0xffffff7f903c493f
0xffffff80a539b350 : 0xffffff7f90388058
0xffffff80a539b3b0 : 0xffffff7f903b9cf4
0xffffff80a539b6d0 : 0xffffff7f9036df0d
0xffffff80a539b700 : 0xffffff7f903be970
0xffffff80a539b780 : 0xffffff7f903a6ae0
0xffffff80a539b7e0 : 0xffffff7f903a73da
0xffffff80a539b830 : 0xffffff7f903a78c0
0xffffff80a539b8a0 : 0xffffff7f903a7fc8
0xffffff80a539b8e0 : 0xffffff7f90374fea
0xffffff80a539ba60 : 0xffffff7f903a4940
0xffffff80a539bb20 : 0xffffff7f90373ad9
0xffffff80a539bb70 : 0xffffff800eed07f6
0xffffff80a539bb90 : 0xffffff800eed1df1
0xffffff80a539bbf0 : 0xffffff800eecf85f
0xffffff80a539bd40 : 0xffffff800eab6e18
0xffffff80a539be50 : 0xffffff800ea26d81
0xffffff80a539be80 : 0xffffff800ea13af5
0xffffff80a539bef0 : 0xffffff800ea1e1d3
0xffffff80a539bf70 : 0xffffff800eaca13d
0xffffff80a539bfb0 : 0xffffff800eaf4ca6
      Kernel Extensions in backtrace:
         com.apple.driver.AppleMuxControl(3.6.22)[32862231-50BC-3AF6-87A2-703321AE4F90]@ 0xffffff7f90b40000->0xffffff7f90b53fff
            dependency: com.apple.driver.AppleGraphicsControl(3.6.22)[AA46D551-BE0F-33DA-93A3-8F46197BB 36F]@0xffffff7f90b38000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xfffff f7f8f32e000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f8f0c1000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f8f386000
            dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[80899285-3952-30DA-A0F9-357C51E104 CF]@0xffffff7f90b3b000
         com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f8f3d9000->0xffffff7f8f641fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f8f0c1000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xff ffff7f8f3c9000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f8f386000
         com.apple.nvidia.classic.NVDANV50HalTesla(8.2.4)[B0E6AAA7-E970-3D81-8B43-145D56 A3A4AC]@0xffffff7f8f64c000->0xffffff7f8f8f5fff
            dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f8f3d9000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f8f0c1000
         com.apple.GeForceTesla(8.2.4)[B0074750-2FC6-3E26-BEA0-5AD5469686CF]@0xffffff7f9 0362000->0xffffff7f9042cfff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[2852ACFE-FD28-3C37-9B39-885201BB8D25]@0xffffff 7f8f0c1000
            dependency: com.apple.iokit.IONDRVSupport(2.4.1)[D41125CE-69BD-32E7-9B1D-4E83431662DD]@0xff ffff7f8f3c9000
            dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[75D81741-64C1-3941-ADFA-9D6B6C434EE4]@0 xffffff7f8f386000
            dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[D61B2BB9-4289-318D-9197-5E1E13B 1FF32]@0xffffff7f8f3d9000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13F34
Kernel version:
Darwin Kernel Version 13.4.0: Wed Dec 17 19:05:52 PST 2014; root:xnu-2422.115.10~1/RELEASE_X86_64
Kernel UUID: 45486BF2-BDDE-34CB-8C71-606FF3FE181B
Kernel slide:     0x000000000e800000
Kernel text base: 0xffffff800ea00000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 42834432702
last loaded kext at 42320631572: com.apple.driver.AudioAUUC 1.60 (addr 0xffffff7f90e2e000, size 28672)
loaded kexts:
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleHDAHardwareConfigDriver 2.6.3f4
com.apple.driver.AGPM 100.14.34
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 2.6.3f4
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.driver.AppleIntelHDGraphics 8.2.4
com.apple.GeForceTesla 8.2.4
com.apple.iokit.IOBluetoothUSBDFU 4.2.7f4
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.iokit.IOBluetoothSerialManager 4.2.7f4
com.apple.driver.AppleIntelHDGraphicsFB 8.2.4
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.7f4
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleBacklight 170.4.11
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.nvidia.NVDAStartup 8.2.6
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleMuxControl 3.6.22
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleUSBCardReader 3.4.1
com.apple.driver.AppleIRController 325.7
com.apple.iokit.SCSITaskUserClient 3.6.7
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AppleUSBHub 683.4.0
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.kext.triggers 1.0
com.apple.nvidia.classic.NVDANV50HalTesla 8.2.4
com.apple.nvidia.classic.NVDAResmanTesla 8.2.4
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.7f4
com.apple.iokit.IOBluetoothFamily 4.2.7f4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleGraphicsControl 3.6.22
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.AppleUSBMultitouch 240.10
com.apple.iokit.IOSCSIBlockCommandsDevice 3.6.7
com.apple.iokit.IOUSBMassStorageClass 3.6.0
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.6.7
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.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.7
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IO80211Family 640.36
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 686.4.1
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.2
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.pthread 1

You have the MacBookPro6,2—the Edsel of Macs. It may have the logic-board defect that was covered by a recall program that has now ended.
Residents of the EU may be entitled to warranty service for up to six years after purchase.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider, to have the machine tested. The routine hardware diagnostics used by service providers do not detect the fault. There is a specific test for this issue that Apple calls "VST" (for "Video Switching Test.") Ask for it. A "Failed" result means that the fault is present.
You may be quoted a price of about $300 (in the U.S.) for a "depot repair," which involves shipping the unit to a central repair facility and takes about two weeks. For that flat fee, anything found wrong with it should be fixed, not just the logic board.
Sometimes the replacement part is also defective, so be prepared for that possibility. If you decide to pay for a new logic board, test thoroughly during the 90-day warranty period on the repair. Some owners have reported that they went through as many as three replacement boards before getting one that worked.
If you don't want to pay for the repair, you may (or may not) be able to work around the problem by disabling automatic graphics switching. To use the discrete graphics processor, you'll need a third-party utility to switch to it manually.
Often the problems start after an OS upgrade. If the upgrade was recent, and you have backups, then you can revert to a previous OS X version.

Aperture 3.3 continues to process non-stop

Similar Messages

Maybe you are looking for