Serial Monitor ActiveX crashing(Read 9403 times)
Serial Monitor ActiveX crashing on: June 20, 2013, 01:36:34 AM
There is a serious problem with activeX control.. I first noticed it on machine that have multiple serial devices and I am monitoring all of them.. later I found out it doesn't matter if I am monitoring one or multiple devices..
Because I tested it with examples from Program Files that gets installed when you install Serialport Monitor ActiveX control package...So, it means my implementation of AX control was good since Eltima's example also crash...

It seems to happen when there is a lot of data coming in fast.. After few minutes of monitoring..
So, either it gives me BSOD with error code:
Error code 1000008e, parameter1 c0000005, parameter2 8057d1fa, parameter3 eeb03c24, parameter4 00000000.

.. or on other systems program just exists/crashes... In one occasion, system just froze at once as soon as I started sending packets.. No BSOD, no control over mouse or system.. Picture just froze..

I managed to reproduce this by downloading COM port stress tool from here:
http://www.aggsoft.com/com-port-stress-test.htm
and setting speed to max, while specifying packet size from 2000-10000 bytes...
SPSniffer will crash every time after max 10 minutes..

And problem is that this also happens on production systems, which don't have emulated port com packets sending, but just regular device input/output...
So, this makes SerialMonitor AX useless for me now :/ Can you please check why this happens? You will reproduce it with the software I posted link to.. It's just a question if you will get BSOD or software will shut down...It's always related to ACCESS DENIED error message...

FOr ex. My VC++ debug output:
First-chance exception in app.exe: 0xC0000005: Access Violation.
First-chance exception in app.exe: 0xC0000005: Access Violation.
First-chance exception in app.exe: 0xC0000005: Access Violation.
First-chance exception in app.exe (SPSNIFFER.DLL): 0xC0000005: Access Violation.

or minidump info:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!NtWriteFile+308
8057d1fa ff530c          call    dword ptr [ebx+0Ch]

TRAP_FRAME:  eeb23c24 -- (.trap 0xffffffffeeb23c24)
ErrCode = 00000000
eax=850d8108 ebx=00000000 ecx=eeb23cd4 edx=850d814c esi=00000000 edi=00000001
eip=8057d1fa esp=eeb23c98 ebp=eeb23d38 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!NtWriteFile+0x308:
8057d1fa ff530c          call    dword ptr [ebx+0Ch]  ds:0023:0000000c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  4

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from 8054161c to 8057d1fa

STACK_TEXT: 
eeb23d38 8054161c 00000040 00000000 00000000 nt!NtWriteFile+0x308
eeb23d38 7c90e4f4 00000040 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fba8 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!NtWriteFile+308
8057d1fa ff530c          call    dword ptr [ebx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!NtWriteFile+308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

FAILURE_BUCKET_ID:  0x8E_nt!NtWriteFile+308

BUCKET_ID:  0x8E_nt!NtWriteFile+308

Followup: MachineOwner
---------



Re: Serial Monitor ActiveX crashing Reply #1 on: June 20, 2013, 12:11:45 PM
Hello,

We have tried reproducing the problem as per your description, and indeed the examples terminated after a short time (which is no wonder provided that they were not optimized for such loads). However, no system freezes or BSODs so far.

Which particular example did you replicate the BSOD with, and on what OS? What kind of serial port did you test with?

Thanks.



Re: Serial Monitor ActiveX crashing Reply #2 on: June 20, 2013, 06:32:02 PM
I tested it on XP SP3.. Multiple systems..
Access violation is made by spsniffer.dll no matter which demo app I choose..
If baud rate is fixed at 115k and some other parameters change randomly, crash is almost instant..
Hardware serial ports I tested it with was with SYBA  Combo 2 DB-9 Serial (RS-232, COM) + 1 DB-25 Parallel Printer Ports (LPT1) PCI-e Controller Card, IOC Chipset ... That was the configuration that gave BSOD.. Everything else resulted in crash or silent shut down of application..

Problem is, no matter if it's constant emulated load or not, there will be instances when legit devices will send such large loads and spsniffer.dll won't be able to handle it(or whatever the case is).. That's why on production systems, crash doesn't appear so frequently.. But it's just a matter of time...
And all points to only one error:
0xC0000005: Access Violation.
« Last Edit: June 20, 2013, 10:17:09 PM by salo »



Re: Serial Monitor ActiveX crashing Reply #3 on: June 21, 2013, 09:35:45 AM
In our tests we can't seem to reach the stage where the system blue-screens: the examples quickly run out of memory and simply crash.

Could you please email us to support@eltima.com the following:

1. Your application that you've managed to reproduce the BSODs with.

2. A small memory dump (minidump).

Minidumps are generated on every BSOD occurrence. By default Windows XP stores them in C:\Windows\Minidump\ directory.

Thanks.



Re: Serial Monitor ActiveX crashing Reply #4 on: June 21, 2013, 04:08:03 PM
I found the cause of BSODs... If you run example on a machine via remote desktop, and then disconnect, BSOD appears instantly.. Although OS as well as default desktop and other applications are still running after I disconnect..



Re: Serial Monitor ActiveX crashing Reply #5 on: June 23, 2013, 07:14:14 AM
Update..
If I run my AX control on any user account, including default desktop - as soon as someone tries to connect remotely via remote desktop, computer crashes :|
User don't even have to authenticate,because OS crashes when someone ATTEMPTS to make remote desktop session.. So, you don't even get a user&pass dialog :/

I don't know what's the connection, but I tried it on few different machines, all running same hardware setup..
The last minidump is in atachment



Re: Serial Monitor ActiveX crashing Reply #6 on: June 25, 2013, 06:35:15 AM
This is log from Demo app.. Which shows windows processes keep opening/closing/interacting with serial port...

And minidump shows that svchost.exe which is legit process, crashes machine when user logs on..



Re: Serial Monitor ActiveX crashing Reply #7 on: July 02, 2013, 01:14:58 PM
Let me post the results of our email discussion here:

The information in the crash dumps proved to be insufficient to debug the issue. Besides, further testing gave evidence of the issue being specific to an Elo Touch device that it was initially reproduced with.

Further debugging will not be possible without having this particular device at hand, and unfortunately we can't offer any solution at the moment.



 

Sitemap 1 2 3 4 5