Çözüldü Mavi ekran hatası

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

erhanuyysal

Kilopat
Katılım
22 Mart 2014
Mesajlar
26
Yer
İstanbul
Daha fazla  
Cinsiyet
Erkek
Meslek
Mimar
Tam olarak ne oldu bilmiyorum. PC'yi tka bilişime temizlik için verdim. Öncesinde hiç mavi ekran almamıştım. Yani son formatım üzerinden 1buçuk sene rahat geçmiştir. Kontrolsüz hiçbir yükleme indirme yapmadım vs. arada bir elektrik gider ayda 1 2 yakalanırım böyle. UPS yok. Akım korumalı priz var. Neyse temizliğinden memnun değilim firmanın, kompresör tutup bırakmış gibiler ama ok geri aldım. Sorun onlardan kaynakladır demiyorum. Tüm süreci bilin istedim. 1-2 gün herhangi bir sorun olmadı. Sonra olaylar başladı.

Sorun olmayan 2 günlük ara süreçte şöyle bir yükleme geçmişim var:

Cloudflare WARP (VPN)
FACEIT ve FACEIT anticheat (CS2 için)
Dragon Center (MSI donanım izleyicisi)
Ryzen Master.
Windows'un telefon bağlantısı uygulaması (anakartta Bluetooth yok harici USB aygıt aldım TP-Link)
Belki 1 2 Win güncelleme ama emin değilim kontrol etmiyorum sürekli.

Sonra bir güncelleme yüklendi, Win yeniden başlatma istiyor bildirimi geldi. Ben işime devam ettim en son hallederiz diye. Ardından TPM 2.0 ile ilgili bir hata aldım. Bu sırada PC in Windows 11'e uygun değildir bildirimi vs geldi. Önemsemedim yine. PC'yi kapatırken de güncelleştir kapat dedim ve hikaye başladı.

Bir daha PC'yi tekrar açabilmek kabus oldu. Aklınıza gelebilecek tüm mavi ekran hatalını aldım herhalde. Aklımda kalanları yazıyorum:

-SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
-KERNEL_SECURITY_CHECK_FAILURE
-CRITICAL_PROCESS_DIED
-Process1 ınıtıalızatıon faıled.
-PAGE_FAULT_IN_NONPAGED_AREA (bu geldiğinde bazen " başarısız: Ntfs.sys " hatası da aldım ek olarak)
-0xc000007b
-0xc00021A
-Bir keresinde direk ekran mavi kaldı. Hata kodu falan yok. Mavi böyle :D

Arada açabildim bir kez. SSD'lerden şüphelendim. Acaba dedim bad sector mü var kontrol ettim. Windows kurulu olanda yazmada problem olduğunu gördüm. Normalde 4-5000 bin arası olması gerekirken benimki 1100mb/s yazıyor. Buna da ayrı başlık açtım pek takan olmadı. SSD Mevzusu neyse sonra yedeklemelerimi yapıp kapattım. Tekrar açmayı denedim aynı problemler devam etti. Açamadım yine bir süre. Sonra RAM'lerden iki tanesini söktüm ve PC açıldı. :)

Ama tüm hataların RAM kaynaklı olup olmadığı konusunda emin değilim. Memory dump verdi ama 1.15 GB. İlk defa bu kadar büyük dump gördüm. Onu buraya nasıl yüklerim bilmiyorum. Yardımcı olabilecek varsa Drive'dan atayım.
 
Çözüm
181951
Rich (BB code): 
13: kd>
 InstancePath is "ACPI\AuthenticAMD_-_AMD64_Family_23_Model_113_-_AMD_Ryzen_9_3900X_12-Core_Processor____________\_e"
 ServiceName is "AmdPPM"
Rich (BB code): 
13: kd> !irp
Irp is active with 3 stacks 2 is current (= 0xffff8a0595153b48)
 No Mdl: No System Buffer: Thread ffff8a059420e280:  Irp stack trace.
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 e0 ffff8a05891e5d40 00000000 00000000-00000000
           \Driver\ACPI
            Args: 00000000 00000000 00000000 00000000
 [IRP_MJ_PNP(1b), IRP_MN_START_DEVICE(0)]
            0 e1 ffff8a0594c8f2d0 00000000 fffff80262f6d5b0-ffff8a05939682a0 Success Error Cancel pending
           \Driver\AmdPPM    nt!PnpDeviceCompletionRoutine
            Args: 00000000 00000000 00000000 00000000

Hataya sebep olan ana şey işlemcin. Ek olarak aşağıdaki sürücüler de problemli.

Rich (BB code): 
*** WARNING: Unable to verify timestamp for FACEIT_AC.sys x2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for logi_joy_xlcore.sys

İşlemcini kontrol et, temizlik sonrası fanı çok sıkılmış olabilir. Gevşet biraz. Ekran kartı sürücünü güncelle ve Logitech araçlarını kaldır. FACEIT'e de giriyorsun sanırım.

Ekleme yapıyorum, Dosyanda disk ile ilişkili çağrılar da mevcut.
Tarihe göre sırala Puana göre sırala
erhanuyysal dedi:
Tam olarak ne oldu bilmiyorum. PC'yi tka bilişime temizlik için verdim. Öncesinde hiç mavi ekran almamıştım. Yani son formatım üzerinden 1buçuk sene rahat geçmiştir. Kontrolsüz hiçbir yükleme indirme yapmadım vs. arada bir elektrik gider ayda 1 2 yakalanırım böyle. UPS yok. Akım korumalı priz var. Neyse temizliğinden memnun değilim firmanın, kompresör tutup bırakmış gibiler ama ok geri aldım. Sorun onlardan kaynakladır demiyorum. Tüm süreci bilin istedim. 1-2 gün herhangi bir sorun olmadı. Sonra olaylar başladı.

Sorun olmayan 2 günlük ara süreçte şöyle bir yükleme geçmişim var:

Cloudflare WARP (VPN)
FACEIT ve FACEIT anticheat (CS2 için)
Dragon Center (MSI donanım izleyicisi)
Ryzen Master.
Windows'un telefon bağlantısı uygulaması (anakartta Bluetooth yok harici USB aygıt aldım TP-Link)
Belki 1 2 Win güncelleme ama emin değilim kontrol etmiyorum sürekli.

Sonra bir güncelleme yüklendi, Win yeniden başlatma istiyor bildirimi geldi. Ben işime devam ettim en son hallederiz diye. Ardından TPM 2.0 ile ilgili bir hata aldım. Bu sırada PC in Windows 11'e uygun değildir bildirimi vs geldi. Önemsemedim yine. PC'yi kapatırken de güncelleştir kapat dedim ve hikaye başladı.

Bir daha PC'yi tekrar açabilmek kabus oldu. Aklınıza gelebilecek tüm mavi ekran hatalını aldım herhalde. Aklımda kalanları yazıyorum:

-SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
-KERNEL_SECURITY_CHECK_FAILURE
-CRITICAL_PROCESS_DIED
-Process1 ınıtıalızatıon faıled.
-PAGE_FAULT_IN_NONPAGED_AREA (bu geldiğinde bazen " başarısız: Ntfs.sys " hatası da aldım ek olarak)
-0xc000007b
-0xc00021A
-Bir keresinde direk ekran mavi kaldı. Hata kodu falan yok. Mavi böyle :D

Arada açabildim bir kez. SSD'lerden şüphelendim. Acaba dedim bad sector mü var kontrol ettim. Windows kurulu olanda yazmada problem olduğunu gördüm. Normalde 4-5000 bin arası olması gerekirken benimki 1100mb/s yazıyor. Buna da ayrı başlık açtım pek takan olmadı. SSD Mevzusu neyse sonra yedeklemelerimi yapıp kapattım. Tekrar açmayı denedim aynı problemler devam etti. Açamadım yine bir süre. Sonra RAM'lerden iki tanesini söktüm ve PC açıldı. :)

Ama tüm hataların RAM kaynaklı olup olmadığı konusunda emin değilim. Memory dump verdi ama 1.15 GB. İlk defa bu kadar büyük dump gördüm. Onu buraya nasıl yüklerim bilmiyorum. Yardımcı olabilecek varsa Drive'dan atayım.
Genişletmek için tıkla...
Virüs bulaşmış. CPD Sistem uygulamaların zorla kapatılmasıyla oluşan sonuç Kendim uygulama yaparken deneme yanılma yöntemiyle Ezberlemiştim.
 
Artı 0 Eksi
erhanuyysal dedi:
Yaptım sorun yok gözüküyor. Ama 2 tane ram im takılı değil şuan
Genişletmek için tıkla...
Verilen hatalara göre sistem dosyaları zarar görmüş gibi. Sfc /scannow sistem dosyalarını denetler ve hatalı olanları düzeltir.
 
Artı 0 Eksi
erhanuyysal dedi:
Onu yaptım konu ordan çok uzak. Ama eskisi gibi değil burası onu anladım. Nerdesin ya recep baltas
Genişletmek için tıkla...
Dostum siz minidump paylaşamazsanız burada her kafadan ses duyarsınız. Eğer minidump dosyanız aşırı büyükse kendiniz bakabilirsiniz.
1-Eğer yoksa WinDbg adlı programı yükleyin daha sonra açın.
1711505201693.png

2-Dump dosyanızı buraya sürükleyin.
1711505253527.png

3- "!analyze -v" adlı altı çizili mavi texte tıklayın, ya da prompa kendiniz yazın.
1711505303626.png


Görüldüğü üzere, şimdi analiz edebilirsiniz. Bugcheck Analysis den başlayıp sonuna kadar kopyalayıp buraya atın ne olduğuna bakalım.
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen and saved in
KiBugCheckDriver.
Arguments:
Arg1: fffff80a2d20bee6, memory referenced
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation
Arg3: fffff80a2d20bee6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, Mm internal code.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1921

Key : Analysis.Elapsed.mSec
Value: 3878

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xce

Key : Bugcheck.Code.TargetModel
Value: 0xce

Key : Failure.Bucket
Value: 0xCE_EasyAntiChea!unknown_function

Key : Failure.Hash
Value: {7ef9ddcc-afc0-3e06-b418-78b47b58c1e5}

Key : Hypervisor.Enlightenments.Value
Value: 77057948

Key : Hypervisor.Enlightenments.ValueHex
Value: 497cf9c

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: ce

BUGCHECK_P1: fffff80a2d20bee6

BUGCHECK_P2: 10

BUGCHECK_P3: fffff80a2d20bee6

BUGCHECK_P4: 0

FILE_IN_CAB: 032624-8656-01.dmp

WRITE_ADDRESS: fffff807836fb390: 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
fffff80a2d20bee6

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedgewebview2.exe

TRAP_FRAME: fffffa82d1e4e6e0 -- (.trap 0xfffffa82d1e4e6e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffff13f129c rbx=0000000000000000 rcx=fffff7b80001d908
rdx=fffff80a2c9613a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80a2d20bee6 rsp=fffffa82d1e4e870 rbp=fffffa82d1e4e8d0
r8=fffff7b80001d7b0 r9=0000000000000003 r10=fffff7b80001de88
r11=ffff787d0de00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
<Unloaded_EasyAntiChea>+0xa4bee6:
fffff80a`2d20bee6 ?? ???
Resetting default scope

IP_MODULE_UNLOADED:
EasyAntiChea+a4bee6
fffff80a`2d20bee6 ?? ???

STACK_TEXT:
fffffa82`d1e4e438 fffff807`82e3c22d : 00000000`00000050 fffff80a`2d20bee6 00000000`00000010 fffffa82`d1e4e6e0 : nt!KeBugCheckEx
fffffa82`d1e4e440 fffff807`82c24660 : 00000000`00000000 00000000`00000010 fffffa82`d1e4e760 00000000`00000000 : nt!MiSystemFault+0x1d8dad
fffffa82`d1e4e540 fffff807`82e0d798 : 00000000`00000000 00000000`00000000 fffffa82`d1e4e6e0 00000000`00000000 : nt!MmAccessFault+0x400
fffffa82`d1e4e6e0 fffff80a`2d20bee6 : fffffc43`05606bf8 ffffd209`359a2f90 00000000`00000004 fffff807`82c4ee79 : nt!KiPageFault+0x358
fffffa82`d1e4e870 fffffc43`05606bf8 : ffffd209`359a2f90 00000000`00000004 fffff807`82c4ee79 00000000`00000003 : <Unloaded_EasyAntiChea>+0xa4bee6
fffffa82`d1e4e878 ffffd209`359a2f90 : 00000000`00000004 fffff807`82c4ee79 00000000`00000003 00000000`00000003 : win32kbase!ReleaseUserCritEvent
fffffa82`d1e4e880 00000000`00000004 : fffff807`82c4ee79 00000000`00000003 00000000`00000003 00000000`00000000 : 0xffffd209`359a2f90
fffffa82`d1e4e888 fffff807`82c4ee79 : 00000000`00000003 00000000`00000003 00000000`00000000 fffff807`82c14dd5 : 0x4
fffffa82`d1e4e890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwWriteEx+0x119


SYMBOL_NAME: EasyAntiChea+a4bee6

MODULE_NAME: EasyAntiChea

IMAGE_NAME: EasyAntiChea

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: a4bee6

FAILURE_BUCKET_ID: 0xCE_EasyAntiChea!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7ef9ddcc-afc0-3e06-b418-78b47b58c1e5}

Followup: MachineOwner
---------
 
Artı 0 Eksi
nader11ndeu dedi:
Dostum siz minidump paylaşamazsanız burada her kafadan ses duyarsınız. Eğer minidump dosyanız aşırı büyükse kendiniz bakabilirsiniz.
1-Eğer yoksa WinDbg adlı programı yükleyin daha sonra açın.
Eki Görüntüle 2151701
2-Dump dosyanızı buraya sürükleyin.
Eki Görüntüle 2151702
3- "!analyze -v" adlı altı çizili mavi texte tıklayın, ya da prompa kendiniz yazın.
Eki Görüntüle 2151703

Görüldüğü üzere, şimdi analiz edebilirsiniz. Bugcheck Analysis den başlayıp sonuna kadar kopyalayıp buraya atın ne olduğuna bakalım.
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen and saved in
KiBugCheckDriver.
Arguments:
Arg1: fffff80a2d20bee6, memory referenced
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation
Arg3: fffff80a2d20bee6, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, Mm internal code.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1921

Key : Analysis.Elapsed.mSec
Value: 3878

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xce

Key : Bugcheck.Code.TargetModel
Value: 0xce

Key : Failure.Bucket
Value: 0xCE_EasyAntiChea!unknown_function

Key : Failure.Hash
Value: {7ef9ddcc-afc0-3e06-b418-78b47b58c1e5}

Key : Hypervisor.Enlightenments.Value
Value: 77057948

Key : Hypervisor.Enlightenments.ValueHex
Value: 497cf9c

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: ce

BUGCHECK_P1: fffff80a2d20bee6

BUGCHECK_P2: 10

BUGCHECK_P3: fffff80a2d20bee6

BUGCHECK_P4: 0

FILE_IN_CAB: 032624-8656-01.dmp

WRITE_ADDRESS: fffff807836fb390: 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
fffff80a2d20bee6

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedgewebview2.exe

TRAP_FRAME: fffffa82d1e4e6e0 -- (.trap 0xfffffa82d1e4e6e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffff13f129c rbx=0000000000000000 rcx=fffff7b80001d908
rdx=fffff80a2c9613a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80a2d20bee6 rsp=fffffa82d1e4e870 rbp=fffffa82d1e4e8d0
r8=fffff7b80001d7b0 r9=0000000000000003 r10=fffff7b80001de88
r11=ffff787d0de00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
<Unloaded_EasyAntiChea>+0xa4bee6:
fffff80a`2d20bee6 ?? ???
Resetting default scope

IP_MODULE_UNLOADED:
EasyAntiChea+a4bee6
fffff80a`2d20bee6 ?? ???

STACK_TEXT:
fffffa82`d1e4e438 fffff807`82e3c22d : 00000000`00000050 fffff80a`2d20bee6 00000000`00000010 fffffa82`d1e4e6e0 : nt!KeBugCheckEx
fffffa82`d1e4e440 fffff807`82c24660 : 00000000`00000000 00000000`00000010 fffffa82`d1e4e760 00000000`00000000 : nt!MiSystemFault+0x1d8dad
fffffa82`d1e4e540 fffff807`82e0d798 : 00000000`00000000 00000000`00000000 fffffa82`d1e4e6e0 00000000`00000000 : nt!MmAccessFault+0x400
fffffa82`d1e4e6e0 fffff80a`2d20bee6 : fffffc43`05606bf8 ffffd209`359a2f90 00000000`00000004 fffff807`82c4ee79 : nt!KiPageFault+0x358
fffffa82`d1e4e870 fffffc43`05606bf8 : ffffd209`359a2f90 00000000`00000004 fffff807`82c4ee79 00000000`00000003 : <Unloaded_EasyAntiChea>+0xa4bee6
fffffa82`d1e4e878 ffffd209`359a2f90 : 00000000`00000004 fffff807`82c4ee79 00000000`00000003 00000000`00000003 : win32kbase!ReleaseUserCritEvent
fffffa82`d1e4e880 00000000`00000004 : fffff807`82c4ee79 00000000`00000003 00000000`00000003 00000000`00000000 : 0xffffd209`359a2f90
fffffa82`d1e4e888 fffff807`82c4ee79 : 00000000`00000003 00000000`00000003 00000000`00000000 fffff807`82c14dd5 : 0x4
fffffa82`d1e4e890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!EtwWriteEx+0x119


SYMBOL_NAME: EasyAntiChea+a4bee6

MODULE_NAME: EasyAntiChea

IMAGE_NAME: EasyAntiChea

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: a4bee6

FAILURE_BUCKET_ID: 0xCE_EasyAntiChea!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7ef9ddcc-afc0-3e06-b418-78b47b58c1e5}

Followup: MachineOwner
---------
Genişletmek için tıkla...
Teşekkürler. Dediğinizi yaptım. İnceleyebilirseniz sevinirim.

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
Genişletmek için tıkla...

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
Genişletmek için tıkla...
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Windows\Minidump\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be 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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`62c00000 PsLoadedModuleList = 0xfffff802`6382a730
Debug session time: Tue Mar 26 17:39:02.406 2024 (UTC + 3:00)
System Uptime: 0 days 0:00:08.063
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`62ffd890 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9a0d`871f5d40=000000000000007e
13: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff80262e3c26e, The address that the exception occurred at
Arg3: ffff9a0d871f6d38, Exception Record Address
Arg4: ffff9a0d871f6570, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 4468

Key : Analysis.Elapsed.mSec
Value: 4485

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

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

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

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x7e

Key : Bugcheck.Code.LegacyAPI
Value: 0x7e

Key : Bugcheck.Code.TargetModel
Value: 0x7e

Key : Failure.Bucket
Value: AV_ACPI!ACPIInternalSetDeviceInterface

Key : Failure.Hash
Value: {9bd9af7e-f910-47b2-1678-c208998b66d3}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

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

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

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

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 16908288

Key : Hypervisor.Flags.ValueHex
Value: 1020000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80262e3c26e

BUGCHECK_P3: ffff9a0d871f6d38

BUGCHECK_P4: ffff9a0d871f6570

FILE_IN_CAB: MEMORY.DMP

EXCEPTION_RECORD: ffff9a0d871f6d38 -- (.exr 0xffff9a0d871f6d38)
ExceptionAddress: fffff80262e3c26e (nt!ExFreeHeapPool+0x000000000000021e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffff9a0d871f6570 -- (.cxr 0xffff9a0d871f6570)
rax=0000000000001000 rbx=2990940108e87a17 rcx=ffffaa81d45b5000
rdx=0000000000001000 rsi=ffff9a0d871f7270 rdi=ffff9a0d871f7260
rip=fffff80262e3c26e rsp=ffff9a0d871f6f70 rbp=ffff9a0d871f71b0
r8=ffffaa81d457d000 r9=ffffaa81d457d000 r10=0000000000000000
r11=ffff9a0d871f6f68 r12=0000000000000000 r13=0000000000000ae0
r14=0000000000000000 r15=00000000fffff802
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!ExFreeHeapPool+0x21e:
fffff802`62e3c26e 488b5328 mov rdx,qword ptr [rbx+28h] ds:002b:29909401`08e87a3f=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


PROCESS_NAME: System

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

LOCK_ADDRESS: fffff80263844a80 -- (!locks fffff80263844a80)

Resource @ nt!PiEngineLock (0xfffff80263844a80) Exclusively owned
Contention Count = 3
NumberOfExclusiveWaiters = 1
Threads: ffff8a059420e280-01<*>

Threads Waiting On Exclusive Access:
ffff8a05890f3240
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff80263844a80
Thread Count : 1
Thread address: 0xffff8a059420e280
Thread wait : 0x204

STACK_TEXT:
ffff9a0d`871f6f70 fffff802`635b70b9 : 00000000`00000000 00000000`00000000 fffff802`62c0acf8 01000000`00100000 : nt!ExFreeHeapPool+0x21e
ffff9a0d`871f7050 fffff802`632cb861 : ffff9a0d`871f7128 00000000`00000000 ffffbf04`7d0eb720 ffff9a0d`871f7270 : nt!ExFreePool+0x9
ffff9a0d`871f7080 fffff802`6334287e : 00000000`00000190 ffff8a05`8c516001 00000000`00000000 ffffbf04`00000000 : nt!PnpUnicodeStringToWstrFree+0x2d
ffff9a0d`871f70b0 fffff802`6334247c : ffff9a0d`871f72e0 ffff9a0d`871f7270 ffff8a05`8c516010 00000000`00000001 : nt!IopProcessSetInterfaceState+0x3c2
ffff9a0d`871f71f0 fffff802`656ccece : 00000000`00000000 fffff802`6572f4d0 fffff802`6572f4d0 ffff8a05`95153a30 : nt!IoSetDeviceInterfaceState+0x3c
ffff9a0d`871f7220 fffff802`656ccd91 : 00000000`00000000 ffff8a05`891e5d40 ffff9a0d`871f72e0 ffff8a05`891e5d40 : ACPI!ACPIInternalSetDeviceInterface+0x5e
ffff9a0d`871f7290 fffff802`656ccc63 : ffff8a05`95150000 fffff802`00000012 ffff9a0d`0000000e ffff8a05`95153a30 : ACPI!ACPIProcessorStartDeviceWorker+0x111
ffff9a0d`871f7320 fffff802`656c1262 : 00000000`00000000 ffff8a05`95607830 ffff8a05`95153a30 fffff802`65634230 : ACPI!ACPIProcessorStartDevice+0x33
ffff9a0d`871f7350 fffff802`62e35cf5 : 00000000`00000007 ffff8a05`95607830 00000000`00000000 00000000`00000000 : ACPI!ACPIDispatchIrp+0x252
ffff9a0d`871f73d0 fffff802`65633cb0 : ffff8a05`95607830 00000000`00000000 ffffbf04`78e00340 ffffbf04`79b187ff : nt!IofCallDriver+0x55
ffff9a0d`871f7410 fffff802`65629fa0 : ffff8a05`95153a30 00000000`00000106 ffff9a0d`871f7510 00000000`00000106 : Wdf01000!FxPkgFdo::pnpSendStartDeviceDownTheStackOverload+0x260 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgfdo.cpp @ 1068]
ffff9a0d`871f7470 fffff802`65629a1a : 00000000`00000106 00000000`00000105 ffff8a05`95607830 ffff8a05`945fba10 : Wdf01000!FxPkgPnp::pnpEventInitStarting+0x10 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1328]
ffff9a0d`871f74a0 fffff802`6562b6f1 : ffff8a05`95607968 ffff8a05`95607830 ffff8a05`95607830 000065f2`78e089d0 : Wdf01000!FxPkgPnp::pnpEnterNewState+0x15e [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1234]
ffff9a0d`871f7530 fffff802`6562b4ba : ffff8a05`95607830 00000000`00000000 ffff8a05`95607990 ffff8a05`95607968 : Wdf01000!FxPkgPnp::pnpProcessEventInner+0x1d1 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1152]
ffff9a0d`871f75a0 fffff802`656329de : 00000000`00000000 ffff8a05`95607830 00000000`0000001b 00000000`00000000 : Wdf01000!FxPkgPnp::pnpProcessEvent+0x182 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 933]
ffff9a0d`871f7630 fffff802`655bccff : ffff8a05`95607830 00000000`0000001b ffff8a05`95607020 00000000`00000000 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 2025]
ffff9a0d`871f7660 fffff802`655ba906 : ffff8a05`95153a30 00000000`00000000 ffff8a05`94c8f2d0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0xaf [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffff9a0d`871f76d0 fffff802`62e35cf5 : 00000000`00000001 ffff8a05`939682a0 fffff802`62f6d5b0 ffff8a05`95153a30 : Wdf01000!FxDevice::DispatchWithLock+0x156 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffff9a0d`871f7730 fffff802`63369836 : ffff8a05`891e5d40 ffff8a05`939682a0 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffff9a0d`871f7770 fffff802`62eb0882 : ffff8a05`891e5d40 00000000`00000000 ffff8a05`939682a0 fffff802`62f6e07c : nt!PnpAsynchronousCall+0xea
ffff9a0d`871f77b0 fffff802`62f6df00 : 00000000`00000000 ffff8a05`891e5d40 fffff802`62f6d5b0 fffff802`62f6d5b0 : nt!PnpSendIrp+0x9e
ffff9a0d`871f7820 fffff802`6333f3a4 : ffff8a05`891e4010 00000000`00000000 ffff8a05`939682a0 00000000`00000001 : nt!PnpStartDevice+0x88
ffff9a0d`871f78b0 fffff802`6333f70b : ffff8a05`891e4010 00000000`00000000 00000000`00000001 fffff802`62f6da52 : nt!PnpStartDeviceNode+0xec
ffff9a0d`871f7940 fffff802`6333a07d : ffff8a05`891e4010 ffff9a0d`871f7a11 00000000`00000000 00000000`00000001 : nt!PipProcessStartPhase1+0x73
ffff9a0d`871f7990 fffff802`633d407c : ffff8a05`94ab1e01 ffff9a0d`871f7b01 ffff9a0d`871f7ab0 fffff802`00000000 : nt!PipProcessDevNodeTree+0x319
ffff9a0d`871f7a60 fffff802`62f6f17c : 00000001`00000003 ffff8a05`94ab1e90 00000000`00000000 ffff8a05`94ab1e90 : nt!PiProcessStartSystemDevices+0x60
ffff9a0d`871f7ab0 fffff802`62ec4695 : ffff8a05`9420e280 ffff8a05`87e88a20 fffff802`63843440 ffff8a05`00000000 : nt!PnpDeviceActionWorker+0x4cc
ffff9a0d`871f7b70 fffff802`62f078c5 : ffff8a05`9420e280 00000000`00000080 ffff8a05`87ea9040 000f8067`bcbbbdff : nt!ExpWorkerThread+0x105
ffff9a0d`871f7c10 fffff802`630067b8 : ffffaa81`d4137180 ffff8a05`9420e280 fffff802`62f07870 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9a0d`871f7c60 00000000`00000000 : ffff9a0d`871f8000 ffff9a0d`871f2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: ACPI!ACPIInternalSetDeviceInterface+5e

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

IMAGE_VERSION: 10.0.19041.3996

STACK_COMMAND: .cxr 0xffff9a0d871f6570 ; kb

BUCKET_ID_FUNC_OFFSET: 5e

FAILURE_BUCKET_ID: AV_ACPI!ACPIInternalSetDeviceInterface

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9bd9af7e-f910-47b2-1678-c208998b66d3}

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

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
Genişletmek için tıkla...

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
Genişletmek için tıkla...
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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


Loading Dump File [C:\Users\erhan\Desktop\Yeni klasör\032624-12046-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`62c00000 PsLoadedModuleList = 0xfffff802`6382a730
Debug session time: Tue Mar 26 17:39:02.406 2024 (UTC + 3:00)
System Uptime: 0 days 0:00:08.063
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
...
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`62ffd890 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9a0d`871f5d40=000000000000007e
13: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff80262e3c26e, The address that the exception occurred at
Arg3: ffff9a0d871f6d38, Exception Record Address
Arg4: ffff9a0d871f6570, Context Record Address

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


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 4062

Key : Analysis.Elapsed.mSec
Value: 8105

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e

Key : Bugcheck.Code.TargetModel
Value: 0x1000007e

Key : Failure.Bucket
Value: AV_ACPI!ACPIInternalSetDeviceInterface

Key : Failure.Hash
Value: {9bd9af7e-f910-47b2-1678-c208998b66d3}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80262e3c26e

BUGCHECK_P3: ffff9a0d871f6d38

BUGCHECK_P4: ffff9a0d871f6570

FILE_IN_CAB: 032624-12046-01.dmp

EXCEPTION_RECORD: ffff9a0d871f6d38 -- (.exr 0xffff9a0d871f6d38)
ExceptionAddress: fffff80262e3c26e (nt!ExFreeHeapPool+0x000000000000021e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: ffff9a0d871f6570 -- (.cxr 0xffff9a0d871f6570)
rax=0000000000001000 rbx=2990940108e87a17 rcx=ffffaa81d45b5000
rdx=0000000000001000 rsi=ffff9a0d871f7270 rdi=ffff9a0d871f7260
rip=fffff80262e3c26e rsp=ffff9a0d871f6f70 rbp=ffff9a0d871f71b0
r8=ffffaa81d457d000 r9=ffffaa81d457d000 r10=0000000000000000
r11=ffff9a0d871f6f68 r12=0000000000000000 r13=0000000000000ae0
r14=0000000000000000 r15=00000000fffff802
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!ExFreeHeapPool+0x21e:
fffff802`62e3c26e 488b5328 mov rdx,qword ptr [rbx+28h] ds:002b:29909401`08e87a3f=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff802638fb390: 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

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

EXCEPTION_STR: 0xc0000005

LOCK_ADDRESS: fffff80263844a80 -- (!locks fffff80263844a80)

Resource @ nt!PiEngineLock (0xfffff80263844a80) Exclusively owned
Contention Count = 3
NumberOfExclusiveWaiters = 1
Threads: ffff8a059420e280-01<*>

Threads Waiting On Exclusive Access:
ffff8a05890f3240
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff80263844a80
Thread Count : 1
Thread address: 0xffff8a059420e280
Thread wait : 0x204

STACK_TEXT:
ffff9a0d`871f6f70 fffff802`635b70b9 : 00000000`00000000 00000000`00000000 fffff802`62c0acf8 01000000`00100000 : nt!ExFreeHeapPool+0x21e
ffff9a0d`871f7050 fffff802`632cb861 : ffff9a0d`871f7128 00000000`00000000 ffffbf04`7d0eb720 ffff9a0d`871f7270 : nt!ExFreePool+0x9
ffff9a0d`871f7080 fffff802`6334287e : 00000000`00000190 ffff8a05`8c516001 00000000`00000000 ffffbf04`00000000 : nt!PnpUnicodeStringToWstrFree+0x2d
ffff9a0d`871f70b0 fffff802`6334247c : ffff9a0d`871f72e0 ffff9a0d`871f7270 ffff8a05`8c516010 00000000`00000001 : nt!IopProcessSetInterfaceState+0x3c2
ffff9a0d`871f71f0 fffff802`656ccece : 00000000`00000000 fffff802`6572f4d0 fffff802`6572f4d0 ffff8a05`95153a30 : nt!IoSetDeviceInterfaceState+0x3c
ffff9a0d`871f7220 fffff802`656ccd91 : 00000000`00000000 ffff8a05`891e5d40 ffff9a0d`871f72e0 ffff8a05`891e5d40 : ACPI!ACPIInternalSetDeviceInterface+0x5e
ffff9a0d`871f7290 fffff802`656ccc63 : ffff8a05`95150000 fffff802`00000012 ffff9a0d`0000000e ffff8a05`95153a30 : ACPI!ACPIProcessorStartDeviceWorker+0x111
ffff9a0d`871f7320 fffff802`656c1262 : 00000000`00000000 ffff8a05`95607830 ffff8a05`95153a30 fffff802`65634230 : ACPI!ACPIProcessorStartDevice+0x33
ffff9a0d`871f7350 fffff802`62e35cf5 : 00000000`00000007 ffff8a05`95607830 00000000`00000000 00000000`00000000 : ACPI!ACPIDispatchIrp+0x252
ffff9a0d`871f73d0 fffff802`65633cb0 : ffff8a05`95607830 00000000`00000000 ffffbf04`78e00340 ffffbf04`79b187ff : nt!IofCallDriver+0x55
ffff9a0d`871f7410 fffff802`65629fa0 : ffff8a05`95153a30 00000000`00000106 ffff9a0d`871f7510 00000000`00000106 : Wdf01000!FxPkgFdo::pnpSendStartDeviceDownTheStackOverload+0x260 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgfdo.cpp @ 1068]
ffff9a0d`871f7470 fffff802`65629a1a : 00000000`00000106 00000000`00000105 ffff8a05`95607830 ffff8a05`945fba10 : Wdf01000!FxPkgPnp::pnpEventInitStarting+0x10 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1328]
ffff9a0d`871f74a0 fffff802`6562b6f1 : ffff8a05`95607968 ffff8a05`95607830 ffff8a05`95607830 000065f2`78e089d0 : Wdf01000!FxPkgPnp::pnpEnterNewState+0x15e [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1234]
ffff9a0d`871f7530 fffff802`6562b4ba : ffff8a05`95607830 00000000`00000000 ffff8a05`95607990 ffff8a05`95607968 : Wdf01000!FxPkgPnp::pnpProcessEventInner+0x1d1 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 1152]
ffff9a0d`871f75a0 fffff802`656329de : 00000000`00000000 ffff8a05`95607830 00000000`0000001b 00000000`00000000 : Wdf01000!FxPkgPnp::pnpProcessEvent+0x182 [minkernel\wdf\framework\shared\irphandlers\pnp\pnpstatemachine.cpp @ 933]
ffff9a0d`871f7630 fffff802`655bccff : ffff8a05`95607830 00000000`0000001b ffff8a05`95607020 00000000`00000000 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 2025]
ffff9a0d`871f7660 fffff802`655ba906 : ffff8a05`95153a30 00000000`00000000 ffff8a05`94c8f2d0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0xaf [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffff9a0d`871f76d0 fffff802`62e35cf5 : 00000000`00000001 ffff8a05`939682a0 fffff802`62f6d5b0 ffff8a05`95153a30 : Wdf01000!FxDevice::DispatchWithLock+0x156 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffff9a0d`871f7730 fffff802`63369836 : ffff8a05`891e5d40 ffff8a05`939682a0 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffff9a0d`871f7770 fffff802`62eb0882 : ffff8a05`891e5d40 00000000`00000000 ffff8a05`939682a0 fffff802`62f6e07c : nt!PnpAsynchronousCall+0xea
ffff9a0d`871f77b0 fffff802`62f6df00 : 00000000`00000000 ffff8a05`891e5d40 fffff802`62f6d5b0 fffff802`62f6d5b0 : nt!PnpSendIrp+0x9e
ffff9a0d`871f7820 fffff802`6333f3a4 : ffff8a05`891e4010 00000000`00000000 ffff8a05`939682a0 00000000`00000001 : nt!PnpStartDevice+0x88
ffff9a0d`871f78b0 fffff802`6333f70b : ffff8a05`891e4010 00000000`00000000 00000000`00000001 fffff802`62f6da52 : nt!PnpStartDeviceNode+0xec
ffff9a0d`871f7940 fffff802`6333a07d : ffff8a05`891e4010 ffff9a0d`871f7a11 00000000`00000000 00000000`00000001 : nt!PipProcessStartPhase1+0x73
ffff9a0d`871f7990 fffff802`633d407c : ffff8a05`94ab1e01 ffff9a0d`871f7b01 ffff9a0d`871f7ab0 fffff802`00000000 : nt!PipProcessDevNodeTree+0x319
ffff9a0d`871f7a60 fffff802`62f6f17c : 00000001`00000003 ffff8a05`94ab1e90 00000000`00000000 ffff8a05`94ab1e90 : nt!PiProcessStartSystemDevices+0x60
ffff9a0d`871f7ab0 fffff802`62ec4695 : ffff8a05`9420e280 ffff8a05`87e88a20 fffff802`63843440 ffff8a05`00000000 : nt!PnpDeviceActionWorker+0x4cc
ffff9a0d`871f7b70 fffff802`62f078c5 : ffff8a05`9420e280 00000000`00000080 ffff8a05`87ea9040 000f8067`bcbbbdff : nt!ExpWorkerThread+0x105
ffff9a0d`871f7c10 fffff802`630067b8 : ffffaa81`d4137180 ffff8a05`9420e280 fffff802`62f07870 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff9a0d`871f7c60 00000000`00000000 : ffff9a0d`871f8000 ffff9a0d`871f2000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: ACPI!ACPIInternalSetDeviceInterface+5e

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

IMAGE_VERSION: 10.0.19041.4106

STACK_COMMAND: .cxr 0xffff9a0d871f6570 ; kb

BUCKET_ID_FUNC_OFFSET: 5e

FAILURE_BUCKET_ID: AV_ACPI!ACPIInternalSetDeviceInterface

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9bd9af7e-f910-47b2-1678-c208998b66d3}

Followup: MachineOwner
---------
 
Artı 0 Eksi

Benzer konular

Emitra
  • Çözüldü
Çözüldü  Mavi ekran hatası
Mesaj
9
Görüntüleme
4B
yusuf2727.X
yusuf2727.X
7
  • Soru
Mavi ekran hatası
Mesaj
2
Görüntüleme
2B
ShandyRoblox
ShandyRoblox
A
  • Soru
Mavi ekran hatası
Mesaj
6
Görüntüleme
2B
haggarz
haggarz
eternity_day
  • Soru
Mavi ekran hatası
Mesaj
1
Görüntüleme
2B
Ted Kaczynski
Ted Kaczynski
X
  • Soru
Mavi ekran hatası
2
Mesaj
10
Görüntüleme
2B
405668
405668

Yeni konular

Yeni mesajlar

Geri
Yukarı