Bonjour ,
Ma nouvelle config :
- Processeur amd ryzen 2700X
- Carte mère gigabyte X470 aorus gaming 7 wifi (rev. 1.0) => https://www.gigabyte.com/Motherboar [...] -rev-10#kf
- Mémoire gskill Flare X Series 16 Go (2x 8 Go) DDR4 2400 MHz CL15 ( ref : F4-2400C15D-16GFX ) => https://www.ldlc.com/fiche/PB00225339.html
( mémoire indiquée comme étant compatible avec la carte mère sur le site de gskill , mais ce n'est pas clair il y a plusieurs listes de compatibilité suivant le processeur installé sur la carte mère )
- Alim : Seasonic PRIME Ultra 650 W Titanium => https://www.ldlc.com/fiche/PB00235078.html
- Carte graphique : gigabyte radeon HD 6950
- radiateur processeur : noctua NH-C14 => https://www.legitreviews.com/noctua [...] eview_1531
Maintenant les problèmes :
-Divers problèmes d'instabilité , avant mise à jour du bios .
Je commence directement à la suite de cette mise à jour du bios pour détailler les ennuis et tests .
- Mise à jour du bios sur la carte mère avec une clé usb au démarrage de l'ordi , ancienne version F3 ... , nouvelle version F6 .
- Ordi plante encore pendant l'installation de win10 avec la clé usb acheté avec les pièces de l'ordi ( version 1803 ) , ainsi qu'avec une clé usb contenant la nouvelle version ( version 1809 )
- Re clear cmos ( le bios 1 et le bios de sauvegarde )
- Lancement mentet version 7.5 , 30 passes .
- Le matin j'allume l'écran de l'ordi pour voir à quel endroit en est memtest , rien à l'écran , l'ordi à planté pendant le test ... avec redémarrage .
- utilisation du diagnostic mémoire de win10 ... reste bloqué à 21%
- stress system mémory de aida64 pendant 19h36 .
- ensuite plusieurs redémarrage à cause d'écran bleu ( mise à jour pilote , lancement de cpuz , etc ) , en voici la liste faite avec whocrashed :
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-4MMKTCB
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\Windows
Hardware: X470 AORUS GAMING 7 WIFI, Gigabyte Technology Co., Ltd., X470 AORUS GAMING 7 WIFI-CF
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 17124474880 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sat 05/01/2019 23:23:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010619-15343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8070FFD7837, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/01/2019 23:23:25 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!memset+0x3288F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8070FFD7837, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 05/01/2019 23:09:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010519-15953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFF988E62081428, 0xFFFFFB066D7C3AC0, 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 Sat 05/01/2019 18:38:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010519-14921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8041D366434, 0xFFFFD48AE927CB10, 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 Sat 05/01/2019 18:34:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010519-14593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x7F (0x8, 0xFFFFAD809AF1C270, 0xFFFFC48C3011E8E8, 0xFFFFF8045E1D0504)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sat 05/01/2019 18:30:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010519-14640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x50 (0xFFFF9F8F0E442010, 0x0, 0xFFFFF8001B0D7D0B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Et partie 2 :
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-4MMKTCB
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\Windows
Hardware: X470 AORUS GAMING 7 WIFI, Gigabyte Technology Co., Ltd., X470 AORUS GAMING 7 WIFI-CF
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor AMD586, level: 23
16 logical processors, active mask: 65535
RAM: 17124462592 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 08/01/2019 13:46:11 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010819-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0xA (0x112DD384, 0x2, 0x0, 0xFFFFF8027CD18EA3)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
On Tue 08/01/2019 13:46:11 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+0x7EA9)
Bugcheck code: 0xA (0x112DD384, 0x2, 0x0, 0xFFFFF8027CD18EA3)
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.
On Tue 08/01/2019 13:44:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010819-5015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x1A (0x41201, 0xFFFFF98122E25DC8, 0x8100000291EDE847, 0xFFFFA38F3F3C4930)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
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. This problem might also be caused because of overheating (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 08/01/2019 13:30:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010819-5640-02.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8033263A756)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8033263A756, 0xFFFFD7074F87CAD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 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 Tue 08/01/2019 13:27:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010819-5687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1B40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807408D3BA2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\010819-5546-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
La suite :
- Test barrette mémoire A sur port DDR4-4 , 2 fois de suite le diagnostic mémoire ( tous fait en test étendus y compris ceux plus haut dans mon message ) ne se lance pas au démarrage de l'ordi , à noter qu'après une installation neuve , ça marche , mais une fois , il doit y avoir un problème peut être car je suis obligé de redémarrer à cause du blocage à 21% .
- memtest lancé le 8-1 à 15h44 , 6 passes sur 30 sont bonnes le soir , rallumage de l'écran le matin , que dalle écran noire , l'ordi à surement encore planté la nuit et à redémarré ...
- Test carte graphique avec OCCT , temp 57° pas de plantage , stress test du processeur avec aida64 ( stress cpu - fpu - cache ) temp 60.4°
- réinstall win 10 , pas de plantage
- changement de barrette mémoire , j'enlève la barrette mémoire A , je met la barrette mémoire B
- réinstallation de win 10 , pas de plantage .
- ce soir , lancement de memtest 1 passe sur 30 est ok , mais je suis déjà sur qu'il va y avoir une connerie ...
C'est vraiment chiant , surtout que par rapport à l'ordi de mon neveu , là , je ne sais même pas ce qu'il se passe , memtest ne pouvant faire les 30 passes , et le test mémoire de win10 étant un désastre ...
Je crois que je suis encore bien dans le caca avec cet ordi ...
Voilà , je sais déjà que demain ou plus tard je mettrais un message pour annoncer un truc qui déconne , mais peut être qu'avec ce que j'ai déjà écrit quelqu'un aura une piste pour le composant causant ces ennuis ( ou une confirmation que la mémoire est encore en cause ) ?
Tant que j'y pense , y a t'il un programme du genre memtest qui marche sous windows ?
Merci.
Message édité par tyrannouille le 19-01-2019 à 14:44:04
FORUM HardWare.fr
