Aller au contenu

AtlasVI

Membres
  • Compteur de contenus

    5
  • Inscription

  • Dernière visite

Visiteurs récents du profil

Le bloc de visiteurs récents est désactivé et il n’est pas visible pour les autres utilisateurs.

AtlasVI's Achievements

Junior Member

Junior Member (3/12)

0

Réputation sur la communauté

  1. Bonjour @Tonton, J'ai bien effectuer les mises a jour ainsi que les facultative. Par contre oui Bit Defender quand jeteint mon pc jai souvent une erreur avec ecrit sa jai donc chercher lapplication mais impossible a trouver.. Apres plusieur recherche j'ai constater que ca peut etre installer a partir dautres logiciel. J'ai donc pu allez sur le site de bit defender et instaler un outil de desintallation que jai ci-tot supprimer bien sur . En esperant que sa fonctionne je vous tiens au courant . Merci beaucoup .
  2. Bonjour @Tonton, Désolé de ma reponse tardive, jai hélas toujours le même soucis jai donc fait toute les manip expliquer dans la reponse ci-dessus en voici le résultat. Merci de ton aides . System Information (local) Computer name: DESKTOP-CPCUFJ0 Windows version: Windows 11, 10.0, version 2009, build: 22000 (x64) Windows dir: C:\WINDOWS Hardware: 90NC00MLFR, LENOVO, 3717 CPU: GenuineIntel Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz 8664, level: 6 Processor count: 12 logical processors, active mask: 4095 RAM: 7933,2MB Crash Dump Analysis Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Fri 29/04/2022 13:27:23 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\042922-20078-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8050ED1E330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Fri 29/04/2022 13:27:23 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8050ED1E330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Thu 28/04/2022 16:57:00 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\042822-16437-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8072A91F330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Wed 27/04/2022 15:12:35 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\042722-239937-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF8031950C330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Tue 26/04/2022 16:02:26 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\042622-16031-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF80653B11330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. On Mon 25/04/2022 15:45:00 your computer crashed or a problem was reported Crash dump file: C:\WINDOWS\Minidump\042522-102546-01.dmp (Minidump) Bugcheck code: 0x133(0x1, 0x1E00, 0xFFFFF80013910330, 0x0) Bugcheck name: DPC_WATCHDOG_VIOLATION Driver or module in which error occurred: intelppm.sys (intelppm+0x153f) File path: C:\WINDOWS\System32\drivers\intelppm.sys Description: Processor Device Driver Product: Microsoft® Windows® Operating System Company: Microsoft Corporation Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue). Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system. The following dump file was found but appeared to be corrupt: C:\WINDOWS\Temp\BitDefender Threat Scanner.dmp Conclusion 7 crash dumps have been found and analyzed. Only 6 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. It is suggested that you run CHKDSK on your system drive to check your drive for errors. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the suggestions displayed in the bugcheck analysis above. The analysis process took 0:00:09 (h:mm:ss).
  3. Bonjour, Désolé c'est Windows 11. Bonne journée.
  4. Bonjour merci. Desolé si le sujet n'est pas au bon endroit je suis novice en forum. Mon pc processeur : Intel Core i5-10400 Carte graphique : Nvidia GeForce GTX 1650 SUPER Mémoire vive : 8 Go (BSOD) - Erreur 133 DPC Watchdog Violation Bonne semaine
  5. bonjour a tous je me tourne vers vous car jai un soucis de blue screen avec toujours le meme code erreur 133 DPC_WATCHDOG_VIOLATION jai essayer beaucoup de manip. il ya souvent un crash pas longtemps apres lallumage du pc et dautres quand bon lui semble . please help
×
×
  • Créer...