3 ms·
I don't think any of those are productive questions. If you alter firmware that is usually unchanged over the life of the product (as for a desktop graphics car
by wtallis 9y ago
I don't think any of those are productive questions. If you alter firmware that is usually unchanged over the life of the product (as for a desktop graphics card) and you specifically edit the rules it contains for thermal throttling, then you are obviously liable for the lump of slag that you end up with. Likewise if you're making hardware modifications that compromise the thermal management capabilities. In either case, it will be pretty easy to show after the fact that the product was modified, and that your modifications were probably related to the failure. None of that applies when the host software is responsible for preventing hardware damage. As I've explained, relying on software running inside of Windows to prevent hardware damage is asking for trouble even without user intervention.
You may also notice that I'm not advocating for "legislating engineering decisions"; though there are plenty of situations where engineering decisions obviously should be determined by legislation, this is more a question of after the fact liability to be worked out by the courts, which are generally pretty good at figuring out whether to place the blame on a user or on the engineers.