Closed Bug 571756 Opened 14 years ago Closed 14 years ago

NVIDIA driver crashes [@ nvwgf2um.dll@0x.....]

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
blocking2.0 --- -

People

(Reporter: icecold, Assigned: bas.schouten)

References

Details

(Keywords: crash, Whiteboard: need-to-report-to-NVIDIA)

Crash Data

Attachments

(6 files, 2 obsolete files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100612 Minefield/3.7a6pre
Build Identifier: 

I was on Facebook and tried to go on MozillaZine and it crashed. How it seems I'm not able to trigger this bug again. Here is a crash: http://crash-stats.mozilla.com/report/index/bp-f3689a7b-055e-485a-b6b4-5ba5d2100612

Reproducible: Always

Actual Results:  
Browser crashed.

Expected Results:  
It shouldn't crash.
Summary: Firefox crashes on random site D2D → Firefox crashes on random site D2D [@ d3d10_1core.dll@0x2bb04 ]
Version: unspecified → Trunk
Signature	d3d10_1core.dll@0x2bb04
UUID	f3689a7b-055e-485a-b6b4-5ba5d2100612
Time 	2010-06-12 11:28:23.669152
Uptime	6139
Install Age	6140 seconds (1.7 hours) since version was first installed.
Product	Firefox
Version	3.7a6pre
Build ID	20100612040049
OS	Windows NT
OS Version	6.1.7600
CPU	x86
CPU Info	AuthenticAMD family 15 model 107 stepping 2
Crash Reason	EXCEPTION_ACCESS_VIOLATION
Crash Address	0x29
User Comments	
Processor Notes 	
EMCheckCompatibility	False
Crashing Thread
Frame 	Module 	Signature 	Source
0 	d3d10_1core.dll 	d3d10_1core.dll@0x2bb04 	
1 	xul.dll 	_cairo_d2d_paint 	gfx/cairo/cairo/src/cairo-d2d-surface.cpp:1790
2 	xul.dll 	_cairo_surface_paint 	gfx/cairo/cairo/src/cairo-surface.c:2015
3 	xul.dll 	_cairo_gstate_paint 	gfx/cairo/cairo/src/cairo-gstate.c:991
4 	xul.dll 	_moz_cairo_paint_with_alpha 	gfx/cairo/cairo/src/cairo.c:2146
5 	xul.dll 	gfxContext::Paint(double) 	gfx/thebes/src/gfxContext.cpp:726
6 	xul.dll 	xul.dll@0x427848 	
7 	xul.dll 	nsWindow::ProcessMessage(unsigned int,unsigned int&,long&,long*) 	widget/src/windows/nsWindow.cpp:4248
8 	xul.dll 	nsWindow::WindowProc(HWND__*,unsigned int,unsigned int,long) 	widget/src/windows/nsWindow.cpp:3964
9 	user32.dll 	InternalCallWinProc 	
10 	user32.dll 	GetRealWindowOwner 	
11 	user32.dll 	DispatchClientMessage 	
12 	user32.dll 	__fnDWORD 	
13 	ntdll.dll 	KiUserCallbackDispatcher 	
14 	ntdll.dll 	KiUserApcDispatcher 	
15 	user32.dll 	DispatchMessageW 	
16 	xul.dll 	nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal*,int,unsigned int) 	widget/src/xpwidgets/nsBaseAppShell.cpp:294
17 	xul.dll 	MessageLoop::DoWork() 	ipc/chromium/src/base/message_loop.cc:430
18 	nspr4.dll 	PR_AttachThread 	nsprpub/pr/src/threads/prcthr.c:174
19 	xul.dll 	nsThread::ProcessNextEvent(int,int*) 	xpcom/threads/nsThread.cpp:517
20 	xul.dll 	mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) 	ipc/glue/MessagePump.cpp:118
21 	xul.dll 	MessageLoop::RunInternal() 	ipc/chromium/src/base/message_loop.cc:216
22 	xul.dll 	MessageLoop::RunHandler() 	ipc/chromium/src/base/message_loop.cc:199
23 	user32.dll 	InternalCallWinProc 	
24 	xul.dll 	MessageLoop::Run() 	ipc/chromium/src/base/message_loop.cc:173
25 	xul.dll 	nsBaseAppShell::Run() 	widget/src/xpwidgets/nsBaseAppShell.cpp:175
26 	xul.dll 	nsAppShell::Run() 	widget/src/windows/nsAppShell.cpp:243
27 	xul.dll 	nsAppStartup::Run() 	toolkit/components/startup/src/nsAppStartup.cpp:192
28 	xul.dll 	XRE_main 	toolkit/xre/nsAppRunner.cpp:3664
29 	firefox.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp:120
30 	firefox.exe 	__tmainCRTStartup 	obj-firefox/memory/jemalloc/crtsrc/crtexe.c:591
31 	kernel32.dll 	kernel32.dll@0x51193 	
32 	ntdll.dll 	__RtlUserThreadStart 	
33 	ntdll.dll 	_RtlUserThreadStart
Keywords: crash
Hrm, that line doesn't even call onto a D3D10 function, some compiler optimization maybe. No idea. I wonder why it's not loading the symbols for d3d10_1core.dll
https://developer.mozilla.org/En/How_to_get_a_stacktrace_with_windbg

if you can reproduce this, please reproduce it while windbg is attached. if we're lucky, we'll get a better stack trace.
No longer blocks: 579092
Have reproduced this multiple time on FF4 beta 1:
D2D crash reproduced as:
0. Enable d2d rendering with:
   0.1 gfx.font_rendering.directwrite.enabled;true
   0.2 mozilla.widget.render-mode;6
1. FeedBack button -> All you studies
2. Study Results Tab -> More info on any
3. Do NOT close the results window. Switch back to Study results windows -> click more info on any question from a different study (studies typically have 4 questions. so more info on 4 questions before or after the one you clicked originally)

Crash reports:
http://crash-stats.mozilla.com/report/index/bp-874552f2-8cbe-4d83-a2e1-bb6b42100727
http://crash-stats.mozilla.com/report/index/bp-f7d0c19b-bf86-4ab4-8b4d-8dd3c2100727

System Specs:
Chipset: Nvidia ION (Intel Atom 330)

--
Will run WinDBG for next crash
Windbg Log: Attached as WinDBG_20100727_aashay147.log
WinDBG log file
Attachment #460590 - Flags: review?(timeless)
Attachment #460590 - Attachment mime type: application/octet-stream → text/plain
Comment on attachment 460590 [details]
WinDBG log file (20100727) by aashay147

(161c.177c): Stack overflow - code c00000fd (first chance)


d3d10_1core!CTexture2D<0>::CTexture2D<0>+0x215
d3d10_1core!CLayeredObject<CTexture2D<6> >::CreateInstance+0x2d
d3d10_1core!CDevice::CreateLayeredChild+0x273
d3d10_1core!CBridgeImpl<IDXGILayeredDevice,IDXGILayeredDevice,CLayeredObject<CDevice> >::CreateLayeredChild+0x22
dxgi!CD3D10LayeredChild<ID3D10DeviceChild,CD3D10Device,64>::FinalConstruct+0x2a
dxgi!CD3D10DeviceChild<IDXGISurface>::FinalConstruct+0x1b
dxgi!CD3D10Resource::FinalConstruct+0x20
dxgi!CLayeredObject<CD3D10Resource>::CreateInstance+0x73
dxgi!CD3D10Device::CreateLayeredChild+0xca
dxgi!CBridgeImpl<IDXGILayeredDevice,IDXGILayeredDevice,CLayeredObject<CD3D10Device> >::CreateLayeredChild+0x22
d3d10_1core!CD3D10LayeredChild<ID3D10VertexShader,NMultithread::CDevice,16>::FinalConstruct+0x2a
d3d10_1core!NMultithread::CTexture2D::FinalConstruct+0x1a
d3d10_1core!CLayeredObject<NMultithread::CTexture2D>::CreateInstance+0x57
d3d10_1core!NMultithread::CDevice::CreateLayeredChild+0xbf
d3d10_1core!CBridgeImpl<IDXGILayeredDevice,IDXGILayeredDevice,CLayeredObject<NMultithread::CDevice> >::CreateLayeredChild+0x22
dxgi!NOutermost::CDeviceChild::FinalConstruct+0x2a
dxgi!CUseCountedObject<NOutermost::CDeviceChild>::CUseCountedObject<NOutermost::CDeviceChild>+0x45
dxgi!CUseCountedObject<NOutermost::CDeviceChild>::CreateInstance+0x72
dxgi!NOutermost::CDevice::CreateLayeredChild+0xd2
d3d10_1core!CDevice::CreateTexture2D_Worker+0x227
d3d10_1core!CDevice::ID3D10Device1_CreateTexture2D_+0x1d
d3d10_1core!NMultithread::CDevice::CreateTexture2D+0x3c
xul!_cairo_d2d_acquire_source_image+0xae [e:\builds\moz2_slave\win32_build\build\gfx\cairo\cairo\src\cairo-d2d-surface.cpp @ 1561]
xul!_cairo_surface_acquire_source_image(
xul!_cairo_surface_clone_similar(               <
xul!_cairo_pattern_acquire_surface_for_surface( <
xul!_cairo_pattern_acquire_surface(
xul!_cairo_pattern_acquire_surfaces(
xul!_cairo_image_surface_composite(
xul!_cairo_surface_composite(
xul!_composite_rectangle(
xul!_clip_and_composite_trapezoids(
xul!_cairo_surface_fallback_paint(
xul!_cairo_surface_paint(
xul!_cairo_surface_fallback_clone_similar(
xul!_cairo_surface_clone_similar(               <
xul!_cairo_pattern_acquire_surface_for_surface( <
xul!_cairo_pattern_acquire_surface(
xul!_cairo_pattern_acquire_surfaces(
xul!_cairo_image_surface_composite(
xul!_cairo_surface_composite(
xul!_composite_rectangle(
xul!_clip_and_composite_trapezoids(
xul!_cairo_surface_fallback_paint(
xul!_cairo_surface_paint(
xul!_cairo_surface_fallback_clone_similar(
xul!_cairo_surface_clone_similar(               <
xul!_cairo_pattern_acquire_surface_for_surface( <
Attachment #460590 - Flags: review?(timeless)
It is #227 top crasher in FF 4.0b6 for the last 2 weeks.

Chris,
Can I have the same analysis as in bug 596431 comment 6 ?
Status: UNCONFIRMED → NEW
blocking2.0: --- → ?
Ever confirmed: true
Summary: Firefox crashes on random site D2D [@ d3d10_1core.dll@0x2bb04 ] → [D2D] Firefox crash mainly with NVIDIA GeForce G210M and out-of-date graphic driver [@ d3d10_1core.dll@0x2bb04 ]
summary:

sort d3d10_1core.dll-0x2bb04.csv | uniq -c | sort -nr  | grep Ada
  72 AdapterVendorID: 10de, AdapterDeviceID: 0a75	d3d10_1core.dll 6.1.7600.16385	nvwgf2um.dll 8.16.11.8783	1
  17 AdapterVendorID: 10de, AdapterDeviceID: 0a74	d3d10_1core.dll 6.1.7600.16385	nvwgf2um.dll 8.16.11.8783	1
   6 AdapterVendorID: 10de, AdapterDeviceID: 0a74	d3d10_1core.dll 6.1.7600.16385	nvwgf2um.dll 8.16.11.8766	1
   2 AdapterVendorID: 8086, AdapterDeviceID: 2a02	d3d10_1core.dll 6.1.7600.16385	igd10umd32.dll 8.14.10.1930	1
   2 AdapterVendorID: 10de, AdapterDeviceID: 0a6c	d3d10_1core.dll 6.1.7600.16385	nvwgf2um.dll 8.16.11.8955	1
   1 AdapterVendorID: 10de, AdapterDeviceID: 0a74	d3d10_1core.dll 6.1.7600.16385	nvwgf2um.dll 8.16.11.8766
May be it can be fixed by MS hotfix KB2028560 for Win7 x32 and x64 with version 6.1.7600.20781 of d3d10_1core.dll.
For more info about that, see bug 596431 comment 9.

Here is a summary of the implicated D3D10 modules by GPU manufacturer :
* Nvidia :
nvwgf2um.dll : 8.16.11.8766, .8783, .8955  (up-to-date for recent cards : x.y.z2.5696)
* Intel :
it is now fixed by the landing of bug 595364.
Depends on: 595364
Assignee: nobody → bjacob
blocking2.0: ? → betaN+
Time to implement the NVIDIA driver blacklist!

We need to do the same as was already done by Scoobidiver for Intel:

* write down a list of device IDs grouped by families (where a family is a group of devices that are sufficiently similar to require the same driver versions)

* for each family, decide on a minimum driver version to require.
here are counts for the most popular combinations of crash sigs, device id, os, and nvwgf2um.dll out of the full sample of the last 8 days in the attachment.

  28 nvwgf2um.dll@0x45e14 : 10de, DeviceID: 0a28 Win 6.1.7600 nvwgf2um.dll 8.16.11.8691
   8 nvwgf2um.dll@0x1638cf : 10de, DeviceID: 0615 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   7 nvwgf2um.dll@0xb3450 : 10de, DeviceID: 0622 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   6 nvwgf2um.dll@0x3cfaca : 10de, DeviceID: 0615 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   6 nvwgf2um.dll@0x3b863 : 10de, DeviceID: 0402 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   5 nvwgf2um.dll@0xf4be1 : 10de, DeviceID: 0402 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   5 nvwgf2um.dll@0xa26f0 : 10de, DeviceID: 06e4 Win 6.1.7600 nvwgf2um.dll 8.15.11.8593
   5 nvwgf2um.dll@0x51bcc : 10de, DeviceID: 0400 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   5 nvwgf2um.dll@0x51909 : 10de, DeviceID: 0615 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   4 nvwgf2um.dll@0x1622c7 : 10de, DeviceID: 06e4 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   3 nvwgf2um.dll@0x9d6e0 : 10de, DeviceID: 0640 Win 6.1.7600 nvwgf2um.dll 8.17.11.9745
   3 nvwgf2um.dll@0x6743a : 10de, DeviceID: 0615 Win 6.1.7601 Service Pack 1, v.178 nvwgf2um.dll 8.17.12.5896
   3 nvwgf2um.dll@0x57ca0 : 10de, DeviceID: 05e6 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   2 nvwgf2um.dll@0xe1360 : 10de, DeviceID: 0600 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   2 nvwgf2um.dll@0xc0651 : 10de, DeviceID: 0402 Win 6.0.6002 Service Pack 2 nvwgf2um.dll 8.17.12.5896
   2 nvwgf2um.dll@0x92d7f : 10de, DeviceID: 0606 Win 6.1.7600 nvwgf2um.dll 8.17.11.9745
   2 nvwgf2um.dll@0x6fa66 : 10de, DeviceID: 0640 Win 6.1.7600 nvwgf2um.dll 8.17.12.6063
   2 nvwgf2um.dll@0x6b949 : 10de, DeviceID: 05e0 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   2 nvwgf2um.dll@0x6b949 : 10de, DeviceID: 0193 Win 6.1.7600 nvwgf2um.dll 8.17.12.5896
   2 nvwgf2um.dll@0x5cd94 : 10de, DeviceID: 0a20 Win 6.1.7600 nvwgf2um.dll 8.17.11.9745
   2 nvwgf2um.dll@0x5ca90 : 10de, DeviceID: 0622 Win 6.1.7600 nvwgf2um.dll 8.17.11.9745
   2 nvwgf2um.dll@0x45564 : 10de, DeviceID: 0a74 Win 6.1.7600 nvwgf2um.dll 8.15.11.8633
   2 nvwgf2um.dll@0x45564 : 10de, DeviceID: 0a74 Win 6.1.7600 nvwgf2um.dll 8.15.11.8628
   2 nvwgf2um.dll@0x17a79f : 10de, DeviceID: 0e22 Win 6.1.7600 nvwgf2um.dll 8.17.12.6063
   2 nvwgf2um.dll@0x16bfeb : 10de, DeviceID: 0640 Win 6.1.7600 nvwgf2um.dll 8.17.12.5721

long tail snipped.
Nvidia device ID list:  http://pci-ids.ucw.cz/read/PC/10de

My approach is going to be to iterate over Chris's crash results, and for each device ID in that list, look up what "family" it seems to be and add in there the other device IDs that seem to be the same family.

What I mean is that if we know that a certain driver version is crashy with say Geforce GTX 123000 then it will probably also be with similar devices e.g. Geforce GTX 123001...
I'm taking care of this, so don't do it ... ;-)
I declare this bug officially hijacked for implementing the nvidia blacklist.
Summary: [D2D] Firefox crash mainly with NVIDIA GeForce G210M and out-of-date graphic driver [@ d3d10_1core.dll@0x2bb04 ] → NVIDIA driver version blacklist
Attached file Geforce PCI IDs grouped by family (obsolete) —
updated: added 4 missing PCI ids.
Attachment #484359 - Attachment is obsolete: true
Attached file nvidia crashes, sorted
This table is basically Chris's table of nvidia crashes with each device ID mapped to its "family" like "Geforce200", etc. Moreover it's sorted by driver version and I have removed the special Optimus lines (vendorID 8086)
Statistics from Chris's crash table:

        1 entry is Optimus
        7 entries are Geforce400
       55 entries are Geforce200
       89 entries are G90
       43 entries are G80
        0 entries are pre-G80
Total 195
Here's now the top 20 entries in Chris's list of most popular crash devices IDs, mapped to card names:

 543 DeviceID: 0322 GeForce FX 5200
 431 DeviceID: 03d0 GeForce 6150SE nForce 430
 334 DeviceID: 0640 GeForce 9500 GT
 313 DeviceID: 0421 GeForce 8500 GT
 299 DeviceID: 0622 GeForce 9600 GT
 290 DeviceID: 0326 GeForce FX 5500
 273 DeviceID: 0110 GeForce2 MX/MX 400
 263 DeviceID: 0402 GeForce 8600 GT
 254 DeviceID: 06e4 GeForce 8400 GS
 237 DeviceID: 0615 GeForce GTS 250
 234 DeviceID: 0221 GeForce 6200
 227 DeviceID: 0641 GeForce 9400 GT
 221 DeviceID: 0614 GeForce 9800 GT
 212 DeviceID: 0181 GeForce4 MX 440
 203 DeviceID: 01d3 GeForce 7300 SE/7200 GS
 172 DeviceID: 05e2 GeForce GTX 260
 152 DeviceID: 0422 GeForce 8400 GS
 152 DeviceID: 0400 GeForce 8600 GTS
 150 DeviceID: 0427 GeForce 8400M GS
 141 DeviceID: 0393 GeForce 7300 GT
(In reply to comment #24)
> Here's now the top 20 entries in Chris's list of most popular crash devices
> IDs, mapped to card names:
> 
>  543 DeviceID: 0322 GeForce FX 5200
>  431 DeviceID: 03d0 GeForce 6150SE nForce 430
>  334 DeviceID: 0640 GeForce 9500 GT
>  313 DeviceID: 0421 GeForce 8500 GT
>  299 DeviceID: 0622 GeForce 9600 GT
>  290 DeviceID: 0326 GeForce FX 5500
>  273 DeviceID: 0110 GeForce2 MX/MX 400
>  263 DeviceID: 0402 GeForce 8600 GT
>  254 DeviceID: 06e4 GeForce 8400 GS
>  237 DeviceID: 0615 GeForce GTS 250
>  234 DeviceID: 0221 GeForce 6200
>  227 DeviceID: 0641 GeForce 9400 GT
>  221 DeviceID: 0614 GeForce 9800 GT
>  212 DeviceID: 0181 GeForce4 MX 440
>  203 DeviceID: 01d3 GeForce 7300 SE/7200 GS
>  172 DeviceID: 05e2 GeForce GTX 260
>  152 DeviceID: 0422 GeForce 8400 GS
>  152 DeviceID: 0400 GeForce 8600 GTS
>  150 DeviceID: 0427 GeForce 8400M GS
>  141 DeviceID: 0393 GeForce 7300 GT

Note that the top 2 on this list are DX9 cards. So people enabling it manually.
Summary: NVIDIA driver version blacklist → NVIDIA driver crashes tracking bug
Can someone please forward this comment to NVIDIA?

These crashes are with recent NVIDIA drivers, on recent NVIDIA hardware.

For each of them, the link gives details, including a stack trace.

This information was extracted from this table:
  https://bugzilla.mozilla.org/attachment.cgi?id=484415
The crashes listed below are just the ones on most recent driver versions and cards. But there are many, many more, especially on G90 cards, including with recent (258.xx) driver versions.

*********************************************
*** Crashes with Geforce 400 series cards ***
*********************************************

Device:                0e22  GF104 [GeForce GTX 460]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x17a79f
2 crash reports:
http://crash-stats.mozilla.com/report/index/74c4ce78-b132-46bd-9e28-5c91a2101013
http://crash-stats.mozilla.com/report/index/1f815dad-36b7-4b9b-8636-f5a422101010

Device:                0e22  GF104 [GeForce GTX 460]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x179c76
http://crash-stats.mozilla.com/report/index/5f484330-204f-466b-a41e-424bf2101012

Device:                0dc4  GF106 [GeForce GTS 450]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x16fa8d
http://crash-stats.mozilla.com/report/index/d1d90588-7218-4ee1-bfc3-f49ef2101016

Device:                06cd  GF100 [GeForce GTX 470]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x5878b
http://crash-stats.mozilla.com/report/index/fbb80d39-89b2-46c8-a9fe-8673a2101016

Device:                06c4  GF100 [GeForce GTX 465]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x143088
http://crash-stats.mozilla.com/report/index/21089dca-ed5d-4b6b-8252-556082101011

Device:                06c4  GF100 [GeForce GTX 465]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x10819b
http://crash-stats.mozilla.com/report/index/9eded4d8-d832-46e2-9292-243262101011



*********************************************
*** Crashes with Geforce 200 series cards ***
*********************************************

Device:                05e6  GT200b [GeForce GTX 275]
NVIDIA driver version: 260.89
address:               nvwgf2um.dll@0x3b5c2
http://crash-stats.mozilla.com/report/index/0e601846-ba50-4b53-bb29-5c57d2101016

Device:                05ea  GT200 [GeForce GTX 260]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x65d42
http://crash-stats.mozilla.com/report/index/2f5dc4af-105e-4188-9165-2172c2101011

Device:                05e2  GT200 [GeForce GTX 260]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x16f7b3
http://crash-stats.mozilla.com/report/index/47c31c5b-9fea-4296-aae2-994442101017

Device:                0a65  GT218 [GeForce 210]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0xcc8d6
http://crash-stats.mozilla.com/report/index/09f78386-0dec-4785-8c67-1df032101013

Device:                0a65  GT218 [GeForce 210]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x74078
http://crash-stats.mozilla.com/report/index/554c96cb-aa62-4144-a282-1eb822101013

Device:                0a65  GT218 [GeForce 210]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x3bfb60
http://crash-stats.mozilla.com/report/index/21d8e4d6-7f7f-4953-8eea-23e7b2101013

Device:                0a60  GT218 [GeForce G210]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x53898
http://crash-stats.mozilla.com/report/index/5f434d9d-59f5-4fb9-b3d3-ac9702101013

Device:                0a20  GT216 [GeForce GT 220]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x5c32f
http://crash-stats.mozilla.com/report/index/dfbeaa2e-fb8f-45d4-b5a7-962ab2101016

Device:                05e6  GT200b [GeForce GTX 275]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x57ca0
3 crash reports:
http://crash-stats.mozilla.com/report/index/854b5eec-11e8-4029-88d7-09ea82101016
http://crash-stats.mozilla.com/report/index/8379881e-c26f-49e8-8273-ff4d72101016
http://crash-stats.mozilla.com/report/index/4caa24f5-126a-449d-8c3a-fe2f42101016

Device:                05e0  GT200b [GeForce GTX 295]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x6b949
2 crash reports:
http://crash-stats.mozilla.com/report/index/588e618b-6f47-4f59-8b0e-a33732101017
http://crash-stats.mozilla.com/report/index/ee8806a7-9943-413e-b615-1e0fb2101017


*************************************
*** Crashes with G90 series cards ***
*************************************

Device:                0640  G96 [GeForce 9500 GT]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x6fa66
2 crash reports:
http://crash-stats.mozilla.com/report/index/e0b40f21-ee6e-4f26-87c2-c9cac2101013
http://crash-stats.mozilla.com/report/index/2eb181b5-88eb-4098-bda3-84d772101013

Device:                0640  G96 [GeForce 9500 GT]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x6fa66
2 crash reports:
http://crash-stats.mozilla.com/report/index/e0b40f21-ee6e-4f26-87c2-c9cac2101013
http://crash-stats.mozilla.com/report/index/2eb181b5-88eb-4098-bda3-84d772101013

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x9fe49
http://crash-stats.mozilla.com/report/index/bfa3c41a-5f11-4759-9e97-341142101017

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0xe6462
http://crash-stats.mozilla.com/report/index/2e699fb0-8ff9-4dfc-a62c-0f5b32101010

Device:                0600  G92 [GeForce 8800 GTS 512]
NVIDIA driver version: 260.63
address:               nvwgf2um.dll@0x16fa45
http://crash-stats.mozilla.com/report/index/8fd5fe0d-4b39-4c29-8217-3efa32101014

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 259.19
address:               nvwgf2um.dll@0x5c750
http://crash-stats.mozilla.com/report/index/c34deb52-1490-4e32-a054-fcb432101010

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x6743a
3 crash reports:
http://crash-stats.mozilla.com/report/index/08183fbe-c1dd-49c4-922b-f82712101010
http://crash-stats.mozilla.com/report/index/a1a6871c-703d-447c-b15e-545582101010
http://crash-stats.mozilla.com/report/index/b04c314a-6ba0-4b05-9c81-0b7a72101010

Device:                06e4  G98 [GeForce 8400 GS]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x1622c7
4 crash reports:
http://crash-stats.mozilla.com/report/index/ee0ff106-56f4-4858-9439-828702101016
http://crash-stats.mozilla.com/report/index/70e1270a-7e34-4292-b6fc-10af82101016
http://crash-stats.mozilla.com/report/index/4e1bfd68-434d-4808-8867-0e3b52101016
http://crash-stats.mozilla.com/report/index/04c5b4ec-9c19-497e-a563-25bbe2101016

Device:                0622  G94 [GeForce 9600 GT]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0xb3450
7 crash reports, here's one of them:
http://crash-stats.mozilla.com/report/index/b5c7dbea-31a2-474b-b70e-6bf4c2101012

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x1638cf
8 crash reports, here's one of them:
http://crash-stats.mozilla.com/report/index/0308b24c-2da9-413f-8032-301262101015

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x51909
5 crash reports, here's one of them:
http://crash-stats.mozilla.com/report/index/e9e843e0-0b7b-4895-b5d2-d64812101013

Device:                0615  G92 [GeForce GTS 250]
NVIDIA driver version: 258.96
address:               nvwgf2um.dll@0x3cfaca
6 crash reports, here's one of them:
http://crash-stats.mozilla.com/report/index/fd84d919-4f9e-49af-96d4-aa4da2101011
Blocks: 605746
No longer blocks: 585973, 605746
Depends on: 585973, 605746, 604278, 604124, 598437, 595929, 593779, 587271
No longer depends on: 595364
No longer depends on: 585973, 587271, 593779, 595929, 598437, 604124, 604278, 605746
Summary: NVIDIA driver crashes tracking bug → NVIDIA driver crashes [@ nvwgf2um.dll@0x.....]
Blocks: 605749
(In reply to comment #26)
> Can someone please forward this comment to NVIDIA?
> 
> These crashes are with recent NVIDIA drivers, on recent NVIDIA hardware.
> 
I've sent the guys I talked to last week an e-mail, hopefully they can put us in touch with the right people.
Filed 606200 about nvwgf2um.dll@0x45e14 , which is the "most popular" nvidia crash except that all reports seem to come from a single user. This one goes in the direction of blacklisting 186.91 if we get more reports from other users.
Filed 606211 about a crash (second "most popular" nvidia crash, but again seemingly from one user only) with driver version 156.71.
Bug 606225: another crash, this time with RECENT driver 258.96
Whiteboard: need-to-report-to-NVIDIA
There are 2 things in this bug.

1) the original crash report. Re-assigning to Bas.

  ---> Bas: check if you think it's the same as bug 612125

2) it's been used as a tracking bug for NVIDIA crashes, but we should now use bug 605749 for that.
Assignee: bjacob → bas.schouten
There's not enough to go on here. Please file new bugs if issues exist!
Status: NEW → RESOLVED
blocking2.0: betaN+ → -
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Crash Signature: [@ nvwgf2um.dll@0x.....]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: