RTX 2070 Super ve Ryzen 7 3700X sistem mavi ekran hatası verdi

Teknoblog

Hectopat
Katılım
14 Nisan 2020
Mesajlar
64
Çözümler
1
Merhaba,
Sistem Özellikleri:
- AMD Ryzen 7 3700X.
-MSI RTX 2070 Super Gaming X Trio.
-Corsair Vengeance RGB Pro 16 GB 3600MHz.
-Samsung 500GB 970 Evo M.2 SSD.
- Seagate Barracuda 2TB harddisk.
-Corsair VS650
Daha önce sistemimde oyunlarda ani FPS düşüşü oluyordu. Premier Pro kasıyordu. Bilgisayara 2 hafta önce format attım. Sorunlarım çözülmedi. Bu sabah Premier Pro ile montaj yaparken bilgisayar aniden mavi ekran verdi. Bilgisayar açılınca kapatıp tekrar açtım. Bilgisayarın açılması yaklaşık 1 dakika sürdü. Bilgisayarı açtığımda Windows çok yavaşlamıştı. PSU'dan kaynaklanma ihtimali var mı? Anakartta 8+4 pin güç girişi var fakat sadece 8 pin bağlı. Başka hangi parçadan kaynaklanabilir? Teşekkürler.
 
Son düzenleyen: Moderatör:
Merhaba,
Sistem özellikleri:
- AMD Ryzen 7 3700X.
-MSI RTX 2070 Super Gaming X Trio.
-Corsair Vengeance RGB Pro 16 GB 3600MHz.
-Samsung 500GB 970 Evo M.2 SSD.
- Seagate Barracuda 2TB harddisk.
-Corsair VS650.
Daha önce sistemimde oyunlarda ani FPS düşüşü oluyordu. Premier Pro kasıyordu. Bilgisayara 2 hafta önce format attım. Sorunlarım çözülmedi. Bu sabah Premier Pro ile montaj yaparken bilgisayar aniden mavi ekran verdi. Bilgisayar açılınca kapatıp tekrar açtım. Bilgisayarın açılması yaklaşık 1 dakika sürdü. Bilgisayarı açtığımda Windows çok yavaşlamıştı. PSU'dan kaynaklanma ihtimali var mı? Anakartta 8+4 pin güç girişi var fakat sadece 8 pin bağlı. Başka hangi parçadan kaynaklanabilir? Teşekkürler.

Genellikle bu durum PSU'dan olur evet. Fakat Corsair kaliteli bir marka. 650 Watt'da yeterli gibi.
 
 
Yanıtınız için teşekkür ederim.
Minidump dosyası:
 
Ağ kartı sürücünüzü güncelleyiniz. Bitdefender güncelleyin güncelse kaldırın.
Kod:
*******************************************************************************
*                                                                             *
*                        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: fffff8032b3fbdd7, The address that the exception occurred at
Arg3: ffffbc8ae4ec8978, Parameter 0 of the exception
Arg4: fffff8032fe80920, Parameter 1 of the exception

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


WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 fffff8032fe80920

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx adresindeki y nerge, 0x%08lx bellek adresine ba

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
fffff803`2b3fbdd7 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_PARAMETER1:  ffffbc8ae4ec8978

EXCEPTION_PARAMETER2:  fffff8032fe80920

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

LAST_CONTROL_TRANSFER:  from fffff8032b50ed9f to fffff8032b3f3ea0

STACK_TEXT: 
fffff803`2fe800a8 fffff803`2b50ed9f : 00000000`0000001e ffffffff`c0000005 fffff803`2b3fbdd7 ffffbc8a`e4ec8978 : nt!KeBugCheckEx
fffff803`2fe800b0 fffff803`2b40f4d6 : fffff803`2fe80920 fffff803`2b253a05 ffffbc8a`e4ec8bb0 fffff803`2b3fbdd7 : nt!KiFatalFilter+0x1f
fffff803`2fe800f0 fffff803`2b3cae62 : fffff803`00000002 fffff803`2b0d2f90 ffffbc8a`e4ec5000 ffffbc8a`e4ecb000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
fffff803`2fe80130 fffff803`2b3fcd62 : fffff803`2b0d2f90 fffff803`2fe80710 fffff803`2b3cadc0 00000000`00000000 : nt!_C_specific_handler+0xa2
fffff803`2fe801a0 fffff803`2b285027 : fffff803`2fe80710 00000000`00000000 ffffbc8a`e4eca1e0 fffff803`2b2b8908 : nt!RtlpExecuteHandlerForException+0x12
fffff803`2fe801d0 fffff803`2b283ce6 : ffffbc8a`e4ec8978 fffff803`2fe80e20 ffffbc8a`e4ec8978 00000000`00000000 : nt!RtlDispatchException+0x297
fffff803`2fe808f0 fffff803`2b3f4d32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff803`2fe80fb0 fffff803`2b3f4d00 : fffff803`2b405fa5 ffffac86`0bd1bf8c ffffac86`5f63fd30 ffffac86`4e659030 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffbc8a`e4ec8838 fffff803`2b405fa5 : ffffac86`0bd1bf8c ffffac86`5f63fd30 ffffac86`4e659030 ffffac86`4e659030 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffbc8a`e4ec8840 fffff803`2b401ce0 : ffffac86`4eebae08 ffffbc8a`e4ec8a89 00000000`00000000 00000000`00000002 : nt!KiExceptionDispatch+0x125
ffffbc8a`e4ec8a20 fffff803`2b3fbdd7 : ffffac86`49542b00 fffff803`40c94b31 fffff803`38cbc6b0 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
ffffbc8a`e4ec8bb0 fffff803`40c94b31 : fffff803`38cbc6b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault
ffffbc8a`e4ec8bc0 fffff803`40c933c9 : 00000000`00000000 00060080`02000000 ffffac86`60552a80 00000000`00000001 : Ndu!NduCreateNblContext+0x59
ffffbc8a`e4ec8c00 fffff803`40c93251 : 00000000`00000000 00060080`02000000 00000000`00009b00 fffff803`38cba580 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0x149
ffffbc8a`e4ec8c80 fffff803`2f5a8c5e : ffffbc8a`e4ec8e68 00000000`00000002 00000000`00000004 00000000`00000000 : Ndu!NduOutboundMacClassify+0x151
ffffbc8a`e4ec8d00 fffff803`2f9e14d5 : 00000000`00000000 ffffac86`4f80de00 ffffac86`60552a80 00000000`00000051 : NETIO!KfdClassify2+0x19e
ffffbc8a`e4ec8dd0 fffff803`2f9e10ce : 00000000`00000000 ffffac86`561e78a0 00000000`00000000 00000000`00000000 : wfplwfs!L2InspectNetBufferListsFast+0x165
ffffbc8a`e4ec8ee0 fffff803`2f4258e8 : 00000000`00000001 ffffac86`60552a80 ffffac86`47b55930 fffff803`38bcb2c0 : wfplwfs!LwfLowerSendNetBufferLists+0xbe
ffffbc8a`e4ec8f90 fffff803`2f45df12 : 00000000`00000000 ffffbc8a`e4ec9059 ffffac86`484f1bd0 ffffbc8a`e4ec9008 : ndis!ndisCallSendHandler+0x58
ffffbc8a`e4ec8fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisInvokeNextSendHandler+0x10e


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8032b3963af-fffff8032b3963b1  3 bytes - nt!MiFreeUltraMapping+33
    [ 7d fb f6:65 cb 96 ]
    fffff8032b3fb391-fffff8032b3fb392  2 bytes - nt!SwapContext+491 (+0x64fe2)
    [ 48 ff:4c 8b ]
    fffff8032b3fb398-fffff8032b3fb39b  4 bytes - nt!SwapContext+498 (+0x07)
    [ 0f 1f 44 00:e8 83 a0 61 ]
    fffff8032b3fbb16-fffff8032b3fbb1a  5 bytes - nt!tcpxsum+96 (+0x77e)
    [ 41 ff e1 cc cc:e8 a5 96 61 00 ]
    fffff8032b3fbec9-fffff8032b3fbecd  5 bytes - nt!RtlpCaptureContext+9 (+0x3b3)
    [ ff e2 cc cc cc:e8 12 92 61 00 ]
19 errors : !nt (fffff8032b3963af-fffff8032b3fbecd)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

BUCKET_ID:  MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:memory_corruption_large

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup: memory_corruption
---------
 

Geri
Yukarı