Bonjour a toutes et a tous,  
J'ai un problème assez récurant, je m'explique, j'ai on va dire en moyenne un BlueScreen par semaine et j'ai beau mettre mes pilotes a jour et autre rien ne change.. Ils apparaissent a n'importe quel moment, quand je suis sur le naviguateur, quand je quitte un jeu. Malheureusement je sais pas trop quoi faire, j'espère que vous seriez m'éclairez.  
 
J'ai installé Who Crashed et analysé :  
System Information (local)  
--------------------------------------------------  
------------------------------  
 
 
computer name: ANDREA-PC  
windows version: Windows 7 , 6.1, build: 7600  
windows dir: C:\Windows  
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-K  
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6  
4 logical processors, active mask: 15  
RAM: 8525926400 total  
VM: 2147352576, free: 1946566656  
 
 
 
 
--------------------------------------------------  
------------------------------  
 
Crash Dump Analysis  
--------------------------------------------------  
------------------------------  
 
 
Crash dump directory: C:\Windows\Minidump  
 
Crash dumps are enabled on your computer.  
 
On Wed 27/08/2014 00:27:22 GMT your computer crashed  
crash dump file: C:\Windows\Minidump\082714-23852-01.dmp  
This was probably caused by the following module: win32k.sys (win32k+0xC6483)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000196483, 0xFFFFF8800A7DC030, 0x0)  
Error: SYSTEM_SERVICE_EXCEPTION  
file path: C:\Windows\system32\win32k.sys  
product: Système d’exploitation Microsoft® Windows®  
company: Microsoft Corporation  
description: Pilote Win32 multi-utilisateurs  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Wed 27/08/2014 00:27:22 GMT your computer crashed  
crash dump file: C:\Windows\memory.dmp  
This was probably caused by the following module: win32k.sys (win32k!memset+0x863)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000196483, 0xFFFFF8800A7DC030, 0x0)  
Error: SYSTEM_SERVICE_EXCEPTION  
file path: C:\Windows\system32\win32k.sys  
product: Système d’exploitation Microsoft® Windows®  
company: Microsoft Corporation  
description: Pilote Win32 multi-utilisateurs  
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
 
--------------------------------------------------  
------------------------------  
 
Conclusion  
--------------------------------------------------  
------------------------------  
 
 
2 crash dumps have 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 actually 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.  
 
 
 
 
Voila, merci d'avance pour vos aides.    

up

Bonsoir HueeyProd,
 
les crash de win32k.sys sont significatifs de barrettes de RAM défectueuses.
 
Creuse dans ce sens.
 
++

Ok merci, donc je vais avoir besoin de memtest pour pouvoir savoir ce qui ne va pas ?