605749 - [meta] tracking bug of crashes with NVIDIA cards

Status: RESOLVED FIXED

(Core :: Graphics, defect)

Description

[Scoobidiver (away)]

It is a tracking bug of all the crashes with NVIDIA cards.

Comment 1

[Benoit Jacob [:bjacob] (mostly away)]

I was already using bug 571756 for this purpose, I even renamed it... ok to close as duplicate?

Comment 2

[Benoit Jacob [:bjacob] (mostly away)]

Attachment: Geforce PCI IDs grouped by family

Attaching latest version of my PCI ids list.

OK to use this as general NVIDIA tracking bug.

The nvwgf2um.dll crashes are already handled in bug 571756. I don't know the complete list of NVIDIA DLL's.

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

Search for nvidia crashes:

http://crash-stats.mozilla.com/query/query?product=Firefox&version=ALL%3AALL&branch=2.0&range_value=1&range_unit=weeks&date=&query_search=signature&query_type=startswith&query=nv&build_id=&process_type=browser&hang_type=any&do_query=1

This confirms that nvwgf2um.dll is the top crash DLL, the others are (by decreasing order):
nvd3dum.dll
nvumdshim.dll
nvSCPAPI.dll
nview.dll
nvapi.dll
nvoglnt.dll

Comment 4

[Benoit Jacob [:bjacob] (mostly away)]

Big one: bug 606222

Comment 5

[Benoit Jacob [:bjacob] (mostly away)]

Filed bug 606262 about crash on D3D10 device creation.

Comment 6

[Danial Horton]

just as a heads up, many reports that appear to be caused by drivers, are usually a global misconfiguration of the system firefox is being run on.

If a driver works on one computer but not another where both use the same parts, the only causation is the computer with issues is not configured properly, and ever since Vista this has been the case with nvidia drivers not liking memory running out of spec timings or voltages, and on another seperate case, Realtek Sound(or creative sound) or network drivers causing long detection and response latency.

I set computers up all the time and the only case of instability has been where the owner has post setup, taken it to some Cowboy computer shop thats reset all the bios settings and left timings at optimal rather than spec configuration.

Comment 7

[Gingerbread Man]

Please excuse the interjection, but there doesn't seem to be a more appropriate place to add the following info.

I think it's worth noting that users experiencing display driver crashes should refer to the Nvidia forum. The 290.53 drivers (and presumably newer) contain the first attempts to fix such issues. These drivers will not fix the problem for everyone. If you keep having trouble, refer to the following posts on the Nvidia forum for troubleshooting steps and bug report instructions:
http://forums.nvidia.com/index.php?showtopic=215256&st=0
http://forums.nvidia.com/index.php?showtopic=215256&st=200&p=1335976&#entry1335976
http://forums.nvidia.com/index.php?showtopic=215256&st=780&p=1355202&#entry1355202

Comment 8

[Wayne Mery (:wsmwk)]

Has this bug been abandoned in favor of a different bug report?

Comment 9

[u279076]

(In reply to Wayne Mery (:wsmwk, use Needinfo for questions) from comment #8)
> Has this bug been abandoned in favor of a different bug report?

I don't know as I'm new to the Graphics team. However I would assume so given the lack of activity here.

Comment 11

[Gregory Pappas [:gregp]]

Inactive metabug