Display Driver has stopped working and has recovered
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: zelinskyj, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0
Steps to reproduce:
After a recent firefox update every time I load Firefox I get a pop up message that says "Display Driver has stopped working and has recovered"
I have Dell laptop Insprion 15 500 running windows 8
The video is AMD RadEon HD 7730M and Intel HD Graphics 4000
All drivers are up to date
I do not get this message with Google Chrome or Chromium
Actual results:
Everything seems to be running OK after I get the pop up message.
I do not get the error message with any other apps.
Comment 1•4 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 2•4 years ago
|
||
Can you upload the contents of your about:support?
Application Basics
Name Firefox
Version 84.0.2
Build ID 20210105180113
Distribution ID
Update Folder
C:\ProgramData\Mozilla\updates\308046B0AF4A39CB
Update History
Update Channel release
User Agent Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0
OS Windows_NT 6.2 9200
Application Binary C:\Program Files\Mozilla Firefox\firefox.exe
Profile Folder
C:\Users\jerryz\AppData\Roaming\Mozilla\Firefox\Profiles\a6c0wuul.default-1539472960245
Enabled Plugins about:plugins
Build Configuration about:buildconfig
Memory Use about:memory
Performance about:performance
Registered Service Workers about:serviceworkers
Launcher Process Enabled
Multiprocess Windows 1/1
Fission Windows 0/1 Disabled by default
Remote Processes 4
Enterprise Policies Inactive
Google Location Service Key Found
Google Safebrowsing Key Found
Mozilla Location Service Key Found
Safe Mode false
Profiles about:profiles
Comment 4•4 years ago
|
||
I'm mostly looking for the graphics section of about:support, which didn't seem to get included in what you uploaded.
Updated•4 years ago
|
Comment 6•4 years ago
|
||
This is just a copy of the docx file in plain text for ease of reading.
Comment 7•4 years ago
|
||
It looks like the Radeon was not detected by Firefox only the Intel graphics was detected. The driver for it is dated 9-2-2012 which seems really old, I know not all laptop manufacturers keep drivers up to date. But I'm surprised webrender is allowed to run on drivers this old?
And there is a bunch of failures recorded:
Failure Log
(#0) GP+[GFX1-]: shader-cache: Timed out before finishing loads
(#1) GP+[GFX1-]: Present1 failed: 0x887a0005
(#2) GP+[GFX1-]: GFX: RenderThread detected a device reset in WaitForGPU
(#3) GP+[GFX1-]: Failed to make render context current during destroying.
(#4) GP+[GFX1-]: Failed to make render context current during destroying.
(#5) GP+[GFX1-]: Present1 failed: 0x887a0005
(#6) GP+[GFX1-]: GFX: RenderThread detected a device reset in WaitForGPU
(#7) GP+[GFX1-]: Failed to make render context current during destroying.
(#8) GP+[GFX1-]: Present1 failed: 0x887a0005
(#9) GP+[GFX1-]: GFX: RenderThread detected a device reset in WaitForGPU
(#10) GP+[GFX1-]: Failed to make render context current during destroying.
(#11) GP+[GFX1-]: Present1 failed: 0x887a0005
(#12) GP+[GFX1-]: GFX: RenderThread detected a device reset in WaitForGPU
(#13) GP+[GFX1-]: Failed to make render context current during destroying.
Do we expect to allow webrender on a driver this old?
Updated•3 years ago
|
Comment 8•2 years ago
|
||
We should probably block on that driver version, but let's see if the reporter is still experiencing the same issue?
Comment 9•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:gw, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE
if it is not actionable?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 10•2 years ago
|
||
No reply from reporter.
Description
•