"serveur occupé...
Fermé
mazals
Messages postés
3
Date d'inscription
samedi 7 janvier 2017
Statut
Membre
Dernière intervention
11 janvier 2017
-
7 janv. 2017 à 02:16
mazals Messages postés 3 Date d'inscription samedi 7 janvier 2017 Statut Membre Dernière intervention 11 janvier 2017 - 11 janv. 2017 à 18:46
mazals Messages postés 3 Date d'inscription samedi 7 janvier 2017 Statut Membre Dernière intervention 11 janvier 2017 - 11 janv. 2017 à 18:46
2 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 628
7 janv. 2017 à 11:18
7 janv. 2017 à 11:18
Salut,
Désinstalle :
Bing Bar
Google Toolbar
McAfee Security Scan Plus
Tu as des restes de Symantec Norton, supprime le : https://www.commentcamarche.net/faq/3151-desinstaller-norton-symantec
C'est probablement COMODO qui génère ces problèmes.
Faudrait tenter de le désinstaller.
Désinstalle :
Bing Bar
Google Toolbar
McAfee Security Scan Plus
Tu as des restes de Symantec Norton, supprime le : https://www.commentcamarche.net/faq/3151-desinstaller-norton-symantec
C'est probablement COMODO qui génère ces problèmes.
Faudrait tenter de le désinstaller.
mazals
Messages postés
3
Date d'inscription
samedi 7 janvier 2017
Statut
Membre
Dernière intervention
11 janvier 2017
11 janv. 2017 à 18:46
11 janv. 2017 à 18:46
Me revoilà,
J'ai fait ce que tu m'as indiquer et j'ai changé d'antivirus pour Total 360 security.
Je viens d'avoir un BSOD et du coup j'ai lancé un diagnostic avec Whocrashed que voici :
System Information (local)
--------------------------------------------------------------------------------
Computer name: MAZALS
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP Pavilion dv7 Notebook PC, Hewlett-Packard, 1803
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535261184 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 11/01/2017 17:53:52 your computer crashed
crash dump file: C:\Windows\Minidump\011117-27861-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003820B60, 0x0, 0xFFFFF80003820B60)
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 Wed 11/01/2017 17:53:52 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: 360fsflt.sys (360FsFlt+0xC6C8)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003820B60, 0x0, 0xFFFFF80003820B60)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\360fsflt.sys
product: 360 Total Security
company: 360.cn
description: 360 Total Security
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).
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: 360fsflt.sys (360 Total Security, 360.cn).
Google query: 360.cn BAD_POOL_HEADER
--------------------------------------------------------------------------------
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:
360fsflt.sys (360 Total Security, 360.cn)
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.
Où trouver la mise à jour ...?
Merci !
J'ai fait ce que tu m'as indiquer et j'ai changé d'antivirus pour Total 360 security.
Je viens d'avoir un BSOD et du coup j'ai lancé un diagnostic avec Whocrashed que voici :
System Information (local)
--------------------------------------------------------------------------------
Computer name: MAZALS
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP Pavilion dv7 Notebook PC, Hewlett-Packard, 1803
CPU: GenuineIntel Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8535261184 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 11/01/2017 17:53:52 your computer crashed
crash dump file: C:\Windows\Minidump\011117-27861-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003820B60, 0x0, 0xFFFFF80003820B60)
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 Wed 11/01/2017 17:53:52 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: 360fsflt.sys (360FsFlt+0xC6C8)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003820B60, 0x0, 0xFFFFF80003820B60)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\360fsflt.sys
product: 360 Total Security
company: 360.cn
description: 360 Total Security
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).
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: 360fsflt.sys (360 Total Security, 360.cn).
Google query: 360.cn BAD_POOL_HEADER
--------------------------------------------------------------------------------
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:
360fsflt.sys (360 Total Security, 360.cn)
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.
Où trouver la mise à jour ...?
Merci !
8 janv. 2017 à 00:10
Merci pour la réponse.
Je fais tout ça et te tiens au courant si tout rentre dans l'ordre.