New Crash in Chofmann's Crash List for Firefox 4 Beta 5 - http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&date=2010-09-14%2014%3A00%3A00&signature=d3d10_1core.dll%400xa642&version=Firefox%3A4.0b5 all Windows 7 Crashes and seem comments are not very useful in this case. Frame Module Signature [Expand] Source 0 KERNELBASE.dll RaiseException 1 d3d10_1core.dll d3d10_1core.dll@0xa642 2 d3d10_1core.dll d3d10_1core.dll@0x2cc6e 3 igd10umd32.dll igd10umd32.dll@0x1e4d6 4 d3d10_1core.dll d3d10_1core.dll@0x137f5 5 d3d10_1core.dll d3d10_1core.dll@0x1ac1e 6 d3d10_1core.dll d3d10_1core.dll@0x1b489 7 d3d10_1core.dll d3d10_1core.dll@0xa1b7 8 dxgi.dll dxgi.dll@0x4423 9 dxgi.dll dxgi.dll@0x43f0 10 dxgi.dll dxgi.dll@0x47b4 11 dxgi.dll dxgi.dll@0x46a5 12 dxgi.dll dxgi.dll@0x4628 13 dxgi.dll dxgi.dll@0x405c 14 d3d10_1core.dll d3d10_1core.dll@0x1b965 15 d3d10_1core.dll d3d10_1core.dll@0x1cb8a 16 d3d10_1core.dll d3d10_1core.dll@0x1d70c 17 d3d10_1core.dll d3d10_1core.dll@0x1e02a 18 d3d10_1core.dll d3d10_1core.dll@0x90ce 19 dxgi.dll dxgi.dll@0x3e9a 20 dxgi.dll dxgi.dll@0x4264 21 dxgi.dll dxgi.dll@0x4212 22 dxgi.dll dxgi.dll@0x41be 23 d3d10_1core.dll d3d10_1core.dll@0x16c56 24 d3d10_1core.dll d3d10_1core.dll@0x1775e 25 d3d10_1core.dll d3d10_1core.dll@0x1c05c 26 d2d1.dll d2d1.dll@0x2f379 27 d2d1.dll d2d1.dll@0x326ec 28 d2d1.dll d2d1.dll@0x3110e 29 d2d1.dll d2d1.dll@0x1f1c6 30 d2d1.dll d2d1.dll@0x1ef48 31 d2d1.dll d2d1.dll@0x212c4 32 d2d1.dll d2d1.dll@0x20779 33 d2d1.dll d2d1.dll@0x1e6e7 34 d2d1.dll d2d1.dll@0x6272d 35 d2d1.dll d2d1.dll@0x32055 36 d2d1.dll d2d1.dll@0x621ef 37 d2d1.dll d2d1.dll@0x1d3f3 38 d2d1.dll d2d1.dll@0x1c25f 39 d2d1.dll d2d1.dll@0x1c8ef 40 d2d1.dll d2d1.dll@0x19127 41 xul.dll xul.dll@0x5cd67d 42 xul.dll xul.dll@0x61d052 43 xul.dll xul.dll@0x63913f 44 xul.dll xul.dll@0x32e341 45 xul.dll xul.dll@0x350a10

Happens with Intel card and out-of-date graphic driver. The up-to-date version for recent graphic card is 8.15.10.2202. It will be fixed by bug 594877.

Comment 1 was too restrictive. For the last 4 weeks, there were 577 crashes with this signature in b7pre, b6, b6pre, b5, b5pre, b4. For b7pre, b6, b6pre, the breakdown is as below : VendorID Graphic driver versions up-to-date driver 8086 (Intel) 8.15.10.1749, 1855, 1872, 1892 (about 97 %) 8.15.10.2202 1002 (ATI) 8.17.10.1036 (aticfx32.dll) (about 1%) 8.762.0.0 10DE (NVIDIA) 8.15.11.8575 (about 1%) 8.15.12.5896 5333 (S3) 8.15.12.84 (about 1%) 8.16.12.259 A driver blacklist must be done for ATI, NVIDIA, S3, the same way as in bug 594877

Scoobidiver: * thanks for the vendor stats and summary * please open separate bugs for nvidia and ati if we don't already have any. This changeset: http://hg.mozilla.org/mozilla-central/rev/b07c0925efe5 makes 8.15.10.2202 the required intel driver version for intel 4500/HD cards. Please close this bug if it doesn't have remaining independent issues.

Chris, Is it possible to have a breakout of d3d10_1core.dll@0xa642 crash reports by : * "App notes", * "d3d10_1core.dll" version (a MS hotfix from 24/08/2010 impacts it, KB2028560 for Win7 x32 and x64) * "igd10umd32.dll" version where it exists (Intel driver) * "nvwgf2um.dll" version where it exists (Nvidia driver) * "aticfx32.dll" version where it exists (ATI driver) Thanks.

in 9 days we got 280 reports. here is the breakdown. a few missing drivers in the list that didn't match the 3 not in your list, but those can be dug out of the attachment. if you find some interesting ones I can add to the script that generated the csv. 134 AdapterVendorID: 8086, AdapterDeviceID: 2a02 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 55 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 18 AdapterVendorID: 5333, AdapterDeviceID: 9045 d3d10_1core.dll 6.1.7600.16385 1 8 AdapterVendorID: 8086, AdapterDeviceID: 2e22 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 7 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1892 1 7 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1808 1 5 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1883 1 5 AdapterVendorID: 10de, AdapterDeviceID: 0647 d3d10_1core.dll 6.1.7600.16385 nvwgf2um.dll 8.15.11.8575 1 4 AdapterVendorID: 8086, AdapterDeviceID: 2e32 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1892 1 4 AdapterVendorID: 8086, AdapterDeviceID: 2e32 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 4 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1872 1 4 AdapterVendorID: 1002, AdapterDeviceID: 6899 d3d10_1core.dll 6.1.7600.16385 aticfx32.dll 8.17.10.1043 1 3 AdapterVendorID: 8086, AdapterDeviceID: 2a12 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 3 AdapterVendorID: 8086, AdapterDeviceID: 2a02 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 2 AdapterVendorID: 8086, AdapterDeviceID: 2e32 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1855 1 2 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1855 1 2 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 2 AdapterVendorID: 1002, AdapterDeviceID: 9440 d3d10_1core.dll 6.1.7600.16385 aticfx32.dll 8.17.10.1041 1 1 AdapterVendorID: 8086, AdapterDeviceID: 2e32 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1808 1 1 AdapterVendorID: 8086, AdapterDeviceID: 2e22 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1872 1 1 AdapterVendorID: 8086, AdapterDeviceID: 2e12 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 1 AdapterVendorID: 8086, AdapterDeviceID: 2a42 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1883 1 AdapterVendorID: 8086, AdapterDeviceID: 2982 d3d10_1core.dll 6.1.7600.16385 igd10umd32.dll 8.15.10.1749 1 1 AdapterVendorID: 5333, AdapterDeviceID: 9045 d3d10_1core.dll 6.1.7600.16385 1 AdapterVendorID: 10de, AdapterDeviceID: 0863 d3d10_1core.dll 6.1.7600.16385 nvwgf2um.dll 8.15.11.8575 1 1 AdapterVendorID: 10de, AdapterDeviceID: 0425 d3d10_1core.dll 6.1.7600.16385 nvwgf2um.dll 8.15.11.8575 1 1 AdapterVendorID: 10de, AdapterDeviceID: 0390 d3d10_1core.dll 6.1.7600.16385 1 1 AdapterVendorID: 1002, AdapterDeviceID: 9513 d3d10_1core.dll 6.1.7600.16385 aticfx32.dll 8.17.10.1036 1 1 AdapterVendorID: 1002, AdapterDeviceID: 9442 d3d10_1core.dll 6.1.7600.16385 aticfx32.dll 8.17.10.1036 1

I wonder if it makes sense to do this kind of analysis on some of the other d3d10_1core.dll signatures? d3d10_1core.dll signature breakdown for 20100921 signature distribution 14 signature list 55 d3d10_1core.dll@0xa642 20 d3d10_1core.dll@0x2bb04 10 d3d10_1core.dll@0x3080b 9 d3d10_1core.dll@0xa80a 6 d3d10_1core.dll@0xa5e3 6 d3d10_1core.dll@0x2bb34 5 d3d10_1core.dll@0x31018 2 d3d10_1core.dll@0x2a1b0 2 d3d10_1core.dll@0x1fdc1 1 d3d10_1core.dll@0x2c548 1 d3d10_1core.dll@0x2c329 1 d3d10_1core.dll@0x2bfa6 1 d3d10_1core.dll@0x1f88b 1 d3d10_1core.dll@0x18bf6

re: comment 6 > sept 10-28 that should have been sept 20-28

It happens only on Win Vista and 7. It does not happens with d3d10_1core.dll 6.1.7600.20781 (KB2028560 for Win7 x32 and x64) I try to find the implicated driver version because the blacklisting by DeviceID must be done in the last case. Here is a summary of the implicated D3D10 modules by GPU manufacturer : * Intel : it is now fixed by the landing of bug 594877 and bug 595364. * Nvidia : nvwgf2um.dll : 8.15.11.8575 (up-to-date for recent cards : x.y.z2.5696) * ATI : aticfx32.dll : 8.17.10.1036, .1041, .1043 (up-to-date for recent cards : x.y.z.8762) * S3 graphics : S3DDX10_32.dll : 8.15.12.78, .84 (up-to-date for recent cards : 8.16.12.0259) There are several solutions : 1. do nothing and hope the KB2028560 update will be done on every Win7 platform and it will correct the issue which is not proved 2. disable D2D/D3D features on Vista/7 by allowing only the latest graphic driver version 3. the same as 2. but with OS that have an old version of d3d10_1core.dll

Great info in comment 9, sorry I'm only getting back to it now. I think we should implement idea 3. in comment 9.

So, we have a big problem on ATI: version 8.17.10.1043 is Catalyst 10.9, the current version! See: http://developer.amd.com/drivers/ccc/Pages/default.aspx So blacklisting it would be blacklisting all ATI cards. Also, the current title of this bug is inaccurate. The fact that this happens on recent drivers and on multiple vendors suggests that it might be our bug!!

Do we have any STR here?

looks like 100% Windows NT6.1.7600 and whatever hardware + driver combo then test urls to try find a bunch of images on http://www.google.com/imghp facebook login and try out http://apps.facebook.com/speeddateah http://www.tagged.com/profile.html?uid=5425394663 http://www.yoshinoya-hk.com/location2.php?id=2 http://www.pregnancymiracle.com/Pregnancy-Miracle.htm?hop=m231g http://jogarjogos.blogspot.com/2008/08/gaja-voadora.html http://www.gockhuat.eu/forum/forumdisplay.php?16-H%ECnh-ch%E2u-%E1 http://pipl.com/directory/people/Amir/Majidimehr and a bunch of adult video sites http://www.highporntube.com http://www.black4porn.com http://nudes-celeb.ne

> Do we have any STR here? Here is a STR for an ATI card with aticfx32.dll version 8.17.10.1043 : Signature d3d10_1core.dll@0xa642 UUID e411dc9a-0401-4dc0-b206-5e2792100926 Time 2010-09-26 17:56:09.645860 Uptime 1384 Last Crash 6159 seconds (1.7 hours) before submission Install Age 33580 seconds (9.3 hours) since version was first installed. Product Firefox Version 4.0b7pre Build ID 20100926042726 Branch 2.0 OS Windows NT OS Version 6.1.7600 CPU x86 CPU Info GenuineIntel family 6 model 30 stepping 5 Crash Reason 0x00000879 / 0x00000000 Crash Address 0x75209617 App Notes AdapterVendorID: 1002, AdapterDeviceID: 6899 Frame Module Signature [Expand] Source 0 KERNELBASE.dll RaiseException 1 d3d10_1core.dll d3d10_1core.dll@0xa642 2 d3d10_1core.dll d3d10_1core.dll@0x2cc6e 3 atidxx32.dll atidxx32.dll@0x515b 4 atidxx32.dll atidxx32.dll@0x9554 5 atidxx32.dll atidxx32.dll@0x11eb9 6 atiuxpag.dll atiuxpag.dll@0x1c4d 7 aticfx32.dll aticfx32.dll@0xab63 8 aticfx32.dll aticfx32.dll@0x2ab0c 9 aticfx32.dll aticfx32.dll@0x280c5 10 aticfx32.dll aticfx32.dll@0x290e1 11 aticfx32.dll aticfx32.dll@0x2f845 12 aticfx32.dll aticfx32.dll@0x2197 13 d3d10_1core.dll d3d10_1core.dll@0x2e9a4 14 d3d10_1core.dll d3d10_1core.dll@0x31266 15 xul.dll xul.dll@0x60db17

(Scoobidiver: STR means steps-to-reproduce, not stack trace! ;-)

It looks like d3d10_1core.dll@0xa642 is CDevice::DriverInternalErrorCB with d3d10_1core.dll version 6.1.7600.16385

This is being called by the driver through pfnSetErrorCb

Taking a look at a minidump should let us figure out what the error code is.

Looks like the error in this case bp-e411dc9a-0401-4dc0-b206-5e2792100926 is D3DERR_OUTOFVIDEOMEMORY

This doesn't need to block a time-based beta 8.

There have been no crashes for the last four weeks. I close it as WFM.