Gros plantages
diablolike
Messages postés
36
Statut
Membre
-
diablolike Messages postés 36 Statut Membre -
diablolike Messages postés 36 Statut Membre -
Bonjour à tous,
J'ai un ordi tout neuf depuis 2semaines, et deja de gros plantages assez réguliers du genre gros freeze,je peux même pas faire ctrl alt suppr, il faut savoir que j'ai deja eu un écran bleu la semaine derniere...
ça arrive a n importe quel moment, quand je suis sur photoshop, sur internet ou quand j écoute de la musique meme...
Peut etre un probleme de compatibilié???
ma config :
processeur intel i7 2600k 3.4ghz
CM: p8p67
CG: gtx 580 3go
RAM: 2x4go corsair vengeance
Merci de votre aide..
J'ai un ordi tout neuf depuis 2semaines, et deja de gros plantages assez réguliers du genre gros freeze,je peux même pas faire ctrl alt suppr, il faut savoir que j'ai deja eu un écran bleu la semaine derniere...
ça arrive a n importe quel moment, quand je suis sur photoshop, sur internet ou quand j écoute de la musique meme...
Peut etre un probleme de compatibilié???
ma config :
processeur intel i7 2600k 3.4ghz
CM: p8p67
CG: gtx 580 3go
RAM: 2x4go corsair vengeance
Merci de votre aide..
4 réponses
pensant que c'était un probleme de compatibilité avec la RAM j'ai changé de RAM et même probleme mais en moins fréquent
help please
help please
UP
le problème n'est pas du tout résolu ça commence à durer je trouve pas la source. Cet ordi m'a couté un bras, ça me rend fou qu'il ne marche pas... je pensais à la ram mais non, j'en ai changé 3 fois et c'est pas ça...
Puvez vous m'aider a trouver des piste svp. Comment isoler le problème???
MERCI
le problème n'est pas du tout résolu ça commence à durer je trouve pas la source. Cet ordi m'a couté un bras, ça me rend fou qu'il ne marche pas... je pensais à la ram mais non, j'en ai changé 3 fois et c'est pas ça...
Puvez vous m'aider a trouver des piste svp. Comment isoler le problème???
MERCI
gros monologue, je trouve pas la solution je deviens dingue, surtout que c'est mon outil de travail...
rapport whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 06/11/2011 15:50:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-26644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880031D7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.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 Sun 06/11/2011 15:50:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880031D7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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.
toujours pas d'idée??
rapport whocrashed :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 06/11/2011 15:50:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110611-26644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880031D7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.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 Sun 06/11/2011 15:50:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880031D7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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.
toujours pas d'idée??
