KMODE_EXCEPTION_NOT_HANDLED mavi ekran hatası


Bellekleri test et.


BIOS güncellemesi gelmiş, güncelle.


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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80759106ba0, The address that the exception occurred at
Arg3: fffff80759b26600, Parameter 0 of the exception
Arg4: fffff8075910eba0, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80759106ba0

BUGCHECK_P3: fffff80759b26600

BUGCHECK_P4: fffff8075910eba0

EXCEPTION_PARAMETER1:  fffff80759b26600

EXCEPTION_PARAMETER2:  fffff8075910eba0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

BAD_STACK_POINTER:  fffff8075f6a38e8

FAILED_INSTRUCTION_ADDRESS:
nt!MiDeleteUltraMapContext+12c
fffff807`59106ba0 40              ???

STACK_TEXT:
fffff807`5f6a38e8 fffff807`5922edf9 : 00000000`0000001e ffffffff`c000001d fffff807`59106ba0 fffff807`59b26600 : nt!KeBugCheckEx
fffff807`5f6a38f0 fffff807`591de8b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b3d59
fffff807`5f6a3fb0 fffff807`591de880 : fffff807`591efa65 ffffce85`0871c501 00000000`00000000 ffff800d`9dd60e10 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff807`5f68d2f8 fffff807`591efa65 : ffffce85`0871c501 00000000`00000000 ffff800d`9dd60e10 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff807`5f68d300 fffff807`591e9fa9 : 00000000`00000000 00001f80`00000200 00000000`00000000 00000000`98d8da01 : nt!KiExceptionDispatch+0x125
fffff807`5f68d4e0 fffff807`59106ba0 : fffff807`67f41ac5 00000000`00000001 ffff800d`98d8da90 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329
fffff807`5f68d678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteUltraMapContext+0x12c


SYMBOL_NAME:  nt!MiDeleteUltraMapContext+12c

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.329

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  12c

FAILURE_BUCKET_ID:  0x1E_c000001d_STACKPTR_ERROR_BAD_IP_nt!MiDeleteUltraMapContext

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5948ba6c-2049-1df2-08d4-e86b71d5ab38}

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

Bellekleri test et.

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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff80759106ba0, The address that the exception occurred at
Arg3: fffff80759b26600, Parameter 0 of the exception
Arg4: fffff8075910eba0, Parameter 1 of the exception

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 4

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

Key : Analysis.System
Value: CreateObject

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff80759106ba0

BUGCHECK_P3: fffff80759b26600

BUGCHECK_P4: fffff8075910eba0

EXCEPTION_PARAMETER1: fffff80759b26600

EXCEPTION_PARAMETER2: fffff8075910eba0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

BAD_STACK_POINTER: fffff8075f6a38e8

FAILED_INSTRUCTION_ADDRESS:
nt!MiDeleteUltraMapContext+12c
fffff807`59106ba0 40 ???

STACK_TEXT:
fffff807`5f6a38e8 fffff807`5922edf9 : 00000000`0000001e ffffffff`c000001d fffff807`59106ba0 fffff807`59b26600 : nt!KeBugCheckEx
fffff807`5f6a38f0 fffff807`591de8b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b3d59
fffff807`5f6a3fb0 fffff807`591de880 : fffff807`591efa65 ffffce85`0871c501 00000000`00000000 ffff800d`9dd60e10 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff807`5f68d2f8 fffff807`591efa65 : ffffce85`0871c501 00000000`00000000 ffff800d`9dd60e10 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff807`5f68d300 fffff807`591e9fa9 : 00000000`00000000 00001f80`00000200 00000000`00000000 00000000`98d8da01 : nt!KiExceptionDispatch+0x125
fffff807`5f68d4e0 fffff807`59106ba0 : fffff807`67f41ac5 00000000`00000001 ffff800d`98d8da90 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329
fffff807`5f68d678 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteUltraMapContext+0x12c

SYMBOL_NAME: nt!MiDeleteUltraMapContext+12c

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.329

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 12c

FAILURE_BUCKET_ID: 0x1E_c000001d_STACKPTR_ERROR_BAD_IP_nt!MiDeleteUltraMapContext

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5948ba6c-2049-1df2-08d4-e86b71d5ab38}

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

Hemen test ediyorum
 
Biraz daha inceledim BIOS sürümü eskiymiş, onu da güncelle. Üstteki mesaja ekledim.

BIOS'un son sürümünde hata almıştım, tekrar günceleyeceğim, bellekler aynı marka model olamasına rağmen chipler farklı.
Biri Hynix öbürü Samsung bellekler XMP profile 2.0 ile 3200 MHz çalışıyorlar, bu arada Windows 10 üzerinde bellek testinde hata verdiler, ben de tek tek test ettim sonrasında ve sorunsuz çalıştılar. Bir tanesini silgi ile temizledim ve BIOS güncelleyip tekrar test edeceğim sonuçları buraya yazarım.
BIOS verisiyonunu en son sürüme güncelleyip bellek testini gerçekleştirdim ve hiçbir sorun bulunamadı. Şu anlık sorunum çözüldü diyebilirim ileleyen zamanlar için tekrar alırsam aynı hatayı diyerek konuya tam anlamıyla çözüldü diyemiyorum.
 

Yeni konular

Geri
Yukarı