sfc /scannowDISM.exe /Online /Cleanup-image /ScanHealthDISM /Online /Cleanup-Image /RestoreHealth
www.asus.com
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8001f771293, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000026099164, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 10843
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 26492
Key : Analysis.IO.Other.Mb
Value: 4
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 7
Key : Analysis.Init.CPU.mSec
Value: 1640
Key : Analysis.Init.Elapsed.mSec
Value: 23576
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Bugcheck.Code.DumpHeader
Value: 0x1e
Key : Bugcheck.Code.Register
Value: 0x1e
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 043023-27625-01.dmp
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8001f771293
BUGCHECK_P3: 0
BUGCHECK_P4: 26099164
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000026099164
READ_ADDRESS: fffff8001b4fb390: 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
0000000026099164
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: ShellExperienceHost.exe
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
STACK_TEXT:
ffffd18a`6f9a4e08 fffff800`1ac60cd3 : 00000000`0000001e ffffffff`c0000005 fffff800`1f771293 00000000`00000000 : nt!KeBugCheckEx
ffffd18a`6f9a4e10 fffff800`1ac0fe6c : 00000000`00001000 ffffd18a`6f9a56b0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1795c3
ffffd18a`6f9a54d0 fffff800`1ac0b8bd : ffffd486`8745d340 ffffd486`94398270 ffffd486`9180a660 ffffe507`1b840018 : nt!KiExceptionDispatch+0x12c
ffffd18a`6f9a56b0 fffff800`1f771293 : fffff800`1aa3f643 00000000`00000000 00000000`00000000 00020000`0001a4fc : nt!KiPageFault+0x43d
ffffd18a`6f9a5848 fffff800`1aa3f643 : 00000000`00000000 00000000`00000000 00020000`0001a4fc ffffd18a`6f9a5a44 : Ntfs!NtfsFcbTableCompare+0x3
ffffd18a`6f9a5850 fffff800`1f764fa4 : 00020000`0001a4fc ffffe507`1b840101 ffffd18a`6f9a5a44 00000000`00000000 : nt!RtlLookupElementGenericTableFullAvl+0x53
ffffd18a`6f9a5880 fffff800`1f706ffd : ffff888e`6ef40848 ffff888e`5e70a180 00000000`00000000 00020000`0001a4fc : Ntfs!NtfsCreateFcb+0xd4
ffffd18a`6f9a59c0 fffff800`1f7213a2 : ffff888e`6ef40848 ffffd486`9180a7c0 ffffd486`8745d340 ffffd18a`6776f1f0 : Ntfs!NtfsOpenFile+0x27d
ffffd18a`6f9a5c70 fffff800`1f74ded2 : 00000000`00000000 ffffd18a`6776ef60 ffffd18a`6776ee00 00000000`00000000 : Ntfs!NtfsCommonCreate+0xf52
ffffd18a`6f9a5f50 fffff800`1ac0030e : ffffd18a`6776f0a0 ffffd18a`6f9a5fd0 00000000`00000000 00000000`0a15fa88 : Ntfs!NtfsCommonCreateCallout+0x22
ffffd18a`6f9a5f80 fffff800`1ac002cc : ffffd18a`6f9a5fd0 ffff888e`75425080 ffffd18a`6f9a6000 fffff800`1aaad7dd : nt!KxSwitchKernelStackCallout+0x2e
ffffd18a`6776ee90 fffff800`1aaad7dd : ffffd18a`6f9a5fd0 ffff888e`75425080 ffffd18a`6776ef00 ffff888e`73bed0b0 : nt!KiSwitchKernelStackContinue
ffffd18a`6776eeb0 fffff800`1aaad5d2 : fffff800`1f74deb0 ffffd18a`6776f0a0 ffff888e`00000002 fffff800`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d
ffffd18a`6776ef50 fffff800`1aaad433 : 00000000`00000008 ffffd18a`6776f1f0 00000000`00000000 ffff888e`65132b20 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2
ffffd18a`6776efc0 fffff800`1aaad3ed : fffff800`1f74deb0 ffffd18a`6776f0a0 ffff888e`65132b20 ffffd18a`6776b000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffffd18a`6776f030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d
SYMBOL_NAME: Ntfs!NtfsFcbTableCompare+3
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
IMAGE_VERSION: 10.0.19041.1223
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 3
FAILURE_BUCKET_ID: AV_R_Ntfs!NtfsFcbTableCompare
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {2482ebef-4022-bcb1-ea20-e29e5ed74842}
Followup: MachineOwner
---------
Disk testi yapın.
Disk testi yapmak
Sizden disk testi istediğim zaman bu rehbere göre disk testi yapıp sonucu gönderebilirsiniz. SSD için aşağıdaki 2 aracı kullanın. https://www.hdsentinel.com/ > Sağlık durumunu gönderin. https://www.guru3d.com/files-details/as-ssd-benchmark.html > Okuma yazma hızını gönderin. HDD için ise health...www.technopat.net
Hocam biraz düşündüm de karar veremedim. Sizce RAM testi de yapmalı mı?
Ben de öyle düşünüyorum ama sizinde fikrinizi sorayım dedim.NTFS.sys genellikle HDD veya SSD ile alakalı bir sorun varsa meydana gelmektedir. İlk önce disk testi yapılması gerekli duruma göre RAM testi yapılabilir ama RAM'lerde bir sorun olacağını şimdilik düşünmüyorum.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.