Aller au contenu
  • Pas encore inscrit ?

    Pourquoi ne pas vous inscrire ? C'est simple, rapide et gratuit.
    Pour en savoir plus, lisez Les avantages de l'inscription... et la Charte de Zébulon.
    De plus, les messages que vous postez en tant qu'invité restent invisibles tant qu'un modérateur ne les a pas validés. Inscrivez-vous, ce sera un gain de temps pour tout le monde, vous, les helpeurs et les modérateurs ! :wink:

Messages recommandés

Posté(e)

Bonjour à tous,

 

Propriétaire d'un nouveau PC depuis 1mois et demi, tout allait bien jusqu'à il y a environ 3 semaines, où est apparu mon 1er BS.

 

Je vais copier coller les 3 analyses de WhoCrashed à suivre, désolé pour le pavé icon_Intelec.gif .

 

On Mon 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-4882-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 that cannot be identified at this time.
On Mon 12/05/2014 20:24:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x29EA6)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800D1DD828, 0xFFFFF8800D1DD080, 0xFFFFF880012C3E83)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
Bug check description: This indicates a problem occurred in the NTFS file system.
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: eamonm.sys (Amon monitor, ESET).
Google query: ESET NTFS_FILE_SYSTEM
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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:
eamonm.sys (Amon monitor, ESET)
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.
On Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051714-4867-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
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 that cannot be identified at this time.
On Sat 17/05/2014 20:16:17 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: iusb3xhc.sys (iusb3xhc+0x24140)
Bugcheck code: 0xA (0x831E9D0, 0x2, 0x1, 0xFFFFF800030DFBC4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\iusb3xhc.sys
product: USB 3.0 Device Driver
company: Intel Corporation
description: Intel® USB 3.0 eXtensible Host Controller Driver
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: iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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:
iusb3xhc.sys (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation)
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.
On Mon 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052614-4508-01.dmp
This was probably caused by the following module: ks.sys (ks+0x10B60)
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 that cannot be identified at this time.
On Mon 26/05/2014 21:14:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ks.sys (ks!KsPinSetPinClockTime+0x1540)
Bugcheck code: 0xBE (0xFFFFF88004CD1B60, 0x800000020E989121, 0xFFFFF88009D4F3F0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\ks.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel CSA Library
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Quelqu'un peut-il m'aider à trouver une solution ?
J'ai l'impression que tout le pc part en cacahuète, et comme il s'agit d'économies depuis des mois, je suis un peu dégouté enerve.gif .. Pour info, j'ai mis à jour NOD32 après le premier BS, et tous mes drivers après le second: je lance une memtest pour le 3ème .. :/
Cdlt
Pierre

Posté(e) (modifié)

bonjour

 

il est parfois tres dificile de déterminer la cause

 

le dernier rapport de Who Crashed n'apporte malheureusement pas beaucoup d'eau au moulin .

 

il faut vérifier aussi dans le gestionnaire de périphérique s'il n'y a pas de problèmes

a ce niveau >> (Intel® USB 3.0 eXtensible Host Controller Driver, Intel Corporation)

 

quand ton controle de mémoire serat fini .

si des problèmes sont décelés

tu seras bon pour un retour SAV ( je suppose que ton PC est garanti)

Modifié par ab-web
Posté(e) (modifié)

Bonjour ab, merci pour ta réponse déjà !

 

2 passes de memtest et aucune erreur décelée .. je ne comprends rien :'(

 

Que faut-il vérifier pour l'usb 3 ? j'ai fait la maj de ce pilote au 2éme BS

Modifié par Kywicha
Posté(e)

hello

 

c'était juste pour voir s'il n'y avais pas un problème signalé comme : un ! ou un ?

 

et si il est déclaré comme fonctionnant correctement .

Posté(e)

Oui c'est marqué fonctionne correctement ! et pilote à jour de février 2014. Je comprends rien du tout ..

->Je peux deviner au 1er BS que mon AV est en cause .. je le mets à jour et ça cesse, et ntfs je pensais avoir un pb sur HDD ou SSD du coup j'ai fait les vérif de windows avec scan des disques, pas de pb ??!

->2ème c'est un peu plus le bordel mais je peux comprendre à travers les recherches google que c'est la ram qui est défectueuse (IRQL_NOT_LESS_OR_EQUAL) et le contrôleur 3.0, du coup j'ai memtest et mis à jour tout le reste + désinstallé Geforce et rinstalle complète

-> 3ème je comprends que la ram est défectueuse mais là encore, memtest dis que tout est vert ! (2 passes)

Surtout que les 2 premiers BS sont arrivées pendant des sessions de BF4, je pensais que c'était lié du coup et hier c'était pendant un LOL donc :/

 

J'imagine que rinstaller complètement W7 ne va rien changer ?

Posté(e)

hello

 

 

J'imagine que rinstaller complètement W7 ne va rien changer ?

effectivement ce n'est pas certain du tout

mais a tu un CD d'installattion

ou c'est un PC , avec partition de recovery ( réinstallation d'usine )?

 

j'aimerais quand même si tu le veux bien controler l'intégritée du système .

 

télécharge et installe ZHPDIAG nous verrons la suite a donner

ZhpDiag


sur le bureau il doit y avoir ces deux icones

thumbs_Capture3adb.PNG

sous XP double clic sur l'icone ZHPDIAG

sous vista - 7 ou 8 - clic droit exécuter en tant qu'administrateur



capture3252.png

clic sur complet , laisse travailler

a la fin du scan le rapport zhpdiag.txt apparait sur le bureau

Comment poster les rapports
Aller sur le site : Cjoint

Appuie sur Parcourir et chercher les rapports sur le bureau
Cliquer sur Ouvrir
Cliquer sur Créer le lien CJoint,
>> dans la page suivante --> ,,
une adresse http//.. sera créée
Copier /coller cette adresse dans votre prochain message.

 

 

Posté(e) (modifié)

J'ai un cd d'install (OEM).

 

Pas de pb, je te fais ça au plus vite et je modifierai ce post pr intégrer le rapport.

 

Voilà : http://cjoint.com/?DEBpMpFmVca

Modifié par Kywicha
Posté(e)

Des nouvelles ab ? :/

Posté(e) (modifié)

bonjour

 

excuse le retard

 

bonne nouvelle pas d'infections

 

un nettoyage de fichiers inutils

 

copie tout le texte en vert ci dessous

 

lance ZHPFIX en tant qu'administrateur clic importer > clic sur GO .

 

Script Zhpfix

O44 - LFC:[MD5.2E770917F6873A048B534D4DD3B45D78] - 27/05/2014 - 11:33:06 ----- . (...) -- C:\bootsqm.dat [3664]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\GoogleCrashHandler.exe [180648]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\GoogleCrashHandler64.exe [233896]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\GoogleUpdate.exe [136176]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\GoogleUpdateBroker.exe [59304]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\GoogleUpdateOnDemand.exe [59304]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdate.dll [811944]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_am.dll [23976]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ar.dll [26024]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_bg.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_bn.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ca.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:02 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_cs.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc.) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ko.dll [22952]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_da.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_de.dll [30632]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_el.dll [30120]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_en-GB.dll [27048]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_en.dll [27048]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_es-419.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_es.dll [30632]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_et.dll [27048]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_fa.dll [27048]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_fi.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_fil.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_fr.dll [30120]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_gu.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_hi.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_hr.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_hu.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_id.dll [27560]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_is.dll [27560]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_it.dll [30120]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_iw.dll [25000]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ja.dll [23976]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_kn.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_lv.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ml.dll [31144]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_mr.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ms.dll [27560]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_nl.dll [29608]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_no.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_pl.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_pt-BR.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_pt-PT.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ro.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ru.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_sk.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_sl.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_sr.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_sv.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_sw.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ta.dll [29096]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_te.dll [28584]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_th.dll [27048]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_tr.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_uk.dll [28072]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_ur.dll [27560]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_vi.dll [27560]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_zh-CN.dll [20904]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_zh-TW.dll [21416]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\npGoogleUpdate3.dll [551848]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\psmachine.dll [157608]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.Google Inc..) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\psuser.dll [157608]
O61 - LFC: 03/11/2014 - 15:37:03 ---A- . (.„Google Inc.“.) -- C:\Users\Pierre\AppData\Local\Temp\{AA7BF71F-6AF4-46DF-B13F-28CA881C36C0}\goopdateres_lt.dll [27560]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_0.bin [16384]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_1.bin [1048576]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_10.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_11.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_2.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_3.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_4.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_5.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_6.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_7.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_8.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_ac78aed3e633319a_0_9.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_0_0.bin [16384]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_0_1.bin [1048576]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_0_2.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_1_0.bin [16384]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_1_1.bin [1048576]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_1_2.bin [8388608]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_2_0.bin [16384]
O61 - LFC: 27/05/2014 - 15:37:02 ---A- . (...) -- C:\Users\Pierre\AppData\Local\Temp\NVIDIA Corporation\NV_Cache\6d1026b4fa6d4c49d77d65f8805a9c0_fce8395c8fd8a85e_c1aa26abfb844f0c_2_1.bin [1048576]
O4 - HKCU\..\Run: [steam] . (.Valve Corporation - Steam Client Bootstrapper.) -- E:\Programmes\Steam\steam.exe
O4 - HKUS\S-1-5-21-1088730531-1601132251-910611079-1000\..\Run: [steam] . (.Valve Corporation - Steam Client Bootstrapper.) -- E:\Programmes\Steam\steam.exe

 

EmptyFlash
EmptyTemp
EmptyClsid
FirewallRaz
Proxyfix
SysRestore

 

héberge le rapport sur http://cjoint.com

 

met le lien dans ta réponse .

Modifié par ab-web
Posté(e)

Rejoindre la conversation

Vous publiez en tant qu’invité. Si vous avez un compte, connectez-vous maintenant pour publier avec votre compte.
Remarque : votre message nécessitera l’approbation d’un modérateur avant de pouvoir être visible.

Invité
Répondre à ce sujet…

×   Collé en tant que texte enrichi.   Coller en tant que texte brut à la place

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.

  • En ligne récemment   0 membre est en ligne

    • Aucun utilisateur enregistré regarde cette page.
×
×
  • Créer...