BSOD for Bad Pool Header on Win 8.1 64 bit

Georgey

Member
Joined
May 23, 2016
Posts
24
Hello,

Recently I've encountered BSOD with the message Bad Pool Header several times. Both sfc/scannow and Dism.exe /Online /Cleanup-Image /Scanhealth reported no issue to fix.

I run Windws 8.1 64 bit on a 5.5 year old Samsung laptop R439; intel i5 double core processor.


Please find enclosed the SysnativeFileCollectionApp.zip file. While I tried to run perfmon /report I got the error message
Rescue and Performance Monitor: 'An error occurred while attempting to generate the report.
Element not found.'

Thank you very much.
 

Attachments

Since I ran SysnativeBSODCollectionApp.exe and Driver Verifier Malwarebytes Anti Exploit wouldn't start. What could've happened, how to get it back?

I have AVG PC Tune Up 2016, I've ran its Disk Doctor now, does this suffice instead of the recommended HDD Diagnostics?
 
Hi Georgey,

I cannot help with MBAE not starting, but for the BSODs try following please
- Open Bitdefender and go to the modules,
- Go to the firewall settings,
- Disable 'Block port scans in the network',
- Reboot your system

The crashes are caused by a driver conflict between Bitdefender Firewall and Malwarebytes Web Protection.
There are many different solutions you could try aside from this one, but this one works for most.

Bitdefender & Malwarebytes are working on fixing this problem so you can enable the firewall settings again.
 
Thank you, I've done this right away.
As to MBAE, if your suggestion works, I go back to a restore point or recovery image before I did the preceding steps, and do only what you said.
 
Since I ran SysnativeBSODCollectionApp.exe and Driver Verifier Malwarebytes Anti Exploit wouldn't start. What could've happened, how to get it back?

Very likely, Driver Verifier flagged a MBAM driver thus disabling it. SysnativeBSODCollectionApp.exe is a collection tool and makes no changes to your system.

Try reinstalling MBAM.

Regards. . .

jcgriff2
 
I've restored a recovery image from before I ran Driver Verifier, and per axe0's advice I disabled 'Block port scans in the network' in Bitdefender. MBAM works fine and so far no BSOD, thank you again axe0.

Could I possibly set something in Driver Verifier to prevent the conflict between Bitdefender's and MBAM's drivers so I could re-enable this function in Bitdefender? Thank you.
 
Driver verifier catches drivers when they violate something resulting in a BSOD, driver verifier is not a tool for preventing a conflict.

The developers need to check the code and rewrite it and/or add code to prevent the conflict, there is nothing else that can be done to prevent the conflict.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top