UNEXPECTED_KERNEL_MODE_TRAP Mavi Ekran

PikaTak

Hectopat
Katılım
17 Ağustos 2016
Mesajlar
468
Çözümler
1
Yer
Bursa
Daha fazla  
Sistem Özellikleri
AMD Ryzen 5 5500
XFX AMD RADEON RX 6650 XT 8GB GDDR6
Asus Prime B450M-K II
GoodRam 512GB M2 SSD PX500 2000/1600MB
MLD 480GB M200 SATA SSD 560/520MB
MLD 480GB M200 SATA SSD 560/520MB
Corsair Vengeance RGB RS 2x16 GB 3600MHz CL18 DDR4
FSP 650W PERFORMANCE PSU
Cinsiyet
Erkek
Meslek
Radyoloji Teknikeri
Son düzenleyen: Moderatör:
CMD yönetici olarak çalıştır.

sfc /scannow
Bu komutu yaz.

Memtest86 ile bellek testi yap.


CODE]UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffc881c53cb090
Arg3: ffffc881c53d4000
Arg4: fffff8014f850b74

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

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

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffc881c53cb090

BUGCHECK_P3: ffffc881c53d4000

BUGCHECK_P4: fffff8014f850b74

TRAP_FRAME: ffffc881c53cb090 -- (.trap 0xffffc881c53cb090)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8014f852250
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8014f850b74 rsp=ffffc881c53d4000 rbp=ffffed8c315d99e0
r8=000000002c4bef28 r9=00000000880bebe9 r10=0000000000002427
r11=00000000242766f5 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
clipsp+0x30b74:
fffff801`4f850b74 51 push rcx
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: LogonUI.exe

BAD_STACK_POINTER: ffffc881c53d4000

STACK_TEXT:
ffffc881`c53caf48 fffff801`4abd41e9 : 00000000`0000007f 00000000`00000008 ffffc881`c53cb090 ffffc881`c53d4000 : nt!KeBugCheckEx
ffffc881`c53caf50 fffff801`4abcf043 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc881`c53cb090 fffff801`4f850b74 : c53d7200`00000000 00000000`ffffc881 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c3
ffffc881`c53d4000 c53d7200`00000000 : 00000000`ffffc881 00000000`00000000 00000000`00000000 c53d73d0`00000000 : clipsp+0x30b74
ffffc881`c53d4008 00000000`ffffc881 : 00000000`00000000 00000000`00000000 c53d73d0`00000000 c53d75d0`ffffc881 : 0xc53d7200`00000000
ffffc881`c53d4010 00000000`00000000 : 00000000`00000000 c53d73d0`00000000 c53d75d0`ffffc881 c53d77d0`ffffc881 : 0xffffc881


SYMBOL_NAME: clipsp+30b74

MODULE_NAME: clipsp

IMAGE_NAME: clipsp.sys

IMAGE_VERSION: 10.0.18362.387

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 30b74

FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {48f2dfdf-6e28-ad4e-f693-f41bb475ff86}

Followup: MachineOwner
---------
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb98c2858f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.

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

fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff8006822a3d8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

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

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb98c2858f028

BUGCHECK_P3: f2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffa800`10eddb58 fffff800`67da4188 : 00000000`00000124 00000000`00000000 ffffb98c`2858f028 00000000`f2000000 : nt!KeBugCheckEx
ffffa800`10eddb60 fffff800`6a5f1920 : ffffb98c`248fc380 00000000`00000000 ffffb98c`2858f028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffa800`10eddba0 fffff800`681410a2 : ffffb98c`248fc380 ffffa800`10eddc29 00000000`00000000 ffffb98c`2858f028 : PSHED!PshedBugCheckSystem+0x10
ffffa800`10eddbd0 fffff800`67da5ae6 : ffffa800`10eddcf0 00000000`00000007 ffffb98c`248fc3d0 ffffb98c`248fc380 : nt!WheaReportHwError+0x382
ffffa800`10eddc90 fffff800`67da5f7a : 00000000`00000010 ffffb98c`248fc3d0 ffffa800`10edde48 ffffa800`10ede090 : hal!HalpMcaReportError+0x72
ffffa800`10edddf0 fffff800`67da5e54 : ffffb98c`24712110 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffa800`10edde40 fffff800`67da60c0 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffa800`10edde80 fffff800`67da5168 : 00000000`00000000 ffffa800`10ede110 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffa800`10eddeb0 fffff800`67da6347 : ffffb98c`24712110 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffa800`10eddee0 fffff800`680a4e40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffa800`10eddf10 fffff800`67fd13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffa800`10eddf40 fffff800`67fd106f : ffff8405`00000000 fffff800`67fd0fac ffff8405`16162968 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa800`10ede080 fffff800`81b2cfbe : ffff8405`16162968 ffff8405`00000000 000000e4`00000000 000000e4`3aeff0b0 : nt!KiMcheckAbort+0x26f
ffff8405`161628d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkGetDeviceStateInternal+0x25e


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ad18667d-e4af-4a49-4062-3121e823755f}

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

KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE (162)
A lock tracked by AutoBoost was released by a thread that did not own the lock.
This is typically caused when some thread releases a lock on behalf of another
thread (which is not legal with AutoBoost tracking enabled) or when some thread
tries to release a lock it no longer owns.
Arguments:
Arg1: ffffd4037b55c080, The address of the thread
Arg2: ffffd4032459bde8, The lock address
Arg3: 00000000ffffffff, The session ID of the thread
Arg4: 0000000000000000, Reserved

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


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

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

Key : Analysis.System
Value: CreateObject

Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1


DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_CODE: 162

BUGCHECK_P1: ffffd4037b55c080

BUGCHECK_P2: ffffd4032459bde8

BUGCHECK_P3: ffffffff

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RazerCortexRpc

STACK_TEXT:
ffff8303`4bbbf5f8 fffff801`50a55acd : 00000000`00000162 ffffd403`7b55c080 ffffd403`2459bde8 00000000`ffffffff : nt!KeBugCheckEx
ffff8303`4bbbf600 fffff801`508f1059 : ffffffff`00000001 ffffa384`00000001 ffffd403`00000000 00000000`00000000 : nt!MiFinishVadDeletion+0x1648fd
ffff8303`4bbbf6b0 fffff801`50e79a0d : 00000000`00000000 00000000`2340c7a0 ffffd403`2459bdc0 00000000`00000000 : nt!MiDeleteVad+0x19a9
ffff8303`4bbbf870 fffff801`50e79803 : ffffd403`2459bdc0 00000000`00000000 00000234`0c7a0000 00000000`00000000 : nt!MiUnmapVad+0x49
ffff8303`4bbbf8a0 fffff801`50e79699 : ffffd403`7b19c080 00000000`00000008 ffffd403`0e8c17a0 00000000`00000000 : nt!MiUnmapViewOfSection+0x133
ffff8303`4bbbf980 fffff801`50e7938c : ffffd403`7b55c080 00000000`00000000 00000000`00000004 ffffd403`7b19c080 : nt!NtUnmapViewOfSectionEx+0x99
ffff8303`4bbbf9d0 fffff801`509d3c15 : 000000aa`8c8fe4c0 ffff8303`4bbbfa80 00007ff6`e63a9c40 ffff8303`4bbbfa80 : nt!NtUnmapViewOfSection+0xc
ffff8303`4bbbfa00 00007ff9`563bc5b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000aa`8c8fe3f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`563bc5b4


SYMBOL_NAME: nt!MiFinishVadDeletion+1648fd

MODULE_NAME: nt

IMAGE_VERSION: 10.0.18362.836

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 1648fd

FAILURE_BUCKET_ID: 0x162_nt!MiFinishVadDeletion

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {76bbccac-c7ba-6d1a-4914-edaf6e42c402}

Followup: MachineOwner
---------
[/CODE]
 
CMD yönetici olarak çalıştır.

sfc /scannow
Bunu zaten daha dün yapmıştım. Windows'un kendi aracıyla da bir iki hafta önce bellek testi yaptım onda da bir sorun çıkmamıştı.
 
Memtest86 ile bellek testi yapınız.
Keşke 3 saatten fazla sürebileceğini söyleseydiniz. Sabah 8'de kalkmam gerekiyor hala testin bitmesini bekliyorum.
Memtest86 ile bellek testi yapınız.
Buyurun. RAM'de bir sorun yok.

56a787a3-a69f-4a93-8e52-73206304c1a2.jpg
242ec728-6061-49f1-8106-4566e54e5b30.jpg
c85debf7-715d-4bef-be26-a9bc7211dc01.jpg
 
Son düzenleyen: Moderatör:
Tekrar mavi ekran alırsan dump dosyanı paylaş.
Çok uzun olmayan bir süre önce farklı bir kodla almıştım. İşlemcime Undervolt uyguladım ondan kaynaklı olabilir diye her mavi ekranda bir tık azaltıyorum. Tekrar olursa paylaşırım.
 
Windows güncel değil 1909'a güncelleyin.
Vanguard kaldırın, Bitdefender güncel değilse güncelleyin.
ThrottleStop gibi yazılımlarını bir daha kullanmayın. Kullanmasını bilmediğiniz yazılımları kullanmayın. Varsayılan değerlere getirip kaldırın.
 
Windows güncel değil 1909'a güncelleyin.
Vanguard kaldırın, Bitdefender güncel değilse güncelleyin.
ThrottleStop gibi yazılımlarını bir daha kullanmayın. Kullanmasını bilmediğiniz yazılımları kullanmayın. Varsayılan değerlere getirip kaldırın.
Windows Update bana güncelleme vermiyor ben de zorla yüklemiyorum. Vanguard kaldırırsam Valorant oynayamam. ThrottleStop ile de undervolt kullanıyorum. Neden kaldırayım? Çok faydasını gördüm. Kullanmasını biliyorum rahat olun.
 

Yeni konular

Geri
Yukarı