Mam problem z resetowaniem się komputera szczególnie przy instalacji programów wymagających ponownego uruchomienia. Po takim restarcie aby komp zaczął działać muszę włączać naprawę systemu. Wklejam raport o błędach. Proszę o pomoc w rozwiązaniu problemu.
Kod: Zaznacz cały
Loading Dump File [C:\Windows\Minidump\102914-35490-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SVR*c\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e51670
Debug session time: Wed Oct 29 21:02:14.409 2014 (GMT+1)
System Uptime: 0 days 0:01:17.688
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8003708a60, fffffa8003708d40, fffff80002f8b460}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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
---------
1: 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: fffffa8003708a60, Terminating object
Arg3: fffffa8003708d40, Process image file name
Arg4: fffff80002f8b460, Explanatory message (ascii)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
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: fffffa8003708a60
IMAGE_NAME: wininit.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xF4
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02739b08 fffff800`03013822 : 00000000`000000f4 00000000`00000003 fffffa80`03708a60 fffffa80`03708d40 : nt+0x7efc0
fffff880`02739b10 00000000`000000f4 : 00000000`00000003 fffffa80`03708a60 fffffa80`03708d40 fffff800`02f8b460 : nt+0x406822
fffff880`02739b18 00000000`00000003 : fffffa80`03708a60 fffffa80`03708d40 fffff800`02f8b460 fffff800`02f7eae4 : 0xf4
fffff880`02739b20 fffffa80`03708a60 : fffffa80`03708d40 fffff800`02f8b460 fffff800`02f7eae4 fffffa80`03708a60 : 0x3
fffff880`02739b28 fffffa80`03708d40 : fffff800`02f8b460 fffff800`02f7eae4 fffffa80`03708a60 fffff800`02fbfe0b : 0xfffffa80`03708a60
fffff880`02739b30 fffff800`02f8b460 : fffff800`02f7eae4 fffffa80`03708a60 fffff800`02fbfe0b 00000000`00000001 : 0xfffffa80`03708d40
fffff880`02739b38 fffff800`02f7eae4 : fffffa80`03708a60 fffff800`02fbfe0b 00000000`00000001 fffffa80`03ba2b50 : nt+0x37e460
fffff880`02739b40 fffffa80`03708a60 : fffff800`02fbfe0b 00000000`00000001 fffffa80`03ba2b50 fffffa80`03708a60 : nt+0x371ae4
fffff880`02739b48 fffff800`02fbfe0b : 00000000`00000001 fffffa80`03ba2b50 fffffa80`03708a60 fffff880`02739c20 : 0xfffffa80`03708a60
fffff880`02739b50 00000000`00000001 : fffffa80`03ba2b50 fffffa80`03708a60 fffff880`02739c20 00000000`00000000 : nt+0x3b2e0b
fffff880`02739b58 fffffa80`03ba2b50 : fffffa80`03708a60 fffff880`02739c20 00000000`00000000 00000000`00000000 : 0x1
fffff880`02739b60 fffffa80`03708a60 : fffff880`02739c20 00000000`00000000 00000000`00000000 fffffa80`03708a60 : 0xfffffa80`03ba2b50
fffff880`02739b68 fffff880`02739c20 : 00000000`00000000 00000000`00000000 fffffa80`03708a60 00000000`00000005 : 0xfffffa80`03708a60
fffff880`02739b70 00000000`00000000 : 00000000`00000000 fffffa80`03708a60 00000000`00000005 fffffa80`03ba2b50 : 0xfffff880`02739c20
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> !process fffffa8003708a60 3
GetPointerFromAddress: unable to read from fffff80002ebb000
NT symbols are incorrect, please fix symbols
1: kd> lmvm wininit
start end module name