Salut la compagnie.
J'ai depuis plusieurs jours des crashs / BSOD / retours bureau en jeu et sur Chrome, peu importe le jeu (ici, Stellaris et Cities ; Skylines) et généralement au bout d'une dizaine de minutes. Après différents tests détaillés en dessous, j'ai d'abord formaté mon ordinateur ce qui a réglé le souci pendant environ une demi-heure. J'ai ensuite réinstallé mon ancienne GTX 970, en supprimant bien le driver geforce avec DisplayDriverUninstaller, ce qui n'a rien changé non plus.
Les BSOD sont plutôt variés, allant de Machine_Check_Exception à NVLDDMKM.sys.
Je rajouterai les différentes erreurs dans le thread au fur et à mesure.
MA CONFIG :
CPU : i5 3570K overcloké à 4,4ghz (2012, OC en 2016)
CM : Gigabyte GA-Z77-D3H (2012)
Ram : 4*4go DDR3 (deux paires différentes de Kingston achetées en 2012 et 2016)
Ventirad : Thermaltake Contac 29 BP (2012)
CG : KFA2 GTX 1070 EXOC Sniper 8bg (2016) puis pour tester MSI GTX 970 gaming 4gb (2015 ?)
SSD système : Samsung 830 256go (2012)
HDD : Seagate Barracuda 2TO (2017)
Alim : LDLC BG-500 (2012)
Boîtier : Fractal Design Define R4 (2017)
DIAGNOSTICS :
OCCT CPU : Des erreurs apparaissent même sur un test court de 10 minutes. Le test se conclut parfois sur un BSOD et un reboot.
Memtest : deux passes complètes, tout est OK
HWmonitor : températures normales
CrystalDiskInfo : les deux disques durs sont OK
Whocrashed :
Crash Log de Stellaris :
On Sat 08/12/2018 07:47:44 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120818-4656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x50 (0xFFFFAE070D482890, 0x11, 0xFFFFAE070D482890, 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 Sat 08/12/2018 07:47:44 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+0x508A1)
Bugcheck code: 0x50 (0xFFFFAE070D482890, 0x11, 0xFFFFAE070D482890, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Fri 07/12/2018 17:18:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120718-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80012B44E0D, 0xFFFF878B162B2820, 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 Fri 07/12/2018 16:50:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120718-4984-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF804221C9F4A, 0xFFFFE10F8CB29BE8, 0xFFFFE10F8CB29430)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Conclusion
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
hardware.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
Dans tous les cas, merci d'avance.######## EXCEPTION: 0xC0000005 at address: 0x00000000: ACCESS VIOLATION
Version: Unknown Version
12/07/18 13:36:08
(-nosymbols- PC == 0)
######## EXCEPTION: 0xC0000005 at address: 0x013B0385: ACCESS VIOLATION write attempt to address 0x0134A801
Version: Unknown Version
12/07/18 13:43:54
######## EXCEPTION: 0xC0000005 at address: 0x013B0385: ACCESS VIOLATION write attempt to address 0x0134A801
Version: Unknown Version
12/07/18 13:51:30
######## EXCEPTION: 0xC0000005 at address: 0x00000000: ACCESS VIOLATION
Version: Unknown Version
12/07/18 14:04:45
(-nosymbols- PC == 0)
######## EXCEPTION: 0xC0000005 at address: 0x0A20FC38: ACCESS VIOLATION
Version: Unknown Version
12/07/18 20:16:16
SymGetLineFromAddr(): GetLastError = 126
Edit : Hearts of Iron IV plante de la même façon que Stellaris.