By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,905 Members | 879 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,905 IT Pros & Developers. It's quick & easy.

Vb.Net application is terminated unexpectedly without message

P: n/a
Hello!

I have some Vb.Net applications, which are terminated at indefinite times
without message.

If I call in the program regulated system.GC.Collect, then the program is
terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na po
nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000
efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx]
ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat
Nov 21 '05 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Please cross-post, not multipost
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hello!

I have some Vb.Net applications, which are terminated at indefinite times
without message.

If I call in the program regulated system.GC.Collect, then the program is
terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na po
nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat

Nov 21 '05 #2

P: n/a
Ralf

What is your program doing? Does it use any serial comms? Can you tell us a
bit more about the APIs it is using?

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hello!

I have some Vb.Net applications, which are terminated at indefinite times
without message.

If I call in the program regulated system.GC.Collect, then the program is
terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na po
nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat

Nov 21 '05 #3

P: n/a
Hi Charles,

Yes, i use serial comm ports via Api from www.codeworks.it/net/index.htm
Rev.21 (24/10/2004).
But i thing i had the same problem with the ActiveX from Microsoft
MSCOMM32.OCX.

I use one or more comm ports in the applications.
Data comes from Comm-Ports and are stored in SQL2k-Database via adodb.
A visualisation with datagrids will shown on screen.
This is that what the program do.

The error with 'application-termination unexpectedly without message' is
very sensible.
In other applications (with comm-ports too) will work longer without
termination.
Same applications have no problem, I think, the more complex the projects
am, the rather arise the problems.

Bye
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:Oe******************@TK2MSFTNGP14.phx.gbl...
Ralf

What is your program doing? Does it use any serial comms? Can you tell us
a bit more about the APIs it is using?

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hello!

I have some Vb.Net applications, which are terminated at indefinite times
without message.

If I call in the program regulated system.GC.Collect, then the program is
terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat


Nov 21 '05 #4

P: n/a
How explained under
http://support.microsoft.com/default...;en-us;Q286350
I have do a Crash-Debug with
ADPlus -crash -pn <EXE>

Here the logfile.

Danke.
Ralf Gedrat

Opened log file 'C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__Date_01-31-2005__Time_22-32-2929.log'
0:012> * Created with ADPlus Version 6.02.018 Version Date 09/28/2004
0:012> *
0:012> * --------- ADPlus was started at: -----------
0:012> .time
Debug session time: Mon Jan 31 22:32:31.030 2005 (GMT+1)
System Uptime: 19 days 10:44:09.616
Process Uptime: 0 days 0:00:04.246
Kernel time: 0 days 0:00:00.230
User time: 0 days 0:00:00.110
0:012> * ------------------------------------------------------
0:012> *
0:012> *
0:012> *
0:012> * --------- ADPlus 6.02.018 was run on server: --------
0:012> * Server name: GEDRATSBS
0:012> * ------------------------------------------------------
0:012> *
0:012> *
0:012> *
0:012> * ------ OS Version Information displayed below. -------
0:012> !version
No export version found
0:012> * ------------------------------------------------------
0:012> *
0:012> *
0:012> *
0:012> *
0:012> * ------ Current Actions for Exceptions ----
0:012> * AccessViolation [av] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * InvalidHandle [ch] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * IllegalInstruction [ii] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * IntegerDivide [dz] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * FloatingDivide [c000008e] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * IntegerOverflow [iov] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * InvalidLockSequence [lsq] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * StackOverflow [sov] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * CPlusPlusEH [eh] return: GN GN
0:012> * 1st chance: Log;Time;Stack
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * UnknownException[*] return: GN GN
0:012> * 1st chance: Log;Time;Stack
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * NET_CLR [clr] return: GN GN
0:012> * 1st chance: VOID
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * CONTRL_C_OR_Debug_Break [bpe] return: Q GN
0:012> * 1st chance:
Log;Time;EventLog;Stacks;LoadedModules;MatchingSym bols;MiniDump;Custom_!locks
!runaway
0:012> * 2nd chance:
0:012> * Wake_Debugger [wkd] return: Q GN
0:012> * 1st chance:
Log;Time;EventLog;Stacks;LoadedModules;MatchingSym bols;MiniDump;Custom_!locks
!runaway
0:012> * 2nd chance:
0:012> * DLL_Load [ld] return: GN GN
0:012> * 1st chance: Log
0:012> * 2nd chance: Log
0:012> * DLL_UnLoad [ud] return: GN GN
0:012> * 1st chance: Log
0:012> * 2nd chance: Log
0:012> * Process_Shut_Down [epr] return: GN GN
0:012> * 1st chance: Log;Time;EventLog;Stacks;FullDump;Custom_!runaway
0:012> * 2nd chance:
0:012> * Application_hang [aph] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * Ctl_C_Console_app [cce] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * Data_misaligned [dm] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * Guard_page_violation [gp] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * In_page_IO_error [ip] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * Invalid_system_call [isc] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * Stack_buffer_overflow [sbo] return: GN GN
0:012> * 1st chance: Log;Time;Stack;MiniDump
0:012> * 2nd chance: Log;Time;Stack;FullDump;EventLog
0:012> * ------ Current symbol path ----
0:012> .sympath
Symbol search path is: C:\WINDOWS\Symbols
0:012> .echotimestamps
Event timestamps are now enabled
0:012> sxe -c @".echo ---;.echo --- 1st chance AccessViolation
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_AccessViolation_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance AccessViolation
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_AccessViolation_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_AccessViola tion__full.dmp;!elog_str
ADPlus detected a 2nd chance AccessViolation exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" av
0:012> sxe -c @".echo ---;.echo --- 1st chance InvalidHandle
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_InvalidHandle_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_InvalidHand le__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance InvalidHandle
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_InvalidHandle_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_InvalidHand le__full.dmp;!elog_str
ADPlus detected a 2nd chance InvalidHandle exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" ch
0:012> sxe -c @".echo ---;.echo --- 1st chance IllegalInstruction
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_IllegalInstruction_exception_in_G1FEHLE RMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_IllegalInst ruction__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance IllegalInstruction
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_IllegalInstruction_exception_in_G1FEHLE RMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_IllegalInst ruction__full.dmp;!elog_str
ADPlus detected a 2nd chance IllegalInstruction exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" ii
0:012> sxe -c @".echo ---;.echo --- 1st chance IntegerDivide
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_IntegerDivide_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_IntegerDivi de__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance IntegerDivide
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_IntegerDivide_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_IntegerDivi de__full.dmp;!elog_str
ADPlus detected a 2nd chance IntegerDivide exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" dz
0:012> sxe -c @".echo ---;.echo --- 1st chance FloatingDivide
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_FloatingDivide_exception_in_G1FEHLERMER KMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_FloatingDiv ide__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance FloatingDivide
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_FloatingDivide_exception_in_G1FEHLERMER KMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_FloatingDiv ide__full.dmp;!elog_str
ADPlus detected a 2nd chance FloatingDivide exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" c000008e
0:012> sxe -c @".echo ---;.echo --- 1st chance IntegerOverflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_IntegerOverflow_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_IntegerOver flow__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance IntegerOverflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_IntegerOverflow_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_IntegerOver flow__full.dmp;!elog_str
ADPlus detected a 2nd chance IntegerOverflow exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" iov
0:012> sxe -c @".echo ---;.echo --- 1st chance InvalidLockSequence
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_InvalidLockSequence_exception_in_G1FEHL ERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_InvalidLock Sequence__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance InvalidLockSequence
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_InvalidLockSequence_exception_in_G1FEHL ERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_InvalidLock Sequence__full.dmp;!elog_str
ADPlus detected a 2nd chance InvalidLockSequence exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" lsq
0:012> sxe -c @".echo ---;.echo --- 1st chance StackOverflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_StackOverflow_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_StackOverfl ow__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance StackOverflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_StackOverflow_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_StackOverfl ow__full.dmp;!elog_str
ADPlus detected a 2nd chance StackOverflow exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" sov
0:012> sxe -c @".echo ---;.echo --- 1st chance CPlusPlusEH
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo; GN" -c2 @".echo ---;.echo --- 2nd chance
CPlusPlusEH
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_CPlusPlusEH_exception_in_G1FEHLERMERKMA LE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_CPlusPlusEH __full.dmp;!elog_str
ADPlus detected a 2nd chance CPlusPlusEH exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" eh
0:012> sxe -c @".echo ---;.echo --- 1st chance UnknownException
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo; GN" -c2 @".echo ---;.echo --- 2nd chance
UnknownException
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_UnknownException_exception_in_G1FEHLERM ERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_UnknownExce ption__full.dmp;!elog_str
ADPlus detected a 2nd chance UnknownException exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" *
0:012> sxi -c @" GN" -c2 @".echo ---;.echo --- 2nd chance NET_CLR
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_NET_CLR_exception_in_G1FEHLERMERKMALE.E XE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_NET_CLR__fu ll.dmp;!elog_str
ADPlus detected a 2nd chance NET_CLR exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" clr
0:012> sxi -c @".echo ---;.echo --- 1st chance CONTRL_C_OR_Debug_Break
exception ----;.echo ---------------------------------------------------------------;.echo
CTRL-C was pressed to stop debugging this process!;.echo When PageHeap is in
use this exception can be an internal
exception;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;!elog_str ADPlus detected a 1st chance
CONTRL_C_OR_Debug_Break exception in process G1FEHLERMERKMALE.EXE and has
taken the following actions at the time of the crash: Log Time EventLog
Stacks LoadedModules MatchingSymbols MiniDump Custom_!locks !runaway. The
output directory is C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929;.echo;.echo All thread
stacks below ---;~*kvn250;.echo;.echo;.echo Listing loaded
modules ---;lmv;.echo;.echo Modules with matching symbols ---;lml;.dump -u
/mdi /c
1st_chance_CONTRL_C_OR_Debug_Break_exception_in_G1 FEHLERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_CONTRL_C_OR _Debug_Break__mini.dmp;.echo;.echo
Executing command !locks;!locks;.echo;.echo Executing command
!runaway;!runaway; Q" -c2 @" GN" bpe
0:012> sxi -c @".echo ---;.echo --- 1st chance Wake_Debugger
exception ----;.echo ---------------------------------------------------------------;.echo
This was added for cases whereby the CTRL-C / debug break exception does not
work and the debugger reverts to a non-invasive attach;.echo CTRL-C was
pressed to stop debugging this process!;.echo When PageHeap is in use this
exception can be an internal exception;.echo Exiting the
debugger!!!;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;!elog_str ADPlus detected a 1st chance
Wake_Debugger exception in process G1FEHLERMERKMALE.EXE and has taken the
following actions at the time of the crash: Log Time EventLog Stacks
LoadedModules MatchingSymbols MiniDump Custom_!locks !runaway. The output
directory is C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929;.echo;.echo All thread
stacks below ---;~*kvn250;.echo;.echo;.echo Listing loaded
modules ---;lmv;.echo;.echo Modules with matching symbols ---;lml;.dump -u
/mdi /c
1st_chance_Wake_Debugger_exception_in_G1FEHLERMERK MALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Wake_Debugg er__mini.dmp;.echo;.echo
Executing command !locks;!locks;.echo;.echo Executing command
!runaway;!runaway; Q" -c2 @" GN" wkd
0:012> sxe -c @".echo ---;.echo --- 1st chance DLL_Load
exception ----;.echo ---------------------------------------------------------------;
GN" -c2 @".echo ---;.echo --- 2nd chance DLL_Load
exception ----;.echo ---------------------------------------------------------------;
GN" ld
Second-chance command for specific event ignored
0:012> sxn -c @".echo ---;.echo --- 1st chance DLL_UnLoad
exception ----;.echo ---------------------------------------------------------------;
GN" -c2 @".echo ---;.echo --- 2nd chance DLL_UnLoad
exception ----;.echo ---------------------------------------------------------------;
GN" ud
Second-chance command for specific event ignored
0:012> sxi -c @".echo ---;.echo --- 1st chance Process_Shut_Down
exception ----;.echo ---------------------------------------------------------------;.echo
This process is shutting down!;.echo This can happen for the following
reasons;.echo 1) Someone killed the process with Task Manager or the kill
command;.echo 2.) If this process is an MTS or COM+ server package, it could
be;.echo * exiting because an MTS/COM+ server package idle limit was
reached.;.echo 3.) If this process is an MTS or COM+ server package,;.echo *
someone may have shutdown the package via the MTS Explorer or;.echo *
Component Services MMC snap-in.;.echo 4.) If this process is an MTS or COM+
server package,;.echo * MTS or COM+ could be shutting down the process
because an internal;.echo * error was detected in the process (MTS/COM+
fail fast
condition).;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;!elog_str ADPlus detected a 1st chance
Process_Shut_Down exception in process G1FEHLERMERKMALE.EXE and has taken
the following actions at the time of the crash: Log Time EventLog Stacks
FullDump Custom_!runaway. The output directory is C:\Programme\Debugging
Tools for Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929;.echo;.echo
All thread stacks below ---;~*kvn250;.echo;.dump -u /ma /c
1st_chance_Process_Shut_Down_exception_in_G1FEHLER MERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Process_Shu t_Down__full.dmp;.echo;.echo
Executing command !runaway;!runaway; GN" -c2 @" GN" epr
Second-chance command for specific event ignored
0:012> sxe -c @".echo ---;.echo --- 1st chance Application_hang
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Application_hang_exception_in_G1FEHLERM ERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Application _hang__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Application_hang
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Application_hang_exception_in_G1FEHLERM ERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Application _hang__full.dmp;!elog_str
ADPlus detected a 2nd chance Application_hang exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" aph
0:012> sxe -c @".echo ---;.echo --- 1st chance Ctl_C_Console_app
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Ctl_C_Console_app_exception_in_G1FEHLER MERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Ctl_C_Conso le_app__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Ctl_C_Console_app
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Ctl_C_Console_app_exception_in_G1FEHLER MERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Ctl_C_Conso le_app__full.dmp;!elog_str
ADPlus detected a 2nd chance Ctl_C_Console_app exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" cce
0:012> sxe -c @".echo ---;.echo --- 1st chance Data_misaligned
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Data_misaligned_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Data_misali gned__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Data_misaligned
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Data_misaligned_exception_in_G1FEHLERME RKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Data_misali gned__full.dmp;!elog_str
ADPlus detected a 2nd chance Data_misaligned exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" dm
0:012> sxe -c @".echo ---;.echo --- 1st chance Guard_page_violation
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Guard_page_violation_exception_in_G1FEH LERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Guard_page_ violation__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Guard_page_violation
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Guard_page_violation_exception_in_G1FEH LERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Guard_page_ violation__full.dmp;!elog_str
ADPlus detected a 2nd chance Guard_page_violation exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" gp
0:012> sxe -c @".echo ---;.echo --- 1st chance In_page_IO_error
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_In_page_IO_error_exception_in_G1FEHLERM ERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_In_page_IO_ error__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance In_page_IO_error
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_In_page_IO_error_exception_in_G1FEHLERM ERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_In_page_IO_ error__full.dmp;!elog_str
ADPlus detected a 2nd chance In_page_IO_error exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" ip
0:012> sxe -c @".echo ---;.echo --- 1st chance Invalid_system_call
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Invalid_system_call_exception_in_G1FEHL ERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Invalid_sys tem_call__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Invalid_system_call
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Invalid_system_call_exception_in_G1FEHL ERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Invalid_sys tem_call__full.dmp;!elog_str
ADPlus detected a 2nd chance Invalid_system_call exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" isc
0:012> sxe -c @".echo ---;.echo --- 1st chance Stack_buffer_overflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /mdi /c
1st_chance_Stack_buffer_overflow_exception_in_G1FE HLERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Stack_buffe r_overflow__mini.dmp;
GN" -c2 @".echo ---;.echo --- 2nd chance Stack_buffer_overflow
exception ----;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at: ;.time;.echo;.echo Faulting stack
below ---;~#kvn250;.echo;.dump -u /ma /c
2nd_chance_Stack_buffer_overflow_exception_in_G1FE HLERMERKMALE.EXE_running_on_GEDRATSBS
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__2nd_chance_Stack_buffe r_overflow__full.dmp;!elog_str
ADPlus detected a 2nd chance Stack_buffer_overflow exception in process
G1FEHLERMERKMALE.EXE and has taken the following actions at the time of the
crash: Log Time Stack FullDump EventLog. The output directory is
C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929; GN" sbo
0:012> *
0:012> * ADPlus is monitoring: G1FEHLERMERKMALE.EXE
0:012> * for 1st chance and 2nd chance exceptions as configured above.
0:012> * To change ADPlus configuration please refer to ADPlus.Doc. This
file can be found
0:012> * in the same folder as ADPlus.vbs
0:012> *
0:012> g
Mon Jan 31 22:32:31.130 2005 (GMT+1): ModLoad: 5e3c0000 5e3c8000
C:\WINDOWS\system32\perfnet.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:31.360 2005 (GMT+1): (15c0.cc): Unknown exception - code
000006ba (first chance)
---
--- 1st chance UnknownException exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:31.360 2005 (GMT+1)
System Uptime: 19 days 10:44:09.946
Process Uptime: 0 days 0:00:04.576
Kernel time: 0 days 0:00:00.250
User time: 0 days 0:00:00.120

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012e708 77c5120c 000006ba 00000001 00000000 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012e71c 77c511bc 000006ba 0012eb20 77cb5495
RPCRT4!RpcpRaiseException+0x1d (FPO: [1,0,0])
02 0012e728 77cb5495 0012e774 0000000c 001d4b10 RPCRT4!NdrGetBuffer+0x44
(FPO: [3,0,0])
03 0012eb08 5f6e1e58 5f6e1ae0 5f6e10ea 0012eb20 RPCRT4!NdrClientCall2+0x195
(FPO: [Non-Fpo])
04 0012eb18 5f6e21b0 00000000 00000000 0012eb84
NNTPAPI!NntprQueryStatistics+0x14 (FPO: [3,0,0])
05 0012eb58 6ba82100 00000000 00000000 0012eb84
NNTPAPI!NntpQueryStatistics+0x22 (FPO: [Non-Fpo])
06 0012eda0 77dd04a5 010ad52c 0012eee8 0012ef14
nntpctrs!CollectNntpPerformanceData+0x8b (FPO: [EBP 0x0012ef38] [4,140,0])
07 0012ef38 77da7db4 0012efa4 00000000 00000000
ADVAPI32!QueryExtensibleData+0x617 (FPO: [Non-Fpo])
08 0012f314 77d87123 80000004 0012f418 00000000
ADVAPI32!PerfRegQueryValue+0x4da (FPO: [Non-Fpo])
09 0012f3ec 77d73034 80000004 0012f418 0012f43c
ADVAPI32!LocalBaseRegQueryValue+0x238 (FPO: [EBP 0x0012f424] [6,42,0])
*** WARNING: Unable to verify checksum for
c:\windows\assembly\nativeimages1_v1.1.4322\system \1.0.5000.0__b77a5c561934e089_098d531a\system.dll
*** ERROR: Module load completed but symbols could not be loaded for
c:\windows\assembly\nativeimages1_v1.1.4322\system \1.0.5000.0__b77a5c561934e089_098d531a\system.dll
0a 0012f460 7b308758 7b2a847c 0012f4c8 010ad540
ADVAPI32!RegQueryValueExW+0xa0 (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
0b 0012f9b0 0012fa94 0012fa44 00000001 0015ade0 system_7b1d0000+0x138758
0c 791b32a8 791d6ae2 7923975f 7929609c 791d6f97 0x12fa94

Mon Jan 31 22:32:32.872 2005 (GMT+1): ModLoad: 5e3a0000 5e3a9000
C:\WINDOWS\system32\perfos.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:32.882 2005 (GMT+1): ModLoad: 5e390000 5e39d000
C:\WINDOWS\system32\perfproc.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.123 2005 (GMT+1): (15c0.cc): Unknown exception - code
000006ba (first chance)
---
--- 1st chance UnknownException exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:33.123 2005 (GMT+1)
System Uptime: 19 days 10:44:11.709
Process Uptime: 0 days 0:00:06.339
Kernel time: 0 days 0:00:00.290
User time: 0 days 0:00:00.120

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012e708 77c5120c 000006ba 00000001 00000000 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012e71c 77c511bc 000006ba 0012eb20 77cb5495
RPCRT4!RpcpRaiseException+0x1d (FPO: [1,0,0])
02 0012e728 77cb5495 0012e774 0000000c 001f3900 RPCRT4!NdrGetBuffer+0x44
(FPO: [3,0,0])
03 0012eb08 5f6e1e58 5f6e1ae0 5f6e10ea 0012eb20 RPCRT4!NdrClientCall2+0x195
(FPO: [Non-Fpo])
04 0012eb18 5f6e21b0 00000000 00000000 0012eb84
NNTPAPI!NntprQueryStatistics+0x14 (FPO: [3,0,0])
05 0012eb58 6ba82100 00000000 00000000 0012eb84
NNTPAPI!NntpQueryStatistics+0x22 (FPO: [Non-Fpo])
06 0012eda0 77dd04a5 010ad52c 0012eee8 0012ef14
nntpctrs!CollectNntpPerformanceData+0x8b (FPO: [EBP 0x0012ef38] [4,140,0])
07 0012ef38 77da7db4 0012efa4 00000000 00000000
ADVAPI32!QueryExtensibleData+0x617 (FPO: [Non-Fpo])
08 0012f314 77d87123 80000004 0012f418 00000000
ADVAPI32!PerfRegQueryValue+0x4da (FPO: [Non-Fpo])
09 0012f3ec 77d73034 80000004 0012f418 0012f43c
ADVAPI32!LocalBaseRegQueryValue+0x238 (FPO: [EBP 0x0012f424] [6,42,0])
0a 0012f460 7b308758 7b2a847c 0012f4c8 010ad540
ADVAPI32!RegQueryValueExW+0xa0 (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
0b 0012f9b0 0012fa94 0012fa44 00000001 0015ade0 system_7b1d0000+0x138758
0c 791b32a8 791d6ae2 7923975f 7929609c 791d6f97 0x12fa94

Mon Jan 31 22:32:33.143 2005 (GMT+1): ModLoad: 5db20000 5db26000
C:\WINDOWS\System32\rasctrs.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.153 2005 (GMT+1): ModLoad: 76d30000 76d41000
C:\WINDOWS\system32\rasman.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.243 2005 (GMT+1): ModLoad: 08ac0000 08adc000
C:\Programme\Microsoft CRM\Server\bin\CRMSecPerfmon.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.253 2005 (GMT+1): ModLoad: 6b230000 6b237000
C:\WINDOWS\system32\smtpctrs.DLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.263 2005 (GMT+1): ModLoad: 5c1d0000 5c1d6000
C:\WINDOWS\system32\SMTPAPI.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.283 2005 (GMT+1): ModLoad: 72e90000 72eb6000
C:\WINDOWS\system32\winspool.drv
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.283 2005 (GMT+1): (15c0.cc): Unknown exception - code
000006ba (first chance)
---
--- 1st chance UnknownException exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:33.283 2005 (GMT+1)
System Uptime: 19 days 10:44:11.869
Process Uptime: 0 days 0:00:06.499
Kernel time: 0 days 0:00:00.290
User time: 0 days 0:00:00.120

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012e884 77c5120c 000006ba 00000001 00000000 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012e898 77c511bc 000006ba 0012ec9c 77cb5495
RPCRT4!RpcpRaiseException+0x1d (FPO: [1,0,0])
02 0012e8a4 77cb5495 0012e8f0 00000824 001f3900 RPCRT4!NdrGetBuffer+0x44
(FPO: [3,0,0])
03 0012ec84 72e9417b 72e970f8 72e97ce2 0012ec9c RPCRT4!NdrClientCall2+0x195
(FPO: [Non-Fpo])
04 0012ec94 72e9412e 0000080a 00000000 00000000
winspool!RpcEnumPrinters+0x14 (FPO: [7,0,0])
05 0012ecec 72e9477f 0000080a 00000000 00000000 winspool!EnumPrintersW+0xb7
(FPO: [Non-Fpo])
06 0012ed7c 72e946e8 0012ed9c 0012eda8 0012edb0
winspool!Pf_dwClientCollect+0x5a (FPO: [Non-Fpo])
07 0012eda0 77dd04a5 000370d0 0012eee8 0012ef14 winspool!PerfCollect+0xc6
(FPO: [Non-Fpo])
08 0012ef38 77da7db4 0012efa4 00000000 00000000
ADVAPI32!QueryExtensibleData+0x617 (FPO: [Non-Fpo])
09 0012f314 77d87123 80000004 0012f418 00000000
ADVAPI32!PerfRegQueryValue+0x4da (FPO: [Non-Fpo])
0a 0012f3ec 77d73034 80000004 0012f418 0012f43c
ADVAPI32!LocalBaseRegQueryValue+0x238 (FPO: [EBP 0x0012f424] [6,42,0])
0b 0012f460 7b308758 7b2a847c 0012f4c8 010ad540
ADVAPI32!RegQueryValueExW+0xa0 (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
0c 0012f9b0 0012fa94 0012fa44 00000001 0015ade0 system_7b1d0000+0x138758
0d 791b32a8 791d6ae2 7923975f 7929609c 791d6f97 0x12fa94

Mon Jan 31 22:32:33.383 2005 (GMT+1): ModLoad: 5b1f0000 5b1f5000
C:\WINDOWS\system32\tapiperf.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.393 2005 (GMT+1): ModLoad: 76bc0000 76bd7000
C:\WINDOWS\system32\MPRAPI.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.403 2005 (GMT+1): ModLoad: 76ce0000 76d13000
C:\WINDOWS\system32\ACTIVEDS.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.403 2005 (GMT+1): ModLoad: 76cb0000 76cd6000
C:\WINDOWS\system32\adsldpc.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.403 2005 (GMT+1): ModLoad: 76a70000 76a9e000
C:\WINDOWS\system32\credui.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.403 2005 (GMT+1): ModLoad: 76d20000 76d2b000
C:\WINDOWS\system32\rtutils.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.403 2005 (GMT+1): ModLoad: 76490000 76591000
C:\WINDOWS\system32\SETUPAPI.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.433 2005 (GMT+1): ModLoad: 5e380000 5e386000
C:\WINDOWS\system32\perfts.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.433 2005 (GMT+1): ModLoad: 76150000 76160000
C:\WINDOWS\system32\WINSTA.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.433 2005 (GMT+1): ModLoad: 5a780000 5a78a000
C:\WINDOWS\system32\UTILDLL.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.433 2005 (GMT+1): ModLoad: 76d50000 76d7e000
C:\WINDOWS\system32\TAPI32.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.453 2005 (GMT+1): ModLoad: 76990000 769bd000
C:\WINDOWS\system32\WINMM.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.473 2005 (GMT+1): ModLoad: 5a3c0000 5a3c9000
C:\WINDOWS\system32\inetsrv\w3ctrs.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.473 2005 (GMT+1): ModLoad: 648b0000 648e1000
C:\WINDOWS\system32\inetsrv\IISUTIL.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.784 2005 (GMT+1): ModLoad: 59140000 59145000
C:\WINDOWS\system32\winsctrs.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.784 2005 (GMT+1): ModLoad: 590b0000 590b7000
C:\WINDOWS\system32\winsrpc.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.794 2005 (GMT+1): ModLoad: 76e40000 76e53000
C:\WINDOWS\system32\secur32.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.794 2005 (GMT+1): ModLoad: 76b80000 76ba4000
C:\WINDOWS\system32\msv1_0.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.814 2005 (GMT+1): ModLoad: 58d20000 58d39000
C:\WINDOWS\system32\wbem\wmiaprpl.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:33.814 2005 (GMT+1): ModLoad: 74fd0000 75008000
C:\WINDOWS\system32\wbem\wbemcomn.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:34.374 2005 (GMT+1): ModLoad: 0ffd0000 0fffd000
C:\WINDOWS\system32\rsaenh.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.075 2005 (GMT+1): ModLoad: 57140000 5715e000
c:\windows\assembly\gac\adodb\7.0.3300.0__b03f5f7f 11d50a3a\adodb.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.126 2005 (GMT+1): ModLoad: 7a6e0000 7a820000
c:\windows\assembly\gac\system.data\1.0.5000.0__b7 7a5c561934e089\system.data.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.206 2005 (GMT+1): ModLoad: 76e80000 76efe000
C:\WINDOWS\system32\CLBCatQ.DLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.256 2005 (GMT+1): ModLoad: 08f30000 08fba000
C:\Programme\Gemeinsame Dateien\System\ado\msado15.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.256 2005 (GMT+1): ModLoad: 74930000 74959000
C:\WINDOWS\system32\MSDART.DLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:35.256 2005 (GMT+1): ModLoad: 761a0000 761e8000
C:\WINDOWS\system32\comdlg32.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.077 2005 (GMT+1): ModLoad: 71930000 71974000
C:\WINDOWS\System32\mswsock.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.097 2005 (GMT+1): ModLoad: 76dc0000 76de8000
C:\WINDOWS\system32\DNSAPI.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.117 2005 (GMT+1): ModLoad: 76e60000 76e67000
C:\WINDOWS\System32\winrnr.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.117 2005 (GMT+1): ModLoad: 76e70000 76e75000
C:\WINDOWS\system32\rasadhlp.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.137 2005 (GMT+1): ModLoad: 718f0000 718f8000
C:\WINDOWS\System32\wshtcpip.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.387 2005 (GMT+1): ModLoad: 79000000 7903e000
c:\windows\assembly\gac\system.enterpriseservices\ 1.0.5000.0__b03f5f7f11d50a3a\system.enterpriseserv ices.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.457 2005 (GMT+1): ModLoad: 79620000 79636000
c:\windows\assembly\gac\system.enterpriseservices\ 1.0.5000.0__b03f5f7f11d50a3a\system.enterpriseserv ices.thunk.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.488 2005 (GMT+1): ModLoad: 6e270000 6e2a1000
C:\WINDOWS\system32\Com\comadmin.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.498 2005 (GMT+1): ModLoad: 61f90000 61f99000
C:\WINDOWS\system32\MfcSubs.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.528 2005 (GMT+1): ModLoad: 6d770000 6d783000
C:\WINDOWS\system32\dbnetlib.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.548 2005 (GMT+1): ModLoad: 71d80000 71d84000
C:\WINDOWS\system32\security.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.568 2005 (GMT+1): ModLoad: 09900000 09907000
C:\WINDOWS\system32\DBnmpNTw.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:36.678 2005 (GMT+1): ModLoad: 765e0000 765f6000
C:\WINDOWS\system32\ntdsapi.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:37.239 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:37.249 2005 (GMT+1)
System Uptime: 19 days 10:44:15.835
Process Uptime: 0 days 0:00:10.465
Kernel time: 0 days 0:00:00.550
User time: 0 days 0:00:00.480

Faulting stack below ---
*** WARNING: Unable to verify checksum for
c:\windows\assembly\nativeimages1_v1.1.4322\system .windows.forms\1.0.5000.0__b77a5c561934e089_f6fb9f 55\system.windows.forms.dll
*** ERROR: Module load completed but symbols could not be loaded for
c:\windows\assembly\nativeimages1_v1.1.4322\system .windows.forms\1.0.5000.0__b77a5c561934e089_f6fb9f 55\system.windows.forms.dll
# ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0012f030 7b81c2ad 0105bd64 013807b4 0105bd64 0x991b5ae
01 00000000 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-37-269_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:39.922 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:39.922 2005 (GMT+1)
System Uptime: 19 days 10:44:18.509
Process Uptime: 0 days 0:00:13.138
Kernel time: 0 days 0:00:00.570
User time: 0 days 0:00:00.480

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012ef84 792c267b c0000005 00000000 00000002 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012efc4 792c26be 791b47d8 0012f9b0 00000000
mscorwks!LinkFrameAndThrow+0x49 (FPO: [Non-Fpo])
02 0012f030 7b81c2ad 0105bd64 013807b4 0105bd64
mscorwks!CPFH_HandleManagedFault (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 00000000 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-40-073_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:40.283 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:40.283 2005 (GMT+1)
System Uptime: 19 days 10:44:18.869
Process Uptime: 0 days 0:00:13.499
Kernel time: 0 days 0:00:00.580
User time: 0 days 0:00:00.490

Faulting stack below ---
# ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0012f01c 7b81c2ad 0105bd64 013807b4 0105bd64 0x991b5ae
01 00000000 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-40-283_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:40.493 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:40.493 2005 (GMT+1)
System Uptime: 19 days 10:44:19.079
Process Uptime: 0 days 0:00:13.709
Kernel time: 0 days 0:00:00.580
User time: 0 days 0:00:00.490

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012ef70 792c267b c0000005 00000000 00000002 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012efb0 792c26be 791b47d8 0012f9b0 00000000
mscorwks!LinkFrameAndThrow+0x49 (FPO: [Non-Fpo])
02 0012f01c 7b81c2ad 0105bd64 013807b4 0105bd64
mscorwks!CPFH_HandleManagedFault (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 00000000 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-40-493_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:46.512 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:46.512 2005 (GMT+1)
System Uptime: 19 days 10:44:25.098
Process Uptime: 0 days 0:00:19.728
Kernel time: 0 days 0:00:00.680
User time: 0 days 0:00:00.590

Faulting stack below ---
# ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0012e4e0 7b81c2ad 0105bd64 013807b4 0105bd64 0x991b5ae
01 0000009e 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-46-512_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:47.123 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:47.123 2005 (GMT+1)
System Uptime: 19 days 10:44:25.709
Process Uptime: 0 days 0:00:20.339
Kernel time: 0 days 0:00:00.680
User time: 0 days 0:00:00.590

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012e434 792c267b c0000005 00000000 00000002 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012e474 792c26be 791b47d8 0012e5a8 81d09000
mscorwks!LinkFrameAndThrow+0x49 (FPO: [Non-Fpo])
02 0012e4e0 7b81c2ad 0105bd64 013807b4 0105bd64
mscorwks!CPFH_HandleManagedFault (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0000009e 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-47-123_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:47.343 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:47.343 2005 (GMT+1)
System Uptime: 19 days 10:44:25.929
Process Uptime: 0 days 0:00:20.559
Kernel time: 0 days 0:00:00.690
User time: 0 days 0:00:00.590

Faulting stack below ---
# ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
00 0012ecb8 7b81c2ad 0105bd64 013807b4 0105bd64 0x991b5ae
01 0000009e 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-47-343_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:47.543 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:32:47.553 2005 (GMT+1)
System Uptime: 19 days 10:44:26.140
Process Uptime: 0 days 0:00:20.769
Kernel time: 0 days 0:00:00.701
User time: 0 days 0:00:00.590

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012ec0c 792c267b c0000005 00000000 00000002 KERNEL32!RaiseException+0x51
(FPO: [Non-Fpo])
01 0012ec4c 792c26be 791b47d8 0012ed80 00000083
mscorwks!LinkFrameAndThrow+0x49 (FPO: [Non-Fpo])
02 0012ecb8 7b81c2ad 0105bd64 013807b4 0105bd64
mscorwks!CPFH_HandleManagedFault (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
03 0000009e 00000000 00000000 00000000 00000000
system_windows_forms_7b810000+0xc2ad

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-32-47-553_15C0.dmp
- mini user dump
Dump successfully written
Mon Jan 31 22:32:48.395 2005 (GMT+1): ModLoad: 739c0000 739c6000
C:\WINDOWS\system32\dciman32.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.046 2005 (GMT+1): ModLoad: 09cf0000 09d6d000
C:\Programme\Gemeinsame Dateien\System\Ole DB\oledb32.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.056 2005 (GMT+1): ModLoad: 1f900000 1f913000
C:\Programme\Gemeinsame Dateien\System\Ole DB\OLEDB32R.DLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.096 2005 (GMT+1): ModLoad: 1f430000 1f437000
C:\Programme\Gemeinsame Dateien\System\ado\msader15.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.296 2005 (GMT+1): ModLoad: 09d70000 09df6000
C:\Programme\Gemeinsame Dateien\System\Ole DB\sqloledb.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.316 2005 (GMT+1): ModLoad: 61310000 61328000
C:\Programme\Gemeinsame Dateien\System\Ole DB\MSDATL3.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.346 2005 (GMT+1): ModLoad: 1b5d0000 1b665000
C:\WINDOWS\system32\MSWSTR10.DLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:49.516 2005 (GMT+1): ModLoad: 754b0000 755dd000
C:\WINDOWS\system32\comsvcs.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:50.448 2005 (GMT+1): ModLoad: 753f0000 75400000
C:\Programme\Gemeinsame Dateien\System\Ole DB\SQLOLEDB.RLL
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:32:50.568 2005 (GMT+1): ModLoad: 0a730000 0a73e000
C:\Programme\Gemeinsame Dateien\System\ado\msadrh15.dll
---
--- 1st chance DLL_Load exception ----
---------------------------------------------------------------
Mon Jan 31 22:34:31.783 2005 (GMT+1): (15c0.cc): Access violation - code
c0000005 (first chance)
---
--- 1st chance AccessViolation exception ----
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:34:31.783 2005 (GMT+1)
System Uptime: 19 days 10:46:10.369
Process Uptime: 0 days 0:02:04.999
Kernel time: 0 days 0:00:04.696
User time: 0 days 0:00:03.084

Faulting stack below ---
# ChildEBP RetAddr Args to Child
00 0012ea88 792121f6 0116accc 00000235 8116ddf4
mscorwks!gc_heap::update_brick_table+0x86 (FPO: [Non-Fpo])
01 0012eb20 79212494 00000002 00000000 00000002
mscorwks!gc_heap::plan_phase+0x3cb (FPO: [Non-Fpo])
02 0012eb78 7921301a 00000000 00000000 00000002 mscorwks!gc_heap::gc1+0x9c
(FPO: [Non-Fpo])
03 0012ebb8 79213c37 00000002 00000000 ffffffff
mscorwks!gc_heap::garbage_collect+0x1bf (FPO: [Non-Fpo])
04 0012ebd8 79216c0c 00000002 00000000 0012f050
mscorwks!GCHeap::GarbageCollectGeneration+0x11b (FPO: [Non-Fpo])
05 0012ebf8 79216c3e ffffffff 00000000 0012ed58
mscorwks!GCHeap::GarbageCollect+0x4a (FPO: [Non-Fpo])
06 0012ec08 00f70e1e 0012ec14 ffffffff 00000000
mscorwks!GCInterface::CollectGeneration+0xf (FPO: [Non-Fpo])
WARNING: Frame IP not in any known module. Following frames may be wrong.
07 0012ed58 0991d5a3 014115f0 010f38b0 014114c4 0xf70e1e
08 0012edd0 0991d051 01116ecc 00935b08 0012edf8 0x991d5a3
09 0012ede0 0991d006 00000000 010f38b0 01410e50 0x991d051
0a 0012edf8 0991cef0 013807b4 0105bd64 010f38b0 0x991d006
0b 0012ee10 7b82b535 0105bd64 013807b4 00000001 0x991cef0
0c 0012ee48 7b828c3b 013807b4 0012ee94 7b9e6ff8
system_windows_forms_7b810000+0x1b535
0d 0012eeb8 0089597a 00000000 00000001 00000006
system_windows_forms_7b810000+0x18c3b
0e 0012ef04 7cd669a5 008a1ec6 185703f6 00000006 0x89597a
0f 0012ef7c 7cd680a0 00000000 008a1ec6 185703f6
USER32!UserCallWinProcCheckWow+0x151 (FPO: [Non-Fpo])
10 0012efd8 7cd680e3 00528c38 00000006 00000001
USER32!DispatchClientMessage+0xd9 (FPO: [Non-Fpo])
11 0012f000 77f33868 0012f010 00000018 00528c38 USER32!__fnDWORD+0x22 (FPO:
[Non-Fpo])
12 0012f024 7cd691aa 00fc0641 185703f6 00000003
ntdll!KiUserCallbackDispatcher+0x13 (FPO: [0,0,0])
13 0012f168 7b8285ff 0105bd64 015f4aac 010f38b0 USER32!NtUserShowWindow+0xc
(FPO: [Non-Fpo])
14 0012f198 7b828408 0140f654 00000004 7b826051
system_windows_forms_7b810000+0x185ff
15 0012f1d8 7b825e65 013807b4 7b825d22 00000000
system_windows_forms_7b810000+0x18408
16 0012f22c 7b8235f9 00000000 013807b4 0012f2dc
system_windows_forms_7b810000+0x15e65
17 0012f28c 7b822fa6 7b822f5f 7b825c6e 013807b4
system_windows_forms_7b810000+0x135f9
18 0012f300 0089597a 00000000 00000001 00000018
system_windows_forms_7b810000+0x12fa6
19 0012f34c 7cd669a5 008a1ec6 185703f6 00000018 0x89597a
1a 0012f3c4 7cd680a0 00000000 008a1ec6 185703f6
USER32!UserCallWinProcCheckWow+0x151 (FPO: [Non-Fpo])
1b 0012f420 7cd680e3 00528c38 00000018 00000001
USER32!DispatchClientMessage+0xd9 (FPO: [Non-Fpo])
1c 0012f448 77f33868 0012f458 00000018 00528c38 USER32!__fnDWORD+0x22 (FPO:
[Non-Fpo])
1d 0012f46c 7cd691aa 00fc0641 185703f6 00000005
ntdll!KiUserCallbackDispatcher+0x13 (FPO: [0,0,0])
1e 0012f53c 7b81f224 00000000 00000000 0012f5bc USER32!NtUserShowWindow+0xc
(FPO: [Non-Fpo])
1f 0012f57c 7b81f126 7b8fdaee 00000000 013807b4
system_windows_forms_7b810000+0xf224
20 0012f668 7b8fd650 00df099c 00000000 0012f6bc
system_windows_forms_7b810000+0xf126
21 0012f69c 791d94bc 0012f7b4 791ed194 0012f6f0
system_windows_forms_7b810000+0xed650
22 0012f6a4 791ed194 0012f6f0 00000000 0012f6c8
mscorwks!CallDescrWorker+0x30 (FPO: [Non-Fpo])
23 0012f7b4 791ed54b 0093507b 00161f98 0012f7e0
mscorwks!MethodDesc::CallDescr+0x1b8 (FPO: [Non-Fpo])
24 0012f870 791ed5b9 0093507b 00161f98 110514fa
mscorwks!MethodDesc::CallDescr+0x4f (FPO: [Non-Fpo])
25 0012f898 7924253d 0012f928 00000000 0015ade0
mscorwks!MethodDesc::Call+0x97 (FPO: [Non-Fpo])
26 0012f950 7921da72 00935080 00000001 00000000
mscorwks!ClassLoader::CanAccess+0x207 (FPO: [Non-Fpo])
27 0012fa64 7921d6e5 00161f98 00000000 79041394
mscorwks!ClassLoader::ExecuteMainMethod+0x49d (FPO: [Non-Fpo])
28 0012fa7c 7921d630 00000000 0012fd70 00000000
mscorwks!Assembly::ExecuteMainMethod+0x21 (FPO: [Non-Fpo])
29 0012fd60 791c71ef 00000000 00000001 0012ffe0
mscorwks!SystemDomain::ExecuteMainMethod+0x421 (FPO: [Non-Fpo])
2a 0012ffa0 791c70ae 8013141b 00000000 00000000 mscorwks!ExecuteEXE+0x1ce
(FPO: [Non-Fpo])
2b 0012ffb0 7917d4d1 00000000 791b0000 0012fff0 mscorwks!_CorExeMain+0x59
(FPO: [0,0,2])
2c 0012ffc0 77e2f38c 00000000 00000000 7ffdf000 mscoree!_CorExeMain+0x30
(FPO: [Non-Fpo])
2d 0012fff0 00000000 7917d4a5 00000000 78746341
KERNEL32!BaseProcessStart+0x23 (FPO: [Non-Fpo])

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_AccessViola tion__mini_10D8_2005-01-31_22-34-32-625_15C0.dmp
- mini user dump
Dump successfully written
---
--- 1st chance Process_Shut_Down exception ----
---------------------------------------------------------------
This process is shutting down!
This can happen for the following reasons
1) Someone killed the process with Task Manager or the kill command
2.) If this process is an MTS or COM+ server package, it could be
* exiting because an MTS/COM+ server package idle limit was reached.
3.) If this process is an MTS or COM+ server package,
* someone may have shutdown the package via the MTS Explorer or
* Component Services MMC snap-in.
4.) If this process is an MTS or COM+ server package,
* MTS or COM+ could be shutting down the process because an internal
* error was detected in the process (MTS/COM+ fail fast condition).
---------------------------------------------------------------

Occurrence happened at:
Debug session time: Mon Jan 31 22:34:33.446 2005 (GMT+1)
System Uptime: 19 days 10:46:12.032
Process Uptime: 0 days 0:02:06.662
Kernel time: 0 days 0:00:04.726
User time: 0 days 0:00:03.084

All thread stacks below ---

.. 0 Id: 15c0.cc Suspend: 0 Teb: 7ffde000 Unfrozen
# ChildEBP RetAddr Args to Child
00 0012ea18 77f33617 77e2f257 ffffffff e0004743
SharedUserData!SystemCallStub+0x4 (FPO: [0,0,0])
01 0012ea1c 77e2f257 ffffffff e0004743 00000000 ntdll!NtTerminateProcess+0xc
(FPO: [2,0,0])
02 0012eb0c 77e2f1f6 e0004743 77e8f3b0 ffffffff KERNEL32!_ExitProcess+0x57
(FPO: [Non-Fpo])
03 0012eb20 7925c04a e0004743 00000000 00000002 KERNEL32!TerminateProcess
(FPO: [Non-Fpo])
04 0012eb78 7921301a 00000000 00000000 00000002 mscorwks!gc_heap::gc1+0x214
(FPO: [Non-Fpo])
05 0012ebb8 79213c37 00000002 00000000 ffffffff
mscorwks!gc_heap::garbage_collect+0x1bf (FPO: [Non-Fpo])
06 0012ebd8 79216c0c 00000002 00000000 0012f050
mscorwks!GCHeap::GarbageCollectGeneration+0x11b (FPO: [Non-Fpo])
07 0012ebf8 79216c3e ffffffff 00000000 0012ed58
mscorwks!GCHeap::GarbageCollect+0x4a (FPO: [Non-Fpo])
08 0012ec08 00f70e1e 0012ec14 ffffffff 00000000
mscorwks!GCInterface::CollectGeneration+0xf (FPO: [Non-Fpo])
WARNING: Frame IP not in any known module. Following frames may be wrong.
09 0012ed58 0991d5a3 014115f0 010f38b0 014114c4 0xf70e1e
0a 0012edd0 0991d051 01116ecc 00935b08 0012edf8 0x991d5a3
0b 0012ede0 0991d006 00000000 010f38b0 01410e50 0x991d051
0c 0012edf8 0991cef0 013807b4 0105bd64 010f38b0 0x991d006
0d 0012ee10 7b82b535 0105bd64 013807b4 00000001 0x991cef0
0e 0012ee48 7b828c3b 013807b4 0012ee94 7b9e6ff8
system_windows_forms_7b810000+0x1b535
0f 0012eeb8 0089597a 00000000 00000001 00000006
system_windows_forms_7b810000+0x18c3b
10 0012ef04 7cd669a5 008a1ec6 185703f6 00000006 0x89597a
11 0012ef7c 7cd680a0 00000000 008a1ec6 185703f6
USER32!UserCallWinProcCheckWow+0x151 (FPO: [Non-Fpo])
12 0012efd8 7cd680e3 00528c38 00000006 00000001
USER32!DispatchClientMessage+0xd9 (FPO: [Non-Fpo])
13 0012f000 77f33868 0012f010 00000018 00528c38 USER32!__fnDWORD+0x22 (FPO:
[Non-Fpo])
14 0012f024 7cd691aa 00fc0641 185703f6 00000003
ntdll!KiUserCallbackDispatcher+0x13 (FPO: [0,0,0])
15 0012f168 7b8285ff 0105bd64 015f4aac 010f38b0 USER32!NtUserShowWindow+0xc
(FPO: [Non-Fpo])
16 0012f198 7b828408 0140f654 00000004 7b826051
system_windows_forms_7b810000+0x185ff
17 0012f1d8 7b825e65 013807b4 7b825d22 00000000
system_windows_forms_7b810000+0x18408
18 0012f22c 7b8235f9 00000000 013807b4 0012f2dc
system_windows_forms_7b810000+0x15e65
19 0012f28c 7b822fa6 7b822f5f 7b825c6e 013807b4
system_windows_forms_7b810000+0x135f9
1a 0012f300 0089597a 00000000 00000001 00000018
system_windows_forms_7b810000+0x12fa6
1b 0012f34c 7cd669a5 008a1ec6 185703f6 00000018 0x89597a
1c 0012f3c4 7cd680a0 00000000 008a1ec6 185703f6
USER32!UserCallWinProcCheckWow+0x151 (FPO: [Non-Fpo])
1d 0012f420 7cd680e3 00528c38 00000018 00000001
USER32!DispatchClientMessage+0xd9 (FPO: [Non-Fpo])
1e 0012f448 77f33868 0012f458 00000018 00528c38 USER32!__fnDWORD+0x22 (FPO:
[Non-Fpo])
1f 0012f46c 7cd691aa 00fc0641 185703f6 00000005
ntdll!KiUserCallbackDispatcher+0x13 (FPO: [0,0,0])
20 0012f53c 7b81f224 00000000 00000000 0012f5bc USER32!NtUserShowWindow+0xc
(FPO: [Non-Fpo])
21 0012f57c 7b81f126 7b8fdaee 00000000 013807b4
system_windows_forms_7b810000+0xf224
22 0012f668 7b8fd650 00df099c 00000000 0012f6bc
system_windows_forms_7b810000+0xf126
23 0012f69c 791d94bc 0012f7b4 791ed194 0012f6f0
system_windows_forms_7b810000+0xed650
24 0012f6a4 791ed194 0012f6f0 00000000 0012f6c8
mscorwks!CallDescrWorker+0x30 (FPO: [Non-Fpo])
25 0012f7b4 791ed54b 0093507b 00161f98 0012f7e0
mscorwks!MethodDesc::CallDescr+0x1b8 (FPO: [Non-Fpo])
26 0012f870 791ed5b9 0093507b 00161f98 110514fa
mscorwks!MethodDesc::CallDescr+0x4f (FPO: [Non-Fpo])
27 0012f898 7924253d 0012f928 00000000 0015ade0
mscorwks!MethodDesc::Call+0x97 (FPO: [Non-Fpo])
28 0012f950 7921da72 00935080 00000001 00000000
mscorwks!ClassLoader::CanAccess+0x207 (FPO: [Non-Fpo])
29 0012fa64 7921d6e5 00161f98 00000000 79041394
mscorwks!ClassLoader::ExecuteMainMethod+0x49d (FPO: [Non-Fpo])
2a 0012fa7c 7921d630 00000000 0012fd70 00000000
mscorwks!Assembly::ExecuteMainMethod+0x21 (FPO: [Non-Fpo])
2b 0012fd60 791c71ef 00000000 00000001 0012ffe0
mscorwks!SystemDomain::ExecuteMainMethod+0x421 (FPO: [Non-Fpo])
2c 0012ffa0 791c70ae 8013141b 00000000 00000000 mscorwks!ExecuteEXE+0x1ce
(FPO: [Non-Fpo])
2d 0012ffb0 7917d4d1 00000000 791b0000 0012fff0 mscorwks!_CorExeMain+0x59
(FPO: [0,0,2])
2e 0012ffc0 77e2f38c 00000000 00000000 7ffdf000 mscoree!_CorExeMain+0x30
(FPO: [Non-Fpo])
2f 0012fff0 00000000 7917d4a5 00000000 78746341
KERNEL32!BaseProcessStart+0x23 (FPO: [Non-Fpo])

Creating C:\Programme\Debugging Tools for
Windows\Crash_Mode__Date_01-31-2005__Time_22-32-2929\PID-5568__G1FEHLERMERKMALE.EXE__1st_chance_Process_Shu t_Down__full_10D8_2005-01-31_22-34-33-516_15C0.dmp
- mini user dump
Dump successfully written

Executing command !runaway
User Mode Time
Thread Time
cc 0 days 0:00:02.493







^ No runnable debuggees error in
'.echo ---;.echo --- 1st chance Process_Shut_Down
exception ----;.echo ---------------------------------------------------------------;.echo
This process is shutting down!;.echo This can happen for the following
reasons;.echo 1) Someone killed the process with Task Manager or the kill
command;.echo 2.) If this process is an MTS or COM+ server package, it could
be;.echo * exiting because an MTS/COM+ server package idle limit was
reached.;.echo 3.) If this process is an MTS or COM+ server package,;.echo *
someone may have shutdown the package via the MTS Explorer or;.echo *
Component Services MMC snap-in.;.echo 4.) If this process is an MTS or COM+
server package,;.echo * MTS or COM+ could be shutting down the process
because an internal;.echo * error was detected in the process (MTS/COM+
fail fast
condition).;.echo ---------------------------------------------------------------;.echo;.echo
Occurrence happened at:'

Nov 21 '05 #5

P: n/a
Ralf

The problem is in the serial comms code. This came up recently (around
23/12/04); have a look at this thread:

http://www.dotnetmonster.com/Uwe/For...-error-message

[I do wish Corrado would post a bug alert on his web-site as this is an
insidious problem that takes everyone who comes across it a long time to
sort out. So if you are listening Corrado ...]

HTH

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hi Charles,

Yes, i use serial comm ports via Api from www.codeworks.it/net/index.htm
Rev.21 (24/10/2004).
But i thing i had the same problem with the ActiveX from Microsoft
MSCOMM32.OCX.

I use one or more comm ports in the applications.
Data comes from Comm-Ports and are stored in SQL2k-Database via adodb.
A visualisation with datagrids will shown on screen.
This is that what the program do.

The error with 'application-termination unexpectedly without message' is
very sensible.
In other applications (with comm-ports too) will work longer without
termination.
Same applications have no problem, I think, the more complex the projects
am, the rather arise the problems.

Bye
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:Oe******************@TK2MSFTNGP14.phx.gbl...
Ralf

What is your program doing? Does it use any serial comms? Can you tell us
a bit more about the APIs it is using?

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hello!

I have some Vb.Net applications, which are terminated at indefinite
times without message.

If I call in the program regulated system.GC.Collect, then the program
is terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat



Nov 21 '05 #6

P: n/a
Hi Charles,

this wrote me Corrado:

Try setting enableevents=true and do nothing inside event procedure, if
problem does not occur it could depend on what you do inside event,
otherwise I have no idea, no one reported me such problem.

I think, i should get a solution. (It's a small snipped code)

Charles can you me send the fixed code-parts of the class rs232?

thanks.
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:eD**************@TK2MSFTNGP12.phx.gbl...
Ralf

The problem is in the serial comms code. This came up recently (around
23/12/04); have a look at this thread:

http://www.dotnetmonster.com/Uwe/For...-error-message

[I do wish Corrado would post a bug alert on his web-site as this is an
insidious problem that takes everyone who comes across it a long time to
sort out. So if you are listening Corrado ...]

HTH

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hi Charles,

Yes, i use serial comm ports via Api from www.codeworks.it/net/index.htm
Rev.21 (24/10/2004).
But i thing i had the same problem with the ActiveX from Microsoft
MSCOMM32.OCX.

I use one or more comm ports in the applications.
Data comes from Comm-Ports and are stored in SQL2k-Database via adodb.
A visualisation with datagrids will shown on screen.
This is that what the program do.

The error with 'application-termination unexpectedly without message' is
very sensible.
In other applications (with comm-ports too) will work longer without
termination.
Same applications have no problem, I think, the more complex the projects
am, the rather arise the problems.

Bye
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:Oe******************@TK2MSFTNGP14.phx.gbl...
Ralf

What is your program doing? Does it use any serial comms? Can you tell
us a bit more about the APIs it is using?

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hello!

I have some Vb.Net applications, which are terminated at indefinite
times without message.

If I call in the program regulated system.GC.Collect, then the program
is terminated here sporadically without message.

It's not possible to debug in visual studio, i get no exceptions
(application is terminated unexpectedly without message).

In the programs, I use UserControls, Timers and WinAPi-Calls.

This behavior will come on all NT systems (Win 2000/XP/2003).

Now, I have make a debug with windbg.

Here the result:

(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): CLR exception - code e0434f4d (first chance)
(a70.cc8): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
edi=00a2ec1c
eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr na
po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
mscorwks!gc_heap::plan_phase+0x6c1:
792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
How can I get a fix of this problem?

Is the problem inside mscorwks.dll?

Who can help?

The system: Framework 1.1 with SP 1

Many Thanks
Ralf Gedrat



Nov 21 '05 #7

P: n/a
Ralf

Corrado has a short memory. I e-mailed him last year and he replied that it
was a known problem in the receive events handler, and that he was testing a
fix.

If you look at the link I posted in my previous reply, you will find the
code you need. The thread also refers to an article in MSDN that shows how
to marshal the overlapped structure correctly in this scenario.

Doing what Corrado suggests will not help; this is a marshalling problem
between the calls to WaitCommEvent() and WaitForSingleObject().

What happens is that the call to WaitCommEvent passes an OVERLAPPED
structure and an event mask that it caches. Subsequent calls use that cached
data. If .NET moves the structure or mask (and occasionally it does) then
the memory being referenced by the API functions is no longer valid, and the
whole thing crashes without so much as a by your leave.

Have a look at the code and if you are still not sure post back.

HTH

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hi Charles,

this wrote me Corrado:

Try setting enableevents=true and do nothing inside event procedure, if
problem does not occur it could depend on what you do inside event,
otherwise I have no idea, no one reported me such problem.

I think, i should get a solution. (It's a small snipped code)

Charles can you me send the fixed code-parts of the class rs232?

thanks.
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:eD**************@TK2MSFTNGP12.phx.gbl...
Ralf

The problem is in the serial comms code. This came up recently (around
23/12/04); have a look at this thread:

http://www.dotnetmonster.com/Uwe/For...-error-message

[I do wish Corrado would post a bug alert on his web-site as this is an
insidious problem that takes everyone who comes across it a long time to
sort out. So if you are listening Corrado ...]

HTH

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
Hi Charles,

Yes, i use serial comm ports via Api from www.codeworks.it/net/index.htm
Rev.21 (24/10/2004).
But i thing i had the same problem with the ActiveX from Microsoft
MSCOMM32.OCX.

I use one or more comm ports in the applications.
Data comes from Comm-Ports and are stored in SQL2k-Database via adodb.
A visualisation with datagrids will shown on screen.
This is that what the program do.

The error with 'application-termination unexpectedly without message' is
very sensible.
In other applications (with comm-ports too) will work longer without
termination.
Same applications have no problem, I think, the more complex the
projects am, the rather arise the problems.

Bye
Ralf Gedrat
"Charles Law" <bl***@nowhere.com> schrieb im Newsbeitrag
news:Oe******************@TK2MSFTNGP14.phx.gbl...
Ralf

What is your program doing? Does it use any serial comms? Can you tell
us a bit more about the APIs it is using?

Charles
"Ralf Gedrat" <ra**@gedrat.de> wrote in message
news:36*************@individual.net...
> Hello!
>
> I have some Vb.Net applications, which are terminated at indefinite
> times without message.
>
> If I call in the program regulated system.GC.Collect, then the program
> is terminated here sporadically without message.
>
> It's not possible to debug in visual studio, i get no exceptions
> (application is terminated unexpectedly without message).
>
> In the programs, I use UserControls, Timers and WinAPi-Calls.
>
> This behavior will come on all NT systems (Win 2000/XP/2003).
>
> Now, I have make a debug with windbg.
>
> Here the result:
>
> (a70.cc8): CLR exception - code e0434f4d (first chance)
> (a70.cc8): CLR exception - code e0434f4d (first chance)
> (a70.cc8): CLR exception - code e0434f4d (first chance)
> (a70.cc8): CLR exception - code e0434f4d (first chance)
> (a70.cc8): CLR exception - code e0434f4d (first chance)
> (a70.cc8): Access violation - code c0000005 (first chance)
> First chance exceptions are reported before any exception handling.
> This exception may be expected and handled.
> eax=01208e14 ebx=01050000 ecx=0001208e edx=c0000120 esi=0000036d
> edi=00a2ec1c
> eip=792143e1 esp=0012eaa0 ebp=0012eb20 iopl=0 nv up ei pl zr
> na po nc
> cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
> mscorwks!gc_heap::plan_phase+0x6c1:
> 792143e1 668b0a mov cx,[edx] ds:0023:c0000120=????
>
>
> How can I get a fix of this problem?
>
> Is the problem inside mscorwks.dll?
>
> Who can help?
>
> The system: Framework 1.1 with SP 1
>
> Many Thanks
> Ralf Gedrat
>
>



Nov 21 '05 #8

This discussion thread is closed

Replies have been disabled for this discussion.