Problèmes blue screens et carte reseau
Fermé
Lola.rb
Messages postés
3
Date d'inscription
mardi 16 novembre 2021
Statut
Membre
Dernière intervention
17 novembre 2021
-
16 nov. 2021 à 23:11
billmaxime Messages postés 50255 Date d'inscription dimanche 20 novembre 2011 Statut Contributeur Dernière intervention 15 septembre 2024 - 17 nov. 2021 à 23:57
billmaxime Messages postés 50255 Date d'inscription dimanche 20 novembre 2011 Statut Contributeur Dernière intervention 15 septembre 2024 - 17 nov. 2021 à 23:57
A voir également:
- Problèmes blue screens et carte reseau
- Carte d'identité - Guide
- Blue screen - Guide
- Pile carte mere - Guide
- Entrer les informations d'identification reseau - Guide
- Carte bancaire machine à laver ✓ - Forum Matériel & Système
3 réponses
billmaxime
Messages postés
50255
Date d'inscription
dimanche 20 novembre 2011
Statut
Contributeur
Dernière intervention
15 septembre 2024
5 988
16 nov. 2021 à 23:38
16 nov. 2021 à 23:38
salut
télécharge Whocrashed sur ton bureau --> clique ici
exécute le en tant qu'administrateur (clic droit) pour l'installer
poste le rapport après analyse via 1 copier/coller
si tu as des questions...
@+
télécharge Whocrashed sur ton bureau --> clique ici
exécute le en tant qu'administrateur (clic droit) pour l'installer
poste le rapport après analyse via 1 copier/coller
si tu as des questions...
@+
Lola.rb
Messages postés
3
Date d'inscription
mardi 16 novembre 2021
Statut
Membre
Dernière intervention
17 novembre 2021
17 nov. 2021 à 16:55
17 nov. 2021 à 16:55
System Information (local)
Computer name: DESKTOP-OJ40MTU
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\Windows
Hardware: 81W1, LENOVO, LNVNB161216
CPU: AuthenticAMD AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 8664, level: 23
8 logical processors, active mask: 255
RAM: 6312697856 bytes (5,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 11/11/2021 00:43:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111121-9343-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF80036E3BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF80036E3BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 11/11/2021 14:39:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111121-9421-01.dmp
This was probably caused by the following module: qcamain10x64.sys (0xFFFFF801455A2577)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801455A2577, 0xFFFFD309CBC7D508, 0xFFFFD309CBC7CD40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\qcamain10x64.sys
product: Driver for Qualcomm Atheros QCA61x4/QCA9377 Network Adapter
company: Qualcomm Atheros, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device 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: qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, Inc.).
Google query: qcamain10x64.sys Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 11/11/2021 14:39:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: qcamain10x64.sys (0xFFFFF801455A2577)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF801455A2577, 0xFFFFD309CBC7D508, 0xFFFFD309CBC7CD40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\qcamain10x64.sys
product: Driver for Qualcomm Atheros QCA61x4/QCA9377 Network Adapter
company: Qualcomm Atheros, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, Inc.).
Google query: qcamain10x64.sys Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 11/11/2021 00:50:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\NDIS-20211111-0050.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisReleaseNicActive+0xAC7)
Bugcheck code: 0x15E (0x25, 0x22, 0xFFFF918F311F9308, 0x0)
Error: BUGCODE_NDIS_DRIVER_LIVE_DUMP
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: NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
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 10/11/2021 22:42:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111021-10281-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF80242C3BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF80242C3BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Tue 09/11/2021 19:06:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110921-8562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x9F (0x3, 0xFFFFE507730778D0, 0xFFFFF8014DA6E850, 0xFFFFE5077198FAA0)
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 Mon 08/11/2021 15:15:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110821-10343-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8053A03BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF8053A03BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Computer name: DESKTOP-OJ40MTU
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\Windows
Hardware: 81W1, LENOVO, LNVNB161216
CPU: AuthenticAMD AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 8664, level: 23
8 logical processors, active mask: 255
RAM: 6312697856 bytes (5,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 11/11/2021 00:43:16 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111121-9343-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF80036E3BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF80036E3BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 11/11/2021 14:39:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111121-9421-01.dmp
This was probably caused by the following module: qcamain10x64.sys (0xFFFFF801455A2577)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801455A2577, 0xFFFFD309CBC7D508, 0xFFFFD309CBC7CD40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\qcamain10x64.sys
product: Driver for Qualcomm Atheros QCA61x4/QCA9377 Network Adapter
company: Qualcomm Atheros, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device 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: qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, Inc.).
Google query: qcamain10x64.sys Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Thu 11/11/2021 14:39:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: qcamain10x64.sys (0xFFFFF801455A2577)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF801455A2577, 0xFFFFD309CBC7D508, 0xFFFFD309CBC7CD40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\qcamain10x64.sys
product: Driver for Qualcomm Atheros QCA61x4/QCA9377 Network Adapter
company: Qualcomm Atheros, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, Inc.).
Google query: qcamain10x64.sys Qualcomm Atheros, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 11/11/2021 00:50:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\NDIS-20211111-0050.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisReleaseNicActive+0xAC7)
Bugcheck code: 0x15E (0x25, 0x22, 0xFFFF918F311F9308, 0x0)
Error: BUGCODE_NDIS_DRIVER_LIVE_DUMP
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: NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
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 10/11/2021 22:42:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111021-10281-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF80242C3BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF80242C3BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Tue 09/11/2021 19:06:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110921-8562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71B0)
Bugcheck code: 0x9F (0x3, 0xFFFFE507730778D0, 0xFFFFF8014DA6E850, 0xFFFFE5077198FAA0)
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 Mon 08/11/2021 15:15:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\110821-10343-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF8053A03BCB2)
Bugcheck code: 0xD1 (0x18, 0x2, 0x0, 0xFFFFF8053A03BCB2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Lola.rb
Messages postés
3
Date d'inscription
mardi 16 novembre 2021
Statut
Membre
Dernière intervention
17 novembre 2021
17 nov. 2021 à 16:56
17 nov. 2021 à 16:56
Conclusion
7 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:
qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, 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.
7 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:
qcamain10x64.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros, 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.
billmaxime
Messages postés
50255
Date d'inscription
dimanche 20 novembre 2011
Statut
Contributeur
Dernière intervention
15 septembre 2024
5 988
17 nov. 2021 à 23:57
17 nov. 2021 à 23:57
salut
Mon père l'a donc donner à réparer a son ami qui a dit que le disque dur ne fonctionne plus et qui vas le changer avec certains autres matériels afin de rendre l'ordinateur plus performant.
tu sais exactement ce qui a été changé sur le pc?
teste ceci:
1) démarre le pc en mode sans échec
pour réaliser la manipulaton:
quand le pc est démarré, redémarre le en maintenant la touche SHIFT/Majuscule enfoncée sans la relâcher
PS: si tu as 1 écran bleu (BSOD), clique sur les touches --> CTRL+ALT+DEL(delete)/SUPP(supprime)
en bas à droite de la page, clique sur le bouton Marche/Arrêt --> redémarrer
tu devrais arriver sur les options avancées
quand tu seras sur la page des options avancées clique sur:
Dépannage
Options avancées
Paramètres --> changer le comportement de Windows au démarrage
Redémarrer
dans la page qui s'ouvre, clique sur le chiffre 4 du pavé numérique, ou sur les touches en haut du clavier
le pc va redémarrer en mode sans échec, et ne devrait pas te faire de BSOD (écran bleu)
là, tu cliques droit sur Démarrer --> Gestionnaire de périphériques
donne moi l'identifiant du périphérique Wifi --> Qualcomm Atheros Extensible Wireless LAN device driver --> clique ici
PS: la 1ère ligne suffit, poste la via 1 copier/coller dans ta réponse
exemple --> PCI\VEN_14E4&DEV_1690&SUBSYS_80001025&REV_01
2) clique droit sur --> Qualcomm Atheros Extensible Wireless LAN device driver --> Désactiver l'appareil
PS: tu as 1 port Ethernet sur le pc?
si oui, branche le câble Ethernet (RJ45) et redémarre le pc
dis-moi si tu as toujours tes soucis de BSOD (écran bleu) après le rédémarrage du pc
si tu as des questions...
@+
Mon père l'a donc donner à réparer a son ami qui a dit que le disque dur ne fonctionne plus et qui vas le changer avec certains autres matériels afin de rendre l'ordinateur plus performant.
tu sais exactement ce qui a été changé sur le pc?
teste ceci:
1) démarre le pc en mode sans échec
pour réaliser la manipulaton:
quand le pc est démarré, redémarre le en maintenant la touche SHIFT/Majuscule enfoncée sans la relâcher
PS: si tu as 1 écran bleu (BSOD), clique sur les touches --> CTRL+ALT+DEL(delete)/SUPP(supprime)
en bas à droite de la page, clique sur le bouton Marche/Arrêt --> redémarrer
tu devrais arriver sur les options avancées
quand tu seras sur la page des options avancées clique sur:
Dépannage
Options avancées
Paramètres --> changer le comportement de Windows au démarrage
Redémarrer
dans la page qui s'ouvre, clique sur le chiffre 4 du pavé numérique, ou sur les touches en haut du clavier
le pc va redémarrer en mode sans échec, et ne devrait pas te faire de BSOD (écran bleu)
là, tu cliques droit sur Démarrer --> Gestionnaire de périphériques
donne moi l'identifiant du périphérique Wifi --> Qualcomm Atheros Extensible Wireless LAN device driver --> clique ici
PS: la 1ère ligne suffit, poste la via 1 copier/coller dans ta réponse
exemple --> PCI\VEN_14E4&DEV_1690&SUBSYS_80001025&REV_01
2) clique droit sur --> Qualcomm Atheros Extensible Wireless LAN device driver --> Désactiver l'appareil
PS: tu as 1 port Ethernet sur le pc?
si oui, branche le câble Ethernet (RJ45) et redémarre le pc
dis-moi si tu as toujours tes soucis de BSOD (écran bleu) après le rédémarrage du pc
si tu as des questions...
@+
