Çözüldü i9 13900KF RTX 4090 sistem Mavi Ekran hatası (INTELPPM.sys)

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


Loading Dump File [C:\Users\hyozbahce\Desktop\Minidump\021423-3281-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 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`54600000 PsLoadedModuleList = 0xfffff807`5522a290
Debug session time: Tue Feb 14 09:42:31.789 2023 (UTC + 3:00)
System Uptime: 0 days 0:02:07.406
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`549f8fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe181`102da160=000000000000001e
15: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8076d148cc3, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2031

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7832

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  021423-3281-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: fffff8076d148cc3

BUGCHECK_P3: 0

BUGCHECK_P4: 0

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  2444884500000088 -- (.trap 0x2444884500000088)
Unable to read trap frame at 24448845`00000088

STACK_TEXT: 
ffffe181`102da158 fffff807`54af5e5e     : 00000000`0000001e ffffffff`c0000096 fffff807`6d148cc3 00000000`00000000 : nt!KeBugCheckEx
ffffe181`102da160 fffff807`54a01e8f     : fffff807`54af5e3c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffffe181`102da1a0 fffff807`54877a77     : ffffe181`102da710 00000000`00000000 fffffd85`eff0fba0 fffff807`549fcb3e : nt!RtlpExecuteHandlerForException+0xf
ffffe181`102da1d0 fffff807`54876676     : fffffd85`eff0f418 ffffe181`102dae20 fffffd85`eff0f418 ffffbb84`de6e6e80 : nt!RtlDispatchException+0x297
ffffe181`102da8f0 fffff807`549f9e32     : ea8b4d24`1c89490a 850fc33b`48c38b48 24448845`00000088 000e488e`8bd2330c : nt!KiDispatchException+0x186
ffffe181`102dafb0 fffff807`549f9e00     : fffff807`54a0b0a5 00000000`025095dd fffff807`548f7383 ffffbb84`dcf4a010 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffd85`eff0f2d8 fffff807`54a0b0a5     : 00000000`025095dd fffff807`548f7383 ffffbb84`dcf4a010 fffff807`548da078 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffd85`eff0f2e0 fffff807`54a06de0     : 00000000`00000000 fffff807`6d1487f5 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffffd85`eff0f4c0 fffff807`6d148cc3     : fffff807`6d147238 00000000`00000000 fffffd85`eff0f7e0 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffffd85`eff0f658 fffff807`6d147238     : 00000000`00000000 fffffd85`eff0f7e0 00000000`00000000 00000000`00000001 : intelppm!WriteIoMemRaw+0x33
fffffd85`eff0f660 fffff807`54997299     : ffffe181`10280180 ffffe181`10280180 00000000`00000246 fffff807`5493ecbb : intelppm!PerfControlHwp+0x88
fffffd85`eff0f6a0 fffff807`5499710d     : 00000000`00000000 ffffbb84`de6e6e00 ffffbb84`de6e6b40 00000000`00000000 : nt!PpmPerfArbitratorApplyProcessorState+0xe5
fffffd85`eff0f700 fffff807`548d16d7     : ffffbb84`de6e6e40 00000000`00000000 00000000`00000004 fffffd85`eff0f8a0 : nt!PpmPerfApplyProcessorState+0xc1
fffffd85`eff0f770 fffff807`5483489e     : ffffe181`10283240 00000000`00000000 00000000`00000004 ffffe181`10280180 : nt!PpmPerfAction+0x87
fffffd85`eff0f7a0 fffff807`54833b84     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffffd85`eff0f910 fffff807`549fcb3e     : ffffffff`00000000 ffffe181`10280180 ffffe181`1028b840 ffffbb84`d1d92140 : nt!KiRetireDpcList+0x1f4
fffffd85`eff0fba0 00000000`00000000     : fffffd85`eff10000 fffffd85`eff09000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  intelppm!WriteIoMemRaw+33

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

IMAGE_VERSION:  10.0.19041.1865

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  33

FAILURE_BUCKET_ID:  0x1E_C0000096_intelppm!WriteIoMemRaw

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1dcb90a3-8b89-d9a6-beb6-a5edbd6c4995}

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