BSOD on 6.1.8

Discussions related to using VirtualBox on Windows hosts.
Post Reply
ChadZ
Posts: 2
Joined: 12. Jun 2020, 20:56

BSOD on 6.1.8

Post by ChadZ »

I've processed the Windows minidump via windbg.exe and it is pointing to VirtualBoxVM.exe was the process responsible. Below is the output of the bugcheck analysis. Is there somewhere I should be reporting this or is there additional information I could provide?

Code: Select all

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8036c3c9865, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
nt!SwapContext+4a5
fffff803`6c3c9865 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  VirtualBoxVM.e

CURRENT_IRQL:  2

BAD_PAGES_DETECTED: 4402b

LAST_CONTROL_TRANSFER:  from fffff8036c41a02b to fffff8036c3c23a0

STACK_TEXT:  
ffff8780`b4cfc8f8 fffff803`6c41a02b : 00000000`0000001e ffffffff`c0000005 fffff803`6c3c9865 00000000`00000000 : nt!KeBugCheckEx
ffff8780`b4cfc900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x18c3ab


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8036c3c9413-fffff8036c3c9414  2 bytes - nt!SwapContext+53
	[ 48 ff:4c 8b ]
    fffff8036c3c941a-fffff8036c3c941d  4 bytes - nt!SwapContext+5a (+0x07)
	[ 0f 1f 44 00:e8 01 0d 8f ]
    fffff8036c3c984e-fffff8036c3c984f  2 bytes - nt!SwapContext+48e (+0x434)
	[ 48 ff:4c 8b ]
    fffff8036c3c9855-fffff8036c3c9858  4 bytes - nt!SwapContext+495 (+0x07)
	[ 0f 1f 44 00:e8 c6 08 8f ]
12 errors : !nt (fffff8036c3c9413-fffff8036c3c9858)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

 *** Memory manager detected 278571 instance(s) of page corruption, target is likely to have memory corruption.

scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: BSOD on 6.1.8

Post by scottgus1 »

Does this always happen, or was it a one-off? Can you determine an exact procedure to cause it?
ChadZ
Posts: 2
Joined: 12. Jun 2020, 20:56

Re: BSOD on 6.1.8

Post by ChadZ »

So far it was a one-off. I wasn't able to narrow down the exact procedure. I've since updated to .10 and will keep an eye on it.
Post Reply