737141 - Display driver nvlddmkm stopped responding and has successfully recovered.

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Thom Crandall]

Attachment: DxDiag_19-Mar-2012_dadpc.txt

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20100101 Firefox/11.0
Build ID: 20120312181643

Steps to reproduce:

Installed update 11.0 today 19 Mar 2012.


Actual results:

After restarting Firefox after the update, the browser appeared briefly and the monitor went blank for about 5 seconds. A triangle "Windows Warning !" showed up on the status bar. Checking Win events I found:

Log Name:      System
Source:        Display
Date:          3/19/2012 11:10:20 AM
Event ID:      4101
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Dad-PC
Description:
Display driver nvlddmkm stopped responding and has successfully recovered.
Event 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="2012-03-19T18:10:20.000000000Z" />
    <EventRecordID>45240</EventRecordID>
    <Channel>System</Channel>
    <Computer>Dad-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nvlddmkm</Data>
    <Data>
    </Data>
  </EventData>
</Event>

This has been happening since I built the system back in Jan '12 with all versions of Firefox. Snippets from DXDiag:

------------------
System Information
------------------
Time of this report: 3/19/2012, 12:33:01
       Machine name: DAD-PC
   Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.111118-2330)
           Language: English (Regional Setting: English)
System Manufacturer: SYX
       System Model: SYX-SBT-X58
               BIOS: BIOS Date: 12/21/10 22:14:25 Ver: 08.00.15
          Processor: Intel(R) Core(TM) i7 CPU         960  @ 3.20GHz (8 CPUs), ~3.2GHz
             Memory: 12288MB RAM
Available OS Memory: 12280MB RAM
          Page File: 2436MB used, 22120MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: 120 DPI (125 percent)
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
        Sound Tab 4: No problems found.
        Sound Tab 5: No problems found.
          Input Tab: No problems found.

---------------
Display Devices
---------------
          Card name: NVIDIA GeForce GTX 560 Ti
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 560 Ti
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15633842&REV_A1
     Display Memory: 4065 MB
   Dedicated Memory: 993 MB
      Shared Memory: 3071 MB
       Current Mode: 1920 x 1080 (32 bit) (60Hz)
       Monitor Name: Dell U2312HM DVI
      Monitor Model: DELL U2312HM
         Monitor Id: DEL4072
        Native Mode: 1920 x 1080(p) (60.000Hz)
        Output Type: DVI
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.8566 (English)
     Driver Version: 8.17.12.8566
        DDI Version: 11
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 10/20/2011 02:50:00, 15694144 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71E3E-5140-11CF-847A-6F351FC2C535}
          Vendor ID: 0x10DE
          Device ID: 0x1200
          SubSys ID: 0x15633842
        Revision ID: 0x00A1
 Driver Strong Name: oem102.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section005:8.17.12.8566:pci\ven_10de&dev_1200
     Rank Of Driver: 00E62001
        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C


Expected results:

um .... the monitor should not have blanked out. What I have done for testing:

- removed all addons
- removed all extensions (that I could)
- removed all version of Firefox, cleaned disk and registry
- reinstalled Firefox 11 from scratch

Only happens with Firefox, no other program. Some gaming sites and other software mfr's support forums are reporting the same thing. I have asked on some of these forums if they have Firefox running with nVidia cards installed. Most have confirmed this is the case. Running without Firefox is the answer is most cases. It may be a combination of the latest nVidia drivers, libraries and Firefox but I can run without the monitor blanking out all day long if I do not use Firefox. I play WoW, Rift, and EVE online, plus I use Adobe Production Premium (CS5.5), and other graphic, sound and editing tools - all without the monitor blanking out ... bring up Firefox and boom, monitor blanks out. FYI, I have stopped using Firefox and using Chrome until there is solution to this issue.

Comment 1

[TinyButStrong]

I have same issue at least 15 times per day. Nvidia GTX 560 Ti + Windows 8 here.

Comment 2

[Matthias Versen [:Matti]]

The bug is in your graphic card driver and it doesn't matter that it only happens with Firefox. Firefox triggers this bug only. 

Please post the contents of the graphic section in about:support (enter as URL in Firefox).
Disable the hardware acceleration in (alt key)/tools/options/advanced/general as workaround or install the latest graphic card driver from the nvidia website. nivida could have already fixed the bug in their driver.

Comment 3

[Thom Crandall]

Matti - I've seen your comments from others on other forums. I will not disable hw accel since it is only Firefox that is causing the issue, so actually it DOES matter. True, I am using an older driver, 285.66, so I will update to 296.10. Graphics output from Ts Info as follows:

  Graphics

        Adapter Description
        NVIDIA GeForce GTX 560 Ti

        Vendor ID
        10de

        Device ID
        1200

        Adapter RAM
        1024

        Adapter Drivers
        nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um

        Driver Version
        8.17.12.8566

        Driver Date
        10-20-2011

        Direct2D Enabled
        true

        DirectWrite Enabled
        true (6.1.7601.17776)

        ClearType Parameters
        DISPLAY1 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 400 ] DISPLAY4 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 400 ]

        WebGL Renderer
        Google Inc. -- ANGLE (NVIDIA GeForce GTX 560 Ti) -- OpenGL ES 2.0 (ANGLE 1.0.0.930)

        GPU Accelerated Windows
        1/1 Direct3D 10

        AzureBackend
        direct2d

Comment 4

[Matthias Versen [:Matti]]

>I will not disable hw accel since it is only Firefox that is causing the issue, so actually it DOES matter.

nvlddmkm is crashing/freezing and that is not Firefox code. It's part of the nvidia driver. We can not fix bug in the video driver.

>since it is only Firefox that is causing the issue, so actually it DOES matter.
You don't seem to understand the Windows API. Any application can put garbage in the DirectX API and the video driver should not crash. It doesn't matter which Application triggers the bug in the driver. Today it's Firefox and tomorrow Application X that is also using DirectX.

>I will not disable hw accel
You either misunderstand me or I don't understand your problem.
You should disable the hardware acceleration in Firefox. The option from my comment is a Firefox only option and why do you don't want to disable it ?
There are only 2 reasons: You either want to live with that issue or the updated driver will fix that bug in the driver.
btw: I expect that the update will fix it.

Anyway, the report is invalid (not our bug)

Comment 5

[Thom Crandall]

Since I was looking at the Dxdiag screen as I was typing I thought you meant to disable DX acceleration or possible PhysX accel (as there is no way at the user level to disable hw accel with ATI or nVidia). Even though you gave the directions I was not thinking Firefox's config. I understand your ire. So I pulled my head out of my a.... I've updated the nvidia driver to 296.10. I will test this driver out without disabling Firefox's hw accel and if problem still remains I will uncheck it. I came here because there was no joy with nVidia support or forums (what a surprise).

Comment 6

[Matthias Versen [:Matti]]

Just to be clear: This would be a valid support issue but this is no support Forum.

This bug report would be valid if many users get the same crash. We would blocklist the driver version/card combination in that case and that would disable the hardware acceleration in Firefox via remote switch. It would be basically the same as disabling the hardware acceleration manually via that option.

I'm using an nvidia 310M and I think I can remember getting the same kind of crashes with a driver version from last year and that could be your version.

Comment 7

[Thom Crandall]

Okay. Thank you. Closed.