Your device ran in to problem win11 minidump

klanus388

80+
Katılım
14 Eylül 2025
Mesajlar
1
Reaksiyon skoru
0
merhaba temiz format attım düzelmedi düzzgün ssürücü kurdum düzelmedi bios güncelledddim düzelmedi ram tek tak yaptım düzelmedi lütfen acil yardım minidump bıraktım


************* 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.047 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 45

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


Loading Dump File [C:\Windows\Minidump\091425-7640-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`d4c00000 PsLoadedModuleList = 0xfffff800`d5af4e70
Debug session time: Sun Sep 14 06:16:31.675 2025 (UTC + 3:00)
System Uptime: 0 days 0:33:26.416
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

Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`d50f9280 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcc0c`641b67a0=000000000000000a
9: 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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800d4ef0b22, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1562

Key : Analysis.Elapsed.mSec
Value: 7512

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27920.1001

Key : Analysis.Version.Description
Value: 10.2506.23.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2506.23.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 0x21008

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_nvlddmkm!unknown_function

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

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

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

Key : Failure.Hash
Value: {7eea5677-f68d-2154-717e-887e07e55cd3}

Key : WER.System.BIOSRevision
Value: 5.19.0.0


BUGCHECK_CODE: a

BUGCHECK_P1: 8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff800d4ef0b22

FILE_IN_CAB: 091425-7640-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe30ba7b5a440

READ_ADDRESS: fffff800d5bc44c0: 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
0000000000000008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcc0c`641b6798 fffff800`d52b39e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffcc0c`641b67a0 fffff800`d52aeca8 : fffff780`00000300 00000008`00000000 ffffe30b`a6af12c8 fffff800`7f41c677 : nt!KiBugCheckDispatch+0x69
ffffcc0c`641b68e0 fffff800`d4ef0b22 : 00000000`00000000 ffffcc0c`641b6b78 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x468
ffffcc0c`641b6a70 fffff800`d4ef099a : 00000000`00000000 ffffe30b`00000001 ffffe30b`00000004 ffffcc0c`641b6b78 : nt!KeReleaseMutantEx+0x172
ffffcc0c`641b6b40 fffff800`7fddc2d0 : ffffe30b`a6af12c8 00000000`00000000 00000000`00000000 ffffcc0c`641b7200 : nt!KeReleaseMutex+0x2a
ffffcc0c`641b6b70 ffffe30b`a6af12c8 : 00000000`00000000 00000000`00000000 ffffcc0c`641b7200 00000000`00000000 : nvlddmkm+0x163c2d0
ffffcc0c`641b6b78 00000000`00000000 : 00000000`00000000 ffffcc0c`641b7200 00000000`00000000 00000000`00000000 : 0xffffe30b`a6af12c8


SYMBOL_NAME: nvlddmkm+163c2d0

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffe30b976d2040; .thread 0xffffe30ba7b5a440 ; kb

BUCKET_ID_FUNC_OFFSET: 163c2d0

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner
---------
 
Yeni mesajlar Yeni Konu Aç  

   

SON KONULAR

Forum istatistikleri

Konular
1,169,537
Mesajlar
10,541,517
Üyeler
185,759
Son üye
gılgameş
Geri
Top