Bonjours à tous, je post ce topic car j'ai un problème qui persiste depuis 1mois et qui me les brises ...
C'est un écran bleu je ne sais ni pour qui pourquoi comment il est arrivé, j'avais déjà quelque soucis avec mon ordi ( écran qui s'éteignait puis se rallumait ) mais jamais jusqu'à l'écran bleu
J'ai déjà posté sur plusieurs forum il y a 1 moi de cela sans réponse ...
Je vous copie colle donc le message posté
Bonjours à tous,
En ce moment j'ai un petit problème.. un gros plus tôt : les écrans bleus.
J'ai donc utiliser bitdefender et fait une analyse antivirus, qui a révélé avoir 8 virus, et 7 ont été corriger, seul celui-ci persiste :
http://www.e-loader.net/i/kgXWLzxkkA.html
( Oui c'est bien lui même si ce n'est pas une photo de la fin de l'analyse )
Je ne sais pas si c'est normal et, si c'est lui qui est à l'origine des mes écrans bleus ...
Voici une photo de mes écrans bleu ( désolé pour le flash ) :
http://www.e-loader.net/i/dfyKrlJT5x.html
http://www.e-loader.net/i/BMoMG9DRmh.html
Je tiens à préciser que l'écran bleu intervient après le lancement d'un jeu comme Call of Duty Battlefield etc .... sinon je peux naviguer sur internet sans aucun ( ou presque ) problème
Et donc là plusieurs questions : Si c'est ce fameux fichier lsass ( ou isass ? ) comment je pourrais faire pour le réparer ? Si ce n'est pas lui qui en est la cause ? Comment je peux réparer mon PC sans avoir à faire trop manipulations ?
Merci d'avance de vos réponses, et merci ( s'il vous plait ^^ ) d'être clair, car je suis peu doué en informatique ( OUHHHH BLASPHÈME ! )
Cordialement
Savran
J'ai chercher sur le forum si il y avait des cas similaire et j'ai vu qu'on conseiller d'utiliser "whocrash"
Voici ce qu'il ma donné :
System Information (local)
--------------------------------------------------------------------------------
computer name: UTILISATEUR-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2310 CPU @ 2.90GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6423584768 total
VM: 2147352576, free: 1940340736
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 02/06/2013 07:54:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1B775D)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA800BDFA060, 0x0)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 311.06
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 311.06
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_VERIFIER_DETECTED_VIOLATION
On Sun 02/06/2013 07:32:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-47127-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFFA80099D8060, 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 Sun 02/06/2013 07:21:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-20139-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xC4 (0x91, 0x2, 0xFFFFF800033FFCC0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 311.06 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.