Oyun Oynarken Sistem Kapanıyor

Birhibile · 27 Eylül 2022

Merhabalar,

Oyun oynarken sistemim kapandı durduk yere. Dump dosyasının içeriğini ekliyorum aşağıya. ROGLiveService.exe sanırım Armoury Crate'ten geliyor. Bütün RGB uygulamalarını kaldırıyorum bakalım ama fikrinizi almak için de konu açıyorum. Hatanın sebebini bulabilecek var mı?

Bu esnada Frostpunk oynuyordum. Dün de crash yedim ama OC yapmıştım denemek için zaten AMD Software da Wattman hatası var demişti. Bu sefer Wattman almadım, ayarlar da default. Tesadüfen mi denk geldi bilmiyorum.

Kod:

Microsoft (R) Windows Debugger Version 10.0.22621.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092722-7796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`82600000 PsLoadedModuleList = 0xfffff803`8322a270
Debug session time: Tue Sep 27 19:54:36.846 2022 (UTC + 3:00)
System Uptime: 0 days 1:13:18.849
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffff90c85ffd8d60, 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: fffff8038283b117, address which referenced memory

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2827

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 33344

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  092722-7796-01.dmp

BUGCHECK_CODE:  a

BUGCHECK_P1: ffff90c85ffd8d60

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8038283b117

WRITE_ADDRESS: fffff803832fb390: 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
 ffff90c85ffd8d60

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  ROGLiveService.exe

TRAP_FRAME:  fffffa027bda7690 -- (.trap 0xfffffa027bda7690)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0a00000126c89867 rbx=0000000000000000 rcx=1a00000126c89867
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8038283b117 rsp=fffffa027bda7820 rbp=0000000000000000
 r8=0a00000126c89867  r9=ffffe20439ce1700 r10=ffff90c864321fff
r11=ffff90c864321fff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiLockPageTableInternal+0xd7:
fffff803`8283b117 f0480fb10f      lock cmpxchg qword ptr [rdi],rcx ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
fffffa02`7bda7548 fffff803`82a0b069     : 00000000`0000000a ffff90c8`5ffd8d60 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa02`7bda7550 fffff803`82a07369     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffa02`7bda7690 fffff803`8283b117     : ffffe204`45f21a20 fffff803`7e384a36 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffffa02`7bda7820 fffff803`8283a2db     : fffffa02`7bda79e0 ffff90c8`00000000 00000000`00000002 ffff90c8`5ffd8d60 : nt!MiLockPageTableInternal+0xd7
fffffa02`7bda7890 fffff803`8283974a     : 00000000`00000000 fffff479`00000000 000000ac`598ff150 00000000`00000000 : nt!MiUserFault+0x61b
fffffa02`7bda7920 fffff803`82a0725e     : 00000000`00000000 ffffe204`40b94080 ffffffff`ffb3b4c0 00000000`00000000 : nt!MmAccessFault+0x16a
fffffa02`7bda7ac0 00007ff6`35520304     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
000000ac`598ff180 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`35520304


SYMBOL_NAME:  nt!MiLockPageTableInternal+d7

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2075

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  d7

FAILURE_BUCKET_ID:  AV_nt!MiLockPageTableInternal

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ec75f940-be6d-bedd-fb38-d04291f99c16}

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

Bu da Wattman hatası aldığım zamanki. Alakalı mı bilmiyorum ama ekliyorum yine de.

Kod:

Microsoft (R) Windows Debugger Version 10.0.22621.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092622-9265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`0ac00000 PsLoadedModuleList = 0xfffff805`0b82a270
Debug session time: Mon Sep 26 21:00:34.901 2022 (UTC + 3:00)
System Uptime: 0 days 21:14:14.537
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: ffff800079656034, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3156

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17001

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  092622-9265-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: ffff800079656034

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  53ffff4104080010 -- (.trap 0x53ffff4104080010)
Unable to read trap frame at 53ffff41`04080010

STACK_TEXT: 
ffff8000`625128e8 fffff805`0b03ce15     : 00000000`0000001e ffffffff`c0000096 ffff8000`79656034 00000000`00000000 : nt!KeBugCheckEx
ffff8000`625128f0 fffff805`0aff9f72     : 006e0049`00650063 0d020078`00650064 53ffff41`04080010 4400046f`8a000000 : nt!KiDispatchException+0x1c6925
ffff8000`62512fb0 fffff805`0aff9f40     : fffff805`0b00b1a5 fffff805`0aff51d0 fffff805`0affff0f 00000000`00000003 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffffd84`19f66a78 fffff805`0b00b1a5     : fffff805`0aff51d0 fffff805`0affff0f 00000000`00000003 ffffa981`ded572d0 : nt!KiExceptionDispatchOnExceptionStackContinue
fffffd84`19f66a80 fffff805`0b006ee0     : fffffd84`19f66d4c ffff9989`aa8af0c0 fffffd84`79517350 fffffd84`19f66c90 : nt!KiExceptionDispatch+0x125
fffffd84`19f66c60 ffff8000`79656034     : ffff8000`796401c3 00000000`00000001 ffff8000`796401c3 ffffffff`b8797400 : nt!KiGeneralProtectionFault+0x320
fffffd84`19f66df0 ffff8000`796401c3     : 00000000`00000001 ffff8000`796401c3 ffffffff`b8797400 00000000`00000000 : 0xffff8000`79656034
fffffd84`19f66df8 00000000`00000001     : ffff8000`796401c3 ffffffff`b8797400 00000000`00000000 fffff805`0f414960 : 0xffff8000`796401c3
fffffd84`19f66e00 ffff8000`796401c3     : ffffffff`b8797400 00000000`00000000 fffff805`0f414960 00000000`0000ffff : 0x1
fffffd84`19f66e08 ffffffff`b8797400     : 00000000`00000000 fffff805`0f414960 00000000`0000ffff 00000000`00000000 : 0xffff8000`796401c3
fffffd84`19f66e10 00000000`00000000     : fffff805`0f414960 00000000`0000ffff 00000000`00000000 ffffa981`00000000 : 0xffffffff`b8797400


SYMBOL_NAME:  nt!KiDispatchException+1c6925

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2075

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c6925

FAILURE_BUCKET_ID:  0x1E_C0000096_nt!KiDispatchException

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {505cfaff-0bdc-8a96-0650-5a81952f0ba1}

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

Criesley · 27 Eylül 2022

Ram hatası gibi ama başka yorumlara da bakın bir ramleri test edin. Başka hata da olabilir.

Birhibile · 27 Eylül 2022

Criesley dedi:
Ram hatası gibi ama başka yorumlara da bakın bir ramleri test edin. Başka hata da olabilir.

Nereden vardınız bu kanıya onu da söyleyebilir misiniz?

Şimdi de başka bir hata aldım. Armour Crate değilmiş gibi. Yine oyun oynuyordum. AMD Adrenaline de ayarlar default'a alındı diye uyarı verdi.

Kod:

Microsoft (R) Windows Debugger Version 10.0.22621.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092722-8437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`72c00000 PsLoadedModuleList = 0xfffff800`7382a270
Debug session time: Tue Sep 27 21:43:41.462 2022 (UTC + 3:00)
System Uptime: 0 days 1:18:03.070
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
13: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000000, A stack-based buffer has been overrun.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000002, Reserved

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2624

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19306

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  092722-8437-01.dmp

BUGCHECK_CODE:  139

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 2

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff585`8ecef748 fffff800`73001c1b     : 00000000`00000139 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff585`8ecef750 fffff800`7307c547     : fffff800`73820de0 00000000`00000000 00000000`00000001 ffff9a00`9aaad240 : nt!guard_icall_bugcheck+0x1b
fffff585`8ecef780 fffff800`72edb5e0     : fffff585`8ecefaf0 ffff9a00`9aaaa180 00000e87`3da25ad0 ffff9a00`9aaaa180 : nt!PpmCheckReportComplete+0x13a3c7
fffff585`8ecef7b0 fffff800`72e3489e     : ffff9a00`9aaad240 ffffaa8f`a91e7000 00000000`00000004 ffff9a00`00000002 : nt!PpmCheckRun+0x40
fffff585`8ecef820 fffff800`72e33b84     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff585`8ecef990 fffff800`72ffcc7e     : ffffffff`00000000 ffff9a00`9aaaa180 ffff9a00`9aab5440 ffffaa8f`b67210c0 : nt!KiRetireDpcList+0x1f4
fffff585`8ecefc20 00000000`00000000     : fffff585`8ecf0000 fffff585`8ece9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!guard_icall_bugcheck+1b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2075

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1b

FAILURE_BUCKET_ID:  0x139_0_LEGACY_GS_VIOLATION_nt!guard_icall_bugcheck

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9bee41a7-2ef9-07ca-7e59-7d5a0c6e2d05}

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

Bellek sıkıntılı çıktı arkadaşlar. DOCP ile ayarlayınca 3603MHz ayarlıyor. Elimle kurcalıycam biraz bakalım.

Memtest64 ile anladım.

Voltajı 1.35'den 1.375'e çıkardım, memtest64'daki hatalar gitti. Böyle kullanmaya devam edicem bir süre.

1.5 saattir sıkıntı yok. Normalde 20-30 dk içinde çöküyordu sistem.

Criesley · 28 Eylül 2022

Sorun ram de çıktı demi hocam ?

Birhibile · 28 Eylül 2022

Criesley dedi:
Sorun ram de çıktı demi hocam ?

Evet. Docp ayarları stabil değil. Voltaj artırdım sıkıntı geçti gibi.

Oyun Oynarken Sistem Kapanıyor

Ayrıntılı düzenleme

Birhibile

Hectopat

Criesley

Kilopat

Birhibile

Hectopat

Criesley

Kilopat

Birhibile

Hectopat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz