CACHE_MANAGER Error/ Stop Code 34.. Yes,this is different - HELP!

Hi all,
I have read posts here in reference to the CACHE_MANAGER BSOD and the stop code 34 error, however I could not find a thread that indicates that no matter what I try to do, I get the BSOD..

I try to boot in regular windows, BSOD
I try to log into safe mode, BSOD
I try to log in with networking, BSOD
Tried Command Prompt.. yep,, BSOD

I even get a BSOD when I put in the Windows 7 disc to try a repair and every time, I get the same error...

Not sure what to do.. I mean, even when putting in the Windows 7 CD??

Anyway, I have Windows 7 Ultimate Edition.. tested memory and seems OK... not sure about the hard drive as I could not find where to test it in the BIOS..??

Any help would be greatly appreciated.

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

Had you changed, or moved yours?

Can you boot at all? From the win 7 dvd, to do a repair install?

If you cant and are not under warranty and are a desktop please remove all the ram but one stick and re-try booting.

If you cant boot at all from anything your options are limited. You cant even boot from a portable OS.

Hey Zigzag..
First and foremost, thanks for your reply and assistance on this!

Yes, as stated, I am extremely limited as to what I can try outside of maybe using rescue CDs, everything I try results in BSOD.. even putting in the Windows CD to try a repair results in BSOD...

I also tried to remove memory and put in just one.. same thing. I added memory and no luck..

The only change I made to the desktop prior to this happening was install Panda Global Security as I wanted to try it out. Did boot up after that though a few times. My 9 year old used it as well and was actually standing over him when he logged off (which he did a proper shut down).. The next time I went to log in, this happened.. over and over again and it is on a restart loop after the BSOD

Not sure what to do from here... ??

UPDATE - I started digging into the hardwar of this desktop and noticed in BIOS that the CPU is running between 76 and 78 degrees C.. seems really hot doesnt it? Especially at idle? Not sure if that is normal or an acceptable range..

Also, took out the hard drive for an inspection.. when shaking the hard drive to listen for any clicking etc I noticed that it sounds like what I can best describe as shaking a bean bag.... what the?? This cant be normal?!?! Is it?

Zomolomo said:

UPDATE - I started digging into the hardwar of this desktop and noticed in BIOS that the CPU is running between 76 and 78 degrees C.. seems really hot doesnt it? Especially at idle? Not sure if that is normal or an acceptable range..

Also, took out the hard drive for an inspection.. when shaking the hard drive to listen for any clicking etc I noticed that it sounds like what I can best describe as shaking a bean bag.... what the?? This cant be normal?!?! Is it?

If a hard drive makes any noise it is not normal. A bean bag definitely isnt.

Well, I ended up taking the hard drive out, installing in onto my other desktop and guess what? Same BSOD.. Hard drive was still under warranty.. contacted WD and got a free replacement.. PC is back up and running and using it now as we speak... well, chat! Resolved..

So, for other peeps that may ne having a similar issue, check your hard drive... that may be the culprit!