Strange crash with photos from Picassa

I came across a problem today that I can't explain. When I download photos from a specific site on picassa and each time i imported them into iphoto it crashed. I received the same photo from the person who put the photos up and it was fine but when I downloaded the photo onto my desktop from Picassa and then dropped onto iphoto it crashed. when i resized the photo in photoshop and saved it it was fine and when i imported a different file, a large tiff file that was fine.
I'll post a part of the crash log if anyone can see something I can't.
Thanks
Command: iPhoto
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Parent: WindowServer [62]
Version: 6.0.5 (6.0.5)
Build Version: 2
Project Name: iPhotoProject
Source Version: 3160000
PID: 355
Thread: 9
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x0000000c
Thread 0:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.HIToolbox 0x93208740 RunCurrentEventLoopInMode + 264
5 com.apple.HIToolbox 0x93207dd4 ReceiveNextEventCommon + 380
6 com.apple.HIToolbox 0x93207c40 BlockUntilNextEventMatchingListInMode + 96
7 com.apple.AppKit 0x936eaae4 _DPSNextEvent + 384
8 com.apple.AppKit 0x936ea7a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
9 com.apple.AppKit 0x936e6cec -[NSApplication run] + 472
10 com.apple.AppKit 0x937d787c NSApplicationMain + 452
11 com.apple.iPhoto 0x0000b05c 0x1000 + 41052
12 com.apple.iPhoto 0x0000af04 0x1000 + 40708
Thread 1:
0 libSystem.B.dylib 0x90049ea8 syscallthreadswitch + 8
1 com.apple.Foundation 0x929795d0 +[NSThread sleepUntilDate:] + 152
2 com.apple.AppKit 0x93787a10 -[NSUIHeartBeat _heartBeatThread:] + 1100
3 com.apple.Foundation 0x92961194 forkThreadForFunction + 108
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x9005b660 accept + 12
1 com.apple.iPhoto 0x001e309c 0x1000 + 1974428
2 com.apple.iPhoto 0x0022f080 0x1000 + 2285696
3 com.apple.iPhoto 0x0022f114 0x1000 + 2285844
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x9001f08c select + 12
1 com.apple.CoreFoundation 0x907ef40c __CFSocketManager + 472
2 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf5500 TSWaitOnSemaphoreCommon + 176
3 ...ickTimeComponents.component 0x98b817c4 ReadSchedulerThreadEntryPoint + 5300
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x9002bbc8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x900306ac pthreadcondwait + 480
2 com.apple.iPhoto 0x001efa50 0x1000 + 2026064
3 com.apple.iPhoto 0x0021b64c 0x1000 + 2205260
4 com.apple.iPhoto 0x000cbe38 0x1000 + 831032
5 com.apple.iPhoto 0x000cfc90 0x1000 + 846992
6 ...ple.CoreServices.CarbonCore 0x90bf763c InvokeDeferredTaskUPP + 24
7 com.apple.iPhoto 0x0021b390 0x1000 + 2204560
8 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 6:
0 libSystem.B.dylib 0x9002bbc8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x900306ac pthreadcondwait + 480
2 com.apple.iPhoto 0x00219fb8 0x1000 + 2199480
3 com.apple.iPhoto 0x001ef380 0x1000 + 2024320
4 com.apple.iPhoto 0x001ef4c8 0x1000 + 2024648
5 com.apple.iPhoto 0x0021b31c 0x1000 + 2204444
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 7:
0 libSystem.B.dylib 0x9002bbc8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x900306ac pthreadcondwait + 480
2 com.apple.iPhoto 0x00219fb8 0x1000 + 2199480
3 com.apple.iPhoto 0x001ef380 0x1000 + 2024320
4 com.apple.iPhoto 0x001ef4c8 0x1000 + 2024648
5 com.apple.iPhoto 0x0021b31c 0x1000 + 2204444
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 8:
0 libSystem.B.dylib 0x9002bbc8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x900306ac pthreadcondwait + 480
2 com.apple.iPhoto 0x00219fb8 0x1000 + 2199480
3 com.apple.iPhoto 0x001ef380 0x1000 + 2024320
4 com.apple.iPhoto 0x001ef4c8 0x1000 + 2024648
5 com.apple.iPhoto 0x0021b31c 0x1000 + 2204444
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 9 Crashed:
0 com.apple.ColorSync 0x91550f34 CheckValidProfile + 16
1 com.apple.ColorSync 0x91551d94 CMCloseProfile + 24
2 com.apple.iPhoto 0x001a200c 0x1000 + 1708044
3 com.apple.iPhoto 0x001a2498 0x1000 + 1709208
4 com.apple.iPhoto 0x0012dfbc 0x1000 + 1232828
5 com.apple.iPhoto 0x000cfa60 0x1000 + 846432
6 ...ple.CoreServices.CarbonCore 0x90bf763c InvokeDeferredTaskUPP + 24
7 com.apple.iPhoto 0x0021b390 0x1000 + 2204560
8 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 10:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x90bf5500 TSWaitOnSemaphoreCommon + 176
3 ...ple.CoreServices.CarbonCore 0x90bfffa8 AIOFileThread(void*) + 520
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 9 crashed with PPC Thread State 64:
srr0: 0x0000000091550f34 srr1: 0x000000000200f030 vrsave: 0x0000000000000000
cr: 0x24422444 xer: 0x0000000020000003 lr: 0x0000000091551d94 ctr: 0x0000000091551d7c
r0: 0x0000000000000000 r1: 0x00000000f01928b0 r2: 0x00000000a474ff1c r3: 0x0000000000000004
r4: 0x0000000000000048 r5: 0x000000000000008c r6: 0x00000000ffffffff r7: 0x0000000000000002
r8: 0x0000000000000000 r9: 0x0000000000000001 r10: 0x000000009474d970 r11: 0x000000000046af30
r12: 0x0000000091551d7c r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000024420422 r17: 0x00000000004a0000 r18: 0x00000000004a0000 r19: 0x0000000005021eb0
r20: 0x00000000063246c0 r21: 0x00000000070c6e30 r22: 0x0000000000000000 r23: 0x0000000005022ba0
r24: 0x0000000006359710 r25: 0x00000000050200d0 r26: 0x0000000000000006 r27: 0x0000000000000001
r28: 0x0000000000000000 r29: 0x00000000007315e8 r30: 0x0000000000000004 r31: 0x0000000000731614

Derek
This looks like a version of the Color Profile bug that afflicts iPhoto since the last update to it and Quicktime.
The crash is at thread 9
Thread 9 Crashed:
0 com.apple.ColorSync 0x91550f34 CheckValidProfile + 16
1 com.apple.ColorSync 0x91551d94 CMCloseProfile + 24
This thread
http://discussions.apple.com/thread.jspa?messageID=3450321&#3450321
Has a link to Mr. Old Toad's script that will embed the correct colour profile on the file/s.
Regards
TD

Similar Messages

Imovie crashes with photos from Iphoto

I recently purchased a mac computer with the latest software. I wanted to import photos from my Iphoto library into Imovie and make a movie. Each time I try to do so Imovie crashes.
The first time I had the error and the first time I used Imovie, here is what I did:
1. I opened Imovie
2. Clicked on "show or hide photo browser"(the camera icon on the right).
3. It said it had to create a thumbnail for videos in Iphoto library and did so.
4. I clicked on the photos to scroll through them.
5. After looking at a few photos, Imovie crashed.
All other times I had an error here is what happened:
1. I opened Imovie
2. clicked on "show or hide photo browser"(the camera icon on the right).
3. Imovie crashes.
If anyone has any thought on what is going on and how to fix this problem please post, Thanks.

love tapas
http://docs.info.apple.com/article.html?artnum=93277
Regards
TD

Can you link Photos from Picassa to the iPod?

I want to get an iPod for a friend who uses a PC and Picassa to organize her photos. Will the iPod easily recognize Picassa and copy the photos to the iPod, or would she have to somehow move the photos from Picassa to the iPod?
Thank you

Nope, Picassa won't recognize an iPod, and you cannot sync from Picassa directly to the iPod.
As long as they know where the picture files are on their computer, they can put them on through iTunes, though. They just choose the folder with the pictures on it, and all pictures in the folder will go to the iPod.

When I send emails with photos from iPhoto recipients often tell me images are upside down. What would cause that?

When I send emails with photos from iPhoto recipients often tell me images are upside down. What would cause that?

Found this :
https://discussions.apple.com/thread/3431867?start=0&tstart=0
by doing this :
http://www.google.com/search?q=images+are+upside+down+ios

Import contact with photo from google

How Do I import contact with photos from google to iCloud?
I uses iPhone6 , 6+ , iPad Air all iOS8.1 and Mac Air Yosemite
I uses google contact with photo all but I need to export all contacts to iCloud but after I imported the photo not have any more. How should I do to import all contact with photo from google?

The thumbnailPhoto attribute is for an octet string, so I can see why that would not work as it should be essentially a byte array (or a binary blob holding the JPG/GIF), and that is what is expected when importing that attribute.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to erase an album with from my iPhone with photos from my Mac that I happened to erase from the Mac already. When typing edit the three bars appearing in grey and do not respond. Txs.

How to erase an album in my iPhone with photos from my Mac that I happened to erase from the Mac already. When typing edit the three bars appear
in grey and do not respond. Txs.

Not sure if it will help but if you had registered it with Apple you could try unregistering it. To do this:
Go to: https://supportprofile.apple.com/MySupportProfile.do
Log in if not already logged in.
Click on ">" to the right of the device you want to unregister
Click "unregister"

IPhoto Crashes with Photo Booth Share

Brand new iMac (less than 2 weeks old) running Lion.
My daughter is having lots of fun with Photo Booth, but whenever we try to "share" (add to iPhoto), iPhoto opens and then promptly crashes.
After that, whenever we try to open iPhoto directly, it says there's a photo that needs to be imported. Regardless of whether I say yes or no to importing the image, iPhoto crashes.
After each crash, a new recovered file folder appears in my pictures directory.
I did figure out how to get iPhoto to work again by finding and removing the Photo Booth file that is trying to be imported. But I was hoping someone could give me a heads up as to why brand new software on a brand new computer isn't working and whether there is a fix.
Thanks.

The fact that a computer is "brand new" doesn't make a whit of difference. Software doesn't suffer from wear and tear and problems are as likely on the first day you use it as they are on the last.
As to the fix... you say you did fix the problem and can get iPhoto to work, didn't you?

Ipad won't sync with photos from Aperture - library cannot be found

Ok I give up. When trying to sync my photos onto my new ipad from Aperture in iTunes I keep getting the message "iTunes cannot sync photos to the ipad because your Aperture Library could not be found. Open the preferences window in Aperture and enable the preference to share previews with other applications. Well the library is where it should be in the Home folder and then pictures. I have the latest version of iTunes and Aperture. The only similar setting I can find in Aperture preferences is under Previews and Share Previews with ilife and iwork, no mention of itunes?
I've gone into my Aperture show contents and deleted the cache folder ipod photo cache (I previously synced to my iphone 3GS). It works syncing to iphoto, as I have tested it and the iphoto is in the same folder as the Aperture library so they are in the right location.
I am now at a loss as to what to try next......PLEASE HELP ME....
I don't want to have to have a Aperture library and an iphoto library on the go!

Hi,
iTunes cannot sync photos to the ipad because your Aperture Library could not be found.
If you have an external drive connected to your Mac, disconnect that, restart your Mac, restart your iPad and try syncing photos from Aperture.
Carolyn

Updating my ipod nano with photos from itune

I have been facing an error ("The ipod cannot be update. the disk could not be read from or written to")when I try to update photos from itunes to the ipod nano.
Although I have been updating music successfully and using the last version of itunes (6) and ipod software it persists with this error.
Do you have any hint to give me ?

Restore the iPod and then see this article for different ways to sync content to your iPod when your iTunes library is larger than what your iPod can hold.
http://support.apple.com/kb/HT1204
B-rock

Strange crash with Intel FFT in Windows XP x64: only when first starting LabVIEW and opening VI, not when opening VI by double-clicking

When I use the Intel FFT libraries(MKL), I seem to have a strange crash whenever I start allocating the Intel DFTI descriptors. I call a DLL from LabVIEW 8.2.1, in which these functions are used. I am working on Windows XP x64. This seems like a bug which was present in these libraries, but I got the libraries where the bug was resolved.
The strange things is that, when I open LabVIEW and then open the VI, LabVIEW crashes from the moment I allocate an Intel Dfti descriptor. But when I just double-click the VI and open it this way, I can run the VI without a crash! I already removed the DLLs in \Program Files (x86)\National Instruments\Shared\MKL\MKL70 to see if they were the cause. But even without them, I still get the crash.
I know there was a strange crash in the previous version of Intel MKL when calling a DLL and allocating this type of descriptor, so it seems like somewhere LabVIEW still uses old versions of some of these DLLs. But even then, can this explain the difference in behaviour between opening the VI through LabVIEW or directly? And if so, were could I find these DLLs? I've already searched from them everywhere.

Update:
- Opening the single VIs directly by double-clicking indeed solves the crash: from then on I can run all VIs using the libraries without any problem. So LabVIEW must do something strange when it is opened.
- Linking my DLLs statically against the Intel libraries ALSO solves the prolbem. So this seems to indicate LabVIEW loads some dynamic library which screws up everything. But only on x64 systems . This bloats my DLL, but currently I do not see another work-around.
Anyone has any more ideas? Otherwise I can always submit some test case to LabVIEW support.

IPhoto 9.3 crashes opening photos from Shared library

Accessing photos from a Shared library - open 1 or 2 photos and crash - everytime on multiple machines.
Report looks like this:
Process:         iPhoto [73851]
Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:      com.apple.iPhoto
Version:         9.3 (9.3)
Build Info:      iPhotoProject-650039000000000~2
App Item ID:     408981381
App External ID: 7636641
Code Type:       X86 (Native)
Parent Process: launchd [127]
Date/Time:       2012-06-20 08:44:09.029 +1200
OS Version:      Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report:          79945 sec
Crashes Since Last Report:           9
Per-App Interval Since Last Report: 1477 sec
Per-App Crashes Since Last Report:   8
Anonymous UUID:                      XXXXXXXXXXXXXXXXXXXXXXXX
Crashed Thread: 36
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x00000000212e8000
VM Regions Near 0x212e8000:
    IOKit                  00000000210e8000-00000000212e8000 [ 2048K] rw-/rw- SM=SHM
--> mapped file            00000000212e8000-000000002177e000 [ 4696K] r--/rwx SM=COW /private/var/folders/*/*.jpg
    IOKit                  0000000021dcf000-000000002298a000 [ 11.7M] rw-/rw- SM=ALI
Application Specific Information:
objc[73851]: garbage collection is OFF
Thread 0:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation                0x9bf86c7b __CFStringHash + 683
1   com.apple.CoreFoundation                0x9bfb6534 __CFRunLoopModeHash + 20
2   com.apple.CoreFoundation                0x9bf8c9f0 __CFSetStandardHashKey + 32
3   com.apple.CoreFoundation                0x9bf7d12f CFBasicHashFindBucket + 1679
4   com.apple.CoreFoundation                0x9bfa71f7 CFSetGetValue + 135
5   com.apple.CoreFoundation                0x9bfb6357 __CFRunLoopFindMode + 183
6   com.apple.CoreFoundation                0x9bfd7f56 __CFRunLoopDoTimer + 1542
7   com.apple.CoreFoundation                0x9bfb6cd0 __CFRunLoopRun + 1888
8   com.apple.CoreFoundation                0x9bfb61dc CFRunLoopRunSpecific + 332
9   com.apple.CoreFoundation                0x9bfb6088 CFRunLoopRunInMode + 120
10 com.apple.HIToolbox                     0x916fd723 RunCurrentEventLoopInMode + 318
11 com.apple.HIToolbox                     0x91704a8b ReceiveNextEventCommon + 381
12 com.apple.HIToolbox                     0x917048fa BlockUntilNextEventMatchingListInMode + 88
13 com.apple.AppKit                        0x94cb30d8 _DPSNextEvent + 678
14 com.apple.AppKit                        0x94cb2942 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
15 com.apple.AppKit                        0x94caecb1 -[NSApplication run] + 911
16 com.apple.AppKit                        0x94f3fbd9 NSApplicationMain + 1054
17 com.apple.iPhoto                        0x000108c6 0x1000 + 63686
18 com.apple.iPhoto                        0x0000fd99 0x1000 + 60825
Any ideas?

It says Crashed Thread 36, below. Looks like a nasty bug...
0   libsystem_c.dylib
0x965db06c memmove$VARIANT$sse3x + 1198
1   com.apple.ImageIO.framework
0x9b8368c3 CGImageReadGetBytesAtOffset + 857
2   com.apple.ImageIO.framework
0x9b83655c CGImageReadSessionGetBytes + 47
3   com.apple.ImageIO.framework
0x9b836437 fill_input_buffer + 223
4   libJPEG.dylib
0x9ba8ef1a decode_mcu_optimized + 2748
5   libJPEG.dylib
0x9ba8e2c9 decompress_onepass + 174
6   libJPEG.dylib
0x9ba8e1bc process_data_simple_main + 43
7   libJPEG.dylib
0x9ba8e186 _cg_jpeg_read_scanlines + 154
8   com.apple.ImageIO.framework
0x9b83a7ac copyImageBlockSetJPEG + 2807
9   com.apple.ImageIO.framework
0x9b839bee ImageProviderCopyImageBlockSetCallback + 440
10 com.apple.CoreGraphics
0x9049f284 CGImageProviderCopyImageBlockSetWithOptions + 173
11 com.apple.CoreGraphics
0x9049f1d1 CGImageProviderCopyImageBlockSet + 69
12 com.apple.CoreGraphics
0x9049ed34 img_blocks_create + 332
13 com.apple.CoreGraphics
0x90416b3a img_decode_stage + 376
14 com.apple.CoreGraphics
0x90415234 img_data_lock + 5022
15 com.apple.CoreGraphics
0x9049e148 CGSImageDataLock + 165
16 libRIP.A.dylib
0x9b67e62d ripc_AcquireImage + 1901
17 libRIP.A.dylib
0x9b67ce7f ripc_DrawImage + 951
18 com.apple.CoreGraphics
0x9049dd41 CGContextDrawImage + 457
19 com.apple.iPhoto
0x000a2c31 0x1000 + 662577
20 com.apple.iPhoto
0x003c370f 0x1000 + 3942159
21 com.apple.iPhoto
0x0031012f 0x1000 + 3207471
22 com.apple.iPhoto
0x0030d14a 0x1000 + 3195210
23 com.apple.iPhoto
0x0030fb4c 0x1000 + 3205964
24 com.apple.iPhoto
0x00516683 0x1000 + 5330563
25 com.apple.CoreFoundation
0x9c015d11 -[NSObject performSelector:withObject:] + 65
26 com.apple.proxtcore
0x0177f336 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166
27 com.apple.CoreFoundation
0x9c015d11 -[NSObject performSelector:withObject:] + 65
28 com.apple.proxtcore
0x01776ee5 -[XTSubscription postMessage:] + 181
29 com.apple.proxtcore
0x01776636 -[XTDistributor distributeMessage:] + 726
30 com.apple.proxtcore
0x01776177 -[XTThread handleMessage:] + 1255
31 com.apple.proxtcore
0x01774916 -[XTThread run:] + 438
32 com.apple.Foundation
0x9b2e9e25 -[NSThread main] + 45
33 com.apple.Foundation
0x9b2e9dd5 __NSThread__main__ + 1582
34 libsystem_c.dylib
0x96602ed9 _pthread_start + 335
35 libsystem_c.dylib
0x966066de thread_start + 34

Strange behavior with images from iPhone

I'm wondering if anyone else has seen this behavior or can replicate.
Take some pictures using an iPhone 3Gs (can't tell if it happens with other models).
Bring the images into iPhoto and then drag them out to regular folders.
Choose Cmd/Ctrl-D to place.
The image, which is in Portrait orientation, comes into CS5 strangely.
The frame does not hug the correct orientation of the image. Instead it follows a landscape orientation as if the image was rotated 90 degrees.
When you let go from dragging the frame, the image appears vertical within the lanscape frame.
The only way to get the frame any way close to the vertical orientation is to hold the Shift key.
I have also noticed that these images are added to a video editing program rotated into a landscape mode.

There's no such thing as a vertical or horizontal image with iPhones or any phone that sports and accelerometer. It's just a tag they add to images that is inconsistently supported. All photos are landscape, just some are tagged to indicate they are portrait. It's like when I was growing up I always thought my dad was Superman only to later find out he was just a drunk wearing a cape.
If you want to just pull the images directly off the phone or just a generally nice thing for your iPhone/Pod/Pad you can get PhoneDisk. Costs nothing and works great other than my minor user interface complaint that they take advantage of the menubar's menuextras area that is supposed to be Apple only and hardware only at that. Human Interface Guidelines aside, it is a really nice utility.
http://www.macroplant.com/phonedisk/

Windows 8.1 Crashes with Dumps from desktop

I have experienced a number of crashes on a PC with Windows 8.1, and have analyzed the mini dumps and one full dump so far, and have seen a myriad of different crash results including IRQL_NOT_LESS_OR_EQUAL, KERNEL_DATA_INPAGE_ERROR, CRITICAL_PROCESS_DIED.
I've posted the raw dmp files, as well as txt files of the results from running them through the debugger here...
https://onedrive.live.com/redir?resid=F1640CE12DEBCE6B!130&authkey=!ABlrD4zyv8gT_SU&ithint=folder%2ctxt
I've ran memtest86 very thoroughly on the RAM with 0 errors, I've updated all of the drivers, ran chkdsk on the HDD, and cannot find any glaring errors, and the computer still seems to crash at random points in time with different applications running each
time. The computer is a custom build if the components matter, and each of the component can be found here...
http://pcpartpicker.com/p/zfmYqs

TTD
There is a very specific problem. The HD. I would go the HD maker and download their HD checking utility and run it
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\022015-12359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is:
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff800`5ba06000 PsLoadedModuleList = 0xfffff800`5bcdf250
Debug session time: Fri Feb 20 22:11:14.919 2015 (UTC - 5:00)
System Uptime: 0 days 23:53:22.598
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb400a1f28, ffffffffc000000e, 10d7b1880, fffff680143e5000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1561f )
Followup: MachineOwner
3: kd> !analyze -v
* Bugcheck Analysis *
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb400a1f28, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000010d7b1880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff680143e5000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000000e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8005bb7c4cf to fffff8005bb569a0
STACK_TEXT:
ffffd000`309d63e8 fffff800`5bb7c4cf : 00000000`0000007a fffff6fb`400a1f28 ffffffff`c000000e 00000001`0d7b1880 : nt!KeBugCheckEx
ffffd000`309d63f0 fffff800`5ba377f8 : 00000000`00000002 ffffd000`309d6558 ffffe001`d859cdd8 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1561f
ffffd000`309d64e0 fffff800`5ba70b7a : ffffe001`d859cdd8 ffffe001`d8385880 01000000`00000001 00000000`00000000 : nt!MiIssueHardFault+0x184
ffffd000`309d65a0 fffff800`5ba67941 : 01000000`00000001 00000000`00000080 fffff680`143e5000 00000000`00000080 : nt!MmAccessFault+0x5ba
ffffd000`309d6760 fffff800`5c0076f1 : ffffe001`d838eb00 00000028`00000000 ffffd000`00000000 00000000`00000004 : nt!MiCommitExistingVad+0x901
ffffd000`309d6890 fffff800`5bb621b3 : 00000028`6fd1e7a0 00000000`00044000 00000028`6f323878 00000000`00043ff0 : nt!NtAllocateVirtualMemory+0xfbd
ffffd000`309d6a90 00007ffb`db9b0f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000028`6fd1d5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`db9b0f5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1561f
fffff800`5bb7c4cf cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1561f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b0c2f7
IMAGE_VERSION: 6.3.9600.17630
BUCKET_ID_FUNC_OFFSET: 1561f
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7a_c000000e_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {5654bc57-9720-546c-de0e-76a002c66fe5}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

How do I create a new library in LR5 with photos from LR3 and older computer?

I want to take photos I originally imported with LR3 on an older computer and creat a new library in LR5 on my new computer. I want to throw out all old metadata, folder names and keywords and start from scratch. How would I go about this. My photo library is on an external drive. Thanks.

I guess I hadn't thought about the fact I'd lose my edits. I have just a little experience with LR. I've realized that I did not organize and cateorize my photos in a useful way when I first created the library and want to start over. Perhaps I should just plug my photo drive into my new computer and go through photo by photo resorting them and reentering keywords and folder names. If you have any suggestions on how to best to this, I'd appreciate it. Thanks.

Best way to deal with photos from the start? (Bridge CS5 and iPhoto)

Hi all,
I'm just learning the ropes of the whole CS5 suite, and was starting to add keywords etc. in Bridge when I realized I couldn't access the files in my iPhoto ('09) library. I've read a few threads about this issue, but haven't really found a consensus on how to deal with it.
I figure I'm in a good position to get things right from the start since I have no tags or ratings etc. in my iPhoto setup (and have only added keywords to the few pics that weren't in my iPhoto Library), and am wondering what you think is the best way to sort photos given I plan on using them in web design etc., and all the parts of my CS5 suite.
If getting the photos out of iPhoto is best what's the best way to do that? I've read suggestions to right click on the library and click on "Show Contents"- or something like that, but that does not come up as an option when I right click my iPhoto Library in Bridge. Thanks so much for your help!
Please let me know if there is any info I could give you that would be helpful in order to figure this one out.
Best,
Mara

I must be far too lazy to be sure. In iPhoto if I want to move an image all I
do is click and drag from iPhoto to the desktop.
Here comes the trouble with using iPhoto and mixing applications. You have
to be sure what you do in iPhoto because you easily grab the wrong version
instead of the original.
As Tai Lao pointed out the the difference between Bridge and iPhoto in short
is open visible structure for Bridge and hidden invisible library for
iPhoto.
There may be perfect and valid reason to use iPhoto but mixing the two
workflows without thinking or knowing what you do is bound to get you sooner
or later in trouble with wrong versions of the file.
And clicking and dragging from iPhoto is easy to mistake in those versions.
1 - I used to create incredible folder/sub-folder arrangements depending upon
operating system file management to find files.
You can create whatever structure you want including a thought through
naming convention that suites your needs, if you keep doing this in Bridge
you can easily open and close folders using the folder panel, in iPhoto you
have a lot of events and albums but none as clear as in Bridge. (at least
that is my opinion...)
Also I would prefer to use a good naming convention with less folders and
subfolders instead of bad file naming and many well named folders. Also
using the metadata options description and keywords let's you easily find
the files you want but when having the need to retrieve the original from an
external disk or DVD using less folders will be quicker to find.
Since depending upon metadata keywords or star ratings I now prefer to have
all images (originals and amended) in one single folder as Bridge (or iPhoto
for that matter) can only see the images in the folder it is looking at.
Wrong, using the find option (cmd+F) you can specify Bridge to look in main
folders or entire disk, include the option to look in subfolders and you are
in business (but the first time Bridge caches it also need to index all the
metadata, that takes some time but only the first time.
2 - potential feature request for Bridge?
To have an option where Bridge can see and display images in subfolder
arrangements from the folder it is looking at.
That is already there since a view versions
Select a folder with subfolders and then from the menu view select 'show
items for subfolders'
It is still not a perfect way of functioning but it gets better every new
version, in CS5 the speed of gathering the files is very much improved.
However here is iPhoto the winner because it keeps the files in cache (or
something like that) Bridge is not the best in this behavior but it is
possible to use.
This is a bit like a restriction of OS X "All images" to all images in the
selected folder and all subfolders of the selected folder (if that makes any
sense at all)
Many users have tons of files on there system, why would you use that option
to view all if you are perfectly capable of finding the files or file types
you want in most applications (but you can also find them in OSX, you want
psd files do a search for ".psd" and you will see all the psd files on your
system.
3 - iPhoto can't really handle large files. With one event consisting of
4,500+ images weighing in at 884 MB it is zippy. Were those to be originals
at a high resolution iPhoto would probably be tediously slow and require a
folder/sub-folder arrangement which, to me, seems to undermine the importance
of managing stuff using keywords.
IPhoto is not designed to be a professional application, therefore you can't
expect behavior for this
In Bridge you have no limit of files on your system only the limit for the
cache is somewhere around 500.000 I believe. But even Bridge is not really
designed for handling that amount of files in a pleasant way.
I also don't know of an application that can do so for normal retail prices,
most users of that amount of files have custom made or customized
application that costs many thousands dollars. Bridge is in fact a free gift
when buying a Suite application from Adobe.
The file size for viewing in Bridge is by default set to a max of 1 GB but
that is for building previews you can see thumbs and small previews of
bigger files. In the Bridge preferences you can set the limit for this to
whatever you want, it only grows the cache file for previews when using many
large files.
In summary: Bridge is great for CS5 partnering on metadata, original images or
large filesizes.
I couldn't agree more!
iPhoto is great on sharing images across devices and better
still if those files are low res with small filesizes?
I couldn't disagree more...
You can do all of this using Bridge to start own created actions or with
scripts like image processor.
Do some research on Adobe TV or view other video tutorials on the web, there
are many free and good tutorials. You will learn that you can do all you
want in Bridge (and a lot more...)

Strange crash with photos from Picassa

Similar Messages

Maybe you are looking for