Merhaba,
23 Temmuz 2024 itibarıyla bilgisayarımı kullanmaya başladım ve ilk kez mavi ekran hatası aldım. Mavi ekran hatasını yaşadığım durumu anlatmak istiyorum ve dosyalarımı paylaşarak yorumlamanızı rica ediyorum.
MSI App Player'ı kuruyordum ve program aracılığıyla indirme yaptıktan sonra, kurulumu geçerken aniden mavi ekran uyarısı aldım ve bilgisayar yeniden başlatıldı. Biraz araştırdıktan sonra, DMP dosyasını analiz ettim ve bellek sorunları olabileceğini düşündüm; fakat emin olamadım. Bu dosyayı ekliyorum. Ayrıca, "SFC /scannow" taraması yaptırdım ve hatalı dosyaların sorunsuz bir şekilde düzeltildiğine dair bir ibare gördüm. Bu bilgiyi de eklemek istiyorum. Sizce sorun nedir ? Zamanınızı ayırdığınız için teşekkürler. Hyper-V açık durumda bilgisinde vereyim dump ile scannow dosyaları – Google Диск
İndirdiğim yazılım https://www.msi.com/Landing/appplayer
Yazılımı tekrar açtığımda emülatör sorunsuz çalıştı ama hata kafama takıldı başka bir önemli sorun teşkil etmesin diye
************* Preparing the environment for debugger extensions gallery repositories **************
Extensionrepository : Implicit.
Useexperimentalfeaturefornugetshare : True.
Allownugetexeupdate : True.
Nonınteractivenuget : True.
Allownugetmscredentialproviderınstall : True.
Allowparallelınitializationoflocalrepositories : True.
Enableredirecttochakrajsprovider : False.
-- Configuring repositories.
----> Repository : Localınstalled, enabled: True.
----> Repository : Userextensions, enabled: True.
----> Repository : Localınstalled, enabled: True, packages count: 42.
Microsoft (r) Windows debugger version 10.0.27668.1000 AMD64.
Copyright (C) Microsoft Corporation. All rights reserved.
Loading dump file [C:\Users\Emrah\Desktop\091324-24062-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 22621 MP (32 procs) Free X64.
Product: Winnt, Suite: Terminalserver singleuserts.
Edition Build lab: 22621.1.AMD64fre.ni_release.220506-1250
Kernel base = 0xfffff801`67c00000 psloadedmodulelist = 0xfffff801`688134f0
Debug session time: Fri sep 13 05:31:36.725 2024 (utc + 3:00)
System uptime: 0 days 0:15:50.689
Loading kernel symbols.
...............................................................
................................................................
................................................................
................................................................
.........
Loading user symbols.
Loading unloaded module list.
................
For analysis of this file, run !analyze -v
NT!kebugcheckex:
Fffff801'68016000 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffffbc0C'230379F0 = 0000000000000020.
10: Kd> !analyze -v
*******************************************************************************
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-Zero, then this is the Source of the problem.
The APC disable count is decremented each time a driver calls.
Keentercriticalregion, fsrtlenterfilesystem, or acquires a mutex. The APC.
Disable count is incremented each time a driver calls keleavecriticalregion,
Fsrtlexitfilesystem, or kereleasemutex. Since these calls should always be in.
Pairs, this Value should be Zero when a thread exits. A negative Value.
İndicates that a driver has disabled APC calls without re-enabling them. A
Positive Value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the.
Machine -- especially unusual or non-standard drivers. Third party file.
System redirectors are especially suspicious since they do not generally.
Receive the heavy duty testing that NTFS, fat, RDR, ETC receive.
This current IRQL should also be 0. ıf it is not, that a driver's.
Cancellation routine can cause this bugcheck by returning at an elevated.
IRQL. Always attempt to Note what you were doing/closing at the.
Time of the crash, and Note all of the installed drivers at the time of.
The crash. This symptom is usually a severe bug in a Third party.
Driver.
Arguments:
Arg1: 0000000000000000, the address of the APC found pending during exit.
Arg2: 000000000000FFFF, the thread's APC disable count.
Arg3: 0000000000000000, the current IRQL.
Arg4: 0000000000000001.
Debugging details:
------------------
Key_values_strıng: 1
Key : Analysis.CPU.msec
Value: 1093.
Key : Analysis.elapsed.msec
Value: 4609.
Key : Analysis.Ither.MB
Value: 0
Key : Analysis.IO.read.MB
Value: 0
Key : Analysis.IO.write.MB
Value: 1
Key : Analysis.ınit.CPU.msec
Value: 171.
Key : Analysis.ınit.elapsed.msec
Value: 11813.
Key : Analysis.Memory.commitpeak.MB
Value: 95.
Key : Bugcheck.code.legacyapı
Value: 0x20.
Key : Bugcheck.code.targetmodel
Value: 0x20.
Key : Failure.bucket
Value: 0x20_nullapc_kapc_negatıve_nt!pspexitthread
Key : Failure.hash
Value: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Key : Hypervisor.enlightenments.valuehex
Value: 1417DF84.
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.phase0ınitdone
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.ıshyperv
Value: 1
Key : Hypervisor.rootflags.livedumpenlightened
Value: 1
Key : Hypervisor.rootflags.mapdeviceınterrupt
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: Ni_release.
Key : Wer.OS.version
Value: 10.0.22621.1
Bugcheck_code: 20.
Bugcheck_p1: 0
Bugcheck_p2: Ffff.
Bugcheck_p3: 0
Bugcheck_p4: 1
Fıle_ın_cab: 091324-24062-01.dmp
Tag_not_defıned_202b: *** unknown tag in analysis list 202b.
Faultıng_thread: FfffBE8304F4C040.
Blackboxbsd: 1 (!blackboxbsd)
Blackboxntfs: 1 (!blackboxntfs)
Blackboxpnp: 1 (!blackboxpnp)
Blackboxwınlogon: 1
Customer_crash_count: 1
Process_name: System.
Stack_text:
Ffffbc0C'230379E8 fffff801'6850279C : 00000000'00000020 00000000'00000000 00000000'0000FFFF 00000000'00000000 : NT!kebugcheckex
Ffffbc0C'230379F0 fffff801'683da943 : Ffffbe82'00000000 fffff801'B17170BB ffffbe83'04F4C040 00000000'00000000 : NT!pspexitthread+0x129338
Ffffbc0C'23037AF0 fffff801'67F54D61 : Ffffbe83'04F4C040 00000000'00000080 fffff801'B17170A0 00000000'00000000 : NT!pspterminatethreadbypointer+0x53
Ffffbc0C'23037B30 fffff801'6801B174 : Ffffe581'E3091180 ffffbe83'04F4C040 fffff801'67F54CF0 00000000'00000246 : NT!pspsystemthreadstartup+0x71
Ffffbc0C'23037B80 00000000'00000000 : Ffffbc0C'23038000 ffffbc0C'23031000 00000000'00000000 00000000'00000000 : NT!kistartsystemthread+0x34
Symbol_name: NT!pspexitthread+129338
Module_name: NT.
Image_name: ntkrnlmp.exe
Image_versıon: 10.0.22621.4169
Stack_command: .process /r /p 0xffffbe82cc170040; .thread 0xffffbe8304f4c040 ; KB.
Bucket_ıd_func_offset: 129338.
Faılure_bucket_ıd: 0x20_nullapc_kapc_negatıve_nt!pspexitthread
Os_versıon: 10.0.22621.1
Buıldlab_str: Ni_release.
Osplatform_type: X64.
Osname: Windows 10.
Faılure_ıd_hash: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Followup: Machineowner.
---------
23 Temmuz 2024 itibarıyla bilgisayarımı kullanmaya başladım ve ilk kez mavi ekran hatası aldım. Mavi ekran hatasını yaşadığım durumu anlatmak istiyorum ve dosyalarımı paylaşarak yorumlamanızı rica ediyorum.
MSI App Player'ı kuruyordum ve program aracılığıyla indirme yaptıktan sonra, kurulumu geçerken aniden mavi ekran uyarısı aldım ve bilgisayar yeniden başlatıldı. Biraz araştırdıktan sonra, DMP dosyasını analiz ettim ve bellek sorunları olabileceğini düşündüm; fakat emin olamadım. Bu dosyayı ekliyorum. Ayrıca, "SFC /scannow" taraması yaptırdım ve hatalı dosyaların sorunsuz bir şekilde düzeltildiğine dair bir ibare gördüm. Bu bilgiyi de eklemek istiyorum. Sizce sorun nedir ? Zamanınızı ayırdığınız için teşekkürler. Hyper-V açık durumda bilgisinde vereyim dump ile scannow dosyaları – Google Диск
İndirdiğim yazılım https://www.msi.com/Landing/appplayer
Yazılımı tekrar açtığımda emülatör sorunsuz çalıştı ama hata kafama takıldı
başka bir önemli sorun teşkil etmesin diye ************* Preparing the environment for debugger extensions gallery repositories **************
Extensionrepository : Implicit.
Useexperimentalfeaturefornugetshare : True.
Allownugetexeupdate : True.
Nonınteractivenuget : True.
Allownugetmscredentialproviderınstall : True.
Allowparallelınitializationoflocalrepositories : True.
Enableredirecttochakrajsprovider : False.
-- Configuring repositories.
----> Repository : Localınstalled, enabled: True.
----> Repository : Userextensions, enabled: True.
************* Waiting for debugger extensions gallery to ınitialize **************
----> Repository : Userextensions, enabled: True, packages count: 0
----> Repository : Localınstalled, enabled: True, packages count: 42.
Microsoft (r) Windows debugger version 10.0.27668.1000 AMD64.
Copyright (C) Microsoft Corporation. All rights reserved.
Loading dump file [C:\Users\Emrah\Desktop\091324-24062-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 22621 MP (32 procs) Free X64.
Product: Winnt, Suite: Terminalserver singleuserts.
Edition Build lab: 22621.1.AMD64fre.ni_release.220506-1250
Kernel base = 0xfffff801`67c00000 psloadedmodulelist = 0xfffff801`688134f0
Debug session time: Fri sep 13 05:31:36.725 2024 (utc + 3:00)
System uptime: 0 days 0:15:50.689
Loading kernel symbols.
...............................................................
................................................................
................................................................
................................................................
.........
Loading user symbols.
Loading unloaded module list.
................
For analysis of this file, run !analyze -v
NT!kebugcheckex:
Fffff801'68016000 48894C2408 mov qword ptr [rsp+8],rcx SS:0018:ffffbc0C'230379F0 = 0000000000000020.
10: Kd> !analyze -v
*******************************************************************************
- *
- Bugcheck analysis *
- *
KERNEL_APC_PENDING_DURING_EXIT (20)
The key data item is the thread's APC disable count.
If this is non-Zero, then this is the Source of the problem.
The APC disable count is decremented each time a driver calls.
Keentercriticalregion, fsrtlenterfilesystem, or acquires a mutex. The APC.
Disable count is incremented each time a driver calls keleavecriticalregion,
Fsrtlexitfilesystem, or kereleasemutex. Since these calls should always be in.
Pairs, this Value should be Zero when a thread exits. A negative Value.
İndicates that a driver has disabled APC calls without re-enabling them. A
Positive Value indicates that the reverse is true.
If you ever see this error, be very suspicious of all drivers installed on the.
Machine -- especially unusual or non-standard drivers. Third party file.
System redirectors are especially suspicious since they do not generally.
Receive the heavy duty testing that NTFS, fat, RDR, ETC receive.
This current IRQL should also be 0. ıf it is not, that a driver's.
Cancellation routine can cause this bugcheck by returning at an elevated.
IRQL. Always attempt to Note what you were doing/closing at the.
Time of the crash, and Note all of the installed drivers at the time of.
The crash. This symptom is usually a severe bug in a Third party.
Driver.
Arguments:
Arg1: 0000000000000000, the address of the APC found pending during exit.
Arg2: 000000000000FFFF, the thread's APC disable count.
Arg3: 0000000000000000, the current IRQL.
Arg4: 0000000000000001.
Debugging details:
------------------
Key_values_strıng: 1
Key : Analysis.CPU.msec
Value: 1093.
Key : Analysis.elapsed.msec
Value: 4609.
Key : Analysis.I
ther.MBValue: 0
Key : Analysis.IO.read.MB
Value: 0
Key : Analysis.IO.write.MB
Value: 1
Key : Analysis.ınit.CPU.msec
Value: 171.
Key : Analysis.ınit.elapsed.msec
Value: 11813.
Key : Analysis.Memory.commitpeak.MB
Value: 95.
Key : Bugcheck.code.legacyapı
Value: 0x20.
Key : Bugcheck.code.targetmodel
Value: 0x20.
Key : Failure.bucket
Value: 0x20_nullapc_kapc_negatıve_nt!pspexitthread
Key : Failure.hash
Value: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Key : Hypervisor.enlightenments.valuehex
Value: 1417DF84.
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.phase0ınitdone
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.ıshyperv
Value: 1
Key : Hypervisor.rootflags.livedumpenlightened
Value: 1
Key : Hypervisor.rootflags.mapdeviceınterrupt
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: Ni_release.
Key : Wer.OS.version
Value: 10.0.22621.1
Bugcheck_code: 20.
Bugcheck_p1: 0
Bugcheck_p2: Ffff.
Bugcheck_p3: 0
Bugcheck_p4: 1
Fıle_ın_cab: 091324-24062-01.dmp
Tag_not_defıned_202b: *** unknown tag in analysis list 202b.
Faultıng_thread: FfffBE8304F4C040.
Blackboxbsd: 1 (!blackboxbsd)
Blackboxntfs: 1 (!blackboxntfs)
Blackboxpnp: 1 (!blackboxpnp)
Blackboxwınlogon: 1
Customer_crash_count: 1
Process_name: System.
Stack_text:
Ffffbc0C'230379E8 fffff801'6850279C : 00000000'00000020 00000000'00000000 00000000'0000FFFF 00000000'00000000 : NT!kebugcheckex
Ffffbc0C'230379F0 fffff801'683da943 : Ffffbe82'00000000 fffff801'B17170BB ffffbe83'04F4C040 00000000'00000000 : NT!pspexitthread+0x129338
Ffffbc0C'23037AF0 fffff801'67F54D61 : Ffffbe83'04F4C040 00000000'00000080 fffff801'B17170A0 00000000'00000000 : NT!pspterminatethreadbypointer+0x53
Ffffbc0C'23037B30 fffff801'6801B174 : Ffffe581'E3091180 ffffbe83'04F4C040 fffff801'67F54CF0 00000000'00000246 : NT!pspsystemthreadstartup+0x71
Ffffbc0C'23037B80 00000000'00000000 : Ffffbc0C'23038000 ffffbc0C'23031000 00000000'00000000 00000000'00000000 : NT!kistartsystemthread+0x34
Symbol_name: NT!pspexitthread+129338
Module_name: NT.
Image_name: ntkrnlmp.exe
Image_versıon: 10.0.22621.4169
Stack_command: .process /r /p 0xffffbe82cc170040; .thread 0xffffbe8304f4c040 ; KB.
Bucket_ıd_func_offset: 129338.
Faılure_bucket_ıd: 0x20_nullapc_kapc_negatıve_nt!pspexitthread
Os_versıon: 10.0.22621.1
Buıldlab_str: Ni_release.
Osplatform_type: X64.
Osname: Windows 10.
Faılure_ıd_hash: {fcbbc787-B7CC-0CA4-C274-C788B86A9951}
Followup: Machineowner.
---------
Dosya Ekleri
Son düzenleyen: Moderatör:
