MACHINE_CHECK_EXCEPTION Mavi Ekran Hatası

Alphi53

Hectopat
Katılım
17 Temmuz 2019
Mesajlar
84
Yeni 8 GB RAM taktım ama RAM'le alakalı değil, Intel ile ilgili bir şey sanırım. Ne yapmam lazım?

CPU : Intel i5 9400F
RAM : 2x8 Crucial Ballistix Sport LT 3000MHz CL15
ANAKART : Gigabyte H310M DS2.0
GPU : ASUS DUAL RX 580 4GB
OS : Windows 10 1903

Kod:
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Alp Eren\Desktop\113019-23218-01 - Kopya.dmp]
Mini Kernel Dump File: Only registers and stack trace are available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (6 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Built by: 18362.1.amd64fre.19h1_release.190318-1202.
Machine Name:
Kernel base = 0xfffff801`42800000 PsLoadedModuleList = 0xfffff801`42c48170.
Debug session time: Sat Nov 30 16:34:20.174 2019 (UTC + 3:00)
System Uptime: 2 days 19:23:11.675.
Loading Kernel Symbols.
...............................................................
................................................................
.........................................................
Loading User Symbols.
Loading unloaded module list.
......................................
For analysis of this file, run !analyze -v.
nt!KeBugCheckEx:
fffff801`429c14e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffac80`e9c2cca0=000000000000009c.
1: kd> !analyze -v.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors.
        If the processor has ONLY MCE feature available (For example Intel.
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR.
        2 - Address of MCA_EXCEPTION structure.
        3 - High 32 bits of P5_MC_ADDR MSR.
        4 - Low  32 bits of P5_MC_ADDR MSR.
        If the processor also has MCA feature available (For example Intel.
        Pentium Pro), the parameters are:
        1 - Bank number.
        2 - Address of MCA_EXCEPTION structure.
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error.
    IA64 Processors.
        1 - Bugcheck Type.
            1 - MCA_ASSERT.
            2 - MCA_GET_STATEINFO.
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO.
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL.
                FW reported a fatal MCA.
            5 - MCA_NONFATAL.
                SAL reported a recoverable MCA and we don't support currently.
                support recovery or SAL generated an MCA and then couldn't.
                produce an error record.
            0xB - INIT_ASSERT.
            0xC - INIT_GET_STATEINFO.
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO.
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL.
                  Not used.
        2 - Address of log.
        3 - Size of log.
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO.
    AMD64 Processors (If Param 1 is < 0x80000000)
        1 - Bank number.
        2 - Address of MCA_EXCEPTION structure.
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error.
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error.
    AMD64 Processors (If Param 1 is > 0x80000000)
        1 - Failure Type.
           VALUES:
                0x80000001: Spurious MCE.
                    2 - Address of MCA_EXCEPTION structure.
                0x80000002: Rendezvous failure.
                    2 - Address of MCA_EXCEPTION structure.
           END_VALUES.
Arguments:
Arg1: 0000000000000000.
Arg2: ffffac80e9c2ccd0.
Arg3: 0000000000000000.
Arg4: 0000000000000000.

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


KEY_VALUES_STRING: 1.

    Key  : Analysis.CPU.Sec.
    Value: 2.

    Key  : Analysis.DebugAnalysisProvider.CPP.
    Value: Create: 8007007e on DESKTOP-6BJ4D89.

    Key  : Analysis.DebugData.
    Value: CreateObject.

    Key  : Analysis.DebugModel.
    Value: CreateObject.

    Key  : Analysis.Elapsed.Sec.
    Value: 15.

    Key  : Analysis.Memory.CommitPeak.Mb.
    Value: 71.

    Key  : Analysis.System.
    Value: CreateObject.


BUGCHECK_CODE:  9c.

BUGCHECK_P1: 0.

BUGCHECK_P2: ffffac80e9c2ccd0.

BUGCHECK_P3: 0.

BUGCHECK_P4: 0.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1.

PROCESS_NAME:  System.

BAD_STACK_POINTER:  ffffac80e9c2cc98.

STACK_TEXT:
ffffac80`e9c2cc98 fffff801`432ff9f1 : 00000000`0000009c 00000000`00000000 ffffac80`e9c2ccd0 00000000`00000000 : nt!KeBugCheckEx.
ffffac80`e9c2cca0 fffff801`432fff7d : 00000000`00000006 ffffac80`e9c2d010 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11d.
ffffac80`e9c2ce00 fffff801`432fefc8 : 00000000`00000000 ffffac80`e9c2d090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131.
ffffac80`e9c2ce30 fffff801`433001a7 : ffff9885`ea2b7a50 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c.
ffffac80`e9c2ce60 fffff801`42aa4a20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37.
ffffac80`e9c2ce90 fffff801`429d04ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10.
ffffac80`e9c2cec0 fffff801`429d0171 : ffffac80`00000000 fffff801`429d00ae ffffac80`e9c20180 00000000`00000000 : nt!KxMcheckAbort+0x7a.
ffffac80`e9c2d000 fffff801`55ff138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271.
ffffa886`8da2f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f.


SYMBOL_NAME:  intelppm!MWaitIdle+1f.

MODULE_NAME: intelppm.

IMAGE_NAME:  intelppm.sys.

IMAGE_VERSION:  10.0.18362.387.

STACK_COMMAND:  .thread ; .cxr ; kb.

BUCKET_ID_FUNC_OFFSET:  1f.

FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle.

OS_VERSION:  10.0.18362.1.

BUILDLAB_STR:  19h1_release.

OSPLATFORM_TYPE:  x64.

OSNAME:  Windows 10.

FAILURE_ID_HASH:  {d82f1232-e6fd-ac41-d01e-ddeec73b684b}

Followup:     MachineOwner.
---------
 
Son düzenleme:
Gayet tabi RAM ile alakalı olabilir. IntelPPM, Intel Processor Power Management oluyor. RAM uyumsuzluğundan mavi ekran alabilirsiniz. İlk iş BIOS güncellemesi yapın.

Ayrıca sorularınızda sistem özelliklerini yazmayı alışkanlık haline getirin.
Salı gününden beri yeni RAM ile kullanıyorum ilk defa bugün mavi ekran yedim. Herhangi bir değişiklik yapmadım. BIOS sürümü güncel. İlk mesaja sistem özellikleri eklendi.
 
Gayet tabi RAM ile alakalı olabilir. IntelPPM, Intel Processor Power Management oluyor. RAM uyumsuzluğundan mavi ekran alabilirsiniz. İlk iş BIOS güncellemesi yapın.

Ayrıca sorularınızda sistem özelliklerini yazmayı alışkanlık haline getirin.
Geçen hafta yeni sürüm BIOS çıkmış. Bugün gene mavi ekran yedim. En güncel BIOS'u şimdi kurdum. Yarın Windows 10 1909 geçmeyi düşünüyorum. Her zaman bu mavi ekranı yemiyorum. 3-4 günde bir bazen oyun oynarken bazen internette aniden donuyor. Minidump dosyasını aşağıya bırakıyorum.

Google Drive
 
Son düzenleyen: Moderatör:
Son düzenleme:
Sorun devam ediyor mu? PSU da belirtin.

Kod:
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors (If Param 1 is < 0x80000000)
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    AMD64 Processors (If Param 1 is > 0x80000000)
        1 - Failure Type
           VALUES:
                0x80000001: Spurious MCE
                    2 - Address of MCA_EXCEPTION structure
                0x80000002: Rendezvous failure
                    2 - Address of MCA_EXCEPTION structure
           END_VALUES
Arguments:
Arg1: 0000000000000000
Arg2: ffffda8016e2ccd0
Arg3: 0000000000000000
Arg4: 0000000000000000

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

*** WARNING: Unable to verify timestamp for intelppm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-NG9H4F5

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 70

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  9c

BUGCHECK_P1: 0

BUGCHECK_P2: ffffda8016e2ccd0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

BAD_STACK_POINTER:  ffffda8016e2cc98

STACK_TEXT: 
ffffda80`16e2cc98 fffff805`1c1a69f1 : 00000000`0000009c 00000000`00000000 ffffda80`16e2ccd0 00000000`00000000 : nt!KeBugCheckEx
ffffda80`16e2cca0 fffff805`1c1a6f7d : 00000000`00000006 ffffda80`16e2d010 00000000`00000000 00000000`00000000 : hal!HalpMcaReportError+0x11d
ffffda80`16e2ce00 fffff805`1c1a5fc8 : 00000000`00000000 ffffda80`16e2d090 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x131
ffffda80`16e2ce30 fffff805`1c1a71a7 : ffff9402`4c6b6a50 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffda80`16e2ce60 fffff805`1c4a4a20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffda80`16e2ce90 fffff805`1c3d04ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffda80`16e2cec0 fffff805`1c3d0171 : ffffda80`00000000 fffff805`1c3d00ae ffffda80`16e20180 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffda80`16e2d000 fffff805`2eb2138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x271
ffffa901`7242f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x138f


SYMBOL_NAME:  intelppm+138f

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  138f

FAILURE_BUCKET_ID:  0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6cccc12e-99c3-bc39-df8f-272aa5582733}

Followup:     MachineOwner
---------
 
Uyarı! Bu konu 6 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Yeni konular

Geri
Yukarı