Solved [x64] BSOD on startup, 0x19 BAD_POOL_HEADER

[FredyC]

It's almost fresh computer, hardware and software. My first time with x64 OS. I am afraid I had over-optimized it as I wanted fast and nice computer after all those years of ignorance. So reading bunch of tutorials, articles and setting things.

I will probably go for another reinstall, but I would like to find out what's the problem with this, so I can avoid it for reinstallation.

Thanks for advice.

 

[Dsprague]

First things first, your using windows 7 enterprise, normally the only way to get this version of windows is through a volume license key from a business. If this is a work PC you should contact your IT department with the problem you are having.

 

[FredyC]

Well it's not work PC, but it's one of the job benefits, that we can use their W7 license at home.

 

[Dsprague]

In that case, Comodo is your problem it is causing your BSODs:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa800b660010, 0, fffffa800b660010}
[COLOR=Red]
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys[/COLOR]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup: Pool_corruption
---------

Driver Reference Table - cmdguard.sys

Please uninstall it then replace it with a combination of MSE and Mbam. Tip: When installing Mbam Be sure to uncheck the box offering to start a free trial.

 

[FredyC]

Hmm, that is really sad, I really like Comodo. I thought thing like this is made to be in top shape. I will try Comodo forums first if there is not some solution. Thanks anyway.

 

[FredyC]

In the end, it was all about faulting RAM modules...