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: fffff807258ddd37, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6530
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 10724
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff807258ddd37
BUGCHECK_P3: 0
BUGCHECK_P4: ffffffffffffffff
READ_ADDRESS: fffff807216fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8072160f330: Unable to get Flags value from nt!KdVersionBlock
fffff8072160f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff
EXCEPTION_PARAMETER2: ffffffffffffffff
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
STACK_TEXT:
ffff9c82`119a2048 fffff807`20e9128d : 00000000`0000001e ffffffff`c0000005 fffff807`258ddd37 00000000`00000000 : nt!KeBugCheckEx
ffff9c82`119a2050 fffff807`20e078ac : 00000007`cf664000 00000001`20c50cb9 ffffb381`62f5c180 ffff9c82`00000000 : nt!KiDispatchException+0x16688d
ffff9c82`119a2710 fffff807`20e035e0 : ffff820f`bc5c40f8 00000000`6c526d4d 00000000`00000000 ffff820f`bc5c4148 : nt!KiExceptionDispatch+0x12c
ffff9c82`119a28f0 fffff807`258ddd37 : ffff820f`b7cca8d0 ffff820f`c7ce1730 fffff807`20c60c8b ffff820f`c7ce1730 : nt!KiGeneralProtectionFault+0x320
ffff9c82`119a2a88 ffffe000`c2b077c0 : 0000000b`ffffff01 ffff9c82`119a3080 ffff9c82`119a2de0 00000000`00000000 : Ntfs!NtfsFindPrefixHashEntry+0xc7
ffff9c82`119a2bb8 0000000b`ffffff01 : ffff9c82`119a3080 ffff9c82`119a2de0 00000000`00000000 ffff820f`bed5a0f8 : 0xffffe000`c2b077c0
ffff9c82`119a2bc0 ffff9c82`119a3080 : ffff9c82`119a2de0 00000000`00000000 ffff820f`bed5a0f8 ffffe000`c50cd201 : 0x0000000b`ffffff01
ffff9c82`119a2bc8 ffff9c82`119a2de0 : 00000000`00000000 ffff820f`bed5a0f8 ffffe000`c50cd201 ffff820f`b7e18180 : 0xffff9c82`119a3080
ffff9c82`119a2bd0 00000000`00000000 : ffff820f`bed5a0f8 ffffe000`c50cd201 ffff820f`b7e18180 00000000`00000000 : 0xffff9c82`119a2de0
SYMBOL_NAME: Ntfs!NtfsFindPrefixHashEntry+c7
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: c7
FAILURE_BUCKET_ID: 0x1E_c0000005_R_Ntfs!NtfsFindPrefixHashEntry
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {90eb9ea8-e04d-aac9-0d0e-f8123034075a}
Followup: MachineOwner
---------
Dün bilgisayarcı RAM'leri takarken dedim ki abi bu anakartların önerilen RAM dizilimi vesaire var ona dikkat ettin mi dedim, etmez miyim kardeşim bak bu A1 B1 takılır falan dedi. Bugün baktım anakartın kılavuzuna A2 B2 diyordu, düzelttim RAM slotlarını. Şu an Valorant'ta bir el attım sorunsuz tamamladım, FPS değerleri mükemmel derecede arttı. İnşallah mavi ekranla karşılaşmadan devam ederiz. 
![[BlittCher]](https://www.technopat.net/sosyal/data/avatars/s/280/280900.jpg?1591207421){kind=avatar}
