Přidat otázku mezi oblíbenéZasílat nové odpovědi e-mailemVyřešeno BSOD - STOP 0x00000124

ne, nezjistím




Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02057000 PsLoadedModuleList = 0xfffff800`0229a670
Debug session time: Tue Jun 4 10:38:00.265 2013 (UTC - 4:00)
System Uptime: 0 days 0:00:17.765
************************************************** *****************************
* *
* 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: fffffa80027c28f8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`01f996f0 fffff800`02317ca9 : fffffa80`027c28d0 fffffa80`018f8b50 fffff8a0`00000005 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`01f99c10 fffff800`021f8e87 : fffffa80`027c28d0 fffff800`022722d8 fffffa80`018f8b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`01f99c40 fffff800`02160285 : fffff800`022d3ae0 00000000`00000001 fffffa80`027be830 fffffa80`018f8b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`01f99c80 fffff800`020d6251 : fffff880`0106ae00 fffff800`02160260 fffffa80`018f8b00 0574c985`4830244c : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`01f99cb0 fffff800`0236aede : 8548d98b`48fa8b48 fffffa80`018f8b50 00000000`00000080 fffffa80`018ed5f0 : nt!ExpWorkerThread+0x111
fffff880`01f99d40 fffff800`020bd906 : fffff880`01e5c180 fffffa80`018f8b50 fffff880`01e66fc0 0010f083`89483024 : nt!PspSystemThreadStartup+0x5a
fffff880`01f99d80 00000000`00000000 : fffff880`01f9a000 fffff880`01f94000 fffff880`025c9750 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner



MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------
systém označí viníka driver a neřekne jaký- to je hodně velký rozpor. ověřoval jsem to online analyze dump.

Reakce na odpověď

1 Zadajte svou přezdívku:
2 Napište svou odpověď:
3 Pokud chcete dostat ban, zadejte libovolný text:

Zpět do poradny