Salut :)

Depuis plusieurs semaines j'ai un problème: mon pc s'éteint tout seul, écran bleu avec du texte qui s'affiche (j'ai généralement pas le temps de lire parce que le pc s'éteint et se rallume au bout d'une ou 2 secondes).

J'ai regardé avec le logiciel Whocrashed, manifestement c'est un (ou des) pilotes qui déconnent.

Tout à l'heure j'ai eu ça :

Citation :


Que faire pour réparer (?) le pilote afin de résoudre le problème d'écran bleu intempestif?

Merci beaucoup d'avance :)

Bonjour,

Merci de ta réponse. C'est windows vista. Jusqu'à présent j'avais pas eu de problèmes de ce genre :(

Bonjour,

Si le problème provient d'une barrette mémoire, et que tu en as plusieurs sur ton PC, tu peux aussi essayer de faire fonctionner ton PC avec une seule barrette !!!

Si tu as encore le problème avec une, et pas avec une autre, tu as trouvé la coupable

Sans résultat > analyse avec "Memtest"

@+ ag

Salut

Je viens de faire le test de la RAM avec Memtest, mais il a rien trouvé.
C'est donc (je suppose) un problème de pilotes. Comment faire pour le résoudre, du coup?

Merci d'avance :)

Bonjour,

Vas sur le site de "touslesdrivers.com", acceptes l'installation d'un programme qui va analyser ta configuration, et te donner la liste des pilotes qui ne sont pas à jour > Cliques sur ce lien

Tu peux tenter également un redémarrage avec la dernière bonne configuration connnue > F8, ou une restauration à une date antérieur au problème

@+ ag

Bonjour,

Merci de ta réponse. En fait je vais sur le site dont tu as donné le lien, ça me donne une liste de plein de mes matériels et de leurs pilotes, ceux installés et ceux disponibles... je dois télécharger tous les pilotes disponibles en question???

merci

Bonjour,

Il faudrait que tu télécharges et remplaces seulement celui qui pause problème, mais Whocrashed t'a dit du quel il s'agit ???
je ne connais pas ce logiciel, donc je ne connais pas ses possibilités !!!

Tu as mis à jour récemment le pilote qui pause problème

Si non, je ne vois pas pourquoi un pilote qui fonctionnait bien, se mettrait tout à coup à poser problème, curieux

Si non commences par celui de la carte graphique, et fais un essai

Sans résultat, passes aux pilotes de la carte mère, ect.........

Avant, rien ne t'empêches de tenter la dernière bonne configuration connue > touche F8 > essai

Sans résultat > restauration de ton système à une date antérieur

@+ ag

Salut et merci de ta réponse.

Je te copie-colle le rapport de Whocrashed:

On Sun 15/01/2012 20:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011512-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57CD7)
Bugcheck code: 0x1 (0xFFFFFFFF82E4DEF2, 0x0, 0xFFFFFFFFFFFF0000, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 15/01/2012 20:35:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!ZwQueryLicenseValue+0xF37)
Bugcheck code: 0x1 (0xFFFFFFFF82E4DEF2, 0x0, 0xFFFFFFFFFFFF0000, 0x0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 15/01/2012 14:45:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011512-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE56F4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D2A6F4, 0xFFFFFFFFAE1FFB54, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 which cannot be identified at this time.


On Sun 15/01/2012 03:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011512-02.dmp
This was probably caused by the following module: msrpc.sys (msrpc+0x611B)
Bugcheck code: 0xC2 (0x7, 0x110B, 0xA775C0, 0x905A4D)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
Bug check description: This indicates that the current thread is making a bad pool request.
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 which cannot be identified at this time.


On Sun 15/01/2012 01:41:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE56F4)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D196F4, 0xFFFFFFFFB336288C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 which cannot be identified at this time.


On Sat 14/01/2012 00:39:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini011412-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBEFF2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CF3311, 0xFFFFFFFFA9B44B6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 08/01/2012 00:11:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini010812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x57CD7)
Bugcheck code: 0x1 (0xFFFFFFFF9913E98B, 0x0, 0xFFFFFFFFFFFF0000, 0x0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 07/01/2012 02:10:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini010712-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x19FFF)
Bugcheck code: 0x24 (0x1904AA, 0xFFFFFFFF9E50C4B0, 0xFFFFFFFF9E50C1AC, 0xFFFFFFFF8B5104AC)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.


On Wed 04/01/2012 11:56:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini010412-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBEFF2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82CFC311, 0xFFFFFFFFAB5ABB6C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 23/12/2011 00:38:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini122311-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xA216)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D21311, 0xFFFFFFFF9DE94A64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



Comment réparer les pilotes qui déconnent?... J'ai déjà essayé avec le Recovery Disk de réparer ce qui déconnait, mais ça n'a rien changé. Mon pc a encore buggé tout à l'heure, et hier soir aussi.
Merci d'avance pour toute aide...