I have confirmed that the new Doom 365.19 drivers:
- Do NOT fix the OpenCL/CUDA miscalculations (Internal NVIDIA Bug ID: 200197534)
- DO fix the Poem@Home TDR/crashes (NVIDIA Bug ID: 1754468)

So... If you do any distributed computing involving OpenCL/CUDA calculating, I recommend that you **stick with 362.00** for correct calculations, until the next driver release which should have the miscalculation fix.

Thanks,
Jacob

I have the 364.72 driver on 3 of my hosts, and my Einstein@home tasks are validating just fine.
So I'm not sure about the extent this issue has on CUDA tasks.

:) PrimeGrid was having miscalculated tasks end up validating each other. The miscalculation doesn't effect every operation, but because it affects some, I stand by my recommendation.

I have the 364.72 driver on 3 of my hosts, and my Einstein@home tasks are validating just fine.
So I'm not sure about the extent this issue has on CUDA tasks.

:) PrimeGrid was having miscalculated tasks end up validating each other. The miscalculation doesn't effect every operation, but because it affects some, I stand by my recommendation.

While I do not want to deny your recommendation, I have to clarify my statement:
I have the 364.72 driver on 3 of my hosts, and my Einstein@home (CUDA) tasks are validated just fine even by AMD Radeon (OpenCL) tasks.

'Upgraded' to 364.72 WHQL (Clean install wouldn't work on W10x64) and found that it crashed all POEM tasks (OpenCL) [driver restarts].
Ran MW and Einstein tasks without problems and so far it's running a task here without difficulty.

My experience with 364.72 on W10 (WDDM 2.0):
No issues at GPUGrid (CUDA 6.5).
No issues with Einstein tasks (CUDA 3.2 + CUDA 5.5).
Issues with POEM tasks (OpenCL).
PG is also OpenCL AFAIK.
MW uses a small and simple OpenCL app, so might not be effected because of that.

After updating to 365.19 - so far:
Able to run MW tasks,
Able to run POEM tasks,
Able to run Einstein tasks,
Able to run a mix of MW and POEM tasks or a mix of MW and Einstein tasks,
No work for GPUGrid so far, and I don't crunch at PG.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

368.22 passed my OpenCL/CUDA calculation checking, which had been failing on all of the R364 drivers. And POEM task crashes, which were fixed in 365.19, are still fixed.

So ... I recommend 368.22 now, instead of 362.00. :)

Thanks,
Jacob Klein

Details:
http://www.primegrid.com/forum_thread.php?id=6775

Thanks Jacob. For us non-gamers is there any particular reason to upgrade?

Thanks Jacob. For us non-gamers is there any particular reason to upgrade?

If it's not broken...

If your driver works (tasks all complete, no system issues) and you don't game then there is no need to upgrade the driver.
The present app uses CUDA6.5, which came out some time ago. If the project recompiled the ACEMD app to a CUDA 7.5 only app using the latest CUDA toolkit (now 8 months old) then some people might need to update their drivers to CUDA 7.5 capable drivers. Sometimes they do this in the lab only to discover that there is no benefit to the app so they dont release it and stick with their existing app; if it's not broken...

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Thanks Jacob. For us non-gamers is there any particular reason to upgrade?

There are always other fixes put in, too. Ultimately, it's up to you. If you don't have a reason to upgrade to R367, then sticking with 362.00 would be fine.

Just avoid R364 -- too many nasty problems (like BSODs, black screens, TDRs, miscalculations, etc.) in my opinion.

For what it's worth... One of the big new features of the 364.* drivers was optimized VR support for Oculus and Vive headsets. Rolling back to 362.00 definitely fixed the OpenCL errors (and other instabilities), but was a clear downgrade in VR performance. I can confirm the new 368.22 brings back the VR performance improvement while also fixing the OpenCL issues Jacob has been testing. So, the new driver seems to work well in all cases!

Exception: The 368.22 driver does NOT work well under Windows Vista. If you install it there, expect many hours for which the computer won't even boot.