Dík už to něco vypsalo hodil sem to sem můžeš na to mrknout podle těch kódů chyb sem stejně nic moc nevygooglil .dík
WARNING: Inaccessible path: 'SRV C:\ProgramData\Windbg-symbols
http://msdl.microsoft.com/download/symbols'WARNING: Whitespace at start of path element
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\RomouseK\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
WARNING: Inaccessible path: 'SRV C:\ProgramData\Windbg-symbols
http://msdl.microsoft.com/download/symbols'WARNING: Whitespace at start of path element
Symbol search path is: SRV*C:\ProgramData\Windbg-symbols*http://msdl.microsoft.com/download/symbols;SRV C:\ProgramData\Windbg-symbols
http://msdl.microsoft.com/download/symbols; _NT_SYMBOL_PATH=srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03010000 PsLoadedModuleList = 0xfffff800`03255e90
Debug session time: Wed Jan 4 21:50:00.178 2012 (GMT+1)
System Uptime: 0 days 0:03:09.068
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa800aa46060, fffffa800aa46340, fffff80003393db0}
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
Probably caused by : wininit.exe
Followup: MachineOwner
---------
16.2: kd:x86> !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: fffffa800aa46060, Terminating object
Arg3: fffffa800aa46340, Process image file name
Arg4: fffff80003393db0, Explanatory message (ascii)
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 000007ff`fffd7018). Type ".hh dbgerr001" for details
PROCESS_OBJECT: fffffa800aa46060
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0xF4_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_IMAGE_wininit.exe
Followup: MachineOwner
---------