Gameloop mavi ekran hatası

Gamezone

Hectopat
Katılım
15 Eylül 2019
Mesajlar
238
Çözümler
1
Oyunda hiçbir sebep olmadan Call of Duty kapatıp PUBG girmek istedim. Tam o sırada mavi ekran hatası verdi ve oyunlar silinmiş. Açmayı denedikçe aynı hata tekrarlanıyor. Ne yapmalıyım?
 
 

gameloop.rar bir tanesi yüklenmedi hata verdi bu var.
 
Minidump dosyalarına gerek yok oyuna güncelleme geldi onu yapıyorsun ve düzeliyor. Eğer düzelmezse oyunu Full sil yükle kesin düzelir. Pcyle alakalı bir sorun değildir. Tamamen oyun kaynaklı dediklerimi yerine getirirsen çözülecektir.
 
Tencent PUBG Mobile programı çöküyor ve sistemi kilitliyor, programı kaldır tekrar yükle.

Ayrıca şunu da bir dene;
DDU ile ekran kartı sürücüsünü kaldır tekrar yükle.
Kod:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 0000000080000003, Exception code that caused the bugcheck
Arg2: fffff8022a1c9218, Address of the instruction which caused the bugcheck
Arg3: ffffd208cb95e6f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.18362.657 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

DUMP_TYPE:  2

BUGCHECK_P1: 80000003

BUGCHECK_P2: fffff8022a1c9218

BUGCHECK_P3: ffffd208cb95e6f0

BUGCHECK_P4: 0

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Bir veya daha fazla ba  ms z de i ken ge ersiz

FAULTING_IP:
aow_drv_x64_ev+79218
fffff802`2a1c9218 cc              int     3

CONTEXT:  ffffd208cb95e6f0 -- (.cxr 0xffffd208cb95e6f0)
rax=0000000000000010 rbx=000000000000001a rcx=fffff8022a150000
rdx=fffff8022a1c9213 rsi=ffff8489d800a000 rdi=00000000ffffffda
rip=fffff8022a1c9218 rsp=ffffd208cb95f0e0 rbp=000000002332f00c
 r8=0000000000000163  r9=000000002332f00c r10=0000000000000228
r11=fffff8022a1c8ff0 r12=0000000000000001 r13=0000000000000000
r14=000000002d17ffd3 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00240206
aow_drv_x64_ev+0x79218:
fffff802`2a1c9218 cc              int     3
Resetting default scope

BUGCHECK_STR:  0x3B_80000003

CPU_COUNT: c

CPU_MHZ: 8a0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  aow_exe.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  02-25-2020 22:21:46.0313

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8022a1c9218

STACK_TEXT: 
ffffd208`cb95f0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff802`1195e848 00000000`00000000 : aow_drv_x64_ev+0x79218


THREAD_SHA1_HASH_MOD_FUNC:  8a96a27a415fe759db5d988341e37a9a5985827f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e2a0eb39e35fbd3fc0828f07d7f53aae1ef85dd1

THREAD_SHA1_HASH_MOD:  8a96a27a415fe759db5d988341e37a9a5985827f

FOLLOWUP_IP:
aow_drv_x64_ev+79218
fffff802`2a1c9218 cc              int     3

FAULT_INSTR_CODE:  247c83cc

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  aow_drv_x64_ev+79218

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aow_drv_x64_ev

IMAGE_NAME:  aow_drv_x64_ev.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5e1e8e6e

STACK_COMMAND:  .cxr 0xffffd208cb95e6f0 ; kb

BUCKET_ID_FUNC_OFFSET:  79218

FAILURE_BUCKET_ID:  0x3B_80000003_aow_drv_x64_ev!unknown_function

BUCKET_ID:  0x3B_80000003_aow_drv_x64_ev!unknown_function

PRIMARY_PROBLEM_CLASS:  0x3B_80000003_aow_drv_x64_ev!unknown_function

TARGET_TIME:  2020-02-25T17:54:16.000Z

OSBUILD:  18362

OSSERVICEPACK:  657

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2005-04-23 04:40:32

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.18362.657

ANALYSIS_SESSION_ELAPSED_TIME:  fc4

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_80000003_aow_drv_x64_ev!unknown_function

FAILURE_ID_HASH:  {4999ea8f-5610-f067-759d-ce2b7bc6ed1d}

Followup:     MachineOwner
---------
 
Windows Defender>Cihaz Güvenliği>Çekirdek yalıtımı ayarını kapatıp dener misin?
Ek Açıklama 2020-02-25 222713.png
 

Geri
Yukarı