Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\011319-37440-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24150.x86fre.win7sp1_ldr_escrow.180528-1700
Machine Name:
Kernel base = 0x82c03000 PsLoadedModuleList = 0x82d57730
Debug session time: Sun Jan 13 20:29:52.325 2019 (UTC + 1:00)
System Uptime: 5 days 9:19:19.230
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....................................
Unable to load image \SystemRoot\system32\drivers\fslx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fslx.sys
*** ERROR: Module load completed but symbols could not be loaded for fslx.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 98a723ed, b06e17b4, 0}

Probably caused by : fslx.sys ( fslx+5d3ed )

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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 98a723ed, The address that the exception occurred at
Arg3: b06e17b4, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP: 
fslx+5d3ed
98a723ed 668b08          mov     cx,word ptr [eax]

TRAP_FRAME:  b06e17b4 -- (.trap 0xffffffffb06e17b4)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=cd971348 edx=00000002 esi=cd9713e4 edi=cd971348
eip=98a723ed esp=b06e1828 ebp=b06e1834 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
fslx+0x5d3ed:
98a723ed 668b08          mov     cx,word ptr [eax]        ds:0023:00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  vpsserver.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from 98a72548 to 98a723ed

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b06e1834 98a72548 00000000 98a52f1e 00020000 fslx+0x5d3ed
b06e1854 98a17857 cd971348 98a52f1e fdb8d000 fslx+0x5d548
b06e1888 98a1cd68 a3ad635c fdb8d000 8a4567a0 fslx+0x2857
b06e1900 98a1b5be 88963518 fd3155d8 00000a34 fslx+0x7d68
b06e1948 98a1c035 8900cb28 fd3155d8 fdbbb628 fslx+0x65be
b06e1968 82c3c117 8900cb28 fd3157d4 fdbbb684 fslx+0x7035
b06e1980 82e55d8a 9a308474 b06e1b30 00000000 nt!IofCallDriver+0x63
b06e1a60 82e35038 85cc4420 85ca19b8 c2409008 nt!IopParseDevice+0xf08
b06e1adc 82e45692 00000000 b06e1b30 00000040 nt!ObpLookupObjectName+0x510
b06e1b38 82e3bf88 06bdcf00 85ca19b8 fdbbb601 nt!ObOpenObjectByName+0x165
b06e1bb4 82e5fd32 06bdcf5c c0100080 06bdcf00 nt!IopCreateFile+0x6c3
b06e1c00 82c42b8e 06bdcf5c c0100080 06bdcf00 nt!NtCreateFile+0x34
b06e1c00 76f26bb4 06bdcf5c c0100080 06bdcf00 nt!KiSystemServicePostCall
06bdcf64 00000000 00000000 00000000 00000000 0x76f26bb4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fslx+5d3ed
98a723ed 668b08          mov     cx,word ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  fslx+5d3ed

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fslx

IMAGE_NAME:  fslx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51faa3e0

FAILURE_BUCKET_ID:  0x8E_fslx+5d3ed

BUCKET_ID:  0x8E_fslx+5d3ed

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_fslx+5d3ed

FAILURE_ID_HASH:  {278957f5-6c83-c844-c330-52f9df9113fe}

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