Closed
Bug 605749
Opened 14 years ago
Closed 2 years ago
[meta] tracking bug of crashes with NVIDIA cards
Categories
(Core :: Graphics, defect)
Core
Graphics
Tracking
()
RESOLVED
FIXED
People
(Reporter: scoobidiver, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: meta)
Attachments
(1 file)
(deleted),
text/plain
|
Details |
It is a tracking bug of all the crashes with NVIDIA cards.
Reporter | ||
Updated•14 years ago
|
Comment 1•14 years ago
|
||
I was already using bug 571756 for this purpose, I even renamed it... ok to close as duplicate?
Comment 2•14 years ago
|
||
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•14 years ago
|
||
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•14 years ago
|
||
Big one: bug 606222
Comment 5•14 years ago
|
||
Filed bug 606262 about crash on D3D10 device creation.
Comment 6•14 years ago
|
||
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.
Reporter | ||
Updated•13 years ago
|
Reporter | ||
Updated•13 years ago
|
Comment 7•13 years ago
|
||
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•9 years ago
|
||
Has this bug been abandoned in favor of a different bug report?
Flags: needinfo?(anthony.s.hughes)
Keywords: meta
(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.
Flags: needinfo?(anthony.s.hughes)
Updated•5 years ago
|
Summary: tracking bug of crashes with NVIDIA cards → [meta] tracking bug of crashes with NVIDIA cards
Updated•2 years ago
|
Severity: normal → S3
Comment 11•2 years ago
|
||
Inactive metabug
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•