Aller au contenu
  • Pas encore inscrit ?

    Pourquoi ne pas vous inscrire ? C'est simple, rapide et gratuit.
    Pour en savoir plus, lisez Les avantages de l'inscription... et la Charte de Zébulon.
    De plus, les messages que vous postez en tant qu'invité restent invisibles tant qu'un modérateur ne les a pas validés. Inscrivez-vous, ce sera un gain de temps pour tout le monde, vous, les helpeurs et les modérateurs ! :wink:

Crash de l'ordinateur


jacketcharly
 Share

Messages recommandés

mon ordinateur s'éteint régulièrement j'ai installé who crashed ci dessous le résultat:

On Fri 18/01/2013 21:01:07 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-23134-01.dmp

This was probably caused by the following module: tcpip.sys (tcpip+0x77A20)

Bugcheck code: 0xD1 (0x1000001D, 0x2, 0x0, 0xFFFFFFFF8B09BA20)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\tcpip.sys

product: Système d’exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote TCP/IP

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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 Fri 18/01/2013 21:01:07 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: tcpip.sys (tcpip+0x77A20)

Bugcheck code: 0xD1 (0x1000001D, 0x2, 0x0, 0xFFFFFFFF8B09BA20)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\tcpip.sys

product: Système d’exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote TCP/IP

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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 Fri 18/01/2013 20:44:03 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17706-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E41B)

Bugcheck code: 0x1A (0x41287, 0x1C, 0x0, 0x0)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.

 

 

 

On Fri 18/01/2013 20:34:33 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17846-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x967C1)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82ECE7C1, 0xFFFFFFFFA07A4AF4, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntkrnlpa.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 Fri 18/01/2013 20:21:03 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-26379-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x82083)

Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82E46B5B)

Error: IRQL_NOT_LESS_OR_EQUAL

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 that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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 Fri 18/01/2013 20:12:02 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17316-01.dmp

This was probably caused by the following module: aswsp.sys (aswSP+0x11414)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF90530414, 0xFFFFFFFFA4DE9C0C, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\aswsp.sys

product: avast! Antivirus

company: AVAST Software

description: avast! self protection module

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: aswsp.sys (avast! self protection module, AVAST Software).

Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

On Fri 18/01/2013 19:20:44 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-16894-01.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xFA994)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF91526994, 0xFFFFFFFFA0AA78D8, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\nvlddmkm.sys

product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

company: NVIDIA Corporation

description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

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: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58 , NVIDIA Corporation).

Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

On Fri 18/01/2013 18:26:37 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-18018-01.dmp

This was probably caused by the following module: aswsp.sys (aswSP+0x1163D)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83042C21, 0xFFFFFFFFA70D89AC, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\aswsp.sys

product: avast! Antivirus

company: AVAST Software

description: avast! self protection module

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: aswsp.sys (avast! self protection module, AVAST Software).

Google query: AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

On Fri 18/01/2013 18:10:20 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17768-01.dmp

This was probably caused by the following module: aswsp.sys (aswSP+0x8C9B)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF855E01E8, 0xFFFFFFFF855E0238, 0x80A0001)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\drivers\aswsp.sys

product: avast! Antivirus

company: AVAST Software

description: avast! self protection module

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.

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: aswsp.sys (avast! self protection module, AVAST Software).

Google query: AVAST Software BAD_POOL_HEADER

 

 

 

On Fri 18/01/2013 17:56:07 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17238-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8CD03A2C, 0xFFFFFFFF8CD03610, 0xFFFFFFFF82F0FDAA)

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 that cannot be identified at this time.

 

 

 

On Fri 18/01/2013 17:10:16 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17503-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E41B)

Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)

Error: MEMORY_MANAGEMENT

file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.

 

 

 

On Fri 18/01/2013 17:06:33 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17019-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0x15A864)

Bugcheck code: 0x19 (0x21, 0xFFFFFFFFFFA8D000, 0x1010, 0xFFFFFFFF854EFC80)

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 that cannot be identified at this time.

 

 

 

On Fri 18/01/2013 16:57:41 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17659-02.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x304160)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8CD7D2C4, 0xFFFFFFFF8CD7CEA0)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\nvlddmkm.sys

product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

company: NVIDIA Corporation

description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

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. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58 , NVIDIA Corporation).

Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

 

 

 

On Fri 18/01/2013 15:05:53 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-18283-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)

Bugcheck code: 0xA (0x55F1E68, 0x2, 0x1, 0xFFFFFFFF82EA2E91)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

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 Thu 17/01/2013 23:57:52 GMT your computer crashed

crash dump file: C:\Windows\Minidump\011813-17659-01.dmp

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1682D)

Bugcheck code: 0x19 (0x3, 0xFFFFFFFF855E17E8, 0xFFFFFFFF855E17E8, 0x100007F)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\drivers\nvlddmkm.sys

product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

company: NVIDIA Corporation

description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58

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.

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 Compatible Windows Vista Kernel Mode Driver, Version 176.58 , NVIDIA Corporation).

Google query: NVIDIA Corporation BAD_POOL_HEADER

 

 

 

 

--------------------------------------------------------------------------------

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:

 

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

aswsp.sys (avast! self protection module, AVAST Software)

aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)

ewusbmdm.sys (USB Modem/Serial Device Driver, Huawei Technologies Co., Ltd.)

nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 176.58 , 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.

Lien vers le commentaire
Partager sur d’autres sites

Bonjour jacketcharly,

 

1. As-tu des "?" ou "!" dans le gestionnaires des tâches ?

 

~~~~~~~~~~~~~~

 

2. Télécharge Security Check de screen317 : screen317.spywareinfoforum.org/SecurityCheck.exe

  • Pour lancer le programme, ferme tout, puis double-clique sur "SecurityCheck.exe"
  • Pour continuer, appuie sur une touche quelconque et suis les indications
  • Si l’un des programmes de sécurité devait demander l’autorisation d'accéder à Internet à partir de dig.exe, il faut accepter
  • A la fin, le Rapport checkup.txt s'ouvre :
    --> poste stp son contenu dans ta prochaine réponse
  • NB : il n’y aura pas d’enregistrement automatique de ce rapport ; si tu souhaites en conserver une copie, clique sur Fichier > Enregistrer sous, puis choisis une localisation (le Bureau, par exemple) et clique en bas à droite sur "Enregistrer".

~~~~~~~~~~~~~~

 

 

@+,

Tonton

Lien vers le commentaire
Partager sur d’autres sites

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Invité
Répondre à ce sujet…

×   Collé en tant que texte enrichi.   Coller en tant que texte brut à la place

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.

 Share

  • En ligne récemment   0 membre est en ligne

    Aucun utilisateur enregistré regarde cette page.

×
×
  • Créer...