Hello !
Et voilà, ça recommence. Mon Windows 10 foirait, j'espérais un souci d'installation corrompue mais ça semble plus lourd.
 
Bref, config :
Phenom X4 980 black ed.
Carte mère M4A785TD
2*2 Go RAM PC12800
Video GF 750 Ti
HDD1 Samsung 850 Evo (système)
HDD2 WD Caviar Blue 1 To (stockage)
Alim Corsair 400 W
Boîtier Coolermaster.
 
RAS sur boîtier alim et HDD2 je pense.
 
Les symptômes sont des plantages aléatoires avec blue screen ("page fault in non paged area", "system service exception", "faulty hardware corrupted page"...), voir écran noir au reboot mais quand même de l'activité HDD2 audible.
Hier soir ma sauvegarde Shadow of the Tomb Raider a été corrompue et perdue, ce matin en rallumant l'ordi il est à l'heure d'hier soir et les icônes du bureau on presque toutes disparu...
 
Hier, 1h de memtest n'a ramené aucune erreur, le HDD1 est en statut Smart bon.
 
Je fais quoi maintenant ?

Bonjour,
 
Peut être la CM, j'ai déjà eu un os HS au démarrage alors que la veille j'ai arrêté la machine normalement.
 
Après changement plus de souci.

 
Un coup de whocrashed ?? Allez...
 
On Mon 10/12/2018 23:40:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121018-6375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1130)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF806226FD17F, 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 Mon 10/12/2018 23:40:14 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!KeRegisterNmiCallback+0x2AE)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF806226FD17F, 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 Mon 10/12/2018 18:36:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121018-6156-01.dmp
This was probably caused by the following module: hardware.sys (hardware)  
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80662CA25B3, 0xFFFFFC8C57928FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.  
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_SERVICE_EXCEPTION
 
 
 
On Mon 10/12/2018 18:35:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121018-6593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1130)  
Bugcheck code: 0x50 (0xFFFFF805342AA97A, 0x10, 0xFFFFF805342AA97A, 0x0)
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 Mon 10/12/2018 18:33:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121018-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1130)  
Bugcheck code: 0xD1 (0xFFFFF8039EBC3674, 0x8, 0x8, 0xFFFFF8039EBC3674)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.  
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 Mon 10/12/2018 18:27:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121018-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B1130)  
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x21E, 0x24907D3B5E0, 0xFFFFE481AD16C000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.  
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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.  
 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
6 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.

certes, mais pour retrouver une carte compatible ça va être chaud non ?

Titre très explicite sur la problématique

Change le titre.
Fais une mise à jour du bios.
Réinstalle Windows mais avec aucun logiciel et une seule barrette de ram.
Si cela fonctionne tu remets une barrette de ram.
Si c'est ok tu remets les pilotes et logiciels progressivement.
Il est probable que tu dois avoir un pilote ou software incompatible.
Utilises des points de restauration pour revenir en arrière s'il y a un écran bleu.
N'hésite pas à créer des points de restauration manuellement.
Vérifie aussi le refroidissement du PC.

Merci !
Pour le refroidissement RAS. Le dernier BIOS date de 2015 et c'est le mien.
 
Quand mes soucis ont commencé j'ai tenté une réinstall sans rien virer (réparation) et ça n'a pas dû arranger les choses... D'autant que j'avais laissé le PC connecté au réseau. Je me suis souvenu que je c'était une très très mauvaise idée...
Là j'ai sauvegardé ce que je voulais, formaté C: et je réinstalle hors du réseau, proprement.
Je vous tiens au jus !
 
EDIT : IRQ less or not equal, pendant l'installation... Pas bon ça !

Teste avec une barrette de RAM, et si ça bug l'autre, et ainsi de suite. Possible qu'une barrette ou plusieurs aient rendu l’âme.

IRQ less or not equal, c'est soit un périphérique ou ses drivers foutant la grouille (a tester un par un en commençant par démarrer avec le strict minimum), soit c'est au niveau de la carte mère, comme ça a été évoqué.

Salut !
Bon, ça n'a pas l'air d'être la RAM : j'ai fait 2 passes de Memtest86 (v4.3.7)  avec chaque barrette de RAM plus 2 passes avec la paire, et RAS...
Pour les périphériques, je fais comment ? Je n'utilise qu'une carte vidéo externe (750 Ti) et le reste est intégré à la carte mère...

Tu peux essayer sans si ta carte mère gère le GPGPU du processeur.
Sinon c'est mauvais signe car ça incriminerai ta carte mère.