Open Bug 1681581 Opened 10 months ago Updated 6 months ago

Nvidia display driver (27.21.14.6079) crashes when playing Youtube videos

Categories

(Core :: Graphics, defect, P3)

Firefox 83
x86_64
Windows 10
defect

Tracking

()

UNCONFIRMED

People

(Reporter: balz.guenat, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

  1. Install a Nvidia RTX 3080
  2. Turn on hardware acceleration (default)
  3. Watch a video on Youtube

Actual results:

Sometimes after only minutes, sometimes after hours, the nvidia driver crashes, the display freezes and then goes black until driver recovers after a few seconds. Windows Event Viewer shows 4 errors per incident, spaced 3-7 seconds apart, all identical:

Error Message: Display driver nvlddmkm stopped responding and has successfully recovered.
Event ID: 4101

Issue first appeared after upgrading the GPU from a GTX 1070 to a RTX 3080.
I have already raised this issue with Nvidia support and after some troubleshooting, it was determined that this issue does not appear on other browsers (I tried Chrome) or if hardware acceleration in Firefox is turned off.

My system runs the newest version of Windows 10, GPU drivers and BIOS.

Additional steps that were tried but didn't yield improvement:

  • Clean reinstall of display driver
  • Installing older driver
  • Disabling GPU overclock
  • Disabling GSync
  • Creating a new Windows user account and use it to watch videos

Expected results:

No driver crash

Looks like GPU driver or even GPU issue to me, not Firefox one.

(In reply to Virtual_ManPL [:Virtual] 🇵🇱 - (please needinfo? me - so I will see your comment/reply/question/etc.) from comment #1)

Looks like GPU driver or even GPU issue to me, not Firefox one.

Agreed and that's why I filed an issue with Nvidia before creating this bug report, but as a mere user, I have no chance of debugging or isolating such a driver bug. My hope is that a Firefox dev can investigate and file a more meaningful bug report with Nvidia.

  1. Does this issue still reproduce while in safe mode? https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
  2. Can you please go to the "about:support" page, copy the information and attach it to this bug?
  3. Would you help us try to investigate this issue further if some more testing is required?
    Thanks.
Flags: needinfo?(balz.guenat)

(In reply to Bodea Daniel [:danibodea] from comment #3)

  1. Does this issue still reproduce while in safe mode? https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

Issue seems to disappear in safe mode, which is to be expected, as safe mode disables hardware acceleration.

  1. Can you please go to the "about:support" page, copy the information and attach it to this bug?

Attached as file.

  1. Would you help us try to investigate this issue further if some more testing is required?
    Thanks.

Sure.

Flags: needinfo?(balz.guenat)
Attached file ff_about_support.json

about:support as json

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Graphics
Product: Firefox → Core

Hi Balz,

When this occurs, do any crash reports show up in about:crashes in firefox? If so, could you please share a link here?

Could you also please try going to about:config and searching for gfx.webrender.compositor. Set the value to false then restart firefox, then see if that helps with the the problem? If it does not, then try setting gfx.webrender.force-disabled to true, restart, and see if that helps. Thanks.

Blocks: gfx-triage
Severity: -- → S2
Flags: needinfo?(balz.guenat)

(In reply to Jamie Nicol [:jnicol] from comment #7)

Hi Balz,

When this occurs, do any crash reports show up in about:crashes in firefox? If so, could you please share a link here?

Not reports show up.

Could you also please try going to about:config and searching for gfx.webrender.compositor. Set the value to false then restart firefox, then see if that helps with the the problem?

Doesn't help, issue still occurs.

If it does not, then try setting gfx.webrender.force-disabled to true, restart, and see if that helps. Thanks.

Doesn't help, issue still occurs.

Flags: needinfo?(balz.guenat)

Could you also try layers.acceleration.disabled=false, restart, and see if that fixes it? If you navigate to about:support it should now say "Compositing: Basic", can you confirm that is what it says? Thanks.

Flags: needinfo?(balz.guenat)

Ah wait a sec. I made an error. I just noticed that for my previous reply, I had set gfx.webrender.compositor.force-enabled to true instead of gfx.webrender.force-disabled. I will correct this, test again and then update.

Welp, didn't have to wait as long for a crash this time.

layers.acceleration.disabled=false was actually already set to false! I don't remember exactly when I changed this but it's likely one of the first things I tried when I started troubleshooting (even before contacting Nvidia).

However, in about:support, it currently says "Compositing: Direct3D 11 (Advanced Layers)".

Flags: needinfo?(balz.guenat)

Since my last comment, I have uninstalled and reinstalled Firefox. Since that, I have not seen the bug.

Please open about:support, click on "Copy text to clipboard" and paste it here. It would be great if we could compare before and after. I haven't seen a similar bug report.

Keywords: crash
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

This might be something nvidia people can comment on or have some ideas about?

Flags: needinfo?(aleino)
Severity: S2 → S3
Priority: -- → P3

I have same issue with Nvidia RTX 3070. I think it's Firefox fault, because Google Chrome works fine.

Aleino, any ideas about this?

(In reply to Glenn Watson [:gw] from comment #17)

Aleino, any ideas about this?

Do we still have a reliable repro?
Comment 12 suggests that the reporter cannot reproduce anymore since reinstalling firefox.

I believe error event 4101 just means that a GPU operation timed out and reset, which is not much to go on: https://social.technet.microsoft.com/wiki/contents/articles/1462.event-id-4101-display-driver-timeout-detection-and-recovery.aspx

I saw 2-3 issues related to TDRs (TDR=total device reset, which I think would show up as error id 4101), while watching videos in chrome or firefox, posted on our internal bug tracker. I've added pointers to this bug on the mentioned issues.
I'll monitor those issues and report here if something interesting happens.

Meanwhile, if you can provide any more information that would be appreciated. I'll then relay that to the internal Nvidia issues.

Flags: needinfo?(aleino)

Those who can reproduce this, can you try setting media.hardware-video-decoding.enabled=false and see if that avoids the problem?

Flags: needinfo?(denis.shelema)

Actually, this bug was gone after updating nVidia driver to 461.40 version. I forgot to add this info to thread, sorry about that.

Flags: needinfo?(denis.shelema)
Summary: Nvidia display driver crashes when playing Youtube videos → Nvidia display driver (27.21.14.6079) crashes when playing Youtube videos

aleino, do you have any idea what could have changed in 461.40 to have fixed this, and what other driver versions might also have the problem?

Flags: needinfo?(aleino)

(In reply to Jeff Muizelaar [:jrmuizel] from comment #21)

aleino, do you have any idea what could have changed in 461.40 to have fixed this, and what other driver versions might also have the problem?

Both issues I found that seemed related (there was a third, but that was marked a dupe of one of the other two) on Nvidia's internal bug tracker, have been fixed. Two one was fixed in November 2020, and the other one in February 2021.

Probably one of the fixes just made it into 461.40.
Due to some complications of our release scheme, it will take a while before I can determine future proof version ranges for each of the fixes.
I do this periodically for a whole batch of bugs at once, based on a spreadsheet.

I've added this bugzilla issue to the spreadsheet so I won't forget to report the fixed version ranges, once the fixes have propagated enough to tell.

Flags: needinfo?(aleino)
Blocks: gfx-stalled
No longer blocks: gfx-triage
You need to log in before you can comment on or make changes to this bug.