MSI GE75 Raider 9SE mavi ekran hatası

İşletim sistemi
Windows 10

Muhammet Çoban

Yoctopat
Katılım
28 Ekim 2021
Mesajlar
4
Daha fazla  
Cinsiyet
Erkek
Minidump.rar minidump dosyalarımı buraya attım arkadaşlar. Mavi ekran hatasını genellikle SSD yük altındayken alıyorum ama sorunu anlayamadım. Ne yapmam gerekiyor? Yardımcı olursanız sevinirim.
Sistem özellikleri:
Cihaz adı MSI GE75 Raider 9SE.
İşlemci Intel(r) Core(tm) i7-9750H CPU @ 2.60GHz 2.59 GHz.
Takılı RAM 16,0 GB (kullanılabilir: 15,8 GB)
Ekran kartı: RTX 2060 6 GB.
SSD: Wdc PC SN720 sdapntw-256g
HDD: ST1000LM049-2GH172
 
Merhaba. Memtest86 ile RAM testi yapar mısınız? Minidump dosyası açık bir şekilde hardware diyor. Memtest86 ile Bozuk RAM Testi
[CODE title="Minidump Dosya 1"]
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffcb00c017b8b8
Arg3: 0004000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2781

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 30012

Key : Analysis.Init.CPU.mSec
Value: 312

Key : Analysis.Init.Elapsed.mSec
Value: 11913

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

Key : MemoryManagement.PFN
Value: 0

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


BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffcb00c017b8b8

BUGCHECK_P3: 4000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: mighost.exe

STACK_TEXT:
ffffdf0e`173aeff8 fffff807`16a440ca : 00000000`0000001a 00000000`00041792 ffffcb00`c017b8b8 00040000`00000000 : nt!KeBugCheckEx
ffffdf0e`173af000 fffff807`16a9e416 : 00000000`00000000 ffffcb8c`b6484700 00000000`00000009 ffffcb00`c017b8b8 : nt!MiDeleteVa+0x153a
ffffdf0e`173af100 fffff807`16a9e52b : ffffcb65`80600bd8 ffffcb8c`b6484700 ffffdf0e`00000000 ffffdf0e`173af570 : nt!MiWalkPageTablesRecursively+0x776
ffffdf0e`173af1a0 fffff807`16a9e52b : ffffcb65`b2c03000 ffffcb8c`b6484700 ffffdf0e`00000001 ffffdf0e`173af580 : nt!MiWalkPageTablesRecursively+0x88b
ffffdf0e`173af240 fffff807`16a9e52b : ffffcb65`b2c03000 ffffcb8c`b6484700 ffffdf0e`00000002 ffffdf0e`173af590 : nt!MiWalkPageTablesRecursively+0x88b
ffffdf0e`173af2e0 fffff807`16a04f4b : 00000001`00000000 ffffcb8c`b6484700 ffffcb8c`00000003 ffffdf0e`173af5a0 : nt!MiWalkPageTablesRecursively+0x88b
ffffdf0e`173af380 fffff807`16a42961 : ffffdf0e`173af520 ffffcb8c`00000000 00000000`00000002 00000180`00000000 : nt!MiWalkPageTables+0x36b
ffffdf0e`173af480 fffff807`16a12aa0 : 00000000`00000001 ffffdf0e`00000000 ffffcb8c`b6484550 ffffcb8c`c92e23c0 : nt!MiDeletePagablePteRange+0x4f1
ffffdf0e`173af790 fffff807`16e01149 : ffffcb8c`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x360
ffffdf0e`173af8a0 fffff807`16e00f22 : ffffcb8c`c03a31e0 00000000`00000000 ffffcb8c`b6484080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffdf0e`173af8d0 fffff807`16e00d99 : ffffcb8c`c92e23c0 00000022`1ff79bd0 00000180`2f77b560 00000000`00000000 : nt!MiUnmapViewOfSection+0x152
ffffdf0e`173af9b0 fffff807`16c090ee : ffffcb8c`c92e23c0 00000180`2f3e0000 ffffdf0e`00000000 ffffcb8c`b6484080 : nt!NtUnmapViewOfSectionEx+0x99
ffffdf0e`173afa00 00007ff9`e35506e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9
00000022`1ff79c78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`e35506e4


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner[/CODE]

[CODE title="Minidump Dosya 2"]
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: fffff80605e08d0c, The address that the exception occurred at
Arg3: fffff90953d074e8, Exception Record Address
Arg4: fffff90953d06d20, Context Record Address

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

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

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 3906

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 55582

Key : Analysis.Init.CPU.mSec
Value: 562

Key : Analysis.Init.Elapsed.mSec
Value: 13642

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

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


BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80605e08d0c

BUGCHECK_P3: fffff90953d074e8

BUGCHECK_P4: fffff90953d06d20

EXCEPTION_RECORD: fffff90953d074e8 -- (.exr 0xfffff90953d074e8)
ExceptionAddress: fffff80605e08d0c (nt!ExAcquireResourceExclusiveLite+0x000000000000001c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff90953d06d20 -- (.cxr 0xfffff90953d06d20)
rax=0000000000000702 rbx=fff7bf0c89e05cb0 rcx=fff7bf0c89e05c02
rdx=ffffe20702f97000 rsi=ffffe20702f972b0 rdi=ffffe20702f972f0
rip=fffff80605e08d0c rsp=fffff90953d07720 rbp=fffff80609fb8d90
r8=0000000000000000 r9=000000000000001e r10=fffff80605e08cf0
r11=000000000000018f r12=0000000000000600 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050202
nt!ExAcquireResourceExclusiveLite+0x1c:
fffff806`05e08d0c 0fb7431a movzx eax,word ptr [rbx+1Ah] ds:002b:fff7bf0c`89e05cca=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

READ_ADDRESS: fffff806068fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

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

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffff909`53d07720 fffff806`09fb7c44 : ffffe207`02f97200 ffffe207`02f97010 ffffe207`02f98880 ffffe207`02f972b0 : nt!ExAcquireResourceExclusiveLite+0x1c
fffff909`53d077b0 fffff806`09fb8f00 : ffffe207`02f972b0 fffff806`09fb8d90 ffffe207`02f972b0 00000000`00000000 : Ntfs!NtfsAcquireResourceExclusive+0x2c
fffff909`53d077e0 fffff806`05eb8515 : ffffbf0c`8057e040 ffffbf0c`8057e040 ffffbf0c`5cead560 fffff806`0a034be0 : Ntfs!NtfsMcbCleanupLruQueue+0x170
fffff909`53d07a70 fffff806`05f55855 : ffffbf0c`8057e040 00000000`00000080 ffffbf0c`5cf101c0 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
fffff909`53d07b10 fffff806`05ffe808 : ffff8701`99959180 ffffbf0c`8057e040 fffff806`05f55800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff909`53d07b60 00000000`00000000 : fffff909`53d08000 fffff909`53d01000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!ExAcquireResourceExclusiveLite+1c

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1288

STACK_COMMAND: .cxr 0xfffff90953d06d20 ; kb

BUCKET_ID_FUNC_OFFSET: 1c

FAILURE_BUCKET_ID: AV_nt!ExAcquireResourceExclusiveLite

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d1328bfd-2b11-7819-3ef8-5888a1d52bca}

Followup: MachineOwner
---------[/CODE]
 
Test daha bitmedi ama şu anlık böyle,
image.jpg

@Muhammet Çoban @siriius
Şimdi de bu çıktı ne yapmam gerekiyor?
EABCC66D-078B-433F-AA2C-03D16B48ACF0.jpeg
 
Son düzenleme:
Uyarı! Bu konu 5 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

Yeni konular

Geri
Yukarı