Hello,
Ca m'arrive depuis 3 semaines.
C'est plusieurs fois par jour depuis quelques jours.
Etant freelance, c'est très dommageable pour mon travail.
J'ai lu plein d'articles sur comment checker les pilotes, etc., mais c'est beaucoup trop compliqué pour moi, je ne parviens pas à résoudre le problème et J'ai peur de faire des bêtises en désactivant des pilotes utiles à mes différents matériels ou logiciels (par ex. ma cam Logitech dont j'ai cru un moment qu'elle était en cause).
J'ai essayé la commande "vérifier", utilisé BlueScreenViewer, mais je ne sais pas quoi faire des informations obtenues.
Merci de votre aide si vous pouvez, et bonne journée.
Régis
Besoin d'aide pour des BSOD à répétition [résolu]
Modérateur : Mods Windows
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Bonjour,
Personne pour m'aider ?
Amitiés.
Personne pour m'aider ?
Amitiés.
- Messages : 31250
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne

Re: Besoin d'aide pour des BSOD à répétition
Bonjour,
Il aurait été, dans ce cas, judicieux de transmettre les éléments de BlueScreenView
Il aurait été, dans ce cas, judicieux de transmettre les éléments de BlueScreenView
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Bonjour,
Merci, je vais le relancer, j'ai eu de multiples écrans bleus depuis ce matin :-(
Merci, je vais le relancer, j'ai eu de multiples écrans bleus depuis ce matin :-(
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Voici ce que ça dit : https://pjjoint.malekal.com/files.php?i ... f9r14n11n5
Mais c'est très incomplet, j'ai eu BSOD depuis 3 semaines, dont déjà 6 ou 7 rien qu'aujourd'hui, qui ne sont pas dans ce rapport.
Mais c'est très incomplet, j'ai eu BSOD depuis 3 semaines, dont déjà 6 ou 7 rien qu'aujourd'hui, qui ne sont pas dans ce rapport.
- Messages : 31250
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne

Re: Besoin d'aide pour des BSOD à répétition
Un double clic sur la ligne du .dmp du 02/05/2021 te donne pas plus d'informations ?
https://www.malekal.com/bsod-ntoskrnl-exe-windows-10/
https://www.malekal.com/power-driver-state-failure/
https://www.malekal.com/bsod-ntoskrnl-exe-windows-10/
https://www.malekal.com/power-driver-state-failure/
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Ca dit ça : https://pjjoint.malekal.com/files.php?i ... s13x5e13x8
Ca n'arrête pas de planter, même en mode sans échec, même au redémarrage qui parfois ne se fait plus.
Ca n'arrête pas de planter, même en mode sans échec, même au redémarrage qui parfois ne se fait plus.
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Je viens de parcourir l'article en diagonale (avant que ça ne plante à nouveau).
J'utilise ESET et Hide My Ass en VPN. Possible que ce soit l'un des deux ?
J'utilise ESET et Hide My Ass en VPN. Possible que ce soit l'un des deux ?
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Voici ce que dit WhoCrashed :
*System Information (local)
--------------------------------------------------------------------------------
Computer name: CASSIUS
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: ZenBook UX433FN_UX433FN, ASUSTeK COMPUTER INC., UX433FN
CPU: GenuineIntel Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 16985100288 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 02/05/2021 00:30:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050221-39484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x9F (0x3, 0xFFFF9F034D5FC060, 0xFFFFFD0DCD857BA0, 0xFFFF9F035D23ED30)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
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 02/05/2021 00:30:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt+0x3F5E40)
Bugcheck code: 0x9F (0x3, 0xFFFF9F034D5FC060, 0xFFFFFD0DCD857BA0, 0xFFFF9F035D23ED30)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
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 29/11/2020 02:10:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112920-19281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x139 (0x3, 0xFFFF820C16217180, 0xFFFF820C162170D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/11/2020 11:26:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112620-19828-01.dmp
This was probably caused by the following module: lvrs64.sys (0xFFFFF80078BA2FC9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80078BA2FC9, 0xFFFFCC83A465F668, 0xFFFFCC83A465EEA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech Kernel Audio Improvement Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.).
Google query: lvrs64.sys Logitech Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 17/11/2020 12:05:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111720-26437-01.dmp
This was probably caused by the following module: lvrs64.sys (0xFFFFF8006AC87DDD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8006AC87DDD, 0xFFFFF0883324F658, 0xFFFFF0883324EE90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech Kernel Audio Improvement Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.).
Google query: lvrs64.sys Logitech Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sun 15/11/2020 22:25:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111620-20281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x139 (0x3, 0xFFFFF4887A767180, 0xFFFFF4887A7670D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 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:
lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.)
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.
*System Information (local)
--------------------------------------------------------------------------------
Computer name: CASSIUS
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: ZenBook UX433FN_UX433FN, ASUSTeK COMPUTER INC., UX433FN
CPU: GenuineIntel Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 16985100288 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 02/05/2021 00:30:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\050221-39484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x9F (0x3, 0xFFFF9F034D5FC060, 0xFFFFFD0DCD857BA0, 0xFFFF9F035D23ED30)
Error: DRIVER_POWER_STATE_FAILURE
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 driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
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 02/05/2021 00:30:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt+0x3F5E40)
Bugcheck code: 0x9F (0x3, 0xFFFF9F034D5FC060, 0xFFFFFD0DCD857BA0, 0xFFFF9F035D23ED30)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
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 29/11/2020 02:10:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112920-19281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x139 (0x3, 0xFFFF820C16217180, 0xFFFF820C162170D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 26/11/2020 11:26:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112620-19828-01.dmp
This was probably caused by the following module: lvrs64.sys (0xFFFFF80078BA2FC9)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80078BA2FC9, 0xFFFFCC83A465F668, 0xFFFFCC83A465EEA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech Kernel Audio Improvement Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.).
Google query: lvrs64.sys Logitech Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Tue 17/11/2020 12:05:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111720-26437-01.dmp
This was probably caused by the following module: lvrs64.sys (0xFFFFF8006AC87DDD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8006AC87DDD, 0xFFFFF0883324F658, 0xFFFFF0883324EE90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
company: Logitech Inc.
description: Logitech Kernel Audio Improvement Filter Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.).
Google query: lvrs64.sys Logitech Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Sun 15/11/2020 22:25:27 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111620-20281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x139 (0x3, 0xFFFFF4887A767180, 0xFFFFF4887A7670D8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 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:
lvrs64.sys (Logitech Kernel Audio Improvement Filter Driver, Logitech Inc.)
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.
- Messages : 31250
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne

Re: Besoin d'aide pour des BSOD à répétition
file path: C:\WINDOWS\system32\drivers\lvrs64.sys
product: Logitech Webcam Software
date de Novembre 2020
Le dernier .dmp du 02/05/2021 ne met en évidence que un "This is likely to be caused by a hardware problem. "
Donc sans parler US, tu vois que c'est un problème matériel.... RAM ! HDD/SSD faut tester et changer , par contre ça demande des pièces de rechange pour tester, une sauvegarde des docs/favoris navigateur au préalable.
Donc c'est pas simple, le forum ne peut que t'aiguiller mais ne peut intervenir physiquement sur ta machine.
product: Logitech Webcam Software
date de Novembre 2020
Le dernier .dmp du 02/05/2021 ne met en évidence que un "This is likely to be caused by a hardware problem. "
Donc sans parler US, tu vois que c'est un problème matériel.... RAM ! HDD/SSD faut tester et changer , par contre ça demande des pièces de rechange pour tester, une sauvegarde des docs/favoris navigateur au préalable.
Donc c'est pas simple, le forum ne peut que t'aiguiller mais ne peut intervenir physiquement sur ta machine.
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/

- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Merci.
Mais comment je peux tester ces éléments ?
A noter que j'ai maintenant eu des dizaines de BSOD depuis le 2 mai, dont un gros paquet aujourd'hui... C'est bizarre que le dernier événement enregistré remonte au 2 mai, non ?
Mais comment je peux tester ces éléments ?
A noter que j'ai maintenant eu des dizaines de BSOD depuis le 2 mai, dont un gros paquet aujourd'hui... C'est bizarre que le dernier événement enregistré remonte au 2 mai, non ?
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Je vais déjà déconnecter mes deux SSD externes, voir si ça résout le pb. > Ca peut être cela ?
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Les BSOD se poursuivent même avec les deux SSD externes débranchés.
(Après, je ne sais pas si les débrancher suffit.)
(Après, je ne sais pas si les débrancher suffit.)
- Messages : 111007
- Inscription : 10 sept. 2005 13:57
Re: Besoin d'aide pour des BSOD à répétition
Il y a quoi de branché sur ce PC en USB etc ?
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
➔ Comment protéger son PC des virus
➔ Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11
Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
➔ Comment protéger son PC des virus
➔ Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11
Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
- Messages : 174
- Inscription : 17 janv. 2008 10:54
- Localisation : France
Re: Besoin d'aide pour des BSOD à répétition
Bonsoir,
Ben un tas de trucs : deux disques durs, une webcam, un écran externe, un micro, la box, deux imprimantes, 2 hubs pour relier tout ça... Et ponctuellement une clé USB ou un phone à charger.
Ben un tas de trucs : deux disques durs, une webcam, un écran externe, un micro, la box, deux imprimantes, 2 hubs pour relier tout ça... Et ponctuellement une clé USB ou un phone à charger.
-
- Sujets similaires
- Réponses
- Vues
- Dernier message
-
- 1 Réponses
- 160 Vues
-
Dernier message par Malekal_morte
-
- 6 Réponses
- 101 Vues
-
Dernier message par toda
-
- 8 Réponses
- 210 Vues
-
Dernier message par Malekal_morte
-
- 1 Réponses
- 60 Vues
-
Dernier message par Parisien_entraide
-
- 1 Réponses
- 42 Vues
-
Dernier message par Malekal_morte