Closed Bug 598896 Opened 14 years ago Closed 9 years ago

crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] mainly with Norton IPS 2.0

Categories

(Core :: General, defect)

x86
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX
Tracking Status
blocking2.0 --- -

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, user-doc-needed)

Crash Data

Build : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100922 Firefox/4.0b7pre

This is a new crash signature that first appeared in 3.6.10 and is also present in trunk builds.
It is #9 top crasher for b7pre/20100922 build.

It is different from bug 545244 that implicates GrabPro.

Here is a list of useful user's comments without the f.. words :
"I can not access the plugin. Firefox unexpectedly quits and gives me this error: A script on this page may be busy or have stopped responding. You can stop the script now, or wait to see if the script ends its execution. Script: file: / / / C: / Program%% 20Files/Mozilla 20Firefox/components/nsExtensionManager.js: 623"
"flash causing crash"
"Firefox continues to crash as soon as it opens. I have tried to clse or delete any tabs and it doesn't seem to make a difference. Help"
"works like crap since new update"
"doesn't want to load youtube.com page...."
"4th crash in 2 minutes, several web pages "
"This is the 23rd crash today. "
"its been happening everytime i go onto a website and its very frustrating!!!! "

Signature	zzz_AsmCodeRange_Begin
UUID	f00f2c40-1254-44d6-91b8-3abac2100922
Time 	2010-09-22 11:58:08.402914
Uptime	126
Last Crash	149 seconds before submission
Install Age	15099 seconds (4.2 hours) since version was first installed.
Product	Firefox
Version	4.0b7pre
Build ID	20100922041040
Branch	2.0
OS	Windows NT
OS Version	6.1.7600
CPU	x86
CPU Info	GenuineIntel family 6 model 23 stepping 10
Crash Reason	0xc000070a / 0x00000000
Crash Address	0x77649d74
App Notes 	AdapterVendorID: 8086, AdapterDeviceID: 29c2

Crashing Thread
Frame 	Module 	Signature [Expand] 	Source
0 	ntdll.dll 	zzz_AsmCodeRange_Begin 	
1 	kernel32.dll 	kernel32.dll@0x51193 	
2 	ntdll.dll 	__RtlUserThreadStart 	
3 	ntdll.dll 	_RtlUserThreadStart 	

Thread 0
Frame 	Module 	Signature [Expand] 	Source
0 	ntdll.dll 	KiFastSystemCallRet 	
1 	ntdll.dll 	ZwWaitForSingleObject 	
2 	KERNELBASE.dll 	WaitForSingleObjectEx 	
3 	kernel32.dll 	kernel32.dll@0x4f002 	
4 	kernel32.dll 	kernel32.dll@0x4efb1 	
5 	nspr4.dll 	_PR_MD_WAIT_CV 	nsprpub/pr/src/md/windows/w95cv.c:280
6 	nspr4.dll 	_PR_WaitCondVar 	nsprpub/pr/src/threads/combined/prucv.c:204
7 	nspr4.dll 	PR_Wait 	nsprpub/pr/src/threads/prmon.c:184
8 	xul.dll 	mozilla::Monitor::Wait 	obj-firefox/dist/include/mozilla/Monitor.h:123
9 	xul.dll 	mozilla::ipc::GeckoChildProcessHost::SyncLaunch 	ipc/glue/GeckoChildProcessHost.cpp:287
10 	xul.dll 	mozilla::plugins::PluginProcessParent::Launch 	dom/plugins/PluginProcessParent.cpp:111
11 	xul.dll 	mozilla::plugins::PluginModuleParent::LoadModule 	dom/plugins/PluginModuleParent.cpp:94
12 	xul.dll 	GetNewPluginLibrary 	modules/plugin/base/src/nsNPAPIPlugin.cpp:433
13 	xul.dll 	nsNPAPIPlugin::CreatePlugin 	modules/plugin/base/src/nsNPAPIPlugin.cpp:455
14 	xul.dll 	CreateNPAPIPlugin 	modules/plugin/base/src/nsPluginHost.cpp:1756
15 	xul.dll 	nsPluginHost::GetPlugin 	modules/plugin/base/src/nsPluginHost.cpp:1795
16 	xul.dll 	nsPluginHost::TrySetUpPluginInstance 	modules/plugin/base/src/nsPluginHost.cpp:1307
17 	xul.dll 	nsPluginHost::SetUpPluginInstance 	modules/plugin/base/src/nsPluginHost.cpp:1230

More reports at :
http://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=exact&query=zzz_AsmCodeRange_Begin&date=09%2F23%2F2010%2003%3A08%3A21&range_value=4&range_unit=weeks&hang_type=any&process_type=any&plugin_field=&plugin_query_type=&plugin_query=&do_query=1&admin=&signature=zzz_AsmCodeRange_Begin
blocking2.0: --- → ?
It is also present in 3.6.9.
Keywords: regression
The exception is STATUS_THREADPOOL_HANDLE_EXCEPTION, thrown by Windows. There's no docs on this exception at all that I've found. It's mentioned at http://msdn.microsoft.com/en-us/library/cc704588%28PROT.10%29.aspx but there aren't details. It's likely to be a resource issue in Windows itself, although I don't know what.

I'm going to clear the blocking nom for now, because I don't think this is a topcrasher, but we can renom if it shows up in the topcrash lists for betas (not nightlies).
blocking2.0: ? → ---
http://www.techsupportforum.com/microsoft-support/windows-vista-windows-7-support/513834-solved-ntdll-dll-issues.html#post2899624

As a start, someone would have needed to take the .dmp and feed it to !analyze. But the next step is to enable verifier:

> Sure enough, the Verifier 0xC2 pointing to nvcwfcpo.sys - my school's
> VPN client. It wouldn't surprise me at all, but I just set up the VPN
> around two weeks ago but I've had this problem for months, and when I
> got the BSOD itself flagged ndis.sys.

ted: I win. I fingered the driver in one of the threads :)
volume regression looks like it is continuing on recent b7pre/b8pre builds and its still ranked around #11 there.


20101006 114  80 3.6.102010091412, 
	     9 3.6.92010082415, 6 3.6.82010072215, 
	     5 4.0b62010091408, 2 4.0b7pre2010100204, 
	     2 3.6.72010071313, 2 3.6.62010062523, 
	     2 3.6.112010100108, 1 4.0b7pre2010100504, 
	     1 4.0b52010083108, 1 4.0b42010081813, 
	     1 4.0b2pre2010070704, 1 3.6.42010061114, 
	     1 3.62010011514, 
20101007 169  95 3.6.102010091412, 
	     24 4.0b62010091408, 20 4.0b8pre2010100704, 
	     5 3.6.92010082415, 5 3.6.112010100108, 
	     4 4.0b2pre2010070704, 4 3.6.82010072215, 
	     4 3.6.62010062523, 3 4.0b42010081813, 
	     1 4.0b7pre2010091804, 1 4.0b52010083108, 
	     1 4.0b32010080519, 1 4.0b22010072019, 
	     1 3.6b12009102917, 
20101008 126  86 3.6.102010091412, 
	     7 4.0b8pre2010100704, 6 4.0b62010091408, 
	     6 3.6.82010072215, 4 3.6.62010062523, 
	     4 3.6.112010100108, 3 4.0b52010083108, 
	     2 3.6.92010082415, 2 3.6.42010061114, 
	     1 4.0b12010063014, 1 3.6.72010071313, 
	     1 3.62010011514, 1 3.5b42009042320, 
	     1 3.0.52008120122, 1 3.0.192010031422, 
20101009 143  87 3.6.102010091412, 
	     17 3.6.112010100108, 10 4.0b62010091408, 
	     9 3.6.82010072215, 6 3.6.92010082415, 
	     4 3.6.62010062523, 3 4.0b52010083108, 
	     2 4.0b42010081813, 1 4.0b8pre2010100804, 
	     1 3.6.42010061114, 1 3.6.32010040108, 
	     1 3.6.22010031607, 1 3.1b32009030515, 
20101010 139  87 3.6.102010091412, 
	     8 3.6.112010100108, 7 4.0b8pre2010101004, 
	     6 4.0b8pre2010100704, 6 4.0b62010091408, 
	     4 4.0b42010081813, 4 3.6.82010072215, 
	     4 3.6.62010062523, 3 3.62010011514, 
	     2 4.0b32010080519, 2 3.6.92010082415, 
	     1 4.0b52010083108, 1 4.0b22010072019, 
	     1 3.6b52009120414, 1 3.6.42010051314, 
	     1 3.6.32010040108, 1 3.5.132010091413,
chofmann: so, it'd be helpful if we could contact people experiencing this and ask them to use verifier.exe.

Microsoft's description:
http://support.microsoft.com/kb/244617

General steps:
1. open the start menu and browse to (or type) "Command Prompt"
2. right click and select "Run as administrator"
3. verifier.exe /standard /all
4. You will be instructed (in the command prompt) to restart. You need to do so.
5. proceed as normal.
6. if you notice crashes, please comment here
7. if the crashes are in Firefox, please follow the instructions at https://developer.mozilla.org/en/how_to_get_a_stacktrace_for_a_bug_report
8. if you notice Blue Screens or crashes in other applications after enabling verifier, please comment here, you can follow the instructions in https://developer.mozilla.org/en/how_to_get_a_stacktrace_with_windbg applied to the .dmp files that are listed in Windows's send crash report details

To disable verifier:
1. open the start menu and browse to (or type "Command Prompt")
2. right click and select "Run as administrator"
3. verifier.exe /reset
4. You will be instructed (in the command prompt) to restart. You need to do so.
5. proceed as normal.
Summary: crash [@ zzz_AsmCodeRange_Begin ] → crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632]
It is #17 top crasher in 4.0b8pre for the last 3 days.

According to crash stats correlations, 90% of crashes with that signature happens with Norton IPS 2.0 vs 1% for all crashes.
blocking2.0: --- → ?
Summary: crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] → crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] mainly with Norton IPS 2.0
kev, can you have our norton contacts have a look at this one?
I'm not going to block on this from nightly user data: only if it shows as #20 or higher in a widespread beta.
blocking2.0: ? → ---
tomcat,  want to take a crack at timeless' suggestion in comment 5?
(In reply to comment #9)
> tomcat,  want to take a crack at timeless' suggestion in comment 5?

sure but i need a reproducible url right ? :)
or you need to datamine and find someone w/ a live email address and walk them through enabling verifier. verifier just slows down systems, it doesn't prevent people from using their computer (except to the extent that they have lots of buggy drivers...). when the computer faults, your user gets back to us and we analyze their .dmp.
> I'm not going to block on this from nightly user data: only if it shows as #20
> or higher in a widespread beta.
It is #20 top crasher in 4.0b9 over the last week. Should we consider it as a blocker?
blocking2.0: --- → ?
blocking2.0: ? → -
Today, it drops to #30 top crasher.

In beta9, it is no more correlated to Norton IPS (correlation in nightlies).

Here are the 3 first add-on correlations:
20% (3/15) vs.   5% (1942/39669) mozilla_cc@internetdownloadmanager.com (IDM CC, https://addons.mozilla.org/addon/6973)
13% (2/15) vs.   2% (598/39669) ffxtlbr@Facemoods.com
13% (2/15) vs.   2% (852/39669) {a0d7ccb3-214d-498b-b4aa-0e8fda9a7bf7} (WOT, https://addons.mozilla.org/addon/3456)
Summary: crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] mainly with Norton IPS 2.0 → crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632]
Probably the same issue as bug 644125, a comment mentions the quarantine
Correlations with Norton IPS 2.0 give 61% in 3.6.15 and 66% in 4.0.
Summary: crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] → crash [@ zzz_AsmCodeRange_Begin ][@ ntdll!TppWaiterpThread+0x00000632] mainly with Norton IPS 2.0
Keywords: topcrash
lets get links to how to solve the Norton problem here too, and hook up the e-mal auto responder to the zzz_AsmCodeRange_Begin signature.

we can tell another 700+ people per day about how to fix this with teh auto responder.
Keywords: user-doc-needed
Crash Signature: [@ zzz_AsmCodeRange_Begin ] [@ ntdll!TppWaiterpThread+0x00000632]
Still valid on recent versions. We have about 250 on 8.0 in the past 4 weeks and 331 on 7.0.1 in the past 4 weeks. Kind of a generic signature. Removing the top crash keyword since the volume isn't very high.

There is a second bug open on this as well - bug 545244.
Crash Signature: [@ zzz_AsmCodeRange_Begin ] [@ ntdll!TppWaiterpThread+0x00000632] → [@ zzz_AsmCodeRange_Begin ] [@ ntdll!TppWaiterpThread+0x00000632]
Keywords: topcrash
Depends on: 793430
Hey there. Just thought I'd mention that a friend was having this problem. Looking at her crash report, I noticed that it was linked to msvcr100.dll, and apparently somehow linked to Steam. When Steam was closed, the crashes stopped happening. So that might be somewhere to start looking?

If this is a persistent issue, I'll see about getting some kind of dump report.
Norton IPS 2.0 is obsolete.
Blocks: Norton
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.