w3wp.exe process runs at 100% cpu

I have seen references on this forum to problems where w3wp.exe/
dllhost.exe consumes 100% of cpu. We have a similar (intermittent and
difficult to replicate) problem on one of our servers running ASP and
I am struggling to identify which ASP page or process is causing the
problem.

I have observed the problem on both IIS5 (WIndows Advanced Server
2000) and IIS6 (Windows Server 2003), leading me to believe that it
might be a problem with our code but have checked all the code
thoroughly and can't see where the problem is. The server normally
runs at just 5% utilisation so I am confident this is not a simple
problem with heavy load.

I have got as far as running IISState and extracting a log file for
the process consuming all the resources but am unable to decipher the
file and identify what is going on. The log file for the thread that I
suspect (because it is the longest running) is attached. I would be
very grateful if anyone could suggest how I might debug or get any
further information on what is causing this problem!


Thread ID: 20
System Thread ID: f64
Kernel Time: 0:2:8.984
User Time: 0:22:29.437
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for C:\WINNT\system32\vbscript.dll -
Thread Type: ASP
Executing Page:

# ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may
be wrong.
00 0202f2cc 73472258 vbscript!DllGetClassObject+0x2e49
01 0202f2ec 734721e2 vbscript!DllGetClassObject+0x2dd8
02 0202f5b0 73464412 vbscript!DllGetClassObject+0x2d62
03 0202f6b4 734654d2 vbscript+0x4412
04 0202f988 73464412 vbscript+0x54d2
05 0202fa8c 7346480d vbscript+0x4412
06 0202faf0 7346d2cf vbscript+0x480d
07 0202fb40 734714ad vbscript!DllCanUnloadNow+0x76ef
08 0202fb5c 74a1c793 vbscript!DllGetClassObject+0x202d
09 0202fb8c 74a1c6ae asp!CActiveScriptEngine::TryCall+0x15
0a 0202fbd0 74a093c6 asp!CActiveScriptEngine::Call+0x4d
0b 0202fbdc 74a0865d asp!CallScriptFunctionOfEngine+0x48
0c 0202fc18 74a0846b asp!ExecuteRequest+0x19e
0d 0202fc60 74a0d9d3 asp!Execute+0x17e
0e 0202fcb0 74a2cfa7 asp!CHitObj::ViperAsyncCallback+0x452
0f 0202fcc8 787c47da asp!CViperAsyncRequest::OnCall+0x3f
10 0202fcd0 7ce72804 COMSVCS!STAActivityWorkHelper+0xa
11 0202fd14 7ce72628 ole32!EnterForCallback+0x6a
12 0202fe40 7ce724e7 ole32!SwitchForCallback+0x12f
13 0202fe68 7ce771b6 ole32!PerformCallback+0x50
14 0202fed4 7ce7700f ole32!CObjectContext::InternalContextCallback
+0x10d
15 0202fef4 787c10e5 ole32!CObjectContext::DoCallback+0x1a
16 0202ff24 787c3731 COMSVCS!STAActivityWork::DoWork+0x75
17 0202ffb4 7c57b3bc COMSVCS!STAThread::STAThreadWorker+0x353
18 0202ffec 00000000 KERNEL32!BaseThreadStart+0x52

Re: w3wp.exe process runs at 100% cpu

You grabbed the right thread. Not sure why IISState didn't get the page
name - normally it is b/c the ASP.dll symbols aren't there, but they look
correct.

Which version of IISState are you using?


Pat

wrote in message
news:1191949095.426481.49270@g4g2000hsf.googlegroups.com...
>I have seen references on this forum to problems where w3wp.exe/
> dllhost.exe consumes 100% of cpu. We have a similar (intermittent and
> difficult to replicate) problem on one of our servers running ASP and
> I am struggling to identify which ASP page or process is causing the
> problem.
>
> I have observed the problem on both IIS5 (WIndows Advanced Server
> 2000) and IIS6 (Windows Server 2003), leading me to believe that it
> might be a problem with our code but have checked all the code
> thoroughly and can't see where the problem is. The server normally
> runs at just 5% utilisation so I am confident this is not a simple
> problem with heavy load.
>
> I have got as far as running IISState and extracting a log file for
> the process consuming all the resources but am unable to decipher the
> file and identify what is going on. The log file for the thread that I
> suspect (because it is the longest running) is attached. I would be
> very grateful if anyone could suggest how I might debug or get any
> further information on what is causing this problem!
>
>
> Thread ID: 20
> System Thread ID: f64
> Kernel Time: 0:2:8.984
> User Time: 0:22:29.437
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for C:\WINNT\system32\vbscript.dll -
> Thread Type: ASP
> Executing Page:
>
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 00 0202f2cc 73472258 vbscript!DllGetClassObject+0x2e49
> 01 0202f2ec 734721e2 vbscript!DllGetClassObject+0x2dd8
> 02 0202f5b0 73464412 vbscript!DllGetClassObject+0x2d62
> 03 0202f6b4 734654d2 vbscript+0x4412
> 04 0202f988 73464412 vbscript+0x54d2
> 05 0202fa8c 7346480d vbscript+0x4412
> 06 0202faf0 7346d2cf vbscript+0x480d
> 07 0202fb40 734714ad vbscript!DllCanUnloadNow+0x76ef
> 08 0202fb5c 74a1c793 vbscript!DllGetClassObject+0x202d
> 09 0202fb8c 74a1c6ae asp!CActiveScriptEngine::TryCall+0x15
> 0a 0202fbd0 74a093c6 asp!CActiveScriptEngine::Call+0x4d
> 0b 0202fbdc 74a0865d asp!CallScriptFunctionOfEngine+0x48
> 0c 0202fc18 74a0846b asp!ExecuteRequest+0x19e
> 0d 0202fc60 74a0d9d3 asp!Execute+0x17e
> 0e 0202fcb0 74a2cfa7 asp!CHitObj::ViperAsyncCallback+0x452
> 0f 0202fcc8 787c47da asp!CViperAsyncRequest::OnCall+0x3f
> 10 0202fcd0 7ce72804 COMSVCS!STAActivityWorkHelper+0xa
> 11 0202fd14 7ce72628 ole32!EnterForCallback+0x6a
> 12 0202fe40 7ce724e7 ole32!SwitchForCallback+0x12f
> 13 0202fe68 7ce771b6 ole32!PerformCallback+0x50
> 14 0202fed4 7ce7700f ole32!CObjectContext::InternalContextCallback
> +0x10d
> 15 0202fef4 787c10e5 ole32!CObjectContext::DoCallback+0x1a
> 16 0202ff24 787c3731 COMSVCS!STAActivityWork::DoWork+0x75
> 17 0202ffb4 7c57b3bc COMSVCS!STAThread::STAThreadWorker+0x353
> 18 0202ffec 00000000 KERNEL32!BaseThreadStart+0x52
>

Re: w3wp.exe process runs at 100% cpu

On 9 Oct, 21:41, "Pat [MSFT]" wrote:
> You grabbed the right thread. Not sure why IISState didn't get the page
> name - normally it is b/c the ASP.dll symbols aren't there, but they look
> correct.
>
> Which version of IISState are you using?
>
> Pat
>
> wrote in message
>
> news:1191949095.426481.49270@g4g2000hsf.googlegroups.com...
>
>
>
> >I have seen references on this forum to problems where w3wp.exe/
> > dllhost.exe consumes 100% of cpu. We have a similar (intermittent and
> > difficult to replicate) problem on one of our servers running ASP and
> > I am struggling to identify which ASP page or process is causing the
> > problem.
>
> > I have observed the problem on both IIS5 (WIndows Advanced Server
> > 2000) and IIS6 (Windows Server 2003), leading me to believe that it
> > might be a problem with our code but have checked all the code
> > thoroughly and can't see where the problem is. The server normally
> > runs at just 5% utilisation so I am confident this is not a simple
> > problem with heavy load.
>
> > I have got as far as running IISState and extracting a log file for
> > the process consuming all the resources but am unable to decipher the
> > file and identify what is going on. The log file for the thread that I
> > suspect (because it is the longest running) is attached. I would be
> > very grateful if anyone could suggest how I might debug or get any
> > further information on what is causing this problem!
>
> > Thread ID: 20
> > System Thread ID: f64
> > Kernel Time: 0:2:8.984
> > User Time: 0:22:29.437
> > *** ERROR: Symbol file could not be found. Defaulted to export
> > symbols for C:\WINNT\system32\vbscript.dll -
> > Thread Type: ASP
> > Executing Page:
>
> > # ChildEBP RetAddr
> > WARNING: Stack unwind information not available. Following frames may
> > be wrong.
> > 00 0202f2cc 73472258 vbscript!DllGetClassObject+0x2e49
> > 01 0202f2ec 734721e2 vbscript!DllGetClassObject+0x2dd8
> > 02 0202f5b0 73464412 vbscript!DllGetClassObject+0x2d62
> > 03 0202f6b4 734654d2 vbscript+0x4412
> > 04 0202f988 73464412 vbscript+0x54d2
> > 05 0202fa8c 7346480d vbscript+0x4412
> > 06 0202faf0 7346d2cf vbscript+0x480d
> > 07 0202fb40 734714ad vbscript!DllCanUnloadNow+0x76ef
> > 08 0202fb5c 74a1c793 vbscript!DllGetClassObject+0x202d
> > 09 0202fb8c 74a1c6ae asp!CActiveScriptEngine::TryCall+0x15
> > 0a 0202fbd0 74a093c6 asp!CActiveScriptEngine::Call+0x4d
> > 0b 0202fbdc 74a0865d asp!CallScriptFunctionOfEngine+0x48
> > 0c 0202fc18 74a0846b asp!ExecuteRequest+0x19e
> > 0d 0202fc60 74a0d9d3 asp!Execute+0x17e
> > 0e 0202fcb0 74a2cfa7 asp!CHitObj::ViperAsyncCallback+0x452
> > 0f 0202fcc8 787c47da asp!CViperAsyncRequest::OnCall+0x3f
> > 10 0202fcd0 7ce72804 COMSVCS!STAActivityWorkHelper+0xa
> > 11 0202fd14 7ce72628 ole32!EnterForCallback+0x6a
> > 12 0202fe40 7ce724e7 ole32!SwitchForCallback+0x12f
> > 13 0202fe68 7ce771b6 ole32!PerformCallback+0x50
> > 14 0202fed4 7ce7700f ole32!CObjectContext::InternalContextCallback
> > +0x10d
> > 15 0202fef4 787c10e5 ole32!CObjectContext::DoCallback+0x1a
> > 16 0202ff24 787c3731 COMSVCS!STAActivityWork::DoWork+0x75
> > 17 0202ffb4 7c57b3bc COMSVCS!STAThread::STAThreadWorker+0x353
> > 18 0202ffec 00000000 KERNEL32!BaseThreadStart+0x52- Hide quoted text -
>
> - Show quoted text -

The version I'm using is IISState 3.3.1, there is a symbol file
directory "symbols" in the c:\iisstate directory which contains 26
folders including asp.dbg, dllhost.dbg and dllhost.pdb but the asp.dll
file/folder doesn't seem to have been downloaded by IISState. Do you
know where can I get this file, can I copy it from somewhere else? I
have run IISState again on another dllhost.exe process and the asp.dll
file was not downloaded.

Re: w3wp.exe process runs at 100% cpu

The ASP.dll symbol file (asp.dbg or asp.pdb) appears to be there, so I don't
think that is the issue. Did you have a .dmp file created with this log &
can you post it somewhere? I can take a quick look & pull the page out.
For those keeping score at home, the method to do that is to open the .dmp
file with WinDBG, switch to the offending thread (~20s), dump the
stack (kb ), then dump (dc

Re: w3wp.exe process runs at 100% cpu

On 10 Oct, 18:27, "Pat [MSFT]" wrote:
> The ASP.dll symbol file (asp.dbg or asp.pdb) appears to be there, so I don't
> think that is the issue. Did you have a .dmp file created with this log &
> can you post it somewhere? I can take a quick look & pull the page out.
> For those keeping score at home, the method to do that is to open the .dmp
> file with WinDBG, switch to the offending thread (~20s), dump the
> stack (kb ), then dump (dc