Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\DUMP Logs\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`01e51000 PsLoadedModuleList = 0xfffff800`02096670 Debug session time: Sun Jan 22 19:16:46.538 2012 (UTC - 5:00) System Uptime: 0 days 0:02:32.038 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols PEB is paged out (Peb.Ldr = 000007ff`fffdb018). Type ".hh dbgerr001" for details Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, fffffa8009960b30, fffffa8009960e10, fffff800021d18b0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ------------------------------------------------ | | | NT symbols are not available | | reduced functionality | | | ------------------------------------------------ unable to get nt!KiCurrentEtwBufferOffset unable to get nt!KiCurrentEtwBufferBase ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : wininit.exe Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_OBJECT_TERMINATION (f4) A process or thread crucial to system operation has unexpectedly exited or been terminated. Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no longer function. Arguments: Arg1: 0000000000000003, Process Arg2: fffffa8009960b30, Terminating object Arg3: fffffa8009960e10, Process image file name Arg4: fffff800021d18b0, Explanatory message (ascii) Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ------------------------------------------------ | | | NT symbols are not available | | reduced functionality | | | ------------------------------------------------ unable to get nt!KiCurrentEtwBufferOffset unable to get nt!KiCurrentEtwBufferBase ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 DEBUG_FLR_IMAGE_TIMESTAMP: 0 PROCESS_OBJECT: fffffa8009960b30 IMAGE_NAME: wininit.exe DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xF4 CURRENT_IRQL: 0 STACK_TEXT: fffff880`0f91b0e8 fffff800`022585e2 : 00000000`000000f4 00000000`00000003 fffffa80`09960b30 fffffa80`09960e10 : nt!KeBugCheckEx fffff880`0f91b0f0 fffff800`0220599b : ffffffff`ffffffff fffffa80`09a02600 fffffa80`09960b30 fffffa80`09960b30 : nt!PsSetCurrentThreadPrefetching+0x6e2 fffff880`0f91b130 fffff800`02185448 : ffffffff`ffffffff 00000000`00000001 fffffa80`09960b30 00000000`00000008 : nt!MmGetSystemRoutineAddress+0x144bb fffff880`0f91b180 fffff800`01ecced3 : fffffa80`09960b30 fffff800`c0000005 fffffa80`09a02600 fffff880`0f91b801 : nt!RtlNtStatusToDosError+0x14ec fffff880`0f91b200 fffff800`01ec9470 : fffff800`01f1967f fffff880`0f91bb78 fffff880`0f91b8d0 fffff880`0f91bc20 : nt!KeSynchronizeExecution+0x3a43 fffff880`0f91b398 fffff800`01f1967f : fffff880`0f91bb78 fffff880`0f91b8d0 fffff880`0f91bc20 00000000`00f21cb0 : nt!ZwUnlockFile+0x130 fffff880`0f91b3a0 fffff800`01ecd2c2 : fffff880`0f91bb78 00000000`0000aab7 fffff880`0f91bc20 00000000`00f21788 : nt!IoFreeErrorLogEntry+0x57f fffff880`0f91ba40 fffff800`01ecbe3a : 00000000`00000001 00000000`00f20a28 00000000`772a9c01 00000000`0000aab7 : nt!KeSynchronizeExecution+0x3e32 fffff880`0f91bc20 00000000`77298e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x29aa 00000000`00f20a30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77298e3d STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------