karimoo Posted September 19, 2010 Share Posted September 19, 2010 Hi. Not sure if this is just me but a couple of times after I've run the cleaner, and clicked on "Run Cleaner" it will put me into a BSOD. So far its only happened twice, but.. I am getting a STOP message of Bad_Pool_Caller and the hexadecimal is 0x000000c2 (0x00000007, 0x00000CD4, 0x020B0001, 0x88FB1278). Only happens when I run this. BTW I am running this on XP. Is this me? I don't know...but any ideas or anything would be great.. Thanks. Link to comment Share on other sites More sharing options...
Moderators Nergal Posted September 19, 2010 Moderators Share Posted September 19, 2010 Try each cehckmark one at a time. 1 Uncheck everything 2 check the first entry 3 run cleaner 4if no BSOD 5 uncheck the entry 6 check the next entry 7 run cleaner repeat 4-7 When done report to this thread each entry that give BSOD also use http://www.nirsoft.net/utils/blue_screen_view.html and post the actual bluescreen info ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF. Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark) ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T. Support at https://support.ccleaner.com/s/?language=en_US Pro users file a PRIORITY SUPPORT via email support@ccleaner.com Link to comment Share on other sites More sharing options...
redhawk Posted September 19, 2010 Share Posted September 19, 2010 Error messages such as Bad_Pool_Caller are usually associated with bad RAM however to rule out other possibilities such as driver conflicts or disk read errors try chkdsk first - " chkdsk /r c: " If no file system errors found then run Memtest86 to test your RAM. Richard S. Link to comment Share on other sites More sharing options...
Moderators DennisD Posted September 19, 2010 Moderators Share Posted September 19, 2010 Have you recently changed anything on your PC? Installed new drivers, new hardware, upgraded anything? Have you tried a System Restore? If it's a driver gone funny, then System Restore is overkill, but it would fix it rather then trying to track down the culprit. If not, then it's down the route described by the guys above. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now