FabulaTech Forum
        (http://www.virtual-serial-port.com/forum)
      

        Serial Port Solution >> Serial Port Redirector >> Bugcheck in ftvspr.sys
        
(Message started by: Atea on Mar 27th, 2007, 11:23pm)
Title: Bugcheck in ftvspr.sys
Post by Atea on Mar 27th, 2007, 11:23pm
Hi - just troubleshooting a Windows 2000 bluescreen which has led me to the Serial Port Redirector Driver. Can you tell me if my version;
- is old?
- can be upgraded?
- has known issues?

All tips are gratefully accepted!

Driver details:
Serial Port Redirector Driver ftvspr.sys 1.4.0.0

Bugcheck details (from Windbg):
STOP D1, {f6413000, 2, 0, f6413000}
DRIVER_IRQL_NOT_LESS_OR_EQUAL
FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_ftvspr+2000
Title: Re: Bugcheck in ftvspr.sys
Post by Atea on Apr 2nd, 2007, 6:03am
Thanks, I have upgraded to 1.4.13.0. So far so good.

Was there ever a "history.txt" or other changelog between 1.4.0 and 1.4.13? Has the bugcheck issue been encountered before?
Title: Re: Bugcheck in ftvspr.sys
Post by Andrew on Apr 3rd, 2007, 7:04am
Serial Port Redirector versions history is below. Missed versions numbers were inside program releases and never were published.

v1.4.13: GUI minor fixes.
v1.4.11: Compatibility issues are fixed.
v1.4.9: Overlapped ports minor fixes.
v1.4.8: Now program allows to create overlapped virtual serial ports (with the same names as existing physical COM ports).
v1.4.6: New features: Optional Bit-Rate emulation and Fixed COM port settings.
v1.4.2: Developer API is extended.
v1.4: Connecting issue is fixed.
Title: Re: Bugcheck in ftvspr.sys
Post by mbaker5408 on Jul 11th, 2007, 11:50am
I have tried this with both the public release and the beta release and get this everytime. I use anything but Hyperterm to access the com port...

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
       use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
       use .trap on that value
Else
       .trap on the appropriate frame will show where the trap was taken
       (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------

Page ec6b0 not present in the dump file. Type ".hh dbgerr004" for details
Page ec710 not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR:  0x7f_0

TRAP_FRAME:  b9be4ba8 -- (.trap 0xffffffffb9be4ba8)
ErrCode = 00000000
eax=0098967f ebx=00000007 ecx=00000000 edx=00000000 esi=00000002 edi=00000000
eip=ba148f46 esp=b9be4c1c ebp=b9be4c24 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
ftvspr+0x3f46:
ba148f46 f7f1            div     eax,ecx
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  daemon.exe

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from 80914ca5 to 80826da2

STACK_TEXT:  
b9be4b44 80914ca5 0000007f ba148f46 00000002 nt!KeBugCheck+0x14
b9be4b9c 80884567 b9be4ba8 b9be4c24 ba148f46 nt!Ki386CheckDivideByZeroTrap+0x41
b9be4b9c ba148f46 b9be4ba8 b9be4c24 ba148f46 nt!KiTrap00+0x87
WARNING: Stack unwind information not available. Following frames may be wrong.
b9be4c24 ba148c1c 8a1a90f0 8a7b8008 8a2f6030 ftvspr+0x3f46
b9be4c64 8081d5a3 8a1a9038 8a7b8008 8a7b8018 ftvspr+0x3c1c
b9be4c78 808f188a 00000000 00000000 00000000 nt!IofCallDriver+0x45
b9be4cb0 8092b6fa 004bf9d0 80a51c86 8a4bf9b8 nt!IopDeleteFile+0x13a
b9be4ccc 80867a43 8a4bf9d0 00000000 0000009c nt!ObpRemoveObjectRoutine+0xdc
b9be4cec 8092c295 e123f1b8 8a40ad88 8a3f7db0 nt!ObfDereferenceObject+0x67
b9be4d04 8092c326 e123f1b8 8a4bf9d0 0000009c nt!ObpCloseHandleTableEntry+0x139
b9be4d48 8092c443 0000009c 00000001 b9be4d64 nt!ObpCloseHandle+0x82
b9be4d58 80883908 0000009c 007afe60 7c8285ec nt!NtClose+0x1b
b9be4d58 7c8285ec 0000009c 007afe60 7c8285ec nt!KiFastCallEntry+0xf8
007afe60 00000000 00000000 00000000 00000000 0x7c8285ec


STACK_COMMAND:  kb

FOLLOWUP_IP:
ftvspr+3f46
ba148f46 f7f1            div     eax,ecx

SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ftvspr

IMAGE_NAME:  ftvspr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45f52c33

SYMBOL_NAME:  ftvspr+3f46

FAILURE_BUCKET_ID:  0x7f_0_ftvspr+3f46

BUCKET_ID:  0x7f_0_ftvspr+3f46

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

kd> lmvm ftvspr
start    end        module name
ba145000 ba14df00   ftvspr     (no symbols)          
   Loaded symbol image file: ftvspr.sys
   Image path: \SystemRoot\system32\drivers\ftvspr.sys
   Image name: ftvspr.sys
   Timestamp:        Mon Mar 12 05:32:19 2007 (45F52C33)
   CheckSum:         00018A38
   ImageSize:        00008F00
   Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0
Title: Re: Bugcheck in ftvspr.sys
Post by mbaker5408 on Jul 11th, 2007, 11:51am
Ooops thats on a windows 2003 R2 SP2 VMWare Guest...
Title: Re: Bugcheck in ftvspr.sys
Post by Andrew on Jul 27th, 2007, 9:04am
Just sent you new driver.
Thanks.