Hi Bob, I'm going to file a couple of bugs. This is the fourth most popular crash, it seems to be Flash talking directly to nVidia. I've saved the .dmp file for 502ef7b6-23e8-4202-a58b-567c22100731. I'll try to get someone to see if we can track down a reporter, however based on the nice crash address and the fact that nvidia doesn't seem to be omitting frame pointers, I hope you can do something w/o a dump. If you can provide public symbols (as flash has), either to mozilla in general, or to me directly, we can try to improve the stack report. If you need help from Adobe, just ask, they should be watching this component. The symbols listed for the Flash frames are mangled in some way to enable them to recognize functions w/o disclosing too much. Tomcat: can you try to track down an email address for which we have a dump? Signature nvapi.dll@0x75e2e UUID 502ef7b6-23e8-4202-a58b-567c22100731 Process Type plugin Version: Filename: NPSWF32.dll Time 2010-07-31 04:28:19.2023 Uptime 86301 Install Age 719878 seconds (1.2 weeks) since version was first installed. Product Firefox Version 3.6.7 Build ID 20100713130626 Branch 1.9.2 OS Windows NT OS Version 5.1.2600 Service Pack 2 CPU x86 CPU Info AuthenticAMD family 15 model 44 stepping 2 Crash Reason EXCEPTION_ACCESS_VIOLATION Crash Address 0xffffffffe2344440 Email Address URL User Comments Processor Notes EMCheckCompatibility False Crashing Thread Frame Module Signature [Expand] Source 0 nvapi.dll nvapi.dll@0x75e2e 1 NPSWF32.dll F_401645424_______________________________________________________ F_1491669247___________________________________________________:211 2 NPSWF32.dll F_870979891_________________________ F940344023_____________________________________________________:2872 3 NPSWF32.dll F1410605401________________________________________________________ F_1233430385________________________________________________________:538 4 NPSWF32.dll F_1510072998________________________________________________________________ F1626822717____________________________________________:1242 5 NPSWF32.dll F_1182767316______________________________________________ F_537549602___________________________________________:197 6 NPSWF32.dll F_1367580201________________________________________________ F_537549602___________________________________________:552 7 NPSWF32.dll F_1597459248____________________________________________________________ F_537549602___________________________________________:2164 8 NPSWF32.dll F_1870130569__________________________________________________________________________ F_537549602___________________________________________:2685 9 NPSWF32.dll F1504482342_______________________________________________________________________ F_537549602___________________________________________:3005 10 NPSWF32.dll F745443706________________________________________________ F816923628_____________________________________________:3224 11 NPSWF32.dll F_1764067967_________________________________________________ F816923628_____________________________________________:3007 12 NPSWF32.dll F450165255___________________________ F816923628_____________________________________________:5198 13 NPSWF32.dll F1295919189______________________________________ F2042946143____________________________________________:1802 14 NPSWF32.dll F_1311131038_________________________________________ F2042946143____________________________________________:3441 15 NPSWF32.dll F_2025036863______________________ F1602437284_________________________________________:11121 16 NPSWF32.dll F_1995396427_________________ F1602437284_________________________________________:11974 17 NPSWF32.dll F1546913566_____________________________________ F_1343382264_______________________________________________________________________:3838 18 NPSWF32.dll F957328252________________________ F_1343382264_______________________________________________________________________:505 19 user32.dll InternalCallWinProc 20 user32.dll UserCallWinProcCheckWow 21 user32.dll CallWindowProcAorW 22 user32.dll CallWindowProcW 23 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run dom/plugins/PluginInstanceChild.cpp:1398 24 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:336 25 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:344 26 xul.dll MessageLoop::DoDelayedWork 27 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:218 28 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:52 29 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 30 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:216 31 xul.dll MessageLoop::RunHandler 32 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:173 33 xul.dll base::Thread::ThreadMain ipc/chromium/src/base/thread.cc:165 34 xul.dll `anonymous namespace'::ThreadFunc ipc/chromium/src/base/platform_thread_win.cc:26 35 kernel32.dll BaseThreadStart NPSWF32.dll 10.1.53.64 547FB6F990234E7FAABA5DE4C9F5BB911 NPSWF32.pdb nvapi.dll 6.14.12.5896 ECCA532735A641ABB46FEA79F4448D741 nvapi.pdb We have 89 crashes in the past week. They're limited to XP sp2/sp3. Covering Firefox 3.6.6, 3.6.7, 3.6.8, 4.0b2, and Thunderbird 3.0.3.

oops, I got the summary stats wrong :( We have 89 crashes in the past week. They're limited to XP sp2/sp3. Covering Firefox 3.0.19, 3.5.7, 3.5.11, 3.6, 3.6.2, 3.6.3, 3.6.3plugin1, 3.6.4, 3.6.6, 3.6.7, 3.6.8, and 4.0b2 .

can anyone tell me what graphics card they are experiencing the issue?

(In reply to smadayag from comment #2) > can anyone tell me what graphics card they are experiencing the issue? They are various. The device ID can be 0110, 0140, 0141, 0151, 0185, 0221, 0314, 0322, 0324, 0326.

i can't find a report of this signature in the last 3 weeks. is this still an issue?

(In reply to smadayag from comment #4) > i can't find a report of this signature in the last 3 weeks. is this still > an issue? There are 330 crash reports across all Firefox versions over the last four weeks: https://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=contains&query=nvapi.dll%40&reason_type=contains&range_value=4&range_unit=weeks&hang_type=any&process_type=any&do_query=1&signature=nvapi.dll%400x75e2e

thanks! how can i map a device ID to an actual model of graphics card?

Bug 584808 which is similar has 5 more occurrences than this one. Crash reports are well distributed across device IDs and driver versions: AdapterVendorID: 10de, AdapterDeviceID: 0151, AdapterDriverVersion: 4.1.0.3 AdapterVendorID: 10de, AdapterDeviceID: 0172, AdapterDriverVersion: 5.2.1.6 AdapterVendorID: 10de, AdapterDeviceID: 0322, AdapterDriverVersion: 5.2.1.6 AdapterVendorID: 10de, AdapterDeviceID: 0150, AdapterDriverVersion: 5.3.0.3 AdapterVendorID: 10de, AdapterDeviceID: 0322, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0110, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0171, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0185, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 01a0, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0201, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0312, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0326, AdapterDriverVersion: 5.6.7.3 AdapterVendorID: 10de, AdapterDeviceID: 0326, AdapterDriverVersion: 6.1.2.1 AdapterVendorID: 10de, AdapterDeviceID: 0324, AdapterDriverVersion: 6.6.1.0 AdapterVendorID: 10de, AdapterDeviceID: 0322, AdapterDriverVersion: 6.6.9.3 AdapterVendorID: 10de, AdapterDeviceID: 00f2, AdapterDriverVersion: 7.1.2.4 AdapterVendorID: 10de, AdapterDeviceID: 00ce, AdapterDriverVersion: 7.7.5.6 AdapterVendorID: 10de, AdapterDeviceID: 0140, AdapterDriverVersion: 7.7.7.2 AdapterVendorID: 10de, AdapterDeviceID: 0141, AdapterDriverVersion: 7.7.7.2 AdapterVendorID: 10de, AdapterDeviceID: 0142, AdapterDriverVersion: 7.7.7.4 AdapterVendorID: 10de, AdapterDeviceID: 0221, AdapterDriverVersion: 7.7.7.6 AdapterVendorID: 10de, AdapterDeviceID: 0221, AdapterDriverVersion: 7.7.7.7 AdapterVendorID: 10de, AdapterDeviceID: 00f4, AdapterDriverVersion: 7.8.0.1 AdapterVendorID: 10de, AdapterDeviceID: 0221, AdapterDriverVersion: 7.8.0.1 (In reply to smadayag from comment #6) > how can i map a device ID to an actual model of graphics card? See http://developer.download.nvidia.com/SDK/9.5/Samples/DEMOS/common/src/VendorDeviceIDsExample/docs/Device_IDs.pdf

There are no crashes after Flash 11.2.

Version and milestone values are being reset to defaults as part of product refactoring.