R9 3900X sistem Trident Z 32 GB RAM ile mavi ekran veriyor

  • Konuyu başlatan Elbar
  • Başlangıç Tarihi
  • Mesaj 12
  • Görüntüleme 602

Elbar

Femtopat
Katılım
22 Aralık 2020
Mesajlar
8
Daha fazla  
Cinsiyet
Erkek
Merhaba arkadaslar. Benim anakartim ASUS TUF Gaming X570 PLUS ve G.Skill Trident Z 32 GB RGB RAM kullaniyorum. Problemim neden kaynaklaniyor tam anlayamiyorum. 32 GB RAM'le 3D programlarda calisinca mavi ekran geliyor, ama tek RAM 16 GB calistirinca mavi ekran gelmiyor. Bazi arkadaslar bana islemcin AMD Ryzen 3900X-IN Intel XMP için uyumluluk saglamadigini soyledi. Eger bu uyumluluk saglamiyorsa o zaman 16 GB olunca da uyumluluk saglamasin ya. Tek RAM'i butun slotlarda tek tek denedim hiçbir sorun cikmadi. Baska 32 GB RAM taktim yine mavi ekran hatasi geldi. Problem kesin RAM problemi ama anakarttan mi yoksa RAM'de mi problem bunu bulamadim işte.
 
RAM'ler kit olarak mı alındı ayrı ayrı mı? Minidump dosyası da paylaşın.
 
RAM'ler kit olarak mı alındı ayrı ayrı mı? Minidump dosyası da paylaşın.


Kardeşim hala hatayi çözemedim, yukledim bakabilirsin.
 
Dosyanın erişimini açmalısınız.

Ek Açıklama 2020-08-16 103509.png


Ayrıca şu soruma cevap vermemişsiniz.
RAM'ler kit olarak mı alındı ayrı ayrı mı?
 
Belleklerde sorun görünüyor. İki modüle de ayır ayrı Memtest yapın, yani yaparken sadece biri takılı olsun. Sonra diğerine yapın.

Bir RAM ile sorun yaşamazken ikisiyle yaşıyorsanız sonradan çıkardığınız RAM'de donanımsal sorun olabilir. Bu durumda o RAM'i takmamak/değiştirmek de mavi ekran sorununuzu çözecektir.

RAM ile ilgili bir iyileştirme göze çarpmıyor ama BIOS da güncelleseniz iyi olur. Bakarsınız, sorun ondan kaynaklanıyordur.

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: fffff8020db0769f, The address that the exception occurred at
Arg3: ffff878b26d0d080, Parameter 0 of the exception
Arg4: 0000fffff8020d00, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7046

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8510

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

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

BUGCHECK_P2: fffff8020db0769f

BUGCHECK_P3: ffff878b26d0d080

BUGCHECK_P4: fffff8020d00

EXCEPTION_PARAMETER1:  ffff878b26d0d080

EXCEPTION_PARAMETER2:  0000fffff8020d00

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

FAILED_INSTRUCTION_ADDRESS:
nt!PspBuildCreateProcessContext+db
fffff802`0db0769f fe              ???

STACK_TEXT: 
ffffde8c`f6f2b5d8 fffff802`0d89128d     : 00000000`0000001e ffffffff`c000001d fffff802`0db0769f ffff878b`26d0d080 : nt!KeBugCheckEx
ffffde8c`f6f2b5e0 fffff802`0d8078ac     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16688d
ffffde8c`f6f2bca0 fffff802`0d801de9     : 00007ffa`cc5820e0 00000233`48e02340 00000000`00000000 00000058`2ce7f9d8 : nt!KiExceptionDispatch+0x12c
ffffde8c`f6f2be80 fffff802`0db0769f     : 00000000`00002000 ffff878b`126bd5a8 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329
ffffde8c`f6f2c010 fffff802`0db071f8     : 00000000`00000000 ffffde8c`f6f2c800 ffffca00`00000001 ffffde8c`f6f2c300 : nt!PspBuildCreateProcessContext+0xdb
ffffde8c`f6f2c290 fffff802`0d8071b8     : 00000000`00000000 00000000`00000003 ffffde8c`f6f2c9c0 ffff878b`26d0d080 : nt!NtCreateThreadEx+0x118
ffffde8c`f6f2c600 fffff802`0d7f95e0     : fffff802`0da41f5e 00000000`00000000 00000000`00000000 00000000`0000041c : nt!KiSystemServiceCopyEnd+0x28
ffffde8c`f6f2c808 fffff802`0da41f5e     : 00000000`00000000 00000000`00000000 00000000`0000041c 00000001`00000001 : nt!KiServiceLinkage
ffffde8c`f6f2c810 fffff802`0d6bfd94     : ffff878b`1f718d10 00000000`00000000 ffff878b`1f718d10 00000000`00000000 : nt!RtlpCreateUserThreadEx+0x156
ffffde8c`f6f2c950 fffff802`0d6460c1     : 00000000`00000000 ffffde8c`f6f2ca30 ffff878b`1f718e48 00000000`00000000 : nt!ExpWorkerFactoryCreateThread+0x10c
ffffde8c`f6f2ca10 fffff802`0d645dab     : ffff878b`1f718d10 ffffde8c`f6f2cae8 ffff878b`1f78e7c8 ffff878b`1f7a3320 : nt!ExpWorkerFactoryCheckCreate+0x201
ffffde8c`f6f2ca70 fffff802`0d8071b8     : ffff878b`26d0d080 ffff878b`00000000 ffff878b`1f718d10 ffff878b`00000000 : nt!NtReleaseWorkerFactoryWorker+0x26b
ffffde8c`f6f2cb00 00007ffa`cc60ed84     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000058`2cd7f7c8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`cc60ed84


CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff8020db07684-fffff8020db076bc)
fffff8020db07680  ff  49  89  b3 *f8  fe  ff  ff  49  89  b3  70 *f8  ff  ff  66 .I......I..p...f
fffff8020db07690  89  74  24  50 *f8  89  b3  80  fe  ff  ff  49 *f8  b3  40  fe .t$P.......I..@.
fffff8020db076a0  ff  ff  49  89 *f8  d0  fe  ff  ff  48  89  74 *f8  60  48  89 ..I......H.t.`H.
fffff8020db076b0  74  24  58  89 *73  24  40  89  74  24  68  49 *f8  b3  60  fe [email protected]$hI..`.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_STRIDE

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

Followup:     memory_corruption
---------
 
Belleklerde sorun görünüyor. İki modüle de ayır ayrı Memtest yapın, yani yaparken sadece biri takılı olsun. Sonra diğerine yapın.

Bir RAM ile sorun yaşamazken ikisiyle yaşıyorsanız sonradan çıkardığınız RAM'de donanımsal sorun olabilir. Bu durumda o RAM'i takmamak/değiştirmek de mavi ekran sorununuzu çözecektir.

RAM ile ilgili bir iyileştirme göze çarpmıyor ama BIOS da güncelleseniz iyi olur. Bakarsınız, sorun ondan kaynaklanıyordur.

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: fffff8020db0769f, The address that the exception occurred at.
Arg3: ffff878b26d0d080, Parameter 0 of the exception.
Arg4: 0000fffff8020d00, Parameter 1 of the exception.

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 7046.

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on BORA.

Key : Analysis.DebugData
Value: CreateObject.

Key : Analysis.DebugModel
Value: CreateObject.

Key : Analysis.Elapsed.mSec
Value: 8510.

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

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: ffffffffc000001d.

BUGCHECK_P2: fffff8020db0769f.

BUGCHECK_P3: ffff878b26d0d080.

BUGCHECK_P4: fffff8020d00.

EXCEPTION_PARAMETER1: ffff878b26d0d080.

EXCEPTION_PARAMETER2: 0000fffff8020d00.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: svchost.exe

FAILED_INSTRUCTION_ADDRESS:
nt!PspBuildCreateProcessContext+db
fffff802`0db0769f fe ???

STACK_TEXT:
ffffde8c`f6f2b5d8 fffff802`0d89128d : 00000000`0000001e ffffffff`c000001d fffff802`0db0769f ffff878b`26d0d080 : nt!KeBugCheckEx
ffffde8c`f6f2b5e0 fffff802`0d8078ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16688d
ffffde8c`f6f2bca0 fffff802`0d801de9 : 00007ffa`cc5820e0 00000233`48e02340 00000000`00000000 00000058`2ce7f9d8 : nt!KiExceptionDispatch+0x12c
ffffde8c`f6f2be80 fffff802`0db0769f : 00000000`00002000 ffff878b`126bd5a8 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x329
ffffde8c`f6f2c010 fffff802`0db071f8 : 00000000`00000000 ffffde8c`f6f2c800 ffffca00`00000001 ffffde8c`f6f2c300 : nt!PspBuildCreateProcessContext+0xdb
ffffde8c`f6f2c290 fffff802`0d8071b8 : 00000000`00000000 00000000`00000003 ffffde8c`f6f2c9c0 ffff878b`26d0d080 : nt!NtCreateThreadEx+0x118
ffffde8c`f6f2c600 fffff802`0d7f95e0 : fffff802`0da41f5e 00000000`00000000 00000000`00000000 00000000`0000041c : nt!KiSystemServiceCopyEnd+0x28
ffffde8c`f6f2c808 fffff802`0da41f5e : 00000000`00000000 00000000`00000000 00000000`0000041c 00000001`00000001 : nt!KiServiceLinkage
ffffde8c`f6f2c810 fffff802`0d6bfd94 : ffff878b`1f718d10 00000000`00000000 ffff878b`1f718d10 00000000`00000000 : nt!RtlpCreateUserThreadEx+0x156
ffffde8c`f6f2c950 fffff802`0d6460c1 : 00000000`00000000 ffffde8c`f6f2ca30 ffff878b`1f718e48 00000000`00000000 : nt!ExpWorkerFactoryCreateThread+0x10c
ffffde8c`f6f2ca10 fffff802`0d645dab : ffff878b`1f718d10 ffffde8c`f6f2cae8 ffff878b`1f78e7c8 ffff878b`1f7a3320 : nt!ExpWorkerFactoryCheckCreate+0x201
ffffde8c`f6f2ca70 fffff802`0d8071b8 : ffff878b`26d0d080 ffff878b`00000000 ffff878b`1f718d10 ffff878b`00000000 : nt!NtReleaseWorkerFactoryWorker+0x26b
ffffde8c`f6f2cb00 00007ffa`cc60ed84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000058`2cd7f7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`cc60ed84

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
8 errors : !nt (fffff8020db07684-fffff8020db076bc)
fffff8020db07680 ff 49 89 b3 *f8 fe ff ff 49 89 b3 70 *f8 ff ff 66 .I......I..p...f
fffff8020db07690 89 74 24 50 *f8 89 b3 80 fe ff ff 49 *f8 b3 40 fe .t$P.......I..@.
fffff8020db076a0 ff ff 49 89 *f8 d0 fe ff ff 48 89 74 *f8 60 48 89 ..I......H.t.`H.
fffff8020db076b0 74 24 58 89 *73 24 40 89 74 24 68 49 *f8 b3 60 fe [email protected]$hI..`.

MODULE_NAME: memory_corruption.

IMAGE_NAME: memory_corruption.

MEMORY_CORRUPTOR: STRIDE.

STACK_COMMAND: .thread ; .cxr ; kb.

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release.

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

FAILURE_ID_HASH: {574dbc1b-92cb-fb09-cb7a-cacc1bb2c511}

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

Teşekkür ederim, BIOS'da RAM'imi guncelleyeyim yoka BIOS'u mu guncelleyeyim anlamadim.
 

Geri
Yukarı