Çözüldü Windows 10 mavi ekran hatasi

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Torabi

Decapat
Katılım
28 Mart 2021
Mesajlar
5
Daha fazla  
Cinsiyet
Erkek
Selam.
PC'yi güvenli modda açmaya çalışırken her seferinde mavi ekran hatası veriyor. PC'yi normal kullanırken ya da oyun oynarken sıkıntı yok sadece güvenli mod girmeye çalıştığımda ariza yapıyor.
 
Çözüm
1) ESEA Client kaldırın.
2) FACEIT kaldırın.
3) Malwarebytes'ı kaldırın. Sorun çözüldükten sonra isterseniz tekrar yükleyebilirsiniz.

Sorun çözülürse bildirmeyi unutmayın. :)

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff803e9b63507, The address that the exception occurred at
Arg3: ffff9284b0c07558, Exception Record Address
Arg4: ffff9284b0c06d90, Context Record Address

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4999

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30509

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

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

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff803e9b63507

BUGCHECK_P3: ffff9284b0c07558

BUGCHECK_P4: ffff9284b0c06d90

EXCEPTION_RECORD: ffff9284b0c07558 -- (.exr 0xffff9284b0c07558)
ExceptionAddress: fffff803e9b63507 (ESEADriver2+0x0000000000003507)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

CONTEXT: ffff9284b0c06d90 -- (.cxr 0xffff9284b0c06d90)
rax=fffff80743e4c19c rbx=ffffac82fedcb000 rcx=ffffac82fedbeda0
rdx=ffffac82fedcb000 rsi=ffffac82fe4796d0 rdi=ffffac82fedbeda0
rip=fffff803e9b63507 rsp=ffff9284b0c07790 rbp=ffff9284b0c077f0
r8=ffff9284b0c06ef0 r9=0000000000000020 r10=0000000000000000
r11=0000000000000000 r12=ffffcc8e5589f0e0 r13=ffffffff80000108
r14=0000000000000000 r15=ffffac82fedcb000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040202
ESEADriver2+0x3507:
fffff803`e9b63507 cc int 3
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM} Kesme Noktas Bir kesme noktas na ula ld .

EXCEPTION_CODE_STR: 80000003

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_STR: 0x80000003

STACK_TEXT:
ffff9284`b0c07790 00000000`00000000 : 00000000`001a54f1 ffff9284`d38c618c 00000000`00000000 fffff803`e9dd2377 : ESEADriver2+0x3507


SYMBOL_NAME: ESEADriver2+3507

MODULE_NAME: ESEADriver2

IMAGE_NAME: ESEADriver2.sys

STACK_COMMAND: .cxr 0xffff9284b0c06d90 ; kb

BUCKET_ID_FUNC_OFFSET: 3507

FAILURE_BUCKET_ID: AV_ESEADriver2!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0517b42b-e84c-cddf-1c70-a246a0c42e80}

Followup: MachineOwner
---------[/CODE]
Minidump paylaşır mısınız?

 
1) ESEA Client kaldırın.
2) FACEIT kaldırın.
3) Malwarebytes'ı kaldırın. Sorun çözüldükten sonra isterseniz tekrar yükleyebilirsiniz.

Sorun çözülürse bildirmeyi unutmayın. :)

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff803e9b63507, The address that the exception occurred at
Arg3: ffff9284b0c07558, Exception Record Address
Arg4: ffff9284b0c06d90, Context Record Address

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4999

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30509

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

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

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff803e9b63507

BUGCHECK_P3: ffff9284b0c07558

BUGCHECK_P4: ffff9284b0c06d90

EXCEPTION_RECORD: ffff9284b0c07558 -- (.exr 0xffff9284b0c07558)
ExceptionAddress: fffff803e9b63507 (ESEADriver2+0x0000000000003507)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 1
Parameter[0]: 0000000000000000

CONTEXT: ffff9284b0c06d90 -- (.cxr 0xffff9284b0c06d90)
rax=fffff80743e4c19c rbx=ffffac82fedcb000 rcx=ffffac82fedbeda0
rdx=ffffac82fedcb000 rsi=ffffac82fe4796d0 rdi=ffffac82fedbeda0
rip=fffff803e9b63507 rsp=ffff9284b0c07790 rbp=ffff9284b0c077f0
r8=ffff9284b0c06ef0 r9=0000000000000020 r10=0000000000000000
r11=0000000000000000 r12=ffffcc8e5589f0e0 r13=ffffffff80000108
r14=0000000000000000 r15=ffffac82fedcb000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040202
ESEADriver2+0x3507:
fffff803`e9b63507 cc int 3
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0x80000003 - { ZEL DURUM} Kesme Noktas Bir kesme noktas na ula ld .

EXCEPTION_CODE_STR: 80000003

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_STR: 0x80000003

STACK_TEXT:
ffff9284`b0c07790 00000000`00000000 : 00000000`001a54f1 ffff9284`d38c618c 00000000`00000000 fffff803`e9dd2377 : ESEADriver2+0x3507


SYMBOL_NAME: ESEADriver2+3507

MODULE_NAME: ESEADriver2

IMAGE_NAME: ESEADriver2.sys

STACK_COMMAND: .cxr 0xffff9284b0c06d90 ; kb

BUCKET_ID_FUNC_OFFSET: 3507

FAILURE_BUCKET_ID: AV_ESEADriver2!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0517b42b-e84c-cddf-1c70-a246a0c42e80}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Hayır yapmayacak. Yani yapmaması gerekiyor. ESEA Client'i ilk defa duydum fakat oyununuz için gerekli sanırsam. Onu kaldırıp tekrar kurun ve sorun çözülürse çözüm içerikli mesajı çözüm olarak seçin.
 
ESEA'yı ve Malwarebayt'ı sildim sonra güvenli moda girdim. Mavi ekran yapmadan girdi. sonra ESEA'yı tekrar kurdum ve güvenli moda mavi ekran yapmadan girdi. Malwarebayt olmasada olur yani sorunum çözülmüş oldu. Teşekkürler.
 

Geri
Yukarı