BSOD During Boot up

[quatin]

I recently bulk installed 70+ updates for my Windows 7 Machine, which caused a hang up on the "shutting down" part of the update. I left it for a couple hours and had to press-hold the power button to recover. I've now gotten a BSOD on a cold boot up of my computer for the past 2 days. It happens for 1 or 2 cycles and then it boots up fine.

I'm thinking the hiccup in the updates is the most likely cause. However, there's a couple other things. I uninstalled/cleaned my HD while updating, removing dozens of programs and GBs of files. My computer also has an issue for the past couple years, where sometimes the screen is frozen when I boot to windows, forcing me to press-hold the power button to restart. There might be a couple BSODs in the minidumps from months before that may or may not be related.

Thanks in advance!

 

[Golden]

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

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 0, fffff800035c1a9b}

*** WARNING: Unable to verify timestamp for avgidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

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

Uninstall AVG. Install MSE. If further BSOD occurs, upload a new zip file.

 

[quatin]

Uninstalled AVG. Installed MSE. Getting a BSOD on a cold boot up sometimes.

 

[quatin]

Now I get BSODs on shut down as well. Attaching a new log.

 

[quatin]

Did this thread get lost? Was I supposed to start a new one?

Meanwhile, I'm starting to think this might be hardware related. Doesn't seem to happen to a warmed up computer. Hope it's not the motherboard again.