Bonjour
J'ai un message BAD Pool Header depuis un bout de temps, voici ce que me dit wo crashed: il semblerait que celà vienne de mon antivirus, je l'ai réinstallé mais en vain.
System Information (local)
--------------------------------------------------------------------------------
computer name: ROLAND
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) M processor 1.73GHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 2146844672 total
VM: 2147352576, free: 2039525376
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 12/04/2012 14:27:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-04.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x17EA)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE5CB9000, 0xFFFFFFFFE5CB9408, 0xC810200)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software BAD_POOL_HEADER
On Thu 12/04/2012 12:07:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-03.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x17EA)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE4C27000, 0xFFFFFFFFE4C27408, 0xC810400)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software BAD_POOL_HEADER
On Thu 12/04/2012 08:13:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-02.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x17EA)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE43E8690, 0xFFFFFFFFE43E8A98, 0xC81020C)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software BAD_POOL_HEADER
On Thu 12/04/2012 07:30:20 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini041212-01.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x17EA)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE6989000, 0xFFFFFFFFE6989408, 0xC810200)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).
Google query: aswfsblk.sys AVAST Software BAD_POOL_HEADER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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:
aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software)
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.
Que puis je faire
Merci d'avance
