Actualités
26/04/24
Les pilotes AMD Software 24.4.1 sont en ligne pour Manor Lords
25/04/24
Crucial publie l'ISO du firmware M3CR046 pour certains SSD Crucial MX500
24/04/24
La version finale de rekordbox 7.0 publiée par Pioneer DJ en mai 2024 ?
16/04/24
Le logiciel Portable SSD Software tire sa révérence pour les SSD USB Samsung
16/04/24
Pilote NVIDIA GeForce Game Ready 552.22 pour Manor Lords et No Rest for the Wicked
05/04/24
Un nouveau firmware pour la webcam Logitech C920
04/04/24
Drivers NVIDIA GeForce 552.12 pour Call of Duty Season 3 et Diablo IV RT
29/03/24
Options+ 1.68 pour le clavier Logitech Signature Slim K950 et la souris Signature Plus M750
25/03/24
La chaîne CORSAIR iCUE LINK supporte désormais jusqu'à 24 périphériques
[MAJ]
25/03/24
Samsung publie Magician 8.1 pour les SSD, clés USB et cartes mémoire
Fichiers
26/04/24
NVIDIA GeForce Experience 3.28.0.412
26/04/24
Nikon D7500 1.12
26/04/24
Nikon D850 1.31
26/04/24
Insta360 X4 1.0.8
26/04/24
Insta360 Ace Pro 1.0.51
26/04/24
Fractal Audio FM9-Edit 1.02.11
26/04/24
Fractal Audio Axe-Edit III 1.13.20
26/04/24
AMD AMD Software : Cloud Edition Gaming Update 24.4.1 WHQL
26/04/24
AMD Install Manager 24.4.1
26/04/24
AMD AMD Software : Adrenalin Edition Combined GCN/RDNA 24.4.1 WHQL
Aller sur les autres Forums
Recherche de drivers, bios et firmwares
Problèmes avec les drivers, bios et firmwares
Matériel
Systèmes d'exploitation et logiciels
Réseaux, Internet et téléphonie
Jeux vidéo
Overclocking
Petites annonces
Autres
Commentaires des news
Accueil
/
Problèmes avec les drivers, bios et firmwares
Rechercher
S'inscrire ou s'identifier
FAQ
Identification
Nom d'utilisateur
Mot de passe
Recevez vos identifiants
par e-mail
si vous les avez oubliés.
Inscrivez-vous
si vous n'êtes pas encore membre de TousLesDrivers.com.
Modifier le message
Titre du message:
Message
Bonjour, Ce forum m'ayant servi à plusieurs reprise, je me suis inscrit en espérant que vous ayez une solution ! Un problème plus qu'ennuyant ! Voilà depuis hier soir qu'un BSOD apparaît dès le démarrage... En parcourant les forums j'ai vu qu'une des causes peut provenir des de la carte graphique Hier soir en lançant le mode sans échec, j'ai effectué une décontamination (RAS), désactivé la mise à jour du pilote de ma carte graphique (Nvidia GEFORCE GTX 660M), puis remis à jour, j'ai redémarré et miracle, le PC tourné normalement, ce matin pareil ! Cette après midi arrivant au travail, j'allume le PC et au démarrage, je retombe sur le même BSOD, j'ai donc retenté la manipulation sur le pilote, rien à faire, toujours le même message... :??: Après une pause clope, je retente, et le PC tournait à nouveau correctement, j'en ai profité pour installer l'avant dernière version de la carte graphique (la dernière version étant une beta) et depuis impossible de faire tourner le PC en dehors du mode sans échec... Ma config : Windows 7 Intel Core I7 Nvidia GEFORCE GTX 660M RAM 4GB On m'a conseillé de lancer WhoCrashed afin de mieux détecté le problème, voici le rapport : [i][b]Crash Dump Analysis [/b] -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. [b]On Wed 09/08/2017 18:19:52 your computer crashed [/b] crash dump file: C:\Windows\Minidump\080917-22464-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40) Bugcheck code: 0x19 (0x20, 0xFFFFFA800372A210, 0xFFFFFA800372A230, 0x4020009) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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. [b]On Wed 09/08/2017 18:19:52 your computer crashed[/b] crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0xB92F) Bugcheck code: 0x19 (0x20, 0xFFFFFA800372A210, 0xFFFFFA800372A230, 0x4020009) Error: BAD_POOL_HEADER file path: C:\Windows\system32\drivers\aswsp.sys product: avast! Antivirus company: AVAST Software description: avast! self protection module Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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: aswsp.sys (avast! self protection module, AVAST Software). Google query: AVAST Software BAD_POOL_HEADER [b]On Wed 09/08/2017 18:18:16 your computer crashed [/b] crash dump file: C:\Windows\Minidump\080917-26598-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40) Bugcheck code: 0x19 (0x20, 0xFFFFFA800958FCD0, 0xFFFFFA800958FCF0, 0x402000C) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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. [b]On Wed 09/08/2017 15:40:10 your computer crashed[/b] crash dump file: C:\Windows\Minidump\080917-23883-02.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40) Bugcheck code: 0x19 (0x20, 0xFFFFFA80081F88D0, 0xFFFFFA80081F88F0, 0x402000C) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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. [b]On Wed 09/08/2017 15:35:43 your computer crashed [/b] crash dump file: C:\Windows\Minidump\080917-23727-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70E40) Bugcheck code: 0x19 (0x20, 0xFFFFFA8009D1D7B0, 0xFFFFFA8009D1D7D0, 0x4020008) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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. [b]Conclusion [/b] -------------------------------------------------------------------------------- 34 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: netwns64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation) aswsp.sys (avast! self protection module, AVAST Software)[/i] Si vous avez une solution, je suis à votre écoute ! Merci d'avoir pris le temps de me lire A bientôt
Insérer des éléments
Plus de smileys
Lien N°1
/
Lien N°2
/
Puce
/
Gras
/
Italique
/
Souligné
/
Barré