Closed Bug 1419264 Opened 7 years ago Closed 7 years ago

Firefox 57.0-58.0b4 & nVidia graphic drivers crash

Categories

(Core :: Graphics, defect, P3)

Product:
Core
Component:
Graphics
Version:
57 Branch
Platform:
Unspecified
Windows
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla59
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox57 --- wontfix
firefox58 + verified
firefox59 --- verified

People

(Reporter: poubelle06210, Assigned: dvander)

References

Details

(Keywords: crash, Whiteboard: [gfx-noted])

Attachments

(11 files)

crash.zip
2.03 KB, application/octet-stream
Details
Event Viewer crash report rar
2.99 KB, application/x-rar
Details
crash 11-23-2017
2.27 KB, application/x-7z-compressed
Details
event viewer log when nvidia display driver stopped working while using Firefox 57
2.89 KB, application/x-7z-compressed
Details
about:support_after_crash.txt
25.41 KB, text/plain
Details
graphic infos after Graphic crash 12-05.txt
8.60 KB, text/plain
Details
ff_log2.txt
24.66 KB, text/plain
Details
about:support with about two driver crashes per day
19.72 KB, text/plain
Details
Firefox Crash Report With As Much Info As Possible
88.10 KB, application/x-rar
Details
patch
1.36 KB, patch
milan
: review+
jcristau
: approval-mozilla-release+
Details | Diff | Splinter Review
cg_about_support.txt
23.85 KB, text/plain
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20171115114231 Steps to reproduce: Once or two times per day, I have a graphic driver crash that seems related to Firefox (it's the only used application each time). Aero transparency is gone, and it's back once I close Firefox. That never happened before the upgrade to Firefox 57. I've tried a new profile, and even a new Windows install, and I still have crashes. It seems a rare bug, but I found an other user, also on Windows 7 and with a nVidia card, who have the same issue. See this two threads on r/firefox: https://www.reddit.com/r/firefox/comments/7dwyr3/am_i_the_only_one_who_experience_graphics_driver/ https://www.reddit.com/r/firefox/comments/7e9l3p/firefox_quantum_keeps_crashing_nvidia_display/ Firefox 57.0 on Windows 7x64, GTX 1060 6GB, GeForce Drivers 388.31 (also happens with 388.13). Right now I'm trying Firefox 58beta to see if the bug is still there. If you need more details, ask me.
Please make sure you have the latest graphics driver: https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
Component: Untriaged → Graphics
Keywords: crash
OS: Unspecified → Windows
Product: Firefox → Core
(In reply to Kohei Yoshino [:kohei] from comment #1) > Please make sure you have the latest graphics driver: > https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware- > acceleration I have the latest, and as I said it was also happening with the previous.
I am the other user with this bug. I've also tried with current, old and beta drivers. I've reinstalled firefox, I've tried disabling my extensions
Here is a sample of the errors I can see in the Windows event viewer: https://www.reddit.com/r/firefox/comments/7dwyr3/am_i_the_only_one_who_experience_graphics_driver/dq1ekie/
Juts had a new crash with 58.0b4
Group: core-security
Here is the logs from the event viewer: https://www.mediafire.com/file/44fmzeb59be1jfs/crash.zip
Summary: Firefox 57.0 & nVidia graphic drivers crash → Firefox 57.0-58.0b4 & nVidia graphic drivers crash
Attached file crash.zip —
log from event viewer
Group: core-security → gfx-core-security
Group: gfx-core-security
An other user have reported the same problem, he's on Windows 10 with latest nVidia drivers. https://www.reddit.com/r/firefox/comments/7dwyr3/am_i_the_only_one_who_experience_graphics_driver/dq887oi/
(In reply to poubelle06210 from comment #9) > And an other one here: > https://www.reddit.com/r/firefox/comments/7e9l3p/ > firefox_quantum_keeps_crashing_nvidia_display/dq7wbo4/ Event viewer data for the crash while browsing a pdf (Win 7 x64 GTX1060 6GB): https://file.io/LoYwan
(In reply to dnn799 from comment #10) > Event viewer data for the crash while browsing a pdf (Win 7 x64 GTX1060 6GB): > > https://file.io/LoYwan 404 not found.
Previous upload 404ed so attaching it to the issue
Attached file crash 11-23-2017 —
Crash log from 11-23-2017
I've been having this same problem daily since I installed Firefox 57. User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 GPU: GTX 1050 Ti 4GB (388.31)
Is anyone at Mozilla investigating this bug ?
(In reply to poubelle06210 from comment #16) > Is anyone at Mozilla investigating this bug ? UNCONFIRMED This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the "canconfirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED. Not yet.
This is also happening to me. Only happened when I moved from chrome to firefox.
Yep. The new FF is causing errors that ends up restarting graphic drivers. These errors typically point to the error in the software and NOT the hardware. I didn't recieve these errors (which I only recieved when I played games that had bad code, rare) until a day after I updated FF and has happened every day. The solution for now is to disable graphics acceleration until they can fix it.
I'm also affected by this. Lots of driver crashes with the log messages "Variable String too Large" and "TEX Exception". Firefox 58 on Windows 7x64, GTX 1050 Ti 4GB, GeForce Drivers 388.31 (also happened with previous driver versions).
I'm also affected by this. With default Hardware Acceleration settings, Firefox 57 crashes 3/4 times a day, at least. I would say it happens most of the time when a new tab starts loading, and has video/heavy content in it. More details : - OS : Windows 7 x64, with 16Gb memory. - GPU hardware : MSI GeForce GTX 1050 Ti GAMING X 4G (NVIDIA) - GPU drivers : GeForce drivers 388.31 (latest), fully reinstalled after running DDU - Was also happening with the previous driver version I'm on a Dual screen, on a single DisplayPort 1.2 connector. I'm pointing this because usually both monitors instantly go in "sleep mode" while browsing, and no way to wake up. Then computer can restart with a BSOD (Dump analyze showed "Probably caused by : nvlddmkm.sys ( nvlddmkm+15f480 )". Sometimes, I can wakeup the monitors by turning then OFF/ON, or disconnecting the DP cable and using HDMI instead. Sometimes, it just reboots. Annoying. Additional information : - I'm running Firefox portable version from Portableapps.com - I also tried a clean install => same - Addons installed : uBlock Origin, Update Scanner, Secure Password Generator, RESTED, Javascript Toggle On and Off Disabling hardware acceleration fixes the problem, but the page display is not smooth, especially when scrolling up/down. And last, it was also happening with previous Firefox version (hardware acceleration ON), but it was really really rare, and always recoverable turning the screens ON/OFF, or connecting HDMI cable instead of HDMI). So since QUANTUM, it's really often, and 95% of the time ends with a BSOD. Frederic
This bug is crashing my graphics stack since weeks. Fresh profile, 57 stable and/or 58 beta. OS : Windows 7 x64, with 16Gb memory. GPU hardware : Asus GeForce GTX 1070 NVIDIA) GPU drivers : GeForce drivers 388.31, clean install (older versions affected as well) The bug often happens when watching videos on Youtube. Really disappointed Mozilla pretends that this bug doesn't exist. They will learn their lesson when less loyal users move to Chrome. I already moved back on the 52 ESR. There needs to be some change of attitude really soon. Yes I'm respecting the netiquette, but indifference from Mozilla isn't nice at all. Will provide crash logs if you tell me how I can. Only the driver crashes, Firefox doesn't close. So I assume I would find nothing about it in any logs created by Firefox itself? Marisa
Since the problem isn't apparent using 52, can someone who is affected track down the regression range using mozregression?
No need to go down to 52, it isn't apparent in 56. I tried to use mozregression, but since I can't easily reproduce the bug (I only have one or two crashes per day), it's very hard to pinpoint where it started. I'm only a user, I can't use mozregression for weeks or even months until I pinpoint the bug. Maybe someone who is more affected (several crashes per days) and have the time and will can do that.
To all the users affected: You can also report the problem to Nvidia via this link: http://www.nvidia.com/object/driverqualityassurance.html Be sure to mention this bug in your feedback, maybe if we are several to report they will investigate, unlike Mozilla...
Flags: needinfo?(milan)
Whiteboard: [gfx-noted]
(In reply to poubelle06210 from comment #26) > To all the users affected: You can also report the problem to Nvidia via > this link: http://www.nvidia.com/object/driverqualityassurance.html > > Be sure to mention this bug in your feedback, maybe if we are several to > report they will investigate, unlike Mozilla... This isn't an NVIDIA problem. These errors relate to problems with the software, not the hardware and NVIDIA will simply tell you they can't (and won't) do anything about it since it's not their problem.
Are there any messages in about:support graphics section when this happens? Is there a browsing pattern (e.g., video, full screen, something else) that causes this to happen more often? Does it happen if the Aero theme is disabled?
Flags: needinfo?(milan)
(In reply to Milan Sreckovic [:milan] from comment #28) > Are there any messages in about:support graphics section when this happens? > Is there a browsing pattern (e.g., video, full screen, something else) that > causes this to happen more often? Does it happen if the Aero theme is > disabled? In my case it happens rarely (1 time in 2 days). It happens when watching a video (only happened on youtube so far, doesn't have to be fullscreen) and while viewing a pdf file in browser(happened only once, although I dont view them daily). When I was viewing the pdf the window sat idly for a few minutes and when trying to scroll with the mouse the window froze for half a second and then the screen turned black for a few seconds until the driver reset. I have two monitors with different resolutions (1920x1080 and 1280x1024). Didn't know about the existence of about:support but I'm going to check it and report back when the bug occurs. I am using Aero. Going to leave it on until I catch the bug once more, then disable it and check if it happens again.
(In reply to Milan Sreckovic [:milan] from comment #28) > Are there any messages in about:support graphics section when this happens? > Is there a browsing pattern (e.g., video, full screen, something else) that > causes this to happen more often? Does it happen if the Aero theme is > disabled? Managed to get the bug to happen again. Switching from a youtube.com tab to a twitch.tv tab made it happen after an hour of watching videos. I am going to attach the failure log from about:support to the issue.
In addition to the previous message. The youtube tab crashed after the driver restarted.
(In reply to Milan Sreckovic [:milan] from comment #28) > Are there any messages in about:support graphics section when this happens? > Is there a browsing pattern (e.g., video, full screen, something else) that > causes this to happen more often? Does it happen if the Aero theme is > disabled? For me there is not particular pattern, it crash sometimes when reading a page (no user action), sometimes when switching to an other tab, it seems very random. I will check about:support graphics section next time a crash happens.
Just had a crash when opening a new tab created by an extension, ViolentMonkey. I have attached the graphic infos.
New crash when browsing a page, I did nothing in particular (#0) CP+[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(154,16488) Code: 0x80070057 format 0 (#8) CP+[GFX1-]: (gfxWindowsPlatform) scheduled device update. (#9) CP+[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3 (#10) CP+[GFX1-]: (gfxWindowsPlatform) scheduled device update. (#11) CP+[GFX1-]: LayerManager::EndTransaction skip RenderLayer(). (#12) GP+[GFX1-]: GFX: D3D11 detected a device reset in Present (#13) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005 (#14) CP+[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3 (#15) CP+[GFX1-]: (gfxWindowsPlatform) scheduled device update. (#16) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005 (#17) CP+[GFX1-]: LayerManager::EndTransaction skip RenderLayer(). (#18) CP+[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3 (#19) CP+[GFX1-]: (gfxWindowsPlatform) scheduled device update. (#20) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005 (#21) CP+[GFX1-]: LayerManager::EndTransaction skip RenderLayer(). (#22) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005
Same issue. Nvidia display drivers crashing repeatedly since switch to Firefox 57. Going back to Chrome for now... Quadro 600, latest drivers. Display driver nvlddmkm stopped responding and has successfully recovered.
So, we have mostly Windows 7, but at least one (or more) Windows 10. One of the Windows 7 with the information is with advanced layers forced on, but I can't tell about the rest. The workflow mentions video, but also PDF. But not everybody reporting the bug reported if there are particular patterns when this occurs. What really helps on a bug like this where things happen on particular hardware, is to eliminate all the other variables (Windows version, non-default preferences) and any workflow more likely to cause it. about:support graphics does that. The about:support attached in comment 31 (thanks dnn799@gmail.com !) just points out Firefox recovering after the driver reset (in earlier versions of Firefox, the driver reset would cause a crash.) For those that have it happen often, if you have time we can see if modifying any of these preferences (in about:config, restart required) makes a difference: * set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false * set media.wmf.vp9.enabled and media.eme.vp9-in-mp4.enabled to false
Another crash yielded a different error log, happened while playing youtube video: (#0) CP+[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(32,24914) Code: 0x80070057 format 0 (#1) GP+[GFX1-]: GFX: AL_D3D11 abandoned sync (#2) GP+[GFX1-]: GFX: D3D11 detected a device reset in Present (#3) GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005 Will attach the whole log to the issue. This as well as my previous crashes happened with the avc1.64002a (299) / mp4a.40.2 (140) codecs which are forced by the h264ify addon.
Attached file ff_log2.txt —
(In reply to Milan Sreckovic [:milan] from comment #38) > For those that have it happen often, if you have time we can see if > modifying any of these preferences (in about:config, restart required) makes > a difference: > > * set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false > * set media.wmf.vp9.enabled and media.eme.vp9-in-mp4.enabled to false I'm still getting crashes with media.wmf.vp9.enabled, media.eme.vp9-in-mp4.enabled and media.wmf.amd.vp9.enabled all set to false. I haven't gotten any crashes in two days with layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled set to false (I did get around two crashes a day before). I'll continue to monitor this, but I guess it would help if someone else could try this as well. As for the usage patterns leading to the crash: Really hard to tell. It does seem to happen more often when playing videos, but it also happens on normal pages. Sometimes it happens while switching tabs, sometimes in the middle of playing a video without any interaction, sometimes while scrolling on a page with text. My gut feeling is that it tends to happen after a certain amount of usage and not right at the start of a session. Maybe someone else can confirm this.
In https://bugzilla.mozilla.org/show_bug.cgi?id=1421262 it was found that since Quantum there is an increased sandbox security level for the Mac, and that it is related to rendering problems on nVidia drivers. A workaround there is to set security.sandbox.content.level to 2. Perhaps the same is at play here?
You can exclude Advanced Layers from the situation, it is not enabled on firefox 56 and the issue is occurring there as well. All instances of this crash are on Release 388 drivers, Release 385 drivers function without issue. I have created an task on nvidia's custhelp site with myself and another users TDR dump files, others should provide feedback in a similar manner and reference the task id of my custhelp feedback which is Ref: # 171218-000117 Please check if you have the Windows 7 platform update installed, as this enables some additional things in the Firefox hardware acceleration (such as decoding video's larger than 1080p in WMF/mp4) Removing it may act as a workaround for the time being, but it is preferrable to just revert to Release 385 drivers or disable Firefox acceleration.
(In reply to poubelle06210 from comment #25) > No need to go down to 52, it isn't apparent in 56. You are wrong.
(In reply to Danial Horton from comment #45) > (In reply to poubelle06210 from comment #25) > > No need to go down to 52, it isn't apparent in 56. > > > You are wrong. I never encountered it before v57, but since you said it is caused by the 388.x and they were released around the same time, it's indeed possible. Downgrading to 385.x is not acceptable, they had a problem with high amount of RAM used by shaders compilation that was corrected in 387.92. https://devtalk.nvidia.com/default/topic/1001276/opengl/excessive-amount-of-ram-used-by-glsl-programs/1 https://www.reddit.com/r/cemu/comments/759gv8/nvidia_ram_fix_official_driver_is_out_38792/ I didn't encountered any crashes since I have set layers.mlgpu.enable-on-windows7 to false, but since the crashes are rare and impossible to reproduce it might just be a coincidence. If I understand correctly, you're implying the problem is caused by Nvidia and not Firefox ?
(In reply to Danial Horton from comment #45) (In reply to poubelle06210 from comment #46) >security.sandbox.content.level;2 Does nothing useful. I can cause crashes in around 5-10mins of use. I just open a few youtube videos, long ones. I open a video on Netflix, then I watch a few webs. \Device\Video7 Variable String too Large \Device\Video7 NVRM: Graphics TEX Exception on (GPC 2, TPC 4): TEX NACK / Page Fault Voila it crashes the NVIDIA driver, but wait! 1) Crashes occur sometimes after hours WITHOUT any videos seen at all 2) can be just a newspaper, switching between tabs Solutions NO_CONSTANT_BUFFER_OFFSETTING Unsupported by driver Error protocol (#0) Error Killing GPU process due to IPC reply timeout (#11) CP+[GFX1-]: (gfxWindowsPlatform) scheduled device update. (#12) CP+[GFX1-]: LayerManager::EndTransaction skip RenderLayer(). (#13) Error Receive IPC close with reason=AbnormalShutdown (#14) Error Receive IPC close with reason=AbnormalShutdown (#15) Error Receive IPC close with reason=AbnormalShutdown (#16) Error Receive IPC close with reason=AbnormalShutdown (#17) CP+[GFX1-]: A content-only TDR is detected. (#18) CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown (#19) CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown (#20) CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown (#21) CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown (#22) CP+[GFX1-]: ClientLayerManager::BeginTransaction with IPC channel down. GPU process may have died. (#23) CP+[GFX1-]: ClientLayerManager::BeginTransaction with IPC channel down. GPU process may have died. (#24) CP+[GFX1-]: ClientLayerManager::BeginTransaction with IPC channel down. GPU process may have died. (#25) CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown So far no about:config solution here worked. For what it is worth I heard there is a debug mode in the NVIDIA driver menu. NVIDIA System-manager > Help > Debug-Mode But I'm no Developer, heard it can catch errors without crashes, might try later but don't count on it. Perhaps moving to the ESR which gives me no bothers.
I have this bug too. I've been using Nightly before and after Quantum and it happens on all versions (now 59.0a1). I have Windows 8.1 64 bit with a nVidia GTX 1080 Ti. It happens since the first driver I've installed for this card, and now I'm on 388.59 and the problem persists. Aside from this bug, the card is completely stable.
My task only covers windows 7 forms of this issue, because on 8 and 10 the tdr system and things firefox does with the api are somewhat different, they might be the same issue but then they might be entirely different. (In reply to poubelle06210 from comment #46) > Downgrading to 385.x is not acceptable, they had a problem with high amount > of RAM used by shaders compilation that was corrected in 387.92. > > https://devtalk.nvidia.com/default/topic/1001276/opengl/excessive-amount-of- > ram-used-by-glsl-programs/1 > > https://www.reddit.com/r/cemu/comments/759gv8/ > nvidia_ram_fix_official_driver_is_out_38792/ > > I didn't encountered any crashes since I have set > layers.mlgpu.enable-on-windows7 to false, but since the crashes are rare and > impossible to reproduce it might just be a coincidence. > > If I understand correctly, you're implying the problem is caused by Nvidia > and not Firefox ? The shaders issue isn't really an 'issue', more that compression is not applied in previous drivers. the more tabs open, especially image heavy tabs - the far more likely it is to happen. I can get a pretty good repro on google image search when clicking a picture to expand its size.
(In reply to Danial Horton from comment #49) > > I can get a pretty good repro on google image search when clicking a picture > to expand its size. Not here.
Anyone want to test removing KB2670838?
(In reply to Danial Horton from comment #52) > Anyone want to test removing KB2670838? This is a terrible idea. The KB is from March 2016, so thinking this KB has to do anything at all with the problems here is highly unlikely. It didn't cause problems for over a year. The problems started when Mozilla introduced Quantum. No other game, software, media player or other piece of code crashed my NVIDIA driver yet. It only happens when surfing with Firefox opened. Please give useful ideas and I will test all I can. Had no luck either with about:config that was suggested. ERROR: CP+[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3 ERROR: CP+[GFX1-]: LayerManager::EndTransaction skip RenderLayer(). ERROR: GP+[GFX1-]: D3D11 swap chain failed to present: 0x887a0005 ERROR: Receive IPC close with reason=AbnormalShutdown ERROR: CP+[GFX1-]: A content-only TDR is detected. ERROR: CP+[GFX1-]: Receive IPC close with reason=AbnormalShutdown > Importance: P3 normal This is making me really REALLY angry. Mozilla is not taking this seriously AT ALL. It literally CRASHED as I typed this message. I demand politely that this BUG is escalated and people who are capable start to work on it. I don't know anymore who can help, the only person I trust here is Bob, please help us :(
Flags: needinfo?(bob.silverberg)
That Platform update. enables things that have introduced web browser instabilities in the past, since firefox makes use of file version checking to enable support for several things it can be a key reason why some Win 7 users are not affected at all. I don't have the ability to remove anything as I have people using a self hosted server on my pc, but someone else should check if removing that KB item is a factor.
FTR: That KB Item is from 2013, and has multiple known unfixed issues that hang games / cause graphical issues Quantum (Advanced layers + Servo) is not even enabled in Firefox 56 and the issue manifests there as I have already demonstrated. The driver is the issue and identifying the actual reason requires an open and curious mind, Don't comment back if you don't have one.
(In reply to Danial Horton from comment #52) > Anyone want to test removing KB2670838? I never had that update installed and I am getting the crashes.
(In reply to Danial Horton from comment #55) > The driver is the issue and identifying the actual reason requires an open > and curious mind, Don't comment back if you don't have one. It is nice that you already identified the reason inside the driver. Care to tell us what part of it causes it? FYI: Cum hoc ergo propter hoc, or correlation does not imply causation. A significant amount of users confirmed the driver operates fine with the other software on their hardware. So saying Firefox is not at fault here is a bold and arrogant claim. > Don't comment back if you don't have one. https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Pretty immature trying to silence helpful posters who offered to test new options. Besides #56 confirmed you are on the wrong track. Once you moved past that fallacy and try not to ego trip we might actually get some work done in here.
(In reply to bugtrackdude from comment #57) > FYI: Cum hoc ergo propter hoc, or correlation does not imply causation. A > significant amount of users confirmed the driver operates fine with the > other software on their hardware. So saying Firefox is not at fault here is > a bold and arrogant claim. Those of us who actually have 15+ years of regression testing experience behind us know better about the ways softwares can interact differently with hardware drivers and trip over issues that other software does not And when an issue is resolved by reverting the driver, Only came about when the driver was updated. And NO FIREFOX UPDATE TO 57 WAS EVER PERFORMED. Well, do the math, if you're able. (In reply to dnn799 from comment #56) > (In reply to Danial Horton from comment #52) > > Anyone want to test removing KB2670838? > > I never had that update installed and I am getting the crashes. (In reply to dnn799 from comment #56) > (In reply to Danial Horton from comment #52) > > Anyone want to test removing KB2670838? > > I never had that update installed and I am getting the crashes. Direct2D 1.1 < You very much DO have that update installed. The non platform update of Direct2D provided with windows 7 and SP1 is 1.0. AFAIK, Advanced layers is not even available on windows 7 without the platform update.
Hey. Started getting this bug with the release of quantum. Have 20 crashes in a month. Used 387.92 before, using 388.59 now. Firefox is the only application causing the crashes. Firefox itself does not crash and hasn't crashed since 2015 (now that's a feat). I'll provide a bunch of different crash logs, not sure where to find them all. When it happens: Random, but mostly viewing pictures or videos or html5. Last time was this site: https://www.magicleap.com/?utm_source=reveal&utm_medium=TW&utm_campaign=WTDO. Crashed when I clicked a icon a bit down (twice, actually).
And a rar containing some info.
Thank you for your comment Danial. Since Firefox Quantum is the only application that causes this problem I did not realize they were without fault. I was using the same driver on 56 as I was on 57 and it did not crash. https://forums.geforce.com/default/topic/1030260/geforce-drivers/windows-7-387-388-accelerated-firefox-tdrs-/post/5262134/#5262134 Maybe it's the 385.69 update then. It's at least good that no other program causes the crashes, hopefully Nvidia can fix this.
Here is a reddit Nvidia user with up to date drivers who's seeing lots of crashes: https://www.reddit.com/r/firefox/comments/7lrfag/nvidia_driver_crashes_while_ff_is_running/ NVIDIA GeForce GTX 1050 Ti Identification of manufacturer 0x10de Identification of hardware 0x1c82 Version of driver 23.21.13.8871 Date of driver 12-15-2017
Testing Nightly 59.0a1, and I currently encounter this issue as well. Happens several times a day, most often when scrolling on a page before all images have finished loading. Using Windows 8.1 x64, EVGA GTX 1060 6GB driver version 388.71 WHQL. I have not rolled back my drivers to test, but I have seen reports of stability issues with the 388.x driver set. I may set aside some time later next week to clean install some older drivers to see if the issue persists, as that would point to the drivers being more at fault.
Since I turned off hardware acceleration and turned only layers.mlgpu.enable-on-windows7 to false I haven't had my drivers crash once. layers.mlgpu.enabled is default value. Just if anyone want to try a temporary fix.
You don't have Advanced Layers without Hardware Acceleration.
It's been more than 15 days that I've turned layers.mlgpu.enable-on-windows7 to false and I didn't encountered a single crash since.
Presumably the layers.mlgpu.enable-on-windows7 option doesn't have an effect on Windows 8 and 10, right?
https://forums.geforce.com/default/topic/1032646/geforce-drivers/eventid-13-source-nvlddmkm-driver-timeout/ Same problem, I've posted some details on nvidia forum. Also I think the problem can be in nvidia driver since 38x. ? I bought my 1050 in september and never expiriensed that bug until I've upgrade nvidia driver/firefox to 57 and installed cumulative windows 7 updates, that bug only in firefox, I can play for hours in any heavy game or watch movie in player with hw acceleration and nothing. Disabling HW acceleration in firefox not solution. Also I have different setups with AMD gpu (which always have hw acceleration problems in mozilla with newest drivers) and with oldest nvidia cards too (730GT GDDR5 and 650Ti both on windows 10 with newest driver) but never experienced that bug on that setups. Someone need to investigate that bug deeply it's totaly impossible to use mozilla.
(In reply to Asif Youssuff from comment #68) > Presumably the layers.mlgpu.enable-on-windows7 option doesn't have an effect > on Windows 8 and 10, right? For me it has no effect, what can I do? This topic is a dead end. People are to stubborn to comprehend it is of course Mozilla's fault when they implement layers in an unsafe way. How ignorant can a person be? I tried the last 7 drivers NVIDIA released. Even those confirmed stable for Firefox on NVIDIA forums. It simply has no effect at all. The bug has been observed on Win 7 / 8 / 10 but mostly on 7. Nobody ever said it was just Quantum. FF56 was already a horrible mess. The ESR it is then for me, and if ESR 60 next year fails in the trash Mozilla goes. Chromium is at least more privacy respecting than Mozilla Mr Robot spyware addon, forced telemetry and pingsender.exe or Cliqz, Pocket and other XPI pushed malware. I give a big finger to the ignorant people her that will never fix this bug. How hard can it be for a developer to write a test with layers and run it step by step to see at which point it crashes the driver? Your attribution game and blamign NVIDIA is weak. 10 crashes a day, I ain't joking.
They use the API's available to them as it permits, stop blaming the software for issues it exposes on your unstable computer setup.
(In reply to Danial Horton from comment #71) > They use the API's available to them as it permits, stop blaming the > software for issues it exposes on your unstable computer setup. Firefox is the only application that trigger the crashes.
Oblivion was the only game that exposed unstable shader overclocks on Tesla gpu's. Your point is null.
(In reply to Danial Horton from comment #71) > They use the API's available to them as it permits, stop blaming the > software for issues it exposes on your unstable computer setup. What an ignorant thing to say when all software I use runs without issues. I play a lot of games on my GTX 1080 and never ever did my driver crash with a a different process than firefox.exe so you can stop pretending you are contributing. Someone who has nearly 900 posts on here and the only bugs 8 fixed. Being a backseat driver and not contribute anything with ignorant comments when you imply it is our setup. The avatar tells enough, I doubt you would act to fellow people like this in the real world. Strange that Chrome, ESR, Waterfox, etc run without issues. Surely must be me and my PC, totally not something in the FF 56-59 code. (In reply to poubelle06210 from comment #72) > Firefox is the only application that trigger the crashes. Thank you for reassuring that your PC runs stable too with every other program running. (In reply to Danial Horton from comment #73) > Your point is null. You comment is useless, unhelpful and rude and you act like this towards everyone in this topic. Saying Mozilla can never be at fault is dogmatism. I really try to get Anthony into this topic, perhaps he can help or at least delete these Danial posts that contribute nothing.
Flags: needinfo?(anthony.s.hughes)
The only ignorant things being said here are the posts saying "but everything else works" - - Driver is shown to crash in Gears of War 4 to BSOD/Freeze but not in any other games. - The driver 388.59 and earlier had a BSOD crash in Heaven Benchmark under particular conditions But please, continue to show a complete ignorance to display driver functionality if it makes you feel better.
(In reply to Danial Horton from comment #75) > The only ignorant things being said here are the posts saying "but > everything else works" - > > - Driver is shown to crash in Gears of War 4 to BSOD/Freeze but not in any > other games. > - The driver 388.59 and earlier had a BSOD crash in Heaven Benchmark under > particular conditions > > But please, continue to show a complete ignorance to display driver > functionality if it makes you feel better. If you stop being so passive aggressive and triggered at everything. http://www.nvidia.com/download/driverResults.aspx/123217/en-us My driver is not the one you say: Version: 385.41 WHQL Release Date: 2017.8.24 Operating System: Windows 7 64-bit, Windows 8.1 64-bit, Windows 8 64-bit Language: English (US) File Size: 395.25 MB You cannot read, nor does your mental text parser work at all. Tried 7 different ones, this is the $current. (In reply to Danial Horton from comment #58) > And when an issue is resolved by reverting the driver, Only came about when > the driver was updated. And NO FIREFOX UPDATE TO 57 WAS EVER PERFORMED. > Well, do the math, if you're able. Several versions of Firefox tested AGAINST several drivers. Result is always you throwing a temper tantrum and the the browser of people crashing. Just had to quote this if you have even a quantum (no pun intended) of self-perception. You need to treat the people around you better or at least take them seriously. mv /dev/sanity /dev/null If the internet historians ever find this thread they will see why and how Firefox disappeared from the browser world map in 2017 A.D. https://upload.wikimedia.org/wikipedia/commons/e/e1/StatCounter-browser-ww-monthly-201707-201707-map.png (the tiny spec still using it, only Cuba and Haiti I presume)
I'm not the triggered one mate, that would be only the group of people who assume a driver working under less system-intensive scenario's. can't be unstable in more specific DMA intensive situations. But thanks for projecting, If I don't have someone do that atleast once a day something is wrong. I'll get the issue fixed for you with or without your help on the end its actually on instead of harassing Mozilla about it.
Some background: Since the drivers are not perfect, there are a number of workarounds that Firefox puts in place in order to avoid trigger the bugs in drivers. And for a "simple web browser", Firefox is fairly unique in what it asks for, so it is quite normal for it to be the only application (in any volume) to trigger a particular driver issue. Then there are the times when Firefox does something wrong, but gets away with it for a while, until an updated drivers closes the door, and the bug is triggered. It is still important for us to figure out when something started and if it's particular to a driver or an OS update. Not to blame and walk away, but to get more information about how to fix it. If the problem is on "active" driver branch and hardware, the fix is often coming, but if it's something old, chances are Firefox will have to work around it anyway. And the more we know, the less need there is for the big hammer of disabling the hardware usage on the particular hardware/driver combination. Bas, David - there is some indication that MLGPU on Windows 7 triggers the problems more often (if not exclusively), combined with the "it also happens on 56, which doesn't have MLGPU". Was there something that would have changed on the non-MLGPU code path at 57 or later? As in, once MLGPU was introduced, did the other path change?
Flags: needinfo?(dvander)
Flags: needinfo?(bas)
(In reply to poubelle06210 from comment #67) > It's been more than 15 days that I've turned layers.mlgpu.enable-on-windows7 > to false and I didn't encountered a single crash since. And I confirm this 1 week later.
Just in case anyone is wondering this issue is real NVIDIA GeForce 1060 3GB Driver 388.31 Windows 7 64bit Firefox 57.0.3 Been crashing an average of once per day ever since I upgraded to Firefox Quantum
Hi, I've had the same problem ever since my Firefox updated to 'Quantum.' My video driver fails at least once a day when FF is running. I keep hoping the next Quantum or Nvidia update fixes this, but it still hasn't happened. I've tried rolling back my drivers to 387.xx because I only recall the crashing starting since 388; it hasn't helped. I've tried layers.mlgpu.enable-on-windows7 to false and that hasn't worked. I've also tried that and unchecking 'Use Hardware Acceleration' in the FF options: they have not fixed the problem. I don't know what else to try. I think I'll just revert to non-quantum until they figure this out. NVIDIA Geforce 1070 Windows 7 64
Interesting that turning off hardware acceleration (and restarting?) didn't help. That is rather unexpected. Any chance of running mozregression tool [1] to find out when this problem started? It would give us details beyond "started in 57" and would help us figure out the cause. [1] http://mozilla.github.io/mozregression/quickstart.html
Flags: needinfo?(TaffingAround)
It seems different issues are hidden in the same symptoms (Nvidia graphic driver crashes), as I said both times, disabling layers.mlgpu.enable-on-windows7 was enough to stop the issue on my end.
My gut reaction is to blocklist AL on NVIDIA + Win7. But I'd first like to look at our Telemetry and see if there are correlations between TDRs and AL, comparing Firefox 56 to 57.
It looks like device resets with reason=3 are disproportionately high for NVIDIA users on Windows 7. On Windows 10, 17% of reason=3 TDRs are NVIDIA. On Windows 7, *67%* of reason=3 TDRs are NVIDIA. I can't find any evidence that correlates this with Advanced Layers. Those ratios are the same on Firefox 56 versus 57. Given the anecdotal evidence though, it's possible that AL exacerbates some existing problem. I'll try to see if there's a narrow blocklist entry we can make.
(In reply to David Anderson [:dvander] from comment #85) > It looks like device resets with reason=3 are disproportionately high for > NVIDIA users on Windows 7. On Windows 10, 17% of reason=3 TDRs are NVIDIA. > On Windows 7, *67%* of reason=3 TDRs are NVIDIA. > > I can't find any evidence that correlates this with Advanced Layers. Those > ratios are the same on Firefox 56 versus 57. Given the anecdotal evidence > though, it's possible that AL exacerbates some existing problem. I'll try to > see if there's a narrow blocklist entry we can make. Those findings seem believable to me, I'd be somewhat surprised if AL somehow disproportionately affected this.
Flags: needinfo?(bas)
My apologies, but I'm not sure why I was needinfo'd on this bug. I have no knowledge nor expertise in this area, and it's not something my team works on.
Flags: needinfo?(bob.silverberg)
(In reply to Milan Sreckovic [:milan] from comment #82) > Interesting that turning off hardware acceleration (and restarting?) didn't > help. That is rather unexpected. Any chance of running mozregression tool > [1] to find out when this problem started? It would give us details beyond > "started in 57" and would help us figure out the cause. > > [1] http://mozilla.github.io/mozregression/quickstart.html You know what, maybe I didn't restart after turning off hardware acceleration. I think it crashed seconds after I turned it off so I assumed that didn't work. I did leave it off and have restarted the browser since then and so far it hasn't crashed so maybe it did work. I'll update if it crashes again. For now I guess those two options together DO work after a restart. I can definitely say they don't work separately cause I tried both separately before. Sorry about that
Flags: needinfo?(TaffingAround)
There is a slight correlation to a few devices IDs, 0x1287, 0x128b, 0x1c03, 0x1c82 in particular. There is a much stronger correlation with driver version: 23.21.13.8813, .8869, and .8871 make up the majority of these device resets. Both of the about:support dumps in this bug have one of those devices or driver versions. A straight-up driver entry in the blocklist would affect about 2% of Windows 7 users. It might be possible to narrow it down further, but I think this is the best approach for now.
Assignee: nobody → dvander
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Flags: needinfo?(dvander)
Attached patch patch — — Splinter Review
This will downgrade affected Windows 7 machines to the old Direct3D 11 compositor. If the Win7 NVIDIA TDR rate doesn't change after this patch, we should probably just block D3D11 entirely. (Also, it's possible NVIDIA doesn't fix this issue in the next release, and we have to keep extending the tail end of the range.)
Attachment #8940878 - Flags: review?(milan)
(In reply to David Anderson [:dvander] from comment #90) > (Also, it's possible NVIDIA doesn't fix this issue in the next release, and > we have to keep extending the tail end of the range.) Well I haven't used your attachment but I can say I'm still having this exact issue on the latest driver that just came out yesterday (v 390.65)
I can confirm that yesterday's driver still has the issue. I run Windows7 x64 with a 1060 6GB. When the crash happens I can't even bring up the task manager or anything, the screen goes completely black, no monitor signal, and I have to reboot the system. Reproducing the crash is difficult, but it seems to happen excessively when using Google Maps and going into or out of a satellite or street view.
cg or Scruffy, could you attach a copy of your about:support?
Flags: needinfo?(cg)
Flags: needinfo?(DeScruffsoftware)
Attached file cg_about_support.txt —
The about:support from my machine (I get frequent crashes to an entirely black screen with loss of monitor signal, very often triggered on Google Maps but also randomly on other websites)
Flags: needinfo?(cg)
Comment on attachment 8940878 [details] [diff] [review] patch Review of attachment 8940878 [details] [diff] [review]: ----------------------------------------------------------------- ::: widget/windows/GfxInfo.cpp @@ +1369,5 @@ > + APPEND_TO_DRIVER_BLOCKLIST_RANGE(OperatingSystem::Windows7, > + (nsAString&) GfxDriverInfo::GetDeviceVendor(VendorNVIDIA), GfxDriverInfo::allDevices, > + nsIGfxInfo::FEATURE_ADVANCED_LAYERS, nsIGfxInfo::FEATURE_BLOCKED_DRIVER_VERSION, > + DRIVER_BETWEEN_INCLUSIVE, V(23,21,13,8813), V(23,21,13,8871), > + "FEATURE_FAILURE_BUG_1419264", "Windows 10"); I guess we are recommending to the user to switch to Windows 10, rather than a newer driver, as we don't know a newer driver will ever come or fix the problem. This is why we have "Windows 10" as the last entry in the macro above?
Attachment #8940878 - Flags: review?(milan) → review+
(In reply to Milan Sreckovic [:milan] from comment #95) > Comment on attachment 8940878 [details] [diff] [review] > patch > > Review of attachment 8940878 [details] [diff] [review]: > ----------------------------------------------------------------- > > ::: widget/windows/GfxInfo.cpp > @@ +1369,5 @@ > > + APPEND_TO_DRIVER_BLOCKLIST_RANGE(OperatingSystem::Windows7, > > + (nsAString&) GfxDriverInfo::GetDeviceVendor(VendorNVIDIA), GfxDriverInfo::allDevices, > > + nsIGfxInfo::FEATURE_ADVANCED_LAYERS, nsIGfxInfo::FEATURE_BLOCKED_DRIVER_VERSION, > > + DRIVER_BETWEEN_INCLUSIVE, V(23,21,13,8813), V(23,21,13,8871), > > + "FEATURE_FAILURE_BUG_1419264", "Windows 10"); > > I guess we are recommending to the user to switch to Windows 10, rather than > a newer driver, as we don't know a newer driver will ever come or fix the > problem. This is why we have "Windows 10" as the last entry in the macro > above? Yeah... though, now we're seeing *.13.9065 is bad too. How do you feel about making the macro have no upper limit?
Flags: needinfo?(milan)
(In reply to David Anderson [:dvander] from comment #96) > > Yeah... though, now we're seeing *.13.9065 is bad too. How do you feel about > making the macro have no upper limit? Yes please.
Flags: needinfo?(milan)
Could the same issue happen to me in Windows 8.1? Is there a way to know for sure what's crashing the driver so I can send it to nvidia? I contacted nvidia about this issue and they told me to just stop using Firefox.
Pushed by danderson@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ac3bbc830d18 Block Advanced Layers on the latest Windows 7 NVIDIA drivers. (bug 1419264, r=milan)
https://hg.mozilla.org/mozilla-central/rev/ac3bbc830d18
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox59: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Not fixed for 58 ? Why ?
David, should we uplift this blocklist change for 58 rc2? If so we'd need an uplift request today.
Flags: needinfo?(dvander)
I'm not sure what the outcome of the technical discussion was, but I want to mention that this: "set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false" did not resolve the issue for me. I set these options to False yesterday, and five minutes ago I had another one of those lovely crashes.
(In reply to cg from comment #103) > "set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false" > did not resolve the issue for me. I set these options to False yesterday, > and five minutes ago I had another one of those lovely crashes. What's your driver version ? Did you have restarted Firefox after changing the value ?
(In reply to poubelle06210 from comment #104) > (In reply to cg from comment #103) > > "set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false" > > did not resolve the issue for me. I set these options to False yesterday, > > and five minutes ago I had another one of those lovely crashes. > > What's your driver version ? > Did you have restarted Firefox after changing the value ? Driver is 390.65 Yes, I did restart after changing the values.
Comment on attachment 8940878 [details] [diff] [review] patch Approval Request Comment [Feature/Bug causing the regression]: NVIDIA driver update [User impact if declined]: Driver resets, causing browser crashes [Is this code covered by automated tests?]: [Has the fix been verified in Nightly?]: [Needs manual test from QE? If yes, steps to reproduce]: [List of other uplifts needed for the feature/fix]: [Is the change risky?]: No [Why is the change risky/not risky?]: It's a hardware blocklist entry that is only for certain NVIDIA users on Windows 7. Performance degradation should be small since we'll still use a Direct3D11 compositor. [String changes made/needed]:
Flags: needinfo?(dvander)
Attachment #8940878 - Flags: approval-mozilla-beta?
(In reply to cg from comment #103) > I'm not sure what the outcome of the technical discussion was, but I want to > mention that this: > "set layers.mlgpu.enable-on-windows7 and layers.mlgpu.enabled to false" > > did not resolve the issue for me. I set these options to False yesterday, > and five minutes ago I had another one of those lovely crashes. That makes sense to me - I didn't see any evidence in our telemetry that would correlate device resets to advanced layers. Most likely this affects all D3D11 composition in Firefox. I'll try to gather some data today/tomorrow to see whether this patch affected the TDR rate, and if not, we'll have to do something else.
Hey Milan, your blocklist is lacking. the affected range is 385.69 - 390.65 and only affects pascal devices. Drivers 385.41 and lower work perfectly with Firefox Quantum, 56, Waterfox and older versions.
(In reply to Milan Sreckovic [:milan] from comment #78) > Some background: > > Bas, David - there is some indication that MLGPU on Windows 7 triggers the > problems more often (if not exclusively), combined with the "it also happens > on 56, which doesn't have MLGPU". Was there something that would have > changed on the non-MLGPU code path at 57 or later? As in, once MLGPU was > introduced, did the other path change? Replying to this, I remained on Firefox 56 beta 12 for some time after 57 released as it was the only way to retain plugin compatibility + netflix capability (the addon dev edition release versions have no netflix capability at all) until waterfox released v56 - since waterfox 55 didn't use the newer storage formats i would have lost session info otherwise. In this time, I had no problems with hardware acceleration on 385.41, and skipped 385.69 to go straight to 388.13. Issues only started with TDR's at this point, Initially It was thought that 388 was the regression point, but others have now confirmed that 385.69 is the first build with TDR's and 385.41 continues to run perfectly in 56 and older, 57 and Waterfox. Users have encountered TDR's GeForce Game Ready Driver WHQL 390.65 January 8, 2018 GeForce Game Ready Driver WHQL 388.71 December 20, 2017 GeForce Game Ready Driver WHQL 388.59 December 7, 2017 GeForce Game Ready Driver WHQL 388.43 November 30, 2017 GeForce Game Ready Driver WHQL 388.31 November 15, 2017 GeForce Game Ready Driver WHQL 388.13 October 30, 2017 GeForce Game Ready Driver WHQL 388.00 October 23, 2017 GeForce Game Ready Driver WHQL 387.92 October 9, 2017 GeForce Game Ready Driver WHQL 385.69 September 21, 2017 With GeForce Game Ready Driver WHQL 385.41 August 24, 2017 being the last firefox solid driver. I run a pretty heavy test case for firefox stability by having many tabs, and multiple instances open, so I had a fair idea that the drivers were not stable from the start. Nvidia has handed my task over to Level 2 engineers, you could get dev-rel with them and cite the task i created for this issue Ref: # 171218-000117
And for those who keep hitting this bugzilla and reporting to reddit that a "FIX" worked. 1. Disabling Hardware Acceleration is a workaround, not a fix. 2. Disablng Hardware Acceleration encompasses all Layer acceleration, you do not combine it with layers.mlgpu.enable-on-windows7 and claim a fix, the latter doesn't fix anything, and the former turns everything relevant off.
Comment on attachment 8940878 [details] [diff] [review] patch let's take this blocklist addition in 58 rc2.
Attachment #8940878 - Flags: approval-mozilla-beta? → approval-mozilla-release+
Flags: needinfo?(DeScruffsoftware)
I did a quick Telemetry analysis against Firefox 59 builds with a build_id including the blocklist patch. I confirmed that these submissions were using CompositorD3D11 instead of Advanced Layers. Indeed, the TDR rate is still abnormally high for NVIDIA. So while the blocklist entry may have some impact on the worst cases, likely many users will still get TDRs. An option would be to see if a more narrow blocklist entry would work (like based on device IDs) and then use that to block D3D11 entirely. Milan pointed out that it could be a risky game to play, since we don't want users on those cards to lose D3D11 if just a small percentage of them will get device resets. But maybe it's possible to make the blocklist even more narrow.
Still occurs in Firefox 58 on beta channel
(In reply to David Anderson [:dvander] - inactive, e-mail if emergency from comment #114) > An option would be to see if a more narrow blocklist entry would work (like > based on device IDs) and then use that to block D3D11 entirely. Milan > pointed out that it could be a risky game to play, since we don't want users > on those cards to lose D3D11 if just a small percentage of them will get > device resets. But maybe it's possible to make the blocklist even more > narrow. Here's a desktop list of affected cards if it can NVIDIA_DEV.1B00 = "NVIDIA TITAN X (Pascal)" NVIDIA_DEV.1B02 = "NVIDIA TITAN Xp" NVIDIA_DEV.1B02.123E.10DE = "NVIDIA TITAN Xp COLLECTORS EDITION" NVIDIA_DEV.1B02.123F.10DE = "NVIDIA TITAN Xp COLLECTORS EDITION" NVIDIA_DEV.1B06 = "NVIDIA GeForce GTX 1080 Ti" NVIDIA_DEV.1B80 = "NVIDIA GeForce GTX 1080" NVIDIA_DEV.1B81 = "NVIDIA GeForce GTX 1070" NVIDIA_DEV.1B82 = "NVIDIA GeForce GTX 1070 Ti" NVIDIA_DEV.1B84 = "NVIDIA GeForce GTX 1060 3GB" NVIDIA_DEV.1C02 = "NVIDIA GeForce GTX 1060 3GB" NVIDIA_DEV.1C03 = "NVIDIA GeForce GTX 1060 6GB" NVIDIA_DEV.1C04 = "NVIDIA GeForce GTX 1060 5GB" NVIDIA_DEV.1C06 = "NVIDIA GeForce GTX 1060 6GB" NVIDIA_DEV.1C81 = "NVIDIA GeForce GTX 1050" NVIDIA_DEV.1C82 = "NVIDIA GeForce GTX 1050 Ti" NVIDIA_DEV.1D01 = "NVIDIA GeForce GT 1030" Possibly affected NVIDIA_DEV.1D81 = "NVIDIA TITAN V"
Just to add, I also have TDR crashes (random) with NVIDIA_DEV.1C03 = "NVIDIA GeForce GTX 1060 6GB" on W7. They are rare, but the occur. For me, whole system just freezes for about 10-20 seconds, and the driver recovers. What is unusal on this recovery, it adds another nVidia HDMI Audio Device. So I have to reset whole PC, to regain normal funcionality of software linked to HDMI Audio (such as VLC).
NVIDIA_DEV.1C03 (also mine) is in the blacklist starting from 58.0. You can download 58.0 final here: http://ftp.mozilla.org/pub/firefox/releases/58.0/
So 58 works normally with HW acceleration and without TDR?
(In reply to poubelle06210 from comment #118) > NVIDIA_DEV.1C03 (also mine) is in the blacklist starting from 58.0. You can > download 58.0 final here: http://ftp.mozilla.org/pub/firefox/releases/58.0/ So 58 works normally with HW acceleration and without TDR?
It seems so, I have updated to 58 final yesterday (I re-enabled layers.mlgpu.enable-on-windows7 before updating) and I don't encountered any crashes so far, but it's a little early to be sure.
(In reply to poubelle06210 from comment #121) > It seems so, I have updated to 58 final yesterday (I re-enabled > layers.mlgpu.enable-on-windows7 before updating) and I don't encountered any > crashes so far, but it's a little early to be sure. OK, Update it. Will see how it works. I'm insterested when will 58 be official.
Already available on the ftp, it will be official tomorrow.
(In reply to animeyu from comment #120) > (In reply to poubelle06210 from comment #118) > > NVIDIA_DEV.1C03 (also mine) is in the blacklist starting from 58.0. You can > > download 58.0 final here: http://ftp.mozilla.org/pub/firefox/releases/58.0/ > > So 58 works normally with HW acceleration and without TDR? No, the blacklist disables on the affected drivers / gpu's and restricts the Compositor to Basic mode which means no advanced layers, no sync on vrefresh or any other hardware features. it is all mozilla can do until nvidia finds and fixes whatever they broke between 385.41 and 385.69
Well....nope. 58 crashed right now. about:crashes doesn't say anything about it.
(In reply to animeyu from comment #125) > Well....nope. 58 crashed right now. about:crashes doesn't say anything about > it. Then this an other issue, this bug is about NVIDIA drivers crashing (TDR) when using Firefox, not Firefox crashing.
True. Hope they fix drivers and at least make them stable as version I'm using currently. Because the only thing that crashes is FF. 385.69 up to 390.65 are having this problem: https://forums.geforce.com/default/topic/1030260/geforce-drivers/windows-7-and-drivers-385-69-388-xx-accelerated-firefox-tdrs-/
Firefox 58 installed, and after 5 minutes of using it I had another one of those same random black screen crashes. Whatever was fixed didn't fix it for me.
With Firefox 57, I didn't had any crashes once layers.mlgpu.enable-on-windows7 set to false. With Firefox 58 (layers.mlgpu.enable-on-windows7 reset to true), no crash either. OS: Windows 7 x64 up to date. Graphic card: NVIDIA_DEV.1C03 = "NVIDIA GeForce GTX 1060 6GB" with latest drivers (390.65)
Sorry Poubelle, but i can only conclude that you have disabled hardware acceleration overall as the layers setting has no impact for any other user.
I find you condescending Danial Horton, I still know how to use & configure software, and I would absolutely notice if the hardware acceleration was disabled. Also, several users on /r/firefox have said the crashes had stopped once layers.mlgpu.enable-on-windows7 was set to false. example: https://www.reddit.com/r/firefox/comments/7lrfag/nvidia_driver_crashes_while_ff_is_running/drpdafq/ In about:config, , I can see hardware acceleration is enabled, only WEBRENDER and ADVANCED_LAYERS are disabled. I can also see some failures: CP+[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(20,24000) Code: 0x80070057 format 0
I mean about:support of course.
I don't care how you find me, that's your concern. >CP+[GFX1-]: [D2D1.1] 4CreateBitmap failure Size(20,24000) Code: 0x80070057 format 0 It might not have TDR'd yet, but that's a symptom of the issue. 385.41 and earlier have a clean failure list, and like David has ascertained, the advanced layers blacklist did not alter the rate at all. A user on evga forums claimed waterfox 56.0 to have fixed it for him only to return many days later saying the issues were still present. Waterfox 56 has no advanced layers, or stylo, the problem can not be present for days, then happen multiple times on the same tab - too occuring immediately on firefox start before the tab has rendered. And 385.41 has no reproduction after weeks.
Waterfox never made the Nvidia drivers crashes here.
(In reply to mooms from comment #134) > Waterfox never made the Nvidia drivers crashes here. Yet.
FF updated itself to 59.0b4 and had about 5 crashes since. Nothing is touched in about:config and hardware acc. is not disabled. Today I had 2 crashes in about 10 or so minutes. Strange thing is that about:crashes doesn't give any "report" so I can check upon or send. That also goes for version 58 that I was on until update. Wil try with layers.mlgpu.enable-on-windows7 to false, to see if it will trigger TDR.
Nvidia has put this in research status, they have reproductions but not consistent enough to root cause the regression.
It seems that layers.mlgpu.enable-on-windows7 works. No TDRs for now.
FYI, even setting these 2 preferences: - layers.mlgpu.enable-on-windows7 - layers.mlgpu.enabled to true in about:config (if they aren't set like that by default already) won't be changing anything, as this bug (bug #1419264) blacklisted all NVIDIA GPU drivers from versions 388.13 to even latest which are 390.77. You can check it by seeing only: > Compositing Direct3D 11 not this one: > Compositing Direct3D 11 (Advanced Layers) under "Features" in "Graphics" section in about:support, and by seeing: > ADVANCED_LAYERS >> available by user: Enabled for Windows 7 via user-preference >> Blocklisted due to known issues; bug 1419264 under "Decision Log" in "Graphics" section in about:support. Blacklist should starts from version 385.69, which is first bugged NVIDIA GPU drivers version according to reports. Bug about it is in bug #1433058.
Status: RESOLVED → VERIFIED
status-firefox58: fixed → verified
status-firefox59: fixed → verified
QA Contact: Virtual
(In reply to animeyu from comment #138) > It seems that layers.mlgpu.enable-on-windows7 works. No TDRs for now. For me it doesnt work anymore :(
(In reply to Flo from comment #140) > (In reply to animeyu from comment #138) > > It seems that layers.mlgpu.enable-on-windows7 works. No TDRs for now. > > For me it doesnt work anymore :( Read the post(s) above yours, advanced layers are blacklisted (disabled) on all GeForce 1xxx series since Firefox 58.0, so this pref is useless. If you still have TDR ( graphic driver crashes) it's not caused by advanced layers.
See also this thread: https://forums.geforce.com/default/topic/1030260/geforce-drivers/windows-7-and-drivers-385-69-388-xx-accelerated-firefox-tdrs-/7/ NVIDIA is working on it, and hopefully it will be fixed soon in the drivers.
Actually I was on 58 and now on 59.0b and on both layers.mlgpu.enable-on-windows7 are working for me.
(In reply to animeyu from comment #143) > Actually I was on 58 and now on 59.0b and on both > layers.mlgpu.enable-on-windows7 are working for me. What do you mean by "are working" ? Are you on the latest NVIDIA drivers ? Do you use Windows 7 ? Do you have a GeForce 1xxx ? As I already said, advanced layers are disabled on Windows 7 on all GeForce 1xxx series since Firefox 58.0 because all recent drivers are blacklisted to avoid them crashing, so AFAIK this pref should not do anything.
I have the same problem for months now: the NVidia driver crashes 4 to 5 times a day when firefox is open. Every time when there is a new nvidia driver update, I install it in the hope that the problem is fixed at least on the driver's end. Currently 390.77 is installed. Setting layers.mlgpu.enable-on-windows7 to false seems to do nothing on my system.
Forgot to mention that I upgraded my system 2 weeks ago: I installed a new NVidia card, a new motherboard and a new CPU. But the problem persists :-( So it's clearly a firefox and/or driver problem.
Are you on Windows 7 ?
(In reply to mooms from comment #147) > Are you on Windows 7 ? Yes, W7 64bit
As a temporary workaround, try to disable hardware acceleration in Firefox.
Thank you, I already tried this yesterday. No driver crashes since. I will stick to this mode until the problem is resolved.
(In reply to mooms from comment #144) > (In reply to animeyu from comment #143) > > Actually I was on 58 and now on 59.0b and on both > > layers.mlgpu.enable-on-windows7 are working for me. > > What do you mean by "are working" ? > Are you on the latest NVIDIA drivers ? > Do you use Windows 7 ? > Do you have a GeForce 1xxx ? > > As I already said, advanced layers are disabled on Windows 7 on all GeForce > 1xxx series since Firefox 58.0 because all recent drivers are blacklisted to > avoid them crashing, so AFAIK this pref should not do anything. 1. Working, when layers is disabled (false) within about:config. 2. Not latest, but on 387.92, which is currently stable. I always pick stable driver which do not rise temp, TDR every few minutes or so and so on. 3. Yes, W7 4. Yes, GTX 1060.
(In reply to mooms from comment #144) > (In reply to animeyu from comment #143) > > Actually I was on 58 and now on 59.0b and on both > > layers.mlgpu.enable-on-windows7 are working for me. > > What do you mean by "are working" ? > Are you on the latest NVIDIA drivers ? > Do you use Windows 7 ? > Do you have a GeForce 1xxx ? > > As I already said, advanced layers are disabled on Windows 7 on all GeForce > 1xxx series since Firefox 58.0 because all recent drivers are blacklisted to > avoid them crashing, so AFAIK this pref should not do anything. Forgot to add, that 58 and 59b crashes for me when layers are on true and with HW acc. ON. When HW acc remains ON, and layers are put on false I do not have any crash. So it seems that integrated "blacklist" doesn't work at all.
(In reply to animeyu from comment #152) > Forgot to add, that 58 and 59b crashes for me when layers are on true and > with HW acc. ON. When HW acc remains ON, and layers are put on false I do > not have any crash. So it seems that integrated "blacklist" doesn't work at > all. In about:support I can see advanced layers are blacklisted: "name": "ADVANCED_LAYERS", "description": "Advanced Layers", "status": "blacklisted", Try this: - Enable the pref layers.mlgpu.enable-on-windows7 again, restart Firefox. - Go in about:support, copy the text in the clipboard, paste it in a text file and attach it here. With these info we will see if your GPU/drivers are blacklisted or not. See also bug #1433058
(In reply to mooms from comment #153) > (In reply to animeyu from comment #152) > > Forgot to add, that 58 and 59b crashes for me when layers are on true and > > with HW acc. ON. When HW acc remains ON, and layers are put on false I do > > not have any crash. So it seems that integrated "blacklist" doesn't work at > > all. > > > In about:support I can see advanced layers are blacklisted: > > "name": "ADVANCED_LAYERS", > "description": "Advanced Layers", > "status": "blacklisted", > > Try this: > - Enable the pref layers.mlgpu.enable-on-windows7 again, restart Firefox. > - Go in about:support, copy the text in the clipboard, paste it in a text > file and attach it here. > > With these info we will see if your GPU/drivers are blacklisted or not. > > See also bug #1433058 I'm back on 58.0.2. Returned layers back to true, restarted FF and about:support doesn't give me anything like that. I can only see this: ADVANCED_LAYERS available by user: Enabled for Windows 7 via user-preference
Please attach the info here, so we can see why it's not blacklisted (maybe because the HWID of your card is not on the blacklist).
You have a button on top of about:support page to copy all the info.
Application Basics ------------------ Name: Firefox Version: 58.0.2 Build ID: 20180206200532 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 OS: Windows_NT 6.1 Multiprocess Windows: 1/1 (Enabled by default) Web Content Processes: 3/4 Stylo: content = true (enabled by default), chrome = false (disabled by default) Google Key: Found Mozilla Location Service Key: Found Safe Mode: false Crash Reports for the Last 3 Days --------------------------------- All Crash Reports Firefox Features ---------------- Name: Activity Stream Version: 2018.01.04.0062-4997c81d ID: activity-stream@mozilla.org Name: Application Update Service Helper Version: 2.0 ID: aushelper@mozilla.org Name: Firefox Screenshots Version: 25.0.0 ID: screenshots@mozilla.org Name: Follow-on Search Telemetry Version: 0.9.6 ID: followonsearch@mozilla.com Name: Form Autofill Version: 1.0 ID: formautofill@mozilla.org Name: Photon onboarding Version: 1.0 ID: onboarding@mozilla.org Name: Pocket Version: 1.0.5 ID: firefox@getpocket.com Name: Shield Recipe Client Version: 76.1 ID: shield-recipe-client@mozilla.org Name: Web Compat Version: 1.1 ID: webcompat@mozilla.org Extensions ---------- Name: Forecastfox (fix version) Version: 4.14 Enabled: true ID: forecastfox@s3_fix_version Name: MEGA Version: 3.23.5 Enabled: true ID: firefox@mega.co.nz Name: StumbleBar by StumbleUpon Version: 11.328 Enabled: true ID: discover@mix.com Name: uBlock Origin Version: 1.15.4 Enabled: true ID: uBlock0@raymondhill.net Graphics -------- Features Compositing: Direct3D 11 (Advanced Layers) Asynchronous Pan/Zoom: wheel input enabled; scrollbar drag enabled; keyboard enabled; autoscroll enabled WebGL 1 Driver WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000000a67f) EGL_VERSION: 1.4 (ANGLE 2.1.0.db3422764a9b) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_ANGLE_display_robust_resource_initialization WebGL 1 Driver Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 1060 6GB Direct3D11 vs_5_0 ps_5_0) WebGL 1 Driver Version: OpenGL ES 2.0 (ANGLE 2.1.0.db3422764a9b) WebGL 1 Driver Extensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_robust_resource_initialization GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object WebGL 1 Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context WebGL 2 Driver WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000000a67f) EGL_VERSION: 1.4 (ANGLE 2.1.0.db3422764a9b) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_ANGLE_display_robust_resource_initialization WebGL 2 Driver Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GTX 1060 6GB Direct3D11 vs_5_0 ps_5_0) WebGL 2 Driver Version: OpenGL ES 3.0 (ANGLE 2.1.0.db3422764a9b) WebGL 2 Driver Extensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_multiview GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_robust_resource_initialization GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object WebGL 2 Extensions: EXT_color_buffer_float EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_texture_float_linear WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context Direct2D: true Off Main Thread Painting Enabled: true DirectWrite: true (6.2.9200.22164) GPU #1 Active: Yes Description: NVIDIA GeForce GTX 1060 6GB Vendor ID: 0x10de Device ID: 0x1c03 Driver Version: 23.21.13.8792 Driver Date: 10-6-2017 Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Subsys ID: 32811462 RAM: 6144 Diagnostics ClearType Parameters: Gamma: 2.2 Pixel Structure: BGR ClearType Level: 50 Enhanced Contrast: 50 AzureCanvasAccelerated: 0 AzureCanvasBackend: Direct2D 1.1 AzureCanvasBackend (UI Process): skia AzureContentBackend: Direct2D 1.1 AzureContentBackend (UI Process): skia AzureFallbackCanvasBackend (UI Process): cairo GPUProcessPid: 8704 ClearType Parameters: Gamma: 2.2 Pixel Structure: BGR ClearType Level: 50 Enhanced Contrast: 50 Decision Log WEBRENDER: opt-in by default: WebRender is an opt-in feature unavailable by runtime: Build doesn't include WebRender ADVANCED_LAYERS: available by user: Enabled for Windows 7 via user-preference Workarounds NO_CONSTANT_BUFFER_OFFSETTING: Unsupported by driver Media ----- Audio Backend: wasapi Max Channels: 2 Preferred Channel Layout: stereo Preferred Sample Rate: 48000 Output Devices Name: Group LG TV-0 (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0800E6 SPDIF-Out (Sound Blaster Z): HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_11020023&REV_1009\5&5145971&4&0101 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Speakers (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 LG TV-4 (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 SPDIF Out (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0800E6 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0800E6 NVIDIA Output (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 SPDIF Out (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 LG TV-0 (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0800E6 NVIDIA Output (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 LG TV-4 (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 NVIDIA Output (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 Speakers (Sound Blaster Z): HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_11020023&REV_1009\5&5145971&4&0101 Input Devices Name: Group Digital-In (Sound Blaster Z): HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_11020023&REV_1009\5&5145971&4&0101 Microphone (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 What U Hear (Sound Blaster Z): HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_11020023&REV_1009\5&5145971&4&0101 Auxiliary (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Internal AUX Jack (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 Internal AUX Jack (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0800E6 Line-In (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Internal AUX Jack (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Microphone (HD Webcam C270): USB\VID_046D&PID_0825&MI_02\7&61076b0&0&0002 Microphone (Sound Blaster Z): HDAUDIO\FUNC_01&VEN_1102&DEV_0011&SUBSYS_11020023&REV_1009\5&5145971&4&0101 Internal AUX Jack (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_14623281&REV_1001\5&1911f251&0&0001 "What U Hear" (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Digital-In (Creative SB X-Fi): PCI\VEN_1102&DEV_0005&SUBSYS_002C1102&REV_00\5&d93df5b&0&0000E6 Important Modified Preferences ------------------------------ accessibility.force_disabled: 1 accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 358400 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.smart_size.first_run: false browser.cache.frecency_experiment: 3 browser.download.useDownloadDir: false browser.places.smartBookmarksVersion: 8 browser.sessionstore.upgradeBackup.latestBuildID: 20180206200532 browser.startup.homepage_override.buildID: 20180206200532 browser.startup.homepage_override.mstone: 58.0.2 browser.tabs.closeWindowWithLastTab: false browser.tabs.drawInTitlebar: false browser.tabs.insertRelatedAfterCurrent: false browser.tabs.remote.autostart.2: true browser.tabs.warnOnClose: false browser.tabs.warnOnCloseOtherTabs: false browser.urlbar.lastSuggestionsPromptDate: 20180112 browser.urlbar.matchBuckets: general:5,suggestion:Infinity browser.urlbar.oneOffSearches: false browser.urlbar.searchSuggestionsChoice: false browser.urlbar.suggest.bookmark: false browser.urlbar.suggest.openpage: false browser.urlbar.suggest.searches: false browser.urlbar.timesBeforeHidingSuggestionsHint: 2 dom.disable_open_during_load: false extensions.lastAppVersion: 58.0.2 layers.mlgpu.sanity-test-failed: false media.benchmark.vp9.fps: 272 media.benchmark.vp9.versioncheck: 3 media.gmp-gmpopenh264.abi: x86_64-msvc-x64 media.gmp-gmpopenh264.lastUpdate: 1515752889 media.gmp-gmpopenh264.version: 1.7.1 media.gmp-manager.buildID: 20180206200532 media.gmp-manager.lastCheck: 1518098540 media.gmp-widevinecdm.abi: x86_64-msvc-x64 media.gmp-widevinecdm.lastUpdate: 1515752889 media.gmp-widevinecdm.version: 1.4.8.1008 media.gmp.storage.version.observed: 1 media.hardware-video-decoding.failed: false network.allow-experiments: false network.cookie.prefsMigrated: true network.dns.disablePrefetch: true network.http.speculative-parallel-limit: 0 network.predictor.enabled: false network.prefetch-next: false places.database.lastMaintenance: 1517928916 places.history.expiration.transient_current_max_pages: 150103 plugin.disable_full_page_plugin_for_types: application/pdf plugin.state.flash: 2 plugin.state.npcontentblocker: 2 plugin.state.nponlinebanking: 2 plugin.state.npvkplugin: 2 print.printer_Adobe_PDF.print_bgcolor: false print.printer_Adobe_PDF.print_bgimages: false print.printer_Adobe_PDF.print_duplex: -437918235 print.printer_Adobe_PDF.print_edge_bottom: 0 print.printer_Adobe_PDF.print_edge_left: 0 print.printer_Adobe_PDF.print_edge_right: 0 print.printer_Adobe_PDF.print_edge_top: 0 print.printer_Adobe_PDF.print_evenpages: true print.printer_Adobe_PDF.print_footercenter: print.printer_Adobe_PDF.print_footerleft: &PT print.printer_Adobe_PDF.print_footerright: &D print.printer_Adobe_PDF.print_headercenter: print.printer_Adobe_PDF.print_headerleft: &T print.printer_Adobe_PDF.print_headerright: &U print.printer_Adobe_PDF.print_in_color: true print.printer_Adobe_PDF.print_margin_bottom: 0.5 print.printer_Adobe_PDF.print_margin_left: 0.5 print.printer_Adobe_PDF.print_margin_right: 0.5 print.printer_Adobe_PDF.print_margin_top: 0.5 print.printer_Adobe_PDF.print_oddpages: true print.printer_Adobe_PDF.print_orientation: 0 print.printer_Adobe_PDF.print_page_delay: 50 print.printer_Adobe_PDF.print_paper_data: 0 print.printer_Adobe_PDF.print_paper_height: 11.00 print.printer_Adobe_PDF.print_paper_name: print.printer_Adobe_PDF.print_paper_size_unit: 0 print.printer_Adobe_PDF.print_paper_width: 8.50 print.printer_Adobe_PDF.print_resolution: -437918235 print.printer_Adobe_PDF.print_reversed: false print.printer_Adobe_PDF.print_scaling: 1.00 print.printer_Adobe_PDF.print_shrink_to_fit: true print.printer_Adobe_PDF.print_to_file: false print.printer_Adobe_PDF.print_unwriteable_margin_bottom: 0 print.printer_Adobe_PDF.print_unwriteable_margin_left: 0 print.printer_Adobe_PDF.print_unwriteable_margin_right: 0 print.printer_Adobe_PDF.print_unwriteable_margin_top: 0 privacy.cpd.cookies: false privacy.cpd.downloads: false privacy.cpd.formdata: false privacy.cpd.history: false privacy.cpd.sessions: false privacy.sanitize.timeSpan: 0 privacy.trackingprotection.introCount: 20 security.sandbox.content.tempDirSuffix: {efb2d67d-a18a-47de-a587-dffd5b2008bd} services.sync.declinedEngines: storage.vacuum.last.index: 1 storage.vacuum.last.places.sqlite: 1515773039 user.js Preferences ------------------- Your profile folder contains a user.js file, which includes preferences that were not created by Firefox. Important Locked Preferences ---------------------------- Places Database --------------- JavaScript ---------- Incremental GC: true Accessibility ------------- Activated: false Prevent Accessibility: 1 Accessible Handler Used: true Accessibility Instantiator: Library Versions ---------------- NSPR Expected minimum version: 4.17 Version in use: 4.17 NSS Expected minimum version: 3.34.1 Version in use: 3.34.1 NSSSMIME Expected minimum version: 3.34.1 Version in use: 3.34.1 NSSSSL Expected minimum version: 3.34.1 Version in use: 3.34.1 NSSUTIL Expected minimum version: 3.34.1 Version in use: 3.34.1 Experimental Features --------------------- Sandbox ------- Content Process Sandbox Level: 4 Effective Content Process Sandbox Level: 4 Internationalization & Localization ----------------------------------- Application Settings Requested Locales: ["en-US"] Available Locales: ["en-US"] App Locales: ["en-US"] Regional Preferences: ["en-US"] Default Locale: "en-US" Operating System System Locales: ["en-US"] Regional Preferences: ["en-US"]
Indeed, you are not on the blacklist, advanced layers is enabled. You could try two things: - Make a new profile https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles and see if the blacklist is working with the new profile. - Update your NVIDIA drivers (maybe version 387.92 is not in the blacklist ? it should be AFAIK). 390.77 are working fine here.
I tested the same on my system: - I re-enabled hardware acceleration - layers.mlgpu.enable-on-windows7 to default (true) The current 390.77 seems to be blacklisted on my system (Problem 1419264): Direct2D: true Zeichnen auf Nebenthread aktiviert: true DirectWrite: true (6.2.9200.22164) GPU 1 Aktiv: Ja Beschreibung: NVIDIA GeForce GTX 1050 Ti Herstellerkennung: 0x10de Gerätekennung: 0x1c82 Treiber-Version: 23.21.13.9077 Treiber-Datum: 1-23-2018 Treiber: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Subsys-ID: 1c8210de RAM: 4096 [...] WEBRENDER: opt-in by default: WebRender is an opt-in feature unavailable by runtime: Build doesn't include WebRender ADVANCED_LAYERS: available by user: Enabled for Windows 7 via user-preference Auf Grund bekannter Probleme blockiert; Problem 1419264
(In reply to mooms from comment #158) > Indeed, you are not on the blacklist, advanced layers is enabled. > > You could try two things: > > - Make a new profile > https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove- > firefox-profiles > and see if the blacklist is working with the new profile. > > - Update your NVIDIA drivers (maybe version 387.92 is not in the blacklist ? > it should be AFAIK). 390.77 are working fine here. Tried with new profile, but it shows the same as above. Mostly, due to new profile. 387.92 should be on blacklist, due to topic on geforce forums: Windows 7 385.69-388.xx Accelerated Firefox TDRs. Well, I have no TDRs with layers disabled, so I will keep it that way for now, until issues are truly resolved and when nV prepares some normal drivers. Even 390.77 have a lot of bugs.
(In reply to Tobias Wiersch from comment #159) > I tested the same on my system: > - I re-enabled hardware acceleration > - layers.mlgpu.enable-on-windows7 to default (true) > > The current 390.77 seems to be blacklisted on my system (Problem 1419264): It seems your crashes are caused by something else, still related to hardware acceleration since the crashes don't happen with it disabled, but not advanced layers. Also try to see with NVIDIA. (In reply to animeyu from comment #160) > > Tried with new profile, but it shows the same as above. Mostly, due to new > profile. > 387.92 should be on blacklist, due to topic on geforce forums: Windows 7 > 385.69-388.xx Accelerated Firefox TDRs. > > Well, I have no TDRs with layers disabled, so I will keep it that way for > now, until issues are truly resolved and when nV prepares some normal > drivers. Even 390.77 have a lot of bugs. I have no clue why your drivers aren't blacklisted. A Firefox dev should check this issue.
WIN7, GTX1060 6GB, 390.65, ff59.0b9 (but i had crashes for around 3 months already since i switched to quantum and new GPU) Having this bug for around 3 months, i can say it triggers everywhere, but i noticed something. Very often scrollin with mouse-wheel triggers it. Or switching tabs. Not necessary watching videos or something, just scrolling webpages enough to trigger it since scrolling utilizes GPU. Last time it crashed so hard i couldnt even get back cuz my monitor cant turn on. about:support - ADVANCED_LAYERS available by user: Enabled for Windows 7 via user-preference Blocklisted due to known issues; bug 1419264
> Very often scrollin with mouse-wheel triggers it. Or switching tabs. Not > necessary watching videos or something, just scrolling webpages enough to > trigger it since scrolling utilizes GPU. Last time it crashed so hard i > couldnt even get back cuz my monitor cant turn on. The monitor never turns back on for me either. I read somewhere else that you can unplug the HDMI and replug it, and indeed this brings back the monitor image for me.
(In reply to keepstay from comment #162) > WIN7, GTX1060 6GB, 390.65, ff59.0b9 (but i had crashes for around 3 months > already since i switched to quantum and new GPU) > > Having this bug for around 3 months, i can say it triggers everywhere, but i > noticed something. > > Very often scrollin with mouse-wheel triggers it. Or switching tabs. Not > necessary watching videos or something, just scrolling webpages enough to > trigger it since scrolling utilizes GPU. Last time it crashed so hard i > couldnt even get back cuz my monitor cant turn on. > > about:support - > > ADVANCED_LAYERS > available by user: Enabled for Windows 7 via user-preference > Blocklisted due to known issues; bug 1419264 Then your crashes are not caused by advanced layers, it's a different issue.
Hi, I also have some NVIDIA graphics driver crashes (screen is black for a short moment and Windows says that the driver has stopped and was restored) when using Firefox 58.0.2 (64 bit) on Windows 7 (fully updated) with the NVIDIA driver 390.77. Everytime the driver crashes, I was starting to watch a video (YouTube, Twitch, etc.). Here is my about:support output: Allgemeine Informationen ------------------------ Name: Firefox Version: 58.0.2 Build-ID: 20180206200532 Update-Kanal: release User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0 Betriebssystem: Windows_NT 6.1 Fenster mit mehreren Prozessen: 1/1 (aktiviert (Standard)) Web-Inhaltsprozesse: 5/4 Stylo: content = true (aktiviert (Standard)), chrome = false (deaktiviert (Standard)) Google-Schlüssel: Gefunden Mozilla-Location-Service-Schlüssel: Gefunden Abgesicherter Modus: false Absturzberichte der letzten 3 Tage ---------------------------------- Meldungs-ID: bp-03a0dfca-e59a-4bd5-b206-fc9d10180216 Gesendet: vor 10 Stunden Alle Absturzberichte (einschließlich 3 nicht abgesendeter Absturzberichte in dieser Zeitspanne) Firefox-Funktionen ------------------ Name: Activity Stream Version: 2018.01.04.0062-4997c81d ID: activity-stream@mozilla.org Name: Application Update Service Helper Version: 2.0 ID: aushelper@mozilla.org Name: Firefox Screenshots Version: 25.0.0 ID: screenshots@mozilla.org Name: Follow-on Search Telemetry Version: 0.9.6 ID: followonsearch@mozilla.com Name: Form Autofill Version: 1.0 ID: formautofill@mozilla.org Name: Photon onboarding Version: 1.0 ID: onboarding@mozilla.org Name: Pocket Version: 1.0.5 ID: firefox@getpocket.com Name: Shield Recipe Client Version: 76.1 ID: shield-recipe-client@mozilla.org Name: Web Compat Version: 1.1 ID: webcompat@mozilla.org Erweiterungen ------------- Name: Brief Version: 2.5.5 Aktiviert: true ID: brief@mozdev.org Name: resumelater Version: 2.0.1 Aktiviert: true ID: resumeLater@mpuppe.de Name: uBlock Origin Version: 1.15.6 Aktiviert: true ID: uBlock0@raymondhill.net Name: YouTube Plus Version: 1.9.6 Aktiviert: true ID: particle@particlecore.github.io Name: Citavi Picker Version: 2017.12.12.21 Aktiviert: false ID: {8AA36F4F-6DC7-4c06-77AF-5035170634FE} Grafik ------ Allgemeine Merkmale Compositing: Direct3D 11 Asynchrones Wischen und Zoomen: Mausrad-Eingabe aktiviert; Ziehen der Bildlaufleiste aktiviert; Tastatur aktiviert; automatischer Bildlauf aktiviert WebGL-1-Treiber: WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000000a7be) EGL_VERSION: 1.4 (ANGLE 2.1.0.db3422764a9b) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_ANGLE_display_robust_resource_initialization WebGL-1-Treiber: Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GT 710 Direct3D11 vs_5_0 ps_5_0) WebGL-1-Treiber: Version: OpenGL ES 2.0 (ANGLE 2.1.0.db3422764a9b) WebGL-1-Treiber: Erweiterungen: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_robust_resource_initialization GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object WebGL-1-Erweiterungen: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context WebGL-2-Treiber: WSI Info: EGL_VENDOR: Google Inc. (adapter LUID: 000000000000a7be) EGL_VERSION: 1.4 (ANGLE 2.1.0.db3422764a9b) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses EGL_ANGLE_display_robust_resource_initialization WebGL-2-Treiber: Renderer: Google Inc. -- ANGLE (NVIDIA GeForce GT 710 Direct3D11 vs_5_0 ps_5_0) WebGL-2-Treiber: Version: OpenGL ES 3.0 (ANGLE 2.1.0.db3422764a9b) WebGL-2-Treiber: Erweiterungen: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_multiview GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_robust_resource_initialization GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_norm16 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_image_external_essl3 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object WebGL-2-Erweiterungen: EXT_color_buffer_float EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_texture_float_linear WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context Direct2D: true Zeichnen auf Nebenthread aktiviert: true DirectWrite: true (6.2.9200.22164) GPU 1 Aktiv: Ja Beschreibung: NVIDIA GeForce GT 710 Herstellerkennung: 0x10de Gerätekennung: 0x128b Treiber-Version: 23.21.13.9077 Treiber-Datum: 1-23-2018 Treiber: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Subsys-ID: 128b10de RAM: 2048 Weitere Informationen AzureCanvasAccelerated: 0 AzureCanvasBackend: Direct2D 1.1 AzureCanvasBackend (UI Process): skia AzureContentBackend: Direct2D 1.1 AzureContentBackend (UI Process): skia AzureFallbackCanvasBackend (UI Process): cairo GPUProcessPid: 7732 Entscheidungsprotokoll WEBRENDER: opt-in by default: WebRender is an opt-in feature unavailable by runtime: Build doesn't include WebRender ADVANCED_LAYERS: available by user: Enabled for Windows 7 via user-preference Auf Grund bekannter Probleme blockiert; Problem 1419264 Medien ------ Audio-Backend: wasapi Max. Kanäle: 2 Bevorzugtes Kanallayout: stereo Bevorzugte Sample-Rate: 48000 Ausgabegeräte Name: Gruppe NVIDIA Output (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0051&SUBSYS_10DE128B&REV_1001\5&8ccaf75&0&0001 Lautsprecher (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 BenQ GW2470 (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0051&SUBSYS_10DE128B&REV_1001\5&8ccaf75&0&0001 Eingabegeräte Name: Gruppe Mikrofon (USB-Audiogerät): USB\VID_0556&PID_0001&MI_00\6&57325ec&0&0000 Eingang (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Stereomix (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Eingang (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Rear (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Center (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Front (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Interne AUX-Buchse (NVIDIA High Definition Audio): HDAUDIO\FUNC_01&VEN_10DE&DEV_0051&SUBSYS_10DE128B&REV_1001\5&8ccaf75&0&0001 Subwoofer (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Rear Green In (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Mikrofon (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Rear Pink In (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Mikrofon (USB Microphone): USB\VID_0C45&PID_6340&MI_02\6&7e33e26&0&0002 Rear Blue In (Realtek High Definition Audio): HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_1565821E&REV_1001\4&1d1bb8c0&0&0201 Wichtige modifizierte Einstellungen ----------------------------------- accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 358400 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.smart_size.first_run: false browser.cache.frecency_experiment: 3 browser.places.smartBookmarksVersion: 8 browser.sessionstore.upgradeBackup.latestBuildID: 20180206200532 browser.startup.homepage_override.buildID: 20180206200532 browser.startup.homepage_override.mstone: 58.0.2 browser.urlbar.searchSuggestionsChoice: false browser.urlbar.suggest.history: false browser.urlbar.suggest.openpage: false browser.urlbar.suggest.searches: false browser.urlbar.timesBeforeHidingSuggestionsHint: 0 dom.push.userAgentID: 8c24f52d23674cde8f262d484d54a18b extensions.lastAppVersion: 58.0.2 font.internaluseonly.changed: true gfx.crash-guard.d3d11layers.appVersion: 58.0.2 gfx.crash-guard.d3d11layers.deviceID: 0x128b gfx.crash-guard.d3d11layers.driverVersion: 23.21.13.9077 gfx.crash-guard.d3d11layers.feature-d2d: true gfx.crash-guard.d3d11layers.feature-d3d11: true gfx.crash-guard.status.d3d11layers: 2 layers.mlgpu.sanity-test-failed: true media.benchmark.vp9.fps: 66 media.benchmark.vp9.versioncheck: 3 media.gmp-gmpopenh264.abi: x86_64-msvc-x64 media.gmp-gmpopenh264.lastUpdate: 1518696711 media.gmp-gmpopenh264.version: 1.7.1 media.gmp-manager.buildID: 20180206200532 media.gmp-manager.lastCheck: 1518696711 media.gmp-widevinecdm.abi: x86_64-msvc-x64 media.gmp-widevinecdm.lastUpdate: 1518696713 media.gmp-widevinecdm.version: 1.4.8.1008 media.gmp.storage.version.observed: 1 media.hardware-video-decoding.failed: false network.cookie.prefsMigrated: true network.dns.disablePrefetch: true network.http.speculative-parallel-limit: 0 network.predictor.cleaned-up: true network.predictor.enabled: false network.prefetch-next: false places.database.lastMaintenance: 1518705226 places.history.expiration.transient_current_max_pages: 51079 plugin.disable_full_page_plugin_for_types: application/pdf security.sandbox.content.tempDirSuffix: {e70d7cbf-407f-4b2a-9954-0956837b96e7} services.sync.declinedEngines: forms,history,prefs services.sync.engine.history: false services.sync.engine.prefs: false services.sync.engine.prefs.modified: false services.sync.lastPing: 1518783406 services.sync.lastSync: Fri Feb 16 2018 13:17:00 GMT+0100 storage.vacuum.last.index: 0 storage.vacuum.last.places.sqlite: 1518705225 Wichtige nicht veränderbare Einstellungen ----------------------------------------- Chronik- und Lesezeichendatenbank --------------------------------- JavaScript ---------- Inkrementelle GC: true Barrierefreiheit ---------------- Aktiviert: false Barrierefreiheit verhindern: 0 Accessible Handler verwendet: true Bedienungshilfen aufgerufen durch: Bibliotheken-Versionen ---------------------- NSPR Minimal vorausgesetzte Version: 4.17 Verwendete Version: 4.17 NSS Minimal vorausgesetzte Version: 3.34.1 Verwendete Version: 3.34.1 NSSSMIME Minimal vorausgesetzte Version: 3.34.1 Verwendete Version: 3.34.1 NSSSSL Minimal vorausgesetzte Version: 3.34.1 Verwendete Version: 3.34.1 NSSUTIL Minimal vorausgesetzte Version: 3.34.1 Verwendete Version: 3.34.1 Experimentelle Funktionen ------------------------- Isolierte Umgebungen -------------------- Ebene der isolierten Umgebung des Inhaltsprozesses: 4 Effektive Ebene der isolierten Umgebung: 4 Internationalisierung & Lokalisierung ------------------------------------- Anwendungseinstellungen Angeforderte Sprachen: ["de","en-US"] Verfügbare Sprachen: ["de"] Anwendungssprachen: ["de"] Region-Einstellungen: ["de-DE"] Standardsprache: "de" Betriebssystem Sprachen des Betriebssystems: ["de-DE"] Region-Einstellungen: ["de-DE"] (I don't know how to send you the information in english.)
You don't need to, you're just once again confirming the fact that advanced layers was only increasing the impact rate of the existing driver issue, it isn't the cause of it.
Maybe it is coincidence, but I think the problems began when I replaced my 3 monitors with a single, very large monitor. Because of this monitor, my NVidia card currently operates at 3840x1600 pixels on a single screen. But as I said: It may be coincidence, because I replaced the monitor around the time Firefox Quantum came out and the culprit might be Quantum alone.
In case this might be a differentiating factor, I also run a high resolution. HDMI to a single 49" screen at 3840x2160. I really hope this problem gets fixed soon.
Hello! I've found some way to reproduce crashes - after driver reset when using firefox, there is no way to play any mkv/mp4 movie in Media Player Classic (at least in version x64, 1.7.11.13, k-lite codec pack 13.0). Nvidia drivers crashes player every time, until full system reset. In the meantime, playback in VLC is just fine (probably because of its embedded codecs?). I have 27" 2560 x 1440 (WQHD) monitor, 1070 GTX card, Win 7 Ent.
ff58.02 stops my display driver. win7 64 Most recently on Google Maps. Is this a different bug? ...Seems similar. All monitors go black. :(
(In reply to Dan Dreifort from comment #170) > ff58.02 stops my display driver. > win7 64 > Most recently on Google Maps. > Is this a different bug? ...Seems similar. > All monitors go black. :( oh - gtx 1060 6gb vidcard
(In reply to Tobias Wiersch from comment #167) > Maybe it is coincidence, but I think the problems began when I replaced my 3 > monitors with a single, very large monitor. > Because of this monitor, my NVidia card currently operates at 3840x1600 > pixels on a single screen. > > But as I said: It may be coincidence, because I replaced the monitor around > the time Firefox Quantum came out and the culprit might be Quantum alone. I also replaced my screen at about the same time and didn't have this issue on my old 30" @ 2560x1600 but do on my 40" @ 3840x2160. Of course Firefox had a number of updates through that period and I also upgraded from a 1070 to a 1080TI so it's hard to say if a high resolution over hdmi is part of the problem.
(In reply to keatingtobias from comment #172) > > I also replaced my screen at about the same time and didn't have this issue > on my old 30" @ 2560x1600 but do on my 40" @ 3840x2160. Of course Firefox > had a number of updates through that period and I also upgraded from a 1070 > to a 1080TI so it's hard to say if a high resolution over hdmi is part of > the problem. For my case, I'm fairly certain the issue is related to high resolution over HDMI or DP. I have 2 machines (same spec Win7x64, GTX1060 and drivers). One can reproduce the issue, the other cannot. The only difference is I had to replace one of my monitors - a 27" 4k monitor. Since replacing it, the machine with the new monitor has been encountering these TDRs while browsing. I've tested both HDMI and DP connectors. The only fix I've had is to disable both HW accel and AL on that machine. I do need to try turning HW accel back on since I only disabled AL after encountering yet another crash after disabling HW accel. With both disabled, there definitely has been no TDRs for me over the past 3 months.
If HW accel is disabled, AL can't be enabled (it's a specific HW accel).
(In reply to mooms from comment #174) > If HW accel is disabled, AL can't be enabled (it's a specific HW accel). I don't know what to say. When I had HW accel disabled, I would still encounter TDRs albeit less frequently. After setting layers.mlgpu.enable-on-windows7 to false, I haven't had a TDR since on the machine with the 4k monitor. Also, for reference, my other machine that can't repro the issue has a 27" 1440p monitor.
>ManuelGuzmanNV > > We believe we have fixed this bug. I am confirming the bug fix will be in our next driver although from the bug details it appears it will be.
Geforce Driver 391.24 lists this issue as resolved.
Indeed, the blacklist should not include drivers 391.24 and up. In the meantime, is there any possibility to bypass the blacklist to test if the crashes are actually gone ?
After disabling the hardware acceleration some weeks ago, I had no more crashes since. Today I installed the new 391.24 driver from nvidia and re-enabled the hardware acceleration in Firefox. Now, two hours later, Firefox crashed the nvidia driver. So this problem is still not fixed - at least on my system.
I'm beginning to wonder if this driver did not actually make the change, and it was added to the upcoming farcry 5 driver.
This bug is fixed, so please take comments to follow up bug, which is bug #1433058. Thanks. + dropping :ni per resolved status
Flags: needinfo?(anthony.s.hughes)
See Also: 1433058 →
Have the same problem with Geforce 1050 TI. Latest video driver and problem with firefox only. Week ago i have used another video card and problem do no appear. windows 7 x64, firefox 60.0.2 (64 bit), 7gb ram. windows event info: ------------- name of journal: System source: Display date: 12.06.2018 18:48:33 event code: 4101 level: warning description: Video driver nvlddmkm stopped responding and was successfully restored. Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Display" /> <EventID Qualifiers="0">4101</EventID> <Level>3</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-06-12T15:48:33.000000000Z" /> <EventRecordID>257194</EventRecordID> <Channel>System</Channel> <Computer>mike</Computer> <Security /> </System> <EventData> <Data>nvlddmkm</Data> <Data> </Data> </EventData> </Event> So, when it happens i see blackscreen few seconds for once and after it all is ok, But in event list i see that driver was crashed not a once but 3 times in the time.
and updating adobe flash not resolve the problem. Problem appers all the time i use ff, 3+ times per hour (depending on the frequency of actions: open sites, scrolling sites, restoring sleeping tabs,...)
(In reply to Mike from comment #182) My ff config: layers.acceleration.force-enabled = false layers.acceleration.disabled = false
This issue is resolved with Release 397 drivers
(In reply to Danial Horton from comment #185) > This issue is resolved with Release 397 drivers sorry for disinformation, now i already got this error on Chrome and VLC. Its not a FF problem... :(
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: