Skocz do zawartości

Problem ram DDR4 Gskillz i Good iriduim


Go to solution Solved by Sundia,

Recommended Posts

Witam mam ost kilka problemow głownie problem z ramami posiadam 2 kosci DDR4 Gskillz 3000mhz i Good iriduim Ram 3000mhz 2x 

 

razem mam 32gb  

 

1 problem wszystkie sa na jednej plycie maksymalnie osiagaja wartosc  2128MHZ  na wiecej nie daje sie przestawic probowalem wszystkiego  czemu nie moge dac im wyzej?

 

 

nie zmienialem timingow na tym sie nie znam ustawilem Ram Voltage na 1.350 profil xmp  

 

Druga sprawa ost wywalalo mi bledy podczas przegladania chrome czy grania 

report z Whocrashed  Wgralem na nowo Wina do PC bo to wywalalo i na zasyfionym  ale nowy win nie pomogl

 

moje pc :

AMD ryzen 5 1600

Plyta AB350 PRO4 

Karta graf 1050ti

Zasilacz Seasonic 520V

Aegis, DDR4, 16 GB,3000MHz, CL16 

Good ram Iridium 3000mhz 16GB CL16

 

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Tue 7/7/2020 1:27:42 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070720-10406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8077B8FA318, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 7/7/2020 4:46:56 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070720-9218-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF80284CC2EC7)
Bugcheck code: 0x1000007F (0x8, 0xFFFF9601892E7E70, 0x0, 0xFFFFF80284CC2EC7)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 7/4/2020 8:54:51 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070420-9109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xC000021A (0xFFFF9283F76F9390, 0xFFFFFFFFC0000428, 0x0, 0x185D2AD0000)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 7/4/2020 4:37:16 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070420-9406-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xF3339)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80775018FFD, 0x1, 0x200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sat 7/4/2020 4:33:44 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070420-9796-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80113C2669B, 0xFFFFED85D7B9B370, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/2/2020 9:26:57 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81B9)
Bugcheck code: 0xA (0xD0000000, 0x2, 0x0, 0xFFFFF80179326B14)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

i 3 problem mam bios z 2018 nie moge zrobic Update pobieram sterowniki z oficjalnej strony wrzucam na pena (przed tym formatuje na fat32)   wchodze do biosu by zrobic aktualizacje  i du*a no image  file detected nie znajduje mi plikow z pen jest na 100% fat32
 

Edytowane przez Sundia
Link to post
Share on other sites

 

Zasilacz Seasonic 520V

 

 

Cześć 

Masz za duże napięcie na zasilaczu 520V toż to pali wszystko.

 

Popraw to bo razi w oczy

 

 

Co do problemu sprawdziłeś na stronie producenta czy te pamięci są zgodne z tą płytą główną? bo może się okazać, iż któreś nie będą pracować z profilami xmp

Edytowane przez kazadan666
Link to post
Share on other sites

Sprawdzilem na stronie wyglada na to ze sa chyba ze zle sprawdzam :P  rzeczywiscie wpisalem V zamiast W sory nie moge tego poprawic juz nie ma opcji edytuj  nie wiem czemu  a profil xmp wejsc wejdzie ale tylko na niskiej wartości mhz 

Edytowane przez Sundia
Link to post
Share on other sites
  • Solution

bios na mobo najnowszy?

 

napisalem na koncu ze mam problem z wgraniem biosu ustawilem format 32  na pena  pobralem pliki i mam image not find  pobieralem z glownej strony amd do plyty asrock ab350 pro4  wedlug dat mam bios 2018 czyli stary ale w zaden sposob nie znajduje mi plikow nowego biosu

dobra problem z biosem rozwiazany jest juz wgrany najnowszy ale dalej kosci pracuja na 2133mhz a nie 3000mhz

wyglada na to ze problem byl z biosem jest juz wgrany najnowszy testowalem najnowszy  odpalilem obciazenie ram na maks procka i karte na 10min nie wywalilo bledu wiec chyba jest juz okej  temat ten do zamkniecia 

Link to post
Share on other sites

Dołącz do dyskusji

Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.

Gość
Odpowiedz w tym wątku...

×   Wklejono zawartość z formatowaniem.   Usuń formatowanie

  Dozwolonych jest tylko 75 emoji.

×   Odnośnik został automatycznie osadzony.   Przywróć wyświetlanie jako odnośnik

×   Przywrócono poprzednią zawartość.   Wyczyść edytor

×   Nie możesz bezpośrednio wkleić grafiki. Dodaj lub załącz grafiki z adresu URL.

Ładowanie
×
×
  • Dodaj nową pozycję...