Aide écran bleu. Options

[darkenrale]

Bonjour/ Bonsoir.

Il n'y a pas longtemps, j'ai installé NETGEAR adaptateur USB sans fil N300 wna3100 avec le CD d'installation. Donc j'ai mis le CD→ Installer le pilote Windows→ j'ai cliqué sur "oui"→ l'installation c'est faite→ ils me demande d'insérez l'adaptateur USB sans fil dans mon ordinateur. Et de cliquer sur ok pour continuer→ donc je la met→ j'appuie sur Ok→Apres une page s'ouvre et me dis: L'installation est terminé→ je clique sur terminer→ je ferme la page NETGEAR→ je me connecte a mon réseau mais ca ne fonctionne pas→ puis un écran bleu apparaît et redémarra mon ordinateur. Pouvez vous m'aidez sil vous plaît?


Cordialement darkenrale.

[princemalko]

Bonjour,

Problème de pilote / compatibilité ? As tu regardé si une version du pilote était disponible sur cette page ?

[darkenrale]

Bonjour,

Problème de pilote / compatibilité ? As tu regardé si une version du pilote était disponible sur cette page ?

J'ai Windows 7 et c'est compatible avec.
En faite, ce probleme a commencer au départ quand j'ai du reintisialisé le systhème (disque dur) a son etat originel.
Puis, j'ai du reinstaller ce NETGEAR wna 3100 et sa me fais l'écran bleu depuis...
Mais si il y a une nouvelle version, comment dois-je faire pour la mettre sur l'installation?

[princemalko]

Si tu as un écran bleu, je te conseil fortement d'analyser le message à partir de l'excellent WhoCrashed. Il permettra d'isoler le driver qui pose problème.

[darkenrale]

Si tu as un écran bleu, je te conseil fortement d'analyser le message à partir de l'excellent WhoCrashed. Il permettra d'isoler le driver qui pose problème.

Ok, mais je fais comment pour l'analysé? Sachant que mon ordinateur et innutilisable.
Actuellement, je suis sur un ordinateur qui n'est pas le mien.

[princemalko]

Tu démarres en "Mode sans échec".

[darkenrale]

Tu démarres en "Mode sans échec".

Ok, merci.

[darkenrale]

Si tu as un écran bleu, je te conseil fortement d'analyser le message à partir de l'excellent WhoCrashed. Il permettra d'isoler le driver qui pose problème.

Apres avoir fais l'analyse avec WhoCrashed, sa me met sa:


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 01/07/2012 15:22:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-23259-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AD1365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 01/07/2012 15:22:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: symnets.sys (SYMNETS+0x27ED1)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AD1365)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: symnets.sys .
Google query: symnets.sys IRQL_NOT_LESS_OR_EQUAL




On Sun 01/07/2012 15:15:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-23946-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AD3365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 01/07/2012 12:41:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-19188-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A88365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 01/07/2012 12:25:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070112-19172-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AD9365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 21:50:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-21294-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A8E365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 21:29:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-20623-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A83365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 21:20:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-22542-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002ADD365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 21:13:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-30451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002ADA365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 20:57:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-22401-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A87365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 30/06/2012 20:52:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063012-23462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AC3365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 28/06/2012 20:09:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062812-23400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A96365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 28/06/2012 17:00:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062812-23790-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A81365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 27/06/2012 16:17:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-22854-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002AC6365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 27/06/2012 16:09:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062712-20904-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80002A85365)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Conclusion
--------------------------------------------------------------------------------

22 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

symnets.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.






Je dois faire quoi après?

[princemalko]

Dans les rapports d'erreurs, je ne vois pas de référence "directe" au pilote Netgear, mais une grosse instabilité du noyau de ton Windows (ntoskrnl.exe). Pourquoi as tu été obligé de réinitialiser ton système ? un soucis particulier ?

PS : Il y a également eu un plantage lié à un produit Norton, mais vu le nombre de plantage du au Noyau, cela parait anecdotique.

[darkenrale]

Dans les rapports d'erreurs, je ne vois pas de référence "directe" au pilote Netgear, mais une grosse instabilité du noyau de ton Windows (ntoskrnl.exe). Pourquoi as tu été obligé de réinitialiser ton système ? un soucis particulier ?

PS : Il y a également eu un plantage lié à un produit Norton, mais vu le nombre de plantage du au Noyau, cela parait anecdotique.

J'ai du reinitialisé mon systhème parce que mon ordinateur ramait beaucoup trop. Et c'est mon frère qui ma dis de le faire.
Pourtant, c'est a cause de ce pilote, car c'est lorsque je le met que l'écran bleu apparait, je peux mettre n'importe quoi d'autre a part la clef USB netgear wna3100 ca ne le fera pas.

[darkenrale]

Dans les rapports d'erreurs, je ne vois pas de référence "directe" au pilote Netgear, mais une grosse instabilité du noyau de ton Windows (ntoskrnl.exe). Pourquoi as tu été obligé de réinitialiser ton système ? un soucis particulier ?

PS : Il y a également eu un plantage lié à un produit Norton, mais vu le nombre de plantage du au Noyau, cela parait anecdotique.

Devrais-je le ramené là où je l'ai acheté?

[princemalko]

A voir, mais si ça fonctionnait avant, et que ça ne fonctionne plus depuis la réinstall, je chercherais à savoir pourquoi. Peut être une mise à jour des pilotes de la carte mère permettrais de résoudre ce soucis.

[darkenrale]

A voir, mais si ça fonctionnait avant, et que ça ne fonctionne plus depuis la réinstall, je chercherais à savoir pourquoi. Peut être une mise à jour des pilotes de la carte mère permettrais de résoudre ce soucis.

Oui, avant sa fonctionnais. Mais depuis que j'ai reinitialisé le systheme, sa me fait sa.
Comment je fais pour la mise a jour de la carte mère?

[princemalko]

Faut que tu cherches du coté du constructeur de ton PC. S'il s'agit d'un assemblé, faut trouver la marque et le modèle de la carte mère, et se rendre sur le site de cette marque.

[darkenrale]

Faut que tu cherches du coté du constructeur de ton PC. S'il s'agit d'un assemblé, faut trouver la marque et le modèle de la carte mère, et se rendre sur le site de cette marque.

Excuse moi, mais ce que tu me dis là est du chinois pour moi. Je ne comprend pas: coté constructeur/ d'un assemblé/ carte mère.

J'ai honte...

[princemalko]

Dans ce cas, je pense que le plus simple est de faire appel à un réparateur, ou la personne qui t'as vendu le PC, car ça va être assez compliqué de te guider si tu ne peux pas faire la différence entre un PC constructeur (DELL, Acer, Asus, Toshiba...) et un PC assemblé.

[darkenrale]

Dans ce cas, je pense que le plus simple est de faire appel à un réparateur, ou la personne qui t'as vendu le PC, car ça va être assez compliqué de te guider si tu ne peux pas faire la différence entre un PC constructeur (DELL, Acer, Asus, Toshiba...) et un PC assemblé.

Ok, bein merci quand même. J'irais dans le magasin où je l'ai acheter.