Blue screen virus?
thomasP01
-
Panth33ra Messages postés 21956 Date d'inscription Statut Membre Dernière intervention -
Panth33ra Messages postés 21956 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
J'ai depuis peu des bluescreen qui surviennent régulièrement, sans forcément faire quelque chose.
Je ne sais pas si c'est du à un composant informatique ou autre chose et j'aimerai corriger le souci.
Merci pour l'aide apportée.
Thomas
J'ai depuis peu des bluescreen qui surviennent régulièrement, sans forcément faire quelque chose.
Je ne sais pas si c'est du à un composant informatique ou autre chose et j'aimerai corriger le souci.
Merci pour l'aide apportée.
Thomas
A voir également:
- Bsod virus
- Bsod - Guide
- Virus mcafee - Accueil - Piratage
- Virus facebook demande d'amis - Accueil - Facebook
- Undisclosed-recipients virus - Guide
- Panda anti virus gratuit - Télécharger - Antivirus & Antimalwares
2 réponses
Panth33ra
Messages postés
21956
Date d'inscription
Statut
Membre
Dernière intervention
Ambassadeur
1 997
Bonjour,
Un BSOD (Blue Screen On the Death ou Ecran bleu de la mort) peut être la cause de bien des maux... https://www.malekal.com/bsod-ecran-bleu-windows/
Un BSOD (Blue Screen On the Death ou Ecran bleu de la mort) peut être la cause de bien des maux... https://www.malekal.com/bsod-ecran-bleu-windows/
Bonjour,
Merci pour votre réponse,
Voici le whoCrashed rapport mais je ne vois pas trop ou chercher. J'ai vu d'autres articles sur ces erreurs mais par ou commencer?
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 27.10.2020 10:09:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201027-1009.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xF84)
Bugcheck code: 0x1A1 (0xFFFFD50394B52080, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 09.09.2020 23:42:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: file.sys (file.)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80555B73358)
Error: DPC_WATCHDOG_VIOLATION
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).
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: file.sys .
Merci pour votre réponse,
Voici le whoCrashed rapport mais je ne vois pas trop ou chercher. J'ai vu d'autres articles sur ces erreurs mais par ou commencer?
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 27.10.2020 10:09:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20201027-1009.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xF84)
Bugcheck code: 0x1A1 (0xFFFFD50394B52080, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
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 09.09.2020 23:42:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: file.sys (file.)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80555B73358)
Error: DPC_WATCHDOG_VIOLATION
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).
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: file.sys .
