This bug was made in reaction to closing bug 1008759. The solution there (not yet accepted) was to blacklist the card from using D2D. Blacklisting is common -- for example WoW busts this card down to D3D9 due to driver issues. Note that 1008759 is an e10s bug only. This bug is not that narrow. However, this spot in the driver seems to cause a lot of crashes on a variety of hardware combinations. And the crashes look pretty similar -- they seem to happen when sharing graphics surfaces across Windows graphics APIs (namely in CreateShaderResourceView). These are the latest CrashReporter bugs of this type: https://crash-stats.mozilla.com/report/list?product=Firefox&range_unit=days&range_value=28&signature=nvwgf2um.dll%400x134a04#tab-reports Asynchronous processing inside of D3D means that this could just be due to some earlier inconsistent graphics operation but, regardless, this is worth knowing the answer.
You need to log in before you can comment on or make changes to this bug.