Itein

Pour NVIDIA, dans la liste des programmes je ne trouve pas. J'ai que NVIDIA Driver. Dans le gestionnaire, j'ai toujours la souris et en plus maintenant j'ai "Périphérique inconnu" et "NVIDIA Controller RAID" (Au démarrage on me demande de trouver les pilotes, mais ça ne marche, j'avais déjà eu ça, on avait régler le problème en installer le Chipset NVIDIA. Sinon le rapport : Cijoint.fr - Service gratuit de dépôt de fichiers

Voilà tout est fait pour les BSOD, comme je te l'ai dit, ils viennent à l'improviste.

J'ai NVIDIA Pilote graphique 267.21 et NVIDIA Driver je commence par lequel ?

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 ?

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

Bonjour, J'ai désactivé NVIDIA NVRAID via : "Démarrer > Exécuter > msconfig > Démarrage" Je n'ai pas trouvé les autres. ----------------- 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+

Je suis crevé désolé je vais dormir, désolé de te faire coucher si tard :/ . A demain ! Bonne nuit (Merci pour tout)

- Imprimante - Webcam - Souris (sans fil) - Clavier - Wifi

Juste parfois c'est bizarre lorsque je lance un fichier ou autre j'ai une fenêtre cmd qui s'ouvre et qui se referme environ 2sec après. Normal ?

Rapport : © CJoint.com, 2010

D'ailleurs dis-moi ce que je peux supprimer s'il te plaît, y a plein de trucs bizarres^^ http://i20.servimg.com/u/f20/11/10/64/81/dokd10.jpg

Bah, rien du tout... http://i20.servimg.com/u/f20/11/10/64/81/ffff11.jpg Quand je l'ouvre avec un bloc note il est vide et il fait 0 ko regardes sa taille.

Oula, pendant l'analyse j'ai eu un BSOD (IRQL_GT_ZERO_AT_SYSTEM_SERVICE) BCCode : 4A (je crois) Ensuite au démarrage j'ai : http://i20.servimg.com/u/f20/11/10/64/81/rrrr10.jpg Je fais ce qu'il dit ?

Non je ne l'ai pas redémarré, l'erreur était pendant l'installation. Je viens de le redémarrer j'ai aucune erreur là. Il faut juste que je configure la restauration, mais on la fera quand l'ordinateur sera stable. Pour les BSOD c'est toujours au démarrage de l'ordinateur après qu'il s'est reposé environ 2h. Ensuite quand je le redémarrage ça enchaîne environ 4-5 BSOD (Environ 30min) et ensuite je peux utiliser l'ordinateur, donc je le laisse allumer car il devient "stable".

Toi aussi t'es tête en l'air apparemment, c'est post #130 pas #30 Acer eLock Management est installé Bravo à toi l'icône est revenue et ça marche ! (Pendant l'installation j'ai eu "CreateDirectory ERROR, reason 21", mais ça a continué ) J'avais fait C:\Acer\Empowering Technology\eRecovery/eRecovery.exe aucune réponse mais maintenant c'est bon !

Excuse-moi je suis un peu tête en l'air aujourd'hui Les services étaient déjà dans le bon mode. Verifier.exe j'ai fais supprimer, mais je n'ai pas fais le reste : L'icône est toujours grise oui. J'ai fais l'analyse pour Microsoft aucune erreur. Sinon tous les services marchent sauf Acer eRecovery et je n'ai pas de Acer eLock Management Application Qui y a-t-il post #30 ?

Nop, cela ne faisait rien.

J'ai pas trop compris le but, mais bon pour C:\Acer\Empowering Technology\ePerformance\MemCheck.exe C:\Acer\Empowering Technology\eSettings\Service\capuserv.exe Ca me fait "" a cessé de fonctionner.

Pour Acer Framework, j'ai dejà la version supérieur, pour installer la tienne je dois désinstaller la mienne je le fais ?

Désolé je n'ai pas les codes d'erreurs pour les BDOS, c'est aller trop rapidement. ------------------------ Pour l'observateur : http://i20.servimg.com/u/f20/11/10/64/81/looki10.jpg Pour les erreurs d'évènement : (24 maintenant) ID / Source / Journal / Nombre d'erreurs - 10 / WMI / Application / 9 - 1002 / Dhcp-Client / Système / 9 - 6008 / Eventlog / Système / 6 Voilà ---------------- Pour vérifier.exe je suis allé dessus j'ai fais tout ce que tu m'as dis mais pour "sélectionner automatiquement tous les pilotes installé sur cet ordinateur", y avait pas "suivant" mais "terminer" alors j'ai cliqué sur terminé et ensuite pour appliquer les fonctions j'ai du redémarrer et rien pas de rapport. ------------- Les BSOD sont revenus hier matin, et je n'ai pas changé les services. ----------------- eRecovery, Oui je l'ai formaté en faisant au démarrage de l'ordi "Alt Gr + F8" cela reviens au même que le eRecovery c'est la même chose mais au démarrage. ----------------- Sinon dans le gestionnaire j'ai que la souris.

J'ai eu droit encore à "IRQL_NO_LESS_EQUAL" et à "BUGCODE_USB_DRIVER".

Bonjour, Pour Recovery cela n'a pas marché. Pour l'observateur d'évènement, y a pas une sorte de rapport ? Car là y a pas mal de choses : http://i20.servimg.com/u/f20/11/10/64/81/okok10.jpg http://i20.servimg.com/u/f20/11/10/64/81/okioki10.jpg

Pour l'icône Acer eRecovery Management : http://i20.servimg.com/u/f20/11/10/64/81/ffff10.jpg Avec ma souris, lorsque je vais dessus, l'icône est barrée (Comme cela Ø) Pour la restauration j'ai pas très bien compris. Regarde : http://i20.servimg.com/u/f20/11/10/64/81/dddd10.jpg ---------------------------- BSOD : J'ai eu trop à un BAD_POOL_CALLER , BCCode : C2 (Il me semble) Et à un autre aucun nom mais erreur 8E (Je crois) et y avais marqué le nom d'un fichier : nvmdx32.sys A toute

Bonjour... Alors pour les disques : http://i20.servimg.com/u/f20/11/10/64/81/joli10.jpg Non je n'ai pas fait de CD de restauration. Et je n'ai pas supprimer de partition. Tu dis : Quel gestionnaire ? Pour Démarrer >> (Tous les Programmes) >> Empowering Technology >> clique sur Acer eRecovery Management. Le programme eRecovery ne se lance pas. J'ai eRAgent, mais pas Monitor. Sinon... Les BSOD reviennent... Je suis en train de mettre les mis à jours esperons que les BSOD ne reviennent pas...

Merci pour le lien Sinon juste deux petites choses encore : - Donc tout ce qui est sur Windows Update c'est toujours la bonne version donc je mets toujours à jour ? (Ex : Là j'ai deux mises à jours facultatives, je les mets ? ; 1. " nVidia - Display, Other hardware - NVIDIA GeForce 7100 / NVIDIA nForce 630i Taille du téléchargement : 115.1 Mo Vous devrez éventuellement redémarrer l’ordinateur pour que cette mise à jour soit appliquée. Type de mise à jour : Facultatif nVidia Display, Other hardware software update released in February, 2011 Plus d'informations : http://winqual.microsoft.com/support/?driverid=20426923 Aide et support : http://support.microsoft.com/select/?target=hub'>http://support.microsoft.com/select/?target=hub " 2. "NVIDIA driver update for NVIDIA nForce Networking Controller Taille du téléchargement : 380 Ko Vous devrez éventuellement redémarrer l’ordinateur pour que cette mise à jour soit appliquée. Type de mise à jour : Facultatif This driver was provided by NVIDIA for support of NVIDIA nForce Networking Controller Plus d'informations : http://winqual.microsoft.com/support/?driverid=2104 Aide et support : http://support.microsoft.com/select/?target=hub ") ------------------------------------------------------ - Et finalement pour Acer eRecovery Management que fait-on ?