Open Bug 1566405 Opened 6 years ago Updated 3 years ago

Widevine DRM causes Windows bluescreen on pageload

Categories

(Core :: Audio/Video: GMP, defect, P3)

68 Branch
x86_64
Windows 10
defect

Tracking

()

People

(Reporter: code, Unassigned)

Details

(Keywords: crash)

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

Steps to reproduce:

  1. Enable DRM playback in Settings
  2. Go to any Widewine protected page (like the Spotify web player)

Actual results:

Windows bluescreens with stop code FAULT IN NONPAGED AREA. The C:/Windows/MEMORY.DMP file can't be analyzed by WinDbg who says the file is corrupt.

Expected results:

It shoudn't have crashed.

Work-around: Disable Windows Security: Device security: Core isolation: Memory integrity.

Severity: normal → critical
Component: Untriaged → Audio/Video: GMP
Keywords: crash
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → x86_64

Bryce, any thoughts here?

Flags: needinfo?(bvandyk)
Summary: Widewine DRM causes Windows bluescreen on pageload → Widevine DRM causes Windows bluescreen on pageload

I'll reach out to Widevine. None of my Windows machines support the feature so am unable to test this, but I've heard talk to isolation causes issues like this in general (people on Microsoft forums complain of BSODs with the feature on, including FAULT IN NONPAGED AREA).

Unless we get information to the contrary, I expect this will be an issue that Widevine and/or Microsoft will need to resolve in their codebases.

Assignee: nobody → bvandyk
Flags: needinfo?(bvandyk)
Priority: -- → P3
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Daniel, could you navigate to about:support and copy the information provided there to this bug? Could you also let me know the following:

  • Did you recently enable memory integrity?
    • If no, were pages with DRM content previously working?
    • If yes, did these crashes start immediately following enabling it?

Bryce, the feature was enabled by default on my system. I reinstalled Windows 10 on my device myself a couple of weeks ago. However, since disabling the feature I’ve been unable to re-enable it again: I’m warned that my PC is incompatible and it can’t be enabled. Some digging reveals that the feature isn’t enabled on upgrade but is enabled by default on new installations (apparently with no regard to whether the PC support it or not).

Thanks for the further information. It sounds like it's been an issue since the re-installation (until toggling the option off again)?

I'm unclear on what the exact requirements to toggle the option on are. I've tried changing config on a couple of my systems, but nothing seems to appease Windows into letting me toggle the option on.

Widevine have confirmed the bug report and are looking into it on their end, I will update this bug should I hear anything back.

Just tested this on a new machine where I can enable enable memory integrity. I couldn't reproduce, so it's not a certain fail and may be intermittent and/or other factors may contribute.

Sorry, there was a problem with the detection of inactive users. I'm reverting the change.

Assignee: nobody → brycebugemail
Status: NEW → ASSIGNED
Flags: needinfo?(jmathies)

Unassigning bugs assigned to Bryce because he no longer works at Mozilla.

Assignee: brycebugemail → nobody
Status: ASSIGNED → NEW
Severity: critical → S2
Severity: S2 → S4
You need to log in before you can comment on or make changes to this bug.