KMODE_EXCEPTION_NOT_HANDLED Windows 10 mavi ekran hats

İşletim sistemi
Windows 10

nef

Hectopat
Katılım
4 Ağustos 2020
Mesajlar
113
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
Minidump Dosyası

Merhaba arkadaşlar, Dün aldığım DPC_WATCHDOG_VİOLATİON dan sonra birde başıma bu çıktı. Dün Blender üzerinden çalışıyorken daha çalışmayı kaydetmeden bilgisayar kapandı ve mavi ekran verdi.

MSI Afterburner ve CPU-Z sildim. Ağ sürücülerini sitesinden güncelledim. RAM'leri de Windows ile kontrol ettim sorunsuz görünüyor. Geriye bir tek BIOS güncellemesi olayı kaldı. Onu da yapacağım ancak bölgemde elektrik kesintisi çok olduğu için son seçenek olarak düşünüyorum. Başka önerebileceğiniz bir şey var mıdır? Ha bir de mavi ekrandan sonra bilgisayar açılınca karşıma şu çıktı:



Kod:
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\PC\Desktop\102620-7515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`26e00000 PsLoadedModuleList = 0xfffff803`27a2a310
Debug session time: Mon Oct 26 23:07:49.104 2020 (UTC + 3:00)
System Uptime: 0 days 5:17:05.757
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`271f45a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffaf01`b3e520b0=000000000000001e
11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff803271fc4d7, The address that the exception occurred at
Arg3: ffffd40092858be8, Parameter 0 of the exception
Arg4: ffffaf01b3e52920, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4593

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13136

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

    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: fffff803271fc4d7

BUGCHECK_P3: ffffd40092858be8

BUGCHECK_P4: ffffaf01b3e52920

WRITE_ADDRESS: fffff80327afb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80327a0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80327a0f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffffaf01b3e52920

EXCEPTION_PARAMETER1:  ffffd40092858be8

EXCEPTION_PARAMETER2:  ffffaf01b3e52920

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  uTorrent.exe

TRAP_FRAME:  fffff80729cebb77 -- (.trap 0xfffff80729cebb77)
Unable to read trap frame at fffff807`29cebb77

BAD_STACK_POINTER:  ffffaf01b3e520a8

STACK_TEXT:
ffffaf01`b3e520a8 fffff803`2730e6bf     : 00000000`0000001e ffffffff`c0000005 fffff803`271fc4d7 ffffd400`92858be8 : nt!KeBugCheckEx
ffffaf01`b3e520b0 fffff803`2720d066     : ffffaf01`b3e52920 fffff803`2708db25 ffffd400`92858e20 fffff803`271fc4d7 : nt!KiFatalFilter+0x1f
ffffaf01`b3e520f0 fffff803`271cb262     : fffff803`00000002 fffff803`26ec9aa4 ffffd400`92855000 ffffd400`9285b000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffffaf01`b3e52130 fffff803`271fd462     : fffff803`26ec9aa4 ffffaf01`b3e52710 fffff803`271cb1c0 00000000`00000000 : nt!_C_specific_handler+0xa2
ffffaf01`b3e521a0 fffff803`27052d97     : ffffaf01`b3e52710 00000000`00000000 ffffd400`9285a220 fffff803`2700d468 : nt!RtlpExecuteHandlerForException+0x12
ffffaf01`b3e521d0 fffff803`270519a6     : ffffd400`92858be8 ffffaf01`b3e52e20 ffffd400`92858be8 00000000`00000000 : nt!RtlDispatchException+0x297
ffffaf01`b3e528f0 fffff803`271f5432     : ffffa880`eb652210 ffffffff`c0000005 fffff807`29cebb77 00000000`00000000 : nt!KiDispatchException+0x186
ffffaf01`b3e52fb0 fffff803`271f5400     : fffff803`272066a5 ffffd982`dc805280 ffffd982`e0245c00 ffffd982`ddbe4000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffd400`92858aa8 fffff803`272066a5     : ffffd982`dc805280 ffffd982`e0245c00 ffffd982`ddbe4000 fffff803`291973a3 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffd400`92858ab0 fffff803`272023e0     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd982`d8e74121 : nt!KiExceptionDispatch+0x125
ffffd400`92858c90 fffff803`271fc4d7     : ffffd982`d7f030c0 fffff803`365f6d7c ffffd982`da98e220 00000000`00000002 : nt!KiGeneralProtectionFault+0x320
ffffd400`92858e20 fffff803`365f6d7c     : ffffd982`da98e220 00000000`00000002 00000000`00000000 fffff803`294114ac : nt!ExpInterlockedPopEntrySListFault
ffffd400`92858e30 fffff803`365f4b4f     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : Ndu!PplGenericAllocateFunction+0x1c
ffffd400`92858e70 fffff803`365f33c9     : 00000000`00000000 00470080`01000000 ffffd982`da89e480 fffff803`3af89ff0 : Ndu!NduCreateNblContext+0x77
ffffd400`92858eb0 fffff803`365f3251     : ffffd982`d7a9bbd4 00470080`01000000 00000000`00002d00 fffff803`28bc8442 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0x149
ffffd400`92858f30 fffff803`28d48c5e     : ffffd400`92859118 00000000`00000002 ffffd982`00000004 fffff803`3af902b1 : Ndu!NduOutboundMacClassify+0x151
ffffd400`92858fb0 fffff803`294914d5     : ffffd982`dc4bca50 fffff803`28bc5afa ffffd982`dc4bca50 00000000`00000051 : NETIO!KfdClassify2+0x19e
ffffd400`92859080 fffff803`294910ce     : 00000000`00000000 ffffd982`d7a9c010 ffffd982`d7a9c010 fffff803`34b26380 : wfplwfs!L2InspectNetBufferListsFast+0x165
ffffd400`92859190 fffff803`28bc58e8     : ffffd982`dced0d01 ffffd982`dc4bca50 ffffd982`da304870 fffff803`349fb2c0 : wfplwfs!LwfLowerSendNetBufferLists+0xbe
ffffd400`92859240 fffff803`28bfe0e2     : 00000000`00000000 ffffd400`92859309 ffffd982`d7a78b20 00000000`00000000 : ndis!ndisCallSendHandler+0x58
ffffd400`92859290 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisInvokeNextSendHandler+0x10e


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_STACKPTR_ERROR_Ndu!PplGenericAllocateFunction

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {040fbfea-4e33-dce2-4a10-b9c4b0dd9e1c}

Followup:     MachineOwner
---------
 
Bir Wİ-Fİ adaptörü kullanıyor musunuz? Eğer kullanıyorsanız. Onun yazılımı varsa güncelleyin.


Wİ-Fİ ağlarını güncelleyerek iyi yapmışsınız.




Buradan en güncel BİOS indirebilirsiniz.
 
Ağ kartı sürücüsü sorun çıkarmış yine. Düzgün güncellediniz mi? Bellek bozulmasıda olabilir belleğe erişim reddedilmiş gözüküyor.
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…