Itein

Bonjour, Toujours des BSOD... Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 17.06.2011 13:16:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061711-03.dmp This was probably caused by the following module: Unknown (0xFFFFFFFF89610889) Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF89610888, 0xFFFFFFFF81F01B60, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M On Fri 17.06.2011 13:16:29 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0xFFFFFFFF81ED9B3F) Bugcheck code: 0x8E (0xFFFFFFFF80000003, 0xFFFFFFFF89610888, 0xFFFFFFFF81F01B60, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED Bug check description: This bug check indicates that a kernel-mode application 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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED On Fri 17.06.2011 13:03:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061711-02.dmp This was probably caused by the following module: elock2fsctldriver.sys (eLock2FSCTLDriver+0x1335) Bugcheck code: 0x19 (0x20, 0xFFFFFFFF9CE8359A, 0xFFFFFFFF9CE8427A, 0x399C0000) Error: BAD_POOL_HEADER 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 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. 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. BAD_POOL_HEADER On Fri 17.06.2011 13:02:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061711-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x1EDAE0) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82035AE0, 0xFFFFFFFF8BC87B80, 0xFFFFFFFF8BC8787C) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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. 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 15.06.2011 08:15:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061511-03.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0xCDB3F) Bugcheck code: 0x19 (0x20, 0xFFFFFFFF9DFDC8B8, 0xFFFFFFFF9DFDC8E8, 0x8060011) Error: BAD_POOL_HEADER 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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 15.06.2011 07:58:34 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061511-02.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x44D91) Bugcheck code: 0x18 (0xFFFFFFFF841CBE38, 0xFFFFFFFF9DEBC0E8, 0x1, 0x1) Error: REFERENCE_BY_POINTER 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 the reference count of an object is illegal for the current state of the object. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 15.06.2011 07:56:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061511-01.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x8F55) Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF81EFC82A) 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 Tue 14.06.2011 13:58:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061411-02.dmp This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x35CD7) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F181CD7, 0xFFFFFFFF8C23BBD4, 0xFFFFFFFF8C23B8D0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\dxgkrnl.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics Kernel 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. 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 Tue 14.06.2011 13:45:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061411-01.dmp This was probably caused by the following module: volsnap.sys (volsnap+0x2759) Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF89D1A758, 0xFFFFFFFF8059DE24, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 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 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. 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 -------------------------------------------------------------------------------- 9 crash dumps have been found and analyzed. 3 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: elock2fsctldriver.sys (ELock File System Filter Driver, Acer, Inc.) 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+

Oui par Windows Update.

Re, Rapport de DelFix : # DelFix v8.0 - Rapport créé le 16/06/2011 à 21:02 # Mis à jour le 01/06/11 à 13h par Xplode # Système d'exploitation : Windows Vista Home Premium (32 bits) [version 6.0.6002] Service Pack 2 # Nom d'utilisateur : Nathan - PC-DE-NATHAN (Administrateur) # Exécuté depuis : C:\Users\Nathan\Desktop\delfix.exe # Option [suppression] ~~~~~~ Dossier(s) ~~~~~~ Supprimé : C:\Program Files\ZHPDiag Supprimé : C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ZHP ~~~~~~ Fichier(s) ~~~~~~ Supprimé : C:\PhysicalDisk0_MBR.bin Supprimé : C:\ZHPExportRegistry-13.06.2011-23-07-35.txt Supprimé : C:\Users\Nathan\Desktop\ZHPDiag2.exe Supprimé : C:\Users\Public\Desktop\MBRCheck.lnk Supprimé : C:\Users\Public\Desktop\ZHPDiag.lnk Supprimé : C:\Users\Public\Desktop\ZHPFix.lnk ~~~~~~ Registre ~~~~~~ Clé Supprimée : HKLM\Software\OldTimer Tools Clé Supprimée : HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\ZHPDiag_is1 ~~~~~~ Autre ~~~~~~ -> Prefetch vidé ########## EOF - "C:\DelFixSuppr.txt" - [1111 octets] ########## J'ai mis Java à jour. J'ai toujours la mise à jour facultative : - nVidia - Display, Other hardware - NVIDIA GeForce 7100 / NVIDIA nForce 630i Je la met ? Pour les BSOD je te dirai demain. A+

Bonjour tomtom95, Pour le test, je l'ai refait, c'est ok. Dans le rapport aucun problème détecté maintenant. J'ai installé. Sur le test INTEL, il n'y a toujours pas de Chipster à installé. Pour DirectX je fais quoi ? Bonne journée !

Bonsoir tomtom95, ... Je ne suis pas sûr, mais je pense que non. D'origine . J'ai fais le test en amélioré, sauf que à 98% il a redémarré . Au début de test, il me disait déjà que j'avais problèmes des matériels. Mais je n'ai pas le rapport, car il a redémarré. Je vais essayé de le refaire plus tard. J'installe celui-ci ? http://www.testmater...-1r7g-4361.html J'ai déjà fais le test INTEL, http://i20.servimg.com/u/f20/11/10/64/81/ijoefk10.jpg http://i20.servimg.com/u/f20/11/10/64/81/fffffv10.jpg Bonne soirée

Bonsoir, C'est ok, c'est juste que après "INTEGRATED PERIPHERALS", il y avait "Onboard Device Setup" et après tout était enabled, sauf "AZALIA AUDIO" qui est en "Internal codec + External codec" et "MACO LAN BOOT ROM" qui est en "Auto" (enabled n'était pas en choix pour ces deux). Pour C'est fait ! Non, j'ai DirectX 11. Je n'ai pas fait cette partie, car il me semble que mon ordinateur n'a pas les mêmes caractéristiques. Par exemple au lieu de 2.4 GHz moi j'ai 2.5 GHz, sinon le processeur par exactement le même. Je te laisse voir : http://i20.servimg.com/u/f20/11/10/64/81/gvoekd10.jpg C'est fait. Voilà tu peux tout voir ici : http://i20.servimg.com/u/f20/11/10/64/81/fokewf10.jpg A+ Itein

Bonjour tomtom95 ! J'ai eu deux BSOD aujourd'hui. Je n'ai pas pu finir la défragmentation, c'était trop long. Mes BSOD : Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 14.06.2011 13:58:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061411-02.dmp This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x35CD7) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F181CD7, 0xFFFFFFFF8C23BBD4, 0xFFFFFFFF8C23B8D0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\dxgkrnl.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: DirectX Graphics Kernel 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. 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 Tue 14.06.2011 13:58:23 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF8F181CD7, 0xFFFFFFFF8C23BBD4, 0xFFFFFFFF8C23B8D0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 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: ntkrpamp.exe . Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED On Tue 14.06.2011 13:45:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061411-01.dmp This was probably caused by the following module: volsnap.sys (volsnap+0x2759) Bugcheck code: 0x1000008E (0xFFFFFFFF80000003, 0xFFFFFFFF89D1A758, 0xFFFFFFFF8059DE24, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M 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 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. 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 Mon 13.06.2011 19:18:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061311-02.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x62C4) Bugcheck code: 0xD1 (0x37889D3, 0x2, 0x0, 0xFFFFFFFF8DA0E2C4) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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 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. 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 Mon 13.06.2011 14:30:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061311-01.dmp This was probably caused by the following module: Unknown (0xFFFFFFFF81E4DFD9) Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF81EA8264) 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: Unknown . Google query: Unknown IRQL_NOT_LESS_OR_EQUAL On Sun 12.06.2011 16:20:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061211-01.dmp This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D) Bugcheck code: 0xD1 (0x486DC, 0x2, 0x0, 0xFFFFFFFF8DA105BC) 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 -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 6 crash dumps have been found and analyzed. 3 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.) unknown ntkrpamp.exe 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 toute

D'accord. Bonne soirée à toi aussi A demain !

Oui c'est bon. et pour la veille prolongée aussi. Voilà le WhoCrashed que tu voulais : Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 13.06.2011 19:18:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061311-02.dmp This was probably caused by the following module: usbport.sys (USBPORT+0x62C4) Bugcheck code: 0xD1 (0x37889D3, 0x2, 0x0, 0xFFFFFFFF8DA0E2C4) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL 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 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. 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 Mon 13.06.2011 14:30:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061311-01.dmp This was probably caused by the following module: Unknown (0xFFFFFFFF81E4DFD9) Bugcheck code: 0xA (0x0, 0x1B, 0x1, 0xFFFFFFFF81EA8264) 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: Unknown . Google query: Unknown IRQL_NOT_LESS_OR_EQUAL On Sun 12.06.2011 16:20:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061211-01.dmp This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D) Bugcheck code: 0xD1 (0x486DC, 0x2, 0x0, 0xFFFFFFFF8DA105BC) 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 -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 3 crash dumps have been found and analyzed. 2 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.) 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.

Rapport : Rapport de ZHPFix 1.12.3288 par Nicolas Coolman, Update du 29/05/2011 Fichier d'export Registre : Run by Nathan at 13.06.2011 23:07:35 Windows Vista Home Premium Edition, 32-bit Service Pack 2 (Build 6002) Web site : ZHPFix Fix de rapport ========== Clé(s) du Registre ========== O42 - Logiciel: eReg - (.Logitech, Inc..) [HKLM] -- {3EE9BCAE-E9A9-45E5-9B1C-83A4D357E05C} => Désinstallation logicielle annulée par l'utilisateur ou désinstallation partielle! HKCU\Software\Logitech => Clé supprimée avec succès HKLM\Software\Logitech => Clé supprimée avec succès ========== Dossier(s) ========== C:\Users\Nathan\AppData\Roaming\Logitech => Supprimé et mis en quarantaine Dossiers temporaires Windows supprimés: 94 ========== Fichier(s) ========== c:\users\nathan\appdata\roaming\microsoft\windows\start menu\programs\startup\logitech . enregistrement du produit.lnk => Fichier absent c:\program files\common files\logishrd\ereg\setpoint\ereg.exe => Supprimé et mis en quarantaine c:\windows\system32\drivers\lnonpnp.sys => Supprimé et mis en quarantaine c:\windows\system32\drivers\l8042mou.sys => Supprimé et mis en quarantaine c:\windows\system32\drivers\lhidfilt.sys => Supprimé et mis en quarantaine c:\windows\system32\drivers\lmoufilt.sys => Supprimé et mis en quarantaine c:\windows\system32\drivers\lmouke.sys => Supprimé et mis en quarantaine Fichiers temporaires Windows supprimés : 340 ========== Récapitulatif ========== 3 : Clé(s) du Registre 2 : Dossier(s) 8 : Fichier(s) End of the scan J'installe le pilote

Re Pour Logitech Set Point, je l'ai désinstallé quand tu me l'avais demandé, il n'est pas dans les programmes. J'ai toujours suivi tes indications... Je télécharge que même Logitech SetPoint Cordless Desktop MX 3200 Laser ? Même si apparemment il n'est pas désinstallé ? Pour la mise en veille prolongée, je ne sais pas. Je ne le laisse jamais en veille normal, donc la prolongée encore moins.

Oui pour IE , msconfig et memory c'est bon. Pour Netgear j'ai fais. Pour la sagem non je n'en ai pas. J'avais déjà remarqué cela, si tu regardes, Sagem XN-720S et Netgear WN111V2 est la même. Ils sont identiques. Pour le SYSDM.CPL pour C'était déjà comme cela. Pour Je n'ai pas Image mémoire complète. Il est déjà configuré en : Image mémoire du noyau Et le fichier d'image mémoire est : %SystemRoot%\MEMORY.DMP

Mise à jour driver : - Nvidia Pilote High Definition Audio HDMI nForce/ION (drivers 1.00.00.59 WHQL) - Nvidia GeForce 6/7/8/9/100/200/300/400/500/ION (drivers 275.33 WHQL) - Netgear WN111 V2 (drivers 3.1 WHQL) - Sagemcom XN-720S (drivers WHQL) - Netgear WNDA3100 V1 (drivers 3.0.0.2 WHQL) - Netgear WNA1000 (drivers 2.0 WHQL) - Logitech SetPoint (drivers 6.22.24 WHQL) - Logitech SetPoint Bluetooth (drivers 4.80.154 WHQL) - Logitech SetPoint Cordless Desktop MX 3200 Laser/EasyCall Desktop (drivers 4.00 WHQL) - Nvidia nForce 5/6/7 (drivers 15.53 WHQL) - Nvidia nForce 4/6/7/9 IGP (drivers 15.49 WHQL) - Nvidia ION (drivers 20.14 WHQL) - Nvidia nForce 4 (drivers 15.23 WHQL) - Nvidia nForce Professional 2000/3000 (drivers 15.16 WHQL) - Realtek RTS5101/RTS5111/RTS5116 (drivers 6.1.7600.30126 WHQL) Pour Je ne trouve pas.

Bonjour, Voilà le chkdsk est fini Encore des BSOD. Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 13.06.2011 10:26:03 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF81E80D45, 0xFFFFFFFFAD4A1904, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED Bug check description: This bug check indicates that a kernel-mode application 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: Unknown . Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED On Sun 12.06.2011 16:20:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061211-01.dmp This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D) Bugcheck code: 0xD1 (0x486DC, 0x2, 0x0, 0xFFFFFFFF8DA105BC) 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 -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 2 crash dumps have been found and analyzed. 2 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.) 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

Bonne nuit

Attends enfaite : D'abord je suis passé en Power Member Plus sérieusement, dans le logiciel qui s'installe, sous l'onglet "About" j'ai : Device : Driver Version : 3.1.0.108 Smart Wireless Utility : Version : 3.0.0.3 Rapport : Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 12.06.2011 16:20:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061211-01.dmp This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D) Bugcheck code: 0xD1 (0x486DC, 0x2, 0x0, 0xFFFFFFFF8DA105BC) 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 -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 1 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: wn111v2v.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.) 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.

Alors, je suis allé : Démarrer > Tous les programmes > NETGEAR WN111v2 Adapter > Uninstall NETGEAR WN111v2 Software Je suis les instructions, il est désinstallé. Il n'est plus dans le gestionnaire. Puis je lance ton installateur, tout est ok. Il est installé, mais dans le gestionnaire il est en 3.1.0.108...

Bon, je l'ai désinstallé et installé l'autre, sauf que dans le gestionnaire, j'ai toujours la 3.1.0.108.

Pour les BSOD, ça ne marche pas comme ça. Il fait des BSOD lorsque je le laisse longtemps éteint et ensuite je le démarrage. Au démarrage, j'arrive à être en moyenne 4min sur mon bureau, ensuite il BSOD en chaîne. Après 1-7 BSOD, l'ordinateur se "stabilise" et je peux allé dessus. Donc pour les BSOD, je te dirai demain si j'en ai eu. Pour le pilote Atheros : http://i20.servimg.com/u/f20/11/10/64/81/dfefe10.jpg

Ok, j'ai mis le Controller. Il me semble que j'ai jamais eu de mise à jour pour ça. Ça = Atheros Extensible Wireless LAN device driver

Pour le Wifi, il n'y a aucune mise à jour. Dans Update, j'ai : - NVIDIA driver update for NVIDIA nForce Networking Controller - nVidia - Display, Other hardware - NVIDIA GeForce 7100 / NVIDIA nForce 630i

Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 12.06.2011 16:20:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\Mini061211-01.dmp This was probably caused by the following module: wn111v2v.sys (WN111v2v+0x12C8D) Bugcheck code: 0xD1 (0x486DC, 0x2, 0x0, 0xFFFFFFFF8DA105BC) 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 -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 1 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: wn111v2v.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.) 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.

Ton lien, c'est celui 15355...

J'ai tout mis normalement...

Dans REVO aussi j'ai que NVIDIA Driver.