Bonsoir a tous, depuis quelques temps j'ai régulièrement des écrans bleu, si vous pouvez m'expliquer le problème et surtout d'où ça viens.
 
Je vous met ci dessous le rapport d'erreurs de Windows et l'analyse avec WhoCrashed.
 
En vous remerciant d'avance.
 
Ma configuration:
 
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220496384 total
 
Rapport d'erreurs Windows:
 
Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.1.7600.2.0.0.256.48
  Identificateur de paramètres régionaux: 1036
 
Informations supplémentaires sur le problème :
  BCCode: f4
  BCP1: 00000003
  BCP2: 8AB58530
  BCP3: 8AB5869C
  BCP4: 82C76200
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1
 
Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\051912-37409-01.dmp
  C:\Users\Momo\AppData\Local\Temp\WER-64662-0.sysdata.xml
 
Analyse WhoCrashed:
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Sat 19/05/2012 19:02:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051912-37409-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCEA4)  
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8AB58530, 0xFFFFFFFF8AB5869C, 0xFFFFFFFF82C76200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.  
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 Sat 19/05/2012 19:02:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)  
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8AB58530, 0xFFFFFFFF8AB5869C, 0xFFFFFFFF82C76200)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.  
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 CRITICAL_OBJECT_TERMINATION
 
 
 
 
On Sat 19/05/2012 16:01:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051912-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3224B3)  
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF882E282C, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
3 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.  

up !

J'ai un Z99 qui a cramé avec écran bleu et tout le bordel.
Pour ton problème essaye de vider le fichier dump sous windows il y a une clef de registre a modifier pour cela => google est ton ami.
Pour moi Asus = Terminé !!

Merci nemesis-77- pour ta réponse.

Salut,
 
Tu nous remettras le rapport au prochain Bosd ?
 
sinon les 3 derniers parlent d'un possible pilote probleme.
 
Avant les bsod ca fonctionnait nickel ? tu as mis quelque chose a jour avant ?
 
*si oui tu peut toujours tenter une restauration a date anterieure si ca fonctionnait.
* Verifier ton disque dur chksdk ou l'

Salut narpa72, non j'ai rien installé a part les pilotes d'origine apres formatage a cause du probléme là, voici le nouveau rapport.
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Mon 21/05/2012 13:53:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052112-41028-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)  
Bugcheck code: 0x116 (0xFFFFFFFF85675278, 0xFFFFFFFF91842880, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.  
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 21/05/2012 13:53:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrCreateRecoveryContext+0x1F2)  
Bugcheck code: 0x116 (0xFFFFFFFF85675278, 0xFFFFFFFF91842880, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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 an attempt to reset the display driver and recover from a timeout failed.  
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 19/05/2012 19:02:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051912-37409-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCEA4)  
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8AB58530, 0xFFFFFFFF8AB5869C, 0xFFFFFFFF82C76200)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.  
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 Sat 19/05/2012 16:01:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051912-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3224B3)  
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF882E282C, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
4 crash dumps have been found and analyzed.  
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.

Il y a plus personne sur ce forum ?  
De l'aide svp.

Bon essai un autre pilote graphique, clic droit mettre a jour le pilote.
 
puis aussi demarrer / rechercher "cmd" et executer en administrateur puis dans la fenetre taper "sfc / scannow"  
 
tu as fait un chkdsk ? verifier et tenter réparation clusteur ?
 
active tes mises a jour window et vérifie ce qu'on te propose comme maj