So I just came home to a frozen computer and after restart I found my 1080ti computing at 95C with the fan at 0%, completely off. AVOID THESE NEW DRIVERS LIKE THE PLAGUE.

Speed control of the fans is done by an embedded controller, and default fan speed configuration is located in the "BIOS" of video card.
For example, 10xx series graphics cards at GPU temperature <= 40 C stop the fans. This works without loading OS/drivers.
Therefore, your statement is highly doubtful. It is not necessary without any evidence to throw accusations and throw a tantrum.
The problem could arise for example, because of the appeal to the controller of fans of the video card in parallel from several programs(MSI Afterburner(can control fan speed curve), HWinfo, GPU-Z & etc) or because of some hardware failure.

The above is a warning not a "tantrum." I have had my entire windows operating system fail to boot due to this driver and was forced to completely wipe it. I can assure you it is not "some other software." After the new windows installation I used driver 399.07 with no problems and tried reinstalling 416.34, with the exact same issues.

Just because something hasn't happened to you doesn't mean it can't happen.

I think I have tacked down the cause of the event. The incompatibility of my previous windows build, 1803 and the new driver, 416.34. I have changed to "Semi-Annual Channel (Targeted)" rather than regular "Semi-Annual Channel" which updated me to 1809 which, at least so far, has solved the problem.

You did not even bother to indicate that the problem occurred on a computer with Win 10, famous for unstable updates.
I worked enough time with the drivers 416.34 and 416.81 on Win 8.1 to say that there are no fundamental problems with these drivers.
Your same statement urged without any exception not to use the drivers 416.34 and above. Notice the difference now?
And yes, when you write LIKE THIS, and without any evidence - that it is exactly the tantrum.

Before you write something, you should:
1) Calm down
2) Think twice over the semantic content of their words.

Please think of this as a warning, something that people can chose to heed or ignore, you act like I am forcing people to not install this driver. You come off as extremely rude and should really think about the difference between a suggestion and treating people like children.

Is that the way(" AVOID THESE NEW DRIVERS LIKE THE PLAGUE.") you're trying to "just" warn other people? Serious?
Your "warning" doesn't sound like that you're trying to explain it now.

Instead of admitting that your "warning" came out at least very "loud" and at the same time completely uninformative, you're just trying to justify yourself, and my attempts to point out that it was not worth writing your "warning" in such manner, you're trying to expose for rudeness.

It's ridiculous.

I once had a problem where my custom GPU fan curve would get set to "off completely" despite tasks running the temps up to 100*C.

When that problem happened, it turned out to be a buggy version of eVGA PrecisionX, that didn't work right when suspending or shutting down and then loading Windows - It stored the very bottom of the curve as a constant setting when resuming from Fast Startup! Ugh. They fixed it eventually, but that was a nasty nasty bug!

I have since ditched that software, and use MSI Afterburner, and highly recommend it. I also disabled Fast Startup in Power Options, so my PC won't be susceptible to hibernation/resume problems.

I'd advise you to double check your fan monitoring software, as it seems possible that the problem you are having is with that software, instead of the NVIDIA drivers.

Make sure to report any results of any more testing you do! Thanks!

Kind regards,
Jacob Klein

While I am also using MSI Afterburner, I have never had a problem with it in the past. The problem occurred directly after updating my drivers from 399.07 to 416.34, 416.81 and 416.94. All three new drivers had several issues. The 0% fan speed only occurred once, so I will call this a fluke.

The main problem is when the screen wakes up the primary screen (I have 3 monitors) it has scan-line errors. If I let the screens go back to sleep again and try to wake it up, it looks like it tried to wake up, but it stays black forever. I would then restart the computer and it would prevent booting entirely. The first time I installed this driver I tried to recover it with windows recovery and everything failed. I was forced to reinstall windows.

With a fresh install I tried driver 399.07 with nothing but success. Now I try 416.34 and above on the fresh install with the exact same errors, this time without MSI afterburner installed.

Have you been active in NVIDIA's GeForce User Forum, in the GeForce Driver Feedback threads?
https://forums.geforce.com/default/board/33/

There is a thread for each driver version, and I read them all, and yes I believe that I have heard of some people having similar problems with Release 415 drivers. But I haven't had any problems, personally.

Make sure to visit there to post your feedback, and also see if there are any workarounds, tips, or solutions. And if you want to report an issue more thoroughly so NVIDIA has a better chance of fixing it, then you should follow the steps in the first post of a driver feedback thread, to fill out the NVIDIA driver feedback form.

... I also disabled Fast Startup in Power Options, so my PC won't be susceptible to hibernation/resume problems.

type [pre]powercfg -h off
There is no output of the command, but you can check the increase of the free disk space to verify the effect of the command.
Turning off hibernation also turns off fast startup.

Unfortunately the solution is not that simple. I have an ASRock mobo and I am still restricted from using any 400 series driver.

PappaLitto, are you using an ASUS MB? I ask because there's a known issue between ASUS motherboards and monitoring programs such as HWiNFO that randomly causes the fans to go to zero. Bad, bad bug. AFAIK this issue only affects ASUS.

Did you try HWiNFO 6.00?
Also, might read this thread and reply there if problem persists:
https://www.hwinfo.com/forum/Thread-ASUS-Prime-X470-Pro-Fan-headers-shutting-down-after-a-while-when-running-HWiNFO?highlight=Asus

Did you try HWiNFO 6.00?
Also, might read this thread and reply there if problem persists:
https://www.hwinfo.com/forum/Thread-ASUS-Prime-X470-Pro-Fan-headers-shutting-down-after-a-while-when-running-HWiNFO?highlight=Asus

Oh yeah, BOINCTasks and TThrottle rule. I couldn't imagine BOINCing without them anymore. Unfortunately, the first time the ASUS shenanigans happened, I wasn't yet using them (and the second time a year later I was present to notice and take care of it immediately):

Thanks for the link, Jacob. That is interesting and no, I haven't tried it with 6 or above I don't think. However, from reading the thread, it seems like there's still no definitive fix? It also mentions disabling the ASUS sensors in HWiNFO, but I did exactly that and was in fact asked whether I wanted to disable them just as Beyond described. It did however not help in the end.

On this one computer I'm using CoreTemp and GPU-Z plus some Windows monitoring Gadgets instead.

Did you try HWiNFO 6.00?
Also, might read this thread and reply there if problem persists:
https://www.hwinfo.com/forum/Thread-ASUS-Prime-X470-Pro-Fan-headers-shutting-down-after-a-while-when-running-HWiNFO?highlight=Asus

Did you try HWiNFO 6.00?
Also, might read this thread and reply there if problem persists:
https://www.hwinfo.com/forum/Thread-ASUS-Prime-X470-Pro-Fan-headers-shutting-down-after-a-while-when-running-HWiNFO?highlight=Asus