BSOD when Jaksta is installed with VirtualBox
Posted: 28. Oct 2012, 23:54
Suffered multiple BSOD's when Jaksta Media Recorder is installed on a system that also had virtualbox.
I am running Windows 7 64 bit. VirtualBox 4.1.22 r80657. Jaksta 4.4.5.
Crash would occur just after logging in probably when network drivers were loaded.
The minidump analysis is below. My guess is that the advice will probably be to reinstall vbox with NAT instead of the network bridge.
Let me know if anything else is needed.
Darren
Crash Dump Analysis provided by OSR Open Systems Resources, Inc.
Online Crash Dump Analysis Service
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ac670
Debug session time: Mon Oct 22 22:55:15.192 2012 (UTC - 4:00)
System Uptime: 0 days 12:24:03.971
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 000000000000c378, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80003212dd3, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0xC5_2
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`03212dd3 418b45f0 mov eax,dword ptr [r13-10h]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
TRAP_FRAME: fffff88003bb1a10 -- (.trap 0xfffff88003bb1a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000c388
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003212dd3 rsp=fffff88003bb1ba0 rbp=fffffa8007608e70
r8=0000000000000000 r9=0000000000000000 r10=fffffa8010299020
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x43:
fffff800`03212dd3 418b45f0 mov eax,dword ptr [r13-10h] ds:ffffffff`fffffff0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030e6569 to fffff800030e6fc0
STACK_TEXT:
fffff880`03bb18c8 fffff800`030e6569 : 00000000`0000000a 00000000`0000c378 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bb18d0 fffff800`030e51e0 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`10068480 : nt!KiBugCheckDispatch+0x69
fffff880`03bb1a10 fffff800`03212dd3 : 00000000`00000000 fffff880`0448738c fffff880`051fc600 fffff880`04e8c6b1 : nt!KiPageFault+0x260
fffff880`03bb1ba0 fffff880`01852845 : fffffa80`10299810 00000000`00000001 00000000`00000000 00000000`0000c388 : nt!ExFreePoolWithTag+0x43
fffff880`03bb1c50 fffff880`043c7aca : fffffa80`07608e70 fffffa80`07608e70 fffffa80`10299810 fffffa80`09d1a1a0 : ndis!NdisFreeMemory+0x15
fffff880`03bb1c80 fffffa80`07608e70 : fffffa80`07608e70 fffffa80`10299810 fffffa80`09d1a1a0 fffffa80`0f79a920 : VBoxNetFlt+0x3aca
fffff880`03bb1c88 fffffa80`07608e70 : fffffa80`10299810 fffffa80`09d1a1a0 fffffa80`0f79a920 fffffa80`09d1a1a0 : 0xfffffa80`07608e70
fffff880`03bb1c90 fffffa80`10299810 : fffffa80`09d1a1a0 fffffa80`0f79a920 fffffa80`09d1a1a0 00000000`00000000 : 0xfffffa80`07608e70
fffff880`03bb1c98 fffffa80`09d1a1a0 : fffffa80`0f79a920 fffffa80`09d1a1a0 00000000`00000000 fffff880`0190c64e : 0xfffffa80`10299810
fffff880`03bb1ca0 fffffa80`0f79a920 : fffffa80`09d1a1a0 00000000`00000000 fffff880`0190c64e fffffa80`0f79a900 : 0xfffffa80`09d1a1a0
fffff880`03bb1ca8 fffffa80`09d1a1a0 : 00000000`00000000 fffff880`0190c64e fffffa80`0f79a900 fffffa80`07608e70 : 0xfffffa80`0f79a920
fffff880`03bb1cb0 00000000`00000000 : fffff880`0190c64e fffffa80`0f79a900 fffffa80`07608e70 fffffa80`09c10010 : 0xfffffa80`09d1a1a0
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+3aca
fffff880`043c7aca ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: VBoxNetFlt+3aca
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 504a14c7
FAILURE_BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca
BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca
Followup: MachineOwner
---------
I am running Windows 7 64 bit. VirtualBox 4.1.22 r80657. Jaksta 4.4.5.
Crash would occur just after logging in probably when network drivers were loaded.
The minidump analysis is below. My guess is that the advice will probably be to reinstall vbox with NAT instead of the network bridge.
Let me know if anything else is needed.
Darren
Crash Dump Analysis provided by OSR Open Systems Resources, Inc.
Online Crash Dump Analysis Service
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03068000 PsLoadedModuleList = 0xfffff800`032ac670
Debug session time: Mon Oct 22 22:55:15.192 2012 (UTC - 4:00)
System Uptime: 0 days 12:24:03.971
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 000000000000c378, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80003212dd3, address which referenced memory
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0xC5_2
CURRENT_IRQL: 2
FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`03212dd3 418b45f0 mov eax,dword ptr [r13-10h]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
TRAP_FRAME: fffff88003bb1a10 -- (.trap 0xfffff88003bb1a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000c388
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003212dd3 rsp=fffff88003bb1ba0 rbp=fffffa8007608e70
r8=0000000000000000 r9=0000000000000000 r10=fffffa8010299020
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExFreePoolWithTag+0x43:
fffff800`03212dd3 418b45f0 mov eax,dword ptr [r13-10h] ds:ffffffff`fffffff0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030e6569 to fffff800030e6fc0
STACK_TEXT:
fffff880`03bb18c8 fffff800`030e6569 : 00000000`0000000a 00000000`0000c378 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03bb18d0 fffff800`030e51e0 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`10068480 : nt!KiBugCheckDispatch+0x69
fffff880`03bb1a10 fffff800`03212dd3 : 00000000`00000000 fffff880`0448738c fffff880`051fc600 fffff880`04e8c6b1 : nt!KiPageFault+0x260
fffff880`03bb1ba0 fffff880`01852845 : fffffa80`10299810 00000000`00000001 00000000`00000000 00000000`0000c388 : nt!ExFreePoolWithTag+0x43
fffff880`03bb1c50 fffff880`043c7aca : fffffa80`07608e70 fffffa80`07608e70 fffffa80`10299810 fffffa80`09d1a1a0 : ndis!NdisFreeMemory+0x15
fffff880`03bb1c80 fffffa80`07608e70 : fffffa80`07608e70 fffffa80`10299810 fffffa80`09d1a1a0 fffffa80`0f79a920 : VBoxNetFlt+0x3aca
fffff880`03bb1c88 fffffa80`07608e70 : fffffa80`10299810 fffffa80`09d1a1a0 fffffa80`0f79a920 fffffa80`09d1a1a0 : 0xfffffa80`07608e70
fffff880`03bb1c90 fffffa80`10299810 : fffffa80`09d1a1a0 fffffa80`0f79a920 fffffa80`09d1a1a0 00000000`00000000 : 0xfffffa80`07608e70
fffff880`03bb1c98 fffffa80`09d1a1a0 : fffffa80`0f79a920 fffffa80`09d1a1a0 00000000`00000000 fffff880`0190c64e : 0xfffffa80`10299810
fffff880`03bb1ca0 fffffa80`0f79a920 : fffffa80`09d1a1a0 00000000`00000000 fffff880`0190c64e fffffa80`0f79a900 : 0xfffffa80`09d1a1a0
fffff880`03bb1ca8 fffffa80`09d1a1a0 : 00000000`00000000 fffff880`0190c64e fffffa80`0f79a900 fffffa80`07608e70 : 0xfffffa80`0f79a920
fffff880`03bb1cb0 00000000`00000000 : fffff880`0190c64e fffffa80`0f79a900 fffffa80`07608e70 fffffa80`09c10010 : 0xfffffa80`09d1a1a0
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxNetFlt+3aca
fffff880`043c7aca ?? ???
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: VBoxNetFlt+3aca
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxNetFlt
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 504a14c7
FAILURE_BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca
BUCKET_ID: X64_0xC5_2_VBoxNetFlt+3aca
Followup: MachineOwner
---------