Mavi Ekran Mavi ekran hatası alıyorum.

@Altotziki

Şuanda bilgisayarda olmadığım için kusura bakmayın göremiyorum dmp dosyasının içeriğini.


Bu uygulamayı indirin sonra minidump dosyasını bu uygulama aracılığıyla açın.

Bir süre bekleyin sonra orada yazılar akacak. Sonrasında mavi renkli üzerine tıklanılabilen bir yazı çıkacak. Ona tıklayın ve bekleyin.

Sonrasında sonuna kadar bekleyerek oradaki hata sebepleri yazacak. Orayı kopyalayıp buraya yapıştırın.
 
@Altotziki

Şuanda bilgisayarda olmadığım için kusura bakmayın göremiyorum dmp dosyasının içeriğini.


Bu uygulamayı indirin sonra minidump dosyasını bu uygulama aracılığıyla açın.

Bir süre bekleyin sonra orada yazılar akacak. Sonrasında mavi renkli üzerine tıklanılabilen bir yazı çıkacak. Ona tıklayın ve bekleyin.

Sonrasında sonuna kadar bekleyerek oradaki hata sebepleri yazacak. Orayı kopyalayıp buraya yapıştırın.
Hocam Microsoft store bu uygulamada bulanamadı hatası veriyor indiremiyorum yani başka altarnatif link var mıdır?
 
Hocam Microsoft store bu uygulamada bulanamadı hatası veriyor indiremiyorum yani başka altarnatif link var mıdır?
Microsoft store üzerinden windbg uygulamasını arayın.
 
PAGE_FAULT_IN_NONPAGED_AREA (50)1. Mavi ekran hatası adı buda fotosu
Ekran Alıntısı1.PNG

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)2. Mavi ekran hatası adı buda fotosu
Ekran Alıntısı2.PNG

SYSTEM_SERVICE_EXCEPTION (3b)3. Mavi ekran hatası adı buda fotosu
Ekran Alıntısı3.PNG

Mesajlar otomatik olarak birleştirildi:

Microsoft store üzerinden windbg uygulamasını arayın.
Mağaza önbelleğini temizlemem gerekiyordu yaptım çalıştı, belki ihtiyacı olan olur yazayım burayada. WSReset.exe bunu çalıştıra yazacaksınız ve bekleyeceksiniz.
 
Baştan sona kopyala yapıştır yapın. Bu şekilde çok aşırı işe yaramaz.
 
Baştan sona kopyala yapıştır yapın. Bu şekilde çok aşırı işe yaramaz.

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


Loading Dump File [C:\Users\Şehri KARAHAN\Desktop\Yeni klasör\022522-18687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`0bc00000 PsLoadedModuleList = 0xfffff805`0c82a2d0
Debug session time: Fri Feb 25 15:01:30.253 2022 (UTC + 3:00)
System Uptime: 0 days 0:52:51.920
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`0bff7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc784`2e68a6c0=000000000000003b
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80519e578fa, Address of the instruction which caused the BugCheck
Arg3: ffffc7842e68afc0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4718

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 45066

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

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

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

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: 022522-18687-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80519e578fa

BUGCHECK_P3: ffffc7842e68afc0

BUGCHECK_P4: 0

CONTEXT: ffffc7842e68afc0 -- (.cxr 0xffffc7842e68afc0)
rax=0000000000000000 rbx=ffffc7842e68ba60 rcx=0000000000000000
rdx=ffffc7842e68bae0 rsi=0000000000000000 rdi=000000baf5e9e460
rip=fffff80519e578fa rsp=ffffc7842e68b9c0 rbp=ffffc7842e68bb80
r8=0000000000000000 r9=7fffa307ab219ea0 r10=0000fffff8051b8c
r11=ffffbf7eb5c00000 r12=000002b8e7f916a0 r13=ffffc7842e68ba68
r14=ffffffffffffffff r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
dxgkrnl!DxgkGetDeviceStateInternal+0x2ca:
fffff805`19e578fa 84c0 test al,al
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffc784`2e68b9c0 fffff805`19e57614 : 000000ba`f5e9e460 000002b8`e7d448c8 ffffa237`00000000 ffffa307`abcaa010 : dxgkrnl!DxgkGetDeviceStateInternal+0x2ca
ffffc784`2e68bad0 fffff805`0c008fb8 : ffffe186`98a73080 ffffe186`96b9f000 ffffe186`96b9f000 00000000`c0004b40 : dxgkrnl!DxgkGetDeviceState+0x24
ffffc784`2e68bb00 00007ff9`31694d44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000ba`f5e9e438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`31694d44


SYMBOL_NAME: dxgkrnl!DxgkGetDeviceStateInternal+2ca

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.1554

STACK_COMMAND: .cxr 0xffffc7842e68afc0 ; kb

BUCKET_ID_FUNC_OFFSET: 2ca

FAILURE_BUCKET_ID: AV_dxgkrnl!DxgkGetDeviceStateInternal

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {87d91068-d3aa-df73-039a-ff85f31d4f64}

Followup: MachineOwner
---------
 
Sorun ramlerde gözüküyor.

Memtest86 testi yapın.eğer hata verirse xmp kapatın birde öyle deneyin.

Eğer yine hata veriyorsa ramlerin yuvasını değiştirin.
 
Baştan sona kopyala yapıştır yapın. Bu şekilde çok aşırı işe yaramaz.

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


Loading Dump File [C:\Users\Şehri KARAHAN\Desktop\Yeni klasör\022522-18703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`39400000 PsLoadedModuleList = 0xfffff805`3a02a2d0
Debug session time: Fri Feb 25 16:20:01.031 2022 (UTC + 3:00)
System Uptime: 0 days 1:18:04.698
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`397f7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffee8f`2020d570=0000000000000050
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff805360226dd, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 4140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9946

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

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

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

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: 022522-18703-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffffffffffffd0

BUGCHECK_P2: 0

BUGCHECK_P3: fffff805360226dd

BUGCHECK_P4: 2

READ_ADDRESS: fffff8053a0fa390: 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
ffffffffffffffd0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffee8f2020d810 -- (.trap 0xffffee8f2020d810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd981aca50d70
rdx=ffffd981aca50de8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805360226dd rsp=ffffee8f2020d9a0 rbp=ffffd981aca50de8
r8=0000000000000000 r9=0000000000000000 r10=fffff80539723e60
r11=ffffc40774fd28d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+0xb5:
fffff805`360226dd 4d8b51d0 mov r10,qword ptr [r9-30h] ds:ffffffff`ffffffd0=????????????????
Resetting default scope

STACK_TEXT:
ffffee8f`2020d568 fffff805`3984a86f : 00000000`00000050 ffffffff`ffffffd0 00000000`00000000 ffffee8f`2020d810 : nt!KeBugCheckEx
ffffee8f`2020d570 fffff805`3969f540 : ffffc407`74fd36b0 00000000`00000000 ffffee8f`2020d890 00000000`00000000 : nt!MiSystemFault+0x18d30f
ffffee8f`2020d670 fffff805`3980575e : ffffc407`00000000 ffffee8f`2020d860 00000000`00000000 ffffd981`ae95dee0 : nt!MmAccessFault+0x400
ffffee8f`2020d810 fffff805`360226dd : ffffd981`aca50c80 ffffd981`00000001 ffff1365`00000000 ffffd981`aca50cb8 : nt!KiPageFault+0x35e
ffffee8f`2020d9a0 fffff805`3602c67d : ffffd981`ae95deb0 ffffee8f`2020db00 ffffd981`ae95dee0 00000000`00000002 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+0xb5
ffffee8f`2020da00 fffff805`36036809 : ffffd981`ab18b020 ffffc407`74fd5001 00000000`00000000 00000000`0af3d300 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe7d
ffffee8f`2020dbe0 fffff805`39755a05 : ffffc407`74fd5080 fffff805`36036800 ffffd981`ab18b020 000f8067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffee8f`2020dc10 fffff805`397fec68 : ffffb201`cfd89180 ffffc407`74fd5080 fffff805`397559b0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffee8f`2020dc60 00000000`00000000 : ffffee8f`2020e000 ffffee8f`20208000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+b5

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1554

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b5

FAILURE_BUCKET_ID: AV_R_(null)_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fef7f818-ce9b-5082-ec31-33dc272aa498}

Followup: MachineOwner
---------
Mesajlar otomatik olarak birleştirildi:

Sorun ramlerde gözüküyor.

Memtest86 testi yapın.eğer hata verirse xmp kapatın birde öyle deneyin.

Eğer yine hata veriyorsa ramlerin yuvasını değiştirin.

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


Loading Dump File [C:\Users\Şehri KARAHAN\Desktop\Yeni klasör\022522-21671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`7e800000 PsLoadedModuleList = 0xfffff805`7f42a2d0
Debug session time: Fri Feb 25 16:36:32.265 2022 (UTC + 3:00)
System Uptime: 0 days 0:16:04.932
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`7ebf7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffaf0a`36f0ed60=000000000000003b
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff80583e206fa, Address of the instruction which caused the BugCheck
Arg3: ffffaf0a36f0f660, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3983

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7026

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

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

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

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: 022522-21671-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80583e206fa

BUGCHECK_P3: ffffaf0a36f0f660

BUGCHECK_P4: 0

CONTEXT: ffffaf0a36f0f660 -- (.cxr 0xffffaf0a36f0f660)
rax=0000000000000001 rbx=ffffaf0a36f10280 rcx=0000000000000000
rdx=0000000000000001 rsi=ffffb387ba9fa2f0 rdi=0000000000000000
rip=fffff80583e206fa rsp=ffffaf0a36f10060 rbp=ffffaf0a36f100e0
r8=0000000000000000 r9=7fffb387ba9fa310 r10=0000000000000000
r11=0000000000000000 r12=ffffaf0a36f10301 r13=0000000000000000
r14=ffffda02ac31e298 r15=ffffaf0a36f10188
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
Ntfs!NtfsBuildMappingPairs+0x92:
fffff805`83e206fa 488b55f0 mov rdx,qword ptr [rbp-10h] ss:0018:ffffaf0a`36f100d0=0000000000000000
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffffaf0a`36f10060 fffff805`83e2c93d : ffff9e81`e88c2108 ffffaf0a`36f10280 ffff9e81`00000000 ffffda02`a46fc180 : Ntfs!NtfsBuildMappingPairs+0x92
ffffaf0a`36f10110 fffff805`83e0e36f : 00000000`00000000 ffffda02`ac31e298 ffffda02`ac31e298 00000000`00000000 : Ntfs!NtfsAddAttributeAllocation+0x4ed
ffffaf0a`36f10310 fffff805`83d27bd3 : ffffda02`ac31e298 ffffda02`afb79ed0 ffffb387`ba9fa170 00000000`00000000 : Ntfs!NtfsAddAllocation+0x2f3
ffffaf0a`36f10450 fffff805`83d1aeff : 00000000`00000000 ffffaf0a`36f10700 ffffda02`ac31e298 00000000`00000000 : Ntfs!NtfsAddAllocationForNonResidentWrite+0xab
ffffaf0a`36f104a0 fffff805`83d177c3 : ffffda02`ac31e298 ffffda02`acd05010 ffffaf0a`36f10740 00000000`00000000 : Ntfs!NtfsCommonWrite+0x32cf
ffffaf0a`36f106d0 fffff805`7ea8f825 : ffffda02`aefc17e0 ffffda02`acd05010 ffffda02`acd05010 ffffda02`a4380d60 : Ntfs!NtfsFsdWrite+0x1d3
ffffaf0a`36f107a0 fffff805`7cb56fcf : 00000000`00000005 00000000`00000000 ffffda02`afb79ea0 ffffda02`a0aff2a0 : nt!IofCallDriver+0x55
ffffaf0a`36f107e0 fffff805`7cb54663 : ffffaf0a`36f10870 00000000`00000000 ffffda02`afa7cb01 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffffaf0a`36f10850 fffff805`7ea8f825 : ffffda02`acd05010 00000000`00000810 00000000`00000000 00000000`00f800ea : FLTMGR!FltpDispatch+0xa3
ffffaf0a`36f108b0 fffff805`7ee76968 : 00000000`00000001 ffffda02`afb79ed0 00000000`00000001 ffffda02`acd053f8 : nt!IofCallDriver+0x55
ffffaf0a`36f108f0 fffff805`7ee8cb7f : ffffda02`00000000 ffffaf0a`36f10b80 000000e1`eabfee50 ffffaf0a`36f10b80 : nt!IopSynchronousServiceTail+0x1a8
ffffaf0a`36f10990 fffff805`7ec08fb8 : 00000000`00000834 00000000`00000000 00000000`00000000 000000e1`eabfee90 : nt!NtWriteFile+0x66f
ffffaf0a`36f10a90 00007ffb`2592ce74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000e1`eabfedd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`2592ce74


SYMBOL_NAME: Ntfs!NtfsBuildMappingPairs+92

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.19041.1554

STACK_COMMAND: .cxr 0xffffaf0a36f0f660 ; kb

BUCKET_ID_FUNC_OFFSET: 92

FAILURE_BUCKET_ID: 0x3B_C000001D_Ntfs!NtfsBuildMappingPairs

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4d04074f-9049-586c-47d2-ed3e815813ef}

Followup: MachineOwner
---------
Mesajlar otomatik olarak birleştirildi:

Sorun ramlerde gözüküyor.

Memtest86 testi yapın.eğer hata verirse xmp kapatın birde öyle deneyin.

Eğer yine hata veriyorsa ramlerin yuvasını değiştirin.
Hocam xmp açık değil ramlerin stok hızı 2666mhz ben 2933mhz çektim manuel overcloke ile 1aya yakındır kullanıyordum bugün stoka çektim sonra yine 2933e çektim bir şey denemek için ondan sonra böyle olmaya başladı ramleri mi bozdum yani?
 
Son düzenleme:
Sorun ramlerde gözüküyor.

Memtest86 testi yapın.eğer hata verirse xmp kapatın birde öyle deneyin.

Eğer yine hata veriyorsa ramlerin yuvasını değiştirin.
Mesajlar otomatik olarak birleştirildi:

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


Loading Dump File [C:\Users\Şehri KARAHAN\Desktop\Yeni klasör\022522-18703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`39400000 PsLoadedModuleList = 0xfffff805`3a02a2d0
Debug session time: Fri Feb 25 16:20:01.031 2022 (UTC + 3:00)
System Uptime: 0 days 1:18:04.698
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`397f7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffee8f`2020d570=0000000000000050
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff805360226dd, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : AV.Type
Value: Read

Key : Analysis.CPU.mSec
Value: 4140

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9946

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

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

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

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: 022522-18703-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffffffffffffd0

BUGCHECK_P2: 0

BUGCHECK_P3: fffff805360226dd

BUGCHECK_P4: 2

READ_ADDRESS: fffff8053a0fa390: 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
ffffffffffffffd0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffee8f2020d810 -- (.trap 0xffffee8f2020d810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd981aca50d70
rdx=ffffd981aca50de8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805360226dd rsp=ffffee8f2020d9a0 rbp=ffffd981aca50de8
r8=0000000000000000 r9=0000000000000000 r10=fffff80539723e60
r11=ffffc40774fd28d8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+0xb5:
fffff805`360226dd 4d8b51d0 mov r10,qword ptr [r9-30h] ds:ffffffff`ffffffd0=????????????????
Resetting default scope

STACK_TEXT:
ffffee8f`2020d568 fffff805`3984a86f : 00000000`00000050 ffffffff`ffffffd0 00000000`00000000 ffffee8f`2020d810 : nt!KeBugCheckEx
ffffee8f`2020d570 fffff805`3969f540 : ffffc407`74fd36b0 00000000`00000000 ffffee8f`2020d890 00000000`00000000 : nt!MiSystemFault+0x18d30f
ffffee8f`2020d670 fffff805`3980575e : ffffc407`00000000 ffffee8f`2020d860 00000000`00000000 ffffd981`ae95dee0 : nt!MmAccessFault+0x400
ffffee8f`2020d810 fffff805`360226dd : ffffd981`aca50c80 ffffd981`00000001 ffff1365`00000000 ffffd981`aca50cb8 : nt!KiPageFault+0x35e
ffffee8f`2020d9a0 fffff805`3602c67d : ffffd981`ae95deb0 ffffee8f`2020db00 ffffd981`ae95dee0 00000000`00000002 : dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+0xb5
ffffee8f`2020da00 fffff805`36036809 : ffffd981`ab18b020 ffffc407`74fd5001 00000000`00000000 00000000`0af3d300 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xe7d
ffffee8f`2020dbe0 fffff805`39755a05 : ffffc407`74fd5080 fffff805`36036800 ffffd981`ab18b020 000f8067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffee8f`2020dc10 fffff805`397fec68 : ffffb201`cfd89180 ffffc407`74fd5080 fffff805`397559b0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffee8f`2020dc60 00000000`00000000 : ffffee8f`2020e000 ffffee8f`20208000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange+b5

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.1554

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: b5

FAILURE_BUCKET_ID: AV_R_(null)_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::CheckBudgetRefreshConditionOnProcessMemoryChange

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fef7f818-ce9b-5082-ec31-33dc272aa498}

Followup: MachineOwner
---------
Mesajlar otomatik olarak birleştirildi:



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


Loading Dump File [C:\Users\Şehri KARAHAN\Desktop\Yeni klasör\022522-21671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`7e800000 PsLoadedModuleList = 0xfffff805`7f42a2d0
Debug session time: Fri Feb 25 16:36:32.265 2022 (UTC + 3:00)
System Uptime: 0 days 0:16:04.932
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`7ebf7610 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffaf0a`36f0ed60=000000000000003b
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff80583e206fa, Address of the instruction which caused the BugCheck
Arg3: ffffaf0a36f0f660, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3983

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7026

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

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

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

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: 022522-21671-01.dmp

BUGCHECK_CODE: 3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff80583e206fa

BUGCHECK_P3: ffffaf0a36f0f660

BUGCHECK_P4: 0

CONTEXT: ffffaf0a36f0f660 -- (.cxr 0xffffaf0a36f0f660)
rax=0000000000000001 rbx=ffffaf0a36f10280 rcx=0000000000000000
rdx=0000000000000001 rsi=ffffb387ba9fa2f0 rdi=0000000000000000
rip=fffff80583e206fa rsp=ffffaf0a36f10060 rbp=ffffaf0a36f100e0
r8=0000000000000000 r9=7fffb387ba9fa310 r10=0000000000000000
r11=0000000000000000 r12=ffffaf0a36f10301 r13=0000000000000000
r14=ffffda02ac31e298 r15=ffffaf0a36f10188
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
Ntfs!NtfsBuildMappingPairs+0x92:
fffff805`83e206fa 488b55f0 mov rdx,qword ptr [rbp-10h] ss:0018:ffffaf0a`36f100d0=0000000000000000
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffffaf0a`36f10060 fffff805`83e2c93d : ffff9e81`e88c2108 ffffaf0a`36f10280 ffff9e81`00000000 ffffda02`a46fc180 : Ntfs!NtfsBuildMappingPairs+0x92
ffffaf0a`36f10110 fffff805`83e0e36f : 00000000`00000000 ffffda02`ac31e298 ffffda02`ac31e298 00000000`00000000 : Ntfs!NtfsAddAttributeAllocation+0x4ed
ffffaf0a`36f10310 fffff805`83d27bd3 : ffffda02`ac31e298 ffffda02`afb79ed0 ffffb387`ba9fa170 00000000`00000000 : Ntfs!NtfsAddAllocation+0x2f3
ffffaf0a`36f10450 fffff805`83d1aeff : 00000000`00000000 ffffaf0a`36f10700 ffffda02`ac31e298 00000000`00000000 : Ntfs!NtfsAddAllocationForNonResidentWrite+0xab
ffffaf0a`36f104a0 fffff805`83d177c3 : ffffda02`ac31e298 ffffda02`acd05010 ffffaf0a`36f10740 00000000`00000000 : Ntfs!NtfsCommonWrite+0x32cf
ffffaf0a`36f106d0 fffff805`7ea8f825 : ffffda02`aefc17e0 ffffda02`acd05010 ffffda02`acd05010 ffffda02`a4380d60 : Ntfs!NtfsFsdWrite+0x1d3
ffffaf0a`36f107a0 fffff805`7cb56fcf : 00000000`00000005 00000000`00000000 ffffda02`afb79ea0 ffffda02`a0aff2a0 : nt!IofCallDriver+0x55
ffffaf0a`36f107e0 fffff805`7cb54663 : ffffaf0a`36f10870 00000000`00000000 ffffda02`afa7cb01 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffffaf0a`36f10850 fffff805`7ea8f825 : ffffda02`acd05010 00000000`00000810 00000000`00000000 00000000`00f800ea : FLTMGR!FltpDispatch+0xa3
ffffaf0a`36f108b0 fffff805`7ee76968 : 00000000`00000001 ffffda02`afb79ed0 00000000`00000001 ffffda02`acd053f8 : nt!IofCallDriver+0x55
ffffaf0a`36f108f0 fffff805`7ee8cb7f : ffffda02`00000000 ffffaf0a`36f10b80 000000e1`eabfee50 ffffaf0a`36f10b80 : nt!IopSynchronousServiceTail+0x1a8
ffffaf0a`36f10990 fffff805`7ec08fb8 : 00000000`00000834 00000000`00000000 00000000`00000000 000000e1`eabfee90 : nt!NtWriteFile+0x66f
ffffaf0a`36f10a90 00007ffb`2592ce74 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000e1`eabfedd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`2592ce74


SYMBOL_NAME: Ntfs!NtfsBuildMappingPairs+92

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

IMAGE_VERSION: 10.0.19041.1554

STACK_COMMAND: .cxr 0xffffaf0a36f0f660 ; kb

BUCKET_ID_FUNC_OFFSET: 92

FAILURE_BUCKET_ID: 0x3B_C000001D_Ntfs!NtfsBuildMappingPairs

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4d04074f-9049-586c-47d2-ed3e815813ef}

Followup: MachineOwner
---------
Mesajlar otomatik olarak birleştirildi:


Hocam xmp açık değil ramlerin stok hızı 2666mhz ben 2933mhz çektim manuel overcloke ile 1aya yakındır kullanıyordum bugün stoka çektim sonra yine 2933e çektim bir şey denemek için ondan sonra böyle olmaya başladı ramleri mi bozdum yani?
Hayır bozmadınız. Sadece anakart uygun değeri giremediği bizden olur. OC değerlerini iyi ayarlayın.
 
Mesajlar otomatik olarak birleştirildi:


Hayır bozmadınız. Sadece anakart uygun değeri giremediği bizden olur. OC değerlerini iyi ayarlayın.
Ayarlanıcak bir şey yok hocam anakart default voktajda 2933 hızında sıkıntı çıkarmıyor yani tek yaptığım 2666mhz 2933 yapmak sıkıntı yapmaya devam ederse stok ayara çekicem bahsettiğiniz program çok uzun sürdüğü için windowstan bellek tanılama yapıyorum bakayım o hata bulucak mı mesela youtubedan video izlerken video bir hata kodu ile kapanıyor ilginç gerçekten.
 
Yeni mesajlar Yeni Konu Aç  

   

SON KONULAR

Forum istatistikleri

Konular
1,185,094
Mesajlar
10,683,986
Üyeler
188,033
Son üye
MahmutTuncer8368
Geri
Top