Problème écran bleu par WER-66378-0.sysdata.xml

Bonjour,
Mon ordinateur (un Asus X53SD-SX720V) crash très souvent en écran bleu et c'est toujours lorsque je suis à la facultélorsque je prend mes cours sur word. Je pense que c'est à cause du fait que je suis connecté au wifi de la fac, un hotspot. c'est très énervant car je perd souvent une partie de mon court (heureusement qu'il y a des minisauvegardes auto)
j'avais eu un problème avec igdkmd64.sys mais la c'est résolu mais maintenant c autre chose.
ma configuration est:
- Windows 7 édition familiale prémium service pack 1
- Nvidia geforce 610M 2GB
- intel inside core i7-2670Qm CPU@2.20GHz

j'ai eu ça pour l'erreur de plantage de windows:
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000406F8
BCP4: FFFFF880053BB92D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\121812-22838-01.dmp
C:\Users\xxxx\AppData\Local\Temp\WER-66378-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


voici ce que whocrashed a mit:

On Tue 18/12/2012 10:09:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121812-24429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 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 Tue 18/12/2012 10:09:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 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 Tue 18/12/2012 09:39:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121812-23228-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 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 Tue 18/12/2012 08:44:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121812-24991-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF80003407CC0, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
The driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. 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 17/12/2012 14:28:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121712-22230-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 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.



comme vous pouvez le voir c'est assez rapprocher dans le temps pendant mon cours... pouvez vous m'aider please?
merci d'avance