Bonjours à tous donc, tout comme il est dis dans le titre j'ai un gros problème de bleu screen depuis pas mal de temps. Si je me suis trompé d'endroit ou bien s'il y a un sujet semblable veuiller me dépacer svp .
 
Alors voilà mes petits message d'erreur:
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Tue 14/12/2010 20:04:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121410-16598-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)  
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF807A3120, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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.  
 
 
On Tue 14/12/2010 20:04:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!HalInitializeOnResume+0x500)  
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF807A3120, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.  
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: hal.sys .  
Google query: hal.sys CLOCK_WATCHDOG_TIMEOUT
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Wed 15/12/2010 19:23:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121510-16208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)  
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86FF06F4, 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.  
 
 
On Tue 14/12/2010 20:04:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121410-16598-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)  
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF807A3120, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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.  
 
 
On Tue 14/12/2010 20:04:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!HalInitializeOnResume+0x500)  
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFFFFF807A3120, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.  
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: hal.sys .  
Google query: hal.sys CLOCK_WATCHDOG_TIMEOUT
 
 
 
 
 
--------------------------------------------------------------------------------
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:  
 
hal.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.
 
 
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.  
 
 
 
 
 
Voilà tout droit sortie de " WhoCrashed "...
 
Alors pour ma config:
 
Système d'exploitation: Windows 7 (32bits)
Proc: Intel i7 - 920    2.67Ghz   x86 ACPI
Mémoire: 6Go de RAM installé mais seulement 3Go en fonction --> ( 32bits )
Carte graphique : ATI Radeon 4890
 
 
 
Si vous voulez d'autre informations n'ésitez pas
 
J'espère avoir de vos nouvelles très bientôt, Merci d'avance !
Cordialement Ghost

UP

Tu as changé quoi entre le moment où ça plantait pas et le moment où ça plantait?
 
Peut être un o/c défaillant, ou soit un driver défaillant, soit le système qui part en vrille, soit un composant hardware qui fait des siennes.

aucun matériel (carte graphique, RAM...) changé depuis la première installation.
 
J'ai flashé mon OS en un plus récent mais je ne sais plus lequel était auparavent et je ne sais plus si je l'avais fait avant ou bien après avoir eut ce problème ... :s j'avous avoir fait le boulet. Donc si jamais quelqu'un à un conseil ca serai avec plaisir que je l'écouterai.
 
Tous mes composant sont à jours, fait avec principalement TousLesDrivers.com .

Essaie de réinstaller ton OS pour voir si ça le fait encore en gardant tout d'abord les drivers de base livrés avec tes composants puis en les mettant à jour.
Si ça le fait encore ça pourrait être un problème d'ordre matériel (connecteurs mal branchés ou qui se sont défaits, matériel en voie de mort etc...).

Ok je viens d'esseyer de réinstaller mon OS... pour le moment tout c'est bien passé durant l'installation, j'attend de remettre tous mes jeux et autres logiciels pour voir si mes écrans bleus sont toujours là.
 
Je vous tiens aux nouvelles.
 
Cordialement, Ghost Mell

Salut,  
 
Bon j' ai toujours le même problème en pleins jeu, au bout d'un moment j'ai un arrêt sur image...
 
Voilà le rapport Windows après le redémarrage:
 
Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.1.7600.2.0.0.768.3
  Identificateur de paramètres régionaux: 1036
 
Informations supplémentaires sur le problème :
  BCCode: 124
  BCP1: 00000000
  BCP2: 866F9394
  BCP3: 00000000
  BCP4: 00000000
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1
 
Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\011411-17721-01.dmp
  C:\Users\jerome\AppData\Local\Temp\WER-40919-0.sysdata.xml
 
Lire notre déclaration de confidentialité en ligne :
  http://go.microsoft.com/fwlink/?li [...] cid=0x040c
 
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
  C:\Windows\system32\fr-FR\erofflps.txt
 
 
 
 
Et le rapport Whocrashed après redémarrage:
 
Welcome to WhoCrashed HOME EDITION v 3.01
--------------------------------------------------------------------------------
 
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.  
 
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.  
 
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.  
 
 
To obtain technical support visit www.resplendence.com/support
 
To check if an update of this program is available, click here.
 
Just click the Analyze button for a comprehensible report ...
 
 
 
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
 
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should ge the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
 
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
 
 
 
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
 
computer name: JEROME-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 3211911168 total
VM: 2147352576, free: 1977868288
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Fri 14/01/2011 16:42:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011411-17721-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x322493)  
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF866F9394, 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
--------------------------------------------------------------------------------
 
1 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.  
 
 
 
 
 
J'ai vraiment besoin d'aide là aidez moi svp
 
Cordialement ghostmell

UP....

...