Mój Windows nie wstaje, po wyświetleniu bootloadera system miga niebieskim tłem i się resetuje, nie widzę co pisze na niebieskim ekranie. Całe szczęście mam drugi system, więc spróbowałem wygrzebać treść błędu. Folder C:\Windows\Minidump\ jest pusty, jedyną informację znalazłem w pliku C:\Windows\MEMOERY.DMP
Automatyczne naprawianie systemu nic nie wykrywa błędu.
Borykam się także z problemem bad sektorów, lecz chkdsk nie wykrywa obecnie uszkodzonego sektora, który by był aktywny i z którym by sobie nie radził, dedukuje ze to nie jest główną przyczyną Bluscreena.
Proszę o pomoc, chcę uniknąć formata.
BugCheck 7E, {ffffffffc0000005, fffff88004b2d284, fffff8800315f6d8, fffff8800315ef30}
Microsoft (R) Windows Debugger Version 6.2.8229.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C]
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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03a50000 PsLoadedModuleList = 0xfffff800`03c94650
Debug session time: Sat Apr 7 11:45:21.050 2012 (UTC + 2:00)
System Uptime: 0 days 0:00:18.673
*********************************************************************
* 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
Loading unloaded module list
....
TRIAGER: Could not open triage file : J:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
TRIAGER: Could not open triage file : J:\Program Files\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : J:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\user.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff88004b2d284, fffff8800315f6d8, fffff8800315ef30}
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for V0260Vid.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ks.sys -
*** ERROR: Module load completed but symbols could not be loaded for ksthunk.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
TRIAGER: Could not open triage file : J:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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 : V0260Vid.sys ( V0260Vid+a284 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004b2d284, The address that the exception occurred at
Arg3: fffff8800315f6d8, Exception Record Address
Arg4: fffff8800315ef30, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
TRIAGER: Could not open triage file : J:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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***
******
*************************************************************************
*************************************************************************
******
******
***Either you specified an unqualified symbol, or your debugger***
***doesn't have full symbol information. Unqualified symbol***
***resolution is turned off by default. Please either specify a***
***fully qualified symbol module!symbolname, or enable resolution***
***of unqualified symbols by typing ".symopt- 100". Note that***
***enabling unqualified symbol resolution with network symbol***
***server shares in the symbol path may cause the debugger to***
***appear to hang for long periods of time when an incorrect***
***symbol name is typed or the network symbol server is down.***
******
***For some commands 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.
FAULTING_MODULE: fffff80003a50000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 469d8a36
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
V0260Vid+a284
fffff880`04b2d284 488b4d08 mov rcx,qword ptr [rbp+8]
EXCEPTION_RECORD: fffff8800315f6d8 -- (.exr 0xfffff8800315f6d8)
ExceptionAddress: fffff88004b2d284 (V0260Vid+0x000000000000a284)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000008
Attempt to read from address 0000000000000008
CONTEXT: fffff8800315ef30 -- (.cxr 0xfffff8800315ef30)
rax=fffff8800315f960 rbx=fffff88004b23000 rcx=fffff8800315f990
rdx=0000000000000000 rsi=fffffa80033b2c60 rdi=fffffa80033a0b30
rip=fffff88004b2d284 rsp=fffff8800315f910 rbp=0000000000000000
r8=fffff8800315f984 r9=000000000000000c r10=000000000000000b
r11=00000000019d85bc r12=0000000000000000 r13=fffff88003a13110
r14=0000000000000001 r15=fffff8800315fc00
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
V0260Vid+0xa284:
fffff880`04b2d284 488b4d08 mov rcx,qword ptr [rbp+8] ss:0018:00000000`00000008=????????????????
Resetting default scope
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88004b4fad1 to fffff88004b2d284
STACK_TEXT:
fffff880`0315f910 fffff880`04b4fad1 : 00000000`00000000 fffffa80`033a0b30 fffffa80`033b2e98 fffffa80`033b2c60 : V0260Vid+0xa284
fffff880`0315fa90 fffff880`04b4ca78 : 00000000`00000000 fffff880`03a13110 00000000`00000000 fffffa80`000e0082 : V0260Vid+0x2cad1
fffff880`0315fac0 fffff880`04b4b8d2 : 00000000`00000001 fffff880`03a13110 fffffa80`0340fe68 fffffa80`0340fbc0 : V0260Vid+0x29a78
fffff880`0315fb00 fffff880`03a2ba9a : fffffa80`00000000 fffffa80`00000001 00000000`00000000 fffffa80`033a8800 : V0260Vid+0x288d2
fffff880`0315fb40 fffff880`03a2b69f : 00000000`00000000 00000000`00000000 fffffa80`033b2e98 fffffa80`033b2e98 : ks!KsServiceBusEnumPnpRequest+0x15ca
fffff880`0315fba0 fffff800`03bca1d2 : fffffa80`00000001 fffffa80`033b2c60 fffffa80`033b2ee0 fffffa80`033b2c60 : ks!KsServiceBusEnumPnpRequest+0x11cf
fffff880`0315fc00 fffff880`041d4938 : fffffa80`02efc710 fffff880`0315fd40 ffffec3a`f796c07d fffff800`00b96080 : nt!IoCompleteRequest+0x4d2
fffff880`0315fc30 fffff800`03be2695 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`029e73e0 : ksthunk+0x938
fffff880`0315fc90 fffff800`03d66f7a : ffffffff`fa0a1f00 fffffa80`03305b60 00000000`00000080 fffffa80`03305b60 : nt!MmSetBankedSection+0x4865
fffff880`0315fd40 fffff800`03abd9c6 : fffff800`03c41e80 fffffa80`03305b60 fffffa80`01904680 fffff880`0121ecb0 : nt!PsCreateSystemThread+0x1da
fffff880`0315fd80 00000000`00000000 : fffff880`03160000 fffff880`0315a000 fffff880`0315f2e0 00000000`00000000 : nt!KeInitializeSemaphore+0x24a
FOLLOWUP_IP:
V0260Vid+a284
fffff880`04b2d284 488b4d08 mov rcx,qword ptr [rbp+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: V0260Vid+a284
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: V0260Vid
IMAGE_NAME: V0260Vid.sys
STACK_COMMAND: .cxr 0xfffff8800315ef30 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
.Jest jeszcze opcja podmienienia rejestru z kopii zapasowej (config\RegBack ->SYSTEM<) - tylko pytanie czy w kopii wszystko gra…
?
kolega nie ma nic w Minidump 
