8 Messages
•
160 Points
Elements 13: Organizer crashes immediately after launch on Win10 (code 0xc0000005)
My PSE13 (newest update) Organizer crashes immediately after launch (Winlog error code 0xc0000005). I believe it is since my upgrade to Windows 10, but it may be a coincidence.
I have the catalog and the photos saved on an external USB-drive. I think I have tried every suggested solution on the internet, but nothing helped.
I found that when I moved the catalog to the local drive and did not connect the USB-drive, Organizer would not crash and I could browse my catalog, reconnect individual photos in a different storage location, and so on. But as soon as I switch on the USB-drive, Organizer crashes.
Here's what I have tried (some multiple times and in different combinations), all without solving the problem:
- repair and optimize the catalog
- clean install of PSE to a different computer
- delete Organizer preferences and caches
- switch off all media analysis and Movie-thumbnails in the prefs
- delete thumbnail-file from catalog (effect: Organizer launched alright, started creating thumbnails and crashed with the same error at some point in the process)
The only thing I have not tried is a downgrade back to Windows 8, because that's not an option.
What else can I try? How can I find out which photo it is that makes Organizer crash?
Thanks in advance for your help. Any idea or comment is appreciated.
I have the catalog and the photos saved on an external USB-drive. I think I have tried every suggested solution on the internet, but nothing helped.
I found that when I moved the catalog to the local drive and did not connect the USB-drive, Organizer would not crash and I could browse my catalog, reconnect individual photos in a different storage location, and so on. But as soon as I switch on the USB-drive, Organizer crashes.
Here's what I have tried (some multiple times and in different combinations), all without solving the problem:
- repair and optimize the catalog
- clean install of PSE to a different computer
- delete Organizer preferences and caches
- switch off all media analysis and Movie-thumbnails in the prefs
- delete thumbnail-file from catalog (effect: Organizer launched alright, started creating thumbnails and crashed with the same error at some point in the process)
The only thing I have not tried is a downgrade back to Windows 8, because that's not an option.
What else can I try? How can I find out which photo it is that makes Organizer crash?
Thanks in advance for your help. Any idea or comment is appreciated.
Responses
jan_renziehausen
8 Messages
•
160 Points
5 years ago
I have deleted all movie files from the database and checked all file paths and drive letters using SQLite, but still no improvement.
Other observations:
When I use the repair function with re-indexing visual simularity option the program crashes with the same error after 50-60% of re-indexing.
When I delete the thumbnail cache, the program launches at first as described above, but crashes at some point during the thumbnail creation process. I followed the process by scrolling through the pictures as the thumbnail creation progresses, but every time it is a different photo at which the program crashes.
I get the feeling that PSE13 is simply incompatible with Windows 10 or so badly programmed that it is not stable in this environment.
Does anyone have a tip for me what else I can try to make PSE work again?
0
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
0
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
Then suddenly the program crashed again in the midst of tagging my pictures and since then it crashes again immediately at every program start.
I have come to the conclusion that PSE is just a badly programmed piece of crappy software and customers are completely let down with no support at all.
0
0
anwesha
72 Messages
•
1.2K Points
5 years ago
Once you install, reboot the machine and try launching Photoshop Elements again. Let us know if it helps.
Thanks,
Anwesha
0
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
The thing is: Organizer works - as long as I don't import my photos :-(
It seems to me that Organizer has a problem handling the memory under Windows 10.
When I delete the thumbs.cache Organizer works for a while and I can open photos, select tagged groups etc., but eventually when Organizer has created enough thumbnails in the background it crashes.
Exactly the same happens with a new catalogue that I import larger amounts of my photos into or with a catalogue that I restore from my backup.tly (which was obviously created when the catalogue still worked in PSE13 under Win8).
And yes, I have deactivated face recognition and video thumbnails in the preferences.
Please help. What else can I try?
I have created the dumps in C:\dumpstore, if that's any help to bring more light into this.
1
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
I have even used SQLitebrowser to manually delete all video entries from the catalog - still it crashes.
I think, EO either crashes on a faulty pic (which EO should really be able to stomach) or on the size of the cache itself.
0
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
"Optimize" catalog finishes also without an error report or crash.
Still EO crashes as soon as I open the catalog.
I'm really at a loss what to do with this. I have spent hundreds of hours tagging my photos and recognizing all the faces - that cannot be all wasted!
0
0
jan_renziehausen
8 Messages
•
160 Points
5 years ago
A bloody tif that any other program on my PC opens without a problem made PSE crash immediatly when the Organizer tried to create a thumbnail. Organizer never gave a hint what the problem was. Not only that the program is apparently pretty unstable, it neither gives any help in finding what the problems are. So it took me ages and third-party programs to finally find a clue that a single pic was the problem :-(
1
robert_kip
5 Messages
•
120 Points
5 years ago
REALLY unhappy with Adobe, though. Their reputation as producers of expensive, system hogging, buggy, crash prone programs to be avoided is deserved. What I'm seeing here is that many folks with substantial competencies that extend beyond their photographic interests into the bowels of their computers and systems - mine are limited - are frustrated. The best the Adobe folks have to offer is an occasional "suggestion" accompanied by a request to let them know if it worked. Not good.
3
0