Reprise du message précédent :
au passage :  
un problème récurent avec les rx460 OC (over clockées donc) dans différents forums.
elle crashe, et le correctif utilisé c'est :  
1) utiliser un utilitaire pour downclocker la fréquence ram GDDR de la carte d'au moins 20%, tester, puis monter de 5% et recommencer tant que ça marche, en testant à chaque fois plusieurs jours / plusieurs jeux.
2) certaines version des pilotes AMD bloquent (ou ne tiennent pas compte, j'ai pas trop lu en détail) la freq des mémoires, donc avec certaines versions de pilotes : ça passe, avec d'autres version ça ne passe pas.
 
tu peux faire une recherche google RX460 crash, il y a quand même pas mal de remontées de pb

Je désespère
 
Depuis, j'ai réinstallé win10 3 fois. Cette histoire me rend fou !!!
 
J'installe windows, j'installe chrome, je vais chez MSI chercher les drivers de ma carte mère et chez Intel chercher le driver du processeur. J'ai une seule barrette de RAM qui est testée, un SSD M.2 et un clavier/souris lambda... Rien d'autre
 
Je ne vois pas ce que je peux faire de plus si ce n'est remplacer les composants 1 par 1 pour tester
 
 
 
 
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: MS-7A74, MSI, B250M PRO-VD (MS-7A74)
CPU: GenuineIntel Intel(R) Pentium(R) CPU G4560 @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8476835840 bytes total
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Thu 25/05/2017 17:46:20 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-3218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x109 (0xA3A00BDEC6CF34E9, 0xB3B71865194D3244, 0xFFFFF8002100F000, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
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 25/05/2017 17:46:20 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)  
Bugcheck code: 0x109 (0xA3A00BDEC6CF34E9, 0xB3B71865194D3244, 0xFFFFF8002100F000, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.  
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 25/05/2017 17:18:42 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-3203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x139 (0x3, 0xFFFFBE81EA986710, 0xFFFFBE81EA986668, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 25/05/2017 17:01:52 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-3000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x50 (0xFFFFB7886449419D, 0x0, 0xFFFFF803FB86C0EA, 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.  
 
 
 
On Thu 25/05/2017 16:55:36 your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-2921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0xA (0x80D0, 0x2, 0x0, 0xFFFFF801C9317C2B)
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 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.