Dec 30th, 2024, 5:42pm
Home Home  Search Search  Members Members  Login Login  Register Register
Welcome, Guest. Please Login or Register.
FabulaTech Forum Serial Port Solutions Virtual Serial Port Kit (Moderators: Tim_GaliullinFT, Sergey_Jarovski, Andrew) * Blue screen caused by vportbus.sys * Previous topic | Next topic
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print
   Author  Topic: * Blue screen caused by vportbus.sys *  (Read 8240 times)
plarusa
FabulaTech Forum Newbie
*

View Profile         
Posts: 2
* Blue screen caused by vportbus.sys *
on: Dec 1st, 2005, 12:16pm 		Quote Quote  Modify Modify
I received this error while using the serial port kit (evaluation 4.7.3) with vmware 5.5. Here is the debugger report,
 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00010004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 80814616, address which referenced memory
 
Debugging Details:
------------------
 
 
WRITE_ADDRESS:  00010004  
 
CURRENT_IRQL:  2
 
FAULTING_IP:  
nt!KeClearEvent+8
80814616 83600400         and     dword ptr [eax+0x4],0x0
 
DEFAULT_BUCKET_ID:  DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
LAST_CONTROL_TRANSFER:  from f7c29d13 to 80814616
 
TRAP_FRAME:  b9bf9aec -- (.trap ffffffffb9bf9aec)
ErrCode = 00000002
eax=00010000 ebx=81de10f0 ecx=00000370 edx=00000042 esi=00000000 edi=82e13ef8
eip=80814616 esp=b9bf9b60 ebp=b9bf9b60 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!KeClearEvent+0x8:
80814616 83600400       and dword ptr [eax+0x4],0x0 ds:0023:00010004=HuhHuh??
Resetting default scope
 
STACK_TEXT:  
b9bf9b60 f7c29d13 00010000 81df5110 00000000 nt!KeClearEvent+0x8
WARNING: Stack unwind information not available. Following frames may be wrong.
b9bf9b78 f7c269f4 01de10f0 f7f034a8 c0000010 vportbus+0x3d13
b9bf9b94 f7c2a0cf 82e13f24 f7f034a8 00000214 vportbus+0x9f4
b9bf9c38 8081d39d 00000214 81d55008 820fe768 vportbus+0x40cf
b9bf9c4c 808ec789 81d5509c 820fe768 81d55008 nt!IofCallDriver+0x45
b9bf9c60 808ed507 82e13e40 81d55008 820fe768 nt!IopSynchronousServiceTail+0x10b
b9bf9d00 808e60be 0000017c 00000000 00000000 nt!IopXxxControlFile+0x5db
b9bf9d34 80882fa8 0000017c 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b9bf9d34 7c82ed54 0000017c 00000000 00000000 nt!KiFastCallEntry+0xf8
00effe80 00402b18 0000017c c0ff2f4e 00000000 0x7c82ed54
77e41689 e877e6ae 0002a0ad 810c7d8b 2d4808ff 0x402b18
77e4168d 0002a0ad 810c7d8b 2d4808ff 81777400 0xe877e6ae
77e41691 810c7d8b 2d4808ff 81777400 074808ff 0x2a0ad
77e41695 2d4808ff 81777400 074808ff 816f7400 0x810c7d8b
77e41699 81777400 074808ff 816f7400 090020ff 0x2d4808ff
77e4169d 074808ff 816f7400 090020ff 33677400 0x81777400
81777400 30014269 000093c8 e107d9a8 00000001 0x74808ff
81c70d60 00000000 00001000 00001000 e1050000 0x30014269
 
 
FOLLOWUP_IP:  
vportbus+3d13
f7c29d13 808b1306000060   or      byte ptr [ebx+0x613],0x60
 
SYMBOL_STACK_INDEX:  1
 
FOLLOWUP_NAME:  MachineOwner
 
SYMBOL_NAME:  vportbus+3d13
 
MODULE_NAME:  vportbus
 
IMAGE_NAME:  vportbus.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  42948e09
 
STACK_COMMAND:  .trap ffffffffb9bf9aec ; kb
 
FAILURE_BUCKET_ID:  0xA_W_vportbus+3d13
 
BUCKET_ID:  0xA_W_vportbus+3d13
 
Followup: MachineOwner
 
 
 
 
Note: This is a recurring problem, I have seen it twice.
System: Windows 2K3 Server (SP1).
 
 
- Pierre
Last Edit: Dec 1st, 2005, 12:46pm by plarusa IP Logged
Andrew
FabulaTech Forum Moderator
Moderator
FabulaTech Forum Senior Member
*****

View Profile   WWW         
Gender: male Posts: 427
Re: * Blue screen caused by vportbus.sys *
Reply #1 on: Dec 2nd, 2005, 3:18am 		Quote Quote  Modify Modify
We are trying to examine this problem now but could you please specify when does this blue screen appear (i.e. during system startup or our program start, moment of serial port opening... or other)?
 
Thank you very much for feedback.
IP Logged
Andrew Scott

FabulaTech
===================
http://www.fabulatech.com
plarusa
FabulaTech Forum Newbie
*

View Profile         
Posts: 2
Re: * Blue screen caused by vportbus.sys *
Reply #2 on: Dec 2nd, 2005, 1:50pm 		Quote Quote  Modify Modify
I received this error while exchanging serial data between two freebsd vmware VMs.
 
This is probably not a typical use case.
 
- Pierre.
Last Edit: Jan 15th, 2007, 4:31am by Andrew IP Logged
Andrew
FabulaTech Forum Moderator
Moderator
FabulaTech Forum Senior Member
*****

View Profile   WWW         
Gender: male Posts: 427
Re: * Blue screen caused by vportbus.sys *
Reply #3 on: Jan 15th, 2007, 4:31am 		Quote Quote  Modify Modify
Could you please try the latest version from our web site.
Thank you.
IP Logged
Andrew Scott

FabulaTech
===================
http://www.fabulatech.com
gitto
FabulaTech Forum Newbie
*

View Profile   WWW   Email      momo  
Gender: female Posts: 1
Re: * Blue screen caused by vportbus.sys *
Reply #4 on: Oct 5th, 2008, 9:34am 		Quote Quote  Modify Modify
Thank you  Cheesy
IP Logged
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print

Previous topic | Next topic
Online Talk to our
support team or
sales department.