przejrzałem forum i zdołałem dojść do tego, jak odczytać raport z błędu, niestety nic z niego nie rozumiem, proszę o pomoc...Loading Dump File [C:\Windows\Minidump\101612-23103-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03097670
Debug session time: Tue Oct 16 18:21:09.373 2012 (UTC + 2:00)
System Uptime: 0 days 0:00:11.918
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800798c8f8, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800798c8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031bd5b0 fffff800`03114ca9 : fffffa80`0798c8d0 fffffa80`06aeb040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdad0 fffff800`02ff5557 : fffffa80`0798c8d0 fffff800`0306f2d8 fffffa80`06aeb040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdb00 fffff800`02f5c935 : fffff800`030d0ae0 00000000`00000001 fffffa80`079a1c90 fffffa80`06aeb040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdb40 fffff800`02edb641 : fffff880`00c65e00 fffff800`02f5c910 fffffa80`06aeb000 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdb70 fffff800`03168e5a : 00000000`00000000 fffffa80`06aeb040 00000000`00000080 fffffa80`069f9040 : nt!ExpWorkerThread+0x111
fffff880`031bdc00 fffff800`02ec2d26 : fffff880`02fd7180 fffffa80`06aeb040 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdc40 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d1b740 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
oraz drugi:
Loading Dump File [C:\Windows\Minidump\101612-26847-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump does not have process information
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03055670
Debug session time: Tue Oct 16 18:16:05.861 2012 (UTC + 2:00)
System Uptime: 0 days 20:28:58.209
Loading Kernel Symbols
.............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002d65180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002d65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'tcpip' and 'Unknown_Module_00000000`00000000' overlap
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0c5cfbf8 fffff800`02ee6d5a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02d65180 : nt!KeBugCheckEx
fffff880`0c5cfc00 fffff800`02e99ad7 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0c5cfc90 fffff800`03403895 : fffff800`03429460 fffff880`0c5cfe40 fffff800`03429460 fffff700`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0c5cfd90 fffff800`02e8c513 : 00000000`20aba476 fffff800`03002e80 fffff800`03002e80 fffff680`0008aff8 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0c5cfdc0 fffff800`02ec1581 : fffff800`03002e80 00000000`00000000 00000000`00000001 fffff880`0c5d0018 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0c5cff50 fffff800`02e7c81f : fffffa80`00000000 00000000`1160bfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x7f0
fffff880`0c5d0110 fffff800`02e8f253 : ffffffff`ffffffff fffff880`0c5d03e0 fffff880`0c5d0448 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`0c5d0210 fffff800`02e8b810 : fffff960`00187068 00000000`00000001 fffff900`c00d3280 fffff900`c34bf010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c5d03a8 fffff960`00187068 : 00000000`00000001 fffff900`c00d3280 fffff900`c34bf010 00000000`00000000 : nt!KiServiceLinkage
fffff880`0c5d03b0 00000000`00000001 : fffff900`c00d3280 fffff900`c34bf010 00000000`00000000 00000000`744d2405 : 0xfffff960`00187068
fffff880`0c5d03b8 fffff900`c00d3280 : fffff900`c34bf010 00000000`00000000 00000000`744d2405 fffff960`00186051 : 0x1
fffff880`0c5d03c0 fffff900`c34bf010 : 00000000`00000000 00000000`744d2405 fffff960`00186051 00000000`115f0000 : 0xfffff900`c00d3280
fffff880`0c5d03c8 00000000`00000000 : 00000000`744d2405 fffff960`00186051 00000000`115f0000 00000000`00000000 : 0xfffff900`c34bf010
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Chyba chodzi o coś z procesorem, mam procesor ADM FX-4100 zainstalowany na płycie głównej Gigabyte 970A-UD3
Zasilacz OCZ 600W
Zbadałem temperaturę procesora i na wszystkich rdzeniach wynosiła ona 20-24C
Co mogę zrobić w takiej sytuacji??
