My main workshop PC (windows XP, Intel dual-core CPU, 2GB DDR3 RAM, WD HDD, Gigabyte mobo, etc… nothing fancy) has been quiet for a few days (another quiet time in business 🙁 ).
So when I started it today, I was surprised to get a blue screen of death: error 0x000000c2 bad_pool_caller
I figured: maybe RAM, maybe the video card… but it was neither.
So, after pressing F8 at boot time, I selected “last known configuration that worked”
And this turned out to be one of the rare times that it actually worked.
As soon as the PC started, taskbar icon for Microsoft security essentials appeared in red… It really wanted to update the software (not just a signature update, it was completely new software.
So I figure: sure, its always best to be safe to keep the AV up to date.
But part way through the update, the computer did another BSOD.
I fixed it again (last known configuration that worked).
Now, when I cast my mind back a few days, to when I last used the PC, I remember doing a windows update, and I got a BSOD. Because I was in a hurry, I just left it, and then forgot to get back to fixing it.
- I uninstall MSE
- I restart the PC
- I download the latest MSE from the microsoft website
- I install the latest MSE and…
- BSOD !
Wow, that proves that the latest MSE either doesn’t like my PC, or it doesn’t like XP in general.
I have another XP PC, but it has the latest MSE, and I get no BSOD from it…
Its a mystery. Next chance I get, I’ll be installing another anvivirus program & see what difference that makes.