Çözüldü i7-9700K & GTX1070 sistemde mavi ekran hatası

Merhaba,

Dün akşam Windows 11 kurdum sürekli mavi ekran hatası alıyorum. Yardımlarınız için teşekkür ederim.


ASUS ex H310M V3
i7 9700K
16 GB RAM
1070 ekran kartı

Memtest yaptım sorun çıkmadı. Başka neler yapabilirim bilmiyorum

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


Loading Dump File [C:\Users\mdemi\OneDrive\Masaüstü\073123-5703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff805`66c00000 PsLoadedModuleList = 0xfffff805`67813470
Debug session time: Mon Jul 31 18:44:11.359 2023 (UTC + 3:00)
System Uptime: 0 days 18:09:23.030
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`6702b8f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcd80`b96c5af0=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: 0000000080000001
Arg2: ffffcd80b96c5b20
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1625

Key : Analysis.Elapsed.mSec
Value: 3736

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 12

Key : Analysis.Init.CPU.mSec
Value: 140

Key : Analysis.Init.Elapsed.mSec
Value: 10647

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9c

Key : Failure.Bucket
Value: 0x9C_SPURIOUS_GenuineIntel_intelppm!MWaitIdle

Key : Failure.Hash
Value: {1132fd1e-b4e3-34d7-1215-2712eb51da30}

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 9c

BUGCHECK_P1: 80000001

BUGCHECK_P2: ffffcd80b96c5b20

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 073123-5703-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcd80`b96c5ae8 fffff805`670f7b0c : 00000000`0000009c 00000000`80000001 ffffcd80`b96c5b20 00000000`00000000 : nt!KeBugCheckEx
ffffcd80`b96c5af0 fffff805`670f8050 : 00000000`00000008 ffffcd80`b96c5e70 00000000`00000000 81a90233`c45a649f : nt!HalpMcaReportError+0x154
ffffcd80`b96c5c60 fffff805`670f71b2 : 00000000`00000000 00000000`80000001 ffffcd80`b96c5ef0 203105c7`aedf07bf : nt!HalpMceHandlerWithRendezvous+0x11c
ffffcd80`b96c5c90 fffff805`670f997b : ffff8687`f652f800 9163cf01`48636e45 acac7605`ac686863 25ef6dea`c0b1e84b : nt!HalpHandleMachineCheck+0x62
ffffcd80`b96c5cc0 fffff805`6715bf09 : 2d225877`130bc8b3 5ec3201f`18685406 b27baba0`3f583638 02e7efb3`eb724bee : nt!HalHandleMcheck+0x3b
ffffcd80`b96c5cf0 fffff805`6703d73e : 547c2039`e132abf8 3ce1d6a6`8bfdbb35 bd56d803`dcb05264 845f40d2`0e0565c3 : nt!KiHandleMcheck+0x9
ffffcd80`b96c5d20 fffff805`6703d353 : 00000000`00000010 00000000`00000000 00000000`00000002 ffffcd80`b96c5ef0 : nt!KxMcheckAbort+0x7e
ffffcd80`b96c5e60 fffff805`9771156f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
ffff8583`ce047458 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.22621.1918

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f

FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_intelppm!MWaitIdle

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1132fd1e-b4e3-34d7-1215-2712eb51da30}

Followup: MachineOwner
---------



buda şimdi oldu