furkanshn0
Femtopat
- Katılım
- 22 Şubat 2025
- Mesajlar
- 8
Daha fazla
- Cinsiyet
- Erkek
- RAM
- Kingston Beast 5600mt/s ddr5 cl36 32x2 64gb
- SSD veya HDD modeli
- Kingston KC3000
- Ekran kartı
- MSI Gaming X 3060
- Anakart
- Colorful battle-ax b760m-plus v20
- İşlemci
- Intel i5 14600KF
Öncelikle merhaba abilerim, kardeşlerim mavi ekrandan hatasından dolayı kriz geçirmek üzereyim PC dizeli 3-4 ay oldu ve yeni olarak 2 gündür sürekli devamlı ortalama 10 - 15 dakikada bir Battlefield 1 oyununu oynarken(AFK kaldığında herhangi bir şey olmuyor) mavi ekran alıyorum. Minidump raporunu ekledim yardımcı olur musunuz? Sürücüler güncel Windows güncel BIOS güncel SFC /scannow gibi testler yapılı. Uzun bir süre dump dosyasınıda alamadım mavi ekrana düştükten sonra donup kalıyordu. Otomatik yeniden başlatmayı kapatınca %100 olduktan sonra kendim yeniden başlatıp denedim o zaman dump dosyası oluştu. Ayrıca her mavi ekranda sistem olay görüntüleyiciye düşen hataları da ekledim. PNG dosyasında 00:45 ve 00:48 arasındaki olayları ekledim 00:47 da mavi ekran aldım, dump dosyasını WinDbg ile incelediğimde ise kod satırına eklediğim bilgiyi aldım.
dump dosyası
dump dosyası
Kod:
************* 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: 42.
Microsoft (R) Windows Debugger Version 10.0.27725.1000 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Furkan\Desktop\022225-7437-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 (20 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`3d400000 PsLoadedModuleList = 0xfffff805`3e02a830
Debug session time: Sat Feb 22 01:12:38.205 2025 (UTC + 3:00)
System Uptime: 0 days 0:12:19.805
Loading Kernel Symbols.
...............................................................
................................................................
................................................................
Loading User Symbols.
Unable to read LDR_DATA_TABLE_ENTRY at 00000000`00468300 - Win32 error 0n30.
Loading unloaded module list.
........
WARNING: .reload failed, module list may be incomplete.
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`3d7fe720 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9386`fbd06450=000000000000001e
0: 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: ffffffffc0000005, The exception code that was not handled.
Arg2: fffff80542068559, The address that the exception occurred at.
Arg3: 0000000000000000, Parameter 0 of the exception.
Arg4: ffffffffffffffff, 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1218.
Key : Analysis.Elapsed.mSec
Value: 1248.
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: 6918.
Key : Analysis.Memory.CommitPeak.Mb
Value: 91.
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre.
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e.
Key : Bugcheck.Code.TargetModel
Value: 0x1e.
Key : Failure.Bucket
Value: AV_R_nt!KiDispatchException
Key : Failure.Hash
Value: {36796e09-312c-3519-a508-ce00ff2df497}
Key : Hypervisor.Enlightenments.Value
Value: 68673420.
Key : Hypervisor.Enlightenments.ValueHex
Value: 417df8c.
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: 21631230.
Key : Hypervisor.Flags.ValueHex
Value: 14a10fe.
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.
Key : WER.OS.Branch
Value: vb_release.
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e.
BUGCHECK_P1: ffffffffc0000005.
BUGCHECK_P2: fffff80542068559.
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff.
FILE_IN_CAB: 022225-7437-01.dmp
FAULTING_THREAD: ffffaf0aeb7a3080.
EXCEPTION_PARAMETER1: 0000000000000000.
EXCEPTION_PARAMETER2: ffffffffffffffff.
READ_ADDRESS: fffff8053e0fb390: 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
ffffffffffffffff.
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: bf1.exe
STACK_TEXT:
ffff9386`fbd06448 fffff805`3d87e721 : 00000000`0000001e ffffffff`c0000005 fffff805`42068559 00000000`00000000 : nt!KeBugCheckEx
ffff9386`fbd06450 fffff805`3d8130ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1447b1
ffff9386`fbd06b10 fffff805`3d80e4ef : ffff9386`fbd06de1 fffff805`3d64b241 ffffaf0a`db010340 ffffaf0a`db010ac0 : nt!KiExceptionDispatch+0x12c
ffff9386`fbd06cf0 fffff805`42068559 : ffff9386`fbd06ea0 00000000`5cc2ccb0 ffffaf0a`eab6b630 00000000`00000001 : nt!KiGeneralProtectionFault+0x32f
ffff9386`fbd06e80 ffff9386`fbd06ea0 : 00000000`5cc2ccb0 ffffaf0a`eab6b630 00000000`00000001 ffff9386`fbd06ec0 : 0xfffff805`42068559
ffff9386`fbd06e88 00000000`5cc2ccb0 : ffffaf0a`eab6b630 00000000`00000001 ffff9386`fbd06ec0 00000018`ffffffff : 0xffff9386`fbd06ea0
ffff9386`fbd06e90 ffffaf0a`eab6b630 : 00000000`00000001 ffff9386`fbd06ec0 00000018`ffffffff 00000000`00000000 : 0x5cc2ccb0.
ffff9386`fbd06e98 00000000`00000001 : ffff9386`fbd06ec0 00000018`ffffffff 00000000`00000000 00000000`00000000 : 0xffffaf0a`eab6b630
ffff9386`fbd06ea0 ffff9386`fbd06ec0 : 00000018`ffffffff 00000000`00000000 00000000`00000000 1cffeefa`2bff52fb : 0x1.
ffff9386`fbd06ea8 00000018`ffffffff : 00000000`00000000 00000000`00000000 1cffeefa`2bff52fb a4ff70fa`2dffabfa : 0xffff9386`fbd06ec0
ffff9386`fbd06eb0 00000000`00000000 : 00000000`00000000 1cffeefa`2bff52fb a4ff70fa`2dffabfa c2003ffa`2f005ffa : 0x00000018`ffffffff
SYMBOL_NAME: nt!KiDispatchException+1447b1
MODULE_NAME: nt.
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.5486
STACK_COMMAND: .process /r /p 0xffffaf0aec539340; .thread 0xffffaf0aeb7a3080 ; kb.
BUCKET_ID_FUNC_OFFSET: 1447b1.
FAILURE_BUCKET_ID: AV_R_nt!KiDispatchException
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release.
OSPLATFORM_TYPE: x64.
OSNAME: Windows 10.
FAILURE_ID_HASH: {36796e09-312c-3519-a508-ce00ff2df497}
Followup: MachineOwner.
---------Dosya Ekleri
Son düzenleyen: Moderatör:
