Reseaux introuvables / bad pool header
Fermé
Mikefunk
Messages postés
3
Date d'inscription
jeudi 9 juillet 2020
Statut
Membre
Dernière intervention
12 juillet 2020
-
9 juil. 2020 à 23:23
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 13 juil. 2020 à 11:27
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 13 juil. 2020 à 11:27
A voir également:
- Reseaux introuvables / bad pool header
- Musique very bad trip - Forum Cinéma / Télé
- Matthias utilise les réseaux sociaux. que doit-il faire dans chacune des situations suivantes ? - Forum Cloud
- Dns probe finished bad config ✓ - Forum DNS
- Musique dans very bad trip ✓ - Forum Cinéma / Télé
- 666-4 - bad request - 666-4 ✓ - Forum Réseaux sociaux
7 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 659
Modifié le 10 juil. 2020 à 10:55
Modifié le 10 juil. 2020 à 10:55
Salut,
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 659
10 juil. 2020 à 10:56
10 juil. 2020 à 10:56
Tu as le Wifi qui plante et la carte Nvidia, pas bon tout ça.
Suivre ce lien : Résoudre BSOD sur Windows
Suivre ce lien : Résoudre BSOD sur Windows
- Faire une vérification SFC et DISM
- Faire une mise à jour des pilotes avec DriversCloud : Mettre à jour ses pilotes avec driversCloud
- faire le memtest
- Vérifier la température de l'ordinateur.
- Vérifier les disques avec CrystalDiskInfo
Mikefunk
Messages postés
3
Date d'inscription
jeudi 9 juillet 2020
Statut
Membre
Dernière intervention
12 juillet 2020
11 juil. 2020 à 22:14
11 juil. 2020 à 22:14
Je sauve mes musiques au propre et je fais ça. Je reviens vers toi rapidement.
Un grand merci encore !
Un grand merci encore !
Je viens donc d'installer un nouveau pilote pour la carte wifi realtek et un nouveau driver également pour la nvidia.
Cependant, toujours pas de wifi, j'ai fait un whocrashed à l'instant, et le dernier crash qu'il me trouve date du 9 juillet (nous sommes le 11)
D'ou peut donc venir ce probleme de reseaux introuvables ?
Cordialement
Voici le dernier whocrashed
System Information (local)
--------------------------------------------------------------------------------
Computer name: MIKE
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire E5-771G, Acer, EA70_HB
CPU: GenuineIntel Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8509480960 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD47F1)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-22750-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1AE996)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 17:05:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-28781-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE000D3E64000, 0x16C0, 0x5744303137324C2D)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 12:31:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-22250-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE0016E5E8000, 0x19E0, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 00:56:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-26234-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE00202757000, 0x2190, 0x205744303137324C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 23/06/2020 01:48:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062320-22484-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE000180F7000, 0xFFFFE000180F7E30, 0x4E30000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Sun 21/06/2020 03:18:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062120-23843-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE00166EBD000, 0xFFFFE00166EBDF00, 0x4F00000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Fri 12/06/2020 21:02:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-24187-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE001DFAAC000, 0xFFFFE001DFAACB50, 0x4B50000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 09/06/2020 00:09:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060920-12796-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE001EF5D7000, 0x1600, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\060420-18984-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation)
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.
Cependant, toujours pas de wifi, j'ai fait un whocrashed à l'instant, et le dernier crash qu'il me trouve date du 9 juillet (nous sommes le 11)
D'ou peut donc venir ce probleme de reseaux introuvables ?
Cordialement
Voici le dernier whocrashed
System Information (local)
--------------------------------------------------------------------------------
Computer name: MIKE
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire E5-771G, Acer, EA70_HB
CPU: GenuineIntel Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8509480960 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD47F1)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-22750-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1AE996)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 390.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 390.65
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 17:05:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-28781-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE000D3E64000, 0x16C0, 0x5744303137324C2D)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 12:31:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-22250-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE0016E5E8000, 0x19E0, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 00:56:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-26234-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE00202757000, 0x2190, 0x205744303137324C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 23/06/2020 01:48:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062320-22484-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE000180F7000, 0xFFFFE000180F7E30, 0x4E30000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Sun 21/06/2020 03:18:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062120-23843-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE00166EBD000, 0xFFFFE00166EBDF00, 0x4F00000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Fri 12/06/2020 21:02:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-24187-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE001DFAAC000, 0xFFFFE001DFAACB50, 0x4B50000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 09/06/2020 00:09:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060920-12796-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE001EF5D7000, 0x1600, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\060420-18984-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.65 , NVIDIA Corporation)
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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 659
12 juil. 2020 à 10:26
12 juil. 2020 à 10:26
Dans le gestionnaire de périphériques, la carte Wifi est en erreur ?
Tu peux lancer une vérification et réparation SFC
Clic droit sur le menu démarrer et invite de commandes (admin)
Dans la fenêtre noire de l'invite de commandes, saisir sfc /scannow dans la fenêtre.
Voir cette image : https://www.malekal.com/wp-content/uploads/ouvrir-invite-commandes-administrateur-Windows10.gif
Cela doit te dire que la protection a détecté des éléments endommagés, qu'il faut redémarrer pour pouvoir les corriger. A ce moment là, redémarre.
Ensuite, lance une Réparation DISM
Toujours dans la fenêtre de l'invite de commandes, passez ces deux commandes successivement.
DISM /Online /Cleanup-image /Scanhealth
DISM /Online /Cleanup-image /Restorehealth
(attention, il y a un espace devant chaque commande commençant par / /Online /Cleanup-image etc)
Vérifie que l'analyse et réparation arrive bien au bout et aucune erreur ne s'affiche.
Redémarre l'ordinateur.
Tentez à nouveau de passer les mises à jour, si cela continue de planter, passe à l'étape suivante.
Tu peux lancer une vérification et réparation SFC
Clic droit sur le menu démarrer et invite de commandes (admin)
Dans la fenêtre noire de l'invite de commandes, saisir sfc /scannow dans la fenêtre.
Voir cette image : https://www.malekal.com/wp-content/uploads/ouvrir-invite-commandes-administrateur-Windows10.gif
Cela doit te dire que la protection a détecté des éléments endommagés, qu'il faut redémarrer pour pouvoir les corriger. A ce moment là, redémarre.
Ensuite, lance une Réparation DISM
Toujours dans la fenêtre de l'invite de commandes, passez ces deux commandes successivement.
DISM /Online /Cleanup-image /Scanhealth
DISM /Online /Cleanup-image /Restorehealth
(attention, il y a un espace devant chaque commande commençant par / /Online /Cleanup-image etc)
Vérifie que l'analyse et réparation arrive bien au bout et aucune erreur ne s'affiche.
Redémarre l'ordinateur.
Tentez à nouveau de passer les mises à jour, si cela continue de planter, passe à l'étape suivante.
Mikefunk
Messages postés
3
Date d'inscription
jeudi 9 juillet 2020
Statut
Membre
Dernière intervention
12 juillet 2020
12 juil. 2020 à 23:36
12 juil. 2020 à 23:36
Bonjour et pardon pour le retard , et merci encore de ton aide !
Je viens de faite toutes ces operations et les reseaux sont toujours introuvables.
Tout a ete fait correctement, aucune erreur n’a ete trouvée.
De plus, la carte realtek fonctionne bien dans les gestionnaires de peripherique !
Etrange etrange !
Je viens de faite toutes ces operations et les reseaux sont toujours introuvables.
Tout a ete fait correctement, aucune erreur n’a ete trouvée.
De plus, la carte realtek fonctionne bien dans les gestionnaires de peripherique !
Etrange etrange !
Je pense avoir trouvé, j'ai telecharge sur le site realtek le driver (en mandarin le site par contre, pas évident !), téléchargé le driver win 8 PCI sur mon bureau, et je l'ai installé manuellement dans le gestionnaire de peripherique, ça a l'air detre OK !
Je croise les doigts, ton site est dans les favoris !
Je croise les doigts, ton site est dans les favoris !
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 659
13 juil. 2020 à 11:27
13 juil. 2020 à 11:27
ok vois si ça passe =)
10 juil. 2020 à 10:43
J'ai fait ce que tu m'as dit, voici le rapport, il semblerait que ma carte nvidia soit a l'origine de ce plantage :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: MIKE
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire E5-771G, Acer, EA70_HB
CPU: GenuineIntel Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8509480960 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD47F1)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.91
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.91
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.91 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 23:17:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-22750-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1AE996)
Bugcheck code: 0xC2 (0x7, 0x1200, 0xDDEB6869, 0xFFFFE000BD2BB010)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.91
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.91
Bug check description: This indicates that the current thread is making a bad pool request.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.91 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_CALLER
On Thu 09/07/2020 17:05:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-28781-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE000D3E64000, 0x16C0, 0x5744303137324C2D)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 12:31:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-22250-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE0016E5E8000, 0x19E0, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Wed 08/07/2020 00:56:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070820-26234-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE00202757000, 0x2190, 0x205744303137324C)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 23/06/2020 01:48:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062320-22484-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE000180F7000, 0xFFFFE000180F7E30, 0x4E30000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Sun 21/06/2020 03:18:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062120-23843-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE00166EBD000, 0xFFFFE00166EBDF00, 0x4F00000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Fri 12/06/2020 21:02:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061320-24187-01.dmp
This was probably caused by the following module: nwifi.sys (nwifi+0x9982)
Bugcheck code: 0x19 (0x20, 0xFFFFE001DFAAC000, 0xFFFFE001DFAACB50, 0x4B50000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nwifi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de miniport WiFi natif
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Tue 09/06/2020 00:09:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060920-12796-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x91C43)
Bugcheck code: 0x19 (0x21, 0xFFFFE001EF5D7000, 0x1600, 0x6573205744303137)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that a pool header is corrupt.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\060420-18984-01.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.91 , NVIDIA Corporation)
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.
Que dois-je faire maintenant ?
Une procédure simple ou délicate ?
Grand merci, cordialement