ntoskrnl.exe+6b2be9 hatası alıyorum sürekli mavi ekran sorunu yaşıyorum

Question

ntoskrnl.exe+6b2be9 hatası alıyorum sürekli mavi ekran sorunu yaşıyorum

Mübin Atmaca 0

minidup analizi şu şekilde;

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToChakraJsProvider : false

-- 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.031 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64

Loading Dump File [C:\Windows\Minidump\111625-29093-01.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 26100 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff8039d400000 PsLoadedModuleList = 0xfffff8039e2f4e70

Debug session time: Sun Nov 16 01:22:36.997 2025 (UTC + 3:00)

System Uptime: 0 days 1:02:14.989

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

PEB is paged out (Peb.Ldr = 00000096`0306d018). Type ".hh dbgerr001" for details

Loading unloaded module list

..........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff8039d8f9280 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff3813e572130=0000000000000050

3: kd> !analyze -v

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

PEB is paged out (Peb.Ldr = 00000096`0306d018). Type ".hh dbgerr001" for details

Loading unloaded module list

..........

                   Bugcheck Analysis                                    *

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: fffffffff37e59b8, memory referenced.

Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.

bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the processor decided the fault was due to a corrupted PTE.

bit 4 is set if the fault was due to attempted execute of a no-execute PTE.

- ARM64: bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the fault was due to attempted execute of a no-execute PTE.

Arg3: fffff8039dd21c62, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000002, (reserved)

Debugging Details:

KEY_VALUES_STRING: 1

Key  : AV.Type

Value: Read

Key  : Analysis.CPU.mSec

Value: 1781

Key  : Analysis.Elapsed.mSec

Value: 3604

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 24

Key  : Analysis.Init.CPU.mSec

Value: 1359

Key  : Analysis.Init.Elapsed.mSec

Value: 73559

Key  : Analysis.Memory.CommitPeak.Mb

Value: 109

Key  : Analysis.Version.DbgEng

Value: 10.0.29457.1000

Key  : Analysis.Version.Description

Value: 10.2506.23.01 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2506.23.1

Key  : Bugcheck.Code.LegacyAPI

Value: 0x50

Key  : Bugcheck.Code.TargetModel

Value: 0x50

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_R_(null)_nt!ExpSnapShotHandleTables

Key  : Failure.Exception.IP.Address

Value: 0xfffff8039dd21c62

Key  : Failure.Exception.IP.Module

Value: nt

Key  : Failure.Exception.IP.Offset

Value: 0x921c62

Key  : Failure.Hash

Value: {5d65072c-590a-4c6b-c58a-855eaa942cfa}

Key  : Hypervisor.Enlightenments.ValueHex

Value: 0x7497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent

Value: 1

Key  : Hypervisor.Flags.ApicEnlightened

Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint

Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested

Value: 0

Key  : Hypervisor.Flags.CpuManager

Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi

Value: 0

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: 38408431

Key  : Hypervisor.Flags.ValueHex

Value: 0x24a10ef

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.16.0.0

BUGCHECK_CODE: 50

BUGCHECK_P1: fffffffff37e59b8

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8039dd21c62

BUGCHECK_P4: 2

FILE_IN_CAB: 111625-29093-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffffb2032cc350c0

READ_ADDRESS: fffff8039e3c44c0: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

fffffffff37e59b8

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: League of Lege

STACK_TEXT:

fffff3813e572128 fffff8039d7e265c : 0000000000000050 fffffffff37e59b8 0000000000000000 fffff3813e572390 : nt!KeBugCheckEx

fffff3813e572130 fffff8039d6b5eb0 : 0000000000000001 ffff800000000000 fffffffff37e59b8 0000007ffffffff8 : nt!MiSystemFault+0x7a0

fffff3813e572220 fffff8039daaebcb : 00000008b23d0ed8 fffff3813e572410 ffff8704fb4f3980 000009d5900c9082 : nt!MmAccessFault+0x630

fffff3813e572390 fffff8039dd21c62 : 0000000000000800 0000000000000000 ffff8705206c2518 0000000000000800 : nt!KiPageFault+0x38b

fffff3813e572520 fffff8039dddc969 : 0000000000000000 0000000000000001 fffff37e59a38628 000000000028c000 : nt!ExpSnapShotHandleTables+0x222

fffff3813e5725c0 fffff8039dddb44e : 0000000000000000 00007ffc5566c008 0000000000000010 00000275a6950000 : nt!ExpQuerySystemInformation+0x13b9

fffff3813e572aa0 fffff8039dab3944 : 00000008b23c0000 ffffb2032cc350c0 ffffb2032cc350c0 0000000000000000 : nt!NtQuerySystemInformation+0x3e

fffff3813e572ae0 00000275e3be0014 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExitPico+0x499

00000096036ff568 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00000275`e3be0014

SYMBOL_NAME: nt!ExpSnapShotHandleTables+222

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.6584

STACK_COMMAND: .process /r /p 0xffffb203354a80c0; .thread 0xffffb2032cc350c0 ; kb

BUCKET_ID_FUNC_OFFSET: 222

FAILURE_BUCKET_ID: AV_R_(null)_nt!ExpSnapShotHandleTables

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5d65072c-590a-4c6b-c58a-855eaa942cfa}

Followup: MachineOwner

0 yorum

1 yanıt

Yanıtınız

Answer 1

DaveM121 905.3K Bağımsız Danışman

Lütfen sahip olduğunuz minidump dosyalarını yükleyin. Sistem çökmelerinin olası bir nedeni hakkında bilgi verip vermediklerini kontrol edeceğim.

Windows Dosya Gezgini'ni açın.

C:\Windows\Minidump konumuna gidin.

Minidump dosyalarını masaüstünüze kopyalayın, ardından sıkıştırın.

Zip dosyasını buluta (OneDrive vb.) yükleyin, ardından paylaşmayı seçin ve bir paylaşım bağlantısı alın.

Ardından, sizin için inceleyebilmem için zip dosyasının bağlantısını buraya gönderin.

0 yorum