This bug was filed from the Socorro interface and is report bp-56291cc1-d18a-40fc-aacd-d59fe2140916. ============================================================= Running Nightly 09-16-2014 on Windows 7. Graphics -------- Adapter Description: Intel(R) HD Graphics 3000 Adapter Description (GPU #2): NVIDIA Quadro 1000M Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Adapter RAM: Unknown Adapter RAM (GPU #2): 2048 Device ID: 0x0126 Device ID (GPU #2): 0x0dfa Direct2D Enabled: true DirectWrite Enabled: true (6.2.9200.16571) Driver Date: 3-20-2014 Driver Date (GPU #2): 10-28-2013 Driver Version: 9.17.10.3517 Driver Version (GPU #2): 9.18.13.1269 GPU #2 Active: false GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC) Subsys ID: 21d117aa Subsys ID (GPU #2): 21d117aa Vendor ID: 0x8086 Vendor ID (GPU #2): 0x10de WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote: true AzureCanvasBackend: direct2d AzureContentBackend: direct2d AzureFallbackCanvasBackend: cairo AzureSkiaAccelerated: 0 https://crash-stats.mozilla.com/report/index/56291cc1-d18a-40fc-aacd-d59fe2140916 https://crash-stats.mozilla.com/report/index/5584c43d-9b04-4ed3-92e5-dbf942140916 https://crash-stats.mozilla.com/report/index/86159cf6-8aa4-46a0-a314-2cf052140916

This is on Lenovo W520.

Again with https://crash-stats.mozilla.com/report/index/647cc5ee-9ea7-4592-85ea-4c4712141201 and https://crash-stats.mozilla.com/report/index/e48f155d-0620-47dd-bb89-82d672141201 Bas, any help here? When this crashes, it also causes the display driver to crash (or maybe vice versa).

(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #2) > Again with > https://crash-stats.mozilla.com/report/index/647cc5ee-9ea7-4592-85ea- > 4c4712141201 > and > https://crash-stats.mozilla.com/report/index/e48f155d-0620-47dd-bb89- > 82d672141201 > > Bas, any help here? When this crashes, it also causes the display driver to > crash (or maybe vice versa). Vice versa - I believe - is what you're seeing, display driver resets crashing us is something I'm actively working on at the moment.

(In reply to Bas Schouten (:bas.schouten) from comment #3) > something I'm actively working on at the moment. Awesome!

This crash happens pretty infrequently but when it does it doesn't go away until I restart my computer. I'll close this bug as fixed now that bug 1107718 has been fixed, but will reopen this bug if I run in to these crashes again.