WinDbg i csrss.exe
Od dość długiego czasu mój komputer pada bez powodu – nie tylko Windows, takźe w Linuksie czy nawet Dosie. Postanowiłem puścić WinDbg, źeby zobaczyć, czy da mi to jakąś informację:
W jaki sposób mogę się dowiedzieć, co dokładniej wywala mi system?
*******************************************************************************
* *
* 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: 00000003, Process
Arg2: 828e8248, Terminating object
Arg3: 828e83bc, Process image file name
Arg4: 805f9f88, Explanatory message (ascii)
Debugging Details:
––––––––––––––––––
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
MODULE_NAME: csrss
FAULTING_MODULE: 00000000
DEBUG_FLR_IMAGE_TIMESTAMP: 0
PROCESS_OBJECT: 828e8248
IMAGE_NAME: csrss.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xF4
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f4e95520 8062c359 000000f4 00000003 828e8248 nt+0x5c31e
f4e95544 805f9f46 805f9f88 828e8248 828e83bc nt+0x155359
f4e95574 804de7ec 828e8490 c0000006 f4e959b0 nt+0x122f46
f4e95584 804ddae1 badb0d00 f4e955fc a39dbcf6 nt+0x77ec
f4e959b0 805064c2 f4e959d8 00000000 f4e95d64 nt+0x6ae1
f4e95d34 804e206b 006efbe8 006efc08 00000000 nt+0x2f4c2
f4e95d50 804de7ec 006efbe8 006efc08 00000000 nt+0xb06b
f4e95d64 7c90eb94 badb0d00 006efbdc 00000000 nt+0x77ec
f4e95d68 badb0d00 006efbdc 00000000 f4d32dcc 0x7c90eb94
f4e95d6c 006efbdc 00000000 f4d32dcc 00000000 0xbadb0d00
f4e95d70 00000000 f4d32dcc 00000000 00000000 0x6efbdc
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
–––––––––
W jaki sposób mogę się dowiedzieć, co dokładniej wywala mi system?
Odpowiedzi: 1
lukmarcus:W jaki sposób mogę się dowiedzieć, co dokładniej wywala mi system?
Pewnie logi systemowe (te z linuksa takźe) masz przejrzane, temperatury i napięca masz sprawdzone ?
A no i przeczytałeś to: http://rtfm.killfile.pl
Strona 1 / 1