[vbox-dev] VBoxNetFlt.sys BSOD on installation time

Tue Jan 19 17:44:30 GMT 2010

yes, it's crashed at installation time. seems the host only driver caused it.

There is another bsod case at installation, which is caused by VBoxNetFlt.sys power handling failure (stop code 0x9f, see my previous email)

--- On Tue, 1/19/10, Mikhail Sennikovsky <Mikhail.Sennikovsky at Sun.COM> wrote:

From: Mikhail Sennikovsky <Mikhail.Sennikovsky at Sun.COM>
Subject: Re: [vbox-dev] VBoxNetFlt.sys BSOD on installation time
To: "Huihong Luo" <huisinro at yahoo.com>
Cc: vbox-dev at virtualbox.org, "Alexey Eremenko" <al4321 at gmail.com>
Date: Tuesday, January 19, 2010, 9:29 AM

When did this crash happen? Is it during the install as well?
The Net[Flt/Adp] drivers are not even in the call stack.

On 1/19/2010 7:52 PM, Huihong Luo wrote: 

decndis.sys caused the crash on one user

decndis is part of the DEC (Digital Equipment Corp) LAT protocol that we use to access the VAX

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000001f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 93401bb0, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from 82975718
Unable to read MiSystemVaType memory at 82955160
000001f0 

CURRENT_IRQL:  2

FAULTING_IP: 
decndis+1bb0
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8078aab0 -- (.trap 0xffffffff8078aab0)
ErrCode = 00000000
eax=00000007 ebx=8589f0e0 ecx=00000000 edx=00000001 esi=00000000 edi=93406978
eip=93401bb0 esp=8078ab24 ebp=8078ab28 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
decndis+0x1bb0:
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1   ds:0023:000001f0=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 93401bb0 to 828537eb

STACK_TEXT:  
8078aab0 93401bb0 badb0d00 00000001 80788000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ab28 934039c3 00000000 00000007 8078ab54 decndis+0x1bb0
8078ab40 934023db 8078ab54 86907ebc 86908008 decndis+0x39c3
8078ab78 93402af0 93406700 86945eac 00000000 decndis+0x23db
8078ab8c 8ae7720d 93406700 86907ebc 00000000 decndis+0x2af0
8078abac 8ae7709c 00908008 86907ebc 00000000 ndis!ndisSendCompleteWithPause+0xaf
8078abd0 8ae758a6 86908008 00000000 00000001 ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x7c
8078ac1c 8ae115e2 00000000 873ae3d8 00000001 ndis!ndisMSendCompleteNetBufferListsInternal+0x217
8078ac30 8ef30848 85fcabd0 873ae3d8 00000001 ndis!NdisFSendNetBufferListsComplete+0x3a
8078ac54 8ae115e2 85fca858 873ae3d8 00000001 pacer!PcFilterSendNetBufferListsComplete+0xb4
8078ac68 8ef4bb35 85fc9008 873ae3d8 00000001 ndis!NdisFSendNetBufferListsComplete+0x3a
8078ac8c 8ae75f0a 85fca008 873ae3d8 00000001 vpcnfltr+0x1b35
8078acb0 8f1d71d9 8589f0e0 873ae3d8 00000001 ndis!NdisMSendNetBufferListsComplete+0xa4
8078ad08 8f1d7e07 873ae3d8 00000000 85f9e000 k57nd60x+0x2b1d9
8078ae60 8f1d606d 85f9e000 00000000 00000000 k57nd60x+0x2be07
8078ae84 8f1ae9d5 85f9e000 00000000 00000000 k57nd60x+0x2a06d
8078aeb0 8f1aef9d 00000001 8589f0e0 85f88578 k57nd60x+0x29d5
8078aec8 8f1af147 00000000 00000000 8078af10 k57nd60x+0x2f9d
8078aee0 8ae63301 85f9e000 00000000 00000000 k57nd60x+0x3147
8078af20 8ae0e9f4 85f8864c 00f88578 00000000 ndis!ndisMiniportDpc+0xda
8078af48 828753b5 85f8864c 85f88578 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 82875218 82936d20 85cc7020 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 828749dc 8e9152cc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 8e9152cc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
828749dc 00000000 0000001a 00d6850f bb830000 0x8e9152cc

STACK_COMMAND:  kb

FOLLOWUP_IP: 
decndis+1bb0
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  decndis+1bb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: decndis

IMAGE_NAME:  decndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3d8305c8

FAILURE_BUCKET_ID:  0xD1_decndis+1bb0

BUCKET_ID:  OLD_IMAGE_decndis.sys

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

--- On Mon, 1/18/10, Huihong Luo <huisinro at yahoo.com> wrote:

From: Huihong Luo <huisinro at yahoo.com>
Subject: Re: [vbox-dev] VBoxNetFlt.sys BSOD on installation time
To: vbox-dev at virtualbox.org, "Alexey Eremenko" <al4321 at gmail.com>
Date: Monday, January 18, 2010, 10:43 AM

Thanks, I will check with the users.

--- On Mon, 1/18/10, Alexey Eremenko <al4321 at gmail.com> wrote:

> From: Alexey Eremenko <al4321 at gmail.com>
> Subject: Re: [vbox-dev] VBoxNetFlt.sys BSOD on installation time
> To: vbox-dev at virtualbox.org
> Date: Monday, January 18, 2010, 10:38 AM
> On Mon, Jan 18, 2010 at 8:35 PM,
> Alexey Eremenko <al4321 at gmail.com>
> wrote:
> > On Mon, Jan 18, 2010 at 8:19 PM, Huihong Luo <huisinro at yahoo.com>
> wrote:
> >> This did happen, although very rarely, 2 users
> from our 30k users got the BSOD. From the below minidump
> info, it's to do with power state of the net filter driver.
> They tested VirtualBox 3.1.2, and got same BSOD.
> >>
> >> I checked the logs, seems this bug was fixed
> somewhat, but it still exists.
> >>
> >
> > The only bug that is somewhat related I can think of,
> is the
> > professional (server) network cards, that support
> bonding and VLANs
> > that are may have compatibility problems with
> vboxnetflt.
> > (there was a ticket but I can't find it)
> 
> Found it !
> http://www.virtualbox.org/ticket/5519
> 
> > It also may have conflict with TrendMicro AV:
> > http://www.virtualbox.org/ticket/3370
> 
> 
> -- 
> -Alexey Eromenko "Technologov"
> 
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-dev
> 

_______________________________________________
vbox-dev mailing list
vbox-dev at virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-dev

_______________________________________________
vbox-dev mailing list
vbox-dev at virtualbox.org
http://vbox.innotek.de/mailman/listinfo/vbox-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20100119/59170a58/attachment.html>