Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18933.amd64fre.win7sp1_gdr.150715-0600
Machine Name:
Kernel base = 0xfffff800`02851000 PsLoadedModuleList = 0xfffff800`02a98730
Debug session time: Wed Aug 19 13:09:35.250 2015 (UTC + 2:00)
System Uptime: 0 days 0:02:38.086
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffffff, 1, fffff960002c1f6a, 0}

Unable to load image VBoxDisp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxDisp.dll
*** ERROR: Module load completed but symbols could not be loaded for VBoxDisp.dll

Could not read faulting driver name

Probably caused by : VBoxDisp.dll ( VBoxDisp+4b4b )

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

0: kd> !analyze -v; .logclose; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffff, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960002c1f6a, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b02100
 ffffffffffffffff 

FAULTING_IP: 
win32k!PopThreadGuardedObject+16
fffff960`002c1f6a 4c8918          mov     qword ptr [rax],r11

MM_INTERNAL_CODE:  0

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007951a40 -- (.trap 0xfffff88007951a40)
.trap 0xfffff88007951a40
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffffffff rbx=0000000000000000 rcx=fffff900c452af20
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002c1f6a rsp=fffff88007951bd0 rbp=fffff88007952780
 r8=0000000000000002  r9=fffff900c452b000 r10=fffff88005424b88
r11=ffffffffffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32k!PopThreadGuardedObject+0x16:
fffff960`002c1f6a 4c8918          mov     qword ptr [rax],r11 ds:ffffffff`ffffffff=????????????????
.trap
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002941017 to fffff800028c45c0

STACK_TEXT:  
fffff880`079518d8 fffff800`02941017 : 00000000`00000050 ffffffff`ffffffff 00000000`00000001 fffff880`07951a40 : nt!KeBugCheckEx
fffff880`079518e0 fffff800`028c26ee : 00000000`00000001 ffffffff`ffffffff 00000000`00001700 fffff900`c452af20 : nt! ?? ::FNODOBFM::`string'+0x4174f
fffff880`07951a40 fffff960`002c1f6a : fffff900`c0499000 fffff900`c28b4f58 fffff900`c461ce90 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07951bd0 fffff960`001188eb : 00000000`00000008 fffff900`c28b4f10 00000000`00000004 fffff900`c0b88cc0 : win32k!PopThreadGuardedObject+0x16
fffff880`07951c00 fffff960`000c5b4d : 00000000`00000000 fffff900`c452af40 fffff900`00000002 00000000`00000000 : win32k!FreeThreadBufferWithTag+0x17
fffff880`07951c30 fffff960`00804b4b : fffff900`00000008 fffff880`00000002 fffff900`c29bcca0 fffff880`07952368 : win32k!EngTextOut+0xee9
fffff880`07951fc0 fffff900`00000008 : fffff880`00000002 fffff900`c29bcca0 fffff880`07952368 00000000`00000000 : VBoxDisp+0x4b4b
fffff880`07951fc8 fffff880`00000002 : fffff900`c29bcca0 fffff880`07952368 00000000`00000000 00000000`00000000 : 0xfffff900`00000008
fffff880`07951fd0 fffff900`c29bcca0 : fffff880`07952368 00000000`00000000 00000000`00000000 fffff900`c19f0d58 : 0xfffff880`00000002
fffff880`07951fd8 fffff880`07952368 : 00000000`00000000 00000000`00000000 fffff900`c19f0d58 fffff900`c19f0de8 : 0xfffff900`c29bcca0
fffff880`07951fe0 00000000`00000000 : 00000000`00000000 fffff900`c19f0d58 fffff900`c19f0de8 fffff900`c19f0c30 : 0xfffff880`07952368


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxDisp+4b4b
fffff960`00804b4b ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  VBoxDisp+4b4b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxDisp

IMAGE_NAME:  VBoxDisp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  550705cb

FAILURE_BUCKET_ID:  X64_0x50_VBoxDisp+4b4b

BUCKET_ID:  X64_0x50_VBoxDisp+4b4b

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