Crashing at the end of processing
Hi,
has anyone else experienced a problem with C1 crashing when it reaches the end of processing an image? This is happening more and more and at the moment around 40% of the time I can't process the files without a crash. The process bar gets to 99% and then I get an application error and windows tells me it's closing C1.
Any ideas?
has anyone else experienced a problem with C1 crashing when it reaches the end of processing an image? This is happening more and more and at the moment around 40% of the time I can't process the files without a crash. The process bar gets to 99% and then I get an application error and windows tells me it's closing C1.
Any ideas?
0
-
FWIW, as a quick answer from another user...when this happened to me it was due to not enough free space on the targeted Develops folder harddrive. ...check your drive under system tools and see if the drive needs a defrag (I'll bet it does...also check the drive you have the Previews on)...hope that helps, if not respond so the official cavalry can answer. 0 -
Thanks for the suggestions but the drive has 30gb or so free - same drive for the app and the photos. Windows says it doesn't need a defrag and I've checked it for errors inc. surface scan.
☹️0 -
ataa60,
Could this be a RAM issue... How much do you have?
Do you have the image set to open in Photoshop post develop?
Also consider where the files are located and the Process to location.
If all on local C:\\ do you get an error/crash?
If to Network is there FireWall or AntiVirus software enabled?
If to an External Hard Drive does User have Read&Write Permissions?
Hope this helps some.
Sincerely,
kc0 -
[quote="Keith Carpenter" wrote:
ataa60,
Could this be a RAM issue... How much do you have?
768mb so I doubt it.[quote="Keith Carpenter" wrote:
Do you have the image set to open in Photoshop post develop?
No, post developing I've not set anything to happen.[quote="Keith Carpenter" wrote:
Also consider where the files are located and the Process to location.
If all on local C:\\ do you get an error/crash?
If to Network is there FireWall or AntiVirus software enabled?
If to an External Hard Drive does User have Read&Write Permissions?
Originally C1 was installed on my C: drive and I was processing to my E: drive. I tried processing to the C: drive and it made no difference. I then uninstalled and installed to the E: drive, still no difference.
No network drives involved, no external drives, logged in as admin.
The crashing seems to be worse on certain images. If I get one that crashes I can sometimes change a value and it will process ok.
I have a feeling that some setting has been corrupted somehow and maybe it wasn't cleaned out during uninstall - the crashing just started after processing hundreds of images without incident. I looked at Event Viewer and then checked all new files on the system since the date of the first crash but nothing new worthy of a mention, just data files.0 -
ataa60,
If not using Photoshop launch post-processing and no other software is operating in the background, then I agree that your RAM seems sufficient. We state a minimum of 512 RAM but Recommend 1 GB of RAM.
One attempt to try is the deletion of the .fld file located in the Preferences folder.
C:\\Program Files\\Phase One\\Capture One LE\\Preferences and within this location is the FoldersList.fld file. With software shutdown, delete this file and then relaunch.
A Refresh of the FoldersList.fld file is a list of Process to drives and locations. Deleting it and letting it rebuild or refresh may be a solution here since your changed form C: to E:
Lastly, I will suggest a complete uninstall and clean install of Capture One. Use the default location on the C: drive for the install and for the Preview Cache as well.
Also, the best advice to offer is to Keep It Simple.
The best setting to have established at the Process tab is to the Set Process Folder… and check the Always process images to associated image folder With this box checked, a folder named Develops is created within the Session folder along with the RAW images.
Set-up the software in this manner and process some images to see if there is any improvement.
If problems continue, a test of your RAM module may be in order.
See Knowledge Base Article # 1665 on a complete uninstall of the software:
http://support.phaseone.com/KB/Home/Sea ... nguageID=1
Hope this helps you out.
Sincerely,
kc0 -
Keith,
I tried all the suggestions above but without luck.
Further testing shows that the crash always happens at 99% of the last file being processed in a batch, no matter how many files are in the batch.
I've tested my memory using MemTest86 and it passed all the tests.
Below is a section from the DrWatson logs. The crash always shows a c0000005 access violation error.*----> State Dump for Thread Id 0x6d8 <----*
eax=07a7a820 ebx=0320bee4 ecx=0528bfb4 edx=0000006d esi=0000002e edi=075e0167
eip=0059df29 esp=0320b628 ebp=0320b6ac iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206
*** WARNING: Unable to verify checksum for C:\\Program Files\\Phase One\\Capture One LE\\CaptureOne.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\\Program Files\\Phase One\\Capture One LE\\CaptureOne.exe
function: CaptureOne
0059df0b 7424 jz CaptureOne+0x19df31 (0059df31)
0059df0d 44 inc esp
0059df0e dd0508277700 fld qword ptr [CaptureOne+0x372708 (00772708)]
0059df14 8b44246c mov eax,[esp+0x6c]
0059df18 8b7008 mov esi,[eax+0x8]
0059df1b 85f6 test esi,esi
0059df1d 0f8491000000 je CaptureOne+0x19dfb4 (0059dfb4)
0059df23 dddc fstp st(4)
0059df25 ddd9 fstp st(1)
0059df27 ddd9 fstp st(1)
FAULT ->0059df29 dd0508277700 fld qword ptr [CaptureOne+0x372708 (00772708)] ds:0023:00772708=0000000000000000
0059df2f dd0508277700 fld qword ptr [CaptureOne+0x372708 (00772708)]
0059df35 dd0508277700 fld qword ptr [CaptureOne+0x372708 (00772708)]
0059df3b 8b580c mov ebx,[eax+0xc]
0059df3e b800000000 mov eax,0x0
0059df43 d9cb fxch st(3)
0059df45 d9c9 fxch st(1)
0059df47 d9ca fxch st(2)
0059df49 d9cc fxch st(4)
0059df4b 7e67 jle CaptureOne+0x19dfb4 (0059dfb4)
0059df4d 8974245c mov [esp+0x5c],esi
*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
ChildEBP RetAddr Args to Child
0320b6ac 00471f65 015e9f08 032ce720 77fa6f2f CaptureOne+0x19df29
00000003 00000000 00000000 00000000 00000000 CaptureOne+0x71f65
*----> Raw Stack Dump <----*
000000000320b628 78 00 22 7c 0e a4 16 7c - 00 00 00 00 20 00 01 00 x.\"|...|.... ...
000000000320b638 08 00 00 00 98 b5 20 03 - 00 00 00 00 8c b6 20 03 ...... ....... .
000000000320b648 7f 02 90 7c 70 05 91 7c - 7f 0e 00 00 6d 05 91 7c ...|p..|....m..|
000000000320b658 16 00 00 00 00 00 5e 01 - 25 00 00 00 8f 21 34 7c ......^.%....!4|
000000000320b668 65 66 01 00 77 00 00 00 - 03 03 00 00 aa 00 00 00 ef..w...........
000000000320b678 e4 be 20 03 b1 bf 28 05 - 6c 00 00 00 2e 00 00 00 .. ...(.l.......
000000000320b688 e4 b6 20 03 e5 ff 17 00 - 01 01 00 00 20 a8 a7 07 .. ......... ...
000000000320b698 ff ff ff ff a6 0d 81 7c - 20 e0 e8 02 20 e0 5b 07 .......| ... .[.
000000000320b6a8 27 18 17 7c 03 00 00 00 - 65 1f 47 00 08 9f 5e 01 '..|....e.G...^.
000000000320b6b8 20 e7 2c 03 2f 6f fa 77 - 78 ae 02 03 78 ae 02 03 .,./o.wx...x...
000000000320b6c8 20 00 54 07 20 00 e1 02 - 00 00 00 00 00 00 00 00 .T. ...........
000000000320b6d8 30 22 a7 07 20 00 77 07 - 00 e0 07 00 30 22 a7 07 0\".. .w.....0\"..
000000000320b6e8 00 00 00 00 38 00 00 00 - 38 00 00 00 00 00 00 00 ....8...8.......
000000000320b6f8 00 00 00 00 01 00 00 00 - 00 e0 07 00 00 0c f8 07 ................
000000000320b708 08 00 03 000 -
Support Case # 12702 Created.
Forum Thread closed.
kc0
Cette publication n’accepte pas de commentaire.
Commentaires
7 commentaires