VirtualBox

Opened 12 years ago

Closed 10 years ago

#10029 closed defect (fixed)

BSOD if VirtualBox network and Applian network both enabled on nic — at Version 5

Reported by: Steve Owned by:
Component: network Version: VirtualBox 4.1.6
Keywords: Applian, VBoxNetFlt Cc:
Guest type: other Host type: Windows

Description (last modified by Frank Mehnert)

A BSOD will occur on Windows 7 Host 64 bit system if Applian's Replay Media Catcher and VirtualBox 4.1.6 are both installed and both network drivers are enabled. Disabling either or uninstalling either will fix the problem.

DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: 000000000000745e, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff800031fbdd3, address which referenced memory

afflicting drivers:
fffff8800462f000 fffff8800465d000 VBoxNetFlt VBoxNetFlt.sys Fri Nov 04 07:36:56 2011 (4EB3CE58)
fffff8800fff2000 fffff8800fffd000 appliand appliand.sys Fri May 20 06:20:42 2011 (4DD6407A)

Change History (5)

comment:1 by Mike Forester, 12 years ago

Identical BSOD under identical circumstances. Applian insists quite persuasively it's a VBox problem and has been known for some time, that the VBox network driver is bringing down the system and that this behavior is unacceptable. I agree.

comment:2 by edwinyzhyip, 12 years ago

I don't use Applian's Replay Media Catcher , but I had exactly the same problem as indicated by the WinDbg report.

BSOD happens immediately when the computer tries to access another computer in the local network, and I fixed the problem by uninstalling VirtualBox-4.1.8-75467-Win then install the newer VirtualBox-4.1.16-78094-Win. Hope it helps.

Last edited 12 years ago by edwinyzhyip (previous) (diff)

comment:3 by escarls, 12 years ago

I can confirm that this crash still occurs on Windows 7 64 bit when both RMC 4.3.3 and VB 4.1.18-78361 are installed on the same computer.

comment:4 by Mike Forester, 11 years ago

This seems fixed as of VB 4.2.10-84104. I see nothing about it in the change logs and it may have been fixed months ago; until now I've been careful not to enable both drivers simultaneously. They now coexist happily.

comment:5 by Frank Mehnert, 10 years ago

Description: modified (diff)
Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use