BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Ak potrebujete pomoc alebo poradiť, píšte sem (len PC, elektronika atď.)...
Napísať odpoveď
Staffy
Amateur
Amateur
Používateľov profilový obrázok
Príspevky: 34
Registrovaný: 05 feb 2007, 19:51

BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Príspevok od používateľa Staffy »

Zdravím, mám takýto zapeklitý problém, BSOD hneď po nalogovaní do windows.
Vyčítal som že je to HW problém (v mojom pripade to ale vyzerá divne, viz. ďalej).
Prečítal som si Dump súbor, a tam je zaujímavé že sa tam spomína súbor ekrn.exe, čo je Eset Smart Security.
V Safe Mode (ten ide bez problémov) som Eset odinštaloval a čuduj sa svete, funguje. Hral som asi 2 hodiny, použil som utilitu od Intelu na kontrolu procesoru, neukázala žiadny problém. Nainštaloval som zase Eset, žiadny problém. A potom zrazu, pri prezeraní netu, zase BSOD, pri zapnutí PC sa to opakuje.

Mal by som reklamovať procesor?
Prikladám výpis z DUMP suboru aj samotny dump subor ak sa niekto chce v tom pohrabať viac.

Spoiler
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Maroš\Desktop\062315-3650-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows

\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows

\symbol_cache*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.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList =

0xfffff800`03298730
Debug session time: Tue Jun 23 17:41:56.137 2015 (UTC + 2:00)
System Uptime: 0 days 0:00:20.448
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol

loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
************************************************************************

*******
*

*
* Bugcheck Analysis

*
*

*
************************************************************************

*******

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800711f028, bf800000, 200401}

Probably caused by : GenuineIntel

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: fffffa800711f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: ekrn.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`0316da58 fffff800`0301aa3b : 00000000`00000124

00000000`00000000 fffffa80`0711f028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`031dec33 : 00000000`00000001

fffffa80`07120ea0 00000000`00000000 fffffa80`07120ef0 : hal!

HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`0301a700 : 00000000`00000728

fffffa80`07120ea0 fffff880`0316de30 fffff880`0316de00 : nt!

WheaReportHwError+0x263
fffff880`0316db00 fffff800`0301a052 : fffffa80`07120ea0

fffff880`0316de30 fffffa80`07120ea0 00000000`00000000 : hal!

HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`03019f0d : 00000000`00000004

00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!

HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`0300de88 : 00000000`00000002

00000000`00001000 00000000`00000000 00000000`00000000 : hal!

HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`030c41ac : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : hal!

HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`030c4013 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KxMcheckAbort+0x6c
fffff880`0316de30 fffff800`030bc394 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KiMcheckAbort+0x153
fffff880`048b2638 00000000`00000000 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0xb4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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: fffffa800711f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: ekrn.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`0316da58 fffff800`0301aa3b : 00000000`00000124

00000000`00000000 fffffa80`0711f028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`031dec33 : 00000000`00000001

fffffa80`07120ea0 00000000`00000000 fffffa80`07120ef0 : hal!

HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`0301a700 : 00000000`00000728

fffffa80`07120ea0 fffff880`0316de30 fffff880`0316de00 : nt!

WheaReportHwError+0x263
fffff880`0316db00 fffff800`0301a052 : fffffa80`07120ea0

fffff880`0316de30 fffffa80`07120ea0 00000000`00000000 : hal!

HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`03019f0d : 00000000`00000004

00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!

HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`0300de88 : 00000000`00000002

00000000`00001000 00000000`00000000 00000000`00000000 : hal!

HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`030c41ac : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : hal!

HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`030c4013 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KxMcheckAbort+0x6c
fffff880`0316de30 fffff800`030bc394 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KiMcheckAbort+0x153
fffff880`048b2638 00000000`00000000 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0xb4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

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: fffffa800711f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: ekrn.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff880`0316da58 fffff800`0301aa3b : 00000000`00000124

00000000`00000000 fffffa80`0711f028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`0316da60 fffff800`031dec33 : 00000000`00000001

fffffa80`07120ea0 00000000`00000000 fffffa80`07120ef0 : hal!

HalBugCheckSystem+0x1e3
fffff880`0316daa0 fffff800`0301a700 : 00000000`00000728

fffffa80`07120ea0 fffff880`0316de30 fffff880`0316de00 : nt!

WheaReportHwError+0x263
fffff880`0316db00 fffff800`0301a052 : fffffa80`07120ea0

fffff880`0316de30 fffffa80`07120ea0 00000000`00000000 : hal!

HalpMcaReportError+0x4c
fffff880`0316dc50 fffff800`03019f0d : 00000000`00000004

00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!

HalpMceHandler+0x9e
fffff880`0316dc90 fffff800`0300de88 : 00000000`00000002

00000000`00001000 00000000`00000000 00000000`00000000 : hal!

HalpMceHandlerWithRendezvous+0x55
fffff880`0316dcc0 fffff800`030c41ac : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : hal!

HalHandleMcheck+0x40
fffff880`0316dcf0 fffff800`030c4013 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KxMcheckAbort+0x6c
fffff880`0316de30 fffff800`030bc394 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!

KiMcheckAbort+0x153
fffff880`048b2638 00000000`00000000 : 00000000`00000000

00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0xb4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae

FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

Followup: MachineOwner
---------
Prílohy
IMG_2392.JPG
BSOD.zip
(18.02 KiB) 38 stiahnutí
Hore
guess.whoo
Redeemer
Redeemer
Používateľov profilový obrázok
Príspevky: 13616
Registrovaný: 30 jan 2008, 12:58
Bydlisko: VK,TN
Kontaktovať používateľa:
Kontaktné informácie používateľa - guess.whoo

Re: BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Príspevok od používateľa guess.whoo »

preco znova neodinstalujes eset? keby si mal vadne cpu tak to robi aj bez esetu
Hore
Gothar
Moderátor
Moderátor
Používateľov profilový obrázok
Príspevky: 19413
Registrovaný: 21 feb 2005, 21:19
Bydlisko: KE

Re: BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Príspevok od používateľa Gothar »

S CPU to nema nic. Mas zrejme nainstalovany este iny AV software.
Skus spustit ESET uninstaller a odinstaluj vsetko co ti ukaze. Potom nahod Smart Security a malo by to fungovat:
Zdroj: https://forum.eset.com/topic/1245-const ... #entry8551
Postup: http://kb.eset.com/esetkb/index?page=co ... d=soln2289
Samotny uninstaller: http://download.eset.com/special/ESETUninstaller.exe
Hore
Staffy
Amateur
Amateur
Používateľov profilový obrázok
Príspevky: 34
Registrovaný: 05 feb 2007, 19:51

Re: BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Príspevok od používateľa Staffy »

Guess.who - tiež tak rozmýšlam, mätie ma ale to, že to ukazuje ako HW problém, aj ďalej v dumpe - dáva to Micro-Architectural Error pri CPU - rozmýšlal som či to nie je len "vyvolané" esetom, pozrel sa tam kam už nebolo bezpečné alebo dačo také:D

Iný AV software nemám, ani nebol spomenutý pri odinštalacii esetu. Po ďalšom gúglení som našiel túto diskusiu, kde sa spomínajú Gigabyte dosky a ich AppCentre (netýka sa to len ich, takže je to fakt zrejme chyba esetu). https://forum.eset.com/topic/5217-eset- ... 124-bsods/

Zatiaľ ďakujem za pomoc.
Hore
hrban
Addict
Addict
Používateľov profilový obrázok
Príspevky: 4950
Registrovaný: 14 júl 2005, 7:44
Bydlisko: Almere
Kontaktovať používateľa:
Kontaktné informácie používateľa - hrban

Re: BSOD - Modrá smrť - Error 0x124 - Vadné CPU?

Príspevok od používateľa hrban »

AV kľudne môže spôsobiť BSOD, ak náhodou zablokuje ovládače alebo nejakú časť OS ktorá je potrebná pre chod systému tak sa zrúti jak domček z karát...
pravdepodobne nejaký konflikt ovládačov a esetu
Hore
Napísať odpoveď

Návrat na "Pomoc"