Prev: Safely removing hardware
Next: Win64 , InterlockedCompareExchange128 and early AMDs
From: hooway on 31 Jan 2007 01:13
I'm getting the following error randomly when my service is running in
Win2003 server.

Source: Application Error
Category: (100)
Type: error
Event ID: 1000

Faulting Application: myservice.exe
Version: 2.7.1.0
Faulting Module: ntdll.dll
Version: 5.2.3790.1830
Fault Address: 0x0002f350


It works well in Win2000 server and XP

How to solve it? Any hints are welcome.


Hooway
From: Max on 31 Jan 2007 06:33
If I understand correct, it might meen stack overflow.
(ERROR_STACK_OVERFLOW)

Do you have a dead loop calling functions?

"hooway" <lavasoft(a)lavasoftware.net> wrote in message
news:kmc0s2tvb9hj740aqtt61dddtf9silqua2(a)4ax.com...
> I'm getting the following error randomly when my service is running in
> Win2003 server.
>
> Source: Application Error
> Category: (100)
> Type: error
> Event ID: 1000
>
> Faulting Application: myservice.exe
> Version: 2.7.1.0
> Faulting Module: ntdll.dll
> Version: 5.2.3790.1830
> Fault Address: 0x0002f350
>
>
> It works well in Win2000 server and XP
>
> How to solve it? Any hints are welcome.
>
>
> Hooway


From: Scherbina Vladimir on 1 Feb 2007 09:13
Try to get the call stack when error will occure next time and write it
here.

--
Vladimir
"hooway" <lavasoft(a)lavasoftware.net> wrote in message
news:kmc0s2tvb9hj740aqtt61dddtf9silqua2(a)4ax.com...
> I'm getting the following error randomly when my service is running in
> Win2003 server.
>
> Source: Application Error
> Category: (100)
> Type: error
> Event ID: 1000
>
> Faulting Application: myservice.exe
> Version: 2.7.1.0
> Faulting Module: ntdll.dll
> Version: 5.2.3790.1830
> Fault Address: 0x0002f350
>
>
> It works well in Win2000 server and XP
>
> How to solve it? Any hints are welcome.
>
>
> Hooway

From: George on 1 Mar 2007 10:37
Hi, I'm facing the same problem. How can I retrieve the stack when the
program is running on a system?

What is the most common reason for this fault?

TA

"Scherbina Vladimir" <v_scherbina(a)online.mvps.org> wrote in news:8ECBDD5A-
02B9-4278-B7D5-A772BB1A610D(a)microsoft.com:

> Try to get the call stack when error will occure next time and write it
> here.
>



--
Saludos a todos
#
# Contra el terrorismo
#
 | 
Pages: 1
Prev: Safely removing hardware
Next: Win64 , InterlockedCompareExchange128 and early AMDs