bad pool header

[kalm]

Beste helpers, ik heb een windows 8 zo juist geinstelleerd. Nu krijg ik de melding, dat er fouten zijn gevonden en de naam van de fout is: Bad Pool Header.
Hoe kan ik dit oplossen?

 

[Lange Pier]

Dat een te algemene fout om er iets zinnigs over te zeggen, welke anti virus wordt er gebruikt?

Genereer met deze tool een log voor de 0x0 code en het bestand wat het veroorzaakt.
http://www.resplendence.com/whocrashed

 

[kalm]

Bad Pool

Hoi bedankt voor uw hulp,
Ik gebruikt Avast antivirus.
ik ga nu aan de slag met het tooltje, tot zo.

 

[kalm]

Bad Pool

Dit is eruit gekomen.
Wat moet ik doen?
--------------------------------------------------------------------------------

computer name: TOP
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: A6VMX, FOXCONN
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 938790912 total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 26-4-2015 16:13:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042615-14671-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C2180) 
Bugcheck code: 0x19 (0x20, 0xFFFFE00029CF4810, 0xFFFFE00029CF4830, 0x4020081)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\tcpip.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-stuurprogramma
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 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 Sun 26-4-2015 16:13:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135) 
Bugcheck code: 0x19 (0x20, 0xFFFFE00029CF4810, 0xFFFFE00029CF4830, 0x4020081)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
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: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation). 
Google query: Malwarebytes Corporation BAD_POOL_HEADER



On Sun 26-4-2015 16:03:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042615-22984-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C2180) 
Bugcheck code: 0x19 (0x20, 0xFFFFE0012E9ECE30, 0xFFFFE0012E9ECE50, 0x40200E3)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\tcpip.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: TCP/IP-stuurprogramma
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 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
--------------------------------------------------------------------------------

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: 

mwac.sys (Malwarebytes Web Access Control, Malwarebytes 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 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.

 

[Lange Pier]

http://support.amd.com/en-us/download

Kijk eens of deze tool nieuwere AMD drivers vind om mee te beginnen.

Het is een driver probleem maar daar staan ook weer diverse bestanden die het veroorzaken.