ASUS ROG SCAR 18 G834JY i9 13980HX RTX 4090 laptopta mavi ekran hatası

P

ProPat

Uzman
Katılım
28 Eylül 2024
Mesajlar
67
Beğeniler
18
ASUS ROG SCAR 18 G834JY 13980HX RTX 4090 laptopta mavi ekran alıyorum açılışlarda bile. Yardımcı olursanız sevinirim. Laptop format ekranında. Normal açılışlarda bile mavi ekran yiyor. Başka cihaza takıp RAM'leri ve SSD'leri test ettim, sağlamlar.
 

Dosya Ekleri

Tarihe göre sırala Puana göre sırala
O zaman sürekli mavi ekran yiyorsa SSD bozuk. Benim de başıma geldi degistir düzelir.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
yusufumm07 dedi:
O zaman sürekli mavi ekran yiyorsa SSD bozuk. Benim de başıma geldi degistir düzelir.
Genişletmek için tıkla...

Hayır değil. SSD'i sağlam. Çok fazla SSD denedim ama hep mavi ekran yiyor cihaz.

DarkRage dedi:
Başka cihazda sorunsuz çalışıyor dedi.
Genişletmek için tıkla...

Evet öyle dedim. Benim cihaz aşırı bir sorun var.

Birisi minidump dosyalarını gözden geçirsin belki sorunu bulursunuz.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Kod: 
BUGCHECK_CODE:  c000021a
Arguments:
Arg1: ffffd20cd5b564a0
Arg2: ffffffffc000001d, Error Code

Kod: 
BUGCHECK_CODE:  d1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL)Faulting.IP.Type: Null2: kd> rrip=fffff802e84f6bb0 ...iopl=0         nv up di ng nz na po nc

Kod: 
STACK_TEXT:
...
ffffca0f`a3e22610 ... nt!VslLoadEnclaveModule+0xc8
ffffca0f`a3e21d58 ... nt!MI_READ_PTE_LOCK_FREE

CPU gitmiş, geçmiş olsun. Piyango vurmuş.

@Recep Baltaş Garanti bitmiş olsa bile, Asus bu işlemci sorununu zamanında kabul ettiği için "Ayıplı mal" kategorisine girebilir diye düşünüyorum. BIOS güncel olmasına rağmen yaşanmış çünkü. Şansınızı deneyin @ProPat
 
Artı 0 Eksi
@ProPat, son durum nedir?

Kod: 
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000014`7e7ac018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8019ae658c0, Address of the instruction which caused the BugCheck
Arg3: ffffba002cefc8d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 718

    Key  : Analysis.Elapsed.mSec
    Value: 741

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.28000.2114

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!MI_READ_PTE_LOCK_FREE

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8019ae658c0

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x2658c0

    Key  : Failure.Hash
    Value: {46795dd4-7dde-8cf0-b2ba-3f69fbe2847b}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: PRCBException

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8019ae658c0

BUGCHECK_P3: ffffba002cefc8d0

BUGCHECK_P4: 0

FILE_IN_CAB:  092325-8109-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff848ab68b1080

CONTEXT:  ffffba002cefc8d0 -- (.cxr 0xffffba002cefc8d0)
.cxr 0xffffba002cefc8d0
rax=ffffca0fa3e21dc0 rbx=0000000000000080 rcx=fffffc81032f9a18
rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff8019ae658c0 rsp=ffffca0fa3e21d58 rbp=ffffca0fa3e21e60
 r8=fffffffffffffff0  r9=ffffca0fa3e21dfc r10=fffffc8000000000
r11=0000000000000001 r12=ffffca0fa3e21f60 r13=fffffc81032f9a18
r14=0000000000000000 r15=ffffca0fa3e221e0
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050287
nt!MI_READ_PTE_LOCK_FREE:
fffff801`9ae658c0 4883ec28        sub     rsp,28h
.cxr
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  lsass.exe

STACK_TEXT: 
ffffca0f`a3e21d58 fffff801`9ae48543     : ffff848a`00000002 ffffca0f`00000000 ffffffff`ffffffff ffff848a`b68b0480 : nt!MI_READ_PTE_LOCK_FREE
ffffca0f`a3e21d60 fffff801`9af85464     : ffff848a`b68b0480 ffffca0f`a3e22000 00000000`00000002 fffffc80`00000000 : nt!MiResolveDemandZeroFault+0x57
ffffca0f`a3e21f00 fffff801`9ae2d933     : 00000206`5f343000 fffff801`00000004 00000000`00001000 ffff848a`b68b0080 : nt!MiDispatchFault+0x210
ffffca0f`a3e22050 fffff801`9b5ce511     : 00000000`00000000 00000000`00000000 00000000`00000000 b0400000`01080a61 : nt!MmAccessFault+0x183
ffffca0f`a3e221c0 fffff801`9b5ce149     : ffffca0f`a3e226a0 00000000`00000000 00000000`0090152d 0000003f`ffffff4e : nt!MmVirtualAccessFault+0xc5
ffffca0f`a3e22270 fffff801`9ae11ea0     : ffff57c2`77cecb31 ffffffff`ffffffff ffff848a`b68b1080 fffffcfe`7283e8f8 : nt!PspIumResolveVirtualFault+0xad
ffffca0f`a3e22300 fffff801`9ae13778     : fffff801`9bb8cca0 ffffca0f`a3e226a0 00000000`00000001 00000000`00000000 : nt!PsDispatchIumService+0x12c
ffffca0f`a3e22550 fffff801`9b58ce3c     : ffffca0f`a3e22650 ffff848a`b4ce16b0 ffffca0f`a3e22710 ffff848a`00000000 : nt!VslpEnterIumSecureMode+0x3a8
ffffca0f`a3e22610 fffff801`9b58c782     : ffff948d`aef2fed0 ffff848a`b56dec40 00000000`00000000 00000000`00000000 : nt!VslLoadEnclaveModule+0xc8
ffffca0f`a3e22750 fffff801`9b58bd49     : ffff848a`b68b0080 ffffca0f`a3e22900 ffff948d`af190470 ffffca0f`a3e229c8 : nt!MiLoadSectionIntoVsmEnclave+0x252
ffffca0f`a3e22810 fffff801`9b286655     : 00000000`00000000 00000000`0000000b 00000000`00000000 00000000`00000000 : nt!NtLoadEnclaveData+0x389
ffffca0f`a3e229b0 00007ffe`a7dc0fd4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000014`7e58e9c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a7dc0fd4


SYMBOL_NAME:  nt!MI_READ_PTE_LOCK_FREE+0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.1742

STACK_COMMAND: .cxr 0xffffba002cefc8d0 ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  AV_nt!MI_READ_PTE_LOCK_FREE

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {46795dd4-7dde-8cf0-b2ba-3f69fbe2847b}

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

Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000a2`64d02018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WINLOGON_FATAL_ERROR (c000021a)
The Winlogon process terminated unexpectedly.
Arguments:
Arg1: ffffd20cd5b564a0, String that identifies the problem.
Arg2: ffffffffc000001d, Error Code.
Arg3: 0000000000000000
Arg4: 0000029474a80000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1125

    Key  : Analysis.Elapsed.mSec
    Value: 1146

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.28000.2114

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xc000021a

    Key  : Bugcheck.Code.TargetModel
    Value: 0xc000021a

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xc000021a_SmpDestroyControlBlock_smss.exe_Terminated_c000001d_nt!PopTransitionSystemPowerStateEx

    Key  : Failure.Hash
    Value: {d1898f46-5905-ff30-1f3b-c814f83f95fc}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  c000021a

BUGCHECK_P1: ffffd20cd5b564a0

BUGCHECK_P2: ffffffffc000001d

BUGCHECK_P3: 0

BUGCHECK_P4: 29474a80000

FILE_IN_CAB:  092325-8281-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error}  The %hs system process terminated unexpectedly with a status of 0x

EXCEPTION_CODE_STR:  c000021a

EXCEPTION_PARAMETER1:  ffffd20cd5b564a0

EXCEPTION_PARAMETER2:  ffffffffc000001d

EXCEPTION_PARAMETER3:  0000000000000000

EXCEPTION_PARAMETER4: 29474a80000

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe50175668080

PROCESS_NAME:  smss.exe

ADDITIONAL_DEBUG_TEXT:  initial session process or

IMAGE_NAME:  ntkrnlmp.exe

MODULE_NAME: nt

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
fffff605`8cc2f4f8 fffff807`c371ad11     : 00000000`0000004c 00000000`c000021a fffff605`8e30f310 ffffe501`82e5d110 : nt!KeBugCheckEx
fffff605`8cc2f500 fffff807`c372b4cd     : ffffffff`ffffffff fffff605`8cc2f619 ffffffff`80000658 00000000`00000000 : nt!PopGracefulShutdown+0x2d9
fffff605`8cc2f560 fffff807`c370a1e0     : 00000000`00000001 fffff807`00000000 00000000`00000000 00000000`00000000 : nt!PopTransitionSystemPowerStateEx+0x895
fffff605`8cc2f680 fffff807`c365cc8d     : 00000000`00000047 00000000`ffffff00 ffffe501`75668080 fffff605`8cc2f8d0 : nt!PopTransitionSystemPowerState+0x4c
fffff605`8cc2f830 fffff807`c365c850     : 00000000`00000000 ffffe501`00000005 00000000`00000004 00000000`c0000004 : nt!PopIssueActionRequest+0x2a9
fffff605`8cc2f8d0 fffff807`c305952e     : 00000000`00000001 00000000`00000000 00000000`ffffffff ffffe501`755f4aa0 : nt!PopPolicyWorkerAction+0x80
fffff605`8cc2f950 fffff807`c2f09e32     : ffffe501`00000000 ffffe501`75668080 fffff605`8cc2fa80 ffffe501`755f4aa0 : nt!PopPolicyWorkerThread+0x7e
fffff605`8cc2f980 fffff807`c305904a     : ffffe501`75668080 ffffe501`75668080 fffff807`c2f09c80 ffffe501`755f4aa0 : nt!ExpWorkerThread+0x1b2
fffff605`8cc2fb30 fffff807`c32741c4     : ffff8381`f2108180 ffffe501`75668080 fffff807`c3058ff0 0078b841`0000441f : nt!PspSystemThreadStartup+0x5a
fffff605`8cc2fb80 00000000`00000000     : fffff605`8cc30000 fffff605`8cc29000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!PopTransitionSystemPowerStateEx+895

IMAGE_VERSION:  10.0.26100.1742

STACK_COMMAND: .process /r /p 0xffffe501754c7040; .thread 0xffffe50175668080 ; kb

BUCKET_ID_FUNC_OFFSET:  895

FAILURE_BUCKET_ID:  0xc000021a_SmpDestroyControlBlock_smss.exe_Terminated_c000001d_nt!PopTransitionSystemPowerStateEx

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d1898f46-5905-ff30-1f3b-c814f83f95fc}

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

Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols

Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000b7, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 890

    Key  : Analysis.Elapsed.mSec
    Value: 883

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.28000.2114

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Bugcheck.Code.TargetModel
    Value: 0xd1

    Key  : Failure.Bucket
    Value: DISABLED_INTERRUPT_FAULT_CODE_AV_nt!KiPageFault

    Key  : Failure.Hash
    Value: {22523384-75ca-2e7e-4899-20e7e5aa6dea}

    Key  : Faulting.IP.Type
    Value: Null

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: b7

BUGCHECK_P4: 0

FILE_IN_CAB:  111124-6453-01.dmp

FAULTING_THREAD:  ffffdf852673c280

PROCESS_NAME:  System

ADDITIONAL_DEBUG_TEXT:  The fault occurred while interrupts were disabled on the processor.

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

STACK_TEXT: 
ffffef8b`a1a6f758 fffff802`e86b25e9     : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`000000b7 : nt!KeBugCheckEx
ffffef8b`a1a6f760 fffff802`e86ad8a8     : 00000000`00000000 fffff802`e8343543 00000000`00000001 00000000`00000129 : nt!KiBugCheckDispatch+0x69
ffffef8b`a1a6f8a0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdf85`31590000 : nt!KiPageFault+0x468


SYMBOL_NAME:  nt!KiPageFault+468

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.6713

STACK_COMMAND: .process /r /p 0xfffff802e8fcef00; .thread 0xffffdf852673c280 ; kb

BUCKET_ID_FUNC_OFFSET:  468

FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_CODE_AV_nt!KiPageFault

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {22523384-75ca-2e7e-4899-20e7e5aa6dea}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru Soru
ASUS ROG STRIX G614PH mavi ekran hataları
Mesaj
3
Görüntüleme
38
Hasan Merkit
3
  • Soru Soru
ASUS ROG STRIX Scar 16 RTX 5080 laptopta mavi ekran hatası
Mesaj
7
Görüntüleme
188
erkanagri
E
  • Çözüldü
Çözüldü ASUS ROG STRIX Scar 18'de yaşanan çeşitli mavi ekran hataları
5 6 7
Mesaj
69
Görüntüleme
1B
Emirhan Abalı
S
  • Soru Soru
i9-14900KS & RTX 4090 sistemde çeşitli mavi ekran sorunları
2
Mesaj
17
Görüntüleme
293
stormhawks47
H
  • Soru Soru
LiveKernelEvent (117) kodlu mavi ekran hatası
Mesaj
1
Görüntüleme
59
xalvorath
  • Soru Soru
CS2 açıldıktan sonra mavi ekran hatası
Mesaj
6
Görüntüleme
64
anaf
  • Soru Soru
GTX 1070 sistemde oyun esnasında mavi ekran hatası
Mesaj
4
Görüntüleme
170
eternatus
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…