Attacking the Windows Nvidia Driver

#1

Post by spaceboy » Thu, Feb 16, 2017, 1:34 PM UTC

Attacking the Windows Nvidia Driver
googleprojectzero.blogspot.com

Re: Attacking the Windows Nvidia Driver

#2

Post by AlwaysRock » Thu, Feb 16, 2017, 4:15 PM UTC

I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.

Re: Attacking the Windows Nvidia Driver

#3

Post by baobrain » Thu, Feb 16, 2017, 4:20 PM UTC

I wonder if AMD drivers have the same attack surfaces as the nvidia drivers

Edit: a quick google search turns up CVEs for the old catalyst driver, but none for the newer crimson drivers.

Re: Attacking the Windows Nvidia Driver

#4

Post by hatsunearu » Thu, Feb 16, 2017, 4:20 PM UTC

AlwaysRock wrote: post #2

I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.

Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.

Re: Attacking the Windows Nvidia Driver

#5

Post by youdontknowtho » Thu, Feb 16, 2017, 4:31 PM UTC

Project Zero is awesome. I'm not normally a fan of the GOOG, but these guys are doing some seriously good work.

Re: Attacking the Windows Nvidia Driver

#6

Post by cr0sh » Thu, Feb 16, 2017, 4:33 PM UTC

hatsunearu wrote: post #4

AlwaysRock wrote: post #2

I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.

Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.

Yeah - that sounds like fun - recreating a driver install issue after you finally have it working on your system. Heck, even if you set up a system -just- to recreate this problem, it would still be one of those "nightmare inducing" trials of will. I'm not saying it shouldn't be done, I just can't imagine doing it (especially on my personal workstation).

Re: Attacking the Windows Nvidia Driver

#7

Post by sleepychu » Thu, Feb 16, 2017, 4:35 PM UTC

AlwaysRock wrote: post #2

I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.

You're being down voted but I had the exact same behavior last week, in the end I gave up trying to fix it and reinstalled Windows to a new drive, at some point I'll wipe my old 'C' and move my new 'C' back to the fastest boot drive.

Re: Attacking the Windows Nvidia Driver

#8

Post by realharo » Thu, Feb 16, 2017, 4:41 PM UTC

hatsunearu wrote: post #4

AlwaysRock wrote: post #2

I cant prove this but my computer blue screened after a Nvidia driver update. It took my several hours to get everything working again because it wouldnt even launch in safe mode. Very frustrating. I wish they had a little more quality control on their drivers.

Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.

I dunno, I have had to live with this bug (https://forums.geforce.com/default/topic/953432/geforce-mobi... , https://answers.microsoft.com/en-us/windows/forum/windows_10... ) for over half a year now.

Re: Attacking the Windows Nvidia Driver

#9

Post by sametmax » Thu, Feb 16, 2017, 5:00 PM UTC

cr0sh wrote: post #6

hatsunearu wrote: post #4

Earlier quoted context omitted.

Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.

Yeah - that sounds like fun - recreating a driver install issue after you finally have it working on your system. Heck, even if you set up a system -just- to recreate this problem, it would still be one of those "nightmare inducing" trials of will. I'm not saying it shouldn't be done, I just can't imagine doing it (especially on my personal workstation).

Plus you paid for the computer, graphic card and OS. Why in hell would you spend hours of work on your free time for this ? Do people try to find defects in their car then send a report to Ferrari ?

Re: Attacking the Windows Nvidia Driver

#10

Post by [deleted] » Thu, Feb 16, 2017, 5:13 PM UTC

realharo wrote: post #8

hatsunearu wrote: post #4

Earlier quoted context omitted.

Oh trust me, they do tons of QA. If you can replicate what problem you have demonstrably with steps that QA can follow and you submit to the Nvforums or whatever, someone in the QA team will eventually try it out.

I dunno, I have had to live with this bug ( https://forums.geforce.com/default/topic/953432/geforce-mobi... , https://answers.microsoft.com/en-us/windows/forum/windows_10... ) for over half a year now.

[deleted]