BlueScreen MEMORY_MANAGEMENT - RAM-OK

Bonjour,

Depuis quelques jour, mon pc se fige, ou m'affiche un bluescreen.
La première fois le bluescreen était composé uniquement de carrés blanc, pas de lettres et chiffres. Maintenant j'ai tout ce qu'il faut, je vous post le rapport WhoCrashed.

J'ai laissé un memtest toute la nuit, 23 pass, 0 erreurs. Le diagnostique HP qu'on peux lancer au boot = tout ok - crystaldisk = Tout bleu OK.

J'ai pensé à la chaleur:
Aida64, burn cpu+ram+cg+hdd, température OK (, avant de figé au bout de 15/20min.)
Capot ouvert, au repos, se fige entre 10 et 30 minutes.
Windows 8.1 installé + carte graphique changé hd 5450 passive + Pate thermique cpu, il y a 10 mois, aucun problème depuis 10 mois donc ...

Je n'ai rien fait de particulier avec, pas d'ajout de matériel ni programme, je vais très peu sur internet, c'est surtout pour excel.
D’ailleurs excel ne s'ouvre plus, il a planté pendant son utilisation, depuis j'ai un message d'erreur quand j'essaie d'ouvrir excel, je le réinstallerais.

Le rapport WhoCrashed me dit:
Un pilote tiers a été identifié comme la cause probable de cette erreur du système.
Mais il ne me précise pas lequel ...

Le rapport WhoCrashed:


System Information (local)
--------------------------------------------------------------------------------

Computer name: PC
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: KQ528AA-ABF m9169.fr, HP-Pavilion, ASUSTeK Computer INC., Benicia
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3220492288 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 03/08/2016 15:36:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF58010804000)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x64B43, 0x64B4500C9687)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
A third party driver was identified as the probable root cause of this system error.
Google query: MEMORY_MANAGEMENT



On Tue 26/07/2016 12:30:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072616-21234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF58010804000, 0x22D5, 0x362700045AB)
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. 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.



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

2 crash dumps have been found and analyzed.
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.



Merci de votre aide :) !