SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M hatası

H4C1..

Decapat
Katılım
4 Mart 2019
Mesajlar
27
Merhaba iyi günler. Dün yeni bir sistem topladım. Birkaç bir sorun yoktu driverları yükledikten sonra mavi ekran vermeye başladı. Bu benim 4. sistemim. Sistem özellikleri:
  • Ryzen5 3500.
  • Gigabyte B450 auros Elite.
  • Corsair 3200MHz 8*2 GB RAM.
  • RTX2070 ekran kartı.
  • Samsung 860Evo 500GB.

Sistemde sürekli mavi ekran alıyorum. Bazen 5 dakika sonra bazen 20 dakika bazen açılır açılmaz.
RAM'leri çıkardım taktım, yerlerini değiştirdim. Tek RAM ile deneme bile yaptım. PC'ye format attım ama maalesef sorun çözülmedi. Minidump dosyaları elimde. Yardımcı olur musunuz? Teşekkürler.


Edit: İndir Minidump rar
 
Ekran kartınızda sorun olma ihtimali var. Modelini belirtin. Ayrıca bir de bellek testi yapın:


Ekran kartını da OCCT ile test edebilirsiniz:


Kod:
KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffff9f8246495080, The address of the thread.
Arg2: ffffc60f35cae1b8, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 6217

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 17159

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 192

BUGCHECK_P1: ffff9f8246495080

BUGCHECK_P2: ffffc60f35cae1b8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: SearchUI.exe

STACK_TEXT:
ffff8585`caed8358 fffff806`2aea1c77 : 00000000`00000192 ffff9f82`46495080 ffffc60f`35cae1b8 00000000`00000000 : nt!KeBugCheckEx
ffff8585`caed8360 fffff806`2aea0fc6 : ffffc60f`35cae170 00000000`00000000 ffff8585`caed8488 ffff9f82`401aa090 : nt!ExAcquirePushLockSharedEx+0x147
ffff8585`caed83a0 fffff806`2f0e7c9c : ffff9f82`45254450 ffff8585`caed8500 ffff9f82`401aa090 ffff8585`caed8500 : nt!FsRtlLookupPerStreamContextInternal+0x46
ffff8585`caed83d0 fffff806`2f0e7bb1 : ffff9f82`401aa090 ffff9f82`478ca7e8 ffff8585`caed85c8 ffff9f82`478ca7e8 : FLTMGR!FltpGetStreamListCtrl+0x6c
ffff8585`caed8440 fffff806`2fa61841 : 00000000`00000000 ffff9f82`478ca888 00000000`00000000 00000000`0012fbc2 : FLTMGR!FltGetStreamContext+0x21
ffff8585`caed8480 fffff806`2f0e4a5c : ffff9f82`478ca888 ffff8585`caed85c8 ffff9f82`00000001 00000000`00000000 : Wof!WofPreReadCallback+0x61
ffff8585`caed8540 fffff806`2f0e45a0 : ffff8585`caed8720 ffffffff`ffffff00 ffff9f82`462e4b03 00000000`00060000 : FLTMGR!FltpPerformPreCallbacks+0x2fc
ffff8585`caed8650 fffff806`2f0e4112 : 00000000`00000000 ffff8585`caed8720 ffff9f82`462e4b50 ffff8585`caed8730 : FLTMGR!FltpPassThroughInternal+0x90
ffff8585`caed8680 fffff806`2f0e3efe : ffff8585`caed8910 fffff806`2ae5fe58 ffff8585`caed8880 ffffc60f`35140678 : FLTMGR!FltpPassThrough+0x162
ffff8585`caed8700 fffff806`2ae99db9 : ffff9f82`462e4b50 fffff806`2af2c7cb 00000001`00000000 00000000`00000005 : FLTMGR!FltpDispatch+0x9e
ffff8585`caed8760 fffff806`2af2c3b3 : 00000000`00000005 ffff9f82`462e4b50 ffff9f82`490edc20 ffff9f82`490edce0 : nt!IofCallDriver+0x59
ffff8585`caed87a0 fffff806`2ae93db9 : ffff9f82`490edbd0 00000000`00000000 ffff9f82`490edc30 ffff9f82`490edbf0 : nt!IoPageReadEx+0x1d3
ffff8585`caed8810 fffff806`2ae94939 : 00000000`00000003 ffff8585`caed88f0 ffff8585`caed8a58 fffff806`2ae5a8a6 : nt!MiIssueHardFaultIo+0xc1
ffff8585`caed8860 fffff806`2ae5895b : 00000000`c0033333 00000000`00000001 00007fff`49fdf180 00000000`00000000 : nt!MiIssueHardFault+0x489
ffff8585`caed8960 fffff806`2afd0a5e : ffff9f82`46495080 ffff8585`caed8b80 00000000`00000000 00000000`00000020 : nt!MmAccessFault+0x40b
ffff8585`caed8b00 00007fff`5727cc83 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
0000009f`967fcee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`5727cc83


SYMBOL_NAME: Wof!WofPreReadCallback+61

MODULE_NAME: Wof

IMAGE_NAME:  Wof.sys

IMAGE_VERSION: 10.0.18362.592

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 61

FAILURE_BUCKET_ID: 0x192_Wof!WofPreReadCallback

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9fc35747-90d7-3dc9-b2e5-8b533c6b7c8a}

Followup: MachineOwner
---------

10: kd> lmvm Wof
Browse full module list
start             end                 module name
fffff806`2fa60000 fffff806`2fa9d000   Wof      # (pdb symbols)          C:\ProgramData\Dbg\sym\wof.pdb\235659A96FA78C2213E6AFB9D81F7AEB1\wof.pdb
    Loaded symbol image file: Wof.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\Wof.sys\EE8C76003d000\Wof.sys
Image path: \SystemRoot\System32\Drivers\Wof.sys
Image name: Wof.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        EE8C7600 (This is a reproducible build file hash, not a timestamp)
CheckSum: 00042754
ImageSize: 0003D000
File version: 10.0.18362.592
Product version: 10.0.18362.592
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: wof.sys
OriginalFilename: wof.sys
ProductVersion: 10.0.18362.592
FileVersion: 10.0.18362.592 (WinBuild.160101.0800)
FileDescription: Windows Overlay Filter
LegalCopyright: © Microsoft Corporation. All rights reserved.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00001f80006400ca, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: 00001f80006400ca, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3124

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 12475

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: d1

BUGCHECK_P1: 1f80006400ca

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: 1f80006400ca

READ_ADDRESS: fffff80505b713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80505a283b8: Unable to get Flags value from nt!KdVersionBlock
fffff80505a283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
00001f80006400ca

PROCESS_NAME: System

ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.

CUSTOMER_CRASH_COUNT: 1

TRAP_FRAME:  ffffad840a0a7970 -- (.trap 0xffffad840a0a7970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffad840a0a7b70 rbx=0000000000000000 rcx=ffffad840a0a7c10
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00001f80006400ca rsp=ffffad840a0a7b00 rbp=ffffad840a0a7c00
r8=0000000000000008 r9=0000000000000000 r10=0000fffff8050da8
r11=ffff887a7e800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
00001f80`006400ca ?? ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
00001f80`006400ca ?? ???

STACK_TEXT:
ffffad84`0a0a7828 fffff805`057d4a29 : 00000000`0000000a 00001f80`006400ca 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffad84`0a0a7830 fffff805`057d0d69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffad84`0a0a7970 00001f80`006400ca : 00000000`00000003 00000000`00000002 ffffbf0a`3f0dc100 00000000`00000008 : nt!KiPageFault+0x469
ffffad84`0a0a7b00 00000000`00000003 : 00000000`00000002 ffffbf0a`3f0dc100 00000000`00000008 00000000`00000000 : 0x00001f80`006400ca
ffffad84`0a0a7b08 00000000`00000002 : ffffbf0a`3f0dc100 00000000`00000008 00000000`00000000 0000ffff`f8050da8 : 0x3
ffffad84`0a0a7b10 ffffbf0a`3f0dc100 : 00000000`00000008 00000000`00000000 0000ffff`f8050da8 ffff887a`7e800000 : 0x2
ffffad84`0a0a7b18 00000000`00000008 : 00000000`00000000 0000ffff`f8050da8 ffff887a`7e800000 000062d1`00006200 : 0xffffbf0a`3f0dc100
ffffad84`0a0a7b20 00000000`00000000 : 0000ffff`f8050da8 ffff887a`7e800000 000062d1`00006200 00000000`00000000 : 0x8


SYMBOL_NAME: nt!KiPageFault+469

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1110

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 469

FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f2ab72c5-099d-9077-bfcf-ba12aa825b36}

Followup: MachineOwner
---------

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff972382da7cd0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8046744ff89, address which referenced memory

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4014

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 15156

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: a

BUGCHECK_P1: ffff972382da7cd0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8046744ff89

WRITE_ADDRESS: fffff804679713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff804678283b8: Unable to get Flags value from nt!KdVersionBlock
fffff804678283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff972382da7cd0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME:  fffffc02daaa78a0 -- (.trap 0xfffffc02daaa78a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000001ed6 rbx=0000000000000000 rcx=950da7f17ec40000
rdx=000000000000082f rsi=0000000000000000 rdi=0000000000000000
rip=fffff8046744ff89 rsp=fffffc02daaa7a30 rbp=fffffc02daaa7b30
r8=000000000000082f r9=000000000000002f r10=0000fffff80467eb
r11=fffffc02daaa7840 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiRetireDpcList+0x419:
fffff804`6744ff89 498984dd10680000 mov qword ptr [r13+rbx*8+6810h],rax ds:00000000`00006810=????????????????
Resetting default scope

STACK_TEXT:
fffffc02`daaa7758 fffff804`675d4a29 : 00000000`0000000a ffff9723`82da7cd0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffc02`daaa7760 fffff804`675d0d69 : ffffe70e`00000000 ffffe70e`786ee180 00000000`20000080 fffff804`67509a7a : nt!KiBugCheckDispatch+0x69
fffffc02`daaa78a0 fffff804`6744ff89 : 00000000`00000000 00000000`00989680 00000000`000231ab 00000000`000000c3 : nt!KiPageFault+0x469
fffffc02`daaa7a30 fffff804`675c66fe : ffffffff`00000000 ffffd700`60fd8180 ffffd700`60fe9340 ffffe70e`7452a080 : nt!KiRetireDpcList+0x419
fffffc02`daaa7c60 00000000`00000000 : fffffc02`daaa8000 fffffc02`daaa2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e


SYMBOL_NAME: nt!KiRetireDpcList+419

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.1110

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 419

FAILURE_BUCKET_ID: AV_nt!KiRetireDpcList

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ed0bb485-7f7e-1f95-20ce-1dac811ad862}

Followup: MachineOwner
---------


DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8016c771358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5218

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12101

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8016c771358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffffb8d52ebc9e0 -- (.trap 0xfffffb8d52ebc9e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000005cbb4c14 rbx=0000000000000000 rcx=fffffb8d52ebcbe8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8016c2447f0 rsp=fffffb8d52ebcb78 rbp=ffffdd00b2ac0180
 r8=0000000000000102  r9=0000000000000000 r10=fffff8016aefe800
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeYieldProcessorEx+0x20:
fffff801`6c2447f0 c3              ret
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

DPC_STACK_BASE:  FFFFFB8D52EBCFB0

STACK_TEXT: 
ffffdd00`b2b18b08 fffff801`6c3fd1a3     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`6c771358 : nt!KeBugCheckEx
ffffdd00`b2b18b10 fffff801`6c2483dc     : 000001cd`d716ecd6 ffffdd00`b2ac0180 00000000`0000878a 00000000`0000878a : nt!KeAccumulateTicks+0x1b1983
ffffdd00`b2b18b70 fffff801`6c15d567     : 00000000`00000000 fffffb8d`52ebc9e0 fffffb8d`52ebca60 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffdd00`b2b18f30 fffff801`6c3377d5     : 00000001`434d7308 ffff9683`922a8300 ffff9683`922a83b0 ffffde5e`f47c37ed : hal!HalpTimerClockInterrupt+0xf7
ffffdd00`b2b18f60 fffff801`6c3c441a     : fffffb8d`52ebca60 ffff9683`922a8300 00000000`00000102 ffff9683`922a8300 : nt!KiCallInterruptServiceRoutine+0xa5
ffffdd00`b2b18fb0 fffff801`6c3c4987     : ffff9683`00000000 00001f80`003c0294 00000000`5cba8d8a fffffb8d`52ebcbe8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb8d`52ebc9e0 fffff801`6c2447f0     : fffff801`6c2b2e81 fffffb8d`52ebcc00 fffff801`6c250afb fffff801`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb8d`52ebcb78 fffff801`6c2b2e81     : fffffb8d`52ebcc00 fffff801`6c250afb fffff801`00000000 ffffdd00`b2ac2f00 : nt!KeYieldProcessorEx+0x20
fffffb8d`52ebcb80 fffff801`6c251686     : ffff9683`9e9cf188 ffff9683`5cbb4c14 ffff9683`9e9cf250 ffff9683`9e9cf180 : nt!KiTryUnwaitThread+0x231
fffffb8d`52ebcbe0 fffff801`6c251262     : ffff9683`9e9cf180 fffff801`6c2f7ac0 927f800f`00000003 fffffb8d`52ebce60 : nt!KiTimerWaitTest+0x1b6
fffffb8d`52ebcc90 fffff801`6c250059     : 00000000`00000012 00000000`00989680 00000000`00003ee8 00000000`00000000 : nt!KiProcessExpiredTimerList+0xd2
fffffb8d`52ebcd80 fffff801`6c3c9995     : 00000000`00000000 ffffdd00`b2ac0180 ffff9683`922a8300 000002aa`8fc545e0 : nt!KiRetireDpcList+0x4e9
fffffb8d`52ebcfb0 fffff801`6c3c9780     : fffff801`6c175b30 fffff801`6c15f37a ffffffff`fffeee90 00000000`00000000 : nt!KxRetireDpcList+0x5
fffffb8d`57772ac0 fffff801`6c3c9035     : 000002aa`8fc545e0 fffff801`6c3c4a01 00000000`00000000 fffffb8d`57772b80 : nt!KiDispatchInterruptContinue
fffffb8d`57772af0 fffff801`6c3c4a01     : 00000000`00000000 fffffb8d`57772b80 ffff9683`922a8300 ffffffff`fffeee90 : nt!KiDpcInterruptBypass+0x25
fffffb8d`57772b00 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1


SYMBOL_NAME:  nt!KeAccumulateTicks+1b1983

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.1082

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1b1983

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8021f08f399, The address that the exception occurred at
Arg3: fffff406ae688b78, Exception Record Address
Arg4: fffff406ae6883c0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 4890

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1IBQR0U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 66749

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8021f08f399

BUGCHECK_P3: fffff406ae688b78

BUGCHECK_P4: fffff406ae6883c0

EXCEPTION_RECORD:  fffff406ae688b78 -- (.exr 0xfffff406ae688b78)
ExceptionAddress: fffff8021f08f399 (dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+0x00000000000001a9)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000004234002a1
Attempt to read from address 00000004234002a1

CONTEXT:  fffff406ae6883c0 -- (.cxr 0xfffff406ae6883c0)
rax=0000000000000000 rbx=ffffda099f603000 rcx=8d7600928ef80000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffda099f4ae790
rip=fffff8021f08f399 rsp=fffff406ae688db0 rbp=0000000423400301
 r8=0000000000000000  r9=0000000000000000 r10=fffff802164a0e20
r11=ffff8c7b35000000 r12=0000000000000000 r13=ffffb00423bf8a30
r14=0000000000000000 r15=fffff406ae689030
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+0x1a9:
fffff802`1f08f399 8b4da0          mov     ecx,dword ptr [rbp-60h] ss:0018:00000004`234002a1=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff802169713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff802168283b8: Unable to get Flags value from nt!KdVersionBlock
fffff802168283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 00000004234002a1

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000004234002a1

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
fffff406`ae688db0 fffff802`1f02287e     : ffffb004`2fd56db0 00000000`00000000 fffff406`ae689030 ffffb004`23bf8a30 : dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+0x1a9
fffff406`ae688ff0 fffff802`1f07aab6     : 00000000`08d20000 fffff406`ae689150 ffffb004`2fd56db0 ffffda09`9f603000 : dxgmms2!CVirtualAddressAllocator::FlushGpuVaTlb+0x96
fffff406`ae689050 fffff802`1f07a949     : 00000000`00000000 ffffda09`9f5ec8a0 ffffda09`9f4d1000 00000001`00001f5c : dxgmms2!VIDMM_GLOBAL::FillAllocationUsingGpuVa+0x146
fffff406`ae689290 fffff802`1f07a8c2     : 00000000`00000000 fffff802`1f084e1b 00000000`00000000 ffffb004`2fd56db0 : dxgmms2!VIDMM_GLOBAL::FillAllocationInternal+0x75
fffff406`ae689450 fffff802`1f07b69a     : 00000000`00000000 ffffda09`9f603000 00000000`00000000 ffffb004`2fd56db0 : dxgmms2!VIDMM_GLOBAL::FillAllocation+0x2e
fffff406`ae6894a0 fffff802`1f07b3c2     : ffffb004`2fd56db0 fffff802`164a1a5d ffffda09`00000000 ffff56d7`3a49040a : dxgmms2!VIDMM_MEMORY_SEGMENT::TransferToSegment+0xfa
fffff406`ae689610 fffff802`1f08caef     : ffffda09`a2763010 ffffda09`9f603000 00000000`00000000 ffffb004`2fd56db0 : dxgmms2!VIDMM_MEMORY_SEGMENT::CommitResource+0x62
fffff406`ae689660 fffff802`1f098582     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x1ef
fffff406`ae689770 fffff802`1f0a85e4     : 00000000`00000001 00000000`00989680 ffffb004`2ed73300 00000000`00000001 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x862
fffff406`ae6899e0 fffff802`1f0a7729     : ffffb004`28548d10 ffff9c81`cbed1301 ffffda09`9f29a000 00000000`00000300 : dxgmms2!VIDMM_WORKER_THREAD::Run+0xea4
fffff406`ae689be0 fffff802`1651e235     : ffffda09`9f29a0c0 fffff802`1f0a7720 ffffb004`28548d10 00000067`b4bbbdff : dxgmms2!VidMmWorkerThreadProc+0x9
fffff406`ae689c10 fffff802`165ca1d8     : ffff9c81`cbec0180 ffffda09`9f29a0c0 fffff802`1651e1e0 c3b09ac4`56e78365 : nt!PspSystemThreadStartup+0x55
fffff406`ae689c60 00000000`00000000     : fffff406`ae68a000 fffff406`ae684000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb+1a9

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.18362.1110

STACK_COMMAND:  .cxr 0xfffff406ae6883c0 ; kb

BUCKET_ID_FUNC_OFFSET:  1a9

FAILURE_BUCKET_ID:  AV_dxgmms2!VIDMM_GLOBAL::FlushGpuVaTlb

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c2272481-e701-854c-65b2-8374ea46a6f3}

Followup:     MachineOwner
---------
 
Ekran kartının sürücülerini DDU ile kaldırıp güncelleyin. AMD ise WHQL sürümünü kurun. Modeli nedir?
Ayrıca bellek testi de yapın.
Ekran kartı modelim Asus Rog Strix RTX2070
 
Sadece kaldırmayacaksınız, aynı zamanda guncelleyeceksiniz de. En güncel sürümü kurabilirsiniz.
DDU ile Nvdia driverını kaldırdım internet kapalı bir şekilde. Yeniden başlatıp masaüstüne geldikten 5 dakika sonra tekrar mavi ekran verdim. Ardından memteste86 testine başladım şuan 2 buçuk saate gelmiş durumda. Teste daha fazla devam etmeli miyim ?
 

Dosya Ekleri

  • 1.jpg
    1.jpg
    165,8 KB · Görüntüleme: 32
Şimdi memtest86 testi bitti. Ardından Aida65 testi yaptım hiçbir sıkıntı çıkmadı. Bütün bileşenler yük altında 10 dk çalıştı. Ssd me hardiskimden bi dosya atmaya başladım, dosya iletimi biranda %70 te kapandı ve sadece sistem yüklü ssd biranda 450gb dolu gözüktü,ardından bu doluluk ne diye bi gireyim dedim. Kullanıcılar klasöründe 333 gb dosya gözüküyordu. İçine girdim ve windows dosyalarından başka bir şey bulamadım. Sonra bu klasörü sildim. Silme işlemi başladı, sildiği dosyalar resmen system32 dosyaları gibiydi. Sildikten sonra mavi ekran verdi. Şuan en büyük şüphem ssd. Ssd de sıkıntı olma ihtimali var mı? Hayatımda ilk defa böyle bir şeyle karşılaştım. Sıfır sistem biranda 400 gb küsür seviyelere ulaştı. Yardımınız için teşekkürler.
 

Dosya Ekleri

  • 2.jpg
    2.jpg
    193,6 KB · Görüntüleme: 29

Geri
Yukarı