[Résolu] Désinfection PC Acer Aspire M3641

[tomtom95]

NON

Je suis sur le rapport

 

Tu n'a pas répondu pour les branchements des supports:

Alors imprimante HP,

Ton NETGEAR pour le wifi

Ta CAM Camera sony

Quoi d'autre ???

[Itein]

- Imprimante

- Webcam

- Souris (sans fil)

- Clavier

- Wifi

[Itein]

Je suis crevé désolé je vais dormir, désolé de te faire coucher si tard :/ .

 

A demain !

 

Bonne nuit

 

(Merci pour tout)

[tomtom95]

Oui merci Bonne nuit

 

J'ai encore pas mal de chose a vérifié.

 

C'est NVIDIA NVRAID qui crée ce problème de BSOD

Pour l'instant tu peux Désactive du démarrage:

NVRaidService (nvraidservice.exe)

HP Software Update

Windows Welcome Center

 

Vide aussi tes Prefetch sauf Layout.ini ,le pc va être un peu plus long que d'habitude au redémarrage du pc,c'est normal.

 

Un petit Complément d'analyse stp

Télécharge WhoCrashed 3.01 sur ton bureau

Clique sur l'icone

Pour Vista et seven

Ferme toutes les applications ouvertes

Désactive tes défenses (anti-virus,anti-spyware)

fais un clique droit sur l'icône et exécute en tant qu'administrateur

Note que Report soit sélectionner.

Clique sur Analyse

Le rapport s’affiche sous la rubrique Analysis et donne aussi des informations dans la rubrique Conclusion

Post le rapport

 

Info WhoCrashed

 

 

A+

Modifié le 11 juin 2011 par tomtom95

[Itein]

Bonjour,

 

C'est NVIDIA NVRAID qui crée ce problème de BSOD

Pour l'instant tu peux Désactive du démarrage:

NVRaidService (nvraidservice.exe)

HP Software Update

Windows Welcome Center

J'ai désactivé NVIDIA NVRAID via : "Démarrer > Exécuter > msconfig > Démarrage" Je n'ai pas trouvé les autres.

 

 

-----------------

 

Vide aussi tes Prefetch sauf Layout.ini ,le pc va être un peu plus long que d'habitude au redémarrage du pc,c'est normal.

 

Je suis allé : "C:\Windows\Prefetch" mais j'ai pas mal de fichier je vide tout ? sûr ?

 

--------------------

 

Pour le WhoCrashed :

 

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Sat 11.06.2011 14:29:52 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-08.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x1025)

Bugcheck code: 0xFE (0x6, 0xFFFFFFFF86D489AA, 0x63706458, 0x0)

Error: BUGCODE_USB_DRIVER

file path: C:\Windows\system32\drivers\usbport.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: USB 1.1 & 2.0 Port Driver

Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sat 11.06.2011 14:29:52 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x1025)

Bugcheck code: 0xFE (0x6, 0xFFFFFFFF86D489AA, 0x63706458, 0x0)

Error: BUGCODE_USB_DRIVER

file path: C:\Windows\system32\drivers\usbport.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: USB 1.1 & 2.0 Port Driver

Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sat 11.06.2011 13:50:08 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-07.dmp

This was probably caused by the following module: usbport.sys (USBPORT+0x8F55)

Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF81F2E82C)

Error: DRIVER_CORRUPTED_EXPOOL

file path: C:\Windows\system32\drivers\usbport.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: USB 1.1 & 2.0 Port Driver

Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.

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.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Sat 11.06.2011 13:47:19 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-06.dmp

This was probably caused by the following module: nvstor32.sys (nvstor32+0xA40D)

Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF807E140C, 0xFFFFFFFF8059DEA0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\drivers\nvstor32.sys

product: NVIDIA nForce SATA Driver

company: NVIDIA Corporation

description: NVIDIA® nForce Sata Performance Driver

Bug check description: This indicates that a kernel-mode program 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: nvstor32.sys (NVIDIA® nForce Sata Performance Driver, NVIDIA Corporation).

Google query: nvstor32.sys NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

 

On Sat 11.06.2011 13:44:28 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-05.dmp

This was probably caused by the following module: elock2fsctldriver.sys (eLock2FSCTLDriver+0x1335)

Bugcheck code: 0xF7 (0xFFFFFFFFCF73A387, 0xFFFFFFFF89C46A92, 0x763B956D, 0x0)

Error: DRIVER_OVERRAN_STACK_BUFFER

file path: C:\Windows\system32\drivers\elock2fsctldriver.sys

product: ELock File System Filter Driver

company: Acer, Inc.

description: ELock File System Filter Driver

Bug check description: This indicates that a driver has overrun a stack-based buffer.

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: elock2fsctldriver.sys (ELock File System Filter Driver, Acer, Inc.).

Google query: elock2fsctldriver.sys Acer, Inc. DRIVER_OVERRAN_STACK_BUFFER

 

 

 

 

On Sat 11.06.2011 13:41:47 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-04.dmp

This was probably caused by the following module: Unknown (0xFFFFFFFF81ED7B3F)

Bugcheck code: 0x119 (0x1, 0xA01, 0xA02, 0xA02)

Error: VIDEO_SCHEDULER_INTERNAL_ERROR

Bug check description: This indicates that the video scheduler has detected a fatal violation.

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: Unknown .

Google query: Unknown VIDEO_SCHEDULER_INTERNAL_ERROR

 

 

 

 

On Sat 11.06.2011 13:37:16 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-03.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)

Bugcheck code: 0xA (0x720069, 0x1B, 0x1, 0xFFFFFFFF81EC55DA)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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 11.06.2011 11:07:20 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-02.dmp

This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x13D3F)

Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFFFFF8F11AD3F)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\wn111v2v.sys

product: Driver for Atheros OTUS Network Adapter

company: Atheros Communications, Inc.

description: Atheros Extensible Wireless LAN device 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 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: wn111v2v.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).

Google query: wn111v2v.sys Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

 

 

 

On Fri 10.06.2011 22:37:21 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061111-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4AFCD)

Bugcheck code: 0x4A (0xFFFFFFFF8209A478, 0xFFFFFFFFC0000001, 0x0, 0x0)

Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Fri 10.06.2011 15:16:57 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061011-05.dmp

This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D)

Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF81F0998C)

Error: DRIVER_CORRUPTED_EXPOOL

file path: C:\Windows\system32\drivers\wn111v2v.sys

product: Driver for Atheros OTUS Network Adapter

company: Atheros Communications, Inc.

description: Atheros Extensible Wireless LAN device driver

Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.

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.

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: wn111v2v.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).

Google query: wn111v2v.sys Atheros Communications, Inc. DRIVER_CORRUPTED_EXPOOL

 

 

 

 

On Fri 10.06.2011 14:56:00 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061011-04.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)

Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF81EC6264)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntkrnlpa.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 Fri 10.06.2011 14:52:41 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061011-03.dmp

This was probably caused by the following module: volsnap.sys (volsnap+0x1056)

Bugcheck code: 0xC1 (0xFFFFFFFFADC3AFD8, 0xFFFFFFFFADC3A080, 0xDB402C, 0x23)

Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION

file path: C:\Windows\system32\drivers\volsnap.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Pilote de cliché instantané du volume

Bug check description: This indicates that the driver wrote to an invalid section of the special pool.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Fri 10.06.2011 14:50:08 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061011-02.dmp

This was probably caused by the following module: fltmgr.sys (fltmgr+0x2AB8)

Bugcheck code: 0x19 (0x20, 0xFFFFFFFF879B0280, 0xFFFFFFFF879B02B8, 0xFFFFFFFF88070005)

Error: BAD_POOL_HEADER

file path: C:\Windows\system32\drivers\fltmgr.sys

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Gestionnaire de filtres de système de fichiers Microsoft

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.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

On Fri 10.06.2011 10:48:43 GMT your computer crashed

crash dump file: C:\Windows\Minidump\Mini061011-01.dmp

This was probably caused by the following module: storport.sys (storport+0x1047)

Bugcheck code: 0x44 (0xFFFFFFFF8816C008, 0xE7A, 0x0, 0x0)

Error: MULTIPLE_IRP_COMPLETE_REQUESTS

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 driver has tried to requested an IRP be completed that is already complete.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

14 crash dumps have been found and analyzed. 5 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:

 

wn111v2v.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

 

elock2fsctldriver.sys (ELock File System Filter Driver, Acer, Inc.)

 

nvstor32.sys (NVIDIA® nForce Sata Performance Driver, NVIDIA Corporation)

 

unknown

 

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.

 

 

A+

Modifié le 11 juin 2011 par Itein

[tomtom95]

Bonjour

 

Désoler pour le retard

 

Oui pour les Prefetch sauf Layout.ini

 

Ta web Cam effectivement pose problème avec le pilote usbport.sys.et le port USB2 qui n'est pas installer correctement.

Quel est la marque de ta Webcam ?

 

Plusieurs infos stp

Quel est la version de Logitech SetPoint, et tu as quoi comme périphérique lier avec (clavier, souris) ???

 

Donne-moi la marque de ta carte mère (motherboard)

 

Dans le gestionnaire des services regarde si le service Carte à puce est bien en automatique.

 

Va dans le gestionnaire des périphériques, clique en haut sur la barre AFFICHAGE, et sur affichés les périphériques cachés.

Donne moi le nom des pilotes et la version de:

Atheros Wireless Extensible pilote de périphérique LAN

Netgear pilote wifi

 

Clique sur contrôleurs ATA /ATAPI IDE

Clique droit sur IDE principale >> propriété

Onglet paramètres avancés

Pour périphérique (0) et (1)

Mettre type de périphérique en auto-détection

En dessous DMA si disponible clique sur ok

Même chose pour IDE secondaire

Dans les périphériques systèmes

Déroule la petit croix dit moi quel est le chipset installer

(EX: INTEL 4 séris chipset PCI express)

Autrement dans les pilotes non Plug-and-Play a tu des pilotes en défaut ?

 

 

Ensuite Fait cette manip:

Débranche tout tes branchements qui sont sur ton pc (imprimante, Webcam, Clavier, Wifi) sauf la souris pour l'instant

Redémarrer le pc

Branche ensuite le clavier, s’il demande installer un pilote accepte le changement

Même chose pour le wifi, après la webcam, et enfin l'imprimante allumer branche-là sur le pc.

 

Dit moi des changements qui sont effectués.

 

A+

[Itein]

Bonjour,

 

Oki pour les Prefetch sauf que tout revient, y a un dossier nommé "ReadyBoot" je le delete aussi ?

 

Ma Webcam cam est une Trust WB-6250X.

 

Pour le SetPoint c'est que ma souris :

 

Version du Control Center 6.20.50

Version du pilote 5.20.51

 

Je vois ou la marque de ma carte mère ?

 

Pour le service Carte à Puce il était en Manuel je l'ai mis en Automatique.

 

Va dans le gestionnaire des périphériques, clique en haut sur la barre AFFICHAGE, et sur affichés les périphériques cachés.

Donne moi le nom des pilotes et la version de:

Atheros Wireless Extensible pilote de périphérique LAN

Netgear pilote wifi

 

http://i20.servimg.com/u/f20/11/10/64/81/ffplf10.jpg Tu peux aussi voir pour les contrôleurs ATA j'ai pas IDE principale, mais Canal IDE

 

Et dans ce canal je vois que : http://i20.servimg.com/u/f20/11/10/64/81/dddd11.jpg

 

Pour le chipset je ne vois rien... http://i20.servimg.com/u/f20/11/10/64/81/lolo10.jpg

 

Rien dans les Plug-and-Play d'anormal.

 

Pour :

Ensuite Fait cette manip:

Débranche tout tes branchements qui sont sur ton pc (imprimante, Webcam, Clavier, Wifi) sauf la souris pour l'instant

Redémarrer le pc

Branche ensuite le clavier, s’il demande installer un pilote accepte le changement

Même chose pour le wifi, après la webcam, et enfin l'imprimante allumer branche-là sur le pc.

 

Rien de nouveau, pour Clavier et Wepcam l'installeur de pilote me dit que c'est Prêt à être utiliser. Pour les deux autres rien.

[tomtom95]

Normal que les Prefetch ,je voulais simplement faire la puge des Prefetch inutile.

 

Pour repartir sur de bonne base désinstaller ,et réinstaller l'ensemble de tes pilotes.

Les pilotes qui pose problème :

Atheros Extensible Wireless LAN device driver

NVIDIA nForce Sata Performance Driver

ELock File System Filter Driver, Acer

 

 

Il s'agit ici de plusieurs bug, difficile à trouver dans ton cas

Lorsque un pilote qui tente de terminer son propre paquet deux fois n'est généralement pas la source du problème.

Mais Plus vraisemblablement, deux pilotes séparer chaqu'un croient qu'ils possèdent le paquet,

et chacun a tenté de le compléter.la premier demande reussi,parcontre la seconde échoue,et tu te retrouve avec une BSOD.

 

On vois sur ta capture le driverInterface qui est en défaut.

Le DMA n'est pas installer.

Conflit avec les pilotes de ta carte graphique

 

 

 

Le pilote Trust c'est bien celui-ci

http://www.trust.com/products/productdrivers.aspx?artnr=15355

 

RangeMax Wireless-N USB Adapter WN111v2 >> Version 3.0

http://www.wireless-driver.com/netgear-wn111v2-windows-driver-software/

 

Pour ta souris Logitech SetPoint.

Actuelement tu as Logitech SetPoint 6.20

Qui gére clavier,souris,webcam

On vois sur le rapport que c'est Microsoft qui prend en charge ta souris

Driver: (mouclass) . (.Microsoft Corporation - Pilote de la classe Souris.) - C:\Windows\System32\DRIVERS\mouclass.sys

 

http://www.logitech.com/en-gb/support-downloads/downloads/software-hidden/devices/3131?section=downloads&bit=&osid=13

 

Le pilote carte graphique

installe ce pilote GeForce 7100 / NVIDIA nForce 630i

http://www.nvidia.fr/object/winvista_x86_163.75_fr.html

 

Je vois ou la marque de ma carte mère ?

 

l'ID du fabricant de la CM dans ton BIOS ID, la ligne qui apparaît en bas à gauche quand tu démarre ton ordinateur

 

Bon je te conseil utiliser revo

Voir tuto http://www.6ma.fr/tuto/revo+uninstaller+pour+desinstaller+des+programmes-354

Télécharge la version gratuite v1.92

http://www.revouninstaller.com/revo_uninstaller_free_download.html

 

Commence par nvidia,désinstalle le raid PUIS les pilotes nvidia

au redémarrage de l'ordinateur refus l'installation par défaut

et va clique en tant qu'administrateursur l'exécutable du pilote que tu aura télécharger

Installation faite redémarre le pc .

 

Bonne soirée

 

A+

[Itein]

Je ne comprends pas très bien ce que je dois faire en premier. Pourrais-tu éditer ton message et me mettre en ordre les choses à faire s'il te plaît ?

[tomtom95]

Sur mon dernier post utilise REVO

 

1)Commence par nvidia,désinstalle le raid

PUIS

2)les pilotes nvidia

au redémarrage de l'ordinateur refus l'installation par défaut

et clique en tant qu'administrateur sur l'exécutable du pilote que tu aura télécharger

Installation faite redémarre le pc .

 

3)Désinstalle Logitech SetPoint 6.20

 

Sinon mets a jour les pilotes

4)Trust,

5) RangeMax Wireless

il vont désinstaller l'ancien pour mettre le nouveau pilote.

Télécharge les pilotes

Clique droit pour exécuter en tant qu'admin sur les exécutables

 

lorsque c'est fait dit moi si tu as encore des BSOD

 

A++