Termal macun değişimi sonrası mavi ekran hatası

HypeRisReal

HypeRisReal

Hectopat
Katılım
5 Eylül 2019
Mesajlar
194
Daha fazla  
Cinsiyet
Erkek
Herkese iyi günler diliyorum. Dün işlemcimin termal macununu değiştirdim ve ilk açtığımda bir problem yoktu fakat oyuna girmeye çalıştığımda mavi ekran hatası alıyorum her şeyi doğru yaptığımdan eminim aşağıya minidump dosyalarını bırakıyorum yardımcı olursanız çok mutlu olurum.

disk.yandex.com.tr

minidump.rar

Görüntüle ve Yandex Disk'ten indir
disk.yandex.com.tr disk.yandex.com.tr

sistem özellikleri
Ryzen 5 1600 Af
A320M PRO-e
RX 570 8 GB
16 GB RAM
 
Tarihe göre sırala Puana göre sırala
Kullanıcı311 dedi:
Ethernet ile ilgili sorun olabilir mi?

Araştırdım. Sorun Ethernet olabilir. Driver yükle.

tr.msi.com

A320M PRO-E

AMD AM4 A320 mATX professional motherboard, M.2, Core Boost, DDR4 Boost, MSI PRO
tr.msi.com tr.msi.com
Genişletmek için tıkla...
pardon araştırma hakkında biraz bilgi verebilir misiniz? Ethernet nasıl bir sorun yaratmış olabilir.
 
Artı 0 Eksi
  • Mavi ekranlardan birinde rt640x64.sys yani Realtek ethernet sürücünüz hata vermiş.
  • Diğerinde gameflt.sys yani Microsoft ile alakalı Gaming Filter sürücüsü. Windows sürücüsü diyebiliriz.
  • Bir diğerini vgk.sys yani Riot Vanguard kaynaklı görüyorum.
  • Dördüncüde memory_corruption yani belleklerde bir arıza var.
  • Ve son olarak beşincide ise dxgkrnl.sys yani DirectX Graphics Kernel sebebiyle kaynaklanmış. Bunu da AMD ekran kartı sürücünüzdeki bir probleme yorabiliriz.

Ancak tüm bu sürücülerin hepsi bir anda bozulacak veya eskiyecek değil ya?

Hatalar çeşitli. Bu şekilde çeşitlenmeye başladığında genelde RAM veya hard disk arızası deriz. Belli ki bir yerde problem var.

Teyit etmek için soruyorum. Ciddi anlamda termal macun yenilemesi öncesinde herhangi bir mavi ekran yoktu değil mi?

Sistemde iki farklı bellek oluşu da şüphe uyandırıyor. Ama bu zamana kadar bir problem yaşanmadı herhalde?
Kod: 
F4-3200C16-8GVKB
CMK8GX4M1D3000C16


* İşlemcide aşırı bir ısınma var mı? Mesela BIOS ekranında ve boşta sıcaklıklar nasıl?

* RAM'leri söküp taktınız mı? RAM'lere de dokunduysanız slota oturduklarından, temasın tam olduğunundan emin olun.

* SSD ve HDD yani depolama birimlerinizin SATA ve POWER kablolarının gevşemediğinden, tam oturduğundan emin olun. Anakarttaki SATA portlarını da kontrol edin.


* İlk başta bu tip fiziksel kontrolleri bir yapın ve tekrar mavi ekran alıyor musunuz diye kontrol edin.


* BIOS'a girin ve F6 yapın. Load Defaults sorusuna YES deyip çıkın.


* Termal macun değişikliğinden önce herhangi bir mavi ekran almadığınızı teyit ederseniz ona göre ekstra çözümler, sürücü güncellemeleri vs. önereceğim.


* BIOS güncelleyebilirsiniz bu arada. H.73 sürümünü kullanıyorsunuz. Bu sürüm siteden kaldırılmış. Bir problem olduğu için kaldırılmış olabilir. 7A36vH75(Beta version) yükleyebilirsiniz.

tr.msi.com

A320M PRO-E

AMD AM4 A320 mATX professional motherboard, M.2, Core Boost, DDR4 Boost, MSI PRO
tr.msi.com tr.msi.com


Dökümler:
Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80747149c80, Virtual address for the attempted write.
Arg2: 0900000005b49021, PTE contents.
Arg3: fffff80747c965a0, (reserved)
Arg4: 000000000000000a, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1561

    Key  : Analysis.Elapsed.mSec
    Value: 7450

    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: 155

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xbe

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_rt640x64!unknown_function

    Key  : Failure.Hash
    Value: {2e96e72d-48ac-dceb-22bd-11e71513e43e}


BUGCHECK_CODE:  be

BUGCHECK_P1: fffff80747149c80

BUGCHECK_P2: 900000005b49021

BUGCHECK_P3: fffff80747c965a0

BUGCHECK_P4: a

FILE_IN_CAB:  062423-34109-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80747c965a0 -- (.trap 0xfffff80747c965a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80747149c80 rbx=0000000000000000 rcx=00000000ff4b3548
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80747149c8b rsp=fffff80747c96738 rbp=00000000c1ebe636
 r8=0000000000001fff  r9=fffff80747c968b8 r10=0000fffff8074714
r11=ffffc27cf2a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
tcpip!Ipv4AddressScope+0xb:
fffff807`47149c8b f00000          lock add byte ptr [rax],al ds:fffff807`47149c80=8b
Resetting default scope

STACK_TEXT:
fffff807`47c963a8 fffff807`44c69f52     : 00000000`000000be fffff807`47149c80 09000000`05b49021 fffff807`47c965a0 : nt!KeBugCheckEx
fffff807`47c963b0 fffff807`44a6e89f     : 09000000`05b49021 00000000`00000003 fffff807`47c96620 00000000`00000000 : nt!MiRaisedIrqlFault+0x1639da
fffff807`47c96400 fffff807`44c0bad8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x4ef
fffff807`47c965a0 fffff807`47149c8b     : fffff807`47185e2b 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
fffff807`47c96738 fffff807`47185e2b     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!Ipv4AddressScope+0xb
fffff807`47c96740 fffff807`47184388     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeadersHelper+0x14b
fffff807`47c96860 fffff807`47183a8f     : fffff807`4733aa70 ffffa58c`95e248e0 ffffa58c`9e319010 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x98
fffff807`47c96960 fffff807`47170fdb     : ffffa58c`9beffb80 ffffa58c`9beac030 00000000`00000001 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x32f
fffff807`47c96a80 fffff807`471c8cee     : ffffa58c`9beffb80 ffffa58c`9e317620 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0xe4b
fffff807`47c96d20 fffff807`44aad488     : ffffa58c`95dfd840 00000000`00000002 fffff807`45527a00 fffff807`47c97018 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x12e
fffff807`47c96e70 fffff807`44aad3fd     : fffff807`471c8bc0 fffff807`47c97018 ffffa58c`95b46b90 fffff807`470223af : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff807`47c96ee0 fffff807`471a39ad     : fffff807`47c96fb8 00000000`00000008 ffffa58c`9fa86700 fffff807`4743142f : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff807`47c96f20 fffff807`471a308d     : 00000000`00000001 fffff807`47c97080 ffffa58c`9e317620 00000000`00000000 : tcpip!NetioExpandKernelStackAndCallout+0x8d
fffff807`47c96f80 fffff807`46eb1eb0     : ffffa58c`9b4fa681 00000000`00000001 ffffa58c`9b51e070 fffff807`47c97390 : tcpip!FlReceiveNetBufferListChain+0x46d
fffff807`47c97230 fffff807`46eb1ccb     : ffffa58c`9b5f8460 ffffa58c`00000001 fffff807`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x140
fffff807`47c97310 fffff807`46eb7ef0     : ffffa58c`9b3341a0 ffffa58c`9beac001 ffffa58c`9b3341a0 fffff807`44b12e01 : ndis!ndisMTopReceiveNetBufferLists+0x22b
fffff807`47c97390 fffff807`46eedfef     : ffffa58c`9beac030 fffff807`47c97461 00000000`00000000 ffffa58c`9e31aa30 : ndis!ndisCallReceiveHandler+0x60
fffff807`47c973e0 fffff807`46eb4a94     : 00000000`000091ac 00000000`00000001 ffffa58c`9b3341a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x1df
fffff807`47c974b0 fffff807`5fbb72ce     : ffffa58c`9b778000 ffffa58c`9b778000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffff807`47c97540 ffffa58c`9b778000     : ffffa58c`9b778000 00000000`00000000 00000000`00000000 ffffa58c`00000001 : rt640x64+0x272ce
fffff807`47c97548 ffffa58c`9b778000     : 00000000`00000000 00000000`00000000 ffffa58c`00000001 ffffa58c`9e644010 : 0xffffa58c`9b778000
fffff807`47c97550 00000000`00000000     : 00000000`00000000 ffffa58c`00000001 ffffa58c`9e644010 00000000`9b450001 : 0xffffa58c`9b778000


SYMBOL_NAME:  rt640x64+272ce

MODULE_NAME: rt640x64

IMAGE_NAME:  rt640x64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  272ce

FAILURE_BUCKET_ID:  AV_rt640x64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2e96e72d-48ac-dceb-22bd-11e71513e43e}

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


*******************************************************************************
*                                                                             *
*                        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: fffff80748f7d020, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff807481f7e44, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.Elapsed.mSec
    Value: 4964

    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: 186

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_R_(null)_gameflt!unknown_function

    Key  : Failure.Hash
    Value: {929e692c-8b3b-3710-b736-a60e6e7319bb}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff80748f7d020

BUGCHECK_P2: 0

BUGCHECK_P3: fffff807481f7e44

BUGCHECK_P4: 0

FILE_IN_CAB:  062423-18625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff807486fb390: 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
 fffff80748f7d020

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff8f0048203350 -- (.trap 0xffff8f0048203350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff807d0637508 rbx=0000000000000000 rcx=002e00300031007e
rdx=ffff8f0048203510 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807481f7e44 rsp=ffff8f00482034e8 rbp=ffff8f0048203550
 r8=0000000000000001  r9=000000000000004d r10=ffffc6fd82a9d8bc
r11=000000000000007e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!RtlEqualUnicodeString+0x1d7d04:
fffff807`481f7e44 488b3dd551d800  mov     rdi,qword ptr [fffff807`48f7d020] ds:fffff807`48f7d020=????????????????
Resetting default scope

STACK_TEXT:
ffff8f00`482030a8 fffff807`47e4b203     : 00000000`00000050 fffff807`48f7d020 00000000`00000000 ffff8f00`48203350 : nt!KeBugCheckEx
ffff8f00`482030b0 fffff807`47c6e7b0     : ffff8f00`48203248 00000000`00000000 ffff8f00`482033d0 00000000`00000000 : nt!MiSystemFault+0x1b2813
ffff8f00`482031b0 fffff807`47e0bad8     : ffff8f00`48200000 ffff8f00`48200000 00000000`00000005 ffff8f00`48203380 : nt!MmAccessFault+0x400
ffff8f00`48203350 fffff807`481f7e44     : fffff807`d064727b ffff9a8d`ce6b05c8 ffff8f00`482035e0 00000000`00000001 : nt!KiPageFault+0x358
ffff8f00`482034e8 fffff807`d064727b     : ffff9a8d`ce6b05c8 ffff8f00`482035e0 00000000`00000001 00000000`00000000 : nt!RtlEqualUnicodeString+0x1d7d04
ffff8f00`482034f0 ffff9a8d`ce6b05c8     : ffff8f00`482035e0 00000000`00000001 00000000`00000000 00000000`00280028 : gameflt+0x1727b
ffff8f00`482034f8 ffff8f00`482035e0     : 00000000`00000001 00000000`00000000 00000000`00280028 ffffbf05`530d4dc4 : 0xffff9a8d`ce6b05c8
ffff8f00`48203500 00000000`00000001     : 00000000`00000000 00000000`00280028 ffffbf05`530d4dc4 ffff9a8d`c1dc1850 : 0xffff8f00`482035e0
ffff8f00`48203508 00000000`00000000     : 00000000`00280028 ffffbf05`530d4dc4 ffff9a8d`c1dc1850 fffff807`d06444fe : 0x1


SYMBOL_NAME:  gameflt+1727b

MODULE_NAME: gameflt

IMAGE_NAME:  gameflt.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1727b

FAILURE_BUCKET_ID:  AV_R_(null)_gameflt!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {929e692c-8b3b-3710-b736-a60e6e7319bb}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000080, 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: fffff8004e6231c5, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1483

    Key  : Analysis.Elapsed.mSec
    Value: 2414

    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: 171

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_win32kbase!GreUnlockDwmState

    Key  : Failure.Hash
    Value: {b7fc9895-04d2-dd05-7033-67990cfe1f84}


BUGCHECK_CODE:  a

BUGCHECK_P1: 80

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8004e6231c5

FILE_IN_CAB:  062423-19312-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

WRITE_ADDRESS: fffff8004f0fb390: 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
 0000000000000080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ow-obs.exe

TRAP_FRAME:  fffff60b4590fde0 -- (.trap 0xfffff60b4590fde0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000080 rbx=0000000000000000 rcx=ffff8d84c87fd190
rdx=ffff8d84cc5b4080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004e6231c5 rsp=fffff60b4590ff70 rbp=fffff60b45910079
 r8=fffff60b4590ffa0  r9=ffff9d8fc8f6b6f0 r10=0000000000000000
r11=ffff9df018000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!ExReleaseResourceAndLeaveCriticalRegion+0x85:
fffff800`4e6231c5 0000            add     byte ptr [rax],al ds:00000000`00000080=??
Resetting default scope

STACK_TEXT:
fffff60b`4590fc98 fffff800`4e810029     : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff60b`4590fca0 fffff800`4e80bbe3     : 00000000`00000003 fffff60b`45910110 fffff60b`459100d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff60b`4590fde0 fffff800`4e6231c5     : ffff8d84`c87fd190 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffff60b`4590ff70 ffffc025`8f6757cf     : ffff9d8f`d5d55070 ffff9d8f`00000000 ffff9d8f`c8b8b1b8 00000000`00000000 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x85
fffff60b`4590ffd0 fffff800`7fa140ac     : fffff60b`45910079 ffff8d84`c8e8d080 00000000`00000000 00000000`00000001 : win32kbase!GreUnlockDwmState+0x2f
fffff60b`45910000 fffff800`7fa13643     : 00000000`00000001 ffff8d84`c2282a70 00000000`00000000 fffff60b`45910980 : dxgkrnl!NotifyPendingFlipPresent+0x59c
fffff60b`459100e0 fffff800`7fb52e38     : fffff60b`45910988 fffff60b`45910170 fffff60b`45910870 00000000`00000001 : dxgkrnl!DxgkQuerySwapChainBindingStatus+0x2b
fffff60b`45910110 fffff800`7fafdb4b     : ffff9d8f`c8b8b050 fffff60b`45910b80 ffff8d84`c8676000 00000000`00000000 : dxgkrnl!SubmitPresentHistoryTokenPreparation+0x178
fffff60b`459101b0 fffff800`7fb00ce1     : ffff9d8f`c8b8b050 fffff60b`45910b80 00000000`00000000 ffff8d84`c8676000 : dxgkrnl!DXGCONTEXT::Present+0x9eb
fffff60b`45910790 fffff800`7fee8325     : fffff60b`45910b80 0000008e`924fc610 00000000`00009000 00000000`00501802 : dxgkrnl!DxgkPresent+0x7f1
fffff60b`45910a60 fffff60b`45910b80     : 0000008e`924fc610 00000000`00009000 00000000`00501802 ffffc025`8f011bf4 : vgk+0x18325
fffff60b`45910a68 0000008e`924fc610     : 00000000`00009000 00000000`00501802 ffffc025`8f011bf4 fffff60b`45910a80 : 0xfffff60b`45910b80
fffff60b`45910a70 00000000`00009000     : 00000000`00501802 ffffc025`8f011bf4 fffff60b`45910a80 00000000`00000008 : 0x0000008e`924fc610
fffff60b`45910a78 00000000`00501802     : ffffc025`8f011bf4 fffff60b`45910a80 00000000`00000008 fffff181`111b2df6 : 0x9000
fffff60b`45910a80 ffffc025`8f011bf3     : fffff60b`45910a80 00000000`00000008 fffff181`111b2df6 ffff8d84`cc5b4080 : 0x501802
fffff60b`45910a88 fffff60b`45910a80     : 00000000`00000008 fffff181`111b2df6 ffff8d84`cc5b4080 fffff800`4e80ff78 : win32k!NtGdiDdDDIPollDisplayChildren+0x13
fffff60b`45910a90 00000000`00000008     : fffff181`111b2df6 ffff8d84`cc5b4080 fffff800`4e80ff78 fffff60b`45910b80 : 0xfffff60b`45910a80
fffff60b`45910a98 fffff181`111b2df6     : ffff8d84`cc5b4080 fffff800`4e80ff78 fffff60b`45910b80 ffff8d84`db181060 : 0x8
fffff60b`45910aa0 ffff8d84`cc5b4080     : fffff800`4e80ff78 fffff60b`45910b80 ffff8d84`db181060 00000000`00000000 : 0xfffff181`111b2df6
fffff60b`45910aa8 fffff800`4e80ff78     : fffff60b`45910b80 ffff8d84`db181060 00000000`00000000 0000008e`924fd7b8 : 0xffff8d84`cc5b4080
fffff60b`45910ab0 00007ffa`76d75424     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3cd
0000008e`924fc4f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`76d75424


SYMBOL_NAME:  win32kbase!GreUnlockDwmState+2f

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.3083

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  2f

FAILURE_BUCKET_ID:  AV_win32kbase!GreUnlockDwmState

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b7fc9895-04d2-dd05-7033-67990cfe1f84}

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


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe181a5720e50
Arg3: fffff80525c11385
Arg4: fffff805435a4095

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 15905

    Key  : Analysis.Elapsed.mSec
    Value: 16539

    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: 217

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: MEMORY_CORRUPTION_STRIDE

    Key  : Failure.Hash
    Value: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}


BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe181a5720e50

BUGCHECK_P3: fffff80525c11385

BUGCHECK_P4: fffff805435a4095

FILE_IN_CAB:  062323-15593-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BAD_STACK_POINTER:  fffff80525c11385

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RuntimeBroker.

UNALIGNED_STACK_POINTER:  fffff80525c11385

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ahcache
16 errors : !ahcache (fffff805435a4081-fffff805435a4239)
fffff805435a4080  05 *ac  45  ff  ff  e9  cf  fb  ff *72  cc  cc  cc  cc  cc  cc ..E......r......
fffff805435a4090  48 *6e  5c  24  08  57  48  83  ec *45  48  8b  8a  b8  00  00 Hn\$.WH..EH.....
fffff805435a40a0  00 *08  8b  da  48  c7  42  38  00 *7e  00  00  8b  41  18  48 ....H.B8.~...A.H
fffff805435a40b0  8b *82  20  c1  e8  02  44  0f  b6 *9d  41  83  f9  0c  0f  83 .. ...D...A.....
...
fffff805435a4200  48 *7f  0f  10  41  40  0f  11  40 *b2  0f  10  49  50  0f  11 H...A@[email protected]..
fffff805435a4210  48 *b2  0f  10  41  60  0f  11  40 *b2  48  8b  49  70  48  89 H...A`[email protected].
fffff805435a4220  48 *f3  eb  09  8b  d8  48  8b  7c *70  38  eb  6a  48  81  c3 H.....H.|p8.jH..
fffff805435a4230  70 *72  00  00  83  fe  06  0f  85 *72  00  00  00  48  8b  0d pr.......r...H..

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup:     memory_corruption
---------


*******************************************************************************
*                                                                             *
*                        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: fffff802ce441970, memory referenced.
Arg2: 0000000000000010, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff802ce441970, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 1656

    Key  : Analysis.Elapsed.mSec
    Value: 1819

    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: 171

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_dxgkrnl!MONITOR_MGR::_GetMonitorInstance

    Key  : Failure.Hash
    Value: {fa461f68-1be5-d318-a9e7-83abc6e8eb39}


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff802ce441970

BUGCHECK_P2: 10

BUGCHECK_P3: fffff802ce441970

BUGCHECK_P4: 0

FILE_IN_CAB:  062323-15609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: fffff80255efb390: 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
 fffff802ce441970

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  ffffac87b2d2c550 -- (.trap 0xffffac87b2d2c550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff850906afb840 rbx=0000000000000000 rcx=ffff85090f159cb0
rdx=45894c000000a89d rsi=0000000000000000 rdi=0000000000000000
rip=fffff802ce441970 rsp=ffffac87b2d2c6e8 rbp=ffff85090f159cb0
 r8=ffff850906afb801  r9=ffffac87b2d2c780 r10=f80255433630ffff
r11=ffffac87b2d2c800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff802`ce441970 ??              ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`ce441970 ??              ???

STACK_TEXT:
ffffac87`b2d2c2a8 fffff802`5564b203     : 00000000`00000050 fffff802`ce441970 00000000`00000010 ffffac87`b2d2c550 : nt!KeBugCheckEx
ffffac87`b2d2c2b0 fffff802`5546e7b0     : 00000000`00000000 00000000`00000010 ffffac87`b2d2c5d0 00000000`00000000 : nt!MiSystemFault+0x1b2813
ffffac87`b2d2c3b0 fffff802`5560bad8     : ffff8509`10177730 fffff802`55401969 00000000`00000799 00000000`00000000 : nt!MmAccessFault+0x400
ffffac87`b2d2c550 fffff802`ce441970     : fffff802`85f56362 ffff8509`101776d0 fffff802`55420ceb ffff8509`10177080 : nt!KiPageFault+0x358
ffffac87`b2d2c6e8 fffff802`85f56362     : ffff8509`101776d0 fffff802`55420ceb ffff8509`10177080 ffff8509`0f0d5088 : 0xfffff802`ce441970
ffffac87`b2d2c6f0 fffff802`85f56284     : ffff8509`0f159cb0 00000000`00000104 ffffac87`b2d2c7b8 fffff802`85e3642d : dxgkrnl!MONITOR_MGR::_GetMonitorInstance+0x5a
ffffac87`b2d2c730 fffff802`860d3d14     : 00000000`00000000 00000000`00000000 ffffac87`b2d2c7d9 ffffae8d`51790750 : dxgkrnl!MonitorGetMonitorHandle+0x94
ffffac87`b2d2c780 fffff802`860d84a2     : 000001fd`2a857aa0 000001fd`2a857aa0 00000000`00000020 ffffac87`b2d2c938 : dxgkrnl!PopulateHDRMetadataFromDisplay+0x124
ffffac87`b2d2c840 fffff802`5560f7f8     : ffff8509`10177080 ffff8509`10177080 00000000`00000001 00000000`00000000 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x3d2
ffffac87`b2d2cb00 00007ffe`5d1d5484     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f7`282fc8f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5d1d5484


SYMBOL_NAME:  dxgkrnl!MONITOR_MGR::_GetMonitorInstance+5a

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

IMAGE_VERSION:  10.0.19041.2913

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  5a

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_dxgkrnl!MONITOR_MGR::_GetMonitorInstance

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fa461f68-1be5-d318-a9e7-83abc6e8eb39}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
EgeN7 dedi:
  • Mavi ekranlardan birinde rt640x64.sys yani Realtek Ethernet sürücünüz hata vermiş.
  • Diğerinde gameflt.sys yani Microsoft ile alakalı Gaming filter sürücüsü. Windows sürücüsü diyebiliriz.
  • Bir diğerini vgk.sys yani Riot Vanguard kaynaklı görüyorum.
  • Dördüncüde memory_corruption yani belleklerde bir arıza var.
  • Ve son olarak beşincide ise dxgkrnl.sys yani DirectX Graphics kernel sebebiyle kaynaklanmış. Bunu da AMD ekran kartı sürücünüzdeki bir probleme yorabiliriz.

Ancak tüm bu sürücülerin hepsi bir anda bozulacak veya eskiyecek değil ya?

Hatalar çeşitli. Bu şekilde çeşitlenmeye başladığında genelde RAM veya hard disk arızası deriz. Belli ki bir yerde problem var.

Teyit etmek için soruyorum. Ciddi anlamda termal macun yenilemesi öncesinde herhangi bir mavi ekran yoktu değil mi?

Sistemde iki farklı bellek oluşu da şüphe uyandırıyor. Ama bu zamana kadar bir problem yaşanmadı herhalde?
Kod: 
F4-3200C16-8GVKB
CMK8GX4M1D3000C16

* İşlemcide aşırı bir ısınma var mı? Mesela BIOS ekranında ve boşta sıcaklıklar nasıl?

* RAM'leri söküp taktınız mı? RAM'lere de dokunduysanız slota oturduklarından, temasın tam olduğunundan emin olun.

* SSD ve HDD yani depolama birimlerinizin SATA ve Power kablolarının gevşemediğinden, tam oturduğundan emin olun. Anakarttaki SATA portlarını da kontrol edin.

* İlk başta bu tip fiziksel kontrolleri bir yapın ve tekrar mavi ekran alıyor musunuz diye kontrol edin.

* BIOS'a girin ve F6 yapın. Load defaults sorusuna yes deyip çıkın.

* Termal macun değişikliğinden önce herhangi bir mavi ekran almadığınızı teyit ederseniz ona göre ekstra çözümler, sürücü güncellemeleri vs. önereceğim.

* BIOS güncelleyebilirsiniz bu arada. H. 73 sürümünü kullanıyorsunuz. Bu sürüm siteden kaldırılmış. Bir problem olduğu için kaldırılmış olabilir. 7A36VH75(beta version) yükleyebilirsiniz.

tr.msi.com

A320M PRO-E

AMD AM4 A320 mATX professional motherboard, M.2, Core Boost, DDR4 Boost, MSI PRO
tr.msi.com tr.msi.com

Dökümler:
Kod: 
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the.
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on.
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff80747149c80, Virtual address for the attempted write.
Arg2: 0900000005b49021, PTE contents.
Arg3: fffff80747c965a0, (reserved)
Arg4: 000000000000000a, (reserved)

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1561.

 Key : Analysis.Elapsed.mSec
 Value: 7450.

 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: 155.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xbe.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_rt640x64!unknown_function

 Key : Failure.Hash
 Value: {2e96e72d-48ac-dceb-22bd-11e71513e43e}

BUGCHECK_CODE: be.

BUGCHECK_P1: fffff80747149c80.

BUGCHECK_P2: 900000005b49021.

BUGCHECK_P3: fffff80747c965a0.

BUGCHECK_P4: a

FILE_IN_CAB: 062423-34109-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: fffff80747c965a0 -- (.trap 0xfffff80747c965a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80747149c80 rbx=0000000000000000 rcx=00000000ff4b3548
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80747149c8b rsp=fffff80747c96738 rbp=00000000c1ebe636
 r8=0000000000001fff r9=fffff80747c968b8 r10=0000fffff8074714
r11=ffffc27cf2a00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy.
tcpip!Ipv4AddressScope+0xb:
fffff807`47149c8b f00000 lock add byte ptr [rax],al ds:fffff807`47149c80=8b
Resetting default scope.

STACK_TEXT:
fffff807`47c963a8 fffff807`44c69f52 : 00000000`000000be fffff807`47149c80 09000000`05b49021 fffff807`47c965a0 : nt!KeBugCheckEx
fffff807`47c963b0 fffff807`44a6e89f : 09000000`05b49021 00000000`00000003 fffff807`47c96620 00000000`00000000 : nt!MiRaisedIrqlFault+0x1639da
fffff807`47c96400 fffff807`44c0bad8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x4ef
fffff807`47c965a0 fffff807`47149c8b : fffff807`47185e2b 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
fffff807`47c96738 fffff807`47185e2b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!Ipv4AddressScope+0xb
fffff807`47c96740 fffff807`47184388 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeadersHelper+0x14b
fffff807`47c96860 fffff807`47183a8f : fffff807`4733aa70 ffffa58c`95e248e0 ffffa58c`9e319010 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x98
fffff807`47c96960 fffff807`47170fdb : ffffa58c`9beffb80 ffffa58c`9beac030 00000000`00000001 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x32f
fffff807`47c96a80 fffff807`471c8cee : ffffa58c`9beffb80 ffffa58c`9e317620 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0xe4b
fffff807`47c96d20 fffff807`44aad488 : ffffa58c`95dfd840 00000000`00000002 fffff807`45527a00 fffff807`47c97018 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x12e
fffff807`47c96e70 fffff807`44aad3fd : fffff807`471c8bc0 fffff807`47c97018 ffffa58c`95b46b90 fffff807`470223af : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff807`47c96ee0 fffff807`471a39ad : fffff807`47c96fb8 00000000`00000008 ffffa58c`9fa86700 fffff807`4743142f : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff807`47c96f20 fffff807`471a308d : 00000000`00000001 fffff807`47c97080 ffffa58c`9e317620 00000000`00000000 : tcpip!NetioExpandKernelStackAndCallout+0x8d
fffff807`47c96f80 fffff807`46eb1eb0 : ffffa58c`9b4fa681 00000000`00000001 ffffa58c`9b51e070 fffff807`47c97390 : tcpip!FlReceiveNetBufferListChain+0x46d
fffff807`47c97230 fffff807`46eb1ccb : ffffa58c`9b5f8460 ffffa58c`00000001 fffff807`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x140
fffff807`47c97310 fffff807`46eb7ef0 : ffffa58c`9b3341a0 ffffa58c`9beac001 ffffa58c`9b3341a0 fffff807`44b12e01 : ndis!ndisMTopReceiveNetBufferLists+0x22b
fffff807`47c97390 fffff807`46eedfef : ffffa58c`9beac030 fffff807`47c97461 00000000`00000000 ffffa58c`9e31aa30 : ndis!ndisCallReceiveHandler+0x60
fffff807`47c973e0 fffff807`46eb4a94 : 00000000`000091ac 00000000`00000001 ffffa58c`9b3341a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x1df
fffff807`47c974b0 fffff807`5fbb72ce : ffffa58c`9b778000 ffffa58c`9b778000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffff807`47c97540 ffffa58c`9b778000 : ffffa58c`9b778000 00000000`00000000 00000000`00000000 ffffa58c`00000001 : rt640x64+0x272ce
fffff807`47c97548 ffffa58c`9b778000 : 00000000`00000000 00000000`00000000 ffffa58c`00000001 ffffa58c`9e644010 : 0xffffa58c`9b778000
fffff807`47c97550 00000000`00000000 : 00000000`00000000 ffffa58c`00000001 ffffa58c`9e644010 00000000`9b450001 : 0xffffa58c`9b778000

SYMBOL_NAME: rt640x64+272ce

MODULE_NAME: rt640x64.

IMAGE_NAME: rt640x64.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 272ce.

FAILURE_BUCKET_ID: AV_rt640x64!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {2e96e72d-48ac-dceb-22bd-11e71513e43e}

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

*******************************************************************************
* *
* 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: fffff80748f7d020, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
 bit 1 is set if the fault was due to a write, clear if a read.
 bit 3 is set if the processor decided the fault was due to a corrupted PTE.
 bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
 - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
 bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff807481f7e44, If non-zero, the instruction address which referenced the bad memory.
 address.
Arg4: 0000000000000000, (reserved)

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

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

KEY_VALUES_STRING: 1

 Key : AV.Type
 Value: Read.

 Key : Analysis.CPU.mSec
 Value: 1546.

 Key : Analysis.Elapsed.mSec
 Value: 4964.

 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: 186.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x50.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_R_(null)_gameflt!unknown_function

 Key : Failure.Hash
 Value: {929e692c-8b3b-3710-b736-a60e6e7319bb}

BUGCHECK_CODE: 50.

BUGCHECK_P1: fffff80748f7d020.

BUGCHECK_P2: 0

BUGCHECK_P3: fffff807481f7e44.

BUGCHECK_P4: 0

FILE_IN_CAB: 062423-18625-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

READ_ADDRESS: fffff807486fb390: 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
 fffff80748f7d020.

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System.

TRAP_FRAME: ffff8f0048203350 -- (.trap 0xffff8f0048203350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff807d0637508 rbx=0000000000000000 rcx=002e00300031007e
rdx=ffff8f0048203510 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807481f7e44 rsp=ffff8f00482034e8 rbp=ffff8f0048203550
 r8=0000000000000001 r9=000000000000004d r10=ffffc6fd82a9d8bc
r11=000000000000007e r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc.
nt!RtlEqualUnicodeString+0x1d7d04:
fffff807`481f7e44 488b3dd551d800 mov rdi,qword ptr [fffff807`48f7d020] ds:fffff807`48f7d020=????????????????
Resetting default scope.

STACK_TEXT:
ffff8f00`482030a8 fffff807`47e4b203 : 00000000`00000050 fffff807`48f7d020 00000000`00000000 ffff8f00`48203350 : nt!KeBugCheckEx
ffff8f00`482030b0 fffff807`47c6e7b0 : ffff8f00`48203248 00000000`00000000 ffff8f00`482033d0 00000000`00000000 : nt!MiSystemFault+0x1b2813
ffff8f00`482031b0 fffff807`47e0bad8 : ffff8f00`48200000 ffff8f00`48200000 00000000`00000005 ffff8f00`48203380 : nt!MmAccessFault+0x400
ffff8f00`48203350 fffff807`481f7e44 : fffff807`d064727b ffff9a8d`ce6b05c8 ffff8f00`482035e0 00000000`00000001 : nt!KiPageFault+0x358
ffff8f00`482034e8 fffff807`d064727b : ffff9a8d`ce6b05c8 ffff8f00`482035e0 00000000`00000001 00000000`00000000 : nt!RtlEqualUnicodeString+0x1d7d04
ffff8f00`482034f0 ffff9a8d`ce6b05c8 : ffff8f00`482035e0 00000000`00000001 00000000`00000000 00000000`00280028 : gameflt+0x1727b
ffff8f00`482034f8 ffff8f00`482035e0 : 00000000`00000001 00000000`00000000 00000000`00280028 ffffbf05`530d4dc4 : 0xffff9a8d`ce6b05c8
ffff8f00`48203500 00000000`00000001 : 00000000`00000000 00000000`00280028 ffffbf05`530d4dc4 ffff9a8d`c1dc1850 : 0xffff8f00`482035e0
ffff8f00`48203508 00000000`00000000 : 00000000`00280028 ffffbf05`530d4dc4 ffff9a8d`c1dc1850 fffff807`d06444fe : 0x1.

SYMBOL_NAME: gameflt+1727b

MODULE_NAME: gameflt.

IMAGE_NAME: gameflt.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1727b.

FAILURE_BUCKET_ID: AV_R_(null)_gameflt!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {929e692c-8b3b-3710-b736-a60e6e7319bb}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 0000000000000080, 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: fffff8004e6231c5, address which referenced memory.

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

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 1483.

 Key : Analysis.Elapsed.mSec
 Value: 2414.

 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: 171.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xa.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_win32kbase!GreUnlockDwmState

 Key : Failure.Hash
 Value: {b7fc9895-04d2-dd05-7033-67990cfe1f84}

BUGCHECK_CODE: a

BUGCHECK_P1: 80.

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8004e6231c5.

FILE_IN_CAB: 062423-19312-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

WRITE_ADDRESS: fffff8004f0fb390: 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
 0000000000000080.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: ow-obs.exe

TRAP_FRAME: fffff60b4590fde0 -- (.trap 0xfffff60b4590fde0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000080 rbx=0000000000000000 rcx=ffff8d84c87fd190
rdx=ffff8d84cc5b4080 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8004e6231c5 rsp=fffff60b4590ff70 rbp=fffff60b45910079
 r8=fffff60b4590ffa0 r9=ffff9d8fc8f6b6f0 r10=0000000000000000
r11=ffff9df018000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy.
nt!ExReleaseResourceAndLeaveCriticalRegion+0x85:
fffff800`4e6231c5 0000 add byte ptr [rax],al ds:00000000`00000080=??
Resetting default scope.

STACK_TEXT:
fffff60b`4590fc98 fffff800`4e810029 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff60b`4590fca0 fffff800`4e80bbe3 : 00000000`00000003 fffff60b`45910110 fffff60b`459100d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff60b`4590fde0 fffff800`4e6231c5 : ffff8d84`c87fd190 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffff60b`4590ff70 ffffc025`8f6757cf : ffff9d8f`d5d55070 ffff9d8f`00000000 ffff9d8f`c8b8b1b8 00000000`00000000 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x85
fffff60b`4590ffd0 fffff800`7fa140ac : fffff60b`45910079 ffff8d84`c8e8d080 00000000`00000000 00000000`00000001 : win32kbase!GreUnlockDwmState+0x2f
fffff60b`45910000 fffff800`7fa13643 : 00000000`00000001 ffff8d84`c2282a70 00000000`00000000 fffff60b`45910980 : dxgkrnl!NotifyPendingFlipPresent+0x59c
fffff60b`459100e0 fffff800`7fb52e38 : fffff60b`45910988 fffff60b`45910170 fffff60b`45910870 00000000`00000001 : dxgkrnl!DxgkQuerySwapChainBindingStatus+0x2b
fffff60b`45910110 fffff800`7fafdb4b : ffff9d8f`c8b8b050 fffff60b`45910b80 ffff8d84`c8676000 00000000`00000000 : dxgkrnl!SubmitPresentHistoryTokenPreparation+0x178
fffff60b`459101b0 fffff800`7fb00ce1 : ffff9d8f`c8b8b050 fffff60b`45910b80 00000000`00000000 ffff8d84`c8676000 : dxgkrnl!DXGCONTEXT::Present+0x9eb
fffff60b`45910790 fffff800`7fee8325 : fffff60b`45910b80 0000008e`924fc610 00000000`00009000 00000000`00501802 : dxgkrnl!DxgkPresent+0x7f1
fffff60b`45910a60 fffff60b`45910b80 : 0000008e`924fc610 00000000`00009000 00000000`00501802 ffffc025`8f011bf4 : vgk+0x18325
fffff60b`45910a68 0000008e`924fc610 : 00000000`00009000 00000000`00501802 ffffc025`8f011bf4 fffff60b`45910a80 : 0xfffff60b`45910b80
fffff60b`45910a70 00000000`00009000 : 00000000`00501802 ffffc025`8f011bf4 fffff60b`45910a80 00000000`00000008 : 0x0000008e`924fc610
fffff60b`45910a78 00000000`00501802 : ffffc025`8f011bf4 fffff60b`45910a80 00000000`00000008 fffff181`111b2df6 : 0x9000.
fffff60b`45910a80 ffffc025`8f011bf3 : fffff60b`45910a80 00000000`00000008 fffff181`111b2df6 ffff8d84`cc5b4080 : 0x501802.
fffff60b`45910a88 fffff60b`45910a80 : 00000000`00000008 fffff181`111b2df6 ffff8d84`cc5b4080 fffff800`4e80ff78 : win32k!NtGdiDdDDIPollDisplayChildren+0x13
fffff60b`45910a90 00000000`00000008 : fffff181`111b2df6 ffff8d84`cc5b4080 fffff800`4e80ff78 fffff60b`45910b80 : 0xfffff60b`45910a80
fffff60b`45910a98 fffff181`111b2df6 : ffff8d84`cc5b4080 fffff800`4e80ff78 fffff60b`45910b80 ffff8d84`db181060 : 0x8.
fffff60b`45910aa0 ffff8d84`cc5b4080 : fffff800`4e80ff78 fffff60b`45910b80 ffff8d84`db181060 00000000`00000000 : 0xfffff181`111b2df6
fffff60b`45910aa8 fffff800`4e80ff78 : fffff60b`45910b80 ffff8d84`db181060 00000000`00000000 0000008e`924fd7b8 : 0xffff8d84`cc5b4080
fffff60b`45910ab0 00007ffa`76d75424 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3cd
0000008e`924fc4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`76d75424

SYMBOL_NAME: win32kbase!GreUnlockDwmState+2f

MODULE_NAME: win32kbase.

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.19041.3083

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 2f.

FAILURE_BUCKET_ID: AV_win32kbase!GreUnlockDwmState

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {b7fc9895-04d2-dd05-7033-67990cfe1f84}

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

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind.
that the kernel isn't allowed to have/catch (bound trap) or that.
is always instant death (double fault). The first number in the.
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these.
traps are. Here is a *portion* of those codes:
If kv shows a taskGate.
 use .tss on the part before the colon, then kv.
Else if kv shows a trapframe.
 use .trap on that value.
Else.
 .trap on the appropriate frame will show where the trap was taken.
 (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif.
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe181a5720e50.
Arg3: fffff80525c11385.
Arg4: fffff805435a4095.

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 15905.

 Key : Analysis.Elapsed.mSec
 Value: 16539.

 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: 217.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x1000007f.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: MEMORY_CORRUPTION_STRIDE

 Key : Failure.Hash
 Value: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

BUGCHECK_CODE: 7f.

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe181a5720e50.

BUGCHECK_P3: fffff80525c11385.

BUGCHECK_P4: fffff805435a4095.

FILE_IN_CAB: 062323-15593-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BAD_STACK_POINTER: fffff80525c11385.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RuntimeBroker.

UNALIGNED_STACK_POINTER: fffff80525c11385.

CHKIMG_EXTENSION: !chkimg -lo 50 -db !ahcache
16 errors : !ahcache (fffff805435a4081-fffff805435a4239)
fffff805435a4080 05 *ac 45 ff ff e9 cf fb ff *72 cc cc cc cc cc cc ..E......r......
fffff805435a4090 48 *6e 5c 24 08 57 48 83 ec *45 48 8b 8a b8 00 00 Hn\$.WH..EH.....
fffff805435a40a0 00 *08 8b da 48 c7 42 38 00 *7e 00 00 8b 41 18 48 ....H.B8.~...A.H
fffff805435a40b0 8b *82 20 c1 e8 02 44 0f b6 *9d 41 83 f9 0c 0f 83 .. ...D...A.....
...
fffff805435a4200 48 *7f 0f 10 41 40 0f 11 40 *b2 0f 10 49 50 0f 11 H...A@[email protected]..
fffff805435a4210 48 *b2 0f 10 41 60 0f 11 40 *b2 48 8b 49 70 48 89 H...A`[email protected].
fffff805435a4220 48 *f3 eb 09 8b d8 48 8b 7c *70 38 eb 6a 48 81 c3 H.....H.|p8.jH..
fffff805435a4230 70 *72 00 00 83 fe 06 0f 85 *72 00 00 00 48 8b 0d pr.......r...H..

MODULE_NAME: memory_corruption.

IMAGE_NAME: memory_corruption.

MEMORY_CORRUPTOR: STRIDE.

STACK_COMMAND: .cxr; .ecxr ; kb.

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup: memory_corruption.
---------

*******************************************************************************
* *
* 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: fffff802ce441970, memory referenced.
Arg2: 0000000000000010, X64: bit 0 set if the fault was due to a not-present PTE.
 bit 1 is set if the fault was due to a write, clear if a read.
 bit 3 is set if the processor decided the fault was due to a corrupted PTE.
 bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
 - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
 bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff802ce441970, If non-zero, the instruction address which referenced the bad memory.
 address.
Arg4: 0000000000000000, (reserved)

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

KEY_VALUES_STRING: 1

 Key : AV.Type
 Value: Execute.

 Key : Analysis.CPU.mSec
 Value: 1656.

 Key : Analysis.Elapsed.mSec
 Value: 1819.

 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: 171.

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x50.

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

 Key : Failure.Bucket
 Value: AV_X_(null)_BAD_IP_dxgkrnl!MONITOR_MGR::_GetMonitorInstance

 Key : Failure.Hash
 Value: {fa461f68-1be5-d318-a9e7-83abc6e8eb39}

BUGCHECK_CODE: 50.

BUGCHECK_P1: fffff802ce441970.

BUGCHECK_P2: 10.

BUGCHECK_P3: fffff802ce441970.

BUGCHECK_P4: 0

FILE_IN_CAB: 062323-15609-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

READ_ADDRESS: fffff80255efb390: 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
 fffff802ce441970.

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

TRAP_FRAME: ffffac87b2d2c550 -- (.trap 0xffffac87b2d2c550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff850906afb840 rbx=0000000000000000 rcx=ffff85090f159cb0
rdx=45894c000000a89d rsi=0000000000000000 rdi=0000000000000000
rip=fffff802ce441970 rsp=ffffac87b2d2c6e8 rbp=ffff85090f159cb0
 r8=ffff850906afb801 r9=ffffac87b2d2c780 r10=f80255433630ffff
r11=ffffac87b2d2c800 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc.
fffff802`ce441970 ?? ???
Resetting default scope.

FAILED_INSTRUCTION_ADDRESS:
+0
fffff802`ce441970 ?? ???

STACK_TEXT:
ffffac87`b2d2c2a8 fffff802`5564b203 : 00000000`00000050 fffff802`ce441970 00000000`00000010 ffffac87`b2d2c550 : nt!KeBugCheckEx
ffffac87`b2d2c2b0 fffff802`5546e7b0 : 00000000`00000000 00000000`00000010 ffffac87`b2d2c5d0 00000000`00000000 : nt!MiSystemFault+0x1b2813
ffffac87`b2d2c3b0 fffff802`5560bad8 : ffff8509`10177730 fffff802`55401969 00000000`00000799 00000000`00000000 : nt!MmAccessFault+0x400
ffffac87`b2d2c550 fffff802`ce441970 : fffff802`85f56362 ffff8509`101776d0 fffff802`55420ceb ffff8509`10177080 : nt!KiPageFault+0x358
ffffac87`b2d2c6e8 fffff802`85f56362 : ffff8509`101776d0 fffff802`55420ceb ffff8509`10177080 ffff8509`0f0d5088 : 0xfffff802`ce441970
ffffac87`b2d2c6f0 fffff802`85f56284 : ffff8509`0f159cb0 00000000`00000104 ffffac87`b2d2c7b8 fffff802`85e3642d : dxgkrnl!MONITOR_MGR::_GetMonitorInstance+0x5a
ffffac87`b2d2c730 fffff802`860d3d14 : 00000000`00000000 00000000`00000000 ffffac87`b2d2c7d9 ffffae8d`51790750 : dxgkrnl!MonitorGetMonitorHandle+0x94
ffffac87`b2d2c780 fffff802`860d84a2 : 000001fd`2a857aa0 000001fd`2a857aa0 00000000`00000020 ffffac87`b2d2c938 : dxgkrnl!PopulateHDRMetadataFromDisplay+0x124
ffffac87`b2d2c840 fffff802`5560f7f8 : ffff8509`10177080 ffff8509`10177080 00000000`00000001 00000000`00000000 : dxgkrnl!DxgkPresentMultiPlaneOverlay3+0x3d2
ffffac87`b2d2cb00 00007ffe`5d1d5484 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000f7`282fc8f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5d1d5484

SYMBOL_NAME: dxgkrnl!MONITOR_MGR::_GetMonitorInstance+5a

MODULE_NAME: dxgkrnl.

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.2913

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 5a.

FAILURE_BUCKET_ID: AV_X_(null)_BAD_IP_dxgkrnl!MONITOR_MGR::_GetMonitorInstance

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {fa461f68-1be5-d318-a9e7-83abc6e8eb39}

Followup: MachineOwner.
---------
Genişletmek için tıkla...

Termal değişimi yapmadan önce herhangi bir mavi ekran almadım.
RAM'leri de çıkartıp silgiyle temizledim.
Fakat şöyle bir sorun oluştu soğutucu fanı takmaya çalışırken vida yuvalarının hafif içeri göçük olduğunu gördüm ne yapsamda eski haline getiremedim daha sonra kasayı yatay poziyondan dikey pozisyona çekince hafif düzeliyor gibi gözüküyorlardı daha sonra arka kapağı açmadan işlemci plakasının olduğu yere hafif bir baskı yaptım ve bir nebzede olsa yuvalar yerine geldi fakat 4 yuvadan sadece 1 tanesini vidalayamadım çünkü konumları bir türlü denk gelmiyordu. Şöyle bir ayrıntıyı da vermek isterim: Yeni bir ATX kasaya geçtim ve kasayı Vatan Bilgisayar'dan aldım eski kasadan yeni kasaya parça aktarımını vatan bilgisayarda ki çalışan birinden yapmasını istedim ve isteğimi kabul ettiler. Yani eski kasa olduğu zamanda bir keresine gene termal değiştirdim ve herhangi bir problem yaşmadım vidalar konusunda fakat bu yeni kasayı aldıktan sonra ilk açışım ve böyle bir sorun ilen karşılaştım.

wedw.jpg

Yaklaşık 2 saattir bilgisayarı sadece googe Chrome üzerinden kullanıyorum herhangi bir oyuna giriş yapmadım ve son olarak şunu da eklemek istiyorum termal macunum fazla kalmadığı için tam yetecek kadar bir macun süremedim ve ek olarak Adana'da yaşıyorum ve Adana'nın hava sıcaklığını biliyorsanız çok sıcak ve bunun ısınmaya çok etkisi var bugün araç içi termometreler 47 dereceyi gösterdi.
 
Artı 0 Eksi
Evet ortam sıcaklığı, termal macunun yeteri kadar ve doğru uygulanması, kasanın hava akışı ve soğutucunun doğru montajı çok ama çok önemli.

Neredeyse boşta diyebileceğimiz bir kullanım senaryosu varken işlemciniz 70 derece. Çok yüksek. Oyunda falan da değilsiniz yani.

Kasanızın önü mesh mi yani delikli ızgara şeklinde mi? Yoksa önü cam mı, yani kapalı mı?

En yakın zamanda kaliteli bir termal macun temin etmeye çalışın ve sürün.

Aşağıda saniyesiyle bir video atıyorum. Bu videoda anlatıldığı şekilde takıyorsunuz değil mi işlemci soğutucuyu? Yani çapraz bir şekilde sıkarak?

Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
 
Artı 0 Eksi
EgeN7 dedi:
Evet ortam sıcaklığı, termal macunun yeteri kadar ve doğru uygulanması, kasanın hava akışı ve soğutucunun doğru montajı çok ama çok önemli.

Neredeyse boşta diyebileceğimiz bir kullanım senaryosu varken işlemciniz 70 derece. Çok yüksek. Oyunda falan da değilsiniz yani.

Kasanızın önü mesh mi yani delikli ızgara şeklinde mi? Yoksa önü cam mı, yani kapalı mı?

En yakın zamanda kaliteli bir termal macun temin etmeye çalışın ve sürün.

Aşağıda saniyesiyle bir video atıyorum. Bu videoda anlatıldığı şekilde takıyorsunuz değil mi işlemci soğutucuyu? Yani çapraz bir şekilde sıkarak?

Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Genişletmek için tıkla...
EgeN7 dedi:
Evet ortam sıcaklığı, termal macunun yeteri kadar ve doğru uygulanması, kasanın hava akışı ve soğutucunun doğru montajı çok ama çok önemli.

Neredeyse boşta diyebileceğimiz bir kullanım senaryosu varken işlemciniz 70 derece. Çok yüksek. Oyunda falan da değilsiniz yani.

Kasanızın önü mesh mi yani delikli ızgara şeklinde mi? Yoksa önü cam mı, yani kapalı mı?

En yakın zamanda kaliteli bir termal macun temin etmeye çalışın ve sürün.

Aşağıda saniyesiyle bir video atıyorum. Bu videoda anlatıldığı şekilde takıyorsunuz değil mi işlemci soğutucuyu? Yani çapraz bir şekilde sıkarak?

Bu içeriği görüntülemek için üçüncü taraf çerezlerini yerleştirmek için izninize ihtiyacımız olacak.
Daha detaylı bilgi için, çerezler sayfamıza bakınız.
Genişletmek için tıkla...
Kasam:

POWERBOOST VK-M202B USB 3.0 MESH RGB FAN ATX SİYAH KASA fiyatı, teknik özellikleri, modelleri, en ucuz fiyatlarla Vatan Bilgisayar'da

POWERBOOST VK-M202B USB 3.0 MESH RGB FAN ATX SİYAH KASA fiyatı, teknik özellikleri, modelleri, en ucuz fiyatlarla Vatan Bilgisayar'da
www.vatanbilgisayar.com www.vatanbilgisayar.com

videoya gelirsek evet bu şekilde sıktım fakat dediğim gibi 4 yuvadan sadece bir tanesini vidalayamadım şu şekilde resimlendirmek isterim:
1687625575524.png


kullandığım termal macun ise:
Rampage TM-501 Termal Macun (bunu da aynı şekilde vatan bilgisayar'dan almıştım)
 
Artı 0 Eksi
Bahsettiğiniz Rampage macun ile alakalı Hepsiburada yorumları genelde olumlu. Ama aynı fiyatlara veya biraz daha yüksek fiyatlara daha kaliteli macunlar var.

Bu yaşadığınız vida problemi sebebiyle işlemcinin üstündeki termal macun ile soğutma bloğu arasındaki ısı transferi efektif bir şekilde gerçekleşmiyor gibi görünüyor. Ufak bir yamukluk veya hiza kayıklığı olsa dahi küçük boşluklar oluşacağından transfer düzgün gerçekleşmiyor.

Zayıf bir etkileşim var yüksek ihtimalle. Isı transferi az olunca da işlemci oluşan ısıyı soğutma bloğuna olması gerektiği şekilde aktaramıyor ve ısınmaya, boğulmaya başlıyor.

Vida zarar görmüşse yapacak bir şey yok gibi. Belki biraz daha düzlemeye çalışabilirsiniz. Vidalar da ne çok sıkı, ne çok gevşek olsun.
 
Artı 0 Eksi
EgeN7 dedi:
Bahsettiğiniz Rampage macun ile alakalı Hepsiburada yorumları genelde olumlu. Ama aynı fiyatlara veya biraz daha yüksek fiyatlara daha kaliteli macunlar var.

Bu yaşadığınız vida problemi sebebiyle işlemcinin üstündeki termal macun ile soğutma bloğu arasındaki ısı transferi efektif bir şekilde gerçekleşmiyor gibi görünüyor. Ufak bir yamukluk veya hiza kayıklığı olsa dahi küçük boşluklar oluşacağından transfer düzgün gerçekleşmiyor.

Zayıf bir etkileşim var yüksek ihtimalle. Isı transferi az olunca da işlemci oluşan ısıyı soğutma bloğuna olması gerektiği şekilde aktaramıyor ve ısınmaya, boğulmaya başlıyor.

Vida zarar görmüşse yapacak bir şey yok gibi. Belki biraz daha düzlemeye çalışabilirsiniz. Vidalar da ne çok sıkı, ne çok gevşek olsun.
Genişletmek için tıkla...

Kasayı tekrar açıp inceledim elimden geldiği kadar ve o son vidayı da tuturmaya çalıştım ama pek bir fark olmadı.
Büyük ihtimalle sürdüğüm termal macun yeterli gelmedi.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi

Benzer konular

Mustali
  • Soru
Termal macun değişimi sonrası mavi ekran hatası
Mesaj
2
Görüntüleme
319
Mustali
Mustali
E
  • Soru
RTX 3050 sistem termal macun değişimi sonrası mavi ekran veriyor
Mesaj
6
Görüntüleme
122
erdonc00
E
T
  • Soru
Termal macun sürümü sonrası sistemde mavi ekran hatası
Mesaj
5
Görüntüleme
481
Enes3078
Enes3078
Buraksahbazz
  • Soru
Macun değişimi yaptıktan sonra mavi ekran hatası
Mesaj
1
Görüntüleme
195
Muhsmmed Özdemir
M
L
  • Soru
Ryzen 5 2600X sistemde termal macun değişimi ardından mavi ekran hataları
Mesaj
4
Görüntüleme
144
Last Jeager
L

Yeni konular

Yeni mesajlar

Geri
Yukarı