Crash - Blue screen
Posté : dim. 29 juil. 2012 12:06
Bonjour.
Episode 1 : j'efface Windows XP puis j'installe Windows 7 64 bits ainsi que quelques jeux dont Call of Duty MW3 qui fonctionnait nominalement sous XP. Je dois alors faire face à des crashes à répétition ayant tous pour origine ce qui semble être le connu "Clock watchdog timeout".
Episode 2 : recherches sur internet, vérifications et mises à jour des pilotes (ma_config.com ... merci à ce site ...). Pas de changement puis ... le pb disparaît sans que je comprenne pourquoi.
Episode 3 : quelques mois plus tard et à la suite de petits incidents, je lance une vérifications des fichiers système de windows (sfc /scannow en mode cmd). De nombreuses anomalies non réparées me conduisent à faire une mise à niveau avec le CD original.
Episode 4 : quelques galères après cette mise à niveau mais tout revient dans l'ordre (sfc /scanow sans erreur) puis après une ultime vérification et mises à jour des pilotes .. tout est OK ...
Episode 5 : je relance CoD MW3 et .. je me retrouve dans la galère de l'épisode 1 ... Grosse fatigue...
Je suppose ne pas être unique et toute expérience en la matière me serait précieuse. Bonne journée à tous.
A toutes fins utiles voici l'analyse du logiciel "Whocrashed" (désolé, c'est un peu long et, pour mémoire, le pilote REALTEK évoqué est parfaitement à jour) :
computer name: PC-DE-PASCAL
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17145352192 total
VM: 2147352576, free: 1950355456
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 28/07/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072812-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003900180, 0x1)
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 Sat 28/07/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x9FD4B)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003900180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: rt64win7.sys Realtek CLOCK_WATCHDOG_TIMEOUT
On Fri 27/07/2012 16:35:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-28657-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880039E4180, 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 Fri 27/07/2012 15:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003772180, 0x2)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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:
rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek )
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.
Episode 1 : j'efface Windows XP puis j'installe Windows 7 64 bits ainsi que quelques jeux dont Call of Duty MW3 qui fonctionnait nominalement sous XP. Je dois alors faire face à des crashes à répétition ayant tous pour origine ce qui semble être le connu "Clock watchdog timeout".
Episode 2 : recherches sur internet, vérifications et mises à jour des pilotes (ma_config.com ... merci à ce site ...). Pas de changement puis ... le pb disparaît sans que je comprenne pourquoi.
Episode 3 : quelques mois plus tard et à la suite de petits incidents, je lance une vérifications des fichiers système de windows (sfc /scannow en mode cmd). De nombreuses anomalies non réparées me conduisent à faire une mise à niveau avec le CD original.
Episode 4 : quelques galères après cette mise à niveau mais tout revient dans l'ordre (sfc /scanow sans erreur) puis après une ultime vérification et mises à jour des pilotes .. tout est OK ...
Episode 5 : je relance CoD MW3 et .. je me retrouve dans la galère de l'épisode 1 ... Grosse fatigue...
Je suppose ne pas être unique et toute expérience en la matière me serait précieuse. Bonne journée à tous.
A toutes fins utiles voici l'analyse du logiciel "Whocrashed" (désolé, c'est un peu long et, pour mémoire, le pilote REALTEK évoqué est parfaitement à jour) :
computer name: PC-DE-PASCAL
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17145352192 total
VM: 2147352576, free: 1950355456
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 28/07/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072812-19437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003900180, 0x1)
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 Sat 28/07/2012 11:43:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rt64win7.sys (Rt64win7+0x9FD4B)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003900180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
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: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
Google query: rt64win7.sys Realtek CLOCK_WATCHDOG_TIMEOUT
On Fri 27/07/2012 16:35:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-28657-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880039E4180, 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 Fri 27/07/2012 15:49:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003772180, 0x2)
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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:
rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek )
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.
