Bonjour à tous...
 
HELP !
 
Depuis ce matin, mon PC qui marchait bien me fait un BSOD au démarrage de windows 7, un peu après l'apparition du bureau, et toujours au même moment.
 
J'ai tenté des trucs en vain :
 
- un memtest (RAS)
- un chkdsk (RAS)
- un démarrage avec une seule barette de RAM, puis l'autre.
- débrancher tous les périphériques, même clavier et souris, et périphériques SATA (sauf le disque principal, évidemment)
- désactiver l'USB dans le BIOS
- désinstaller les programmes récents
- changer l'alim
- débrancher la carte graphique
- restaurer à une date antérieure (la restauration a merdé et effacé tous les points de restauration...)
 
 
L'ordi fonctionne parfaitement en mode SANS ECHEC avec réseau.
 
Ma config :
- windows 7 64 bits familial
- carte mère Gigabyte GA-Z77-D3H
- disque principal : SSD SAMSUNG
 
 
 
Merci d'avance.

Je vous poste le rapport Whocrashed :
System Information (local)
Computer name: ANDRE-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., Z77-D3H
CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8543629312 bytes total
 
 
 
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Thu 20/07/2017 18:12:13 your computer crashed
crash dump file: C:\Windows\Minidump\072017-18517-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88005F06710, 0xFFFFF9804A666DC0, 0xFFFFFA800AE90D90)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Thu 20/07/2017 18:12:13 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: lgvirhid.sys (LGVirHid+0x624)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88005F06710, 0xFFFFF9804A666DC0, 0xFFFFFA800AE90D90)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\lgvirhid.sys
Bug check description: This is the bug check code for all Driver Verifier
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: lgvirhid.sys .
Google query: lgvirhid.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION
 
 
 
On Thu 20/07/2017 17:51:08 your computer crashed
crash dump file: C:\Windows\Minidump\072017-36660-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88008767710, 0xFFFFF9803C4BEDC0, 0xFFFFFA800AB2DD90)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Thu 20/07/2017 16:11:06 your computer crashed
crash dump file: C:\Windows\Minidump\072017-11434-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88005927710, 0xFFFFF9804AAA4DC0, 0xFFFFFA8004759D90)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 Thu 20/07/2017 16:07:24 your computer crashed
crash dump file: C:\Windows\Minidump\072017-21777-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0x2710)
Bugcheck code: 0xC9 (0x220, 0xFFFFF88005A02710, 0xFFFFF9806F2CADC0, 0xFFFFFA80048921C0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.
 
 
 
 
Conclusion
18 crash dumps have been found and analyzed. Only 5 are included in this report. 2 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:
 
ysusb64.sys (Yamaha Steinberg USB Driver, Yamaha Corporation)
lgvirhid.sys
 
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.

A la vue du rapport de Whocrashed, ton souci se situe au niveau des drivers des périphériques d'entrée.
Plus spécifiquement du coté des drivers Yamaha Steinberg et Logitech.
 
Essaye de réinstaller les drivers de ces périphériques.
Sinon essaye de démarrer en débranchant ces périphériques.

Merci de ta réponse.
J'ai essayé de tout débrancher (même la souris) et de désinstaller les pilotes (notamment Yamaha), mais rien n'y fait.
 
 
- De nouveaux écrans bleus, un peu tout le temps. Quand je branche ma carte son, par exemple.
 
- L'USB 3 ne fonctionne plus, les pilotes de la carte graphique ne sont plus reconnus, la carte son non plus.
 
- Le PC rame (démarrage en 2 minutes au lieu de 30 secondes), la mise à jour des pilotes échoue.
 
- L'antivirus refuse de démarrer, même après réinstallation. Windows defender ne veut pas prendre le relai :"ce programme est bloqué par une stratégie de groupe".
 
- Plusieurs programmes d'installation m'affichent des messages d'erreur.
 
- J'ai essayé de réinstaller les pilotes, et c'est même pire : windows ne démarre plus qu'en mode Sans échec, j'ai donc désinstallé les pilotes.
 
 
 
J'avais fait un gros scan antivirus hier, avant la catastrophe, car je trouvais que le PC ramait, et que le processus svchost.exe prenait trop d'UC et de RAM.
 
Avast : RAS
Adwcleaner et Antimalware m'ont retiré deux ou trois trucs qui n'avaient pas l'air méchant et ça a été le début de la catastrophe.
 
 
Une autre idée ?
J'ai l'impression que je ne couperai pas à un gros formatage...

Le formatage a résolu le problème. Merci de votre aide.

bonjour
j'ai le meme soucis au boulot
tous les PC HP sous windows 7 ont le meme symptome depuis ce matin