KERNEL_DATA_INPAGE_ERROR (7a) hatası olan dökümlerde şu sürücüde problem yaşanmış :| Name: | vmswitch.sys |
| Info: | Microsoft Hyper-V Network Virtualization Service Provider driver |
| Source: | Windows Update |
Generally, this bugcheck is caused by a serious virus infection or failing HDD/SSD and/or a corrupted filesystem.
Böyle bir yorum yapılmış. Genel olarak ömür sorunları da vardı bu modelin.Düşük hız sorunu var genel olarak. Phison S11'in enerji tüketimi amacıyla sanırım biraz kırpılmış bir modeli olan Phison S11T kontrolcüyü kullanıyor, bundan kaynaklı olması muhtemel.
SFC /scannowDISM /Online /Cleanup-Image /RestoreHealth*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffff910486caf140, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: ffff910486caf140, The process object that initiated the termination.
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2312
Key : Analysis.Elapsed.mSec
Value: 4136
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: 203
Key : Analysis.Init.Elapsed.mSec
Value: 1153
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : Bugcheck.Code.LegacyAPI
Value: 0xef
Key : CriticalProcessDied.ExceptionCode
Value: 89ee3500
Key : CriticalProcessDied.Process
Value: csrss.exe
Key : Failure.Bucket
Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_89ee3500_nt!PspCatchCriticalBreak
Key : Failure.Hash
Value: {3af5295f-77c6-0c1e-db79-dae4845eef9b}
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
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: ef
BUGCHECK_P1: ffff910486caf140
BUGCHECK_P2: 0
BUGCHECK_P3: ffff910486caf140
BUGCHECK_P4: 0
FILE_IN_CAB: 070323-25203-01.dmp
PROCESS_NAME: csrss.exe
CRITICAL_PROCESS: csrss.exe
ERROR_CODE: (NTSTATUS) 0x89ee3500 - <Unable to get error code text>
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
fffffd87`5c3b7d48 fffff804`629b7afb : 00000000`000000ef ffff9104`86caf140 00000000`00000000 ffff9104`86caf140 : nt!KeBugCheckEx
fffffd87`5c3b7d50 fffff804`628d5659 : ffff9104`86caf140 fffff804`623381c1 00000000`00000000 fffff804`62337a4b : nt!PspCatchCriticalBreak+0x11b
fffffd87`5c3b7de0 fffff804`627a7657 : ffff9104`86caf140 00000000`c0000006 ffff9104`86caf140 00000000`00000001 : nt!PspTerminateAllThreads+0x1d16f1
fffffd87`5c3b7e50 fffff804`627a7431 : ffffffff`ffffffff ffff9104`86caf140 ffff9104`89ee3500 ffff9104`86caf140 : nt!PspTerminateProcess+0xe3
fffffd87`5c3b7e90 fffff804`62440fe8 : 000000c8`00000318 ffff9104`89ee3500 ffff9104`86caf140 fffff804`6294f2e7 : nt!NtTerminateProcess+0xb1
fffffd87`5c3b7f10 fffff804`62431b10 : fffff804`624ced79 ffffffff`ffffffff 000000c8`4b8b13b0 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x28
fffffd87`5c3b80a8 fffff804`624ced79 : ffffffff`ffffffff 000000c8`4b8b13b0 00000000`00000001 fffffd87`5c3b80e0 : nt!KiServiceLinkage
fffffd87`5c3b80b0 fffff804`624419fc : 00000000`00000000 00000000`00000000 000006d6`279b4099 00000000`00000000 : nt!KiDispatchException+0x1bb029
fffffd87`5c3b8900 fffff804`6243cf0e : 00000000`00000000 ffffc901`824b9640 000000c8`4b8b1690 ffff9104`00000000 : nt!KiExceptionDispatch+0x13c
fffffd87`5c3b8ae0 00007ffb`7c870352 : 00007ffb`79c39364 00007ffb`79c44000 000000c8`4b8b2270 00000000`00000000 : nt!KiPageFault+0x44e
000000c8`4b8b15e0 00007ffb`79c39364 : 00007ffb`79c44000 000000c8`4b8b2270 00000000`00000000 00007ffb`79c44000 : 0x00007ffb`7c870352
000000c8`4b8b15e8 00007ffb`79c44000 : 000000c8`4b8b2270 00000000`00000000 00007ffb`79c44000 00007ffb`79c30000 : 0x00007ffb`79c39364
000000c8`4b8b15f0 000000c8`4b8b2270 : 00000000`00000000 00007ffb`79c44000 00007ffb`79c30000 00000ad4`00019000 : 0x00007ffb`79c44000
000000c8`4b8b15f8 00000000`00000000 : 00007ffb`79c44000 00007ffb`79c30000 00000ad4`00019000 000000c8`4b8b2270 : 0x000000c8`4b8b2270
SYMBOL_NAME: nt!PspCatchCriticalBreak+11b
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.1848
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 11b
FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_89ee3500_nt!PspCatchCriticalBreak
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3af5295f-77c6-0c1e-db79-dae4845eef9b}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000006, Exception code that caused the BugCheck
Arg2: fffff802284ad88c, Address of the instruction which caused the BugCheck
Arg3: ffff858520c60390, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: 3015
Key : Analysis.Elapsed.mSec
Value: 3225
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: 202
Key : Analysis.Init.Elapsed.mSec
Value: 991
Key : Analysis.Memory.CommitPeak.Mb
Value: 150
Key : Bugcheck.Code.LegacyAPI
Value: 0x3b
Key : Failure.Bucket
Value: 0x3B_C0000006_nt!HvpGetCellPaged
Key : Failure.Hash
Value: {68f3db38-ae8e-4bae-c37a-85819946495f}
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
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000006
BUGCHECK_P2: fffff802284ad88c
BUGCHECK_P3: ffff858520c60390
BUGCHECK_P4: 0
FILE_IN_CAB: 070323-16359-01.dmp
CONTEXT: ffff858520c60390 -- (.cxr 0xffff858520c60390)
rax=000001ad9f51e000 rbx=00000000026add90 rcx=000001ad9f51ed90
rdx=ffffc90736124038 rsi=ffff858520c60e80 rdi=00000000a88ef046
rip=fffff802284ad88c rsp=ffff858520c60db0 rbp=ffff858520c60ee0
r8=ffff858520c60e84 r9=00000000000000ad r10=ffffc90734878000
r11=0000000003232ff0 r12=00000000a88ef046 r13=ffff858520c61250
r14=000001ada00b9b1c r15=000001ada00b9024
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
nt!HvpGetCellPaged+0x7c:
fffff802`284ad88c 8b01 mov eax,dword ptr [rcx] ds:002b:000001ad`9f51ed90=????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Registry
STACK_TEXT:
ffff8585`20c60db0 fffff802`284ac73e : 00000000`a88ef046 00000000`e9c5e935 ffff8585`20c61250 00000000`00000000 : nt!HvpGetCellPaged+0x7c
ffff8585`20c60de0 fffff802`284ae577 : ffffc907`5ad26af0 ffff8585`20c61160 ffff8585`20c61060 ffff8585`20c61180 : nt!CmpWalkOneLevel+0x73e
ffff8585`20c60f40 fffff802`284b3435 : 00000000`0000001c ffff8585`20c61470 ffff8585`20c613f8 00000000`00000000 : nt!CmpDoParseKey+0x867
ffff8585`20c61380 fffff802`284b79db : fffff802`284b3101 ffffaf0f`00000000 ffffaf0f`acccaaa0 00000000`00000001 : nt!CmpParseKey+0x2e5
ffff8585`20c61570 fffff802`284b6e52 : ffffaf0f`acccaaa0 ffff8585`20c617a0 00000000`00000040 ffffaf0f`9837a6c0 : nt!ObpLookupObjectName+0x63b
ffff8585`20c61710 fffff802`284ba184 : 00000000`00000000 ffffaf0f`9837a6c0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2
ffff8585`20c61840 fffff802`284bab48 : 00000063`fd27d5a8 00000000`00000000 ffff8585`20c61b60 fffff802`28549d99 : nt!CmOpenKey+0x2c4
ffff8585`20c61a90 fffff802`28240fe8 : ffffaf0f`9f5cb080 00000000`00000000 00000000`000075c0 ffffaf0f`00000000 : nt!NtOpenKeyEx+0x48
ffff8585`20c61ae0 00007ff8`feef1164 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000063`fd27d588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`feef1164
SYMBOL_NAME: nt!HvpGetCellPaged+7c
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.22621.1848
STACK_COMMAND: .cxr 0xffff858520c60390 ; kb
BUCKET_ID_FUNC_OFFSET: 7c
FAILURE_BUCKET_ID: 0x3B_C0000006_nt!HvpGetCellPaged
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffffb68f1eb9f228, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000003ea2f7860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff80771e257c0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1655
Key : Analysis.Elapsed.mSec
Value: 8716
Key : Analysis.IO.Other.Mb
Value: 4
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 4
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 1101
Key : Analysis.Memory.CommitPeak.Mb
Value: 159
Key : Bugcheck.Code.LegacyAPI
Value: 0x7a
Key : Failure.Bucket
Value: 0x7a_c000000e_nt!MiWaitForInPageComplete
Key : Failure.Hash
Value: {329318b9-5fab-73eb-d104-f79603e1bdb3}
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
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 7a
BUGCHECK_P1: ffffb68f1eb9f228
BUGCHECK_P2: ffffffffc000000e
BUGCHECK_P3: 3ea2f7860
BUGCHECK_P4: fffff80771e257c0
FILE_IN_CAB: 070223-11828-01.dmp
ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.
DISK_HARDWARE_ERROR: There was error with disk hardware
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff38f48b77680 -- (.trap 0xfffff38f48b77680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80771e257c0 rbx=0000000000000000 rcx=ffffb68f4cf8b758
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80771e257c0 rsp=fffff38f48b77818 rbp=fffff38f48b778f9
r8=00000000000000ff r9=0000800000000000 r10=0000fffff80771e2
r11=ffff6ffd27200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
vmswitch!tlgEnableCallback:
fffff807`71e257c0 4883ec48 sub rsp,48h
Resetting default scope
STACK_TEXT:
fffff38f`48b77358 fffff807`34e93b3f : 00000000`0000007a ffffb68f`1eb9f228 ffffffff`c000000e 00000003`ea2f7860 : nt!KeBugCheckEx
fffff38f`48b77360 fffff807`34c4f46b : 00000000`00000000 fffff38f`00000000 fffff38f`48b77508 fffff807`00000000 : nt!MiWaitForInPageComplete+0x24412f
fffff38f`48b77460 fffff807`34c33fb7 : 00000000`c0033333 00000000`00000000 fffff807`71e257c0 fffff807`71e257c0 : nt!MiIssueHardFault+0x1cb
fffff38f`48b77560 fffff807`34e3ce29 : 00000000`00000000 ffffb68f`168003b9 00008000`00000000 ffffb68f`4cf891fe : nt!MmAccessFault+0x347
fffff38f`48b77680 fffff807`71e257c0 : fffff807`3515e3cc 00000000`44777445 fffff807`34c85fdf 00000000`000001c0 : nt!KiPageFault+0x369
fffff38f`48b77818 fffff807`3515e3cc : 00000000`44777445 fffff807`34c85fdf 00000000`000001c0 ffff918c`c7f330d8 : vmswitch!tlgEnableCallback
fffff38f`48b77820 fffff807`35119d76 : 00000000`00000000 fffff38f`48b77a60 ffffb68f`4cf8b720 ffff918c`c7f330a0 : nt!EtwpSendDataBlock+0x138
fffff38f`48b77960 fffff807`3511817a : ffff8001`92202380 ffff8001`92202380 ffff918c`c7f330a0 ffff918c`c7bce000 : nt!EtwpClearSessionAndUnreferenceEntry+0x296
fffff38f`48b77aa0 fffff807`3518bf04 : fffff807`34a0ebe8 ffff918c`c7bdc600 ffff918c`c7bdc7e0 00000000`00000000 : nt!EtwpDisableTraceProviders+0x4e
fffff38f`48b77af0 fffff807`352d9599 : ffff918c`c7bdc600 ffff918c`c7bdc600 ffff918c`c7bdc7e0 ffff918c`c7bdc7c8 : nt!EtwpStopLoggerInstance+0x58
fffff38f`48b77b70 fffff807`34cd8dc7 : ffffffff`fffffffd ffff918c`c7f8d040 00000000`00000080 fffff807`351168e0 : nt!EtwpLogger+0x1c2cb9
fffff38f`48b77bf0 fffff807`34e311e4 : ffff8001`92c51180 ffff918c`c7f8d040 fffff807`34cd8d70 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff38f`48b77c40 00000000`00000000 : fffff38f`48b78000 fffff38f`48b72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: nt!MiWaitForInPageComplete+24412f
MODULE_NAME: nt
IMAGE_VERSION: 10.0.22621.1848
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 24412f
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3}
Followup: MachineOwner
---------
******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: ffff898d5549a228, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000014901a860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8071af457c0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1671
Key : Analysis.Elapsed.mSec
Value: 4690
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: 233
Key : Analysis.Init.Elapsed.mSec
Value: 1580
Key : Analysis.Memory.CommitPeak.Mb
Value: 160
Key : Bugcheck.Code.LegacyAPI
Value: 0x7a
Key : Failure.Bucket
Value: 0x7a_c000000e_nt!MiWaitForInPageComplete
Key : Failure.Hash
Value: {329318b9-5fab-73eb-d104-f79603e1bdb3}
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
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Version
Value: 10.0.22621.1
BUGCHECK_CODE: 7a
BUGCHECK_P1: ffff898d5549a228
BUGCHECK_P2: ffffffffc000000e
BUGCHECK_P3: 14901a860
BUGCHECK_P4: fffff8071af457c0
FILE_IN_CAB: 070223-19281-01.dmp
ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi.
DISK_HARDWARE_ERROR: There was error with disk hardware
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffff85022d777680 -- (.trap 0xffff85022d777680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8071af457c0 rbx=0000000000000000 rcx=ffff898da2d710c8
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8071af457c0 rsp=ffff85022d777818 rbp=ffff85022d7778f9
r8=00000000000000ff r9=0000800000000000 r10=0000fffff8071af4
r11=ffffc57c98c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
vmswitch!tlgEnableCallback:
fffff807`1af457c0 4883ec48 sub rsp,48h
Resetting default scope
STACK_TEXT:
ffff8502`2d777358 fffff807`0b693b3f : 00000000`0000007a ffff898d`5549a228 ffffffff`c000000e 00000001`4901a860 : nt!KeBugCheckEx
ffff8502`2d777360 fffff807`0b44f46b : 00000000`00000000 ffff8502`00000000 ffff8502`2d777508 fffff807`00000000 : nt!MiWaitForInPageComplete+0x24412f
ffff8502`2d777460 fffff807`0b433fb7 : 00000000`c0033333 00000000`00000000 fffff807`1af457c0 fffff807`1af457c0 : nt!MiIssueHardFault+0x1cb
ffff8502`2d777560 fffff807`0b63ce29 : 00000000`00000000 ffff898d`4a2003b9 00008000`00000000 ffff898d`a2d5722e : nt!MmAccessFault+0x347
ffff8502`2d777680 fffff807`1af457c0 : fffff807`0b95e3cc 00000000`44777445 fffff807`0b485fdf 00000000`000001c0 : nt!KiPageFault+0x369
ffff8502`2d777818 fffff807`0b95e3cc : 00000000`44777445 fffff807`0b485fdf 00000000`000001c0 ffffa705`c7332118 : vmswitch!tlgEnableCallback
ffff8502`2d777820 fffff807`0b919d76 : 00000000`00000000 ffff8502`2d777a60 ffff898d`a2d71090 ffffa705`c73320e0 : nt!EtwpSendDataBlock+0x138
ffff8502`2d777960 fffff807`0b91817a : ffffd581`57202380 ffffd581`57202380 ffffa705`c73320e0 ffffa705`c5fc8000 : nt!EtwpClearSessionAndUnreferenceEntry+0x296
ffff8502`2d777aa0 fffff807`0b98bf04 : fffff807`0b20ebe8 ffffa705`c5fd7600 ffffa705`c5fd77e0 00000000`00000000 : nt!EtwpDisableTraceProviders+0x4e
ffff8502`2d777af0 fffff807`0bad9599 : ffffa705`c5fd7600 ffffa705`c5fd7600 ffffa705`c5fd77e0 ffffa705`c5fd77c8 : nt!EtwpStopLoggerInstance+0x58
ffff8502`2d777b70 fffff807`0b4d8dc7 : ffffffff`fffffffd ffffa705`c5fd9040 00000000`00000080 fffff807`0b9168e0 : nt!EtwpLogger+0x1c2cb9
ffff8502`2d777bf0 fffff807`0b6311e4 : ffffd581`57c51180 ffffa705`c5fd9040 fffff807`0b4d8d70 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffff8502`2d777c40 00000000`00000000 : ffff8502`2d778000 ffff8502`2d772000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: nt!MiWaitForInPageComplete+24412f
MODULE_NAME: nt
IMAGE_VERSION: 10.0.22621.1848
STACK_COMMAND: .cxr; .ecxr ; kb
IMAGE_NAME: ntkrnlmp.exe
BUCKET_ID_FUNC_OFFSET: 24412f
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete
OS_VERSION: 10.0.22621.1
BUILDLAB_STR: ni_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3}
Followup: MachineOwner
---------Detaylı cevap için çok teşekkürler. 2 adet aynı SSD'yi kullanıyorum ve beni hiç üzmemişti. Windows'uum bu iki SSD'de değil, markasını bilmediğim bir M2 SSD'de. Hyper-V'ye WSA kullandığım için ihtiyacım var ama sorun bundan kaynaklanıyorsa kapatabilirim. Yazılımdan kontrol ettim, SSD'ler güncel görünüyor.KERNEL_DATA_INPAGE_ERROR (7a)hatası olan dökümlerde şu sürücüde problem yaşanmış :
Name: vmswitch.sys Info: Microsoft Hyper-V Network Virtualization Service Provider driver Source: Windows Update
KERNEL_DATA_INPAGE_ERROR (7a) için olasılıklar:
- Sistemde anti-virüs var, bu yüzden virüs olma ihtimalini es geçiyorum.
- Windows işletim sistemi ve dosya sistemi bozulmuş olabilir.
- Hyper-V'ye ihtiyacınız yoksa kapatılmalı.
- SSD'lerden birinin arızalı olma ihtimali çok yüksek. Kioxia Exceria modelleri biraz problemliydi :
Böyle bir yorum yapılmış. Genel olarak ömür sorunları da vardı bu modelin.
* SSD'nizin yazılımı yüklü değilse indirip iki SSD için de firmware güncellemesi var mı diye bakar mısınız? Varsa yükleyin.
* Ayrıca bu SSD'lerin S.M.A.R.T. verilerini de gönderir misiniz? Yazılımda olması lazım.
Daha sonra CMD'yi yönetici olarak çalıştırıp aşağıdaki komutları yazın:
SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth
* SSD'nin yazılımında S.M.A.R.T. verileri görünmüyorsa HD Tune ile iki SSD'nizin de "Health" sekmesini ekran görüntüsü olarak paylaşın.
* HD Tune ile "Error Scan" kısmını girip "Quick scan" tiki kapalı olacak şekilde iki SSD'nize de test yapın ve paylaşın.
- BIOS sürümünüz 3810.
- 4004 sürümüne güncelleyin.
- Asus Anakartlarda BIOS Güncelleme | 2023
- BIOS'u güncelledikten sonra BIOS'a girin, F5 tuşuna basın ve gelen "Load optimized defaults?" sorusuna "Yes" deyip BIOS'tan çıkın. BIOS'a tekrar girin ve ayarlarınızı yapın (RAM XMP profili, fan ayarları vs.).
* Sistemde Windows'un Hyper-V (sanallaştırma sistemi) açık. Sanal makine, sanal makine yazılımı, emülatör (BlueStacks vs.) kullanmıyorsanız Hyper-V'yi kapatın. Hyper-V bazı oyunlar ve anti-hileler ile problem çıkarmasıyla ünlü. Ancak bu özelliği kapatmak biraz zorlu olabiliyor. Kapandı sanıyorsunuz ama açık vs. olabiliyor. Kapatmak için tüm yöntemleri deneyin.
Dökümler:
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_PROCESS_DIED (ef) A critical system process died Arguments: Arg1: ffff910486caf140, Process object or thread object Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died. Arg3: ffff910486caf140, The process object that initiated the termination. Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2312 Key : Analysis.Elapsed.mSec Value: 4136 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: 203 Key : Analysis.Init.Elapsed.mSec Value: 1153 Key : Analysis.Memory.CommitPeak.Mb Value: 152 Key : Bugcheck.Code.LegacyAPI Value: 0xef Key : CriticalProcessDied.ExceptionCode Value: 89ee3500 Key : CriticalProcessDied.Process Value: csrss.exe Key : Failure.Bucket Value: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_89ee3500_nt!PspCatchCriticalBreak Key : Failure.Hash Value: {3af5295f-77c6-0c1e-db79-dae4845eef9b} 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 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: ef BUGCHECK_P1: ffff910486caf140 BUGCHECK_P2: 0 BUGCHECK_P3: ffff910486caf140 BUGCHECK_P4: 0 FILE_IN_CAB: 070323-25203-01.dmp PROCESS_NAME: csrss.exe CRITICAL_PROCESS: csrss.exe ERROR_CODE: (NTSTATUS) 0x89ee3500 - <Unable to get error code text> BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: fffffd87`5c3b7d48 fffff804`629b7afb : 00000000`000000ef ffff9104`86caf140 00000000`00000000 ffff9104`86caf140 : nt!KeBugCheckEx fffffd87`5c3b7d50 fffff804`628d5659 : ffff9104`86caf140 fffff804`623381c1 00000000`00000000 fffff804`62337a4b : nt!PspCatchCriticalBreak+0x11b fffffd87`5c3b7de0 fffff804`627a7657 : ffff9104`86caf140 00000000`c0000006 ffff9104`86caf140 00000000`00000001 : nt!PspTerminateAllThreads+0x1d16f1 fffffd87`5c3b7e50 fffff804`627a7431 : ffffffff`ffffffff ffff9104`86caf140 ffff9104`89ee3500 ffff9104`86caf140 : nt!PspTerminateProcess+0xe3 fffffd87`5c3b7e90 fffff804`62440fe8 : 000000c8`00000318 ffff9104`89ee3500 ffff9104`86caf140 fffff804`6294f2e7 : nt!NtTerminateProcess+0xb1 fffffd87`5c3b7f10 fffff804`62431b10 : fffff804`624ced79 ffffffff`ffffffff 000000c8`4b8b13b0 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x28 fffffd87`5c3b80a8 fffff804`624ced79 : ffffffff`ffffffff 000000c8`4b8b13b0 00000000`00000001 fffffd87`5c3b80e0 : nt!KiServiceLinkage fffffd87`5c3b80b0 fffff804`624419fc : 00000000`00000000 00000000`00000000 000006d6`279b4099 00000000`00000000 : nt!KiDispatchException+0x1bb029 fffffd87`5c3b8900 fffff804`6243cf0e : 00000000`00000000 ffffc901`824b9640 000000c8`4b8b1690 ffff9104`00000000 : nt!KiExceptionDispatch+0x13c fffffd87`5c3b8ae0 00007ffb`7c870352 : 00007ffb`79c39364 00007ffb`79c44000 000000c8`4b8b2270 00000000`00000000 : nt!KiPageFault+0x44e 000000c8`4b8b15e0 00007ffb`79c39364 : 00007ffb`79c44000 000000c8`4b8b2270 00000000`00000000 00007ffb`79c44000 : 0x00007ffb`7c870352 000000c8`4b8b15e8 00007ffb`79c44000 : 000000c8`4b8b2270 00000000`00000000 00007ffb`79c44000 00007ffb`79c30000 : 0x00007ffb`79c39364 000000c8`4b8b15f0 000000c8`4b8b2270 : 00000000`00000000 00007ffb`79c44000 00007ffb`79c30000 00000ad4`00019000 : 0x00007ffb`79c44000 000000c8`4b8b15f8 00000000`00000000 : 00007ffb`79c44000 00007ffb`79c30000 00000ad4`00019000 000000c8`4b8b2270 : 0x000000c8`4b8b2270 SYMBOL_NAME: nt!PspCatchCriticalBreak+11b MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1848 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 11b FAILURE_BUCKET_ID: 0xEF_csrss.exe_BUGCHECK_CRITICAL_PROCESS_89ee3500_nt!PspCatchCriticalBreak OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3af5295f-77c6-0c1e-db79-dae4845eef9b} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000006, Exception code that caused the BugCheck Arg2: fffff802284ad88c, Address of the instruction which caused the BugCheck Arg3: ffff858520c60390, Address of the context record for the exception that caused the BugCheck Arg4: 0000000000000000, zero. 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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: 3015 Key : Analysis.Elapsed.mSec Value: 3225 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: 202 Key : Analysis.Init.Elapsed.mSec Value: 991 Key : Analysis.Memory.CommitPeak.Mb Value: 150 Key : Bugcheck.Code.LegacyAPI Value: 0x3b Key : Failure.Bucket Value: 0x3B_C0000006_nt!HvpGetCellPaged Key : Failure.Hash Value: {68f3db38-ae8e-4bae-c37a-85819946495f} 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 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000006 BUGCHECK_P2: fffff802284ad88c BUGCHECK_P3: ffff858520c60390 BUGCHECK_P4: 0 FILE_IN_CAB: 070323-16359-01.dmp CONTEXT: ffff858520c60390 -- (.cxr 0xffff858520c60390) rax=000001ad9f51e000 rbx=00000000026add90 rcx=000001ad9f51ed90 rdx=ffffc90736124038 rsi=ffff858520c60e80 rdi=00000000a88ef046 rip=fffff802284ad88c rsp=ffff858520c60db0 rbp=ffff858520c60ee0 r8=ffff858520c60e84 r9=00000000000000ad r10=ffffc90734878000 r11=0000000003232ff0 r12=00000000a88ef046 r13=ffff858520c61250 r14=000001ada00b9b1c r15=000001ada00b9024 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206 nt!HvpGetCellPaged+0x7c: fffff802`284ad88c 8b01 mov eax,dword ptr [rcx] ds:002b:000001ad`9f51ed90=???????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Registry STACK_TEXT: ffff8585`20c60db0 fffff802`284ac73e : 00000000`a88ef046 00000000`e9c5e935 ffff8585`20c61250 00000000`00000000 : nt!HvpGetCellPaged+0x7c ffff8585`20c60de0 fffff802`284ae577 : ffffc907`5ad26af0 ffff8585`20c61160 ffff8585`20c61060 ffff8585`20c61180 : nt!CmpWalkOneLevel+0x73e ffff8585`20c60f40 fffff802`284b3435 : 00000000`0000001c ffff8585`20c61470 ffff8585`20c613f8 00000000`00000000 : nt!CmpDoParseKey+0x867 ffff8585`20c61380 fffff802`284b79db : fffff802`284b3101 ffffaf0f`00000000 ffffaf0f`acccaaa0 00000000`00000001 : nt!CmpParseKey+0x2e5 ffff8585`20c61570 fffff802`284b6e52 : ffffaf0f`acccaaa0 ffff8585`20c617a0 00000000`00000040 ffffaf0f`9837a6c0 : nt!ObpLookupObjectName+0x63b ffff8585`20c61710 fffff802`284ba184 : 00000000`00000000 ffffaf0f`9837a6c0 00000000`00000000 00000000`00000000 : nt!ObOpenObjectByNameEx+0x1f2 ffff8585`20c61840 fffff802`284bab48 : 00000063`fd27d5a8 00000000`00000000 ffff8585`20c61b60 fffff802`28549d99 : nt!CmOpenKey+0x2c4 ffff8585`20c61a90 fffff802`28240fe8 : ffffaf0f`9f5cb080 00000000`00000000 00000000`000075c0 ffffaf0f`00000000 : nt!NtOpenKeyEx+0x48 ffff8585`20c61ae0 00007ff8`feef1164 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000063`fd27d588 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`feef1164 SYMBOL_NAME: nt!HvpGetCellPaged+7c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1848 STACK_COMMAND: .cxr 0xffff858520c60390 ; kb BUCKET_ID_FUNC_OFFSET: 7c FAILURE_BUCKET_ID: 0x3B_C0000006_nt!HvpGetCellPaged OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {68f3db38-ae8e-4bae-c37a-85819946495f} Followup: MachineOwner --------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: ffffb68f1eb9f228, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000000e, error status (normally i/o status code) Arg3: 00000003ea2f7860, current process (virtual address for lock type 3, or PTE) Arg4: fffff80771e257c0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1655 Key : Analysis.Elapsed.mSec Value: 8716 Key : Analysis.IO.Other.Mb Value: 4 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 4 Key : Analysis.Init.CPU.mSec Value: 218 Key : Analysis.Init.Elapsed.mSec Value: 1101 Key : Analysis.Memory.CommitPeak.Mb Value: 159 Key : Bugcheck.Code.LegacyAPI Value: 0x7a Key : Failure.Bucket Value: 0x7a_c000000e_nt!MiWaitForInPageComplete Key : Failure.Hash Value: {329318b9-5fab-73eb-d104-f79603e1bdb3} 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 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 7a BUGCHECK_P1: ffffb68f1eb9f228 BUGCHECK_P2: ffffffffc000000e BUGCHECK_P3: 3ea2f7860 BUGCHECK_P4: fffff80771e257c0 FILE_IN_CAB: 070223-11828-01.dmp ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi. DISK_HARDWARE_ERROR: There was error with disk hardware BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: fffff38f48b77680 -- (.trap 0xfffff38f48b77680) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff80771e257c0 rbx=0000000000000000 rcx=ffffb68f4cf8b758 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80771e257c0 rsp=fffff38f48b77818 rbp=fffff38f48b778f9 r8=00000000000000ff r9=0000800000000000 r10=0000fffff80771e2 r11=ffff6ffd27200000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy vmswitch!tlgEnableCallback: fffff807`71e257c0 4883ec48 sub rsp,48h Resetting default scope STACK_TEXT: fffff38f`48b77358 fffff807`34e93b3f : 00000000`0000007a ffffb68f`1eb9f228 ffffffff`c000000e 00000003`ea2f7860 : nt!KeBugCheckEx fffff38f`48b77360 fffff807`34c4f46b : 00000000`00000000 fffff38f`00000000 fffff38f`48b77508 fffff807`00000000 : nt!MiWaitForInPageComplete+0x24412f fffff38f`48b77460 fffff807`34c33fb7 : 00000000`c0033333 00000000`00000000 fffff807`71e257c0 fffff807`71e257c0 : nt!MiIssueHardFault+0x1cb fffff38f`48b77560 fffff807`34e3ce29 : 00000000`00000000 ffffb68f`168003b9 00008000`00000000 ffffb68f`4cf891fe : nt!MmAccessFault+0x347 fffff38f`48b77680 fffff807`71e257c0 : fffff807`3515e3cc 00000000`44777445 fffff807`34c85fdf 00000000`000001c0 : nt!KiPageFault+0x369 fffff38f`48b77818 fffff807`3515e3cc : 00000000`44777445 fffff807`34c85fdf 00000000`000001c0 ffff918c`c7f330d8 : vmswitch!tlgEnableCallback fffff38f`48b77820 fffff807`35119d76 : 00000000`00000000 fffff38f`48b77a60 ffffb68f`4cf8b720 ffff918c`c7f330a0 : nt!EtwpSendDataBlock+0x138 fffff38f`48b77960 fffff807`3511817a : ffff8001`92202380 ffff8001`92202380 ffff918c`c7f330a0 ffff918c`c7bce000 : nt!EtwpClearSessionAndUnreferenceEntry+0x296 fffff38f`48b77aa0 fffff807`3518bf04 : fffff807`34a0ebe8 ffff918c`c7bdc600 ffff918c`c7bdc7e0 00000000`00000000 : nt!EtwpDisableTraceProviders+0x4e fffff38f`48b77af0 fffff807`352d9599 : ffff918c`c7bdc600 ffff918c`c7bdc600 ffff918c`c7bdc7e0 ffff918c`c7bdc7c8 : nt!EtwpStopLoggerInstance+0x58 fffff38f`48b77b70 fffff807`34cd8dc7 : ffffffff`fffffffd ffff918c`c7f8d040 00000000`00000080 fffff807`351168e0 : nt!EtwpLogger+0x1c2cb9 fffff38f`48b77bf0 fffff807`34e311e4 : ffff8001`92c51180 ffff918c`c7f8d040 fffff807`34cd8d70 00000000`00000000 : nt!PspSystemThreadStartup+0x57 fffff38f`48b77c40 00000000`00000000 : fffff38f`48b78000 fffff38f`48b72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!MiWaitForInPageComplete+24412f MODULE_NAME: nt IMAGE_VERSION: 10.0.22621.1848 STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 24412f FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3} Followup: MachineOwner --------- ****************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: ffff898d5549a228, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc000000e, error status (normally i/o status code) Arg3: 000000014901a860, current process (virtual address for lock type 3, or PTE) Arg4: fffff8071af457c0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1671 Key : Analysis.Elapsed.mSec Value: 4690 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: 233 Key : Analysis.Init.Elapsed.mSec Value: 1580 Key : Analysis.Memory.CommitPeak.Mb Value: 160 Key : Bugcheck.Code.LegacyAPI Value: 0x7a Key : Failure.Bucket Value: 0x7a_c000000e_nt!MiWaitForInPageComplete Key : Failure.Hash Value: {329318b9-5fab-73eb-d104-f79603e1bdb3} 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 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 7a BUGCHECK_P1: ffff898d5549a228 BUGCHECK_P2: ffffffffc000000e BUGCHECK_P3: 14901a860 BUGCHECK_P4: fffff8071af457c0 FILE_IN_CAB: 070223-19281-01.dmp ERROR_CODE: (NTSTATUS) 0xc000000e - Varolmayan bir ayg t belirtildi. DISK_HARDWARE_ERROR: There was error with disk hardware BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffff85022d777680 -- (.trap 0xffff85022d777680) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff8071af457c0 rbx=0000000000000000 rcx=ffff898da2d710c8 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8071af457c0 rsp=ffff85022d777818 rbp=ffff85022d7778f9 r8=00000000000000ff r9=0000800000000000 r10=0000fffff8071af4 r11=ffffc57c98c00000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy vmswitch!tlgEnableCallback: fffff807`1af457c0 4883ec48 sub rsp,48h Resetting default scope STACK_TEXT: ffff8502`2d777358 fffff807`0b693b3f : 00000000`0000007a ffff898d`5549a228 ffffffff`c000000e 00000001`4901a860 : nt!KeBugCheckEx ffff8502`2d777360 fffff807`0b44f46b : 00000000`00000000 ffff8502`00000000 ffff8502`2d777508 fffff807`00000000 : nt!MiWaitForInPageComplete+0x24412f ffff8502`2d777460 fffff807`0b433fb7 : 00000000`c0033333 00000000`00000000 fffff807`1af457c0 fffff807`1af457c0 : nt!MiIssueHardFault+0x1cb ffff8502`2d777560 fffff807`0b63ce29 : 00000000`00000000 ffff898d`4a2003b9 00008000`00000000 ffff898d`a2d5722e : nt!MmAccessFault+0x347 ffff8502`2d777680 fffff807`1af457c0 : fffff807`0b95e3cc 00000000`44777445 fffff807`0b485fdf 00000000`000001c0 : nt!KiPageFault+0x369 ffff8502`2d777818 fffff807`0b95e3cc : 00000000`44777445 fffff807`0b485fdf 00000000`000001c0 ffffa705`c7332118 : vmswitch!tlgEnableCallback ffff8502`2d777820 fffff807`0b919d76 : 00000000`00000000 ffff8502`2d777a60 ffff898d`a2d71090 ffffa705`c73320e0 : nt!EtwpSendDataBlock+0x138 ffff8502`2d777960 fffff807`0b91817a : ffffd581`57202380 ffffd581`57202380 ffffa705`c73320e0 ffffa705`c5fc8000 : nt!EtwpClearSessionAndUnreferenceEntry+0x296 ffff8502`2d777aa0 fffff807`0b98bf04 : fffff807`0b20ebe8 ffffa705`c5fd7600 ffffa705`c5fd77e0 00000000`00000000 : nt!EtwpDisableTraceProviders+0x4e ffff8502`2d777af0 fffff807`0bad9599 : ffffa705`c5fd7600 ffffa705`c5fd7600 ffffa705`c5fd77e0 ffffa705`c5fd77c8 : nt!EtwpStopLoggerInstance+0x58 ffff8502`2d777b70 fffff807`0b4d8dc7 : ffffffff`fffffffd ffffa705`c5fd9040 00000000`00000080 fffff807`0b9168e0 : nt!EtwpLogger+0x1c2cb9 ffff8502`2d777bf0 fffff807`0b6311e4 : ffffd581`57c51180 ffffa705`c5fd9040 fffff807`0b4d8d70 00000000`00000000 : nt!PspSystemThreadStartup+0x57 ffff8502`2d777c40 00000000`00000000 : ffff8502`2d778000 ffff8502`2d772000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!MiWaitForInPageComplete+24412f MODULE_NAME: nt IMAGE_VERSION: 10.0.22621.1848 STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 24412f FAILURE_BUCKET_ID: 0x7a_c000000e_nt!MiWaitForInPageComplete OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {329318b9-5fab-73eb-d104-f79603e1bdb3} Followup: MachineOwner ---------
Diğer 2 SSD'nizden önce bu SSD'ye odaklanalım o zaman.Markasını bilmediğim bir M2 SSD'de.
Şimdilik kapatmayın, Hyper-V ile alakalı problemler var gibi ama sorun M.2 SSD'nizde ise suçu Hyper-V'ye ve onun yazılımlarına atıyor olabilir. Mavi ekranlar depolama kaynaklı görünüyor çünkü.Hyper-V'ye WSA kullandığım için ihtiyacım var ama sorun bundan kaynaklanıyorsa kapatabilirim.
Tekrardan selam. BIOS'umu yükselttim.Diğer 2 SSD'nizden önce bu SSD'ye odaklanalım o zaman.
- Bu SSD'niz için de HD Tune'dan Health sekmesini paylaşır mısınız?
- Ayrıca Quick Scan kapalı olacak şekilde Error Scan yapın.
- İşletim sisteminin kurulu olduğu SSD'de problem olması daha yüksek.
Şimdilik kapatmayın, Hyper-V ile alakalı problemler var gibi ama sorun M.2 SSD'nizde ise suçu Hyper-V'ye ve onun yazılımlarına atıyor olabilir. Mavi ekranlar depolama kaynaklı görünüyor çünkü.
chkdsk /f /rSonuç bu şekilde. Kodu da yazdım.O zaman sadece Quick Scan tiki kapalı olacak şekilde Error Scan yapmayı dener misiniz?
Bir de CMD'yi yönetici olarak çalıştırıp şunu da yazın, gelen soruya Y deyip enterlayın, PC'yi yeniden başlatın. Tarama yapsın.
chkdsk /f /r
Herhangi bir sorun yok mu hocam? Hyper-V'yi ne yapayım ve Health sekmesi neden açılmadı? Ayrıca dediğim gibi aldığım tüm mavi ekranları Edge'de aldım.Tamamdır. Tekrar mavi ekran alırsanız yeni dökümleri paylaşırsınız.