Ecran bleu faulty hardware corrupted page

Bonjour à tous,

Depuis quelques temps, mon PC sous W10 me faisait des écrans bleu, sans raison particulière identifiée.

Après plusieurs tentatives de réparation infructueuse, j'ai décidé de restaurer w10 aux paramètres d'usine. Aucun nouvel écran bleu pendant 3 semaine, jusque ce matin :

Voici le rapport Who crashed :

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 09/08/2017 08:48:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\080917-35765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x4C8, 0x8A68680, 0xFFFFC781A0038000)
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

One crash dump has 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.


J'avais déjà fait avant de reboot un memtest au démarrage, sans erreur détectée.

La petite chose qui m'interpelle est ma RAM (d'origine): une barrette soudée de 4GO et une autre de 2GO...je pensais qu'il était conseillé d'avoir deux barrettes de même capacité.


Merci d'avance pour votre aide
Bonne journée

Maxime