Forum Clubic

Problème de crash dump !

Bonjour,
Depuis que j’ai réalisé une config pour mon fils, je rencontre tjrs le même Pb.
J’ai le message d’erreur sur écran bleu ( 1 à 4 x jour ) :
Stop 0x00000101 : clock interrupt not received on second processor within allocated time interval

Ma configuration :
Processeur Intel Core I7-2600K à 3.4GHz
Mémoire :8 Go de mémoire totale de type DDR3 à 802.43 MHz
Système : Windows 7 - 64 bit.
Carte mère:ASUSTeK Computer INC. P8P67-M PRO Rev X.0X
carte graphique:Radeon R9 - 380 gaming 4G.
Disque système:Disque dur ST3750640AS de 698.64 Go SATA II
Alimentation: ANTEC -TP 650W / 9A - 4.5A
Ventilateur process:Pure Rock 150W TDP/Beqquiet

Je n’utilise pas l’overclocking.

Dans les réglages suggérés, je n’ai pas mis 100% comme valeur de l’état minimal du processeur, mais 15%, valeur un peu supérieure à 1/8 de charge du CPU, dont la transition semble poser problème.
MAis le problème reste identique. Merci d avance pour votre aide

Cordialement,

:hello:

Cette valeur est peut-être un peu trop basse pour un i7 2600K :neutre:

Personnellement au montage d’un i5 4690K en 2015, j’ai eu ce problème qu’il était à sa fréquence maximum (3,5 Ghz) tout le temps :confused: je me suis alors aperçu que son état minimal était réglé à 100%, je l’ai donc réglé à 20%, ce qui correspond à 800 Mhz en fréquence minimum…or après plusieurs tests, si je mettais moins de 20 % le pc se comportait globalement très mal :neutre:

Donc essaie de régler l’état minimal à 20%, et vérifie aussi dans le bios de la carte mère que le SpeedStep est bien activé, c’est lui qui gère les variations de fréquences en fonction des tâches demandées ^^
Edité le 24/09/2017 à 17:09

Bonjour , et Merci pour ton aide

désolé pour la réponse tardive car je travaillais ce week end. j ai bien réglé l’état minimal à 20%

et controlé le bios de la carte mére ,le SpeedStep est bien sur activé.

MAis je pense que ce pb de Crash vient plutot d’un pilote non compatible avec mon matériel

Quand penses-tu , es -ce possible qu’ un pilote soit à l’origine du problème ?

Car je me suis aperçu que lorsque je me trouvé ds le bios , aucun pb au bout de 20mn

Mais aprés un démarrage classique de windows, environ 5 minutes aprés , survient ce crash !!

Comme puis-je procéder pour retrouver le pilote à l’origine du pb. ?? Merci encore et bonne journée

Bonjour , Pour donner suite à mon Pb

J ai effectué une mise à jour du Bios sur le site ASUS.
carte mère P8P67-M PRO BIOS 3701. version 2013.

Problème identique environs 1 heures aprés > crash !!
à 4 reprises aujourd 'hui

Voici mon rapport avec “Whocrashed” Merci d 'avance pour votre Aide !!!:(:wink:

System Information (local)


Computer name: NICO-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:Windows
Hardware: ASUSTeK COMPUTER INC., P8P67-M PRO
CPU: GenuineIntel Intel® Core™ i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8553099264 bytes total


Crash Dump Analysis


Crash dump directory: C:WindowsMinidump

Crash dumps are enabled on your computer.

On Sun 08/10/2017 01:52:04 your computer crashed
crash dump file: C:WindowsMinidump100817-11668-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003565180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:Windowssystem32ntoskrnl.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 also be caused because of overheating (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 08/10/2017 01:52:04 your computer crashed
crash dump file: C:Windowsmemory.dmp
This was probably caused by the following module: farflt.sys (farflt+0x8560)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003565180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:Windowssystem32driversfarflt.sys
product: Malwarebytes Anti-Ransomware Protection
company: Malwarebytes
description: Malwarebytes Anti-Ransomware Protection
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 also be caused because of overheating (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: farflt.sys (Malwarebytes Anti-Ransomware Protection, Malwarebytes).
Google query: Malwarebytes CLOCK_WATCHDOG_TIMEOUT

On Sun 08/10/2017 00:25:07 your computer crashed
crash dump file: C:WindowsMinidump100817-12916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:Windowssystem32ntoskrnl.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 also be caused because of overheating (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 06/10/2017 21:13:20 your computer crashed
crash dump file: C:WindowsMinidump100617-14944-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F980)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF88003365180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:Windowssystem32ntoskrnl.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 also be caused because of overheating (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


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:

farflt.sys (Malwarebytes Anti-Ransomware Protection, Malwarebytes)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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.

Si on se fie à la conclusion du rapport :

Bref, désactive pendant un temps la protection anti-ransomware de Malwarebytes et vois si les crashs cessent ou s’ils continuent :neutre:

Tu ne serais apparemment pas le seul à avoir ce genre de souci :

answers.microsoft.com…
Edité le 09/10/2017 à 01:30

Ok je te remercie bien pour ton aide , j’ ai carrément désinstallé Mallwarebytes

afin de déterminer si il est vraiment la source du Pb.

je reviendrais dans quelques temps , pour annoncer si le crash a cessé … :hello:

Il suffisait de désactiver la fonctionnalité “anti-ransomware” dans les options :wink:

J’utilise aussi Malwarebytes, mais en version Free et non Premium, je n’ai donc pas cette fonction “anti-ransomware” ^^