Problems with NVIDIA
Hi there,
maybe sombody out there has the same HW configuration as me and the same issue:
Since I have updated my NVIDIA GeForce driver to 457.09 for my GeForce GTX960M, C1 fails if I use OpenCL. It will not render anything if I change a setting (like exposure) and if I terminate C1 it will keep alive in the tasklist.
I am using Win10, latest version, on a DELL XPS15 9550
Does anybody else has this issue?
Cheers,
Oliver
-
Looking at the NV forums there are a fair number of complaints and issues with this driver version. I suggest reverting to whatever prior driver was working for you until NV gets this sorted out. While it is recommended to use the latest driver, I generally am in no rush to install a new version because of previous bad experiences (especially with AMD, but NV is obviously not immune to misfires).
0 -
Hi, I would like to add that there may be other causes as I also have v457.09 on my HP PC (GTX1050/4GB) and haven't encountered any problems running on windows 20H2(OS Build 19042.572) but I do see there are issues with Dell computers and especially screen flicker.
In my experience Dell computers should only use drivers verified by Dell.
0 -
That's interesting Don.
My ancient Dell notebook keeps trying to tell me us "update" my NVidia driver (for an ancient and low power GPU) to one from about 2 years ago even though I already have a later release installed and working without any obvious problems.
The Intel embedded HD4000 software is a different matter but the NVidia does not seem to be a problem. However, n the past I did experience an NVidis update that was a clear wrong step and reverting to the previous release solved the problem.
It's also worth noting that the drivers seem to fork down separate paths for different intended purposes. Probably something else to be careful about.
I agree that if a driver update has introduced a problem then working with the Dell recommendation ought to offer the best route for a certain solution for the specific hardware configuration. The SupportAssist tool seems to be a good starting point.
1 -
I think 457.09 is the latest game ready driver, unless you are seriously into gaming you may be better off with the latest studio driver (456.71) which is optimised for creative use. Beware Windows update can update you to a game ready driver if you don't keep a close eye on it.
Hope this helps.
Dave
0 -
I´m using CO20 latest release on an Acer notebook (4k screen, i7 CPU, Geforce GTX 960M with NVIDIA driver 457.09) without problems. Just double checked to be sure. OS is Win10 with all updates.
Just one interesting thing you may want to check with the task manager. My system uses mainly the HD Graphics 530.
0 -
Re the Studio driver mentioned above, I don't think those drivers are available for the 960M because it has older architecture than the required Pascal or Turing.
0 -
Hi Thomas
You have make some adjustments in Windows 10 to ensure that the Nvidia card on Notebooks is used by Capture One.
Go to Windows Settings/System/Display and at the bottom of that page you will see a link to Graphics settings, click on this and the Graphics settings page opens. The second item is Graphics performance preference. In the dropdown select Desktop app and browse to the Capture One .exe (C:/Program Files/Capture One/Capture One 20/CaptureOne.exe on my machine) and select it., select options and in the Graphics preference popup select High Performance and save.
In the above I am talking about the new style settings - start /settings.
Dave
0 -
Hi again Thomas
I forgot all is not yet finished having adjusted the operating system you have to force Capture One to rebuild the ImageCore file. Simply go to C:/Users/your name/AppData/Local/CaptureOne/ImageCore/ and delete the directory looking something like 13.1.3.13. Start Capture One and go away and have a cup of coffee or 2 while Capture one rebuilds the ImageCore file using the Nvidia card.
Dave
0 -
Hi All,
I've tried to replace the driver but to no avail: Still the same problem. Regardless which old driver I use (a very old one like 443 or the one from last month), C1 does not show any reaction when I change a value and when I close C1, the program is still running and I have to close it by using the task manager.
As soon as I set the two "Ignore CL" options the system works.
Which makes me wonder where the exact problem is based because it seems that it is not related to a specific driver
(And yes, I rebuild the ImageCore as well)
So far, I never had any issues with C1 and my hardware
Oliver
0 -
Oliver,
There is a specific Log file for the process and it is also recorded in one of the other log files as well.
Also if you open the "Activities" window before closing a C1 session or catalog it should reappear when you reopen the session. At that time it may also work through the OpenCL assessment once again - depending on what happened last time.
My WIn 7 system started to have a problem with assessment of the Intel HD4000 software based OpenCL driver (Device 0) and would fail before the NVidia GPU (Device 1) assessment had completed. Restarting C1 again allowed completion and OpenCL became active.
More recently the process hung up rather than failing and so the "Fail" was never recorded and the process never completed. Suddenly, on day, it all started to work as before so simply diabaling and then enabling Hardware Acceleration starts the GPU assessment, device 0 is a known fail so it skips that and goes to device 1 which now completes.
It has now stopped working once again so further investigations required.
I have no idea how Win 10 deals with the process. I should be the same but we are talking Microsoft here so who knows whether it is?
The Intel stuff is especially directed for use in screen handling.
What
0 -
Dave, thanks a lot for pointing me to the windows configuration. I already configured it in the Nvidia control app, but not in the Win 10 config.
Now done and C1 rebuilded the Image Core files. On the task manager it now looks like its using both, fine with me.
@Oliver: still no problems like you described it. The driver works fine on my system.
0 -
So - I installed C1 V21 and now C1 is not crashing any longer when both HW accelaration settings are set to auto :-)
The only thing I am now discovering is that C1 seems to use neither the internal GPU (if I look at my task manager) nor the NVIDIA. No special activities e.g. when I recreate my previews. Also the assignment of C1 to NVDIA within windows did not changed anything.
I will look further... ;)
0
Post ist für Kommentare geschlossen.
Kommentare
12 Kommentare