bluescreen STOP 0x0101
Bonjours,
J'ai un soucis avec mon ordinateur, depuis quelque temps quand je joue à des jeux (the witcher 3, dota 2), 10-15 minutes après un écran bleu apparaît, depuis 2 jours je tourne en rond à essayer de régler le problème, voilà pourquoi je vous demande de l'aide. Voici quelques informations qui j'espère pourra vous aider à trouver l'anomalie.
Configuration pc :
Carte mère : ASUSTeK Computer INC. P8P67-M PRO Rev X.0X
Processeur : Intel Core i7 2600 Cadencé à 3.40 GHz
Système d'exploitation : Windows 7 Edition Familiale Premium (X64)
Mémoire : 8 Go de mémoire totale de type DDR3 à 668.69 MHz
Carte Graphique : NVIDIA GeForce GTX 970 (Version DirectX installée: 11.0)
Disque dur : Disque dur MD05000-BLDW-RO de 465.76 Go SATA II et Disque dur WDCWD5000AZRX-00A8LB0 de 465.76 Go SATA III
Cartes multimedia : Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller
NVIDIA Corporation GM204 High Definition Audio Controller
whoCrashed :
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 25/05/2015 09:46:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052515-14320-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F9180, 0x6)
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 that cannot be identified at this time.
On Mon 25/05/2015 09:46:59 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, 0xFFFFF880030F9180, 0x6)
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 that cannot be identified at this time.
On Sun 24/05/2015 10:07:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052415-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 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 that cannot be identified at this time.
On Sun 24/05/2015 00:13:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052415-14601-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B2180, 0x4)
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 that cannot be identified at this time.
On Sat 23/05/2015 15:47:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052315-15256-01.dmp
This was probably caused by the following module: unknown_module_00000000`0000001f.sys (Unloaded_Unknown_Module_00000000`0000001f+0xE2)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 0x2)
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: unknown_module_00000000`0000001f.sys .
Google query: unknown_module_00000000`0000001f.sys CLOCK_WATCHDOG_TIMEOUT
On Sat 23/05/2015 01:45:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052315-18205-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F9180, 0x6)
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 that cannot be identified at this time.
On Fri 22/05/2015 18:01:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052215-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 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 that cannot be identified at this time.
On Fri 22/05/2015 16:13:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052215-19266-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B2180, 0x4)
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 that cannot be identified at this time.
On Wed 20/05/2015 00:45:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052015-19016-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0xA0 (0xB, 0x17F1EA000, 0x3, 0x0)
Error: INTERNAL_POWER_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 the power policy manager experienced a fatal error.
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 that cannot be identified at this time.
On Sun 17/05/2015 15:00:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051715-15210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88002F64180, 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 that cannot be identified at this time.
Conclusion
25 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 352.86 , NVIDIA Corporation)
unknown_module_00000000`00000000.sys
unknown_module_00000000`0000001f.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 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.
JE VOUS REMERCIE D'AVANCE POUR VOS REPONSE.
Répondre avec citation
dSZjd
, mais je crois bien avoir trouvé mon problème. Directement après l'installation de Windows 7 sans pertes de données, j'ai testé de jouer a the witcher 3 et aucun écran bleu en 45 minutes de jeu, J'ai eu un ecran bleu pendant que j'étais sur internet après avoir installé la mise a jour service pack 1. donc je peux en conclure que le problème viens de cet mise à jour? Si oui comment je peux régler ça?
Partager