If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Basically they are paying 250$ per test just to be able to put a windows logo sticker on their product. Read up some stuff on wikipedia and they seem to run some basic tests on the driver, wouldn't be surprised if it was fully automated and would take a hour max without any kind of input.
But this case just proves the drawbacks of em old binary blobs. Too bad Nvidia isn't planning on going open source or at least letting more people in on the thing.
Don't drivers have some sort of shut off mechanism that prevents damage to the GPU due to overheating? If not then they should.
and that's what happens here; the driver fails to act on a soft limit and the hardware shuts down due to a hard limit.
You should be able to use the card again after it has cooled down (though doing this constantly will probably damage the card eventually)
That doesn't apply here. Nvidia is perfectly aware that there is a problem, and it's not like you would notice quicker that your card is being fried if you were using an open source driver. Actually, now that I think about it, I don't see any case were people would be more likely to find bugs or other anomalies in OSS software. As for fixing it quicker, I guess that's debatable and pretty much depends on the company, the project and the gravity of the problem we are talking about.
Well it's not related, there will be bugs like these on both blobs and OSS but the delta between the release of the driver and the fix would be usually lower on well managed OSS project(in my opinion), as you have more assets(so to speak, just more ppl that dig in the code or test the stuff more internally-like).
But Nvidia is doing a good job with their blob thingy, just saying theres still room for improvement.