Bluescreen Server2003 (USB to Ethernet Connector 12141 times)

I have got a bluescreen problem with 3 Windows2003R2 Servers.
One server is sharing 2 Marx USB-Dongles to the other servers. (Terminalservers)
This configuration worked for some months.

Now each server makes sometimes bluescreen, but never on the same time. (since 2 weeks)
The faulting driver on the terminalservers is vuhub.sys
(the faulting driver of the sharing server is C:\Programme\Eltima Software\USB to Ethernet Connector\drv\NT5\fusbhub.sys)

Had someone the same problem?
Do I have to delete all drivers, uninstall eltima software, and make a new installation?


DumpFile analyze of one terminalserver:

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Dokumente und Einstellungen\fs\Desktop\Mini102109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\Symbole*
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer
Built by: 3790.srv03_sp2_gdr.090805-1438
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Wed Oct 21 08:17:04.700 2009 (GMT+2)
System Uptime: 0 days 9:39:27.385
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*** WARNING: Unable to verify timestamp for vuhub.sys
*** ERROR: Module load completed but symbols could not be loaded for vuhub.sys
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, f712eabf, f52e7b44, 0}

Probably caused by : vuhub.sys ( vuhub+7abf )

Followup: MachineOwner

3: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: f712eabf, The address that the exception occurred at
Arg3: f52e7b44, Trap Frame
Arg4: 00000000

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang  "%s" konnte nicht auf dem Speicher durchgef hrt werden.

f712eabf ??              ???

TRAP_FRAME:  f52e7b44 -- (.trap 0xfffffffff52e7b44)
ErrCode = 00000002
eax=00000000 ebx=897f6008 ecx=89754368 edx=0000000f esi=8a3a47b8 edi=897f6008
eip=f712eabf esp=f52e7bb8 ebp=f52e7bc8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
f712eabf ??              ???
Resetting default scope





LAST_CONTROL_TRANSFER:  from 89f49700 to f712eabf

WARNING: Stack unwind information not available. Following frames may be wrong.
f52e7bb4 89f49700 89f492a0 889ecc08 00000000 vuhub+0x7abf
f52e7bc8 f712ece8 89cbbf10 89754368 89f492a0 0x89f49700
f52e7bf0 f71292b2 897f6008 8a3a3008 00000000 vuhub+0x7ce8
f52e7c0c f7128026 897f6008 0000000c 8a3a3008 vuhub+0x22b2
f52e7c28 f7127927 8a3a3f10 897f6008 8a3a3008 vuhub+0x1026
f52e7c3c 80840153 8a3a3f10 897f6008 89c269b0 vuhub+0x927
f52e7c50 8092b51f 897f609c 8a1e44f0 897f6008 nt!IofCallDriver+0x45
f52e7c64 8092b454 8a3a3f10 897f6008 8a1e44f0 nt!IopSynchronousServiceTail+0x10b
f52e7d00 8092b574 00000398 000003b0 00000000 nt!IopXxxControlFile+0x60f
f52e7d34 80833bef 00000398 000003b0 00000000 nt!NtDeviceIoControlFile+0x2a
f52e7d34 7c94860c 00000398 000003b0 00000000 nt!KiFastCallEntry+0xfc
0224fe40 00000000 00000000 00000000 00000000 0x7c94860c


f712eabf ??              ???


SYMBOL_NAME:  vuhub+7abf

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  vuhub.sys


FAILURE_BUCKET_ID:  0x8E_vuhub+7abf

BUCKET_ID:  0x8E_vuhub+7abf

Followup: MachineOwner
« Last Edit: October 21, 2009, 10:37:04 AM by fschenk »

Re: Bluescreen Server2003 (USB to Ethernet Connector Reply #1 on: October 21, 2009, 02:52:36 PM

We are currently investigating the problem, you encountered using our product.

We would like to offer you to test the latest beta build of the product. Please, let us know your decision.

Re: Bluescreen Server2003 (USB to Ethernet Connector Reply #2 on: October 22, 2009, 09:02:35 AM

Yesterday I deactivated one of the two dongles.
Until now we had no more bluescreens.

Is it possible that the bluescreens occur, because the dongles are exactly the same?
(same adress, signals etc..)

How works the communication with the USB to Ethernet Connector between the servers?
using only port number of the device? Should i take the dongles on separate RootHubs?


Re: Bluescreen Server2003 (USB to Ethernet Connector Reply #3 on: October 26, 2009, 08:42:22 AM

Thanks for your feedback.

We will investigate the problem you described.

Please, be informed that it is not necessary to plug the devices into different hubs. USB to Ethernet Connector shares USB port. Therefore the name of device does not matter.


Sitemap 1 2 3 4 5