Forum-seven : Communauté francaise de Windows 7

Bonsoir, mon pc a un problème de crash écran bleu un peu n'importe quand et j'ai beau eu le déposé chez des "informaticiens" ils m'ont tous dit (3) que le pc crash mais "je ne sais pas pourquoi", bref des incapables.
En espérant que cette analyse puisse aider a trouver ce qui est a changé.
Mes drivers sont a jours sauf celui de ma souris, de mon clavier et celui nommé Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1 (que je n'arrive pas a dl sur intel)
D'après un ami j'ai une carte graphique 4890hd raedon series qui n'est pas adapté a mon W7 qui bug(ca me ramène sur windows) des fois cad que je joue et a des moment la couleur de ma barre windows ainsi que le alt tab change de style.
Merci d'avance

Analyse:
System Information (local)
--------------------------------------------------------------------------------

computer name: BAZINGA-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8587894784 total
VM: 2147352576, free: 1939890176



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 26/05/2011 22:36:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052711-24975-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x4E (0x99, 0x1C023E, 0x0, 0x1C027E)
Error: PFN_LIST_CORRUPT
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 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 which cannot be identified at this time.


On Thu 26/05/2011 22:36:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x4E (0x99, 0x1C023E, 0x0, 0x1C027E)
Error: PFN_LIST_CORRUPT
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 which cannot be identified at this time.


On Thu 26/05/2011 19:56:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052611-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E24A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E02F8C, 0xFFFFF8800C461580, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 26/05/2011 11:23:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052611-23727-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x41201, 0xFFFFF683FF7C04A8, 0xFDD00001E1FF6847, 0xFFFFFA80098F7010)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 which cannot be identified at this time.


On Thu 26/05/2011 01:00:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052611-22245-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x4E (0x2, 0xC6ABF, 0x22FFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 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 which cannot be identified at this time.


On Thu 19/05/2011 23:19:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052011-33228-01.dmp
This was probably caused by the following module: unknown_module_00000000`00229600.sys (Unloaded_Unknown_Module_00000000`00229600+0x2E08)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001F9F080, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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.
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: unknown_module_00000000`00229600.sys .
Google query: unknown_module_00000000`00229600.sys MEMORY_MANAGEMENT




On Sun 15/05/2011 17:10:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-32900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E24A)
Bugcheck code: 0x34 (0x50830, 0xFFFFF88003193838, 0xFFFFF880031930A0, 0xFFFFF80002CC1E2E)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 which cannot be identified at this time.


On Fri 29/04/2011 16:20:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042911-28111-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF8A00D7774E0, 0x0, 0xFFFFF80002DF6F8C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 05/04/2011 17:35:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040511-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7E24A)
Bugcheck code: 0x116 (0xFFFFFA800A8C1010, 0xFFFFF88003E072E4, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 01/04/2011 14:41:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040111-26504-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88003BB09C2)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002F6A6AE, 0xFFFFF880031A8A08, 0xFFFFF880031A8270)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: Unknown .
Google query: Unknown SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Wed 30/03/2011 11:24:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033011-32651-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x4E (0x99, 0x20FFB4, 0x0, 0x20FF74)
Error: PFN_LIST_CORRUPT
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 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 which cannot be identified at this time.


On Fri 18/03/2011 12:58:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031811-18595-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x22C41B)
Bugcheck code: 0x50 (0xFFFFF8A010FCB430, 0x0, 0xFFFFF8800402105B, 0x2)
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. It is suggested you look for an update for the following driver: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys PAGE_FAULT_IN_NONPAGED_AREA




On Mon 07/03/2011 23:47:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030811-21840-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4461)
Bugcheck code: 0x19 (0x21, 0xFFFFF900C20F7000, 0x1230, 0xFF1230)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 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 Sat 05/03/2011 20:42:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030611-21169-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800319A678, 0xFFFFF88003199EE0, 0xFFFFF880012CA173)
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 02/03/2011 15:48:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030211-22058-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003EB8D08, 0xFFFFF88003EB8570, 0xFFFFF880012C8A91)
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.



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

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

atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

unknown_module_00000000`00000000.sys

unknown

unknown_module_00000000`00229600.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.

Bonjour
Ouvre le gestionnaire de périphériques et dis-moi si tu vois une alerte sur un ou plusieurs d'entre eux.
En haut dans Affichage, coche Afficher les périphériques cachés.
Il y a déjà un souci avec ta carte graphique, mais il y a trois pilotes inconnus en cause.

@+

Bonjour,
Concernant la carte graphique certains bugs ont eu lieu après la mise a jour driver.
Je n'ai aucune périphérie avec un point d'exclamation
Après si ca peut aider j'ai avg(gratuit) comme anti virus et j'ai bug quand je téléchargeais des fichiers .rar

Bonjour
Il faut recharger le pilote de ta carte graphique, désinstaller celui qui esty installé.
Redémarrer avec le pilote VGA et installer le pilote fraîchement chargé.
1- Télécharge et installe Malwarebytes Anti-Malware de RubbeR DuckY

Double-clique sur le fichier mbam-setup-1.50.exe (sous Vista et 7 autorise les modifications)
A la fin de l'installation, veille à ce que les options suivantes soient cochées

• -Mettre à jour Malwarebytes' Anti-Malware
  -Exécuter Malwarebytes' Anti-Malware

Clique sur Terminer
Une fenêtre Mise à jour de Malwarebytes' Anti-Malware va s'ouvrir avec une barre de progression.
Puis une autre annonçant le succès de la mise à jour de la base de données. Clique sur OK.
Le programme s'ouvre sur l'onglet Recherche.
Coche Exécuter un examen rapide, clique sur le bouton

A la fin du scan, sélectionne tout et clique sur Supprimer la sélection

Poste le rapport qui s'ouvre après cette suppression.
Redémarre le pc si cela est demandé
Tu peux retrouver le rapport dans l'onglet Rapports/Logs avec la date et l'heure d'exécution.

2- Télécharge ZHPDiag de Nicolas Coolman sur ton bureau.

Explication en images

Si besoin est, nous ferons appel à d'autres outils.

@+

Bonjour,
Aucun problème révéler par malwarebytes.
Je ne vois pas trop ce que fais le 2éme logiciel.
Quand j'éteins ou redémarre mon ordinateur je suis souvent obligé de forcer l'arrêt autrement ca reste bloqué et généralement ca finit pas un crash écran bleu

Bonjour
Je te demande de respecter la procédure proposée, nous gagnerons du temps.
Sinon je laisse tomber.
@+

Je dis que rien n'a été signalé, je ne sais pas a quoi sert le dernier logiciel et tout de suite ça part dans les "si tu fais pas ce que je dis, démerde toi".
Poster un log sur malwarebytes alors qu'il n'a rien détecté (de plus en scan rapide) je vois pas l'utilité vu qu'il donne aucune info.
On arrive donc au -2 télécharge l'autre logiciel mais a part le démarrer et avoir tout un rapport je vois pas trop ce qu'il fait, a moins que ce soit ce rapport que je dois poster au quel cas ce n'est pas spécifié.
Donc dans le doute je poste celui ci mais celui de malware n'indique rien.
Finalement je post le rapport mal vu que l'autre rapport comporte trop de caractère.
Malwarebytes' Anti-Malware 1.50.1.1100
http://www.malwarebytes.org

Version de la base de données: 6686

Windows 6.1.7600
Internet Explorer 8.0.7600.16385

27/05/2011 18:53:11
mbam-log-2011-05-27 (18-53-11).txt

Type d'examen: Examen rapide
Elément(s) analysé(s): 159047
Temps écoulé: 2 minute(s), 31 seconde(s)

Processus mémoire infecté(s): 0
Module(s) mémoire infecté(s): 0
Clé(s) du Registre infectée(s): 0
Valeur(s) du Registre infectée(s): 0
Elément(s) de données du Registre infecté(s): 0
Dossier(s) infecté(s): 0
Fichier(s) infecté(s): 0

Processus mémoire infecté(s):
(Aucun élément nuisible détecté)

Module(s) mémoire infecté(s):
(Aucun élément nuisible détecté)

Clé(s) du Registre infectée(s):
(Aucun élément nuisible détecté)

Valeur(s) du Registre infectée(s):
(Aucun élément nuisible détecté)

Elément(s) de données du Registre infecté(s):
(Aucun élément nuisible détecté)

Dossier(s) infecté(s):
(Aucun élément nuisible détecté)

Fichier(s) infecté(s):
(Aucun élément nuisible détecté)

Bonsoir
As-tu lu le tutoriel en image indiqué plus haut concernant ZHPDiag ?
Il y est indiqué comment héberger le rapport qui est assez conséquent.
Ce rapport va me permettre de voir presque tout ce qui peut y avoir d'indésirable sur ton pc.
Merci pour le rapport Malwarebytes.
Remarque amicale.
Ce n'est pas moi qui vient demander de l'aide, aussi la moindre des choses est de faire un minimum à quelqu'un qui cherche à résoudre ton problème et de faire ce qui est demandé.
Cette procédure est appliqué des centaines de fois par jour et je ne connais personne qui s'en soit plaint jusqu'à ce jour.
J'espère que comprends mieux le sens de ma demande.
@+

Oui et je n'ai pas trouvé ma réponse ca fait 48h que je suis debout en même temps.
Donc, merci pour ton aide et tant pis pour moi.
Bonne soirée.
Edit : Normal que je n'ai pas trouvé ma réponse elle n'était pas dans la page -_-

Bonjour
Un outil à passer pour supprimer toutes les toolbars inutiles.
Télécharge AD-Remover sur ton bureau.

Double clique sur AD-R.exe
Clique sur le bouton Nettoyer.
Poste le rapport qui va s'ouvrir en fin de scan.
Le rapport est sauvegardé sous C:\Ad-report-SCAN[1].txt
Ferme le programme par Quitter.

Il faudra mettre à jour le système, le pack SP1 n'est pas installé. Faire un Windows Update dans le panneau de configuration.

De même pour Java
-Java Runtime Environment (JRE)6u25 :
http://java.sun.com/javase/downloads/index.jsp
Clique sur Download JRE
Dans la page suivante, double clique sur Accept License Agreement
Clique sur Windows x86 Offline 15.77MB- jre-6u25-windows-i586.exe en bas, pour télécharger l'installateur .
Tu l'installeras hors connexion, c'est-à-dire le navigateur fermé.*
Il existe une version pour les systèmes 64bits.
jre-6u-25-windows-x64.exe de 16.09 MB

@+