Çözüldü Windows 10 Mavi Ekran "kernel security check failure"

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

Şahin Özer

Femtopat
Katılım
30 Ekim 2020
Mesajlar
7
Daha fazla  
Cinsiyet
Erkek
Son 2 haftadır mavi ekran hatası alıyorum. Birinci hata: "kmode exception not handled" ikinci hata ise "kernel security check failure" bilgisayarı kullanırken bir anda küçük donmalar yaşıyorum, ardından mavi ekran geliyor ve bu hataları alıyorum. Format attım, tüm sürücülerimi güncelleştirdim.

Minidump dosyaları : minidump.rar

MemTest86 Sonuçum : memorytest.rar
 
Son düzenleyen: Moderatör:
Çözüm
Bora Dere
Kontrolcü için olan donanım kimliklerini kopyalayıp buraya yapıştırınız. Resimden yazamam. Ayrıca anakartın sitesinden ağ sürücülerinizi güncellediniz mi? Yeni dosyayı da paylaşın ve ekran kartınızın sürücüsünü DDU ile kaldırıp güncelleyin.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
Tarihe göre sırala Puana göre sırala
Ek MSI yazılımlarını kaldırın. Ağ sürücülerinizi güncelleyin. Bluetooth ve Wi-Fi adaptörü kullanıyorsanız donanım kimliklerini paylaşın.

MSI Global - The Leading Brand in High-end Gaming & Professional Creation

As a world leading gaming brand, MSI is the most trusted name in gaming and eSports. We stand by our principles of breakthroughs in design, and roll out the amazing gaming gear like motherboards, graphics cards, laptops and desktops.
www.msi.com www.msi.com

Donanım KimliÄi ile Sürücüleri Bulma

Aygıtların donanım kimliÄi ile aradıÄınız sürücüyü çok daha kısa sürede bulabilirsiniz. Dünya üzerindeki neredeyse her bilgisayar parçasının bir Vendor (Ãretici) ve bir de Device (Aygıt) ID'si yani kimliÄi vardır. VEN yani Vendor üreticinin kodudur.
www.technopat.net www.technopat.net

Sisteme kablosuz bir klavye bağlıyorsanız çıkarın. Windows altından hızlı başlatma ayarı açıksa kapatın. Afterburner ile ekran kartına bir işlem yaptıysanız onu da sıfırlayın.

Kod: 
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800167fc4d7, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4530

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11554

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800167fc4d7

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff800170fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8001700f340: Unable to get Flags value from nt!KdVersionBlock
fffff8001700f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  audiodg.exe

BAD_STACK_POINTER:  fffff8001b280158

STACK_TEXT:
fffff800`1b280158 fffff800`168f465e     : 00000000`0000001e ffffffff`c0000005 fffff800`167fc4d7 00000000`00000000 : nt!KeBugCheckEx
fffff800`1b280160 fffff800`167fd462     : fffff800`168f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff800`1b2801a0 fffff800`16652d97     : fffff800`1b280710 00000000`00000000 fffff800`1b272fb0 fffff800`167fb5e5 : nt!RtlpExecuteHandlerForException+0x12
fffff800`1b2801d0 fffff800`166519a6     : fffff800`1b272148 fffff800`1b280e20 fffff800`1b272148 ffffcd08`ec496600 : nt!RtlDispatchException+0x297
fffff800`1b2808f0 fffff800`167f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff800`1b280fb0 fffff800`167f5400     : fffff800`168066a5 fffff800`17125440 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff800`1b272008 fffff800`168066a5     : fffff800`17125440 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff800`1b272010 fffff800`168023e0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff800`1b2721f0 fffff800`167fc4d7     : 00000000`00000000 fffff800`6432472f ffffcd08`ed6721d0 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff800`1b272380 fffff800`6432472f     : ffffcd08`ed6721d0 00000000`00000000 ffffcd08`f08fb5f0 fffff800`276fc701 : nt!ExpInterlockedPopEntrySListFault
fffff800`1b272390 fffff800`1a4c8c5e     : 00000000`00000000 fffff800`1b2724a9 00000000`00000001 fffff800`1b2725a8 : Ndu!NduInboundMacClassify+0x1ff
fffff800`1b272440 fffff800`1a5c14d5     : 00000000`00000000 00000000`00000000 ffffcd08`ec60b030 00000000`00000050 : NETIO!KfdClassify2+0x19e
fffff800`1b272510 fffff800`1a5c1270     : ffffcd08`eca99bf0 00000000`4e414859 00000000`00000100 00000000`0000076e : wfplwfs!L2InspectNetBufferListsFast+0x165
fffff800`1b272620 fffff800`1a347ef0     : ffffa281`00000002 ffffcd08`ec60b030 00000000`00000000 ffffcd08`e71d7001 : wfplwfs!LwfLowerRecvNetBufferLists+0xd0
fffff800`1b2726e0 fffff800`1a37de2c     : ffffcd08`ec25e040 fffff800`1b2727b1 fffff800`1b272778 fffff800`00000000 : ndis!ndisCallReceiveHandler+0x60
fffff800`1b272730 fffff800`1a344a94     : 00000000`000fa1e0 00000000`00000001 ffffcd08`e9cb51a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148
fffff800`1b272800 fffff800`24126ae8     : ffffcd08`ec2b9000 ffffcd08`ec2b9000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffff800`1b272890 ffffcd08`ec2b9000     : ffffcd08`ec2b9000 00000000`00000000 00000000`00000000 00000000`00000001 : rt640x64+0x26ae8
fffff800`1b272898 ffffcd08`ec2b9000     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : 0xffffcd08`ec2b9000
fffff800`1b2728a0 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : 0xffffcd08`ec2b9000


SYMBOL_NAME:  Ndu!NduInboundMacClassify+1ff

MODULE_NAME: Ndu

IMAGE_NAME:  Ndu.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1ff

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_Ndu!NduInboundMacClassify

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {523e0fc8-5ffd-58fd-a46c-d32152d95c8a}

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



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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8063affc4d7, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4624

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 7403

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8063affc4d7

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff8063b8fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8063b80f340: Unable to get Flags value from nt!KdVersionBlock
fffff8063b80f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  javaw.exe

BAD_STACK_POINTER:  fffff80641680158

STACK_TEXT:
fffff806`41680158 fffff806`3b0f465e     : 00000000`0000001e ffffffff`c0000005 fffff806`3affc4d7 00000000`00000000 : nt!KeBugCheckEx
fffff806`41680160 fffff806`3affd462     : fffff806`3b0f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`416801a0 fffff806`3ae52d97     : fffff806`41680710 00000000`00000000 fffff806`41672fb0 fffff806`3affb5e5 : nt!RtlpExecuteHandlerForException+0x12
fffff806`416801d0 fffff806`3ae519a6     : fffff806`41672148 fffff806`41680e20 fffff806`41672148 ffffbc05`5e7e5d80 : nt!RtlDispatchException+0x297
fffff806`416808f0 fffff806`3aff5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`41680fb0 fffff806`3aff5400     : fffff806`3b0066a5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`41672008 fffff806`3b0066a5     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`41672010 fffff806`3b0023e0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff806`416721f0 fffff806`3affc4d7     : 00000000`00000000 fffff806`3c59472f fffff806`41672330 fffff806`41672540 : nt!KiGeneralProtectionFault+0x320
fffff806`41672380 fffff806`3c59472f     : fffff806`41672330 fffff806`41672540 ffffbc05`5e6f81d0 00000000`00000008 : nt!ExpInterlockedPopEntrySListFault
fffff806`41672390 fffff806`40ba8c5e     : 00000000`00000000 fffff806`416724a9 fffff806`00000001 fffff806`416725a8 : Ndu!NduInboundMacClassify+0x1ff
fffff806`41672440 fffff806`410114d5     : 00000000`00000000 ffffbc05`688d4010 ffffbc05`59fbf9f0 00000000`00000050 : NETIO!KfdClassify2+0x19e
fffff806`41672510 fffff806`41011270     : ffffbc05`5a4e1810 ffffbc05`5c8886b0 00000000`00000000 ffffbc05`5c8886d0 : wfplwfs!L2InspectNetBufferListsFast+0x165
fffff806`41672620 fffff806`40a27ef0     : ffffbc05`00000001 ffffbc05`59fbf9f0 00000000`00989680 fffff806`41672601 : wfplwfs!LwfLowerRecvNetBufferLists+0xd0
fffff806`416726e0 fffff806`40a5de2c     : ffffbc05`59393040 fffff806`416727b1 fffff806`41672778 ffffbc05`5c8886c0 : ndis!ndisCallReceiveHandler+0x60
fffff806`41672730 fffff806`40a24a94     : 00000000`00faabd3 00000000`00000001 ffffbc05`5947a1a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148
fffff806`41672800 fffff806`4ae06ae8     : ffffbc05`59e03000 ffffbc05`59e03000 00000000`00000000 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffff806`41672890 ffffbc05`59e03000     : ffffbc05`59e03000 00000000`00000000 00000000`00000000 fffff806`00000001 : rt640x64+0x26ae8
fffff806`41672898 ffffbc05`59e03000     : 00000000`00000000 00000000`00000000 fffff806`00000001 0001f306`90161840 : 0xffffbc05`59e03000
fffff806`416728a0 00000000`00000000     : 00000000`00000000 fffff806`00000001 0001f306`90161840 00000000`5c3f0001 : 0xffffbc05`59e03000


SYMBOL_NAME:  Ndu!NduInboundMacClassify+1ff

MODULE_NAME: Ndu

IMAGE_NAME:  Ndu.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1ff

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_Ndu!NduInboundMacClassify

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {523e0fc8-5ffd-58fd-a46c-d32152d95c8a}

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



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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8073c9fc4d7, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4014

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16200

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8073c9fc4d7

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff8073d2fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8073d20f340: Unable to get Flags value from nt!KdVersionBlock
fffff8073d20f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

BAD_STACK_POINTER:  fffff80740e80158

STACK_TEXT:
fffff807`40e80158 fffff807`3caf465e     : 00000000`0000001e ffffffff`c0000005 fffff807`3c9fc4d7 00000000`00000000 : nt!KeBugCheckEx
fffff807`40e80160 fffff807`3c9fd462     : fffff807`3caf463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff807`40e801a0 fffff807`3c852d97     : fffff807`40e80710 00000000`00000000 fffff807`40e6bc60 fffff807`3c9f810e : nt!RtlpExecuteHandlerForException+0x12
fffff807`40e801d0 fffff807`3c8519a6     : fffff807`40e6adb8 fffff807`40e80e20 fffff807`40e6adb8 ffffce8f`9058d340 : nt!RtlDispatchException+0x297
fffff807`40e808f0 fffff807`3c9f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff807`40e80fb0 fffff807`3c9f5400     : fffff807`3ca066a5 fffff807`3c8755c0 fffff807`40e6ad6c fffff77b`bdd72001 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff807`40e6ac78 fffff807`3ca066a5     : fffff807`3c8755c0 fffff807`40e6ad6c fffff77b`bdd72001 fffff77b`bddeeb90 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff807`40e6ac80 fffff807`3ca023e0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff807`40e6ae60 fffff807`3c9fc4d7     : ffffce8f`9058d280 fffff807`4c0e6d7c 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff807`40e6aff0 fffff807`4c0e6d7c     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
fffff807`40e6b000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ndu!PplGenericAllocateFunction+0x1c


SYMBOL_NAME:  Ndu!PplGenericAllocateFunction+1c

MODULE_NAME: Ndu

IMAGE_NAME:  Ndu.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1c

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_Ndu!PplGenericAllocateFunction

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {420a9a8f-b98c-79e3-5534-69180eef1429}

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



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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8041e7fc4d7, The address that the exception occurred at
Arg3: ffff960ed2cf2e68, Parameter 0 of the exception
Arg4: ffffe3814653f920, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7875

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11585

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8041e7fc4d7

BUGCHECK_P3: ffff960ed2cf2e68

BUGCHECK_P4: ffffe3814653f920

WRITE_ADDRESS: fffff8041f0fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8041f00f340: Unable to get Flags value from nt!KdVersionBlock
fffff8041f00f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffe3814653f920

EXCEPTION_PARAMETER1:  ffff960ed2cf2e68

EXCEPTION_PARAMETER2:  ffffe3814653f920

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  8b48ffce83480000 -- (.trap 0x8b48ffce83480000)
Unable to read trap frame at 8b48ffce`83480000

BAD_STACK_POINTER:  ffffe3814653f0a8

STACK_TEXT:
ffffe381`4653f0a8 fffff804`1e90e6bf     : 00000000`0000001e ffffffff`c0000005 fffff804`1e7fc4d7 ffff960e`d2cf2e68 : nt!KeBugCheckEx
ffffe381`4653f0b0 fffff804`1e80d066     : ffffe381`4653f920 fffff804`1e68db25 ffff960e`d2cf30a0 fffff804`1e7fc4d7 : nt!KiFatalFilter+0x1f
ffffe381`4653f0f0 fffff804`1e7cb262     : fffff804`00000002 fffff804`1e4c9aa4 ffff960e`d2cef000 ffff960e`d2cf5000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffe381`4653f130 fffff804`1e7fd462     : fffff804`1e4c9aa4 ffffe381`4653f710 fffff804`1e7cb1c0 00000000`00000000 : nt!_C_specific_handler+0xa2
ffffe381`4653f1a0 fffff804`1e652d97     : ffffe381`4653f710 00000000`00000000 ffff960e`d2cf4220 fffff804`1e60d468 : nt!RtlpExecuteHandlerForException+0x12
ffffe381`4653f1d0 fffff804`1e6519a6     : ffff960e`d2cf2e68 ffffe381`4653fe20 ffff960e`d2cf2e68 ffff9902`32186950 : nt!RtlDispatchException+0x297
ffffe381`4653f8f0 fffff804`1e7f5432     : 000000d3`850f1042 00c9850f`081b42f6 8b48ffce`83480000 48087ac1`0f48f0fe : nt!KiDispatchException+0x186
ffffe381`4653ffb0 fffff804`1e7f5400     : fffff804`1e8066a5 00000000`00000000 00000000`00000000 ffff9902`22b9e278 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff960e`d2cf2d28 fffff804`1e8066a5     : 00000000`00000000 00000000`00000000 ffff9902`22b9e278 fffff804`20578db0 : nt!KiExceptionDispatchOnExceptionStackContinue
ffff960e`d2cf2d30 fffff804`1e8023e0     : 00000000`00000000 00000000`00000000 ffff0002`00000000 00001fff`00000021 : nt!KiExceptionDispatch+0x125
ffff960e`d2cf2f10 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


SYMBOL_NAME:  nt!KiFatalFilter+1f

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f

FAILURE_BUCKET_ID:  0x1E_c0000005_STACKPTR_ERROR_nt!KiFatalFilter

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0e643978-4781-6d9a-a33f-6c4c27edcac8}

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


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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8015b1fc4d7, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4952

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12049

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

    Key  : Analysis.System
    Value: CreateObject

    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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8015b1fc4d7

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS: fffff8015bafb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8015ba0f340: Unable to get Flags value from nt!KdVersionBlock
fffff8015ba0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

BAD_STACK_POINTER:  fffff8015ee80158

STACK_TEXT:
fffff801`5ee80158 fffff801`5b2f465e     : 00000000`0000001e ffffffff`c0000005 fffff801`5b1fc4d7 00000000`00000000 : nt!KeBugCheckEx
fffff801`5ee80160 fffff801`5b1fd462     : fffff801`5b2f463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff801`5ee801a0 fffff801`5b052d97     : fffff801`5ee80710 00000000`00000000 fffff801`5ee6bc60 fffff801`5b1f810e : nt!RtlpExecuteHandlerForException+0x12
fffff801`5ee801d0 fffff801`5b0519a6     : fffff801`5ee6adf8 fffff801`5ee80e20 fffff801`5ee6adf8 ffffcc04`a15abf00 : nt!RtlDispatchException+0x297
fffff801`5ee808f0 fffff801`5b1f5432     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff801`5ee80fb0 fffff801`5b1f5400     : fffff801`5b2066a5 fffff801`5ee6ad10 00000000`00000001 fffff801`67b8a940 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff801`5ee6acb8 fffff801`5b2066a5     : fffff801`5ee6ad10 00000000`00000001 fffff801`67b8a940 00000000`00000050 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff801`5ee6acc0 fffff801`5b2023e0     : fffff801`68058e18 fffff801`6805b148 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff801`5ee6aea0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320


SYMBOL_NAME:  nt!HvlpVtlCallExceptionHandler+22

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.572

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  22

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_nt!HvlpVtlCallExceptionHandler

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c4bb52a5-c6c0-a69d-d04f-6665c2332629}

Followup:     MachineOwner
---------
 
Son düzenleme:
Artı 0 Eksi
Wifi adaptörü kullanmıyorum.
Bluetooth adaptörümün donanım kimliği : Bluetooth Adaptör.rar
Msi Dragon Center kullanıyordum kaldırdım.Wireless mouse kullanıyordum ikinci bir mouse olarak çıkartım. Ancak tekrardan yeni ve farklı bir mavi ekran hatası aldım.Durdurma kodu: "Dpc_Watchdog_Violation"
 
Artı 0 Eksi
Kontrolcü için olan donanım kimliklerini kopyalayıp buraya yapıştırınız. Resimden yazamam. Ayrıca anakartın sitesinden ağ sürücülerinizi güncellediniz mi? Yeni dosyayı da paylaşın ve ekran kartınızın sürücüsünü DDU ile kaldırıp güncelleyin.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
 
Artı 0 Eksi
Çözüm
Tamamdır, şimdilik Bluetooth aygıtınızla oynamamıza gerek yok gibi. Şu işlemleri yapın.
Bora Dere dedi:
Ayrıca anakartın sitesinden ağ sürücülerinizi güncellediniz mi? Yeni dosyayı da paylaşın ve ekran kartınızın sürücüsünü DDU ile kaldırıp güncelleyin.

Rehber: DDU ile Sürücü Kaldırma Rehberi

Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
www.technopat.net www.technopat.net
Genişletmek için tıkla...
 
Artı 0 Eksi
Bu önceden aldığınız minidump, değil mi? Burada dediğiniz yani:
Şahin Özer dedi:
Ancak tekrardan yeni ve farklı bir mavi ekran hatası aldım.
Genişletmek için tıkla...
O halde DDU işlemi sorununuzu çözmüş olabilir. Emin olmak için BIOS default edin ve PC'ye telefonunuzu bağlıyorsanız bağlantısını kesin.
 
Son düzenleme:
Artı 0 Eksi
En son güncel tarih minidump bu vardı.Telefonumu bağlamıyorum.BIOS'u default yapayım.Çözülmüş olabilir.Ekran kartını güncelleştirdikten sonra kapanıp açılırken böyle birşey geldi.Düzelmesini umut ediyorum.Şimdiden teşekkür ederim.
 

Dosya Ekleri

  • e5e7ccf0-3746-4e58-b2ae-3b7f2366ca26.jpg
    e5e7ccf0-3746-4e58-b2ae-3b7f2366ca26.jpg
    56,5 KB · Görüntüleme: 56
Artı 0 Eksi
Rica ederim, disk checking yapıyor gibi. Yine mavi ekran alırsanız bu mesajımdan sonra yeni minidump dosyasını atarsınız. Çözülmüşse de belirtirseniz sevinirim.
 
Artı 0 Eksi

Benzer konular

Yunus Emre Doğru
  • Soru
Windows 10 "Kernel Security Check Failure" mavi ekran hatası
Mesaj
2
Görüntüleme
3B
Yunus Emre Doğru
Yunus Emre Doğru
frayed one
  • Soru
Windows 10 "kernel Security check failure" mavi ekran
Mesaj
3
Görüntüleme
872
maksu
maksu
HyperNowa
  • Soru
Windows 10 mavi ekran kernel Security check failure
2 3
Mesaj
22
Görüntüleme
3B
HyperNowa
HyperNowa
aly68
  • Soru
Windows 10 Kernel security check failure mavi ekran
Mesaj
4
Görüntüleme
3B
aly68
aly68
S
  • Soru
Windows 10 Mavi Ekran - Kernel security check failure
2 3 4
Mesaj
37
Görüntüleme
5B
FairyTale
F

Yeni konular

Yeni mesajlar

Geri
Yukarı