Windows 10 "SYSTEM THREAD EXCEPTION NOT HANDLED" Mavi Ekran Hatası

  • Konuyu başlatan ynhl
  • Başlangıç Tarihi
  • Mesaj 5
  • Görüntüleme 2.992

ynhl

Hectopat
Katılım
17 Eylül 2019
Mesajlar
71
Daha fazla  
Cinsiyet
Erkek
Bu hatayı alıyorum neden olabilir?

Yeni HDD aldım onu taktıktan sonra olmaya başladı.

Minidump dosyaları.




Kod:
Crash dump directories:
C:\Windows.
C:\Windows\Minidump.

On Sat 26.10.2019 14:45:51 your computer crashed or a problem was reported.
crash dump file: C:\Windows\Minidump\102619-9421-01.dmp.
This was probably caused by the following module: bindflt.sys (bindflt+0x604C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8033A2050B0, 0xFFFF870F82999FA8, 0xFFFF870F829997F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.
file path: C:\Windows\system32\drivers\bindflt.sys.
product: Microsoft® Windows® Operating System.
company: Microsoft Corporation.
description: Windows Bind Filter Driver.
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 26.10.2019 14:45:51 your computer crashed or a problem was reported.
crash dump file: C:\Windows\MEMORY.DMP.
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1CFC)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8033A2050B0, 0xFFFF870F82999FA8, 0xFFFF870F829997F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
file path: C:\Windows\system32\drivers\fltmgr.sys.
product: Microsoft® Windows® İşletim Sistemi.
company: Microsoft Corporation.
description: Microsoft Dosya Sistemi Filtre Yöneticisi.
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 26.10.2019 14:32:37 your computer crashed or a problem was reported.
crash dump file: C:\Windows\Minidump\102619-8437-01.dmp.
This was probably caused by the following module: bindflt.sys (bindflt+0x604C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF804700050B0, 0xFFFFA689A14E8FA8, 0xFFFFA689A14E87F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.
file path: C:\Windows\system32\drivers\bindflt.sys.
product: Microsoft® Windows® Operating System.
company: Microsoft Corporation.
description: Windows Bind Filter Driver.
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 26.10.2019 14:30:43 your computer crashed or a problem was reported.
crash dump file: C:\Windows\Minidump\102619-10312-01.dmp.
This was probably caused by the following module: bindflt.sys (bindflt+0x604C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF807734050B0, 0xFFFF9288DCE61FA8, 0xFFFF9288DCE617F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.
file path: C:\Windows\system32\drivers\bindflt.sys.
product: Microsoft® Windows® Operating System.
company: Microsoft Corporation.
description: Windows Bind Filter Driver.
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 26.10.2019 14:28:41 your computer crashed or a problem was reported.
crash dump file: C:\Windows\Minidump\102619-8531-01.dmp.
This was probably caused by the following module: bindflt.sys (bindflt+0x604C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF804116050B0, 0xFFFF8209154C9FA8, 0xFFFF8209154C97F0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M.
file path: C:\Windows\system32\drivers\bindflt.sys.
product: Microsoft® Windows® Operating System.
company: Microsoft Corporation.
description: Windows Bind Filter Driver.
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Son düzenleyen: Moderatör:
Malwarebytes modülü hataya neden olmuş gibi. Malwarebytes'ı kaldırın. Bir de Windows'u güncelleyin, 1909'a geçin.
Kod:
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804116050b0, The address that the exception occurred at
Arg3: ffff8209154c9fa8, Exception Record Address
Arg4: ffff8209154c97f0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 9

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 22

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff804116050b0

BUGCHECK_P3: ffff8209154c9fa8

BUGCHECK_P4: ffff8209154c97f0

EXCEPTION_RECORD:  ffff8209154c9fa8 -- (.exr 0xffff8209154c9fa8)
ExceptionAddress: fffff804116050b0 (nt!IoThreadToProcess)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000220
Attempt to read from address 0000000000000220

CONTEXT:  ffff8209154c97f0 -- (.cxr 0xffff8209154c97f0)
rax=0000000000000000 rbx=ffff8209154ca318 rcx=0000000000000000
rdx=ffff8209154ca338 rsi=ffff980273dd1010 rdi=ffff98027c0462a0
rip=fffff804116050b0 rsp=ffff8209154ca1e8 rbp=ffff8209154ca270
r8=ffff8209154ca318  r9=000000000000003e r10=0000fffff8041ffc
r11=ffff74ff3da00000 r12=0000000010000004 r13=ffff98027c046010
r14=ffff8209154ca338 r15=ffff980273dd10f8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!IoThreadToProcess:
fffff804`116050b0 488b8120020000  mov     rax,qword ptr [rcx+220h] ds:002b:00000000`00000220=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff80411b733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80411a2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff80411a2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000220

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000220

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffff8209`154ca1e8 fffff804`1ffc4841 : ffff9802`78a0fa20 ffff8209`154ca288 ffff8209`154ca288 ffff9802`7cae6058 : nt!IoThreadToProcess
ffff8209`154ca1f0 ffff9802`78a0fa20 : ffff8209`154ca288 ffff8209`154ca288 ffff9802`7cae6058 ffff8209`154ca318 : farflt+0x4841
ffff8209`154ca1f8 ffff8209`154ca288 : ffff8209`154ca288 ffff9802`7cae6058 ffff8209`154ca318 fffff804`2159604c : 0xffff9802`78a0fa20
ffff8209`154ca200 ffff8209`154ca288 : ffff9802`7cae6058 ffff8209`154ca318 fffff804`2159604c ffff9802`78a0fa20 : 0xffff8209`154ca288
ffff8209`154ca208 ffff9802`7cae6058 : ffff8209`154ca318 fffff804`2159604c ffff9802`78a0fa20 ffff9802`73dd10f8 : 0xffff8209`154ca288
ffff8209`154ca210 ffff8209`154ca318 : fffff804`2159604c ffff9802`78a0fa20 ffff9802`73dd10f8 ffff8209`154ca2b0 : 0xffff9802`7cae6058
ffff8209`154ca218 fffff804`2159604c : ffff9802`78a0fa20 ffff9802`73dd10f8 ffff8209`154ca2b0 ffff9802`7c1494b0 : 0xffff8209`154ca318
ffff8209`154ca220 00000000`00000000 : ffff9802`7c046010 00000000`10000004 ffff9802`73dd1010 ffff9802`73dd1198 : bindflt!BfCheckAndSwitchTarget+0x44


SYMBOL_NAME:  farflt+4841

MODULE_NAME: farflt

IMAGE_NAME:  farflt.sys

STACK_COMMAND:  .cxr 0xffff8209154c97f0 ; kb

BUCKET_ID_FUNC_OFFSET:  4841

FAILURE_BUCKET_ID:  AV_farflt!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {840e8ea7-730a-df84-3539-24936294114f}

Followup:     MachineOwner
---------
 
Malwarebytes modülü hataya neden olmuş gibi. Malwarebytes'ı kaldırın. Bir de Windows'u güncelleyin, 1909'a geçin.
Kod:
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff804116050b0, The address that the exception occurred at
Arg3: ffff8209154c9fa8, Exception Record Address
Arg4: ffff8209154c97f0, Context Record Address

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

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

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 9

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 22

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff804116050b0

BUGCHECK_P3: ffff8209154c9fa8

BUGCHECK_P4: ffff8209154c97f0

EXCEPTION_RECORD:  ffff8209154c9fa8 -- (.exr 0xffff8209154c9fa8)
ExceptionAddress: fffff804116050b0 (nt!IoThreadToProcess)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000220
Attempt to read from address 0000000000000220

CONTEXT:  ffff8209154c97f0 -- (.cxr 0xffff8209154c97f0)
rax=0000000000000000 rbx=ffff8209154ca318 rcx=0000000000000000
rdx=ffff8209154ca338 rsi=ffff980273dd1010 rdi=ffff98027c0462a0
rip=fffff804116050b0 rsp=ffff8209154ca1e8 rbp=ffff8209154ca270
r8=ffff8209154ca318  r9=000000000000003e r10=0000fffff8041ffc
r11=ffff74ff3da00000 r12=0000000010000004 r13=ffff98027c046010
r14=ffff8209154ca338 r15=ffff980273dd10f8
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!IoThreadToProcess:
fffff804`116050b0 488b8120020000  mov     rax,qword ptr [rcx+220h] ds:002b:00000000`00000220=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff80411b733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80411a2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff80411a2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000220

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000220

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffff8209`154ca1e8 fffff804`1ffc4841 : ffff9802`78a0fa20 ffff8209`154ca288 ffff8209`154ca288 ffff9802`7cae6058 : nt!IoThreadToProcess
ffff8209`154ca1f0 ffff9802`78a0fa20 : ffff8209`154ca288 ffff8209`154ca288 ffff9802`7cae6058 ffff8209`154ca318 : farflt+0x4841
ffff8209`154ca1f8 ffff8209`154ca288 : ffff8209`154ca288 ffff9802`7cae6058 ffff8209`154ca318 fffff804`2159604c : 0xffff9802`78a0fa20
ffff8209`154ca200 ffff8209`154ca288 : ffff9802`7cae6058 ffff8209`154ca318 fffff804`2159604c ffff9802`78a0fa20 : 0xffff8209`154ca288
ffff8209`154ca208 ffff9802`7cae6058 : ffff8209`154ca318 fffff804`2159604c ffff9802`78a0fa20 ffff9802`73dd10f8 : 0xffff8209`154ca288
ffff8209`154ca210 ffff8209`154ca318 : fffff804`2159604c ffff9802`78a0fa20 ffff9802`73dd10f8 ffff8209`154ca2b0 : 0xffff9802`7cae6058
ffff8209`154ca218 fffff804`2159604c : ffff9802`78a0fa20 ffff9802`73dd10f8 ffff8209`154ca2b0 ffff9802`7c1494b0 : 0xffff8209`154ca318
ffff8209`154ca220 00000000`00000000 : ffff9802`7c046010 00000000`10000004 ffff9802`73dd1010 ffff9802`73dd1198 : bindflt!BfCheckAndSwitchTarget+0x44


SYMBOL_NAME:  farflt+4841

MODULE_NAME: farflt

IMAGE_NAME:  farflt.sys

STACK_COMMAND:  .cxr 0xffff8209154c97f0 ; kb

BUCKET_ID_FUNC_OFFSET:  4841

FAILURE_BUCKET_ID:  AV_farflt!unknown_function

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {840e8ea7-730a-df84-3539-24936294114f}

Followup:     MachineOwner
---------
Ben de mavi ekran alıyorum ve benim de Windows'um 1903. 1909'a nasıl geçerim?
 

Veya:

 
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.

Technopat Haberler

Geri
Yukarı