Problème de navigateur [Résolu]

Azereck 85 Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention - 20 nov. 2017 à 11:53 - Dernière réponse : Azereck 85 Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention
- 1 déc. 2017 à 02:25
Bonjour, comme marqué dans le titre, j'ai un problème sur mon navigateur (Google Chrome) j'ai Chromesearch.today et je n'arrive pas à m'en débarrasser...
Et je pense qu'à cause de lui, il fait planter mon ordinateur (quand je souhaite le démarrer, il m'affiche un écran bleu avec marqué qu'une erreur est survenue concernant Windows je crois) et je dois le redémarrer au moins 3,4 fois avant que je puisse atteindre mon bureau. Il ne faisait jamais ça avant que Chromeserach.today apparaisse sur mon ordinateur.

Si quelqu'un peut m'aider, je vous en serais éternellement reconnaissant.

Merci d'avance.
Afficher la suite 
85Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention

14 réponses

Répondre au sujet
Destrio5 87044 Messages postés dimanche 11 juillet 2010Date d'inscriptionModérateurStatut 10 décembre 2017 Dernière intervention - 20 nov. 2017 à 13:43
0
Utile
13
Bonjour,

--> Télécharge Farbar Recovery Scan Tool (de Farbar) sur ton Bureau.

Attention : tu dois prendre la version compatible avec ton système : 32 ou 64 bits.

32 ou 64 bits - Comment savoir ?

--> Ferme toutes les applications en cours.
--> Lance FRST (Sous Windows Vista/7/8/10, clic droit sur FRST > Exécuter en tant qu'administrateur).
--> Coche la case Addition.txt.
--> Clique sur Analyser.
--> Une fois le scan terminé, deux rapports FRST.txt et Addition.txt seront présents sur le Bureau.
--> Héberge les deux rapports sur pjjoint.malekal.com et copie-colle les liens fournis dans ta prochaine réponse.
Azereck 85 Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention - 27 nov. 2017 à 11:21
Mon PC plante toujours autant. Qu'est ce que je dois faire ?
Destrio5 87044 Messages postés dimanche 11 juillet 2010Date d'inscriptionModérateurStatut 10 décembre 2017 Dernière intervention - 27 nov. 2017 à 20:23
Fais une analyse avec WhoCrashed pour voir et transmets-moi le résultat :
https://www.malekal.com/tutoriel-whocrashed/
Azereck 85 Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention - 27 nov. 2017 à 23:20
Welcome to WhoCrashed (HOME EDITION) v 5.54

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)

Computer name: WINDOWS-HQC4RC3
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: MS-7817, MSI, B85M-E45 (MS-7817)
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17104379904 bytes total



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 27/11/2017 11:19:16 your computer crashed
crash dump file: C:\Windows\Minidump\112717-37830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFC9D3200001A, 0x0, 0xFFFFF80004167BAC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 27/11/2017 11:19:16 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: amifldrv64.sys (amifldrv64+0x1A04)
Bugcheck code: 0x50 (0xFFFFFC9D3200001A, 0x0, 0xFFFFF80004167BAC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: amifldrv64.sys .
Google query: amifldrv64.sys PAGE_FAULT_IN_NONPAGED_AREA



On Mon 27/11/2017 11:14:26 your computer crashed
crash dump file: C:\Windows\Minidump\112717-37752-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8013EC2000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27/11/2017 11:09:23 your computer crashed
crash dump file: C:\Windows\Minidump\112717-40653-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFCA5E400001A, 0x0, 0xFFFFF800041ACBAC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 27/11/2017 11:04:15 your computer crashed
crash dump file: C:\Windows\Minidump\112717-39577-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70E00)
Bugcheck code: 0x50 (0xFFFFFC560D00001A, 0x0, 0xFFFFF8000417ABAC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.




Conclusion

7 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

amifldrv64.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
Destrio5 87044 Messages postés dimanche 11 juillet 2010Date d'inscriptionModérateurStatut 10 décembre 2017 Dernière intervention - 28 nov. 2017 à 09:52
Cela parle du pilote amifldrv64.sys. Il serait en lien avec MSI. J'ai vu que tu avais effectivement une carte mère MSI et que tu avais installé les utilitaires de la marque. Tu as la version 6.2.0.19 de MSI Live Update 6, le site officiel propose la version 6.2.0.23 :
http://download.msi.com/uti_exe/LiveUpdate.zip

Je ne sais pas si ça va résoudre ton problème, à tester.
Azereck 85 Messages postés mardi 7 juillet 2015Date d'inscription 1 décembre 2017 Dernière intervention - 1 déc. 2017 à 02:25
J'ai fait ce que vous m'avez conseillé de faire et pour l'instant, je n'ai pas de problème au démarrage, je vous remercie énormément.
Commenter la réponse de Destrio5