Microsoft (R) Windows Debugger Version 6.8.0004.0 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\123014-19765-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableMini Kernel Dump does not have process informationSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image Unknown_Module_29101a00`29101a00, Win32 error 0n2*** WARNING: Unable to verify timestamp for Unknown_Module_29101a00`29101a00*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_29101a00`29101a00Debugger can not determine kernel base addressWindows Kernel Version 7600 MP (8 procs) Free x64Product: Server, suite: TerminalServer DataCenter SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Kernel base = 0xfffff800`01a03000 PsLoadedModuleList = 0xfffff800`01c40e50Debug session time: Tue Dec 30 16:40:15.265 2014 (GMT+8)System Uptime: 0 days 0:01:02.905********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Unable to load image Unknown_Module_29101a00`29101a00, Win32 error 0n2*** WARNING: Unable to verify timestamp for Unknown_Module_29101a00`29101a00*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_29101a00`29101a00Debugger can not determine kernel base addressLoading Kernel Symbols.Loading User Symbols******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 124, {0, fffffa8007efb028, b2000004, 10000800}***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : Unknown_ImageFollowup: MachineOwner---------