Getting bad work unit (Unreleased driver issue)

[bruce]

Thanks for the info. We'll pass it on to others who may be in the same situation.

I think it's fair to assume that MS/nV will figure out and release drivers that will successfully work either inside or outside of WSL.

[Tetnacious]

Same thing.
On windows insider fast ring, geforce 460.15.
Running RTX 2060 S.
Note clCreateContext fails anywhere with "NVIDIA CUDA", this is not FAH specific.

Also note, 222 is the least significant byte in the error code -34 CL_INVALID_CONTEXT, which is the actual error.
This is quite confusing, and it'd be better to show the actual error codes. This prompt is only useful for developers anyway.

[silverpulser]

UPDATE - Windows has automatically updated the driver to 460.15 which has once again stopped FAH from working. Tried DDU in Safe Mode and before I could install 452.06 it loaded in 460.15 after restarting. I wonder if this is in the Windows Insider Preview ISO so Windows doesn't need to download it.

[PantherX]

...I wonder if this is in the Windows Insider Preview ISO so Windows doesn't need to download it.

Assuming you have disconnected the internet, you can manually uninstall the drivers and continue. Also, it's something that the people over that Microsoft Forum might be able sort out. Do keep us posted on your findings

[Tetnacious]

UPDATE - Windows has automatically updated the driver to 460.15 ...

You can disable update for a specific device, this doesn't have a UI though, it's in the group policy and you need the hardware IDs.
https://www.tenforums.com/tutorials/146 ... river.html

[silverpulser]

I had already clicked on Pause updates for 7 days before running DDU in Safe Mode. As that didn't resolve the problem I downloaded 452.06 from the Nvidia site and ran it. It has replaced 460.15 and over last night has continued to run FAH without failing. GPU-Z reports 452.06 is still the driver today. I will continue to watch and report my findings. I have submitted a report to the Feedback Hub and included the link on my observations on the conversations on page 4 of the Windows Insider forum discussion on the latest build

[silverpulser]

24 hours later and still folding with the 452.06 driver.

[JohnChodera]

Glad the driver rollback worked!

We've been working with some good folks at NVIDIA to better understand these failures, so if you have complete details on how to reproduce the issue, that would be super helpful!

~ John Chodera // MSKCC

[silverpulser]

Would you like me to install the 460.15 driver again? As a matter of interest the Windows Insider/Dev channel upgrades to a new build each Wednesday. I am expecting that this will probably load in the 460.15 driver during the upgrade to the new build.

[JohnChodera]

@silverpulser: If you want to experiment with this, it would be better to do it in the #core22 development slack I invited you to since we have an NVIDIA rep working with the driver team who can help guide you through specific tests!

~ John Chodera // MSKCC

[silverpulser]

OK, have accepted the invite and posted first msg.

[silverpulser]

Same thing.
On windows insider fast ring, geforce 460.15.
Running RTX 2060 S.
Note clCreateContext fails anywhere with "NVIDIA CUDA", this is not FAH specific.

Also note, 222 is the least significant byte in the error code -34 CL_INVALID_CONTEXT, which is the actual error.
This is quite confusing, and it'd be better to show the actual error codes. This prompt is only useful for developers anyway.

The driver has now been updated to 460.20 and after a couple of hours testing I can confirm that the problem looks to be resolved with this release.

[Tetnacious]

The driver has now been updated to 460.20 and after a couple of hours testing I can confirm that the problem looks to be resolved with this release.

Had to get it from NVIDIA developer website, did not get it in driver updates.
https://developer.nvidia.com/cuda/wsl/download