PROBLEMA BAD POOL HEADER

[klasher]

Ciao a tutti, ho il seguente problema, ogni tanto, abbastanza randomicamente, il pc mi va in crash, blue screen of death, con il seguente errore "Bad pool header"
Qualcuno ha idea di come si risolva?
grazie

 

[Federico83]

Ciao a tutti, ho il seguente problema, ogni tanto, abbastanza randomicamente, il pc mi va in crash, blue screen of death, con il seguente errore "Bad pool header"
Qualcuno ha idea di come si risolva?
grazie

scarica e posta il log di whocrashed e vediamo di che si tratta

 

[SuperXmod]

Ciao a tutti, ho il seguente problema, ogni tanto, abbastanza randomicamente, il pc mi va in crash, blue screen of death, con il seguente errore "Bad pool header"
Qualcuno ha idea di come si risolva?
grazie

Utilizza anche BlueScreenView;
32 Bit: http://www.nirsoft.net/utils/bluescreenview.zip
64 bit: http://www.nirsoft.net/utils/bluescreenview-x64.zip

Posta uno screen di entrambi i tool.

 

[klasher]

intanto grazie, posto screen, fatemi sapere che ne pensate!

Crash Dump Analysis

---

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 24/04/2016 11.08.14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-59765-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE0016DF3EC20, 0xFFFFE0016DF3EC40, 0x4020012)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 24/04/2016 11.08.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, 0xFFFFE0016DF3EC20, 0xFFFFE0016DF3EC40, 0x4020012)
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

---

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:

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 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.






- - - Updated - - -

Ulteriore crash qualche minuto fa :(

On Sun 24/04/2016 17.28.39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-91515-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE001AAA00110, 0xFFFFE001AAA00130, 0x4020011)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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.

e ancora...

[FONT=Segoe UI, Arial]On Sun 24/04/2016 17.39.07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-89109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE001BBE61730, 0xFFFFE001BBE61750, 0x4020004)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver TCP/IP
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.
[/FONT]
possibile sia causato da bitdefender 2016 che in qualche modo interferisce con malwarebytes?

 

[Federico83]

intanto grazie, posto screen, fatemi sapere che ne pensate!

Visualizza allegato 203132Crash Dump Analysis

---

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 24/04/2016 11.08.14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-59765-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE0016DF3EC20, 0xFFFFE0016DF3EC40, 0x4020012)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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 24/04/2016 11.08.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, 0xFFFFE0016DF3EC20, 0xFFFFE0016DF3EC40, 0x4020012)
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

---

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:

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 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.






- - - Updated - - -

Ulteriore crash qualche minuto fa :(

On Sun 24/04/2016 17.28.39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-91515-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE001AAA00110, 0xFFFFE001AAA00130, 0x4020011)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
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.

e ancora...

[FONT=Segoe UI, Arial]On Sun 24/04/2016 17.39.07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042416-89109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x1C0180)
Bugcheck code: 0x19 (0x20, 0xFFFFE001BBE61730, 0xFFFFE001BBE61750, 0x4020004)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver TCP/IP
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.
[/FONT]
possibile sia causato da bitdefender 2016 che in qualche modo interferisce con malwarebytes?

prova a disabilitare entrambi e vedi se continua a dare problemi

 

[klasher]

provo e riferisco :)

 

[SuperXmod]

intanto grazie, posto screen, fatemi sapere che ne pensate!

Visualizza allegato 203132
possibile sia causato da bitdefender 2016 che in qualche modo interferisce con malwarebytes?

Secondo me è un qualcosa che manda in conflitto i driver di rete;

Se non li hai installi, installa i driver proprietari della tua scheda di rete, si, può essere anche un conflitto tra Malwarebytes e Bitdefender. Ti ricordo inoltre, di togliere ogni singolo programma dall'avviamento automatico, esegui un avvio come è chiamato in gergo 'Pulito', ossia senza alcun programma non necessario all'avvio.

 

[klasher]

Secondo me è un qualcosa che manda in conflitto i driver di rete;

Se non li hai installi, installa i driver proprietari della tua scheda di rete, si, può essere anche un conflitto tra Malwarebytes e Bitdefender. Ti ricordo inoltre, di togliere ogni singolo programma dall'avviamento automatico, esegui un avvio come è chiamato in gergo 'Pulito', ossia senza alcun programma non necessario all'avvio.

ho disattivato malwarebytes e da allora non ho più avuto problemi...
grazie comunque!

 

[Federico83]

chiudo alla prox