VirtualBox

Ticket #6919 (closed defect: duplicate)

Opened 4 years ago

Last modified 4 years ago

after update from 3.2.0 to 3.2.2 has BSOD when start linux guest on windows host

Reported by: Alpx Owned by:
Priority: blocker Component: other
Version: VirtualBox 3.2.2 Keywords:
Cc: Guest type: Linux
Host type: Windows

Description

I have updated VB 3.2.0 to 3.2.2 and after it has BSOD when start linux guest. I had two reproducible cases:

  1. Host: Windows 7, Guest: Ubuntu 10.4
  2. Host: Windows Vista, Guest: FC 6.0

Probably this issue is reproduced with other OS versions. I had to revert to 3.2.0.

Bugcheck Analysis of minidamp image.

BugCheck D1, {14, 2, 0, 9df0e7cb} Probably caused by : VMMR0.r0 ( VMMR0+447cb )

Followup: MachineOwner


0: kd> !analyze -v

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: 00000014, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 9df0e7cb, address which referenced memory

Debugging Details:


READ_ADDRESS: 00000014

CURRENT_IRQL: 2

FAULTING_IP: VMMR0+447cb 9df0e7cb 8b4e14 mov ecx,dword ptr [esi+14h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 9df0e7cb to 82a467eb

STACK_TEXT: 8dd1b64c 9df0e7cb badb0d00 00000000 00000001 ntMiUnlinkPageFromList+0x13d WARNING: Stack unwind information not available. Following frames may be wrong. 8dd1b6e0 9df0fda7 00000000 00000002 00000000 VMMR0+0x447cb 8dd1b718 9dfe1e6d 0179938c 872a0a90 00000000 VMMR0+0x45da7 8dd1b740 9dfe3ce3 87143018 00000036 86a54020 VBoxNetAdp+0x1e6d 8dd1b764 8bb8d4e5 87143074 8dd1b7ac 00000000 VBoxNetAdp+0x3ce3 8dd1b78c 8bb8d30a 8dd1b7b0 8dd1b7ac 00000001 ndis!_NULL_IMPORT_DESCRIPTOR <PERF> (ndis+0x6c4e5) 8dd1b7f4 8bb25474 859250e0 87434860 00000000 ndis!_NULL_IMPORT_DESCRIPTOR <PERF> (ndis+0x6c30a) 8dd1b820 8bb89d8c 859250e0 87434860 00000000 ndisNdisSetupDmaTransfer+0x3e 8dd1b850 8bed003e 85901160 87434860 00000000 ndis!_NULL_IMPORT_DESCRIPTOR <PERF> (ndis+0x68d8c) 8dd1b89c 8bed07c1 873a6008 00000000 00000000 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x6903e) 8dd1b8f0 8bed04d3 8bf50d98 00000000 00000000 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x697c1) 8dd1b928 8bed8273 8bf50d98 865c245c 865c24f8 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x694d3) 8dd1b9c8 8bede30e 005c245c 86b1e670 86a96138 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x71273) 8dd1ba48 8bede5c9 00000000 8dd1ba00 8bf50d98 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x7730e) 8dd1ba68 8becd2c3 8bf50d98 8dd1ba84 86b1e734 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x775c9) 8dd1bcc4 8be8d466 86b1e670 87368688 00000001 tcpip!_NULL_IMPORT_DESCRIPTOR <PERF> (tcpip+0x662c3) 8dd1bcec 82c207b5 86597590 86b1e670 85790d48 tcpip!ARPSendData+0x1c1 8dd1bd00 82a6df2b 876f1b98 00000000 85790d48 nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x2207b5) 8dd1bd50 82c0e66d 00000001 bf29e890 00000000 ntKdDebuggerDataBlock+0x24b 8dd1bd90 82ac00d9 82a6de1e 00000001 00000000 nt!_NULL_IMPORT_DESCRIPTOR <PERF> (nt+0x20e66d) 8dd1be28 00000000 00000000 00000000 00000000 ntNtRequestWaitReplyPort+0x4f9

STACK_COMMAND: kb

FOLLOWUP_IP: VMMR0+447cb 9df0e7cb 8b4e14 mov ecx,dword ptr [esi+14h]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: VMMR0+447cb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VMMR0

IMAGE_NAME: VMMR0.r0

DEBUG_FLR_IMAGE_TIMESTAMP: 4c066d60

FAILURE_BUCKET_ID: 0xD1_VMMR0+447cb

BUCKET_ID: 0xD1_VMMR0+447cb

Followup: MachineOwner


Change History

comment:1 Changed 4 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to duplicate

The first uploaded VBox 3.2.2 Windows build contained a regression which was fixed and the package was updated. The package with the build number 62298 has the bug, the fixed build (available from the download page) is 62321. Please download and install again, this should fix your problem.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use