Bonjour,

Depuis quelque jour mon ordi crash énormément : parfois lorsque je suis seulement sur internet et la plupart du temps , lorsque je joue a guild wars 2. Bizarrement le risque de crash pendant guild wars ce présente sur les 10 premières minutes d'une session de jeu. Passé ce cap , je peux le laisser tourner 1H ou 10H , l'ordi ne crash plus.

J'ai donc effectuer des analyses avec le soft whocrashed de tout les crash de mon pc ces derniers jours. J'aimerais savoir s'il est possible pour vous de les analyser , voir de m'aider a résoudre le problème.

Voici ma config ( 2 ans et demi )
-AMD phenom II x4 965
-Radeon HD 5850
-4Go ram
-Vista

Merci d'avance pour votre aide et pour le temps que vous prendrai pour m'aider.

Et voici les rapport de crash :

On Mon 03/09/2012 12:44:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090312-02.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6DC1D)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFFC8678C1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 which cannot be identified at this time.

On Mon 03/09/2012 12:44:26 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6DC1D)
Bugcheck code: 0xD1 (0x4, 0x2, 0x1, 0xFFFFFFFFC8678C1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 which cannot be identified at this time.

On Mon 03/09/2012 11:35:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090312-01.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x2C1F)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFE3725010, 0xFFFFFFFFC979770C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

On Sun 02/09/2012 17:58:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-07.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x3008E)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFD1ADB08E, 0xFFFFFFFFE8AAC6B4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 02/09/2012 15:38:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-06.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6D54E)
Bugcheck code: 0xD1 (0xB0, 0x2, 0x1, 0xFFFFFFFFC867054E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 which cannot be identified at this time.

On Sun 02/09/2012 10:06:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-05.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x233B9D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFE386AB9D, 0xFFFFFFFFDEBEC924, 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 which cannot be identified at this time.

On Sun 02/09/2012 09:52:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-04.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x17311)
Bugcheck code: 0xD1 (0x1, 0xE8, 0x0, 0x0)
Error: DRIVER_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 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 which cannot be identified at this time.

On Sun 02/09/2012 09:51:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-03.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DF99)
Bugcheck code: 0xA (0xFFFFFFFFC03B95F0, 0x0, 0x0, 0xFFFFFFFFE3675805)
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 which cannot be identified at this time.

On Sun 02/09/2012 09:33:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xEE010)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFE352C010, 0xFFFFFFFFD08148DC, 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 which cannot be identified at this time.

On Sun 02/09/2012 09:24:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x1A (0x61940, 0x774BB000, 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 which cannot be identified at this time.

On Sat 01/09/2012 10:40:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090112-02.dmp
This was probably caused by the following module: ecache.sys (ecache+0x29F8)
Bugcheck code: 0xD1 (0x4, 0x2, 0x0, 0xFFFFFFFFC89779F8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ecache.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Special Memory Device Cache
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 which cannot be identified at this time.

On Sat 01/09/2012 10:18:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini090112-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x4736)
Bugcheck code: 0xD1 (0xFFFFFFFFC31F432C, 0x2, 0x1, 0xFFFFFFFFBFF76736)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 which cannot be identified at this time.

On Fri 31/08/2012 15:13:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini083112-06.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDABF)
Bugcheck code: 0x4E (0x99, 0x7953C, 0x2, 0x7940D)
Error: PFN_LIST_CORRUPT
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 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 31/08/2012 15:04:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini083112-05.dmp
This was probably caused by the following module: win32k.sys (win32k+0x936FD)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFDF2F36FD, 0xFFFFFFFFDFFBEA20, 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 31/08/2012 14:54:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini083112-04.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x24781)
Bugcheck code: 0x50 (0xFFFFFFFFF20309C4, 0x0, 0xFFFFFFFFD4ED3781, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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.

hum deja pour commencer par le commecnement ton alim c'est quoi ?

Ups j'avais oublié : C'est une Power 650W .

- "Stop 0x000000D1 ou Stop 0xD1 ou DRIVER_IRQL_NOT_LESS_OU_EQUAL" :

Cela vient d'un pilote de périphérique, d'un service incompatible. Si ce problème survient au moment de la fermeture de Windows et si vous avez plusieurs périphériques USB branchés, installez le dernier Service Pack. Si l'erreur signale le fichier Kbdclass.sys, cela provient d'un pilote ou d'un programme gestionnaire de clavier non compatible. Un pare-feu de connexion Internet peut provoquer également ce type d'erreur. Vous devez dans ce cas procéder à une mise à jour du programme.
"J’ai une erreur STOP 0X000000D1 incriminant le fichier USBUHCI.SYS et ce uniquement quand je grave un CD-R ou pendant la lecture des DVD-ROM…" Il suffit de faire une mise à jour du BIOS.
"J’ai des erreurs STOP 0X000000D1 incriminant le fichier USBPORT.SYS et ce uniquement quand je grave un CD-R ou pendant la lecture des DVD-ROM…" Cela dénote un conflit avec un pilote de disque USB qu'il vous suffit de désinstaller puis de réinstaller. Au pire, procédez à une mise à jour du pilote incriminé.
"STOP 0x000000D1 ATAPI.SYS : c'est un problème sur le microprocesseur symptomatique d'un mauvais fonctionnement ou d'un overclocking mal maîtrisé. Le temps de l'installation de votre système, revenez aux paramètres par défaut.
- "Erreur STOP Driver irql not less or equal" :
Le fichier incriminé est sptd.sys.
Redémarrez en mode sans échec.
Procédez à la désinstallation de tous les programmes de gravure qui émulent un lecteur virtuel (Alcohol, etc.).
Accédez au Gestionnaire de périphériques puis activez l'affichage des périphériques cachés.
Désinstallez les pilotes virtuels installés par ces programmes.
Redémarrez votre machine

Merci beaucoup pour la réponse , mais je ne comprend pas tout ce qu'elle implique.

Par contre ce que je peux affirmer :
-Mon processeur n'est pas OC.
-Je viens de mettre a jour les driver de ma carte graphique.
-"programmes de gravure qui émulent un lecteur virtuel" : je n'utilise pas ce genre de logiciel.
-Je ne grave pas de cd ou de dvd.

Est ce que ces info peuvent vous aider , au regard de la réponse de grognon ?

Merci d'avance .

Une idée ?

lc power 650w ?

ça peut etre elle la cause.

des soucis sur d'autres jeux ?

Oui c'est bien cette alim ...
J'avais pas de problème avant guild wars 2 , et puis n'est il pas bizarre que ca crash que sur les début de session de jeu ? De plus j'ai quelque crash sur internet ou même juste au démarrage.

C'est de pire en pire , maintenant mon pc galère a démarrer : je reste bloquer au premier écran , ça freeze ... J'espere que c'est pas le hardware ...

Up

Ton problème est dû à ton installation Windows et tes drivers ! j'essayerai de passer dans la semaine chez toi pour régler tout ça !