Bonsoir!
Je viens chercher votre aide pour que vous m'éclairiez, apparemment c'est un problème de driver (comme d'hab'..) par rapport à la veille,  
mais je voudrais savoir qu'est ce que je peux faire?!
Cordialement
Jérémy
 
Le rapport Whocrashed:
 
 
On Mon 12/12/2011 22:44:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)  
Bugcheck code: 0x9F (0x3, 0xFFFFFFFF87961030, 0xFFFFFFFF83171AE0, 0xFFFFFFFF87FA35A8)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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: ntkrpamp.exe .  
Google query: ntkrpamp.exe DRIVER_POWER_STATE_FAILURE
 
 
 
 
On Mon 12/12/2011 22:44:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-24663-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEEB4)  
Bugcheck code: 0x9F (0x3, 0xFFFFFFFF87961030, 0xFFFFFFFF83171AE0, 0xFFFFFFFF87FA35A8)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
2 crash dumps have been found and analyzed. A third party driver has 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:  
 
ntkrpamp.exe  
 
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.

Un nouveau crash, pas longtemps après une mise à jour windows..
 
 
On Tue 13/12/2011 21:52:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)  
Bugcheck code: 0xA (0x325BE7A4, 0x2, 0x0, 0xFFFFFFFF830C658C)
Error: IRQL_NOT_LESS_OR_EQUAL
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.  
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: ntkrpamp.exe .  
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
 
 
 
 
On Tue 13/12/2011 21:52:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121311-27830-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415FB)  
Bugcheck code: 0xA (0x325BE7A4, 0x2, 0x0, 0xFFFFFFFF830C658C)
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.  

Up, personne ne peut m'aider..

Si c'est un problème lié au passage en veille essaye de supprimer la mise en veille pour voir ...
 
 
tu peux aussi essaye un réparation via le dvd d'installation

Bonjour,
 
Tu peux également vérifier (et réparer) ton disque dur, souvent les erreur dues à "ntkrpamp.exe" ont pour origine le disque dur (et son réveil après la mise en veille).
 
Sous vista:  
 

• Clique droit sur l’icône du ton disque dur (poste de travail)
• Propriétés
• Outils
• Vérification des erreurs

En espérant avoir aidé!
 
l0stsn4k3

Salut à tous,
Merci de votre aide,
Non je n'ai pas de veille..
J'ai un nouveau rapport pour vous..
 
 
On Mon 19/12/2011 13:00:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1CF3A)  
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF87883F38, 0xFFFFFFFF878849C0, 0x7951DEC5)
Error: BAD_POOL_HEADER
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 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.  

Si je formate ça réglera tous mes problèmes de BSOD?

as tu fait le scandisk ?

Oui, rien apparemment..
Sauf si y'a un rapport à aller lire quelque part?

tu lui as bien demandé de corriger les erreurs ?
as tu jeté un oeuil dans les logs ? Panneau de config / outils d'admin / observateur d'evenements  

Oui je demandé de corriger les erreurs si je me souviens bien.  
Je viens de ravoir un crash.. (voir en PS)
Je dois regarder quoi dans l'observateur d’évènements?  
J'ai regardé les erreurs, depuis la dernière heure j'ai 4 erreurs:
_vérification d'erreur
_EventLog
_Service Control Manager
_amdkmdag
 
Une idée?
Voici le crash dump report:
On Mon 19/12/2011 14:24:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\memory.dmp
This was probably caused by the following module: athrusb.sys (athrusb+0xD0A4)  
Bugcheck code: 0xD1 (0x2421697E, 0x2, 0x0, 0xFFFFFFFF9A316860)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrusb.sys
product: Driver for Atheros Wireless USB Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device 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.  
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: athrusb.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: athrusb.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

tu regardes dans tous les logs, avant ton plantage si il y a une erreur qui semble grave
et tu regardes aussi, si il y en a pas une qui revient régulièrement
et enfin si il n'y a pas une erreur sur un disque

Voici ce que je trouve dans l'observateur d'évènements, dans la partie ERREUR
http://imageshack.us/f/687/captureuuq.jpg/
 
J'ai fais une vérification avec réparation, comment je sais si cela a réparé quelque chose?
Merci
Cordialement
 

So?