Çözüldü RDR 2 mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

cll93

Femtopat
Katılım
1 Aralık 2023
Mesajlar
2
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Kod:
************* 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.031 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:\Windows\Minidump\120123-11453-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 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`74800000 PsLoadedModuleList = 0xfffff806`754134a0
Debug session time: Fri Dec 1 00:37:07.319 2023 (UTC + 3:00)
System Uptime: 1 days 4:25:43.100
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 = 00000086`20655018). Type ".hh dbgerr001" for details
Loading unloaded module list
...................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`74c16980 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff509`a0c6e370=000000000000000a
8: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffffd800007528, 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: fffff80674aae5bd, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1234

Key : Analysis.Elapsed.mSec
Value: 6443

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

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!MiWalkVaCheckCommon

Key : Failure.Hash
Value: {18f0f161-6c2c-5db0-d879-b666add2f2f6}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

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

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

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: 3f7


BUGCHECK_CODE: a

BUGCHECK_P1: ffffffd800007528

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80674aae5bd

FILE_IN_CAB: 120123-11453-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

READ_ADDRESS: fffff8067551d470: 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
ffffffd800007528

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RuntimeBroker.

TRAP_FRAME: fffff509a0c6e4b0 -- (.trap 0xfffff509a0c6e4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff509a0c6e6d8 rbx=0000000000000000 rcx=ffff800c574b6740
rdx=fffff73fff1a9e68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80674aae5bd rsp=fffff509a0c6e640 rbp=fffff509a0c6eb00
r8=ffffffd800007500 r9=0000000000000001 r10=0000fffff80674c6
r11=ffffab7e42600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MiWalkVaCheckCommon+0x1d:
fffff806`74aae5bd 480fba632828 bt qword ptr [rbx+28h],28h ds:00000000`00000028=????????????????
Resetting default scope

STACK_TEXT:
fffff509`a0c6e368 fffff806`74c2bfa9 : 00000000`0000000a ffffffd8`00007528 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff509`a0c6e370 fffff806`74c27634 : 00000000`00000003 fffff806`00000000 00000000`00000003 00001f80`00c60038 : nt!KiBugCheckDispatch+0x69
fffff509`a0c6e4b0 fffff806`74aae5bd : ffff6a67`acc2c639 86000004`2e1e2847 00000000`00000001 fffff806`74b03638 : nt!KiPageFault+0x474
fffff509`a0c6e640 fffff806`74c63f67 : fffff509`a0c6eb00 ffffffd8`00007500 00000000`00000000 fffff806`74b035da : nt!MiWalkVaCheckCommon+0x1d
fffff509`a0c6e670 fffff806`74a8a4e6 : fffff509`a0c6eb00 ffff800c`574b6740 fffff73f`ff1a9e68 20294800`00270711 : nt!MiUpdateOldPte+0x87
fffff509`a0c6e6c0 fffff806`74a8a8aa : fffff509`00000000 ffff800c`574b6740 fffff77b`00000000 fffff509`a0c6eb50 : nt!MiWalkPageTablesRecursively+0x266
fffff509`a0c6e750 fffff806`74a8a8aa : fffff509`00000000 ffff800c`574b6740 fffff77b`00000000 fffff509`a0c6eb60 : nt!MiWalkPageTablesRecursively+0x62a
fffff509`a0c6e7e0 fffff806`74a8a8aa : fffff509`a0c6eb00 ffff800c`574b6740 fffff77b`00000000 fffff509`a0c6eb70 : nt!MiWalkPageTablesRecursively+0x62a
fffff509`a0c6e870 fffff806`74a8a181 : fffff806`00000000 ffff800c`574b6740 ffff800c`00000000 fffff509`a0c6eb80 : nt!MiWalkPageTablesRecursively+0x62a
fffff509`a0c6e900 fffff806`74e3365c : fffff509`a0c6eb00 00000000`00000001 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x371
fffff509`a0c6ea00 fffff806`7517bd5d : ffff800c`5258d0c0 fffff509`00002000 00000000`00000000 00000000`00000008 : nt!MmUpdateOldWorkingSetPages+0x1a0
fffff509`a0c6ed30 fffff806`750dc53f : ffff800c`574b60c0 0000004f`ed07d0a8 00000000`00000000 00000000`00000000 : nt!PfpDeprioritizeOldPagesInWs+0x121
fffff509`a0c6eda0 fffff806`74f4f6f0 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`00000001 : nt!PfSetSuperfetchInformation+0x18c56b
fffff509`a0c6ee90 fffff806`74c2b6e8 : ffff800c`526670c0 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!NtSetSystemInformation+0x280
fffff509`a0c6f460 00007ffe`9b312a84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000004f`ed07d068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`9b312a84


SYMBOL_NAME: nt!MiWalkVaCheckCommon+1d

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.2715

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1d

FAILURE_BUCKET_ID: AV_nt!MiWalkVaCheckCommon

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {18f0f161-6c2c-5db0-d879-b666add2f2f6}

Followup: MachineOwner
---------
DMP dosyası bu şekilde sistemi yeni topladım neden kaynaklı bu hatayı veriyor acaba ?
 
Çözüm
Problemi çözdüm teşekkür ederim. AMD Adrenalin hata verdiği için böyle bir sorun yaşıyormuşum. Adrenalini ve drivere silip only driver yuklemesi yaptım şu anda bir sorun yok.

Burada paylaşın, kendiniz buraya okuyup copy paste şekilde atmayın.
 
Problemi çözdüm teşekkür ederim. AMD Adrenalin hata verdiği için böyle bir sorun yaşıyormuşum. Adrenalini ve drivere silip only driver yuklemesi yaptım şu anda bir sorun yok.
 
Son düzenleyen: Moderatör:
Çözüm

Technopat Haberler

Yeni konular

Geri
Yukarı