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. ⚠️

Fequent BSoD after 20

David Woodcock
I have never had a BSoD system crash before but I have had 3 in 2 days after installing 20. After a system restore, I found that C1 ver.12 was no longer activated. Using my previously valid license code, it shows as initially valid then comes up as invalid at the final step. ☹️
0

Comments

21 comments

Date Votes
  • Michael Ben-Gershon
    Are you using WIndows 10?

    If so, have you upgraded recently to release 1909 (via the standard upgrade system)?

    If so, then I would suspect that, rather than Capture One.

    I have been plagued by sudden crashes and reboots of Windows 10 since the 1909 upgrade, and have managed to eliminate them by downgrading (may be done via Settings)
    0
  • SFA
    NNN634514126675355624 wrote:
    I have never had a BSoD system crash before but I have had 3 in 2 days after installing 20. After a system restore, I found that C1 ver.12 was no longer activated. Using my previously valid license code, it shows as initially valid then comes up as invalid at the final step. ☹️


    You new V20 licence code is not the activation you require for V12 and earlier versions. Just re-activate when prompted. It only needs to be done once.


    Grant
    0
  • Keith Reeder
    NNN634514126675355624 wrote:
    I have never had a BSoD system crash before but I have had 3 in 2 days after installing 20.

    How much RAM do you have?

    Is it healthy?
    0
  • SFA
    Just for reference.

    https://support.captureone.com/hc/en-us/articles/360002408757-Which-version-of-Capture-One-will-work-with-my-Windows-operating-system-
    0
  • Paul Steunebrink
    For users running Windows 10 build 1903 or 1909, please see the tip on installing the latest Visual Studio in this post:
    https://forum.phaseone.com/En/viewtopic.php?p=172515#p172515
    0
  • David Woodcock
    FYI, I am running a fully updated version of Win10, i5, 8Gb RAM. Personally I have never seen a BSoD since an early version of NT4, probably 20 years ago.
    Also, FYI, if you do a system restore to clean ver.20 fully from your system, your previous ver.12 license will not work but the ver.20 license key (converted from your pre-release voucher) will work with ver.12. The only problem is that any sessions opened with ver.20 (& converted) will not open with ver.12.
    Anyone know how to re-convert sessions converted to 20 to go back to 12?
    0
  • Jim Hughes
    I thought that when a session was converted to a new version, a backup copy was created.
    0
  • SFA
    JimHughes wrote:
    I thought that when a session was converted to a new version, a backup copy was created.


    It is.

    Plus session edits are saved in subfolders local to the location of the image file. Separately for each version that has been used to look at the files.

    So even if, for some reason, the session file has been lost or discarded there should be a folder with the edit data and that could be read by a new session that is making use of an older version. Unless, of course, all of that has been discarded by choice.


    HTH.

    Grant
    0
  • Thomas Achermann
    NNN634514126675355624 wrote:
    I have never had a BSoD system crash before but I have had 3 in 2 days after installing 20. After a system restore, I found that C1 ver.12 was no longer activated. Using my previously valid license code, it shows as initially valid then comes up as invalid at the final step. ☹️


    An application cannot provoke a BSOD by itself because it runs in user mode. BSODs are caused by kernel mode parts, usually buggy drivers. First of all I would make sure all drivers on your PC are up-to-date, especially graphics drivers.
    0
  • Michael Ben-Gershon
    Thomas Achermann wrote:
    An application cannot provoke a BSOD by itself because it runs in user mode. BSODs are caused by kernel mode parts, usually buggy drivers. First of all I would make sure all drivers on your PC are up-to-date, especially graphics drivers.

    I read on the web that there may be graphics driver incompatibilities with WIndows 10 release 1909, so I updated my NVIDIA drivers to the latest stable version. It made no difference. The only thing which actually stopped all the crashes was downgrading 1909 to 1903. I should add that these problems began before my upgrade of Capture One to version 20.
    0
  • SFA
    Michael17 wrote:
    Thomas Achermann wrote:
    An application cannot provoke a BSOD by itself because it runs in user mode. BSODs are caused by kernel mode parts, usually buggy drivers. First of all I would make sure all drivers on your PC are up-to-date, especially graphics drivers.

    I read on the web that there may be graphics driver incompatibilities with WIndows 10 release 1909, so I updated my NVIDIA drivers to the latest stable version. It made no difference. The only thing which actually stopped all the crashes was downgrading 1909 to 1903. I should add that these problems began before my upgrade of Capture One to version 20.

    Thanks for that Michael.

    As someone happily running a stable WIn 7 system I face the prospect of a forced move to Win 10 in the new year. I know next to nothing about Win 10 except that Microsoft seem to have adapted the Apple path of employing thousands of people to push some good but some decidedly dodgy code to millions of users across the world and then leave the user and their application code supplier to sort out most of the immediate mess.

    It could be dealt with once, centrally. But even if they eventually patch and re-issue they will have created havoc for some users out in the wild and caused hours of unnecessary headaches and millions of days of wasted time.

    They are not alone amongst the large corporations.

    I don't personally feel a desperate need to be at the forefront of this rolling disaster area.

    If anyone has any tips, specifically for Windows, about how to ensure one is never conned into installing a recent but non-reliable update for which there is no urgent need (security, etc.) to be satisfied then I will be extremely grateful for the guidance.

    Many thanks in advance,


    Grant
    0
  • Permanently deleted user
    SFA wrote:
    I don't personally feel a desperate need to be at the forefront of this rolling disaster area.

    If anyone has any tips, specifically for Windows, about how to ensure one is never conned into installing a recent but non-reliable update for which there is no urgent need (security, etc.) to be satisfied then I will be extremely grateful for the guidance.

    Many thanks in advance,


    Grant

    While I don't deny that some people are having issues, I have had absolutely ZERO issues with Windows 10 and I have been running it on five machines (seven if you count two older and now de-commissioned laptops) since before it was even released to the public. I think the last BSOD I had was on Windows 7 but it has been so long I can't remember. My machines are an i7 desktop, two C2Duo desktops and an i7 laptop. And an Atom powered Windows tablet with 32GB HD and 2GB RAM that I updated to Windows 10.

    I have issues with how they currently implement Windows updates but the OS itself is very stable. I can even remove a hard drive from one machine type and put it in another (different CPU and hardware) and it figures it out and runs perfectly.

    If you are paranoid (like I was), clone your Windows 7 installation to a new HD and then upgrade THAT copy. That way, you can always put the original HD back in and you are back where you started in 30 seconds. Or use a good backup program like Macrium Reflect and image your installation before the upgrade. Also note that Windows 10 keeps a copy of your old installation and you can roll back within a week or two. The rollback usually works 😉

    Yes, there are some things to dislike in Windows 10 but it is absolutely not the hot mess that people would have you think it is.

    Paul
    0
  • SFA
    pgoelz wrote:
    SFA wrote:
    I don't personally feel a desperate need to be at the forefront of this rolling disaster area.

    If anyone has any tips, specifically for Windows, about how to ensure one is never conned into installing a recent but non-reliable update for which there is no urgent need (security, etc.) to be satisfied then I will be extremely grateful for the guidance.

    Many thanks in advance,


    Grant

    While I don't deny that some people are having issues, I have had absolutely ZERO issues with Windows 10 and I have been running it on five machines (seven if you count two older and now de-commissioned laptops) since before it was even released to the public. I think the last BSOD I had was on Windows 7 but it has been so long I can't remember. My machines are an i7 desktop, two C2Duo desktops and an i7 laptop. And an Atom powered Windows tablet with 32GB HD and 2GB RAM that I updated to Windows 10.

    I have issues with how they currently implement Windows updates but the OS itself is very stable. I can even remove a hard drive from one machine type and put it in another (different CPU and hardware) and it figures it out and runs perfectly.

    If you are paranoid (like I was), clone your Windows 7 installation to a new HD and then upgrade THAT copy. That way, you can always put the original HD back in and you are back where you started in 30 seconds.

    Yes, there are some things to dislike in Windows 10 but it is absolutely not the hot mess that people would have you think it is.

    Paul


    Paul,

    Thanks for that.

    I had assumed that by now a stable version of V10 should be possible but it is the updates that concern me most in terms of maintaining day to day stability since I really cannot get interested in chasing down OS related problems these days.

    I still need to check some older application that I use from time to time in terms of Win 10 compatibility. They are unlikely to be updated but maybe by now I will not need them again.

    It is probably time to buy an new notebook and put this one aside but having been monitoring the options for a while I have yet to spot what I really wish for at the spec, I would like and the price I feel somewhat justified in paying.

    Maybe something will present itself in the new year.


    Thanks again.


    Grant
    0
  • Ian Leslie
    SFA wrote:
    If anyone has any tips, specifically for Windows, about how to ensure one is never conned into installing a recent but non-reliable update for which there is no urgent need (security, etc.) to be satisfied then I will be extremely grateful for the guidance.


    There are various sites that manually walk you through how to disable automatically applying Windows updates. I personally use Winaero Tweker (https://winaero.com/blog/the-list-of-winaero-tweaker-features/ search for "Windows Update Settings"). This allows me to go back to me manually approving the download and install time table for all Windows updates. Note the documentation on that page does not perfectly match the latest version but you can find the right panel easily enough.

    As Paul said Win10 is nice and stable and rolling back does seem to work well but being able to just wait for a time when your schedule allows for updating and control rebooting is such a relief.

    There is only one thing I hate more the going to my computer in the morning expecting to start work where I left off only to find the damn thing rebooted in the night is having those updates actually cause me to be unable to do the work I want. This doesn't eliminate that possibility but you get to control when you are exposed to this potential problem
    0
  • Dave R
    IanL wrote:
    SFA wrote:
    If anyone has any tips, specifically for Windows, about how to ensure one is never conned into installing a recent but non-reliable update for which there is no urgent need (security, etc.) to be satisfied then I will be extremely grateful for the guidance.


    There are various sites that manually walk you through how to disable automatically applying Windows updates. I personally use Winaero Tweker (https://winaero.com/blog/the-list-of-winaero-tweaker-features/ search for "Windows Update Settings"). This allows me to go back to me manually approving the download and install time table for all Windows updates. Note the documentation on that page does not perfectly match the latest version but you can find the right panel easily enough.

    As Paul said Win10 is nice and stable and rolling back does seem to work well but being able to just wait for a time when your schedule allows for updating and control rebooting is such a relief.

    There is only one thing I hate more the going to my computer in the morning expecting to start work where I left off only to find the damn thing rebooted in the night is having those updates actually cause me to be unable to do the work I want. This doesn't eliminate that possibility but you get to control when you are exposed to this potential problem

    If you have the pro version of Windows 10 you can delay updates for up to a year using the Group Policy Editor (GPE).

    Dave
    0
  • Filthy Lucre
    David532 wrote:

    If you have the pro version of Windows 10 you can delay updates for up to a year using the Group Policy Editor (GPE).

    Dave

    You can do that from within the windows update dialog (advanced options). At least this was true for 1903, which I am still running. Looks like the dust needs to settle a bit more before I move on to 1909... I have my delay set to 150 days. 😊
    0
  • Keith Reeder
    pgoelz wrote:
    While I don't deny that some people are having issues, I have had absolutely ZERO issues with Windows 10

    Agreed - I have it on two laptops, and it's bomb-proof.

    There's nothing wrong with Win 10. The only reason it isn't on my desktop is that Win 8.1 is just as bomb-proof on it, and I believe in not fixing what isn't broken.

    To control updates:

    https://www.sordum.org/9470/windows-update-blocker-v1-5/
    0
  • Permanently deleted user
    IanL wrote:
    There is only one thing I hate more the going to my computer in the morning expecting to start work where I left off only to find the damn thing rebooted in the night is having those updates actually cause me to be unable to do the work I want. This doesn't eliminate that possibility but you get to control when you are exposed to this potential problem

    Hasn't that already been changed in Windows? My machine will download and partially install updates as it needs to but if it needs to reboot to finish an installation it asks for permission. I think it reboots on its own if you ignore the request long enough, though (like days). As for cherry picking updates, I have never had an issue with an update EVER on any of my machines so I really don't worry about it.

    And wandering a bit farther off target..... Grant, take a look on Ebay at the Lenovo Thinkpad X1 Carbon 3rd generation. They go for around $400 with i7, 256GB SSD and 8GB RAM. Small, rugged, VERY quiet (the fan is off most of the time and you can't hear it when it is on) and very reliable. I'm running one with a 2560X1440 display and I love it. PM me if you need more info.

    Paul
    0
  • Ian Leslie
    pgoelz wrote:
    Hasn't that already been changed in Windows? My machine will download and partially install updates as it needs to but if it needs to reboot to finish an installation it asks for permission. I think it reboots on its own if you ignore the request long enough, though (like days).

    Humm may be they have - I was upset the second time Windows did that so I took steps 😊 Never again.


    pgoelz wrote:
    As for cherry picking updates, I have never had an issue with an update EVER on any of my machines so I really don't worry about it.


    I don't cherry pick updates I cherry pick the time I do updates. Hold back a little to make sure no reports of apps I care about not working. Then time things for when I am not in the middle of a project and if things go sideways I can fix it with out missing deadlines. And I agree things have gone smoothly for the vast majority of the time. It is like backing up your pictures: just prudent steps for that rare time when something does not go smoothly.
    0
  • David Woodcock
    JimHughes wrote:
    I thought that when a session was converted to a new version, a backup copy was created.

    Thanks, I poked around and found the .backup versions.
    Now working on ver.12 with no problems. I sent in my information to Support but no response yet. they are usaully very quick. Snowed under?
    Incidentally, on my wife's PC (very similar configuration), ver.20 is working without a glitch.
    0
  • SFA
    NNN634514126675355624 wrote:
    I sent in my information to Support but no response yet. they are usaully very quick. Snowed under?


    It does seem strange.

    I suspect that a new system, the separation of teams (Hardware/Software) and some releases that are not without licencing issues and the effects of OS updates (especially Mac in this round) may have overloaded the resources somewhat.

    Not the time of year I would choose for this work and in earlier times new releases seemed to come around spring iirc.

    I guess the need to support the Apple/Microsoft major updates schedule simply means that putting so much into this time of year becomes important for any attempt as efficiency in the development projects.

    And of course there may be a year end angle to it as well.


    Grant
    0

Post is closed for comments.