Oyundan Çıkarken UNEXPECTED_KERNEL_MODE_TRAP Mavi Ekran

jeunesturcs

Kilopat
Katılım
28 Ekim 2019
Mesajlar
873
Çözümler
14
Daha fazla  
Cinsiyet
Erkek
Meslek
Sosyolog
Öncelikle merhaba, ilginç bir sorunum var. Oyun oynarken değil de oyundan çıkarken PC'nin görüntüsü gidiyor ve bir süre sonra yeniden başlıyor. Anladığım kadarıyla bu süreçte mavi ekran veriyor fakat görüntü gelmediği için göremiyorum. Şöyle ki uzun süre Battlefield V veya Battlefield 1 oynadıktan sonra oyundan çıkmak istediğimde ekrana görüntü gelmemeye başlıyor. Ancak oyunu beş saat altı saat bile oynasam herhangi bir ısınma, takılma, hata söz konusu değil. Aynı hatayı WATCH_DOGS oyununda da yaşadım ve oyundan çıktığımda mavi ekran hatası verdi. Bu mavi ekranı BF 1 oynadıktan sonra da görmüştüm. Fakat şöyle bir durum var. Diğer oynadığım oyunlarda herhangi bir sıkıntı yok. Demek istediğim BF'den daha ağır olan Metro Exodus veya CoH 2 gibi oyunlar oynarsam herhangi bir sorunla karşılaşmıyorum. Eğer hata veren oyunları Alt+Tab yaparsam sıkıntısız bir şekilde kapatabiliyorum. RAM testi yaptım ancak bir sorun bulunamadı. Acaba bu hatalarla karşılaşan var mı? Formatla çözülebilecek bir şey mi? Minidump dosyalarını ekliyorum. Eğer okumasını bilen varsa çok memnun olurum.

Minidump

Sistem:
  • AMD Ryzen 2600
  • AMD RX 580 8 GB
  • 3000 MHz 8 GB RAM
  • 480 GB SSD
 
Son düzenleyen: Moderatör:
BIOS'u güncelleyin ve herhangi bir bileşende overclock varsa kaldırın. Ekran kartı sürücü sürümü nedir? Anakart modelini de belirtin.
Sorun çözümü için BIOS güncellemesi ve ekran kartı güncellemesini dün yaptım ancak hala değişen bir şey olmadı. Anakart modeli Gigabyte B450M S2h.
Ekran kartı Sapphire Rx 580 Pulse OC
Fabrika çıkışlı Oc olduğu için herhangi bir müdahalede veya ayarda bulunmadım. Zaten ayarları da fabrika ayarlarına döndürdüm birkaç kere ancak sonuç yine değişmedi. Adrenalin 2019 Edition 19.9.2 sürücüsü kuruluydu ve sorunlar çözülür diye Adrenalin 2019 Edition 19.10.2 kurdum fakat değişen bir şey yok hiç.
Amd Ryzen Master kurulu ve onda Game Mode'a almıştım fakat yine de birkaç kez fabrika ayarlarına döndürmüştüm. 2600 işlemci olduğu için Oc olacağını zannetmiyorum. Acaba imkanı var mı?
Ha bir de XMP profilini açarak Ram'i 3000 Mhz yaptım ancak bunda bir sakınca olacağını hiç düşünmedim, sonuçta Ram'i 3000 Mhz olarak aldım.
 
Son düzenleme:
Gıgabyte ve AMD araçlarını kaldır. BIOS'a gir ve optimize defaults save yap. XMP kapat. Birde PSU nedir? Güç ile ilgili bir problem var gibi bilgin olsun.
Kod:
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: ffffad8085b0b1b0
Arg3: ffffeb0479a69fe0
Arg4: fffff8066966b4f6

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 12

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 37

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffad8085b0b1b0

BUGCHECK_P3: ffffeb0479a69fe0

BUGCHECK_P4: fffff8066966b4f6

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

STACK_OVERFLOW: Stack Limit: ffffeb0479a6a000. Use (kF) and (!stackusage) to investigate stack usage.

STACK_TEXT:
ffffad80`85b0b068 fffff806`697d30e9 : 00000000`0000007f 00000000`00000008 ffffad80`85b0b1b0 ffffeb04`79a69fe0 : nt!KeBugCheckEx
ffffad80`85b0b070 fffff806`697cdf45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffad80`85b0b1b0 fffff806`6966b4f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5
ffffeb04`79a69fe0 fffff806`697164db : ffffeb04`79a6b9f0 ffffeb04`79a6a0f0 00000000`00000000 fffff806`697bd46a : nt!KeQueryCurrentStackInformationEx+0x36
ffffeb04`79a6a030 fffff806`697c96e0 : 00000000`00000000 ffffeb04`79a6b7b8 fffff806`69b19790 fffff806`697ca0d2 : nt!KeCheckStackAndTargetAddress+0x2b
ffffeb04`79a6a060 fffff806`696c5a22 : 00000000`00000000 ffffeb04`79a6b860 ffffeb04`79a6a5f0 ffffeb04`79a6b9f0 : nt!RtlRestoreContext+0x1e0
ffffeb04`79a6a0b0 fffff806`6979c3df : fffff806`718ab6f4 ffffeb04`00000001 ffffeb04`79a6b9f0 ffffeb04`79a70000 : nt!RtlUnwindEx+0x6f2
ffffeb04`79a6a7e0 fffff806`697ca052 : ffffeb04`79a6b9f0 ffffeb04`79a6adc0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xef
ffffeb04`79a6a850 fffff806`696c3375 : ffffeb04`79a6b7b8 00000000`00000000 ffffeb04`79a6adc0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffeb04`79a6a880 fffff806`696c790e : ffffeb04`79a6b7b8 ffffeb04`79a6b500 ffffeb04`79a6b7b8 00000000`00299000 : nt!RtlDispatchException+0x4a5
ffffeb04`79a6afd0 fffff806`697d321d : ffffd2e9`74ba5000 ffffeb04`79a6b860 ffff8000`00000000 00000000`0029a7b8 : nt!KiDispatchException+0x16e
ffffeb04`79a6b680 fffff806`697cf405 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffeb04`79a6b918 : nt!KiExceptionDispatch+0x11d
ffffeb04`79a6b860 fffff806`7189ad35 : 00000000`00000003 ffffeb04`79a6ba68 01d58d67`6ba93334 00000000`00000000 : nt!KiPageFault+0x445
ffffeb04`79a6b9f0 fffff806`718ef4df : ffffeb04`79a6bc38 00000000`00000000 00000000`00000000 ffffd707`20ea6cb0 : cldflt!HsmOsIsCbdTransacted+0x41
ffffeb04`79a6ba30 fffff806`718f0019 : 00000000`00000000 ffffd707`268f5ba8 ffffd707`203b8b30 ffffeb04`79a6bc79 : cldflt!HsmiFltPreECPCREATE+0xaf
ffffeb04`79a6bba0 fffff806`6e0e4a5c : ffffd707`268f59a0 00000000`00000000 ffffd707`00000003 00000000`00000000 : cldflt!HsmFltPreCREATE+0x9
ffffeb04`79a6bbd0 fffff806`6e0e45a0 : ffffeb04`79a6bd50 ffffeb04`79a6bd00 ffffd707`2c6c0000 00000000`00000000 : FLTMGR!FltpPerformPreCallbacks+0x2fc
ffffeb04`79a6bce0 fffff806`6e11cd13 : fffff806`6e109060 00000000`00000050 00000020`00000000 00000000`00000000 : FLTMGR!FltpPassThroughInternal+0x90
ffffeb04`79a6bd10 fffff806`69631f39 : 00000000`00000000 fffff806`69be5904 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x2f3
ffffeb04`79a6bdc0 fffff806`69630fe4 : 00000000`00000003 00000000`00000000 00000000`00000000 fffff806`696317a3 : nt!IofCallDriver+0x59
ffffeb04`79a6be00 fffff806`69be5ffb : ffffeb04`79a6c0c0 fffff806`69be5904 ffffeb04`79a6c030 ffffd707`2ba6e9a0 : nt!IoCallDriverWithTracing+0x34
ffffeb04`79a6be50 fffff806`69becfcf : ffffd707`203668f0 ffffd707`20366804 ffffd707`27a924e0 00000000`00000000 : nt!IopParseDevice+0x62b
ffffeb04`79a6bfc0 fffff806`69beb431 : ffffd707`27a92400 ffffeb04`79a6c208 00000002`000002c0 ffffd707`1aaf5400 : nt!ObpLookupObjectName+0x78f
ffffeb04`79a6c180 fffff806`69c30300 : ffffffff`00000001 ffffeb04`79a6c6c0 00000000`00000000 ffffad80`85b00180 : nt!ObOpenObjectByNameEx+0x201
ffffeb04`79a6c2c0 fffff806`69c2fac9 : ffffeb04`79a6c660 ffffc108`00000000 ffffeb04`79a6c6c0 ffffeb04`79a6c6a0 : nt!IopCreateFile+0x820
ffffeb04`79a6c360 fffff806`697d2b18 : ffffc108`d5a05b00 fffff806`00000040 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x79
ffffeb04`79a6c3f0 fffff806`697c5060 : fffff806`74a694ae 00000000`00000016 ffffeb04`79a6c700 00000000`0000012c : nt!KiSystemServiceCopyEnd+0x28
ffffeb04`79a6c5f8 fffff806`74a694ae : 00000000`00000016 ffffeb04`79a6c700 00000000`0000012c ffffec02`a777b930 : nt!KiServiceLinkage
ffffeb04`79a6c600 00000000`00000016 : ffffeb04`79a6c700 00000000`0000012c ffffec02`a777b930 ffffeb04`79a6c688 : atikmdag+0x694ae
ffffeb04`79a6c608 ffffeb04`79a6c700 : 00000000`0000012c ffffec02`a777b930 ffffeb04`79a6c688 00000000`00000080 : 0x16
ffffeb04`79a6c610 00000000`0000012c : ffffec02`a777b930 ffffeb04`79a6c688 00000000`00000080 00000000`00000001 : 0xffffeb04`79a6c700
ffffeb04`79a6c618 ffffec02`a777b930 : ffffeb04`79a6c688 00000000`00000080 00000000`00000001 ffffc108`00000003 : 0x12c
ffffeb04`79a6c620 ffffeb04`79a6c688 : 00000000`00000080 00000000`00000001 ffffc108`00000003 00000000`00000021 : 0xffffec02`a777b930
ffffeb04`79a6c628 00000000`00000080 : 00000000`00000001 ffffc108`00000003 00000000`00000021 00000000`00000000 : 0xffffeb04`79a6c688
ffffeb04`79a6c630 00000000`00000001 : ffffc108`00000003 00000000`00000021 00000000`00000000 ffffeb04`00000000 : 0x80
ffffeb04`79a6c638 ffffc108`00000003 : 00000000`00000021 00000000`00000000 ffffeb04`00000000 fffff806`69633254 : 0x1
ffffeb04`79a6c640 00000000`00000021 : 00000000`00000000 ffffeb04`00000000 fffff806`69633254 00000000`00000000 : 0xffffc108`00000003
ffffeb04`79a6c648 00000000`00000000 : ffffeb04`00000000 fffff806`69633254 00000000`00000000 ffffc108`012c0016 : 0x21


SYMBOL_NAME: cldflt!HsmOsIsCbdTransacted+41

MODULE_NAME: cldflt

IMAGE_NAME:  cldflt.sys

IMAGE_VERSION: 10.0.18362.1034

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 41

FAILURE_BUCKET_ID: 0x7f_8_cldflt!HsmOsIsCbdTransacted

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3df30f89-f82f-1e80-218f-4990f13904d4}

Followup:     MachineOwner
 
Gıgabyte ve AMD araçlarını kaldır. BIOS'a gir ve optimize defaults save yap. XMP kapat. Birde PSU nedir? Güç ile ilgili bir problem var gibi bilgin olsun.
Kod:
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: ffffad8085b0b1b0
Arg3: ffffeb0479a69fe0
Arg4: fffff8066966b4f6

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 12

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 37

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffad8085b0b1b0

BUGCHECK_P3: ffffeb0479a69fe0

BUGCHECK_P4: fffff8066966b4f6

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

STACK_OVERFLOW: Stack Limit: ffffeb0479a6a000. Use (kF) and (!stackusage) to investigate stack usage.

STACK_TEXT:
ffffad80`85b0b068 fffff806`697d30e9 : 00000000`0000007f 00000000`00000008 ffffad80`85b0b1b0 ffffeb04`79a69fe0 : nt!KeBugCheckEx
ffffad80`85b0b070 fffff806`697cdf45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffad80`85b0b1b0 fffff806`6966b4f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5
ffffeb04`79a69fe0 fffff806`697164db : ffffeb04`79a6b9f0 ffffeb04`79a6a0f0 00000000`00000000 fffff806`697bd46a : nt!KeQueryCurrentStackInformationEx+0x36
ffffeb04`79a6a030 fffff806`697c96e0 : 00000000`00000000 ffffeb04`79a6b7b8 fffff806`69b19790 fffff806`697ca0d2 : nt!KeCheckStackAndTargetAddress+0x2b
ffffeb04`79a6a060 fffff806`696c5a22 : 00000000`00000000 ffffeb04`79a6b860 ffffeb04`79a6a5f0 ffffeb04`79a6b9f0 : nt!RtlRestoreContext+0x1e0
ffffeb04`79a6a0b0 fffff806`6979c3df : fffff806`718ab6f4 ffffeb04`00000001 ffffeb04`79a6b9f0 ffffeb04`79a70000 : nt!RtlUnwindEx+0x6f2
ffffeb04`79a6a7e0 fffff806`697ca052 : ffffeb04`79a6b9f0 ffffeb04`79a6adc0 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xef
ffffeb04`79a6a850 fffff806`696c3375 : ffffeb04`79a6b7b8 00000000`00000000 ffffeb04`79a6adc0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
ffffeb04`79a6a880 fffff806`696c790e : ffffeb04`79a6b7b8 ffffeb04`79a6b500 ffffeb04`79a6b7b8 00000000`00299000 : nt!RtlDispatchException+0x4a5
ffffeb04`79a6afd0 fffff806`697d321d : ffffd2e9`74ba5000 ffffeb04`79a6b860 ffff8000`00000000 00000000`0029a7b8 : nt!KiDispatchException+0x16e
ffffeb04`79a6b680 fffff806`697cf405 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffeb04`79a6b918 : nt!KiExceptionDispatch+0x11d
ffffeb04`79a6b860 fffff806`7189ad35 : 00000000`00000003 ffffeb04`79a6ba68 01d58d67`6ba93334 00000000`00000000 : nt!KiPageFault+0x445
ffffeb04`79a6b9f0 fffff806`718ef4df : ffffeb04`79a6bc38 00000000`00000000 00000000`00000000 ffffd707`20ea6cb0 : cldflt!HsmOsIsCbdTransacted+0x41
ffffeb04`79a6ba30 fffff806`718f0019 : 00000000`00000000 ffffd707`268f5ba8 ffffd707`203b8b30 ffffeb04`79a6bc79 : cldflt!HsmiFltPreECPCREATE+0xaf
ffffeb04`79a6bba0 fffff806`6e0e4a5c : ffffd707`268f59a0 00000000`00000000 ffffd707`00000003 00000000`00000000 : cldflt!HsmFltPreCREATE+0x9
ffffeb04`79a6bbd0 fffff806`6e0e45a0 : ffffeb04`79a6bd50 ffffeb04`79a6bd00 ffffd707`2c6c0000 00000000`00000000 : FLTMGR!FltpPerformPreCallbacks+0x2fc
ffffeb04`79a6bce0 fffff806`6e11cd13 : fffff806`6e109060 00000000`00000050 00000020`00000000 00000000`00000000 : FLTMGR!FltpPassThroughInternal+0x90
ffffeb04`79a6bd10 fffff806`69631f39 : 00000000`00000000 fffff806`69be5904 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x2f3
ffffeb04`79a6bdc0 fffff806`69630fe4 : 00000000`00000003 00000000`00000000 00000000`00000000 fffff806`696317a3 : nt!IofCallDriver+0x59
ffffeb04`79a6be00 fffff806`69be5ffb : ffffeb04`79a6c0c0 fffff806`69be5904 ffffeb04`79a6c030 ffffd707`2ba6e9a0 : nt!IoCallDriverWithTracing+0x34
ffffeb04`79a6be50 fffff806`69becfcf : ffffd707`203668f0 ffffd707`20366804 ffffd707`27a924e0 00000000`00000000 : nt!IopParseDevice+0x62b
ffffeb04`79a6bfc0 fffff806`69beb431 : ffffd707`27a92400 ffffeb04`79a6c208 00000002`000002c0 ffffd707`1aaf5400 : nt!ObpLookupObjectName+0x78f
ffffeb04`79a6c180 fffff806`69c30300 : ffffffff`00000001 ffffeb04`79a6c6c0 00000000`00000000 ffffad80`85b00180 : nt!ObOpenObjectByNameEx+0x201
ffffeb04`79a6c2c0 fffff806`69c2fac9 : ffffeb04`79a6c660 ffffc108`00000000 ffffeb04`79a6c6c0 ffffeb04`79a6c6a0 : nt!IopCreateFile+0x820
ffffeb04`79a6c360 fffff806`697d2b18 : ffffc108`d5a05b00 fffff806`00000040 00000000`00000000 00000000`00000000 : nt!NtCreateFile+0x79
ffffeb04`79a6c3f0 fffff806`697c5060 : fffff806`74a694ae 00000000`00000016 ffffeb04`79a6c700 00000000`0000012c : nt!KiSystemServiceCopyEnd+0x28
ffffeb04`79a6c5f8 fffff806`74a694ae : 00000000`00000016 ffffeb04`79a6c700 00000000`0000012c ffffec02`a777b930 : nt!KiServiceLinkage
ffffeb04`79a6c600 00000000`00000016 : ffffeb04`79a6c700 00000000`0000012c ffffec02`a777b930 ffffeb04`79a6c688 : atikmdag+0x694ae
ffffeb04`79a6c608 ffffeb04`79a6c700 : 00000000`0000012c ffffec02`a777b930 ffffeb04`79a6c688 00000000`00000080 : 0x16
ffffeb04`79a6c610 00000000`0000012c : ffffec02`a777b930 ffffeb04`79a6c688 00000000`00000080 00000000`00000001 : 0xffffeb04`79a6c700
ffffeb04`79a6c618 ffffec02`a777b930 : ffffeb04`79a6c688 00000000`00000080 00000000`00000001 ffffc108`00000003 : 0x12c
ffffeb04`79a6c620 ffffeb04`79a6c688 : 00000000`00000080 00000000`00000001 ffffc108`00000003 00000000`00000021 : 0xffffec02`a777b930
ffffeb04`79a6c628 00000000`00000080 : 00000000`00000001 ffffc108`00000003 00000000`00000021 00000000`00000000 : 0xffffeb04`79a6c688
ffffeb04`79a6c630 00000000`00000001 : ffffc108`00000003 00000000`00000021 00000000`00000000 ffffeb04`00000000 : 0x80
ffffeb04`79a6c638 ffffc108`00000003 : 00000000`00000021 00000000`00000000 ffffeb04`00000000 fffff806`69633254 : 0x1
ffffeb04`79a6c640 00000000`00000021 : 00000000`00000000 ffffeb04`00000000 fffff806`69633254 00000000`00000000 : 0xffffc108`00000003
ffffeb04`79a6c648 00000000`00000000 : ffffeb04`00000000 fffff806`69633254 00000000`00000000 ffffc108`012c0016 : 0x21


SYMBOL_NAME: cldflt!HsmOsIsCbdTransacted+41

MODULE_NAME: cldflt

IMAGE_NAME:  cldflt.sys

IMAGE_VERSION: 10.0.18362.1034

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 41

FAILURE_BUCKET_ID: 0x7f_8_cldflt!HsmOsIsCbdTransacted

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {3df30f89-f82f-1e80-218f-4990f13904d4}

Followup:     MachineOwner
Psu:
High Power 600W 80 Plus bronze
Amd Ryzen Master'ı ve Gigabyte uygulamalarını kaldırıp deneyeyim bir de. Ancak Ram'de Xmp'yi kapatmak istemiyorum hiç. Evde voltaj sıkıntısı var. Bu nedenle oluyor olabilir mi? Fakat oyun oynarken ve birçok oyunda sorun yokken sadece bu oyunlarda olması çok ilginç geliyor.
Uygulamaları kaldırdım ancak Xmp’yi kapatmadım ve sonuç değişmedi.
Aynı zamanda aida64 ile stress test yaptım 15 dakika boyunca ve herhangi bir sorunla karşılaşmadım. İşlemci sıcaklığı 82 dereceye kadar ve gpu 75 dereceye çıktı. Ancak bu sırada mavi ekran vs. vermedi. Sanırım işletim sisteminde bir hata var gibi. Son çare format atacağım artık.
Bios default yapıp xmp’yi kapattım ancak yine devam ediyor.
 
Son düzenleme:
Uyarı! Bu konu 7 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı