BattlEye ve Faceit AC mavi ekran sorunu

MetCorleone

MetCorleone

Megapat
Katılım
31 Temmuz 2017
Mesajlar
487
Çözümler
4
Daha fazla  
Cinsiyet
Erkek
Zula'ya girerken mouse donuyor. Zula açılmadan bilgisayar kapanıyor ve mavi ekran veriyor. Aynı sorun PUBG'ye girerken de oluyor. İkisinde de Battleye var. O yüzden diye düşünüyorum. Nasıl çözeceğim, yardımcı olur musunuz?
 
Tarihe göre sırala Puana göre sırala
Temiz bir format attıktan sonra bilgisayara uygun tüm sürücüleri kendi sitelerinden tek tek indirerek kurunuz Windows'un kendi kurduğu sürücüler eski tarihli ve birçoğu da hatalı. BIOS güncelleyin.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Dediğiniz gibi bu siteden 4 adet driverı Windows 10 64 Bit için indirip kurdum. BIOS'u güncellemek için bu linkteki yöntemi kullandım. Diğer driverları setuplarından kurup bilgisayarı yeniden başlattım ve Black Squad oyununda denemek için oyuna girmeyi denedim ancak tekrar mavi ekran verdi. Bu da dumb file dosyası

1 Saat önce oynayabildiğim PUBG'yi tekrar denedim ve mavi ekran verdi. Ancak bu sefer DPC_WATCHDOG_VIOLATION hata kodu ile mavi ekran verdi. Pubg sonrası dumb file
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Bazı oyun kolları, gamepadler, direksiyon setlerinin yazılımları da bu hataya sebep olabiliyor onları kaldır.

Kardeşim bu işin kesin çözümü ise Windows Defender'dan BattleEye ve PUBG ile ilgili bütün klasörleri uygulamaları seçip hariç tutman gerekiyor. Hariç tut ya da dışlama diye bir seçenek olması lazım tam hatırlayamıyorum şuan. Yabancı bir forum sitesinde bulmuştum ve benim sorunumu kalıcı olarak çözdü.
 
Artı 0 Eksi
bysuvari dedi:
Bazı oyun kolları, gamepadler, direksiyon setlerinin yazılımları da bu hataya sebep olabiliyor onları kaldır.

Kardeşim bu işin kesin çözümü ise Windows Defender'dan BattleEye ve PUBG ile ilgili bütün klasörleri uygulamaları seçip hariç tutman gerekiyor. Hariç tut ya da dışlama diye bir seçenek olması lazım tam hatırlayamıyorum şu an. Yabancı bir forum sitesinde bulmuştum ve benim sorunumu kalıcı olarak çözdü.
Genişletmek için tıkla...
Şu an takılı Thurstmaster HOTAS X joystick var sadece ancak önceleri de bunu kullanıyordum ama hata vermiyordu. Genede denerim çıkartıp çalıştırmayı.

Battleye'ın dosyaları nerede bilmiyorum tam olarak o yüzden ekleyemedim ama Steam'i tamamen istisnalara ekleyip deneyeceğim.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
C sürücüsü içerisindeki program dosyalarında olması lazım. Netten ararsanız dosyaların doğru yerlerini bulursunuz. Steamden ziyade onun dosyaları önemli.
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
bysuvari dedi:
C sürücüsü içerisindeki program dosyalarında olması lazım. Netten ararsanız dosyaların doğru yerlerini bulursunuz. Steamden ziyade onun dosyaları önemli.
Genişletmek için tıkla...

Benim oyunlarım harici diskimde yüklü ve sanıyorum battleye dosyaları da oyunların kurulu olduğu yerdelermiş. Windows Security den steam klasörlerini ve BEDaisy.sys ile win27k.sys işlemlerini istisnalara ekledim. Windows güvenlik duvarından da PUBG, Black Squad ve Rainbow 6 Siege oyun klasörlerinde bulunan her Battleye exe dosyasını ve oyunların klasörlerindeki her exe dosyasını istisnalara ekledim. Yeniden başlattıktan sonra PUBG ye girmeyi denediğimde mavi ekran verdi tekrar ancak bu sefer KERNEL_SECURITY_CHECK_FAILURE hata kodu ile verdi. İşe yarar mı bilmiyorum ama ben gene de dumb file dosyasını göndereyim. Ayrıca joystick in kablosunu da çıkartmıştım.
 
Artı 0 Eksi
FahdLeR dedi:
Benim oyunlarım harici diskimde yüklü ve sanıyorum battleye dosyaları da oyunların kurulu olduğu yerdelermiş. Windows Security den steam klasörlerini ve BEDaisy.sys ile win27k.sys işlemlerini istisnalara ekledim. Windows güvenlik duvarından da PUBG, Black Squad ve Rainbow 6 Siege oyun klasörlerinde bulunan her Battleye exe dosyasını ve oyunların klasörlerindeki her exe dosyasını istisnalara ekledim. Yeniden başlattıktan sonra PUBG ye girmeyi denediğimde mavi ekran verdi tekrar ancak bu sefer KERNEL_SECURITY_CHECK_FAILURE hata kodu ile verdi. İşe yarar mı bilmiyorum ama ben gene de dumb file dosyasını göndereyim. Ayrıca joystick in kablosunu da çıkartmıştım.
Genişletmek için tıkla...
Ben onların Common Files klasöründe kurulu olduğunu biliyorum. O klasörü kontrol edebilir misin? Sonuçta oyun dosyalarını yüklediğin HDD'ye kurulmuyor güvenlik yazılımları. İşletim sisteminin bulunduğu HDD'ye kuruluyor. Yazılımını kaldırır mısın joystickin?
 
Artı 0 Eksi
Common files klasöründeki BattlEye ile ilgili dosyaları da ekledim istisnalara ancak gene de bir fark olmadı PUBG ye girerken mavi ekran verdi. Ayrıca joystickin yazılımı yok.
 
Son düzenleme:
Artı 0 Eksi
Yolladığınız 2 Minidump dosyasında da Battleye hatası mevcut silip tekrar kurmayı dener misiniz?
Yada Windows Defender Gerçek Zamanlı korumayı devre dışı bırakmayı deneyin.
Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for BEDaisy.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  X550JK

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  X550JK.304

BIOS_DATE:  04/16/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X550JK

BASEBOARD_VERSION:  1.0       

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80606973358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: aea

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  11-05-2019 17:50:46.0944

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806065eeb2b to fffff806065c1410

STACK_TEXT: 
ffff8601`99ebab08 fffff806`065eeb2b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`06973358 : nt!KeBugCheckEx
ffff8601`99ebab10 fffff806`0641f897 : 00000206`62465737 ffff8601`99e9b180 00000000`00000286 ffffb38a`864bc460 : nt!KeAccumulateTicks+0x1cc0cb
ffff8601`99ebab70 fffff806`063601e1 : 00000000`00000000 ffffbe01`dcec0400 ffffb38a`864bc4e0 ffffbe01`dcec04b0 : nt!KeClockInterruptNotify+0xc07
ffff8601`99ebaf30 fffff806`06402a25 : ffffbe01`dcec0400 00000000`00000000 00000000`00000000 ffff697a`4abeade6 : hal!HalpTimerClockIpiRoutine+0x21
ffff8601`99ebaf60 fffff806`065c2eaa : ffffb38a`864bc4e0 ffffbe01`dcec0400 ffffbe01`e031c7b0 ffffbe01`dcec0400 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8601`99ebafb0 fffff806`065c3417 : ffffbe01`de990360 ffffb38a`864bc4e0 ffffbe01`dcec0400 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb38a`864bc460 fffff806`06467dd1 : ffffb38a`864bc6f8 fffff806`0644c65e 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb38a`864bc5f0 fffff806`06448af8 : 00000000`00000000 ffffb38a`864bc6c1 ffff8601`99e9b180 00000000`00000000 : nt!KiAcquireKobjectLockSafe+0x31
ffffb38a`864bc620 fffff806`064a597d : ffffbe01`de990360 00000000`00000200 ffff8601`99e9b101 fffff806`0676f06d : nt!KiExitDispatcher+0x148
ffffb38a`864bc680 fffff806`082d7fd7 : 00000000`00000100 ffffbe01`eb76e068 00000000`00000057 ffffbe01`00000002 : nt!KeInsertQueueApc+0x14d
ffffb38a`864bc720 00000000`00000100 : ffffbe01`eb76e068 00000000`00000057 ffffbe01`00000002 00000000`00000000 : BEDaisy+0x2a7fd7
ffffb38a`864bc728 ffffbe01`eb76e068 : 00000000`00000057 ffffbe01`00000002 00000000`00000000 00000000`00000000 : 0x100
ffffb38a`864bc730 00000000`00000057 : ffffbe01`00000002 00000000`00000000 00000000`00000000 ffff8601`9a000100 : 0xffffbe01`eb76e068
ffffb38a`864bc738 ffffbe01`00000002 : 00000000`00000000 00000000`00000000 ffff8601`9a000100 00000000`00000000 : 0x57
ffffb38a`864bc740 00000000`00000000 : 00000000`00000000 ffff8601`9a000100 00000000`00000000 ffff8601`ffffff01 : 0xffffbe01`00000002


THREAD_SHA1_HASH_MOD_FUNC:  da54fe951f6d164d57faa36875cd631d57d5b4f4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0bde1bfad0baea3ccefe59099bafc10b14c79dab

THREAD_SHA1_HASH_MOD:  9a7298c6f0b6278bc5c7cf4f4e13435ac37b503f

FOLLOWUP_IP:
BEDaisy+2a7fd7
fffff806`082d7fd7 84c0            test    al,al

FAULT_INSTR_CODE:  e9c084

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  BEDaisy+2a7fd7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME:  BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c936027

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2a7fd7

FAILURE_BUCKET_ID:  0x133_ISR_BEDaisy!unknown_function

BUCKET_ID:  0x133_ISR_BEDaisy!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_BEDaisy!unknown_function

TARGET_TIME:  2019-11-04T21:02:26.000Z

OSBUILD:  18362

OSSERVICEPACK:  449

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:  2011-01-12 16:55:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  107b7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_bedaisy!unknown_function

FAILURE_ID_HASH:  {9c879213-f11f-75a6-c374-755b6bad7487}

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


*******************************************************************************
*                                                                             *
*                        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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff9803aa8bc3d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff9803aa8bc328, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  X550JK

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  X550JK.304

BIOS_DATE:  04/16/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X550JK

BASEBOARD_VERSION:  1.0       

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: ffff9803aa8bc3d0

BUGCHECK_P3: ffff9803aa8bc328

BUGCHECK_P4: 0

TRAP_FRAME:  ffff9803aa8bc3d0 -- (.trap 0xffff9803aa8bc3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc389e0990368 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80235648b10 rsp=ffff9803aa8bc560 rbp=ffffc389df7aa040
 r8=0000000000000001  r9=0000000000000002 r10=ffffc389deff1400
r11=ffffac8126a00180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!KiExitDispatcher+0x160:
fffff802`35648b10 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff9803aa8bc328 -- (.exr 0xffff9803aa8bc328)
ExceptionAddress: fffff80235648b10 (nt!KiExitDispatcher+0x0000000000000160)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 4

CPU_MHZ: aea

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x139

PROCESS_NAME:  System

CURRENT_IRQL:  2

DEFAULT_BUCKET_ID:  FAIL_FAST_CORRUPT_LIST_ENTRY

ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  11-05-2019 17:50:41.0982

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff802357d32e9 to fffff802357c1410

STACK_TEXT: 
ffff9803`aa8bc0a8 fffff802`357d32e9 : 00000000`00000139 00000000`00000003 ffff9803`aa8bc3d0 ffff9803`aa8bc328 : nt!KeBugCheckEx
ffff9803`aa8bc0b0 fffff802`357d3710 : 00000000`02000103 00000000`00000000 0199b8b0`0199b908 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9803`aa8bc1f0 fffff802`357d1aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9803`aa8bc540 : nt!KiFastFailDispatch+0xd0
ffff9803`aa8bc3d0 fffff802`35648b10 : 00000000`00000000 ffff9803`aa8bc601 ffffac81`26a00180 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x325
ffff9803`aa8bc560 fffff802`356a597d : ffffc389`e0990360 00000000`00000200 ffffac81`26a00101 fffff802`3596f06d : nt!KiExitDispatcher+0x160
ffff9803`aa8bc5c0 fffff802`4a9b07f8 : 00000000`00000100 ffffc389`ec3da068 00000000`00000001 00000000`00000002 : nt!KeInsertQueueApc+0x14d
ffff9803`aa8bc660 00000000`00000100 : ffffc389`ec3da068 00000000`00000001 00000000`00000002 00000000`00000000 : BEDaisy+0x2b07f8
ffff9803`aa8bc668 ffffc389`ec3da068 : 00000000`00000001 00000000`00000002 00000000`00000000 00000000`00000000 : 0x100
ffff9803`aa8bc670 00000000`00000001 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc389`ec3da068
ffff9803`aa8bc678 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffff9803`aa8bc680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`c0000001 : 0x2


THREAD_SHA1_HASH_MOD_FUNC:  b61d566806c3900e9d82f26f996154d545d8a932

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fca4a2c9edc5b93556e4b2fb148f6720c6f965b3

THREAD_SHA1_HASH_MOD:  0079172978a7673b45090780b1c9d2221d299a5f

FOLLOWUP_IP:
BEDaisy+2b07f8
fffff802`4a9b07f8 84c0            test    al,al

FAULT_INSTR_CODE:  e9c084

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  BEDaisy+2b07f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME:  BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d9f95a0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2b07f8

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

TARGET_TIME:  2019-11-04T20:48:40.000Z

OSBUILD:  18362

OSSERVICEPACK:  449

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:  2011-01-12 16:55:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  6b95

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_bedaisy!unknown_function

FAILURE_ID_HASH:  {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

Followup:     MachineOwner
---------
 
Artı 0 Eksi
MayCrasH dedi:
Yolladığınız 2 Minidump dosyasında da Battleye hatası mevcut silip tekrar kurmayı dener misiniz?
Yada Windows Defender Gerçek Zamanlı korumayı devre dışı bırakmayı deneyin.
Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

*** WARNING: Unable to verify timestamp for BEDaisy.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  X550JK

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0      

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  X550JK.304

BIOS_DATE:  04/16/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X550JK

BASEBOARD_VERSION:  1.0      

DUMP_TYPE:  2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80606973358

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 4

CPU_MHZ: aea

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  11-05-2019 17:50:46.0944

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff806065eeb2b to fffff806065c1410

STACK_TEXT:
ffff8601`99ebab08 fffff806`065eeb2b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`06973358 : nt!KeBugCheckEx
ffff8601`99ebab10 fffff806`0641f897 : 00000206`62465737 ffff8601`99e9b180 00000000`00000286 ffffb38a`864bc460 : nt!KeAccumulateTicks+0x1cc0cb
ffff8601`99ebab70 fffff806`063601e1 : 00000000`00000000 ffffbe01`dcec0400 ffffb38a`864bc4e0 ffffbe01`dcec04b0 : nt!KeClockInterruptNotify+0xc07
ffff8601`99ebaf30 fffff806`06402a25 : ffffbe01`dcec0400 00000000`00000000 00000000`00000000 ffff697a`4abeade6 : hal!HalpTimerClockIpiRoutine+0x21
ffff8601`99ebaf60 fffff806`065c2eaa : ffffb38a`864bc4e0 ffffbe01`dcec0400 ffffbe01`e031c7b0 ffffbe01`dcec0400 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8601`99ebafb0 fffff806`065c3417 : ffffbe01`de990360 ffffb38a`864bc4e0 ffffbe01`dcec0400 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb38a`864bc460 fffff806`06467dd1 : ffffb38a`864bc6f8 fffff806`0644c65e 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb38a`864bc5f0 fffff806`06448af8 : 00000000`00000000 ffffb38a`864bc6c1 ffff8601`99e9b180 00000000`00000000 : nt!KiAcquireKobjectLockSafe+0x31
ffffb38a`864bc620 fffff806`064a597d : ffffbe01`de990360 00000000`00000200 ffff8601`99e9b101 fffff806`0676f06d : nt!KiExitDispatcher+0x148
ffffb38a`864bc680 fffff806`082d7fd7 : 00000000`00000100 ffffbe01`eb76e068 00000000`00000057 ffffbe01`00000002 : nt!KeInsertQueueApc+0x14d
ffffb38a`864bc720 00000000`00000100 : ffffbe01`eb76e068 00000000`00000057 ffffbe01`00000002 00000000`00000000 : BEDaisy+0x2a7fd7
ffffb38a`864bc728 ffffbe01`eb76e068 : 00000000`00000057 ffffbe01`00000002 00000000`00000000 00000000`00000000 : 0x100
ffffb38a`864bc730 00000000`00000057 : ffffbe01`00000002 00000000`00000000 00000000`00000000 ffff8601`9a000100 : 0xffffbe01`eb76e068
ffffb38a`864bc738 ffffbe01`00000002 : 00000000`00000000 00000000`00000000 ffff8601`9a000100 00000000`00000000 : 0x57
ffffb38a`864bc740 00000000`00000000 : 00000000`00000000 ffff8601`9a000100 00000000`00000000 ffff8601`ffffff01 : 0xffffbe01`00000002


THREAD_SHA1_HASH_MOD_FUNC:  da54fe951f6d164d57faa36875cd631d57d5b4f4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0bde1bfad0baea3ccefe59099bafc10b14c79dab

THREAD_SHA1_HASH_MOD:  9a7298c6f0b6278bc5c7cf4f4e13435ac37b503f

FOLLOWUP_IP:
BEDaisy+2a7fd7
fffff806`082d7fd7 84c0            test    al,al

FAULT_INSTR_CODE:  e9c084

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  BEDaisy+2a7fd7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME:  BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c936027

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2a7fd7

FAILURE_BUCKET_ID:  0x133_ISR_BEDaisy!unknown_function

BUCKET_ID:  0x133_ISR_BEDaisy!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_ISR_BEDaisy!unknown_function

TARGET_TIME:  2019-11-04T21:02:26.000Z

OSBUILD:  18362

OSSERVICEPACK:  449

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:  2011-01-12 16:55:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  107b7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_isr_bedaisy!unknown_function

FAILURE_ID_HASH:  {9c879213-f11f-75a6-c374-755b6bad7487}

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


*******************************************************************************
*                                                                             *
*                        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: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff9803aa8bc3d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff9803aa8bc328, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  X550JK

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0      

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  X550JK.304

BIOS_DATE:  04/16/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  X550JK

BASEBOARD_VERSION:  1.0      

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: ffff9803aa8bc3d0

BUGCHECK_P3: ffff9803aa8bc328

BUGCHECK_P4: 0

TRAP_FRAME:  ffff9803aa8bc3d0 -- (.trap 0xffff9803aa8bc3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc389e0990368 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80235648b10 rsp=ffff9803aa8bc560 rbp=ffffc389df7aa040
r8=0000000000000001  r9=0000000000000002 r10=ffffc389deff1400
r11=ffffac8126a00180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!KiExitDispatcher+0x160:
fffff802`35648b10 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff9803aa8bc328 -- (.exr 0xffff9803aa8bc328)
ExceptionAddress: fffff80235648b10 (nt!KiExitDispatcher+0x0000000000000160)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 4

CPU_MHZ: aea

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x139

PROCESS_NAME:  System

CURRENT_IRQL:  2

DEFAULT_BUCKET_ID:  FAIL_FAST_CORRUPT_LIST_ENTRY

ERROR_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - <Unable to get error code text>

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_SESSION_HOST:  DESKTOP-18V31A3

ANALYSIS_SESSION_TIME:  11-05-2019 17:50:41.0982

ANALYSIS_VERSION: 10.0.18362.1 x86fre

LAST_CONTROL_TRANSFER:  from fffff802357d32e9 to fffff802357c1410

STACK_TEXT:
ffff9803`aa8bc0a8 fffff802`357d32e9 : 00000000`00000139 00000000`00000003 ffff9803`aa8bc3d0 ffff9803`aa8bc328 : nt!KeBugCheckEx
ffff9803`aa8bc0b0 fffff802`357d3710 : 00000000`02000103 00000000`00000000 0199b8b0`0199b908 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff9803`aa8bc1f0 fffff802`357d1aa5 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9803`aa8bc540 : nt!KiFastFailDispatch+0xd0
ffff9803`aa8bc3d0 fffff802`35648b10 : 00000000`00000000 ffff9803`aa8bc601 ffffac81`26a00180 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x325
ffff9803`aa8bc560 fffff802`356a597d : ffffc389`e0990360 00000000`00000200 ffffac81`26a00101 fffff802`3596f06d : nt!KiExitDispatcher+0x160
ffff9803`aa8bc5c0 fffff802`4a9b07f8 : 00000000`00000100 ffffc389`ec3da068 00000000`00000001 00000000`00000002 : nt!KeInsertQueueApc+0x14d
ffff9803`aa8bc660 00000000`00000100 : ffffc389`ec3da068 00000000`00000001 00000000`00000002 00000000`00000000 : BEDaisy+0x2b07f8
ffff9803`aa8bc668 ffffc389`ec3da068 : 00000000`00000001 00000000`00000002 00000000`00000000 00000000`00000000 : 0x100
ffff9803`aa8bc670 00000000`00000001 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffc389`ec3da068
ffff9803`aa8bc678 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
ffff9803`aa8bc680 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`c0000001 : 0x2


THREAD_SHA1_HASH_MOD_FUNC:  b61d566806c3900e9d82f26f996154d545d8a932

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fca4a2c9edc5b93556e4b2fb148f6720c6f965b3

THREAD_SHA1_HASH_MOD:  0079172978a7673b45090780b1c9d2221d299a5f

FOLLOWUP_IP:
BEDaisy+2b07f8
fffff802`4a9b07f8 84c0            test    al,al

FAULT_INSTR_CODE:  e9c084

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  BEDaisy+2b07f8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BEDaisy

IMAGE_NAME:  BEDaisy.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5d9f95a0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2b07f8

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_BEDaisy!unknown_function

TARGET_TIME:  2019-11-04T20:48:40.000Z

OSBUILD:  18362

OSSERVICEPACK:  449

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:  2011-01-12 16:55:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  6b95

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_bedaisy!unknown_function

FAILURE_ID_HASH:  {59d8eb10-b2e4-7df6-f6a5-49968226dbb8}

Followup:     MachineOwner
---------
Genişletmek için tıkla...
Battleye i denetim masasında silme olmadığından bende common files ve oyun klasörlerinin içindeki dosyaları sildim. Bilgisayarı yeniden başlattım ve gerçek zamanlı korumayı kapattım. Black squad oyununun boyutu düşük olması nedeniyle steamden dosya bütünlüğü doğrulaması yaparak battleye dosyalarını tekrar yüklettim ve oyuna girmeye çalıştım ancak sonuç değişmedi. Dumb file
 
Artı 0 Eksi
Uyarı! Bu konu 6 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.

Benzer konular

mburaktekin
  • Soru
BattlEye Mavi ekran hatası
Mesaj
1
Görüntüleme
650
342524
3
E
  • Soru
BattlEye oyunlarında mavi ekran
Mesaj
1
Görüntüleme
397
The G.O.A.T
The G.O.A.T
BRHN59
  • Soru
BattlEye oyunlarında mavi ekran hatası
Mesaj
3
Görüntüleme
320
BRHN59
BRHN59
LADES312
  • Soru
BattlEye yüzünden mavi ekran hatası
Mesaj
4
Görüntüleme
523
LADES312
LADES312
U
  • Soru
BattlEye kullanan oyunlarda mavi ekran
Mesaj
9
Görüntüleme
2.929
Murat5038
Murat5038

Technopat Haberler

Yeni konular

Yeni mesajlar

Geri
Yukarı