Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

crash under windows 2000 in niserial.sys (v1.45)

with a PCI-232 card, I get this crash under w2000 in a visual C++ app.
let me know what other info you may need.
dump:


*** Fatal System Error: 0x0000007f
(0x00000008,0x00000000,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

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

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 0, 0, 0}

Loading symbols for bec81000 niserial.sys -> niserial.sys
*** ERROR: Module load completed but symbols could not be loaded for niserial.sys
WARNING: Process directory table base 04AD9000 doesn't match CR3 00030000
WARNING: Process directory table base 04AD9000 doesn't match CR3 00030000
Probably caused by : niserial.sys ( niserial+16cb )

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

nt!RtlpBreakWithStatusInstruction:
80455994 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* 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 parens 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: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 28)
eax=00000003 ebx=00000000 ecx=8171a730 edx=0000c802 esi=8171a0f8 edi=800679bc
eip=bec826cb esp=ed17d000 ebp=ed17d008 iopl=3 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00013246
niserial+16cb:
bec826cb 56 push esi
Resetting default context

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from bec81ca7 to bec826cb

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ed17d008 bec81ca7 8171a0f8 00000000 81762150 niserial+0x16cb
00000000 f000e816 f000e2c3 f000e816 f000e816 niserial+0xca7
f000e816 00000000 00000000 00000000 00000000 0xf000e816


FOLLOWUP_IP:
niserial+16cb
bec826cb 56 push esi

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: niserial+16cb

MODULE_NAME: niserial

IMAGE_NAME: niserial.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 39b576ee

STACK_COMMAND: .tss 28 ; kb

BUCKET_ID: 0x7f_8_niserial+16cb

Followup: MachineOwner
---------
0 Kudos
Message 1 of 2
(2,961 Views)
Try to update your drivers to 1.5 version.
Try to use the MSComm ActiveX control, it work fine.
And give us the part of your code to have a better idea of your problem.
Thanks
0 Kudos
Message 2 of 2
(2,961 Views)