C1 v10.2 crashes when using the "Details" view
Hi,
I'm currently evaluating C1 v10.2 (Pro, Sony edition) and have encountered multiple crashes when getting in the "Details" view (sharpening, noise reduction). Whenever I get in this view, the application just stops responding (some CPU activity seen in task manager) and eventually a crash report popup appears (nice touch but reading C++ stack traces is out of my league).
This is on Windows 10 (build 10.0.15063, 64bit-Home), hardware is a Dell XPS 9560 (16GB, 4K screen, 512GB M.2 SSD). I've tried disabling the Nvidia 1050 GPU (sometimes those crashes are related to unsupported drivers): no difference. Still crashes whenever I get near this view.
I've uploaded the crash report in hoping that Phase One will be able to sort this out: C1 looks very promising as it handles Sony RAW files very well but, if I can't use it to denoise / increase sharpness, then it is very much crippleware to me.
For the records: LR and ACDsee do not crash on this laptop. So, I don't think this is hardware related.
Has anyone seen such problems with C1 v10.2 on Windows 10 using similar hardware or not?
Cheers,
Patrick
I'm currently evaluating C1 v10.2 (Pro, Sony edition) and have encountered multiple crashes when getting in the "Details" view (sharpening, noise reduction). Whenever I get in this view, the application just stops responding (some CPU activity seen in task manager) and eventually a crash report popup appears (nice touch but reading C++ stack traces is out of my league).
This is on Windows 10 (build 10.0.15063, 64bit-Home), hardware is a Dell XPS 9560 (16GB, 4K screen, 512GB M.2 SSD). I've tried disabling the Nvidia 1050 GPU (sometimes those crashes are related to unsupported drivers): no difference. Still crashes whenever I get near this view.
I've uploaded the crash report in hoping that Phase One will be able to sort this out: C1 looks very promising as it handles Sony RAW files very well but, if I can't use it to denoise / increase sharpness, then it is very much crippleware to me.
For the records: LR and ACDsee do not crash on this laptop. So, I don't think this is hardware related.
Has anyone seen such problems with C1 v10.2 on Windows 10 using similar hardware or not?
Cheers,
Patrick
0
-
Hopefully Support will be able to sort it out for you. Meanwhile have you tried turning off hardware acceleration in the Capture One preferences to see whether that makes a difference?
Ian0 -
Hi Ian,
Yes, I have tried that. In C1 preferences (disabled for both), in NVidia Control Center (disabled it for C1 explicitly).
Funny enough, things are getting a bit better now that I'm avoiding the details view (moved it out to the right, so that I can't stumble upon it by accident).
I'm starting to wonder if this was not due to a combination of factors: like having several layers on the image then going to Details view. Maybe there's a magic combination that leads to a crash, no matter what. Remains to be seen 😊
Regards,
Patrick0 -
[quote="NNN636448225950231576" wrote:
Hi Ian,
Yes, I have tried that. In C1 preferences (disabled for both), in NVidia Control Center (disabled it for C1 explicitly).
Funny enough, things are getting a bit better now that I'm avoiding the details view (moved it out to the right, so that I can't stumble upon it by accident).
I'm starting to wonder if this was not due to a combination of factors: like having several layers on the image then going to Details view. Maybe there's a magic combination that leads to a crash, no matter what. Remains to be seen 😊
Regards,
Patrick
Patrick,
The generic Crash Report is just that - a generic report for mass data analysis.
You can get personalised support by creating a Support Case and the C1 Support Team will be able to look at the log files the application generates and provide guidance from what they see.
Strongly recommended.
Weekday coverage so good timing!
HTH.
Grant
ETA: What do you mean when you write "Details" view?0 -
Patrick,
I have just seen your post in the Mac section of the forum.
There is no "Details" mode in C1 - just a Menu tab that by default groups certain tools together.
You can open and work with each of the tools individually - perhaps as a floating tool. That is an option for you.
If you do that you might be able to work out if there is indeed one tool that might be causing your problems but I have to say that over several years of using various versions of C1 the operation of individual tools it not something I can recall as being the source of any problems - at least not obviously.
I would strongly advise that you create a Support Case and allow the Support Team to take a look at the information that C1 captures in its log files.
HTH.
Grant0 -
guessing Details Mode = Details Tab 0 -
guessing Details Mode = Details Tab
Right, that's exactly what I mean. Clicked the details tab, then boom. And reboom, and reboom again 😉
I'll find out if I can open an incident, even though I've not purchased C1 yet.
Thanks,
Patrick0 -
[quote="NNN636448225950231576" wrote:
guessing Details Mode = Details Tab
Right, that's exactly what I mean. Clicked the details tab, then boom. And reboom, and reboom again 😉
I'll find out if I can open an incident, even though I've not purchased C1 yet.
Thanks,
Patrick
You can create a Support Case.
From the Help menu in the application: "Contact Support".
However first you might just want to try reinstalling C1 if you have not already done so. Just in case something did not quite install correctly. Also reboot your system just in case there is something floating about in the Windows stuff that may resolve itself.
What you are seeing is not typical at all. However it is certainly not safe to assume that all software products that perform a certain task, like RAW file conversion for example, are doing similar things in the same way so whether one works and another does not (at the tome) is not a good measure of how you will experience things in the future.
HTH.
Grant0 -
Hi Grant,
I'll try to update to 10.2.1. Maybe that will help. For some reason, I was not able to able the series of crashes afterwards. Weird :/ Thanks for the advice.
Patrick0
Post ist für Kommentare geschlossen.
Kommentare
8 Kommentare