Bad_Pool_Caller 0xC2 killed hard drive?

Pali

Well my hard-drive has apprently died on me.. Bad_Pool_Caller 0xC2 ... lovely.

Quad Core Q6600 (2.4ghz)
500GB WD Hard Drive
4GB Ram (Geil Pc2-6400 1gb *4)
Geforce 8800GTS 640mb

I was running a fresh install of xp so I could use the upgrade disk to Vista ultimate.

I Installed Motheboard drivers here so the Vista install would go ahead.

All good once Vista took its sweet time installing, I had my fresh Vista desktop.

I then installed:
Nvidea drivers
Firefox
PC plus firewall
Avast
Ultramon
MSN
Rainladar

After a little while I got Bad_Pool_Caller 0xC2, for my nice BSOD.

After rebooting i am greeted with "Boot drive Failure - Insert boot disk" so I follow instructions. It brings me back to the repair/install screen and behold my nice lovely 500Gb drive where my OS was is now non-existant.

I've ordered a new 500Gb drive because I could do with the space if the other one is salvageable.



What is the problem here?

Is it just the drive dead?

Is it the Bad_Pool_Caller 0xC2 making it unseeable?

Is it just Vista? =S

Fristle

The blue screen error code, "Bad Pool Caller," means that some driver has made an invalid pool request. A pool request is a kind of memory allocation (there is more detail in the blue screen message, which also gets stored to disk as a Minidump file in your C:\Windows\Minidump\ directory, if you can still retrieve that from the disk). This kind of fault can be a symptom of many things, but if I were you I might download and run the Windows Memory Diagnostic.

alfredalbert

Blue screen of death or bad pool caller is encountered because of various reasons like due to outdated drivers, registry problem or in some cases due to viruses or spyware. But in most of the cases it is occurred because of registry problem. Once i had also passed from the same kind of situation and at that time i had tried registry repair software and finally managed to fix this error. So i will suggest you to repair registry file by using nay third party registry repair software. I think that after repairing registry files this bad pool caller error will definitely get resolved. Wish you all the best.

Foomy

bsod can sometimes mess up boot records if something bad enough happens, go find a windows disk (boot with it, than select repair, than run recovery console), or some dos bootdisk like http://www.ultimatebootcd.com/ and than get into a command prompt, than try running fdisk /mbr and try a mbr repair. than usually fixes it up and will get you back to where you were before the bsod happened.