Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

(Fixed- see last post) Capture One 12 Crashing on Startup

Comments

7 comments

  • SFA
    3 thoughts.

    Firstly you maybe don't want to publish your email address on a public web site (it's in the crash log file).

    Secondly most of the dates recorded are last month. Was that when you had the problem?

    Thirdly this is a User to User forum and so maybe not too much help with problems like this without more information - such as whether or not the system has worked since you upgraded the GPU and did it work before your last Windows update?

    I would suggest that you create a Support Case and send the Capture One support team the log files (Not the crash log but the C1 log files) to see what they come up with.


    Grant
    0
  • mli20
    [quote="NNN636440140118682523" wrote:
    ... bought the value pack of styles, added them during upgrade, ...

    Styles are mentioned a number of times in the logs you provided. I'd suggest you delete (Capture One 12 User Guide, p. 303) all your styles and take it from there.

    MLI
    0
  • Michael Schneider
    Thanks for your tips. I have never had an issue with Capture One in several years, so I did not know How to file an issue.

    Finally completed that task.

    Thanks for the tip about email, fixed that.

    Since Capture One dies on startup, I am unable to delete styles, or interact with Capture one in any way.


    Will keep everyone posed.

    Thanks
    0
  • mli20
    [quote="NNN636440140118682523" wrote:


    Since Capture One dies on startup, I am unable to delete styles, or interact with Capture one in any way.

    Duh, but never fear, all is not lost. You can search your disk for .costyle files, and delete them.

    On my PC, I find such files here: User\AppData\Local\CaptureOne\Styles50\SAMPLES (v11). Yours might be located elsewhere, but User\AppData\Local\CaptureOne\ is still a good place to start.

    MLI
    0
  • Michael Schneider
    ****************************** Fixed ************************************************

    The problem was that I had updated my graphics card from an NVIDIA to an AMD. NVIDA and AMD have different OPENCL


    I deleted all the files in C:\ProgramData\Phase One\Capture One\ImageCore
    Note: NVIDEA and AMD graphic cards use different OPENCL solutions. When I installed Capture One, I was using
    NVIDIA, I upgraded to an AMD graphics card, and Capture One did not verify the OPENCL libs
    at startup. So Capture One crashed everytime on startup. Deleting the files causes Capture One to
    recreate them for the current graphics card at startup. It may take about 30minutes to rebuild the
    files, but I have not have the problems since


    Then restarted.

    This repopulated with the files necessary for the AMD graphics card.


    Thanks to you all for your suggestions, hope this is helpful
    0
  • SFA
    [quote="NNN636440140118682523" wrote:
    ****************************** Fixed ************************************************

    The problem was that I had updated my graphics card from an NVIDIA to an AMD. NVIDA and AMD have different OPENCL


    I deleted all the files in C:\ProgramData\Phase One\Capture One\ImageCore
    Note: NVIDEA and AMD graphic cards use different OPENCL solutions. When I installed Capture One, I was using
    NVIDIA, I upgraded to an AMD graphics card, and Capture One did not verify the OPENCL libs
    at startup. So Capture One crashed everytime on startup. Deleting the files causes Capture One to
    recreate them for the current graphics card at startup. It may take about 30minutes to rebuild the
    files, but I have not have the problems since


    Then restarted.

    This repopulated with the files necessary for the AMD graphics card.


    Thanks to you all for your suggestions, hope this is helpful


    Hmm.

    I was going to suggest checking that BUT, since C1 as I understand it (somewhat supported I think by what I saw in the log files) will check for possible OpenCL processing options on start up I'm a little surprised that your upgrade seems to have been recognised but not acted upon. Or at least if acted upon maybe did not at the same time recognise the need to ignore the Nvidia card.

    I think you should still discuss this with the Support Team. It seems like something did not quite work as intended.


    Grant
    0
  • Paul Steunebrink
    [quote="NNN636440140118682523" wrote:
    ****************************** Fixed ************************************************

    The problem was that I had updated my graphics card from an NVIDIA to an AMD. NVIDA and AMD have different OPENCL

    Thanks for the feedback. Makes perfect sense to me. The OpenCL kernel are generated based on the hardware and corresponding driver. When you change that, they are no longer valid.

    Sometimes the installation of a new driver makes it necessary to delete the OpenCL kernel and let CO generate a new set.
    0

Post is closed for comments.