Ecrans bleus sous XP

[Stéphane]

Bonjour,

N'ayant pas trouvé de réponse auprès d'un professionnel ayant pignon sur rue, je viens de découvrir votre site et je m'en remets à vous.

Depuis début Octobre, mon système est touché par divers écrans bleus, surtout lors de lecture de clip vidéo sur YouTube ou au démarrage de Windows et encore lors de sortie de mise en veille.

Tous mes drivers sont à jours et ce matin, j'ai installé le logiciel WhoCrashed dont voici le rapport :

System Information (local)
--------------------------------------------------------------------------------

computer name: MON_PC
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146611200 total
VM: 2147352576, free: 2050170880




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 03/11/2012 09:11:37 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFC4BFB980)
Bugcheck code: 0x50 (0xFFFFFFFFC4BFB980, 0x0, 0xFFFFFFFFB30B960A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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.
Google query: PAGE_FAULT_IN_NONPAGED_AREA



On Sat 03/11/2012 08:25:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110312-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x4D9F9E, 0xFFFFFFFFF789E750, 0xFFFFFFFFF789E44C)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread 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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Thu 01/11/2012 09:15:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini110112-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x90900)
Bugcheck code: 0x100000EA (0xFFFFFFFF890799F0, 0xFFFFFFFF89852658, 0xFFFFFFFFF78B6CBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 301.42
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 301.42
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 301.42 , NVIDIA Corporation).
Google query: NVIDIA Corporation THREAD_STUCK_IN_DEVICE_DRIVER_M



On Tue 30/10/2012 19:13:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini103012-03.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x26A633)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xF1CBD11, 0xFFFFFFFFB2954C04, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 301.42
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 301.42
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.
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 301.42 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Tue 30/10/2012 18:36:59 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini103012-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6070A)
Bugcheck code: 0x4E (0x99, 0x3FFFFFF, 0x4, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 30/10/2012 15:59:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini103012-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x19E72B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBD1B072B, 0xFFFFFFFFB3083A58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 301.42
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 301.42
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.
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 301.42 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Mon 29/10/2012 20:17:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102912-03.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x648D)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFF8B, 0x0, 0xFFFFFFFFF74A548D, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 Mon 29/10/2012 17:55:32 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102912-02.dmp
This was probably caused by the following module: cmdhlp.sys (cmdhlp+0x804)
Bugcheck code: 0x100000D1 (0x2CFF0, 0x2, 0x0, 0xFFFFFFFFF77BF804)
Error: CUSTOM_ERROR
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: cmdhlp.sys .
Google query: cmdhlp.sys CUSTOM_ERROR



On Mon 29/10/2012 17:52:56 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102912-01.dmp
This was probably caused by the following module: cmdguard.sys (cmdguard+0x1D1D2)
Bugcheck code: 0x10000050 (0xFFFFFFFFFFFFFFF0, 0x0, 0xFFFFFFFF804EA590, 0x0)
Error: CUSTOM_ERROR
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: cmdguard.sys .
Google query: cmdguard.sys CUSTOM_ERROR



On Sun 28/10/2012 21:38:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-04.dmp
This was probably caused by the following module: sr.sys (sr+0x362E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFFF749062E, 0xFFFFFFFFABDB8B10, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\sr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de filtre de système de fichiers pour la restauration du système
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 that cannot be identified at this time.



On Sun 28/10/2012 17:14:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2B61)
Bugcheck code: 0x1000000A (0x4, 0x1C, 0x0, 0xFFFFFFFF804D9B61)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
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 28/10/2012 15:10:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-02.dmp
This was probably caused by the following module: inspect.sys (inspect+0x25A7)
Bugcheck code: 0x100000D1 (0x6142AA21, 0x2, 0x0, 0x6142AA21)
Error: CUSTOM_ERROR
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: inspect.sys .
Google query: inspect.sys CUSTOM_ERROR



On Sun 28/10/2012 08:56:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102812-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Sat 27/10/2012 20:31:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102712-11.dmp
This was probably caused by the following module: cmdhlp.sys (cmdhlp+0x804)
Bugcheck code: 0x100000D1 (0xE6258, 0x2, 0x0, 0xFFFFFFFFF778F804)
Error: CUSTOM_ERROR
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: cmdhlp.sys .
Google query: cmdhlp.sys CUSTOM_ERROR



On Sat 27/10/2012 18:18:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102712-10.dmp
This was probably caused by the following module: cmdhlp.sys (cmdhlp+0x804)
Bugcheck code: 0x100000D1 (0xFFFFFFFFD80F6724, 0x2, 0x0, 0xFFFFFFFFB7790804)
Error: CUSTOM_ERROR
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: cmdhlp.sys .
Google query: cmdhlp.sys CUSTOM_ERROR




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 15 are included in this report. 6 third party drivers have 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:

nv4_mini.sys (NVIDIA Windows XP Miniport Driver, Version 301.42 , NVIDIA Corporation)
kmixer.sys (Kernel Mode Audio Mixer, Microsoft Corporation)
nv4_disp.dll (NVIDIA Windows XP Display driver, Version 301.42 , NVIDIA Corporation)
inspect.sys
cmdguard.sys
cmdhlp.sys

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.


En précision, j'ai également des plantages de Windows (sablier) au démarrage pas d'autre choix que re-démarré.

J'ai remis les drivers Nvidia (306.81 vers 301.42) à une date antérieure aux écrans bleus mais rien n'y fait.

Je compte sur vous.

Merci.

[bernard53]

Bonjour
Dans un premier temps vérifies tes barrettes mémoires.
http://www.commentcamarche.net/download ... -memtest86

2-désinstalle complètement ta carte Nvidia puis nouvelle installe propre. Possible que tu as déjà fait cela.

3-ceci pour voir plus.

* Télécharge >> OTL <<sur ton bureau.

* Fait un double-clic sur l'icône d'OTL pour le lancer
/!\ pour Vista/Seven fais un clic-droit sur l'icône d'OTL et choisis "Exécuter en tant qu'administrateur"

* Assure-toi d'avoir fermé toutes les applications en court de fonctionnement.

* Quand la fenêtre d'OTL apparaît, assure toi que dans la section "Rapport" (en haut à droite) la case "Rapport minimal " soit cochée.

* Copies et colles le contenue de cette citation dans la partie inférieure d'OTL " Personnalisation"

HKLM\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl|FEATURE_BROWSER_EMULATION /rs
HKEY_USERS\.DEFAULT\Software\Microsoft\Internet Explorer\Main\FeatureControl|feature_enable_ie_compression /rs
HKEY_USERS\S-1-5-18\Software\Microsoft\Internet Explorer\Main\FeatureControl|feature_enable_ie_compression /rs
hklm\software\clients\startmenuinternet|command /rs
hklm\software\clients\startmenuinternet|command /64 /rs
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers /s
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 /s
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc /s
%temp%\smtmp\1\*.* /s
%temp%\smtmp\2\*.* /s
%temp%\smtmp\4\*.* /s
nslookup http://www.google.fr /c
SAVEMBR:0
NetSvcs
%systemroot%\system32\drivers\*.sys /lockedfiles
msconfig
safebootminimal
safebootnetwork
activex
drivers32
%systemroot%\*. /mp /s
%systemroot%\system32\*.dll /lockedfiles
%systemroot%\Tasks\*.job /lockedfiles

* Cliques sur l'icône "Analyse" (en haut à gauche) .
* Laisse le scan aller à son terme sans te servir du PC
* A la fin du scan un ou deux rapports vont s'ouvrir "OTL.Txt" et ( ou ) "Extras.Txt"( dans certains cas).
* Copie et colle le ou les rapports dans ta réponse stp...
* Au cas où, tu peux les retrouver dans le dossier C:\OTL ou sur ton bureau en fonction des cas rencontrés
Mets le rapport ici car il prend bien de la place.
http://cjoint.com/
ou.
http://www.1fichier.com/

[Stéphane]

Bonjour Bernard,

J'avais commencé les tests que tu m'as proposés et des amis m'ont envoyé un technicien en Informatique qui est venu constater et il a trouvé la réponse en inspectant ma tour : 3 condensateurs de ma carte-mère sont gonflés et le problème vient de là.

Donc maintenant, je sais ce qu'il me reste à faire...

Bon Dimanche.

[bernard53]

ok affaire réglé