Blue Screen sous Windows 7

Bonjour à tous !

Je suis actuellement sous windows 7 version intégrale et depuis quelques jours mon PC fait un écran bleu et reboot à chaque fois ...

Voici le message erreur lorsqu'il redemarre :

Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.256.1
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF96000114A92
BCP3: FFFFF880088B65D0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\101615-32105-01.dmp
C:\Users\Pylou\AppData\Local\Temp\WER-49811-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt


J'ai essayé de regarder si je pouvais résoudre cela par moi même avec notre ami Google mais rien n'y fait ...

-J'ai enlevé la poussière dans ma tour ... Aucun changement
-J'ai vérifié ma RAM ... Aucune RAM HS
-J'ai mis à jour le pilote de ma carte graphique ... Aucun changement
-J'ai fait allé CCleaner et nettoyé mon PC ... Aucun changement
-J'ai même changé d'antivirus car quelqu'un avait la même chose avec AVAST ... mais aucun changement ...

J'ai donc finalement installé Whocrashed comme suggéré sur pas mal de forum et voilà son rapport :


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 15/10/2015 09:57:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101515-23665-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4A92)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000164A92, 0xFFFFF8800AE37FB0, 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 Thu 15/10/2015 09:57:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x1072)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000164A92, 0xFFFFF8800AE37FB0, 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 14/10/2015 19:10:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101415-42822-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4A92)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000104A92, 0xFFFFF8800A8F9680, 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
--------------------------------------------------------------------------------

3 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 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.

Étant incapable de résoudre ce problème très embêtant et n'étant pas fort en Anglais , j'espère qu'une bonne âme charitable pourra m'aider !

En vous Remerciant !

Pylou59