Witam
Od pewnego czasu komp sam sie restartuje… widze tylko niebieska ramke a wniej biale napisy. zasilacz,kartra,ramy,procesor odpadada poniewaz zasilacz i plyta zmieniona ramy przekladalem, procesorow mam 2 na ten socket wiec tez sprawdzalem, ale wpadlem na program WinDBg ktory potrafi rozszyfrowac kod bledu pojawiajacego sie podczas zatrzymania kompa. Oto rezulatat :
Debugger Version 6.8.0004.0 X86Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/downloads/symbols.v
Executable search path is:
Unable to load image 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri Apr 18 23:43:16.187 2008 (GMT+2)
System Uptime: 0 days 0:16:02.761
Unable to load image 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 100000CE, {f3b6c2e2, 0, f3b6c2e2, 0}
ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for ALCXWDM.SYS
*** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS
*************************************************************************
*** ***
*** ***
*** 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 : dump_wmimmc. ( dump_wmimmc+22e2 )
Followup: MachineOwner
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver’s name is displayed on the screen.
Arguments:
Arg1: f3b6c2e2, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: f3b6c2e2, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, Mm internal code.
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
f3b6c2e2
FAULTING_IP:
dump_wmimmc+22e2
f3b6c2e2 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xCE
IP_MODULE_UNLOADED:
dump_wmimmc+22e2
f3b6c2e2 ?? ???
LAST_CONTROL_TRANSFER: from 804df06b to f3b6c2e2
FAILED_INSTRUCTION_ADDRESS:
dump_wmimmc+22e2
f3b6c2e2 ?? ???
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f3c19d4c 804df06b 0012fa38 001f0fff 0012fa18 +0x22e2
f3c19d64 7c90eb94 badb0d00 0012f9e0 6f6f6f6f nt+0x806b
f3c19d68 badb0d00 0012f9e0 6f6f6f6f 6f6f6f6f 0x7c90eb94
f3c19d6c 0012f9e0 6f6f6f6f 6f6f6f6f 00000000 ALCXWDM+0x7d00
f3c19d70 6f6f6f6f 6f6f6f6f 00000000 00000000 0x12f9e0
f3c19d74 6f6f6f6f 00000000 00000000 00000000 0x6f6f6f6f
f3c19d78 00000000 00000000 00000000 00000000 0x6f6f6f6f
STACK_COMMAND: kb
FOLLOWUP_IP:
dump_wmimmc+22e2
f3b6c2e2 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dump_wmimmc+22e2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dump_wmimmc
IMAGE_NAME: dump_wmimmc.
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
kd> lmvm dump_wmimmc
start end module name
jak cos moge dac loga combofixem pomozcie bo zwarjuje…